| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 4269.1 |  | 2582::YAHEY::BOSE |  | Thu Dec 17 1992 10:11 | 7 | 
|  | 
	You need to re-register the SNMP entities in question. The entities
	need to be fully registered and accessible via SNMP. The release notes
	for T1.3 spell out a procedure which will allow you to re-register
	all the entities automatically.
	Rahul.
 | 
| 4269.2 | Same behaviour after re-register | GOYA::MERINO | Angel Garc�a - NSC Madrid Spain | Fri Dec 18 1992 08:02 | 8 | 
|  |     I re-registered the snmp entities and the behaviour is the same. I used
    the environment variable setenv MCC_REGISTRATION_FM_LOG 0x01000000.
    I am using the ULTRIX version.
    
    Any other idea?
    
    Thanks,
        Angel.
 | 
| 4269.3 |  | 2582::YAHEY::BOSE |  | Fri Dec 18 1992 09:41 | 4 | 
|  | 
	Is the entity fully registered ? (Do a MCC> DIR SNMP full_name
	to find out). Also, did you have SNMP read access to the entity
	from your DECmcc station at the time of registration?
 | 
| 4269.4 | Entity fully registered and accessible. | GOYA::MERINO | Angel Garc�a - NSC Madrid Spain | Mon Dec 21 1992 08:24 | 52 | 
|  |     Yes, the entity is fully registered.
    
    MCC> dire snmp .es.cica.cisca1
    
    SNMP PIVE:.es.cica.cisca1
    AT 1992-12-21-14:15:34.388
    
    Directory successful.
                            Registered Name = PIVE:.es.cica.cisca1
                                    Address = 150.214.4.30
                                       Name = cisca1.cica.es
    
    I had SNMP read access to the entity from the DECmcc station at
    registration time. The SNMP entity has configured the 'public'
    community for read access.
    
    MCC> show mcc 0 tcpip_am all attr
    
    MCC 0 TCPIP_AM
    AT 1992-12-21-14:19:11.858 All Attributes
    
                          Component Version = T1.3.0
                   Component Identification = "DECmcc TCP/IP SNMP AM"
                                UDP Timeout = 5
                                UDP Retries = 2
                               ICMP Timeout = 5
                               ICMP Retries = 2
                   Mib Extensions Available = ( "rmon",
                                                "EXP_RMON",
                                                "cisco" )
    
    I can do the following command from the FCL but I cannot do it from the
    IMPM. The 'cisco' attributes partition does not appear in the IMPM.
    
    MCC> show snmp cisca1.cica.es cisco temporary decnet dnarea 54 all attr
    
    SNMP cisca1.cica.es cisco temporary decnet dnAreaTable 54
    AT 1992-12-21-14:20:55.883 All Attributes
    
                                     dnArea = 54
                                    dnACost = 0
                                     dnAHop = 0
                                 dnAIfIndex = 0
                                 dnANextHop = %X0000
                                     dnAAge = 0
                                    dnAPrio = 0
    MCC>
    
    Any ideas?
    
    Again many thanks for answers,
    Angel.
 | 
| 4269.5 |  | 2582::YAHEY::BOSE |  | Mon Dec 21 1992 10:35 | 5 | 
|  | 
	Can you re-register the entity in question and see if you still
	don't get the cisco child entity on the map?
	Rahul.
 | 
| 4269.6 |  | GOYA::MERINO | Angel Garc�a - NSC Madrid Spain | Tue Dec 22 1992 13:13 | 6 | 
|  |     I cannot re-register the entity because I am not in customer site. But
    I did it before and the cisco child entity did not appear on the map.
    
    The ULTRIX version is V4.3.
    
    Angel.
 | 
| 4269.7 |  | 2582::YAHEY::BOSE |  | Wed Dec 23 1992 10:45 | 17 | 
|  | 
	There are two conditions that must be fulfilled for the child enterprise
	entity to appear on the map. 
	o The entity must be fully registered (ie. both the IP name
	  and address must be present. This will change with the field
	  test update kit.)
	o During registration, a successful GetNext operation can be done
	  on the mib extension implemented by the agent. That is how the
	  SNMP AM figures out which mib extensions are supported by the 
	  agent.
	If you are sure that both the conditions are fulfilled, then file
	a QAR against the SNMP AM.
	Rahul.
 |