When checking the logs on one of my switches, I see many entries for for a number of interfaces in the format of:
Mon Jun 02 14:45:12 2014: <187>312: *hostname*: Jun 2 13:47:32.575: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to down
Mon Jun 02 14:54:51 2014: <187>313: *hostname*: Jun 2 13:57:11.536: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to up.
It is a 24 port switch and the errors occur on at least 10 ports, there are no user complaints, but I just want the errors to stop being generated. Any ideas how to do this?
I have changed a couple of ports around, done a shutdown/no shutdown on each of the interfaces and even reset the switch. My next step is to change the cables, but because of the number of ports involved, I'm not sure that will really do anything.
Most of the times it was noticed as the hardware/nvram issue and the fix was to replace the Switch.
However please try below steps if it works:
- Check the power supply to switch (As there could be a intermittent power issue)
- format nvram (take backup of configuration before formatting)
- apply the backup config and save it
- reload the switch couple of times and look for the error if the issue still persists
- if issue still persists then you can go for the replacement of the switch as these steps will specify this as an hardware/nvram issue.
Thanks, I think I can rule out a power issue as the interfaces do not all go down simultaneously. I'll look into your other points too.
Interface UPs and Downs may be caused by Layer1 issues too. Users may not report for drops as the downs are for very short time and the applications in use may sustain that drop.
I am looking to format the nvram this evening. Can you verify some things? What do you mean when you say "format nvram"? The options I get for format are:
[format command output]
flash1: Filesystem to be formatted
flash: Filesystem to be formatted
nvram is not listed. So I assume it cannot be formatted?
/all List all files
/recursive List files recursively
all-filesystems List files on all filesystems
bs: Directory or file name
cns: Directory or file name
flash1: Directory or file name
flash: Directory or file name
null: Directory or file name
nvram: Directory or file name
system: Directory or file name
tar: Directory or file name
tmpsys: Directory or file name
xmodem: Directory or file name
ymodem: Directory or file name
Looking at the above, I can format flash but not nvram. Are you saying to delete my startup-config from nvram and reload a couple times? If that does not work, the switch will need replacing?
There are also 5 files in nvram: Am I deleting them all (backing up beforehand, of course).
Sorry, I missed this. CRC errors and everything else is at 0 from what I can see I have around 8 ports generating errors today (No user complaints, just what appears to be in syslog file).
Below is an example:
#sh int gi1/0/15
GigabitEthernet1/0/15 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is xxxx (xxxx)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 449000 bits/sec, 45 packets/sec
2488655 packets input, 1248642231 bytes, 0 no buffer
Received 49783 broadcasts (11867 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 11867 multicast, 0 pause input
0 input packets with dribble condition detected
14588660 packets output, 8527492873 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
Check the inetrface configuration..Are all interfaces configured with appropriate access ports and trunk port commands, inorder to avoid auto negotiation?
Thanks for the comments. So I have changed all the cables, changed the ports and reloaded the switch at least 4 times now. It was clear all weekend (no users logged in), but early this morning (Monday), the logs started filling up again.
I have four files in my nvram: directory, but I cannot see how deleting them will resolve the problems I am experiencing. Can you tell me what result I expect to see as a result of erase nvram: ?
[Files in nvram:]
500 -rw- 8454 <no date> startup-config
501 ---- 1937 <no date> private-config
1 ---- 35 <no date> persistent-data
2 -rw- 0 <no date> ifIndex-table
3 -rw- 649 <no date> xxxxxxxxhost#xxxx.cer