"enhanced interrogation techniques"
Thought waterboarding colleagues was a bad thing?
Cheers,
E
Sent from my iPhone
On Feb 20, 2010, at 1:04 PM, Jim Tarvid <[email protected]> wrote:
Using enhanced interrogation techniques, my partner has admitted
manually causing these symptoms (except the cable cut) and not
sending an email.
On Fri, Feb 19, 2010 at 8:35 AM, Jim Tarvid <[email protected]> wrote:
r...@helen:~# uname -a
Linux helen 2.6.28-17-generic #58-Ubuntu SMP Tue Dec 1 21:27:25 UTC
2009 x86_64 GNU/Linux
This box has two Ethernet interfaces. The onboard nic - eth0 -
connects to a Ciena 3290 and the Internet.
A cable cut in our upstream infrastructure yesterday resulted in
eth0 and eth2 going down, eth0 coming up but eth2 remaining down
until a reboot.
Feb 18 10:26:27 helen kernel: [3251918.453137] r8169: eth0: link down
Feb 18 10:26:30 helen kernel: [3251921.244552] r8169: eth0: link up
Feb 18 10:26:31 helen kernel: [3251922.156904] eth2: link down
Feb 18 21:50:17 helen syslogd 1.5.0#5ubuntu3: restart.
Feb 18 21:50:18 helen kernel: Inspecting /boot/System.map-2.6.28-17-
generic
The upstream provider says the Ciena 3290 did not get a mac address
from eth0 (ARP failure?)
On reboot dmesg says eth2 above is now eth1.
r...@helen:~# dmesg | grep eth
[ 1.329422] Driver 'sd' needs updating - please use bus_type
methods
[ 1.329430] Driver 'sr' needs updating - please use bus_type
methods
[ 4.289752] eth0: RTL8168c/8111c at 0xffffc200100cc000,
00:25:11:30:71:64, XID 3c4000c0 IRQ 2301
[ 4.309690] eth1: RealTek RTL8139 at 0xe800, 00:0e:2e:55:a1:ed,
IRQ 22
[ 4.309692] eth1: Identified 8139 chip type 'RTL-8100B/8139D'
[ 9.186289] udev: renamed network interface eth1 to eth2
[ 12.338871] r8169: eth0: link up
[ 12.338876] r8169: eth0: link up
[ 12.340735] eth2: link up, 100Mbps, full-duplex, lpa 0x43E1
but ifconfig and route report the usual devices
eth0 Link encap:Ethernet HWaddr 00:25:11:30:71:64
inet addr:208.94.92.222 Bcast:208.94.92.223 Mask:255.255.255.252
inet6 addr: fe80::225:11ff:fe30:7164/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1174879 errors:0 dropped:0 overruns:0 frame:0
TX packets:1230138 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:103241356 (103.2 MB) TX bytes:376658406 (376.6 MB)
Interrupt:253 Base address:0xc000
eth0:0 Link encap:Ethernet HWaddr 00:25:11:30:71:64
inet addr:208.94.89.129 Bcast:208.94.89.191 Mask:255.255.255.192
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:253 Base address:0xc000
eth0:1 Link encap:Ethernet HWaddr 00:25:11:30:71:64
inet addr:208.94.89.130 Bcast:208.94.89.191 Mask:255.255.255.192
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:253 Base address:0xc000
eth2 Link encap:Ethernet HWaddr 00:0e:2e:55:a1:ed
inet addr:172.17.100.5 Bcast:172.17.100.7 Mask:255.255.255.252
inet6 addr: fe80::20e:2eff:fe55:a1ed/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2703 errors:0 dropped:0 overruns:0 frame:0
TX packets:9097 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:393990 (393.9 KB) TX bytes:3868877 (3.8 MB)
Interrupt:22 Base address:0xe800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:17791 errors:0 dropped:0 overruns:0 frame:0
TX packets:17791 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1763424 (1.7 MB) TX bytes:1763424 (1.7 MB)
r...@helen:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
172.17.100.4 * 255.255.255.252 U 0
0 0 eth2
208.94.92.220 * 255.255.255.252 U 0
0 0 eth0
208.94.89.192 172.17.100.6 255.255.255.192 UG 0
0 0 eth2
10.4.0.0 172.17.100.6 255.255.255.0 UG 0
0 0 eth2
10.5.0.0 172.17.100.6 255.255.255.0 UG 0
0 0 eth2
default 208.94.92.221 0.0.0.0 UG 100
0 0 eth0
r...@helen:/etc/network# cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
#auto eth0
#iface eth0 inet dhcp
# Alias for Internet access via primary interface
# Added to /etc/network/interfaces in preparation of cutover
# Uncomment the next seven lines
auto eth0
iface eth0 inet static
address 208.94.92.222
netmask 255.255.255.252
broadcast 208.94.92.223
network 208.94.92.220
gateway 208.94.92.221
auto eth0:0
iface eth0:0 inet static
address 208.94.89.129
netmask 255.255.255.192
broadcast 208.94.89.191
network 208.94.89.128
auto eth0:1
iface eth0:1 inet static
address 208.94.89.130
netmask 255.255.255.192
broadcast 208.94.89.191
network 208.94.89.128
auto eth2
iface eth2 inet static
address 172.17.100.5
netmask 255.255.255.252
up ip route add 208.94.89.192/26 via 172.17.100.6
up ip route add 10.4.0.0/24 via 172.17.100.6
up ip route add 10.5.0.0/24 via 172.17.100.6
Several questions:
1) would an upgrade to 9.10 help?
2) is there a simple watchdog that would test upstream connectivity
periodically and bounce the interface is there is none
3) same for downstream?
4) can the link down for eth2 be prevented?
5) is there a way to refresh detection of eth2?
Seems like Hotel California. I am stuck in Networking 101.
TIA
Jim
--
Rev. Jim Tarvid, PCA
http://ls.net
http://drupal.ls.net
http://crossleft.org
--
Rev. Jim Tarvid, PCA
http://ls.net
http://drupal.ls.net
http://crossleft.org
--
ubuntu-server mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
--
ubuntu-server mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
