CG boards fail to boot after upgrade from AG boards

http://www.dialogic.com/support/helpweb/helpweb.aspx/2877/cg_boa...

Technical Helpweb
Dialogic NaturalAccess Products - more articles
CG boards fail to boot after upgrade from AG boards
Symptom: After upgrading from Dialogic AG boards to Dialogic CG boards the CG board fails to boot when using oamsys. Subsequently, running "oamcfg -q" still shows the AG board in the oamcfg query output. Or, the CG board will just fails to boot after system reboot. The failure has output is similar one of the following:

Possible failure 1: oamcfg -p Stopping all boards. Fri Apr 28 10:41:33 - OAMEVN_STOPBOARD_REQ INFO Board 0 "CG_6565 0" Stop board in 150ms. Fri Apr 28 10:41:34 - OAMEVN_ALERT ERROR "cg6kpi.bpi" Cannot stop board CG_6565 0 - board not found Fri Apr 28 10:41:34 - OAMEVN_STOPBOARD_DONE OAM_REASON_FAILED ERROR Board 0 "CG_6565 0" Failed to stop board. Possible failure 2: Fri Mar 18 15:55:56 - OAMEVN_ALERT ERROR "cg6kpi.bpi" Cannot start board CG6565C_B1 - not found on bus 9, slot 14 Fri Mar 18 15:55:56 - OAMEVN_ALERT ERROR "cg6kpi.bpi" Cannot start board CG6565C_B2 - not found on bus 9, slot 13 Fri Mar 18 15:55:56 - CLKEVN_CONFIG_FAILED ERROR Board 1 "CG6565C_B1" CLKMGR.EMC: Board fail to Boot Reason for the issue: When booting up boards, oamsys uses the information stored in the OAM database. It's possible that the OAM database was not updated properly after upgrading to a different board using the same PCI bus and slot, or the database files became corrupted for an unknown reason. The invalid information in the database results in various board failures when running oamsys. Workaround: The OAM database is made up of a set of *.xmo files, if one of these .xmo files is corrupted, then the oamsys board booting process will not run correctly. To workaround this, simply remove all the .xmo files. For Windows: in the \nms\oam\cfg folder For UNIX: in /opt/nms/oam/cfg. Here is the procedure to follow: 1. Stop the ctdaemon service 2. Go to the \nms\oam\cfg directory and delete all the files with the .xmo extension 3. Restart ctdaemon service 4. Try bootup the board again using oamsys When the .xmo files do not exist, oamsys recreates these files, so the new .xmo files will contain the most up-to-date information. It is recommended to try the above steps any time there are boot failures related to the OAM database. Product List: All Dialogic CG boards. All Dialogic Natural Access releases.

Glossary of Acronyms: PCI -- Peripheral component interconnect; a 32/64 bit local bus inside a PC. OAM -- Operations, administration, and maintenance: an industry term for system management operations. Related Documentation: http://www.dialogic.com/webhelp/NaturalAccess/Release9.0/OAM_System_Dev_Manual/default.htm

1 of 1

04.09.12 8:41 AM