| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hi.
This is an interesting one. I've been setting up a DECmcc
workstation on a site where the main backbone is a token ring with IBM
8209 bridges connecting the various ethernet segments via the token
ring backbone. This all works fine with the various DECnet and SNMP
nodes across the site. However it doesn't give management capability of
the 8209's which would be nice. I suggested that as they are on the
ethernet we could at least register them as ethernet stations and test
when necessary etc. We got the ethernet address and attempted to
register the 8209 and..... it crashed !
It did take a while to trace the fact that this was happening due
to the registration via DECmcc. Can anyone shed any light/guess as to
why this could happen ? I tried the various options under the functions
supported field and it still crashed so I'm at the stage where I can
only blame the IBM box for lack of capability.
Thanks for any help,
Euan
>>>Cross-posted in Token Ring file>>>>>
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5073.1 | problem solved | SMAC10::BARKER_E | Ummm... | Tue May 18 1993 13:20 | 44 |
Answer found, I missed one of the options :- details follow :-
Subject: RE: IBM 8209 and DECmcc
Greetings,
My guess is that the IBM 8209 Agent has a problem.
Can you (if you haven't done this already) issue the TEST STATION
<address>
command (with 8209 *NOT* registered in MCC) from the FCL UI, with
FUNCTION
SUPPORTED = IEEE802_Only, to see whether THIS command crashes the
bridge?
It's the simplest standard request (IEEE802.2 TEST) that MCC can make
to
an entity.
If it crashes with the above request, IBM has a problem!
Chris
----------------------------------
Chris,
We must have missed that specific option on Friday as it works,
and
they have managed to register the bridge as well. Thanks for the
advice, and sorry to trouble you for no real reason. I think we
skipped
IEEE802.2 as the 8209 is meant to have an algorithm that picks up
whether each ethernet address on the network is talking Ethernet V2
or
IEEE 802.2. As we are running DECnet Phase IV on the mcc system I
assumed only Enet V2 would be responded to by the 8209, wrongly as
it
happens !
Thanks again,
Euan
| |||||