High Packet Loss - Sporadic After GB Switch Upgrade

Hello,
We are experiencing an issue after our GB switch was upgraded from 100MB.  The switch I am referring to in this case will be referred to as SWITCH1 and SWITCH2, which are being presented virtually via the IOS as SWITCHVM.  We have been experiencing sporadic outages, which are affecting the following services: DHCP, DNS, and corporate email.  Users are noticing limited network connectivity on their NICs via the client OS.  Listed below is the sequence of the events:

Interface GigabitEthernet0/1 - Gi0/1 on Node SWITCH3.dom has risen above 10%.  The actual packet loss is:  60 %.

Interface Vlan18 - Vl18 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface Vlan16 - Vl16 on Node SWITCH1.dom  has risen above 10%.  The actual packet loss is:  30 %.

Interface Port-channel1 • fileserver001 on Node SWITCH1.dom  has risen above 10%.  The actual packet loss is:  30 %.

Node SWITCH1.dom's packet loss has risen above 40% to 60 %%.

Interface SWITCH1.dom • AD001 2/1 on Node SWITCH1.dom  has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet1/0/7 • IMAGEsrv 0/2 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet1/0/9 • NJ005 3/1 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet1/0/11 • NJ004 0/1 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface StackPort2 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet1/0/12 • Fileserver01 0/1 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet1/0/10 • Fileserver01 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface StackPort1 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet1/0/8 • SWITCH1.dom on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet2/0/12 • Fileserver01 0/2 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet2/0/1 • FW001B 0/1 on Node SWITCH1.dom has risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet1/0/23 • trunk to SW001.1 on Node SWITCH1.domhas risen above 10%.  The actual packet loss is:  30 %.

Interface GigabitEthernet1/0/24 • trunk to JSW020 on Node SWITCHVM.dom has risen above 10%.  The actual packet loss is:  30 %.

Node SW003.jtax.com is Down.

Node SWITCHVM.dom packet loss has risen above 40% to 70 %%.

Node SWITCHVM.dom is Down.

Node SWITCHVM.dom packet loss has risen above 40% to 50 %%.

Interface GigabitEthernet0/1 - Gi0/1 on Node SWITCHVM.dom has risen above 10%.  The actual packet loss is:  50 %.

Interface GigabitEthernet0/1 - Gi0/1 on Node SWITCHVM.dom has risen above 10%.  The actual packet loss is:  20 %.

Interface GigabitEthernet0/1 - Gi0/1 on Node SWITCHVM.dom has risen above 10%.  The actual packet loss is:  50 %.

Interface GigabitEthernet0/1 - Gi0/1 on Node SWITCHVM.dom has risen above 10%.  The actual packet loss is:  50 %.

Interface GigabitEthernet0/1 - Gi0/1 on Node SWITCHVM.dom has risen above 10%.  The actual packet loss is:  50 %.

Interface GigabitEthernet0/2 - Gi0/2 on Node SWITCHVM.dom has risen above 10%.  The actual packet loss is:  50 %.

Node SWITCHVM.dompacket loss has risen above 40% to 50 %%.

Interface GigabitEthernet0/1 - Gi0/1 on Node SWITCHVM.dom has risen above 10%.  The actual packet loss is:  50 %.

Node SW002.jtax.com's packet loss has risen above 40% to 50 %%.

Node SW002.jtax.com's packet loss has risen above 40% to 50 %%.

Interface GigabitEthernet0/2 - Gi0/2 on Node SW002.jtax.com has risen above 10%.  The actual packet loss is:  50 %.

Node SW003.jtax.com is Up.

Interface GigabitEthernet0/1 - Gi0/1 on Node SW004.jtax.com has risen above 10%.  The actual packet loss is:  30 %.

Node SWITCHVM.dom  has rebooted at Friday, December 23, 2011 8:47 AM.

Node SWITCHVM.dom  is Up.



jduran04Asked:
Who is Participating?
 
webwyzsystemsCommented:
You'll need to get your network verified professionally I'm afraid. Most people simply don't have access to the tools: specifically the meter that tests maximum speed capability, noise and wire length.

The meters cost about $1200 for a decent one. You can get the entry level models for around $500.

Hiring a pro will cost you about $250 - $300, depeding upon facility size of course. But you should end up with a detailed network wiring map, information about the capacity of every jack on the system, a verified head end, and a list of recommendations on proceeding with the best fixes.
If its a simple pull...the tech might even pull in CAT6 for you and fix the issue immediately.

Wire length can play a part in older infrastructure too. 100 meters is the maximum distance for any network cable working on standard hardware. I mention this because some facilities used to use an inline 100 Mb POE switch! So, somewhere hidden in the building is a hardware peice that chops off GB! Very annoying to find!
0
 
LDIitManagerCommented:
Sounds like a duplex mismatch issue.
Can you verify the new switch speed and duplex settings?
I would not rely on the switch-port statistics.
0
 
webwyzsystemsCommented:
Hows the wiring and network infrastructure? I have seen similar issues when there is CAT3 run in the infrastructure somewhere. CAT 3 simply doesn't have the bandwidth capabilities....it's too noisy.

How old is the facility you are in? Is it possible that punch blocks for the phone system have been used in running the network? If so, CAT 3 might have been used somewhere and this will cause speed and packet loss in a gb system for sure.

0
 
jduran04Author Commented:
The wiring is very poor and I would not be surprised if that is what is causing the issue.  There is a high probability that CAT3 is running from the infrastructure somewhere.  I would not be surprised.  What would you recommend as troubleshooting steps in isolating this issue?  It may be very difficult to isolate a bad CAT3 cable especially if they are not marked as such.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.