We have a catalyst 2924XL-EN which seems to have started rebooting almost randomly. I can't be sure it's rebooting but the switch uptime is definitely reset, which leads me to this conclusion.
When the switch boots back up it looks for a DHCP lease, even though it's assigned a static address. It's given a lease but doesn't seem to use it - the IP assigned to it does not respond. It does however respond normally on the static address assigned to it, which makes me wonder why on earth it's looking for a DHCP lease when it reboots.
The reboots are seemingly random, occuring in gaps of up to one week or just a few hours. Machines connected to the switch show the following:
May 25 03:53:49 xxxxxx kernel: eth0: link down
May 25 03:53:51 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 03:53:57 xxxxxx kernel: eth0: link down
May 25 03:53:58 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 03:54:18 xxxxxx kernel: eth0: link down
May 25 03:54:19 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 03:54:35 xxxxxx kernel: eth0: link down
May 25 03:54:41 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 12:33:46 xxxxxx kernel: eth0: link down
May 25 12:34:35 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 12:34:40 xxxxxx kernel: eth0: link down
May 25 12:34:42 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 12:35:01 xxxxxx kernel: eth0: link down
May 25 12:35:03 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 12:35:19 xxxxxx kernel: eth0: link down
May 25 12:35:24 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
This is fairly typical in that the interface goes up and down quite a few times in the space of a few minutes. Everything then returns to normal.
Switch info:
IOS (tm) C2900XL Software (C2900XL-C3H2S-M), Version 12.0(5)WC8, RELEASE SOFTWARE (fc1)
I'm completely at a loss as to why this is happening. I've got informational level logging via syslog to another machine and this shows nothing at all - am I using the wrong logging level?
All suggestions welcome, I'm on the verge of replacing the unit but I'd really love to know if this is something fixable before I do so.
Cheers.
When the switch boots back up it looks for a DHCP lease, even though it's assigned a static address. It's given a lease but doesn't seem to use it - the IP assigned to it does not respond. It does however respond normally on the static address assigned to it, which makes me wonder why on earth it's looking for a DHCP lease when it reboots.
The reboots are seemingly random, occuring in gaps of up to one week or just a few hours. Machines connected to the switch show the following:
May 25 03:53:49 xxxxxx kernel: eth0: link down
May 25 03:53:51 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 03:53:57 xxxxxx kernel: eth0: link down
May 25 03:53:58 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 03:54:18 xxxxxx kernel: eth0: link down
May 25 03:54:19 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 03:54:35 xxxxxx kernel: eth0: link down
May 25 03:54:41 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 12:33:46 xxxxxx kernel: eth0: link down
May 25 12:34:35 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 12:34:40 xxxxxx kernel: eth0: link down
May 25 12:34:42 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 12:35:01 xxxxxx kernel: eth0: link down
May 25 12:35:03 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
May 25 12:35:19 xxxxxx kernel: eth0: link down
May 25 12:35:24 xxxxxx kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
This is fairly typical in that the interface goes up and down quite a few times in the space of a few minutes. Everything then returns to normal.
Switch info:
IOS (tm) C2900XL Software (C2900XL-C3H2S-M), Version 12.0(5)WC8, RELEASE SOFTWARE (fc1)
I'm completely at a loss as to why this is happening. I've got informational level logging via syslog to another machine and this shows nothing at all - am I using the wrong logging level?
All suggestions welcome, I'm on the verge of replacing the unit but I'd really love to know if this is something fixable before I do so.
Cheers.