Re: Help debugging director problems after a period of time

[nick garratt <nick-lvs@xxxxxxxxxxxxxx>]

hi

your problem is is that your alias eth2:0 has a 255.255.255.255 mask 
whereas it should have the same mask as eth2, being on the same 
subnet. eth2:0 will be brought up after eth2 and this is probably 
messing up routing on interface eth2 to the directly connected net.
nick

> eth2      Link encap:Ethernet  HWaddr 00:01:02:E8:65:FF
>           inet addr:66.208.187.25  Bcast:66.208.187.127
> Mask:255.255.255.128
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:727 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:547 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:70986 (69.3 Kb)  TX bytes:218884 (213.7 Kb)
>           Interrupt:9 Base address:0x1400
>
> eth2:0    Link encap:Ethernet  HWaddr 00:01:02:E8:65:FF 
>           inet addr:66.208.187.27  Bcast:66.208.187.27  Mask:255.255.255.255
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:727 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:547 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:70986 (69.3 Kb)  TX bytes:218884 (213.7 Kb)
>           Interrupt:9 Base address:0x1400