While trying to track down some network issues this morning we came across a handful of ports on the passport (8600) that had their duplex settings set to auto-negotiate. As of Friday at 6:00 these ports were set to 100/full with autonegotiate disabled. I verified these settings before I left the office. Over the weekend we upgraded our database system, but made no changes to the passport itself. I have looked through the logs with Nortel and there is no indication of a change being made or even of one of the suspect ports bouncing. We are running 3.7.0.0 code. I can find no reason why this would suddenly go back to autonegotiation and only on a handful of ports. Other config on the passport seems ok. We aren't seeing any errors and the port is negotiated properly, but these are mission critical servers and our policy is to have them hard coded due to the possible issues with autonegotiation. Any ideas why this changed? And how?
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!
Strange passport issue
- Thread starter AyrishGrl
- Start date
Sounds like a bug to me.
Any chance someone changed it via Java Device Manager rather than the TI?
Version 3.7.7.0 just came out. You might want to check release notes between your version (3.7.0.0) and the latest. Just because Nortel didn't identify it as a bug doesn't mean it's okay.
In most cases, the engineer you get at Nortel very much determines what type of info you get (good, bad, something in between).
Good luck...
- Thread starter
- #3
No, changes were not made using DM (at least not that we are aware of). I will check the release notes.
Is there any way to track config changes that have been made either via CLI or DM? The Nortel tech assured me that this was not possible, yet there was no bug related to it.
Out of all the groups at Nortel I have dealth with the Passport group seems to give me the worst support.
Is there any way to track config changes that have been made either via CLI or DM? The Nortel tech assured me that this was not possible, yet there was no bug related to it.
Out of all the groups at Nortel I have dealth with the Passport group seems to give me the worst support.
re: Track changes. Unless it's a recent addition, I don't think there's any way to do that. Bay RS (routers) has the audit feature that tracks the MIBs but I don't think the Passport has anything like that.
re: Passport Support. I agree, I've had Nortel give me wrong info on Passport questions, charge me for that question...then charge me to correct the incorrect info...*laughing* (needless to say we didn't pay).
I'll poke around a little bit when I get some free time. I have a customer who was trying to figure out a way to do that but I don't know where they got with it. To the best of my knowledge, Nortel told the truth this time.
(oh yeah!...did you get Report Generator working okay?)
What you can do, from version 3.7 ?? is enabling cli logging.
Another option and that exist already from 3.3 ?? is using radius logging.
Anyway you need radius, otherwise you have no track of the user who's doing the changes (identify the user).
And for every 40 commands (or when the telnet session is closed), the switch will send a list of used commands to the radius server.
Another option and that exist already from 3.3 ?? is using radius logging.
Anyway you need radius, otherwise you have no track of the user who's doing the changes (identify the user).
And for every 40 commands (or when the telnet session is closed), the switch will send a list of used commands to the radius server.
netmanrick
Technical User
Hi:
What's on the other end of those ports? I suspect(can't prove it)that a conbination of JDM,8600 TX blade rev,switch
type(450/470);switch fw rev has caused me this type of problem.
I've access the 8600's(8606&8610) with jdm just to check some data and when I exited JDM wanted to know if I wished to save changes.
Another piece of the puzzle: Optivity is running.
Rick Harris
SC Dept of Motor Vehicles
Network Operations
What's on the other end of those ports? I suspect(can't prove it)that a conbination of JDM,8600 TX blade rev,switch
type(450/470);switch fw rev has caused me this type of problem.
I've access the 8600's(8606&8610) with jdm just to check some data and when I exited JDM wanted to know if I wished to save changes.
Another piece of the puzzle: Optivity is running.
Rick Harris
SC Dept of Motor Vehicles
Network Operations
- Status
Similar threads
- Locked
- Question
- Locked
- Question