Troubleshooting for the Network Management Card

Troubleshooting for NMC Access

Problem	Solution
Unable to ping the NMC	If the NMC’s status LED is green and the link LED is flashing, try to ping another node on the same network segment as the NMC. If that does not work, try the following: Verify if the TCP/IP setting configuration of the NMC is set manually or obtained through DHCP or BOOTP. Verify the number of the subnet bits set for the NMC’s subnet mask. Check any VLAN, firewall, or proxy configurations. Check the NMC status and system info through the local serial interface. If the NMC’s status LED is not solid green and/or the link LED is not flashing, perform the following checks: Verify that the NMC is properly connected in the system. Check that the Ethernet cable is connected securely to your network and the NMC. If there is an issue with the Ethernet cable, try a second cable. Verify that the network device (switch) port the NMC is connected to is not disabled, or that the port speed is set incorrectly. Check that your network DHCP or BOOTP server is active.
Cannot allocate the communications port through a terminal program	Before you can use a terminal program to configure the NMC, you must shut down any application, service, or program using the communications port.
Cannot access the command line interface through a serial connection	Verify that the NMC LEDs are illuminated and the NMC is powered on. Make sure that you did not change the baud rate. Try 2400, 9600, 19200, or 38400. Check your PC’s COM port configuration. Make sure the port is not already in use. Verify that the serial cable is firmly attached to the NMC and PC. Verify that the cable part number being used is compatible. Verify that Scroll Lock is not disabled on your keyboard.
Cannot access the command line interface remotely	Make sure you are using the correct access method, Telnet or Secure SHell (SSH). An Administrator can enable these access methods. By default, Telnet is disabled. For SSH, the NMC may be creating a host key. The NMC can take up to one 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 and configured correctly. Make sure you are specifying the correct URL, 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 supported web browser. If the NMC has just restarted and SSL security is being set up, the NMC may be generating a server certificate. The NMC can take up to one minute to create this certificate, and the SSL server is not available during that time.
Cannot access the NMC from EcoStruxture or another asset software	Make sure that EcoStruxture (or asset software) is correctly configured for the NMC. Check that the About > Charger page displays the correct information for the system.

Troubleshooting for NMC SNMP

Problem	Solution
Unable to perform a GET	Check the user profile configuration (SNMPv3) or the read (GET) community name (SNMPv1). Use the CLI or the web interface to make sure that the NMS has access.
Unable to perform a SET	Check the user profile configuration (SNMPv3) or the read/write (SET) community name (SNMPv1). Use the command line interface or UI to ensure that the NMS is granted access to the target IP address through the access control list (SNMPv3) or has write (SET) access (SNMPv1).
Unable to receive traps at the NMS	Make sure the trap type (SNMPv3 or SNMPv1) is correctly configured for the NMS as a trap receiver. For SNMPv3, check the user profile configuration for the NMS, and run a trap test. For SNMP v1, query the mconfigTrapReceiverTable MIB OID to verify that the NMS IP address is listed correctly, and that the community name defined for the NMS matches the community name in the table. If either is not correct, use SETs to the mconfigTrapReceiverTable OIDs, or use the CLI or web interface to correct the trap receiver definition.
Traps received at an NMS are not identified	See your NMS documentation to verify that the traps are properly integrated in the alarm/trap database.