asked on

Solaris 8 routing not working

Came to customer site for some upgrade work on my app. I rebooted the server and they told me they lost their routing. Turns out they had never made their static routes permanent. So they added them back and I told them to edit the inetinit file so they will be persistent routes.

All worked fine for 2 days. This morning I rebooted the server, saw the routes being added.

But I cannot connect to anything.

There are 3 interfaces on this box.

bge0 172.20.1.28 ff ff ff 00
bge1 64.89.94.41 ff ff ff f0
bge2 63.167.200.115 ff 00 00 00

I get an ALIVE when I ping 64.89.96.32, but a traceroute shows that he tries to use bge1, but just stars out.

And if I try to ping 172.20.1.1 it tells me that 63.167.200.115 cannot reach 172.20.1.1

There is no /etc/notrouter file

And all this worked 2 days ago, and we did nothing but add some route comand in inetinit

What is the issue?

pseudocyber

I'm NOT a unix guru, but I work with them and help them with network issues from time to time ... what about your gateway?

If you could post your interface results ... I forget the command. The equivalent of a DOS ipconfig /all.

Also your routing table.

roone

ASKER

Wait.

Looking at the rear of the machine, there are 2 green lights above each port.

Yet only bge1 has both on (left flickers, and right is steady)

bge0 and bge2 only have the left flickering. Right is off.

pseudocyber

If those are GigE interfaces, I know the GigE's we have are a bit finniky - ours need to be Autonegotiate in order to operate at 1000. They don't like being manually set.

roone

ASKER

yeah, the left is the link light, and the right being off just means its not at max speed, so dead end that is.

I can't post since all there is is console access at this point

This is the table from yesterday, and it looks the same today

Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
216.68.79.243 64.89.96.33 UGH 1 3
205.242.95.64 64.89.96.33 UGH 1 0
205.242.95.160 64.89.96.33 UGH 1 0
10.10.0.97 172.20.1.1 UGH 1 74
142.146.253.0 64.89.96.33 UGH 1 0
12.25.119.0 64.89.96.33 UGH 1 0
12.25.118.0 64.89.96.33 UGH 1 0
209.103.202.57 64.89.96.33 UGH 1 0
64.178.236.24 64.89.96.33 UGH 1 0
12.25.118.5 64.89.96.33 UGH 1 4
209.103.202.58 64.89.96.33 UGH 1 0
216.155.160.197 64.89.96.33 UGH 1 25
64.178.236.25 64.89.96.33 UGH 1 0
216.68.79.244 64.89.96.33 UGH 1 0
216.155.160.196 64.89.96.33 UGH 1 46
142.146.244.0 64.89.96.33 UGH 1 0
206.228.128.2 64.89.96.33 UGH 1 0
12.25.118.10 64.89.96.33 UGH 1 4
216.155.160.106 64.89.96.33 UGH 1 42
12.174.3.11 64.89.96.33 UGH 1 0
216.155.160.105 64.89.96.33 UGH 1 47
142.146.247.0 64.89.96.33 UGH 1 0
208.254.124.25 64.89.96.33 UGH 1 0
209.59.65.128 64.89.96.33 UGH 1 0
12.174.3.12 64.89.96.33 UGH 1 0
168.103.195.1 64.89.96.33 UGH 1 0
209.59.65.164 64.89.96.33 UGH 1 0
12.174.3.17 64.89.96.33 UGH 1 0
209.183.42.252 64.89.96.33 UGH 1 0
205.242.95.16 64.89.96.33 UGH 1 0
209.183.42.253 64.89.96.33 UGH 1 0
208.254.124.32 64.89.96.33 UGH 1 0
12.174.3.18 64.89.96.33 UGH 1 0
208.254.125.32 64.89.96.33 UGH 1 0
209.59.65.152 64.89.96.33 UGH 1 0
208.163.54.241 64.89.96.33 UGH 1 0
209.183.46.252 64.89.96.33 UGH 1 0
209.183.42.248 64.89.96.33 UGH 1 69
168.103.195.24 64.89.96.33 UGH 1 0
208.163.54.240 64.89.96.33 UGH 1 0
209.183.46.253 64.89.96.33 UGH 1 0
64.89.96.32 64.89.96.41 UGH 1 0
172.20.1.0 172.20.1.28 UGH 1 0
64.89.96.3 172.20.1.1 UGH 1 67
209.59.65.144 64.89.96.33 UGH 1 0
209.59.65.176 64.89.96.33 UGH 1 0
216.15.160.105 64.89.96.33 UGH 1 0
64.89.96.32 64.89.96.41 U 1 49 bge1
192.168.0.0 172.20.1.1 UG 1 0
209.153.204.0 64.89.96.33 UG 1 0
10.0.0.0 172.20.1.1 UG 1 45
205.205.50.0 64.89.96.33 UG 1 0
209.167.5.0 64.89.96.33 UG 1 0
172.20.1.0 172.20.1.28 U 1 120 bge0
172.15.0.0 172.20.1.1 UG 1 0
192.168.0.0 172.20.1.1 UG 1 0
224.0.0.0 172.20.1.28 UG 1 0
10.0.0.0 172.20.1.1 UG 1 8
63.0.0.0 63.167.200.115 U 1 46 bge2
63.0.0.0 63.167.200.115 UG 1 0
224.0.0.0 172.20.1.28 U 1 0 bge0
default 63.167.200.113 UG 1 614
127.0.0.1 127.0.0.1 UH 28 229657 lo0

roone

ASKER

all interfaces say they are up.

my first question is, why when I do a ping for 172.20.1.1 it tells me that bge2 can't reach it.

Isn't it supposed to route to connected networks by itself? So bge0 should be trying the ping

roone

ASKER

in the table I have given, I can do a good trace route to any address where 64.89.96.33 is the gateway

roone

ASKER

63.167.200.115 can talk to 63.167.200.113 or 114

That is just crazy

roone

ASKER

ifconfig reported this:

bge0 172.20.1.28 ff ff ff 00
bge1 64.89.94.41 ff ff ff f0
bge2 63.167.200.115 ff 00 00 00

but /etc/netmasks has:

172.20.1.0 255.255.255.0
64.89.96.32 255.255.255.240
63.167.200.115 255.255.255.248

We used ifconfig to change the nemask of bge2 to ff ff ff f8

And now we can get to 63.167.200.113 and 114

But 172 still no good

roone

ASKER

using snoop, seems udp is working but not tcp

roone

ASKER

It was somehow due to routes added via inetinit file. Either we added duplicate routes or added host using a -net option.

But removing those, all works now.

ASKER CERTIFIED SOLUTION

pseudocyber

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial