Dear ALL,
my server give me messages like below:
Apr 20 21:33:09 TAISERVER in.routed[175]: [ID 238047
daemon.warning] interface bge3 to 192.168.11.22 turned off
I check with ifconfig,but nothing error that,how can make it solve...thanks for your help.
post the output of:
# ifconfig -a
# cat /etc/hostname.*
# netstat -rn
please change sensitive information (names, ips and so on...) to xxx!
is bge3 going to a switch or router?
#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 172.16.250.12 netmask ffff0000 broadcast 172.16.255.255
groupname prod_ge0+ce1
bge0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
inet 172.16.250.14 netmask ffff0000 broadcast 172.16.255.255
bge0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.10.253 netmask ffffff00 broadcast 192.168.10.255
bge0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.16.250.10 netmask ffff0000 broadcast 172.16.255.255
bge1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.41.224.102 netmask ff000000 broadcast 10.255.255.255
bge1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.41.224.100 netmask ff000000 broadcast 10.255.255.255
bge3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 192.168.11.22 netmask ffffff00 broadcast 192.168.11.255
ce1: flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 1500 index 5
inet 172.16.250.17 netmask ffff0000 broadcast 172.16.255.255
groupname prod_ge0+ce1
cip0: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 6
inet 193.169.1.2 netmask ffffff00 broadcast 193.169.1.255
ether 0:14:4f:5e:70:b4
#cat /etc/hostname.*
prd-taiserver netmask + broadcast + group prod_ge0+ce1 up
addif prd-taiserver12A netmask + broadcast + deprecated -failover up
taiserver
upstaiserver
prd-taiserver12B netmask + broadcast + group prod_ge0+ce1 deprecated -failover standby up
#netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
192.168.10.0 192.168.10.253 U 1 0 bge0:2
192.168.11.0 192.168.11.22 U 1 81 bge3
193.169.1.0 193.169.1.2 U 1 14315 cip0
172.16.0.0 172.16.250.12 U 1 105230 bge0
172.16.0.0 172.16.250.10 U 1 0 bge0:3
172.16.0.0 172.16.250.12 U 1 0 bge0:1
172.16.0.0 172.16.250.12 U 1 12106 ce1
10.0.0.0 10.41.224.102 U 1 165003 bge1
10.0.0.0 10.41.224.100 U 1 0 bge1:1
224.0.0.0 10.41.224.102 U 1 0 bge1
127.0.0.1 127.0.0.1 UH 7756854010 lo0
there is only ONE hostname.* file? the output of ifconfig looks ok. so maybe pupp is right and it's a problem with the switch or cable...
what do you get if you force a ping out bge3 to the default gwy? can you ping that gwy?
like these :
lsav@taiserver> rsh 192.168.11.22
lsav@taiserver> ping -s 192.168.11.0
PING 192.168.11.0: 56 data bytes
64 bytes from upstaiserver12 (192.168.11.22): icmp_seq=0. time=0.226 ms
64 bytes from upstaiserver12 (192.168.11.22): icmp_seq=1. time=0.232 ms
64 bytes from upstaiserver12 (192.168.11.22): icmp_seq=2. time=0.158 ms
^C
----192.168.11.0 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max/stddev = 0.158/0.205/0.232/0.041
lsav@taiserver> ping -s 192.168.11.22
PING 192.168.11.22: 56 data bytes
64 bytes from upstaiserver12 (192.168.11.22): icmp_seq=0. time=0.201 ms
64 bytes from upstaiserver12 (192.168.11.22): icmp_seq=1. time=0.175 ms
64 bytes from upstaiserver12 (192.168.11.22): icmp_seq=2. time=0.180 ms
64 bytes from upstaiserver12 (192.168.11.22): icmp_seq=3. time=0.173 ms
64 bytes from upstaiserver12 (192.168.11.22): icmp_seq=4. time=0.187 ms
^C
----192.168.11.22 PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms) min/avg/max/stddev = 0.173/0.183/0.201/0.011
Restart the in.routed daemon
check if there's any collisions using netstat -i