T.R | Title | User | Personal Name | Date | Lines |
---|
1336.1 | | KONING::KONING | Paul Koning, B-16504 | Thu May 12 1994 12:25 | 7 |
| That's a feature, not a bug.
With FDDI, only DECnet uses the AA-00... address; other protocols continue
to use the hardware address. This eliminates problems caused by starting
things in the wrong order (as well as other, FDDI-specific, issues).
paul
|
1336.2 | startup sequence is ok. | MLNCSC::FACCHETTI | | Fri May 13 1994 02:52 | 7 |
| Hi,Paul
the problem is random,sometimes the fddi board respond with
AA-00-04.... and sometimes with 08-00-2b.... ,we install a fddi
analyzer and see that.
Gianni
|
1336.3 | | KONING::KONING | Paul Koning, B-16504 | Fri May 13 1994 15:39 | 4 |
| You mean that you sometimes see MOP messages with AA-00... source address?
That's not the way it is supposed to work.
paul
|
1336.4 | answere from the server aa-00-04 is correct... | MLNCSC::FACCHETTI | | Mon May 16 1994 10:24 | 7 |
| hi,PAUL
the answer to a MOP from del servers is sometime AA-00-04 ... and the
client (pc) works fine,and sometime the answere from the server is
08-00-2b... and the pc hangs
Gianni
|
1336.5 | | KONING::KONING | Paul Koning, B-16504 | Mon May 16 1994 12:44 | 7 |
| Perhaps the PCs are set up to assume the AA... address.
What I meant is: MOP isn't supposed to be using the AA... address on FDDI.
So if some client expects that, it should be changed so it doesn't, and the
server likewise.
paul
|