Cisco Headend System Release 2.7 Installation Guide
Appendix B
Troubleshooting
86
4022447 Rev B
To view all ASI card log messages while ignoring the case, type grep -i
Hmux messages* and press Enter. A list similar to the following opens:
Hmux messages* and press Enter. A list similar to the following opens:
messages:Jan 6 09:45:44 rncsatm Hmux: [ID 625728 kern.notice] NOTICE:
Hmux0 info: BOARD TYPE IS DVP-2764, mux enabled
messages:Jan 6 09:45:44 rncsatm Hmux: [ID 218146 kern.notice] NOTICE:
messages:Jan 6 09:45:44 rncsatm Hmux: [ID 218146 kern.notice] NOTICE:
Hmux0: firmware 01.03.06
messages.1:Dec 22 08:09:16 rncsatm Hmux: [ID 625728 kern.notice] NOTICE:
messages.1:Dec 22 08:09:16 rncsatm Hmux: [ID 625728 kern.notice] NOTICE:
Hmux0 info: BOARD TYPE IS DVP-2764, mux enabled
messages.1:Dec 22 08:09:16 rncsatm Hmux: [ID 218146 kern.notice] NOTICE:
messages.1:Dec 22 08:09:16 rncsatm Hmux: [ID 218146 kern.notice] NOTICE:
Hmux0: firmware 01.03.06
messages.3:Dec 11 15:56:55 rncsatm Hmux: [ID 625728 kern.notice] NOTICE:
messages.3:Dec 11 15:56:55 rncsatm Hmux: [ID 625728 kern.notice] NOTICE:
Hmux0 info: BOARD TYPE IS DVP-2764, mux enabled
messages.3:Dec 11 15:56:55 rncsatm Hmux: [ID 218146 kern.notice] NOTICE:
messages.3:Dec 11 15:56:55 rncsatm Hmux: [ID 218146 kern.notice] NOTICE:
Hmux0: firmware 01.03.06
rncsatm:/var/adm>
rncsatm:/var/adm>
Notes:
If the ASI card is working correctly, the log file will be relatively small (few
log entries).
log entries).
For more information on the grep utility, type man grep and press Enter.
4 Scan the log messages for errors.
If you find the
ASI card in slot PCI1 (/dev/Hmux0) does not have the
correct permissions
error, you need to copy the configureASI.pl script from
the DNCS to the RNCS. See Copying the configureASI.pl Script to the RNCS
for more information.
for more information.
If you find other recurring errors, contact Cisco Services.
Verifying the ASI Card Owner and Permissions
If you receive an error message concerning the ASI card in your RNCS when you
attempt to start the RNCS services, you will need to verify the ASI card owner and
the card permissions.
attempt to start the RNCS services, you will need to verify the ASI card owner and
the card permissions.
Note: Solaris logs the ASI card error messages as part of the standard Solaris log. To
view the ASI log messages, see ASI Card Log Messages (on page 85).
1 Log into the RNCS as any user except root.
2 Open an xterm window.
3 Type /opt/solHmux64/vpStatus -d /dev/Hmux0 -P 0 and press Enter. The screen
view the ASI log messages, see ASI Card Log Messages (on page 85).
1 Log into the RNCS as any user except root.
2 Open an xterm window.
3 Type /opt/solHmux64/vpStatus -d /dev/Hmux0 -P 0 and press Enter. The screen
displays the ASI card status information similar to the following:
STATUS: /dev/Hmux0
PORT: 0
MAX BANDWIDTH: 38800000
REMAINING BANDWIDTH: 18300000
TRANSPORT ID: 2
PSI INTERVAL: 80
OPTION SETTINGS:
188 byte packets