I would check the ram logs for any link up/down notifications. With spanning tree off (or using fastlink) you are just overriding the port going from blocking->listening->learning->forwarding, the port just starts forwarding when a link is up. This can be a band-aid fix with minor port flapping, but your case sounds like longer link drops.
If the ram logs don't show any unusual link up/down notifications, you could also check the port counters and rmon stats for errors. Compare the amount of errors to the amount of traffic, anything around 1-2% you will probably not notice.
If everything looks clean, no port flapping, no errors, you may have a traffic problem and not a physical issue. You could do some pings to check latency, and also capture traffic to get an idea of what is going on.
OK, good. Now you have to find out if those ports where meant to go up/down.
Notice how the port is only down for about 2 seconds. This could be someone rebooting their computer.
If you Know the client on that port never rebooted, then you have a case of port flapping. Port flapping is usually a physical layer issue. One possible workaround is to try hard setting the switchport and the clients NIC to say 100 full.
OK - I'm finding out that people are rebooting alot because the network is being so flaky - slowness - hesitation.... So where do I look next?
I do have someone coming in with a network sniffer on Thursday - we're going to start really checking connections.... but is there some specific errors I could look for on the ports to see if I have a bad card or connection somewhere?
Well did alot more research today - the people that are having the problems are in the 3348 switch - I moved 3 of them today (to the 3248) and they all breathed a huge sigh of relief - but now what to do with the rest? I don't have enough room on the 3248 for everyone -
GregM_1
1 Rookie
•
112 Posts
0
December 27th, 2004 15:00
I would check the ram logs for any link up/down notifications. With spanning tree off (or using fastlink) you are just overriding the port going from blocking->listening->learning->forwarding, the port just starts forwarding when a link is up. This can be a band-aid fix with minor port flapping, but your case sounds like longer link drops.
If the ram logs don't show any unusual link up/down notifications, you could also check the port counters and rmon stats for errors. Compare the amount of errors to the amount of traffic, anything around 1-2% you will probably not notice.
If everything looks clean, no port flapping, no errors, you may have a traffic problem and not a physical issue. You could do some pings to check latency, and also capture traffic to get an idea of what is going on.
empmelanie
10 Posts
0
December 27th, 2004 17:00
I do have entries in my Ram logs - what do they mean? And what can I do about them? This is what I'm seeing:
1 2147483554 27-Dec-2004 10:35:14 Informational %LINK-I-Up: 1/e4
2 2147483555 27-Dec-2004 10:35:14 Warning %STP-W-PORTSTATUS: 1/e4: STP status Forwarding
3 2147483556 27-Dec-2004 10:35:12 Warning %LINK-W-Down: 1/e4
4 2147483557 27-Dec-2004 09:32:30 Informational %LINK-I-Up: 1/e44
5 2147483558 27-Dec-2004 09:32:30 Warning %STP-W-PORTSTATUS: 1/e44: STP status Forwarding
6 2147483559 27-Dec-2004 09:32:30 Informational %LINK-I-Up: 1/e41
7 2147483560 27-Dec-2004 09:32:30 Warning %STP-W-PORTSTATUS: 1/e41: STP status Forwarding
8 2147483561 27-Dec-2004 09:32:27 Warning %LINK-W-Down: 1/e44
9 2147483562 27-Dec-2004 09:32:27 Warning %LINK-W-Down: 1/e41
10 2147483563 27-Dec-2004 09:24:03 Informational %LINK-I-Up: 1/e28
11 2147483564 27-Dec-2004 09:24:03 Warning %STP-W-PORTSTATUS: 1/e28: STP status Forwarding
12 2147483565 27-Dec-2004 09:24:01 Warning %LINK-W-Down: 1/e28
13 2147483566 27-Dec-2004 08:12:33 Informational %LINK-I-Up: 1/e3
14 2147483567 27-Dec-2004 08:12:33 Warning %STP-W-PORTSTATUS: 1/e3: STP status Forwarding
15 2147483568 27-Dec-2004 08:12:31 Warning %LINK-W-Down: 1/e3
16 2147483569 27-Dec-2004 08:05:01 Informational %LINK-I-Up: 1/e47
17 2147483570 27-Dec-2004 08:05:01 Warning %STP-W-PORTSTATUS: 1/e47: STP status Forwarding
18 2147483571 27-Dec-2004 08:05:00 Warning %LINK-W-Down: 1/e47
19 2147483572 27-Dec-2004 08:01:49 Informational %LINK-I-Up: 1/e26
20 2147483573 27-Dec-2004 08:01:49 Warning %STP-W-PORTSTATUS: 1/e26: STP status Forwarding
21 2147483574 27-Dec-2004 08:01:47 Warning %LINK-W-Down: 1/e26
22 2147483575 27-Dec-2004 07:58:11 Informational %LINK-I-Up: 1/e10
23 2147483576 27-Dec-2004 07:58:11 Warning %STP-W-PORTSTATUS: 1/e10: STP status Forwarding
24 2147483577 27-Dec-2004 07:58:09 Warning %LINK-W-Down: 1/e10
GregM_1
1 Rookie
•
112 Posts
0
December 27th, 2004 18:00
empmelanie
10 Posts
0
January 5th, 2005 15:00
OK - I'm finding out that people are rebooting alot because the network is being so flaky - slowness - hesitation.... So where do I look next?
I do have someone coming in with a network sniffer on Thursday - we're going to start really checking connections.... but is there some specific errors I could look for on the ports to see if I have a bad card or connection somewhere?
empmelanie
10 Posts
0
January 5th, 2005 22:00
Well did alot more research today - the people that are having the problems are in the 3348 switch - I moved 3 of them today (to the 3248) and they all breathed a huge sigh of relief - but now what to do with the rest? I don't have enough room on the 3248 for everyone -