WILL NETVIEW/6000 LOOK AT THE ADDRESS IN THE PDU

ITEM: RTA000028767



QUESTION:                                                                       
We have a (Internally written) SNMP Proxy agent on a SUN                        
workstation. This proxy monitors network devices and sends traps to             
the network management station. They have had problems (needed coding)          
with other net management systems where the trap would be sent from             
proxy to the Net Management System and the Proxy would turn red (not the        
device with the problem). The cause has to do with the IP header source         
field containing the Proxy address (not the agent address). The PDU in          
the SNMP record DOES contain the problem agent address. My question is          
if we set this same scenario up with Netview/6000, what should we expect        
to happen? If the SUN Proxy turns RED (incorrectly), can you tell me            
if there is any way for us to (without coding) cause Netview/6000 to get        
the address from the PDU record? I vaguely remember that we support             
proxy agents, but do those proxy agents have the ability to report traps        
to another Netview? If yes, which Netview/6000 supports this (ie, the          
currently available one or the recently announced/enhanced Netview?)            
                                                                                
---------- ---------- ---------- --------- ---------- ----------                
A: In NV/6000, all traps, requests and responses are transmitted in the         
   form of ASN.1 messages.  The structure of the message is defined by          
   RFC 1157 and is structured as follows: Version Community PDU .  The          
   PDU contains the SNMP request, response or trap data.  The PDU and           
   the message MUST BE encoded according to the ASN.1 rules.  If they           
   are not encoded according to these rules, NV/6000 will not know what         
   to do with them.  The messages from the proxy agent you mention are          
   probably not adhering to the ASN.1 rules as required by NV/6000              
   versions 1 AND 2.                                                            
                                                                                
   So in answer to your question regarding additional coding, it sounds         
   like coding will be needed to interpret the proxy agent's messages and      
   PDU data.                                                                    
                                                                                
---------- ---------- ---------- --------- ---------- ----------                
                                                                                
                                                                                
This item was created from library item Q617928      BZKJT                      
                                                                                
Additional search words:                                                        
ADDR ADDRESS AGENT AIX ALTERNATE BZKJT COMMUNICATIO CORRECTLY FEB93             
INDEX IX LOOK NETVIEW NETVIEW6000 PDU PROXY REACT RISCNETV                      
RISCSYSTEM SENT SOFTWARE TRAP 6000                                              
                                                                                
                                                                                
                                                                                
                                                                               


WWQA: ITEM: RTA000028767 ITEM: RTA000028767
Dated: 09/1996 Category: RISCNETV
This HTML file was generated 99/06/24~12:43:11
Comments or suggestions? Contact us