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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MLT Drops for no reason
- Thread starter pcorbin1
- Start date
- Thread starter
- #3
Working in a Nortel enviroment i have seen some weird things with the Passports, 450,BPS2K ,Acclear,etc.
Nortel does not post that there are some problems with the MDA cards .
Description of the issue is intermittent connectivity problems. Ports losing
link, not passing traffic.
One of the ways to identify a possible MDA issue is if the MDA fails power
on diagnostic self-test.
The recommended action is to replace the MDA if you experience these issues.
But before hardware is to blame you should have recent or at best the latest images on your equipment.
Nortel does not post that there are some problems with the MDA cards .
Description of the issue is intermittent connectivity problems. Ports losing
link, not passing traffic.
One of the ways to identify a possible MDA issue is if the MDA fails power
on diagnostic self-test.
The recommended action is to replace the MDA if you experience these issues.
But before hardware is to blame you should have recent or at best the latest images on your equipment.
Using the latest 450 and 8600 code really seems to have helped the old MLT issues.
We still have customers scared to re-visit MLT as they had SO MANY problems a couple of years ago.
For existing problems on older code, we have found that the ONLY sure fire way to avoid MLT issues -apart from code upgrades- is to:-
For 8600's.
Build your configuration from scratch with a Vi editor from the factory default config.
Disconnect all trunk connections from the 8600, and reset to factory default then load your new config onto each SSF.
Connect up only a SINGLE trunk link to each device.
Now the 450's:
Disconnect all trunk connections, disconnect ALL cascade cables, reset EACH 450 to factory defaults, load your template config onto each switch, reset and power off.
Connect up all cascade cables, power on the STACK, now add your MLT settings, reset and only now can you plug in your trunk links, now you can connect up the rest of the 8600 trunk connections.
step away slowly, and NEVER make any alteration to the MLT settings again
We still have customers scared to re-visit MLT as they had SO MANY problems a couple of years ago.
For existing problems on older code, we have found that the ONLY sure fire way to avoid MLT issues -apart from code upgrades- is to:-
For 8600's.
Build your configuration from scratch with a Vi editor from the factory default config.
Disconnect all trunk connections from the 8600, and reset to factory default then load your new config onto each SSF.
Connect up only a SINGLE trunk link to each device.
Now the 450's:
Disconnect all trunk connections, disconnect ALL cascade cables, reset EACH 450 to factory defaults, load your template config onto each switch, reset and power off.
Connect up all cascade cables, power on the STACK, now add your MLT settings, reset and only now can you plug in your trunk links, now you can connect up the rest of the 8600 trunk connections.
step away slowly, and NEVER make any alteration to the MLT settings again
telecom116
MIS
If I'm in school, I'll raise my hand as one of those scared off by MLTs between an 8600 and 450s because of these exact issues.
I can't prove it, but I have a feeling that a cause of this might be if you have IPX running on the MLT.
I can't prove it, but I have a feeling that a cause of this might be if you have IPX running on the MLT.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question