Conference azur::mcc

1373.0. "Cannot register SNMP agent" by CSC32::WOESTEMEYER (Why??...Why not!!!) Wed Aug 21 1991 17:07

Having problems registering an SNMP node, node is DECserver 300 V2.1 field
field test software, this software has an SNMP agent.

A Transpath 350 is included as an example. Note both entities, TP350-1 and
NSU301 are in the UCX host table and UCX loop works to both devices.  The
Transpath can be registered, but the DECserver cannot be.

Whats even stranger the Decserver can be accessed via SNMP if the IP address
is used. Why can't it be registered?

DECmcc V1.1

MCC> sh mcc 0 tcpip_am all char

MCC 0 TCPIP_AM
AT 21-AUG-1991 14:03:39 Characteristics

Examination of attributes shows:
                      Component Version = T1.1.0
               Component Identification = "DECmcc TCP/IP SNMP AM"
                            UDP Timeout = 5
                            UDP Retries = 2

-------------------------------------------------------------------------
$ ucx show host
       
     LOCAL database
  
Host address    Host name
 
16.63.16.5      BOULDR, bouldr
16.63.0.52      BRISA, brisa
16.63.0.50      HOLSTN, holstn
127.0.0.1       LOCALHOST, localhost
16.63.0.203     NSU-CONS-1, nsu-cons-1
16.63.0.204     NSU-CONS-2, nsu-cons-2
16.63.0.205     NSU-LB500-1, nsu-lb500-1
16.63.0.206     NSU-LB500-2, nsu-lb500-2
16.63.0.32      NSU301, nsu301
16.63.0.201     TP350-1, tp350-1
16.63.0.202     TP350-2, tp350-2
16.63.16.193    TP530-1, tp530-1
16.63.16.129    TP550-1, tp550-1
16.63.0.14      coors
16.63.0.27      keroon, KEROON
16.63.0.2       tsc

$ ucx loop tp350-1
%UCX-I-LOOPACT, TP350-1 is alive

$ ucx loop nsu301
%UCX-I-LOOPACT, NSU301 is alive

$ manage/enter
DECmcc (V1.1.0)

MCC> register snmp tp350-1
SNMP tp350-1 
AT 21-AUG-1991 13:54:48 
Registration Successful

MCC> register snmp nsu301
SNMP nsu301 
AT 21-AUG-1991 13:55:11 
The requested operation cannot be completed
                      MCC Routine Error = %MCC-E-INCONSISTENTCLA, specified 
                                          class is inconsistent with entity 
                                          class

MCC> show snmp 16.63.0.32 all char
SNMP 16.63.0.32 
AT 21-AUG-1991 13:55:38 Characteristics
Examination of attributes shows:
                               sysDescr = "DECserver 300 V2.1  BL21  ROM V1.0.5 
                                           LAT V5.1  LOAD IMAGE: SH21BL21"
                            sysObjectID = "1.3.6.1.4.1.36.2.15.5.1.2"
                               ifNumber = 17
                             sysContact = "                                "
                                sysName = "NSU301"
                            sysLocation = "                                "
                            sysServices = 79
MCC> exit
$

RE: .0

> MCC> register snmp nsu301
> SNMP nsu301
> AT 21-AUG-1991 13:55:11
> The requested operation cannot be completed
>                      MCC Routine Error = %MCC-E-INCONSISTENTCLA, specified
>                                          class is inconsistent with entity
>

It seems that you may have an object with DNS name '.nsu301' in your namespace.
(use the DNS$Control command to see if the object exists in the namespace: 
 	$ mcr dns$control show object .nsu301)

In MCC V1.1, the SNMP registration checks if the IP Name specified in the
command (e.g. nsu301) exists in the DNS namespace. If the name exists,
the registration fails and "MCC-E-INCONSISTENTCLA" is displayed. 

The reason for this name-conflict check is to eliminate the ambiguity in
determining domain members.  For example, when the following command is issued:
	MCC> create domain .foo mem nsu301

the member name ('nsu301') can be a Fullname or an IP Name in MCC V1.1.

By disallowing the registration of an SNMP object with IP name 'nsu301' when
an MCC entity with the fullname '.nsu301' is already registered, there is
no ambiguity in the above MCC command.

	Let me say it another way...

	Global Entity names (ie:nsu301) have to be unique.

	do the following...
	MCC> DIR NODE4 nsu301
	MCC> DIR NODE  nsu301
	MCC> DIR DOMAIN nsu301
	MCC> DIR BRIDGE nsu301
	MCC> DIR STATION nsu301
	MCC> DIR TRANSLAN nsu301
	MCC> DIR ICMP nsu301

	if any  other  class  has  an instance name of nsu301, there is
	your problem.

    Well nsu301 was indeed in DNS as an object, it was registered with the
    Terminal Server AM. I deregistered it as a terminal server and then was
    able to register it as a TCPIP entity.
    
    Sure wish the error message was clearer, I know we at the center will
    see alot of calls on this kind of problem.  
    
    Thanks for the quick answer.
    

    In DECmcc V1.2, if you try to register an entity with a name which is
    already registered with an entity of another class (just like your
    case), the following message will be returned (instead of
    INCONSISTENTCLA):
    
    	The registration name is already used by another entity class.
    
    
    Ed