Conference azur::mcc

4444.0. "SNMP TRAPS from Cisco NOT SEEN by DECmcc" by GIDDAY::STANISLAUS () Tue Jan 26 1993 01:34

    
    
    	I have a problem in a network with DECmcc and Cisco Routers.
    	DECmcc is running 1.2.3 and the Cisco Routers are running 8.3.58
    	There are around 30 routers in the network all running the same
    	software version. Some are AGS+, some CGS and some IGS routers.
    
    	The problem is that the SNMP traps from some routers are not seen
    	by the DECmcc station. So some routers' traps ae seen and some are
    	not sen by the DECmcc station. About 4 or five Routers' traps are 
    	seen and the remaining 20 odd routers' traps are not seen by
    	DECmcc. The interseting thing is the 4 or 5 routers whose traps
    	are seen now by DECmcc are not seen by DECmcc the next day or after
    	a few hours.
    
    	There is no pattern such as IGS or CGS or AGS+ routers' whose traps
    	are not seen. There are no bridges in the path that are doing any
    	filtering. 
    
    	I traced the packets from one router whose trap is seen and the
    	packets from one router whose traps are not seen by DECmcc. The
    	IP address of the one whose traps are seen is 161.117.120.254
    	and the one whose traps are not seen by DECmcc is 161.117.248.2
    
    	The traces are in the DEFAULT DECNET DIRECTORY of a node called
    	RIPPER and the file name is TELECOM.LIS
    
    	Any suggestions please
    
    	Any suggestions please
    	Any suggestions please.

    I have the same problem with one AGS+ and 23 IGS/R routers.  They are
    all running 9.0(1.10).  The routers are configured for the following:
    snmp-server community public RW
    snmp-server trap-authentication
    snmp-server host 159.13.96.6 public snmp tty (address of DECmcc)
    
    The network is running DECnet and TCP/IP over a private X.25 network.
    
    Reece Boucher
    SWS 
    Adelaide, Australia

	It is possible that the encoding of the trap PDU is such that
	the SNMP AM is rejecting them as bad PDUs. This seems more likely
	when you consider the fact that this seems to happen only for traps
	generated by a particular agent only.

	You can find out if the traps were accepted by the SNMP AM's 
	event sink by issuing the following command :

	MCC> SHOW MCC 0 TCPIP_AM SINK ALL COUNTERS

	This will give you a count of the traps received and their types.
	If you see the count going up, but the events not appearing in
	DECmcc, then this could be a different (and more serious) problem.

	Could you also send me an ASN.1 dump of the trap PDU so that I 
	may figure out if it is following the SNMP protocol.

	Rahul.

	This fault turned out to be due to the fact that all agents where 
registered with their IP address of the Ethernet Port. Once we registered the
IP address of the serial port it was all OK. We found this by tracing the data
with the LANanalyzer.

Alphonse