RE: MIB format

Hi

I think that in :

.1.3.6.1.4.1.9.9.187.1.2.5.1.17.32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2=04 00

04 00 is the Error code and Error subcode (https://tools.ietf.org/html/rfc4271#page-21)

NOT 32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2

So the error 04 = Hold time expired
Subcode 02 = bad message length.

Please: OID should not be confused with returned value

32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2
Provides information about the route that was updated while the error occurred: looks like RD (route distinguisher + route + netmask+ ???)

Best Regards

JM


De : Fulko Hew [mailto:[email protected]]
Envoyé : mercredi, 18. mai 2016 16:55
À : andrewarnier <[email protected]>
Cc : [email protected]
Objet : Re: MIB format



On Wed, May 18, 2016 at 10:01 AM, andrewarnier <[email protected]<mailto:[email protected]>> wrote:
> Hi all,
>
> Tue May 17 23:59:43 2016: Unknown trap (.1.3.6.1.4.1.9.9.187.0.8) received
> from CISCOASR at:
>
> Value 0: CISCOASR
> Value 1: 10.10.1.2
> Value 2: 386:3:31:07.03
> Value 3: .1.3.6.1.4.1.9.9.187.0.8
> Value 4: 10.10.1.2
> Value 5: public
> Value 6: .1.3.6.1.4.1.9.9.187
> Value 7:
> Value 8:
> Value 9:
> Value 10:
> Ent Value 0: .1.3.6.1.4.1.9.9.187.1.2.5.1.17.32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2=04 00
> Ent Value 1: .1.3.6.1.4.1.9.9.187.1.2.5.1.3.32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2=1
> Ent Value 2: .1.3.6.1.4.1.9.9.187.1.2.5.1.28.32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2=hold time expired
> Ent Value 3: .1.3.6.1.4.1.9.9.187.1.2.5.1.29.32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2=3
>
> I think the trap is about CISCO-BGP4-MIB
>
> For example ,
>
> As you can see part of the
> OID(1.3.6.1.4.1.9.9.187.1.2.5.1.28.32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2)
> can be translated into cbgpPeer2LastError
>
> What's the string (32.1.14.16.255.255.17.0.0.0.0.0.0.0.0.2) meaning?

This trap is the 'cbgpPeer2BackwardTransition' trap, and provides the following 4 variables:
cbgpPeer2LastError, cbgpPeer2State, cbgpPeer2LastErrorTxt, cbgpPeer2PrevState

Each variable's OID is defined by its base OID and its index.
In the case of these variables, they are part of a table that is indexed by:

cbgpPeer2Type, cbgpPeer2RemoteAddr

cbgpPeer2Type
​      ​
is defined as an INTEGER
cbgpPeer2RemoteAddr is defined as an InetAddress
​                    which ​
is ultimately defined as an OCTET STRING (SIZE (0..255))

so:

32 - is the
​​
​​
​'​
cbgpPeer2Type
​'​
​​
and probably tells you the exact format of the value of cbgpPeer2RemoteAddr
      (unfortunately the version of that MIB file I have doesn't have the value of 32 defined.
      Obviously they have updated that MIB since I got my copy)

1.14.16.255.255.17.0.0.0.0.0.0.0.0.2 - is the
​value of ​
cbgpPeer2RemoteAddr

And this was all defined in their 'CISCO-BGP4-MIB-V1SMI' MIB.

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users