Could either be an IP address conflict on the LAN or RPM database corruption. I ran into this myself a while back. See below.
BCM 4.0 cannot log in using Element Manager, getting error: "BCM detector cannot determine the device type for {BCM IP ADDRESS}"
--------------------------------------------------------------------------------
Problem Description
BCM 4.0 cannot log in using Element Manager with any BCM user account, getting error: "BCM detector cannot determine the device type for {BCM IP ADDRESS}". Same Element Manager client is able to access other BCM 4.0 and BCM50 systems without issue. Problem is directly associated with the BCM 4.0 site that access is being attempted on. BCM Monitor, Web page, and serial port are accessible using same user accounts denied access using Element Manager.
When trying to connect to BCM 4.0 using Element Manager get the following error.
This may be a result of RPM database corruption. This is normally observed by the following symptoms:
1) Select the IP address of the BCM using Element Manager. Do not connect. On the right hand pane, the System Software Version should include the correct version. If it is not populated, this would possibly suggest RPM database corruption.
2) Attempts to connect to the same BCM using Web browser interface and/or BCM Monitor are successful.
3) By downloading and observing the logs. Namely systemInformation\tmp\InstalledSoftware.txt. Attached is a "sample good InstalledSoftware.txt" file which shows a normal "InstalledSoftware.txt". Attached is a "sample bad InstalledSoftware.txt" file which shows an abnormal (truncated / shortened) "InstalledSoftware.txt"
4) Unable to connect to the BCM as per above graphic.
Assuming these symptoms are observed, then the affected BCM 4.0 system's RPM database is likely corrupt. This database is a set of files that resides in /var/local/lib/rpm. They look like this:
[root@bcm40 rpm]# ls -l
total 5464
-rw-r--r-- 1 root root 335872 Mar 13 18:32 Basenames
-rw-r--r-- 1 root root 86016 Mar 13 18:32 Dirnames
-rw-r--r-- 1 root root 323584 Mar 13 18:32 Filemd5s
-rw-r--r-- 1 root root 12288 Mar 13 18:32 Group
-rw-r--r-- 1 root root 12288 Mar 13 18:32 Installtid
-rw-r--r-- 1 root root 12288 Mar 13 18:32 Name
-rw-r--r-- 1 root root 1925120 Mar 13 18:32 Packages
-rw-r--r-- 1 root root 90112 Mar 13 18:32 Providename
-rw-r--r-- 1 root root 28672 Mar 13 18:32 Provideversion
-rw-r--r-- 1 root root 40960 Mar 13 18:32 Requirename
-rw-r--r-- 1 root root 28672 Mar 13 18:32 Requireversion
-rw-r--r-- 1 root root 24576 Mar 13 18:32 Sha1header
-rw-r--r-- 1 root root 24576 Mar 13 18:32 Sigmd5
-rw-r--r-- 1 root root 12288 Mar 13 18:32 Triggername
-rw-r--r-- 1 root root 8192 Mar 13 18:22 __db.001
-rw-r--r-- 1 root root 1310720 Mar 13 18:22 __db.002
-rw-r--r-- 1 root root 360448 Mar 13 18:22 __db.003
[root@bcm40 rpm]# pwd
/var/local/lib/rpm
This database contains information about the versions of all of the software installed on the BCM 4.0 system. The RPM database is created at system build time, and is updated when the BCM is patched or upgraded.
Please note:
The problem is currently under investigation on BCM 4.0. The problem may also occur on BCM50s, however this is not conclusive (partners have done a reset level 2 to recover, before further diagnosis has been done). In order to assist Nortel, where possible on a BCM50, please report the problem and do not perform level 2 reset.
Problem Resolution
Where RPM Database corruption is identified:
- Partners experiencing this issue should open a case and obtain logs (via http, select "Administrator Applications" and select "Retrieve Log Files") from systems exhibiting RPM corruption for analysis. Please provide remote access details when raising the case.
- A workaround using a replacement RPM database file is available in extreme circumstances requiring system access using Element Manager. The workaround will require Nortel Support intervention to generate the replacement database file based on patches applied to the system. Site logs are especially helpful in reducing resolution time to determine the patch level of the affected system and build the replacement RPM patch database file. Rebuild of the RPM database will require extensive Nortel Support lab time to generate the replacement file due to the requirement for the exact patch level as the affected site.
- Data collection tools to ascertain HDD characteristics and create a resulting data file for Design analysis is attached to this solution as hdd_data.tgz. This tool will require Nortel Support to facilitate the data collection as root access is required to collect the data. Resulting data captures should be attached to CR #Q01540071
- CR #Q01540071 is open and under investigation to determine the trigger event for the RPM corruption. Logs should be attached to CR #Q01540071 if available.
- Cases opened against this issue should be linked to Solution #S00281307 in Clarify as it is linked to CR #Q01540071.
- Attached .tar file for an unpatched system is attached to this solution and may be used by Nortel Support to lessen file creation time if the files apply to the affected site.
- Use of the attached .tar files requires bsh shell access to the affected BCM, which requires a BCM 4.0 Password of the Day. These replacement RPM database files should not be applied to the system except under direct instruction or supervision by Nortel Support.
Where RPM Database corruption is not identified:
- Please refer to solution 5047231 - BCM 4.0 cannot log in using Element Manager, getting error: "BCM detector cannot determine the device type for {BCM IP ADDRESS}" not resolved by solution 9834392 (RPM database corruption)
