nv-l
[Top] [All Lists]

RE: [nv-l] Authentication Failure Trap Argument interpretation

To: <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] Authentication Failure Trap Argument interpretation
From: "Treptow, Craig" <Treptow.Craig@principal.com>
Date: Thu, 23 Oct 2003 12:21:07 -0500
Delivery-date: Thu, 23 Oct 2003 18:33:12 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l-digest@lists.us.ibm.com
Thread-index: AcOZcuVDkCXszjvnQe+Ptbnnhk2L/AAFrspQ
Thread-topic: [nv-l] Authentication Failure Trap Argument interpretation
So this implies that sniffer, ethereal, and Netview have not been updated to 
handle this new way of sending an IP address?  If so, then I guess it's time to 
see the release notes for 7.1.4 to see if something like this has been 
addressed.


>-----Original Message-----
>From: Joe Fernandez [mailto:jfernand@kardinia.com]
>Sent: Thursday, October 23, 2003 9:30 AM
>To: nv-l@lists.us.ibm.com
>Subject: Re: [nv-l] Authentication Failure Trap Argument interpretation
>
>
>James,
>
>The two objects that Craig lists are from the Cisco System MIB.
>
>1.3.6.1.4.1.9.9.131.1.5.2.0 = csySnmpAuthFailAddressType
>Syntax=netAddressType
>
>1.3.6.1.4.1.9.9.131.1.5.3.0 = csySnmpAuthFailAddress
>Syntax=InetAddress
>
>The MIB imports these Textual Conventions from INET-ADDRESS-MIB
>
>If I read INET-ADDRESS-MIB correctly, the IETF is telling MIB 
>designers to
>stop
>using the old IpAddress syntax because it does not cater for 
>IPv6, and start
>using these Textual Conventions to allow for both IP v4 and v6. 
>
>And the way to use them is to have two objects, the first 
>defining the type of
>address (v4,v6,..), the second with the actual address.
>The first value below is 1 which is the enumeration for IPv4 if
>Syntax=netAddressType.
>The syntax of InetAddress is defined as just Octet String, so 
>that is why
>it is
>encoded that way.
> 


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web