Sun Netra T5440 Server
 
Sun SPARC Enterprise T5220 Server
 
Sun SPARC Enterprise T5140 Server
 
Sun SPARC Enterprise T5120 Server
 
Sun Netra T5220 Server
 
Sun SPARC Enterprise T5440 Server
 

PLA-Support>Sun Systems>SPARC>CMT>SN-SPARC: T5xx0
 

A Service Processor network management port failing to establish a connection to local network may look like a hardware failure but the reason could be a link speed negotiation failure between the Service Processor and the switch. The document provides a procedure to test Service Processor network management before assuming a hardware failure.

In this Document

Symptoms

Cause

Solution

References

Applies to:

Symptoms

No link could be established between the Service Processor network management port and the local network.
A different switch port and a different network cable had already been tested but the Link / Activity LEDs did not light up.

Cause

The root cause was a link speed negotiation failure between the Service Processor and the switch used to connect the Service Processor to local network.
The switch was a Gigabit Ethernet switch which did not decrease link speed to 10/100 Mbps as required for Service Processor network management port.

Solution

• Set up a test environment which consists of two 10/100 Mbps capable network stations. For example, connect a Laptop via crossover cable directly to the Service Processor.
  
  
• Establish a serial connection to the Service Processor to be able to work with ILOM command line (see Power On the System for the First Time in the documentation)
  
  
• Configure the Laptop's network interface into the same network address range the Service Processor network management port is configured
  
  To view the Service Processor network management port configuration, use the ILOM command show /SP/network
  
  
  Example output:
  
  /SP/network
      Properties:
          commitpending = (Cannot show property)
          dhcp_server_ip = none
          ipaddress = 192.168.0.20
          ipdiscovery = static
          ipgateway = 192.168.0.1
          ipnetmask = 255.255.255.0
          macaddress = 00:21:28:AB:CD:EF
          pendingipaddress = 192.168.0.20
          pendingipdiscovery = static
          pendingipgateway = 192.168.0.1
          pendingipnetmask = 255.255.255.0
          state = enabled
  
  

• In case the Service Processor network management port ipdiscovery is set to dhcp, you need to set up a static IP address, (see Configure the Service Processor Network Management Port)
  
  
  
• Once the Service Processor and Laptop are configured into the same network, check if a link has been established by
  
  - checking the link and activity LEDs on the Service Processor's network management port
  
  - sending a ping from Service Processor to the Laptop and vice versa
  - use the ILOM command set /SP/network/test ping=(IP-Address) to send a ping to the laptop
  
  - trying to connect to the Service Processor via ssh or using the Web Browser to connect to ILOM Web GUI
  
  
  
• If a link has not been established yet, reset the Service Processor to re-initialize the Service Processor network management port and check again
  
  - to reset the Service Processor on ILOM CLI, type the command reset /SP
  
  
  Upon a link speed negotiation failure the Service Processor network management port may not work again until the Service Processor has been reset.
  Not resetting the Service Processor in order to re-initialize the Service Processor network management port will lead to false test results.
  
  
  
• Another cause of link failures has been reported on the T5xx0 Service Processors when connected to Cisco Catalyst switches that have the Power over Ethernet (PoE) feature enabled,
  for example to provide power to Cisco IP phones - see Document 1611277.1 for solution
  
  
  
  

In case the test procedure has been followed and the link could not be established between the two 10/100 Mbps capable network stations, please open a Service
Request and provide a summary of the tests done.

This solution has no attachment