Environment
Novell Teaming + Conferencing
Situation
Troubleshooting Conferencing and the NMS card installation and configuration
Resolution
Where can I get the NMS card drivers for Teaming + Conferencing?
The drivers are available on the Novell download site, https://download.novell.com/Download?buildid=Nee_OLad1Yo~
Will the NMS drivers work on a different kernel version than the one stated in the readme file?
The NMS drivers are tightly coupled with the 32 bit SLES 10sp1 kernel (2.6.16.46-0.12). This is the only supported kernel for Teaming + Conferencing audio option. The 'bigsmp' kernel is not supported and must be replaced if installed.
How can I tell if the board is installed correctly?
After the drivers are installed run '/opt/nms/bin/pciscan'. If the board is detected then it is installed correctly.
How can I tell if the board is configured correctly?
After running the 'nmsconfig' command, run 'oamsys' and verify that the board boots up correctly. Refer below to an example output from 'oamsys' where the board that is configured correctly:
oamcfg -d
oamcfg -c"CG_6565" -n"CG_6565 - 0" -b0 -l2:3 -f"C:/NMS/CG/CFG/Board0.cfg"
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
After running oamsys I see the message "Failed to start board". What happened?
You may have chosen the wrong MIPS for the board. Re-run 'nmsconfig', when asked for the number of MIPS choose an option that has less MIPS than the one you chose before.
Refer below for an example output of oamsys for a board that is configured incorrectly and fails to start:
oamcfg -d
oamcfg -s
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
OAMEVN_ALERT ERROR Board 0 "CG_6565 - 0"
OAMEVN_STARTBOARD_DONE
My board has booted. How do I check the physical trunks for alarms?
Run the command '/opt/nms/bin/trunkmon' to verify the status of every trunk.
How do I turn logging on for the conference bridge?
In the file '/opt/iic/conf/config.xml' change <level>error</level> to <level>debug</level> and restart all of the services.
My conference bridge doesn’t come up and I’ve turned logging on, what should I look for in the log file?
Check '/var/log/iic/voice.log' to ensure a proper license file is used. Also search for the string "NMS" and any related error messages.
The conference bridge loads. I’m connecting to the bridge via an ISDN line. I’m unable to place calls to the conference bridge. What could be wrong?
Ensure you have the proper ISDN parameters in the '/opt/iic/conf/voiceconfig.xml' file:
(Check “isdncta –h” for other operator values)
I can connect to the bridge with my PC client when I’m inside the firewall. What ports do I need open in order to connect outside the firewall?
You will need to open ports 443, 80 and 4569.
I have my inbound sip calls to the conference bridge working correctly. How do I configure the bridge to make outbound sip calls?
The drivers are available on the Novell download site, https://download.novell.com/Download?buildid=Nee_OLad1Yo~
Will the NMS drivers work on a different kernel version than the one stated in the readme file?
The NMS drivers are tightly coupled with the 32 bit SLES 10sp1 kernel (2.6.16.46-0.12). This is the only supported kernel for Teaming + Conferencing audio option. The 'bigsmp' kernel is not supported and must be replaced if installed.
How can I tell if the board is installed correctly?
After the drivers are installed run '/opt/nms/bin/pciscan'. If the board is detected then it is installed correctly.
How can I tell if the board is configured correctly?
After running the 'nmsconfig' command, run 'oamsys' and verify that the board boots up correctly. Refer below to an example output from 'oamsys' where the board that is configured correctly:
/> oamsys
oamcfg -p
Stopping all boards.
OAMEVN_STOPBOARD_REQ INFO Board 0 "CG_6565 - 0"
Stop board in 150ms.
OAMEVN_STOPBOARD_DONE Finished INFO Board 0 "CG_6565 – 0"
Board is stopped.
oamcfg -d
Deleting all boards from database.
oamcfg -c"CG_6565" -n"CG_6565 - 0" -b0 -l2:3 -f"C:/NMS/CG/CFG/Board0.cfg"
Creating new board of product type "CG_6565".
Updating keywords in board.
oamcfg -s
Starting all boards.
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
2:3 - log cg6x6x boot info to file C:\NMS\OAM\log\CG_6565boot_2_3.txt
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
Writing at SDRAM 0xfd1987f for 1467049 bytes ...
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
Board Event 0x121e: Ethernet Link #2 State: UP, Speed: 100MB, Duplex: FULL
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
cg6565core.ulm loaded, version 2.10030, built Feb 12 2008 15:10:32
fusion.dlm loaded, version 2.10030, built Jul 17 2007
OAMEVN_STARTBOARD_DONE Finished INFO Board0 "CG_6565 - 0"
Board is started.
After running oamsys I see the message "Failed to start board". What happened?
You may have chosen the wrong MIPS for the board. Re-run 'nmsconfig', when asked for the number of MIPS choose an option that has less MIPS than the one you chose before.
Refer below for an example output of oamsys for a board that is configured incorrectly and fails to start:
/>oamsys
oamcfg -p
Stopping all boards.
OAMEVN_STOPBOARD_REQ INFO Board 0 "CG_6565 - 0"
Stop board in 150ms.
OAMEVN_STOPBOARD_DONE Finished INFO Board 0"CG_6565 - 0"
Board is stopped.
oamcfg -d
Deleting all boards from database.
oamcfg -c"CG_6565" -n"CG_6565 - 0" -b0 -l2:3 -f"C:/NMS/CG/CFG/Board0.cfg"
Creating new board of product type "CG_6565".
Updating keywords in board.
oamcfg -s
Starting all boards.
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
2:3 - log cg6x6x boot info to file C:\NMS\OAM\log\CG_6565boot_2_3.txt
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
Writing at SDRAM 0xfd1987f for 1467049 bytes ...
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
Board Event 0x121e: Ethernet Link #2 State: UP, Speed: 100MB, Duplex: FULL
OAMEVN_ALERT INFO Board 0 "CG_6565 - 0"
cg6565core.ulm loaded, version 2.10030, built Feb 12 2008 15:10:32
fusion.dlm loaded, version 2.10030, built Jul 17 2007
OAMEVN_ALERT ERROR Board 0 "CG_6565 - 0"
Failed in RM_LOAD_RESOURCE_COMPLETE with error code 519
OAMEVN_ALERT ERROR "cg6kpi.bpi"
Cannot start board CG_6565 - 0 - failed to configure board
CLKEVN_CONFIG_FAILED ERROR Board 0 "CG_6565 -0"
CLKMGR.EMC: Board fail to Boot
OAMEVN_STARTBOARD_DONE
OAM_REASON_FAILED ERROR Board 0 "CG_6565 – 0"
Failed to start board.
My board has booted. How do I check the physical trunks for alarms?
Run the command '/opt/nms/bin/trunkmon' to verify the status of every trunk.
How do I turn logging on for the conference bridge?
In the file '/opt/iic/conf/config.xml' change <level>error</level> to <level>debug</level> and restart all of the services.
My conference bridge doesn’t come up and I’ve turned logging on, what should I look for in the log file?
Check '/var/log/iic/voice.log' to ensure a proper license file is used. Also search for the string "NMS" and any related error messages.
The conference bridge loads. I’m connecting to the bridge via an ISDN line. I’m unable to place calls to the conference bridge. What could be wrong?
Ensure you have the proper ISDN parameters in the '/opt/iic/conf/voiceconfig.xml' file:
<IsdnCountry>33</IsdnCountry> - 33 is France
<IsdnOperator>11</IsdnOperator> - 11 is EuroIsdn
<LineProtocol>isd0</LineProtocol>
(Check “isdncta –h” for other operator values)
I can connect to the bridge with my PC client when I’m inside the firewall. What ports do I need open in order to connect outside the firewall?
You will need to open ports 443, 80 and 4569.
I have my inbound sip calls to the conference bridge working correctly. How do I configure the bridge to make outbound sip calls?
You will need to set the following in the '/opt/iic/conf/voiceconfig.xml' file:
<SipOutboundProxy>sip:YourSipProxy</SipOutboundProxy>
