LOCK-BOLT 9M1367 - Caterpillar

Network Management Card Access Problems
ReferenceFor problems that are not described here, see the troubleshooting flowcharts .Unable to Ping the NMC
If the NMCs Status LED is green, try to ping another node on the same network segment as the NMC. If that fails, the NMC is not the problem. If the Status LED is not green, or if the ping test succeeds, perform the following checks:
Verify that the NMC is properly seated in the UPS.
Verify all network connections.
Verify the IP addresses of the NMC and the NMS.
If the NMS is on a different physical network, or subnetwork, from the NMC, verify the IP address of the default gateway, or router.
Verify the number of subnet bits for the NMCs subnet mask.Cannot Allocate the Communications Port Through a Terminal Program
Before you can use a terminal program to configure the NMC, shut down any application, service, or program using the communications port.Cannot Access the Command Line Interface Through a Serial Connection
Make sure that you did not change the baud rate. Try 2400, 9600, 19200, or 38400.Cannot Access the Command Line Interface Remotely
Make sure that you are using the correct access method, Telnet, or Secure SHell (SSH). An Administrator can enable these access methods. By default, Telnet is enabled. Enabling SSH automatically disables Telnet.
For SSH, the NMC may be creating a host key. The NMC can take up to 1 minute to create the host key, and SSH is inaccessible for that time.Cannot Access the "Web Interface"
Verify that HTTP or HTTPS access is enabled.
Make sure that you are specifying the correct URL - one that is consistent with the security system used by the NMC. SSL requires "https", not "http", at the beginning of the URL.
Verify that you can ping the NMC.
Verify that you are using a web browser supported for the NMC.ReferenceRefer to the "Supported Web browsers" section in the, ""Web Interface"" chapter of this manual.
If the NMC has restarted and SSL security is being set up, the NMC may be generating a server certificate. The NMC can take up to 1 minute to create this certificate, and the SSL server is not available during that time.SNMP Issues
Unable to perform a GET
Verify the read (GET) community name (SNMPv1) or the user profile configuration (SNMPv3).
Use the "command line interface" or "Web interface" to ensure that the NMS has access.ReferenceRefer to the "SNMP" section in the, "Administration : Network Features" chapter of this manual.Unable to perform a SET
Verify the read/write (SET) community name (SNMPv1) or the user profile configuration (SNMPv3).
Use the "command line interface" or "Web interface" to ensure that the NMS has the write(SET) access (SNMPv1) or is granted access to the target IP address through the access control list (SNMPv3).ReferenceRefer to the "SNMP" section in the, "Administration : Network Features" chapter of this manual.Unable to receive traps at the NMS
Make sure the trap type (SNMPv1 or SNMPv3) is correctly configured for the NMS as a trap receiver.
For SNMP v1, query the "mconfigTrapReceiverTable" MIB OID to verify that the NMS IP address is