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!
Nortel Passport 8600 Routing Issues
- Thread starter rsieler
- Start date
It's been about a year since I've worked on an 8600 but I'll try to help you since it seems on one else has tried.
You haven't stated what routing protocol you're using but since you have routes aging out I'll assume you're using at least RIP. If so, which version? RIP 1 or 2?
It would appear that the 8600 isn't getting or understanding the routes it's receiving and then aging them out after the timeout.
What is the type and make of equipment that the 8600 is receiving the routing updates from? What's the firmware version on the 8600?
BTW, I don't know how big your network is or how dynamic it is but if it's not too large it's actually easier to use static routes IMHO.
You haven't stated what routing protocol you're using but since you have routes aging out I'll assume you're using at least RIP. If so, which version? RIP 1 or 2?
It would appear that the 8600 isn't getting or understanding the routes it's receiving and then aging them out after the timeout.
What is the type and make of equipment that the 8600 is receiving the routing updates from? What's the firmware version on the 8600?
BTW, I don't know how big your network is or how dynamic it is but if it's not too large it's actually easier to use static routes IMHO.
- Thread starter
- #4
Thank you CPUSmith.
It's a large network. And we did solve the problem. The problem was BAD HARDWARE. The 48 port 10/100 blade has a section of 12 ports, not affection network connectivity, but affecting routing being passed to the 8600 from the ASN Router. We switched ports that the ASN was plugged into and called Nortel to replace the Blade. Maybe you know what is special about how the ASN talks to the 8600 and why only that would be affected by this malfunction and not all 12 ports connectivity to the network. The other 11 ports have servers plugged in and we didn't have any problems with them.
Thanks,
Ryan
It's a large network. And we did solve the problem. The problem was BAD HARDWARE. The 48 port 10/100 blade has a section of 12 ports, not affection network connectivity, but affecting routing being passed to the 8600 from the ASN Router. We switched ports that the ASN was plugged into and called Nortel to replace the Blade. Maybe you know what is special about how the ASN talks to the 8600 and why only that would be affected by this malfunction and not all 12 ports connectivity to the network. The other 11 ports have servers plugged in and we didn't have any problems with them.
Thanks,
Ryan
ministryman
IS-IT--Management
I stumbled across this post, and I need to ask you a question:
Which ports failed you?
I ask because I am not getting OSPF route updates.
Hmmmmm.....................
Which ports failed you?
I ask because I am not getting OSPF route updates.
Hmmmmm.....................
- Thread starter
- #6
It was port 7/1 which is a 48port 10/100 blade which was the port that our ASN Router was plugged into. Our quick fix was to move the ASN to another open port which just so happened to be on the other side of the card 7/47. The issue acctually turned out to be bad Switching Fabrics, we may have other issues still as well. If you are using duel processors, the load is split between the two. It's not split by the top CPU processing the top cards and the bottom processing the bottom, it's spilt by the top processing the left side of each card and the bottom CPU processing the right side of each card. If you have two CPU's try removing each one at a time and see if your problem goes away. We still aren't sure whether or not there is a software fix for this problem or whether it is bad hardware. We have maintenance and they were replaced for us.
- Status
Similar threads
- Locked
- Question