T.R | Title | User | Personal Name | Date | Lines |
---|
116.1 | Please gather some more data- does agent work | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Tue Jan 05 1993 21:00 | 6 |
| Look at the agent out of band port. See what address youhave for the
bridge.
Try connecting to the bridge from the agent out of band (choice 18).
This all assumes you have the bridge at 3.0.
|
116.2 | Bridge 90 3 ethernet addresses? | ANGLIN::ORTHOBER | | Wed Jan 06 1993 10:27 | 22 |
|
Ok, using the only menu entry on the console
of the agent that I did not before (connect)
I got to the bridge a here are the addresses...
08-00-2b-29-89-13 (hub address, port1)
08-00-2b-2d-4a-a5 (port 2)
But when I do a show module address from
the agent for the bridge I get...
08-00-2b-2e-fc-bb
Which is what is stamped on the outside of the
bridge...
I'll try the other addresses, but what gives?
The bridge does not have 3 addresses?
thanks
ort1
|
116.3 | None of the 3 addreses work for the bridge | ANGLIN::ORTHOBER | | Wed Jan 06 1993 10:35 | 9 |
|
Well I tried all three of the above addresses and
none work. What else could I be doing wrong?
Ultrix V4.3, MSU V1.1, Hubwatch V1.0 (I think)
thanks
ort1
|
116.4 | Update your bridge to 3.0 | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Fri Jan 08 1993 12:27 | 4 |
| try updating your bridge to V3.0.
Bridge version shows up on screen when you connect to it (MOP or from
agent)
|
116.5 | Dec Bridge 90 Need V3.0 FEPROM Version | ANGLIN::ORTHOBER | | Sat Jan 09 1993 01:52 | 4 |
|
Yep, that was the problem. It would have been nice if hub watch
would have told be that the bridge is not up to rev, maybe it
simply never got that far...
|
116.6 | Will put bridge code check in the manuals | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Tue Jan 19 1993 10:23 | 3 |
| NIce, but we do not have time in the schedule to do this at the
moement. I will notify the writers to put this in the manual as a step
in setup and also as part of the what to do if problems section.
|