[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

3563.0. "'Entity not valid' when trying to invoke Autotopology-created domain" by CADSYS::LEMONS (And we thank you for your support.) Thu Aug 13 1992 18:03

DECmcc V1.2 and DECmcc ELM V1.2

I'm using the DECmcc Map interface to try to examine a domain created by
Autotopology.

I select 'Open Domain', click 'Filter', wait a minute for my skads of domains
to appear.  I see my new domain (HLOMCC_NS:.mcc.domain.hlo_bridges) in the Open
Domain window.  I click on my new domain (it turns reverse video), then click
on Open.  Several seconds later, I get the following pop-up message:

		DECmcc Message:

	Map Window Message:  Entity not valid. Please check spelling.

		Acknowledged

What's to check?   I click on a domain that I see, and it barfs.

A dir/title="Entity not valid" did not find this, nor is this error message in
the Autotopology manaul.  Sorry if it's been reported, and I can't find.

tl
T.RTitleUserPersonal
Name		DateLines
3563.1VERNA::V_GILBERTFri Aug 14 1992 09:029
Check (using FCL) what is in this new domain (HLOMCC_NS:mcc.domain.hlo_bridges).

My guess is that some entity in the domain is not in the dictionary and when
the Iconic Map tries to parse that particulary domain member, it returns this
error.  Check the classes of entities in the domain vs those in the dictionary
(or even look at the entity classes in the toolbox).

Hope this helps,
Verna
3563.2Maybe DNS problem...MSBCS::HSUFri Aug 14 1992 11:216
    Hi! 
      I guess it might have something to do with the MCC_DNS_SELECTION
    (name registration). I think if you change the logical
    MCC_DNS_SELECTION to "MIR", it might work.
    
    -Hamilton
3563.3CADSYS::LEMONSAnd we thank you for your support.Fri Aug 14 1992 11:2645
Verna

Thanks for the hint.

1) how could this happen?  Did I do something wrong?

2) This domain has ~ 50 members.  How can I figure out which one MCC is
throwing up on?

3) many of the bridge were added with names like BR_08002B2F2D7D.  I'd rather
use the real names for the bridges.  What's the best way to make this happen?

4) I see the following errors in MCC_STM_FM_HLO_BRIDGES_MESSAGES.LOG

(E)  Error polling bridge - bridge name: BR_08002B2F2D7D
- bridge address: 08-00-2B-2F-2D-7D
(E)  Error polling bridge - bridge name: BR_08002B2F2D7E
- bridge address: 08-00-2B-2F-2D-7E
(E)  Error polling bridge - bridge name: BR_08002B26DC66
- bridge address: 08-00-2B-26-DC-66
(E)  Error polling bridge - bridge name: BR_08002B26DC67
- bridge address: 08-00-2B-26-DC-67

Could these contribute to my problem?

5) I see the following errors in MCC_STM_HLO_BRIDGES_AUTOREG.LOG:

REGISTER BRIDGE HLOMCC_NS:.mcc.domain.HLOMCC_NS:.L2A1 ADDRESS=08-00-2B-2C-7E-9F
%MCC-I-NOPARCMD, BRIDGE HLOMCC_NS:.mcc.domain.HLOMCC_NS:.L2A1 ADDRESS=08-00-2B-
                 ^
%MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
%MCC-E-INVALIDIDENT, invalid entity identifier

CREATE DOMAIN HLOMCC_NS:.mcc.domain.hlo_bridges MEMBER HLOMCC_NS:.mcc.domain.HLOMCC_NS:.L2A1
%MCC-I-NOPARCMD, MEMBER HLOMCC_NS:.mcc.domain.HLOMCC_NS:.L2A1
                 ^
%MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
%MCC-W-ARGSYNTAX, syntax error in argument :

REGISTER BRIDGE HLOMCC_NS:.mcc.domain.BR_08002B2C76FD ADDRESS=08-00-2B-2C-76-FD

What should I do about this, and could they contribute to my problem?

Thanks!
tl
3563.4CADSYS::LEMONSAnd we thank you for your support.Fri Aug 14 1992 11:4910
More information:

1) two of my bridges are 'partially registered'.  Could this cause the
problem I'm seeing?

2) One of the two bridges is a Vitalink bridge.  If I need to have it
registered, how can I do this on a DECmcc V1.2 system?

Thanks!
tl
3563.5partial answerTOOK::MCPHERSONLife is hard. Play short.Fri Aug 14 1992 12:5413
> 2) One of the two bridges is a Vitalink bridge.  If I need to have it
> registered, how can I do this on a DECmcc V1.2 system?

You can't register it as a bridge.
You _could_ register it as
	1) a station
	2) an SNMP sntity (if you're running the latest version of Translan
	   software (that supports an SNMP agent on the bridge.)  This would be
	   	10.5 for TL350 or TL335
	   	20.3 for TL320
	   	6.11 for TLIII

/doug
3563.6CADSYS::LEMONSAnd we thank you for your support.Fri Aug 14 1992 13:0933
Re .5

>You can't register it as a bridge.

I hear you, but autotoplogy did it!

Bridge HLOMCC_NS:.mcc.domain.UBR_08007C0006C1
AT 13-AUG-1992 16:26:26

Partial registration success. Please retry later to complete the registration.
.
.
.
REGISTER BRIDGE HLOMCC_NS:.mcc.domain.UBR_08007C0704FF ADDRESS=08-00-7C-07-04-FF

Bridge HLOMCC_NS:.mcc.domain.UBR_08007C0704FF
AT 13-AUG-1992 16:30:36

Registration Successful

By the address, we know they're Vitalinks.  And the second bridge seems to have
been registered successfully.

The Autotopolgy manual states (in Section 5 'Spanning Tree Maps' 'Analyzing Map
Results):

     "The bridge could not be polled so its location in the tree is
      unknown. These bridges are names using the convention
      UBR_<bridge_id> and are partially registered as bridge entities."

Hmmm.

tl
3563.7QAR 3361TOOK::MINTZErik Mintz, dtn 226-5033Fri Aug 14 1992 13:132
This note and replies -> .7 entered as QAR 3361
3563.8Partial registration is intentionalQUIVER::HAROKOPUSFri Aug 14 1992 14:3160
Partial registration of "bridges" that could not be reached with the
bridge AM (but were found to be on the map)  is done intentionally.  These
bridges cannot be managed, but it was the only way to get the IMPM to 
display the icons in the domain window.  

This does not explain why you cannot open the domain.   


>3) many of the bridge were added with names like BR_08002B2F2D7D.  I'd rather
>use the real names for the bridges.  What's the best way to make this happen?

These are autogenerated names for bridge that were not already registered.
There is a rename bridge command to change the names.


>4) I see the following errors in MCC_STM_FM_HLO_BRIDGES_MESSAGES.LOG
>
>(E)  Error polling bridge - bridge name: BR_08002B2F2D7D
>- bridge address: 08-00-2B-2F-2D-7D
>(E)  Error polling bridge - bridge name: BR_08002B2F2D7E
>- bridge address: 08-00-2B-2F-2D-7E
>(E)  Error polling bridge - bridge name: BR_08002B26DC66
>- bridge address: 08-00-2B-26-DC-66
>(E)  Error polling bridge - bridge name: BR_08002B26DC67
>- bridge address: 08-00-2B-26-DC-67

None of these would cause the problem you are seeing.   This simply means these
bridges could not be polled by the Bridge_AM.


>5) I see the following errors in MCC_STM_HLO_BRIDGES_AUTOREG.LOG:
>
>REGISTER BRIDGE HLOMCC_NS:.mcc.domain.HLOMCC_NS:.L2A1 ADDRESS=08-00-2B-2C-7E-9F
>%MCC-I-NOPARCMD, BRIDGE HLOMCC_NS:.mcc.domain.HLOMCC_NS:.L2A1 >ADDRESS=08-00-2B-
>                 ^
>%MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
>%MCC-E-INVALIDIDENT, invalid entity identifier
>
>CREATE DOMAIN HLOMCC_NS:.mcc.domain.hlo_bridges MEMBER HLOMCC_NS:.mcc.domain.HLOMCC_NS:.L2A1
>%MCC-I-NOPARCMD, MEMBER HLOMCC_NS:.mcc.domain.HLOMCC_NS:.L2A1
>                 ^
>%MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
>%MCC-W-ARGSYNTAX, syntax error in argument :

I don't know how these records got into the autoregistration script.  Was this
file editted??  The first bridge name looks invalid. 

I agree with Verna something in your dictionary appears to be not right. 
Can you post the following:

$manage/tool/dict
show class bridge
show class domain


Thanks,

Bob
3563.9Information requestedCADSYS::LEMONSAnd we thank you for your support.Fri Aug 14 1992 14:43175
    > Was this file editted??
    
    Nope.  I ran it just as it was given to me.
    
    > Can you post the following:
    
    As requested:
$ manage/tool/dict
%DAP-S-USE_DICT_RDONLY, Using dictionary file: sys$common:[mcc]mcc_fdictionary.dat;5, with read-only access
)0
=



	DECmcc Dictionary Administrator Program   Version V1.2.0



DAP> show class bridge



-> Class (1) : BRIDGE

     Definition (3) : PRESENTATION_NAME

     Definition (3) : INSTANCE_REQUIRED

     Definition (3) : DYNAMIC

     Definition (3) : INSTANCE_DATATYPE

     Definition (3) : VARIANT_SELECTOR

     Subclass (2) : PROTOCOLDATABASE 11

     Subclass (2) : LINE 12

     Subclass (2) : FORWARDINGDATABASE 21

     Subclass (2) : PHYPORT 47

     Attribute (5) : NAME 1

     Attribute (5) : ADDRESS 2

     Attribute (5) : ID 4

     Attribute (5) : HARDWARETYPE 5

     Attribute (5) : HARDWAREVERSION 6

     Attribute (5) : SOFTWAREVERSION 7

     Attribute (5) : UPDATESWITCH 8

     Attribute (5) : DOWNLINELOADSWITCH 10

     Attribute (5) : DOWNLINELOADFILENAME 11

     Attribute (5) : PORTCOUNT 12

     Attribute (5) : ROOTPRIORITY 13

     Attribute (5) : BADHELLOLIMIT 14

     Attribute (5) : BADHELLORESETINTERVAL 15

     Attribute (5) : PORTTESTPASSEDTHRESHOLD 16

     Attribute (5) : PORTTESTINTERVAL 17

     Attribute (5) : NOFRAMEINTERVAL 18

     Attribute (5) : HELLOINTERVAL 19

     Attribute (5) : LISTENTIME 20

     Attribute (5) : FORWARDINGDELAY 21

     Attribute (5) : IPFRAGMENTATIONSWITCH 22

     Attribute (5) : UPLINEDUMPSWITCH 23

     Attribute (5) : PREFERREDDUMPHOST 24

     Attribute (5) : LASTDUMPHOST 25

     Attribute (5) : DOWNLINELOADPHYSICALSWITCH 26

     Attribute (5) : LASTLOADHOST 27

     Attribute (5) : LOOPSELFTESTSWITCH 28

     Attribute (5) : NVRAMRESETSWITCH 29

     Attribute (5) : BRIDGEONLYSWITCH 30

     Attribute (5) : RESETDEFAULTSSWITCH 31

     Attribute (5) : LB100SPANNINGTREECOMPATIBILITY 32

     Attribute (5) : LANBRIDGE100BEINGPOLLED 33

     Attribute (5) : LB100SPANNINGTREEVERSION 34

     Attribute (5) : LB100POLLTIME 35

     Attribute (5) : LB100RESPONSETIMEOUT 36

     Attribute (5) : IEEE802SPANNINGTREEVERSION 37

     Attribute (5) : PASSWORD 38

     Attribute (5) : BRIDGEFUNCTION 39

     Attribute (5) : DEVICESTATE 40

     Attribute (5) : MANAGEMENTHEARDPORT 41

     Attribute (5) : BESTROOT 42

     Attribute (5) : BESTROOTPRIORITY 43

     Attribute (5) : BESTROOTAGE 44

     Attribute (5) : ROOTPORT 45

     Attribute (5) : MYCOST 46

     Attribute (5) : TIMESINCELASTHELLOSENT 47

     Attribute (5) : TOPOLOGYCHANGEFLAG 48

     Attribute (5) : TOPOLOGYCHANGENOTIFICATIONFLAG 49

     Attribute (5) : TOPOLOGYCHANGETIMER 50

     Attribute (5) : ACTUALHELLOINTERVAL 51

     Attribute (5) : ACTUALFORWARDDELAY 52

     Attribute (5) : ACTUALLISTENTIME 53

     Attribute (5) : FRAGMENTATIONERRORCHECKSWITCH 54

     Attribute (5) : NVRAMFAILEDFLAG 55

     Attribute (5) : DEVICEBROKENREASON 56

     Attribute (5) : SPANNINGTREEMODE 57

     Attribute (5) : LOADEDTASKS 58

     Attribute (5) : COUNTERCREATIONTIME 59

     Attribute (5) : SECONDSOPERATING 60

     Attribute (5) : MANAGEMENTRESETS 61

     Attribute (5) : POWERUPS 62

     Attribute (5) : DEVICEFRAMESLOST 63

     Attribute (5) : UPLINEDUMPFAILED 64

     Attribute (5) : UPLINEDUMPSUCCESS 65

     Attribute (5) : SPANNINGTREEMODECHANGES 66

     Attribute (5) : INVALIDPASSWORDS 67

     Attribute (5) : UNSOLICITEDRESETS 68

     Attribute (5) : LOCATION 69

     Attribute (5) : IMPLEMENTATIONDESC 70

     Attribute (5) : RESPONSIBLEPERSON 71

     Attribute (5) : PHONENUMBER 72

     Attribute (5) : MAILACCOUNT 73

     Attribute (5) : REMARKS 74

     Attribute (5) : TEXTFILE 75

     Attribute (5) : ADDRESSTABLEOVERFLOWFLAG 76

     Attribute (5) : CONFIGURATIONERRORFLAG 77

     Attribute (5) : HUBMANAGEMENTENABLED 78

     Attribute (5) : NTPENTRY 79

     Attribute (5) : NTPTABLE 80

     Attribute (5) : IPADDRESS 81

     Attribute (5) : DEFAULTIPGATEWAY 82

     Attribute (5) : TRAPADDRESS 83

     Attribute (5) : TRAPADDRESSTABLE 84

     Attribute (5) : DEVICECONFIGURATION 85

     Attribute (5) : DIAGNOSTICBLOCK 86

     Attribute (5) : SNMPSETSALLOWEDSWITCH 87

     Attribute (5) : SOFTWAREMINORVERSION 88

     Attribute (5) : DEVICECONFIGURATIONERRORCONDITION 89

     Attribute (5) : ROMVERSION 90

     Directive (6) : SHOW 1

     Directive (6) : SET 2

     Directive (6) : TEST 3

     Directive (6) : RESET 5

     Directive (6) : ADD 21

     Directive (6) : REMOVE 25

     Directive (6) : DIRECTORY 26

     Directive (6) : REGISTER 29

     Directive (6) : DEREGISTER 30

     Directive (6) : ERASE 33

     Directive (6) : RENAME 34

     Directive (6) : GETVARSELECTOR 124

     Attribute_Partition (11) : IDENTIFIERS 1

     Attribute_Partition (11) : STATUS 2

     Attribute_Partition (11) : COUNTERS 3

     Attribute_Partition (11) : CHARACTERISTICS 4

     Attribute_Partition (11) : REFERENCES 5

     Attribute_Group (12) : SPANNINGCHARACTERISTICS 76



DAP> 

DAP> show class domain



-> Class (1) : DOMAIN

     Definition (3) : PRESENTATION_NAME

     Definition (3) : INSTANCE_REQUIRED

     Definition (3) : DYNAMIC

     Definition (3) : INSTANCE_DATATYPE

     Subclass (2) : RULE 5

     Subclass (2) : MEMBER 88

     Subclass (2) : EXPRESSIONRULE 600

     Subclass (2) : COMPARISONRULE 601

     Subclass (2) : OCCURSRULE 602

     Subclass (2) : OCCURSNTIMERULE 603

     Subclass (2) : CHANGEOFRULE 604

     Attribute (5) : DOMAINNAME 1

     Attribute (5) : OWNERID 12

     Attribute (5) : DIRECTORY 13

     Attribute (5) : LOCATION 100

     Attribute (5) : IMPLEMENTATIONDESC 101

     Attribute (5) : RESPONSIBLEPERSON 102

     Attribute (5) : PHONENUMBER 103

     Attribute (5) : MAILACCOUNT 104

     Attribute (5) : REMARKS 105

     Attribute (5) : TEXTFILE 106

     Directive (6) : SHOW 1

     Directive (6) : SET 2

     Directive (6) : CREATE 12

     Directive (6) : DELETE 13

     Directive (6) : COPY 20

     Directive (6) : DIRECTORY 26

     Directive (6) : POPULATE 27

     Directive (6) : REGISTER 29

     Directive (6) : NOTIFY 121

     Directive (6) : ASSIGNTARGET 306

     Directive (6) : DEASSIGNTARGET 307

     Directive (6) : DIRECTORYTARGETS 309

     Attribute_Partition (11) : IDENTIFIERS 1

     Attribute_Partition (11) : CHARACTERISTICS 4

     Attribute_Partition (11) : REFERENCES 5



DAP> exit
3563.10VITALINK and BRIDGECHRISB::BRIENENDECmcc LAN and SNMP Stuff...Mon Aug 17 1992 12:0823
RE: 3563.5

>> 2) One of the two bridges is a Vitalink bridge.  If I need to have it
>> registered, how can I do this on a DECmcc V1.2 system?
>
>You can't register it as a bridge.
>You _could_ register it as
>	1) a station
>	2) an SNMP sntity (if you're running the latest version of Translan
>	   software (that supports an SNMP agent on the bridge.)  This would be
>	   	10.5 for TL350 or TL335
>	   	20.3 for TL320
>	   	6.11 for TLIII


 Why can't a Vitalink Bridge be registered as a BRIDGE ?

 Did the code to do this get -removed- from the Bridge AM for V1.2 ?

 Bridge AM (until recently?) supported a subset of information (BRIDGE and
LINE) for the TransLAN III and 350.

						Chris
3563.11SLINK::CHILDSEd ChildsMon Aug 17 1992 12:567
--> Did the code to do this get -removed- from the Bridge AM for V1.2 ?

    I don't think so.  There are still Vitalink bridges listed in the spec
    and translation table.

    Chris, do you know which bridge commands have been tested with Vitalink
    bridges and known to work?
3563.12At least SHOW worked...CHRISB::BRIENENDECmcc LAN and SNMP Stuff...Mon Aug 17 1992 19:5611
>    Chris, do you know which bridge commands have been tested with Vitalink
>    bridges and known to work?

Boy, it's been awhile...

I'm pretty sure that the SHOW directive worked for BRIDGE and LINE entities.
I seem to recall REGISTER working as well...

I don't have a Vitalink hanging around to test with.

						Chris
3563.13accidental support;dead as of 6.9.7TOOK::MCPHERSONLife is hard. Play short.Mon Aug 17 1992 22:5023
>>    Chris, do you know which bridge commands have been tested with Vitalink
>>    bridges and known to work?
>
>Boy, it's been awhile...
>
>I'm pretty sure that the SHOW directive worked for BRIDGE and LINE entities.
>I seem to recall REGISTER working as well...

    Vitalink changed some of their RBMS codes from 1 byte to 2 byte codes
    as of 6.9.7 of Translan software.... (This *includes* attributes from
    the IDENTIFIERS partition...)  

    So in a nutshell, it *used* to work, but it don't no mo. 

    If you want the new RBMS parameter codes, drop me a line...

>
>I don't have a Vitalink hanging around to test with.
>

	Drop by LKG anytime, CB!  ;^)

    /doug