Sun SPARC[TM] Enterprise M4000/M5000 Network: It Takes a Few Minutes for XSCF LAN Port to Respond Ping Request

Asset ID:	1-72-1553624.1
Update Date:	2017-11-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1553624.1 : Sun SPARC[TM] Enterprise M4000/M5000 Network: It Takes a Few Minutes for XSCF LAN Port to Respond Ping Request

Applies to:

Sun SPARC Enterprise M4000 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise M5000 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

On an M4000 server, it takes a few minutes for xscf lan port to respond access request. For example, ping request will be timeout within first 3 minutes. After about 3 minutes, the ping request can be answered by xscf Lan port in a timely manner. And all other network request will be fine, for example, SSH, HTTP, etc.

Cause

In a M4000 server, two Lan ports on xscf are configured as follows:

XSCF> shownetwork -a
xscf#0-lan#0
          Link encap:Ethernet HWaddr 00:0B:5D:E2:01:5C
          inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:12460249 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13222 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:825924036 (787.6 MiB) TX bytes:1701525 (1.6 MiB)
          Base address:0xe000

xscf#0-lan#1
          Link encap:Ethernet HWaddr 00:0B:5D:E2:01:5D
          inet addr:172.31.1.1 Bcast:172.31.1.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Base address:0xc000

The routing table is as below:

XSCF> showroute -a
Destination     Gateway         Netmask         Flags Interface
192.168.1.0    *               255.255.255.0   U     xscf#0-lan#0
172.31.1.0     *               255.255.255.0   U     xscf#0-lan#0
default         172.31.1.254   0.0,.0.0        UG    xscf#0-lan#1
default         192.168.1.254 0.0.0.0         UG    xscf#0-lan#0

There is no cable connected to port lan#1. When a ping request reached at lan#0, it takes time for xscf to try first default gateway on lan#1 until it times out. Thereafter, default gateway on lan#0 will be used and everything will be fine since then.

Solution

Either connect a cable to lan#1 or remove the default gateway on lan#1.

Attachments

This solution has no attachment