Solaris 10: cannot ping to/from server

routingsolaris

All,

I have a Solaris 10 server which is not reachable by IP (ie can't ping to/from the server). I believe I have the default route setup correctly. See below:

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.62.100 netmask ffffff00 broadcast 192.168.62.255
ether 0:14:4f:b1:9b:30

# netstat -rn
Routing Table: IPv4
Destination       Gateway           Flags        Ref        Use  Interface
-------------------- -------------------- ----- ----- ------ ---------
192.168.62.0      192.168.62.100     U           1          40   bge0
224.0.0.0         192.168.62.100     U           1           0   bge0
default           192.168.62.1       UG          1           0
127.0.0.1         127.0.0.1          UH          1           4   lo0
#

# cat /etc/defaultrouter
192.168.62.1

I have verified layer1 and layer 2 are up on the switchport, and that it's on the correct VLAN. I have also checked the default gateawy (192.168.62.1) is in fact reachable since I can ping it from my PC:

Pinging 192.168.62.1 with 32 bytes of data:

Reply from 192.168.62.1: bytes=32 time=1ms TTL=254
Reply from 192.168.62.1: bytes=32 time=1ms TTL=254
Reply from 192.168.62.1: bytes=32 time=3ms TTL=254
Reply from 192.168.62.1: bytes=32 time=6ms TTL=254

I'm at a loss as to what is wrong. I would highly appreciated your assistance.

Thank you very much.

UPDATE1:

Don't see ARP entry for default gateway:

# arp -a
Net to Media Table: IPv4
Device   IP Address               Mask      Flags   Phys Addr
------ -------------------- --------------- ----- ---------------
bge0   192.168.77.1         255.255.255.255       00:17:59:01:55:50
bge0   pgw1                 255.255.255.255 SP    00:14:4f:b1:9b:30
bge0   192.168.62.53        255.255.255.255       00:1b:53:36:f5:30
bge0   224.0.0.0            240.0.0.0       SM    01:00:5e:00:00:00

UPDATE2:

I added a static arp entry for the default gateway but this did not help. Please suggest the next step.

UPDATE3:

I moved the server to a different switchport and that resolved the problem. Thanks guys for your helpful suggestions. Peace.

Best Answer

I have checked an S10 system I have to hand and it looks exactly like yours. Can you try connecting something else to the same switch port and cable to verify them? Is there a second NIC on the system ?

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.1.68 netmask ffffff00 broadcast 192.168.1.255
        ether 0:c:29:25:22:f8

# netstat -rn

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              192.168.1.254        UG        1          8
192.168.1.0          192.168.1.68         U         1          3 e1000g0
224.0.0.0            192.168.1.68         U         1          0 e1000g0
127.0.0.1            127.0.0.1            UH        4        127 lo0

Related Solutions

Solaris Network troubleshooting

I've never tried putting IPs into hostname.XX; typically the file has a hostname, and /etc/hosts maps the host name to the IP for that interface. Swap the hostnames listed in the per-interface files and reboot, and presto, swapped interfaces. (Or swap in /etc/hosts, but that could break more things.)

Centos 6.2 Fresh ‘Basic Server’ install networking issues

Your routes and configuration look fine.

$: route -n
Destination // Gateway // Genmask // Flags // Metric // Ref // Use // Iface
66.*.*.0       0.0.0.0    255.255.255.248   U   1003      0   0     0  em2
0.0.0.0        66.*.*.1   0.0.0.0           UG     0      0   0     0  em2

The first route, 66.*.*.0/29 with gateway 0.0.0.0 tells your computer to use interface em2 and then make an arp request to find the hardware address of the host you're trying to reach. This is a "connected" route.

The second one is the default route, pointing at your default gateway through em2. If you need to send a packet in another network than 66.*.*.0/29, your computer will make an arp request to find 66.*.*.1 and then send the packets to it.

The only thing in your configuration that could be an issue is the NM_CONTROLLED=yes statement in /etc/sysconfig/network-scripts/ifcfg-em2. This tells the system that this interface is controlled by NetworkManager. This could interfere with your static configuration.

However, even without any default gateway you should be able to ping and ssh from the 66.*.*.0/29 subnet to your machine.

Check layer 1 first, and ensure that the cable is plugged on each side. Use leds on nic and switch, and check if the system sees it correctly:

# mii-tool
eth0: negotiated 1000baseT-FD flow-control, link ok

Then verify if any iptables are dropping the packets. Use iptables -L or iptables-save to check for any rules, and iptables -D <rule> to delete them. Pay attention to the default policy.

Also, on some systems, NetworkManager can configure ufw automatically, and I've had issues with static interface configuration that wasn't seen by NM and hence blocked by ufw.

Best Answer

Related Solutions

Solaris Network troubleshooting

Centos 6.2 Fresh ‘Basic Server’ install networking issues

Related Topic