Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MLT issues 8600 and 470 stack

Status
Not open for further replies.

norteldude78

IS-IT--Management
Nov 10, 2005
214
US
I have an MLT between 8600 and 470 stack (3).

Code on 8600 is 3.2, on 470 is 3.6

Using fiber GBIC's on the 470's. When one link is taken down there is no packet loss/connectivity issues.

When the MLT is up, frame errors are recieved on the 470 port statistics and clients have some connection problems.

Ports are tagged, there is one spanning tree group. My question is what could be causing the frame errors? The MDA's in each switch have been swicthed several times and the frame errors don't seem to follow a particular device.

Let me know if you need more information. Thanks for all your guys help, im new to the forum.


peace
 
Are you tagging VLANs? Spanning tree off on the ports?

How do you have the MLT set on each?

For the 8600, in the MLT_LACP config, what is the port type and MLT type set to?

On the 470, is it set as access or trunk?
 
Thank you for response.

MLT is set and enabled on each, have tried disabling and enabling it after connecting cables, makes no difference.

STP is enabled, i figure this shouldnt matter though since it is logically one link, though i may be mistaken.

The 470 is tagged, i think that answers your last question, correct?

Not sure where to look on the 8600 for the MLT_LACP config. How can I check the port type and MLT type? Should they be a certain value?

Thanks again. In the meantime i'll check the docs, im completely new to the 8600.

peace
 
Ethernet frame errors indicate the packets are a valid size but are not framed right or have CRC errors. Do you get any other counters on either side?

It could be that the 470 isn't recognizing the tagged packets, but that shouldn't change when only one link is in use... and packets routed over a normal MLT look the same as any other packet on the wire. I assume it doesn't matter which links in the MLT are active, the issue only occurs when both are up?

What kind of client connection problems do you see, are the issues sporadic or consistent? Also: does it seem like every packet increments the frame error counter or only a fraction of them?

This will show the basic config for MLT X on the 8600:
config mlt X info

8600 Version 3.2 is fairly old, perhaps this is some kind of bug that might be mentioned in later release notes. If you do a "show sys sw" what is the exact version you're running?
 
Thanks for the help. Can't really pinpoint what clients have problems. I could run a packet trace, but there is a lot of traffic on this network, so I might not be able to decipher what is what. It doesnt seem like every packet causes an error. The errors increase, but not as rapid as packets do. I guess this could be a certain type of traffic or PDU?

The issue is consistent and it only happens when the MLT is up. It happens on any giving link, but once the MLT is up, the errors stay on one link. I will check the release notes.

Unfortunately, I won't be able to change any configs right now, one link must be up at all times and I dont want to take any chances. I won't have more news for at least a week, I appreciate all your help, I think I am headed in the right direction.

peace
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top