To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | RE: [nv-l] Authentication Failure Trap Argument interpretation |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Thu, 23 Oct 2003 09:26:53 -0400 |
Delivery-date: | Thu, 23 Oct 2003 14:37:35 +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 |
That is exactly what I am saying. The tag they use determines how the variable will be processed. x'40' is the unique identifier for an IP address. x'04' is the unique identifier for a printable octet string. This is standard ASN.1 encoding. Any book on SNMP should confirm this. Sorry I misunderstood about the other tools, but the fact that all the tools agree that this is being sent as an octet string should confirm that it is incorrectly encoded. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
Well, if that's the trap hex, it just says "OCTET STRING" (x04) and not "IP ADDRESS" (x40) 04 04 a2 83 26 3d means "octet string of 4 bytes" with that data. We would expect an IP Address to be 40 04 a2 83 26 3d I cannot answer why your other tools seem to know that this is meant as an IP Address. That's not what it says. [Treptow, Craig] I don't think I made myself clear. None of the tools interpret it as an IP address. Are you saying then that Cisco should be sending this argument with a type of x40, instead of x04? |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Fw: [nv-l] NV 7.1.4 and TEC forwarding / Correlation Gateway, Christopher Haynes |
---|---|
Next by Date: | Re: [nv-l] netview server, James Shanks |
Previous by Thread: | RE: [nv-l] Authentication Failure Trap Argument interpretation, Treptow, Craig |
Next by Thread: | RE: [nv-l] Authentication Failure Trap Argument interpretation, Treptow, Craig |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web