Conference azur::mcc

5780.0. "Ultrix ELAM questions" by SIOG::PARKS () Thu Dec 09 1993 12:51

I have some questions on the Extended LAN AM (V1.3 August CDs) running on 
DECstation 5000/200 with 128 Mbytes and Ultrix V4.3 at a customer site.

I have a domain with the DECmcc icon registered. When I double click on the 
director icon to look at the child entities of the director, all the MMs 
enrolled should appear. I have the following questions

1) When I look into the director I get the following information message in 
a window. "The Show Identifier operation is not supported for MCC 0 FDDI_AM.
Supporting MM may not be enrolled." Is this normal ?  This does not happen
on a VMS system running DECmcc-EMS V1.3.

On Ultrix, when I execute the command 'show mcc 0 fddi_am all att' I get the 
error message
'MCC-E-NOTFOUND, unsupported combination of verb, entity, partition.'
This command works on VMS.

2) After doubling clicking on the director icon, the bridge_am does not show
up in the display. Using the command line interface, if I enter 'show mcc 0
bridge_am all att', the first line returned says "Cannot communicate with
target'. What's wrong here ? I can see the 'mcc_bridge_am' process running. I
tried enrolling the bridge_am and got a duplicate entries message.

On my office system (Ultrix), I don't see the bridge_am icon yet the spanning
tree map works and the command 'show mcc 0 bridge_am all att' works.  Is the
customer's DECmcc system corrupt ? (A mib load failed while updating the
dictionary, see note 5779). 

Colman

Reply also applies to previous topic.

It looks like the parse tables are out of sync and the previous abort
during dictionary update may well be the cause. It depends on exactly
where the segmentation fault hit. 

You should restore the saved dictionary files (.dat, .ctm and .bpt) and
see if it works like before the update mess. Then retry the update after
finding out what caused the abort (what does 'segmentation fault' mean?
I'm not an ULTRIX expert...) 

*Robert