[tkined] Re: illegal length of instance identifier

From: Tim Westbrook (iondiode@yahoo.com)
Date: Thu Oct 26 2000 - 17:06:52 MET DST


Hello

More background :
This error occurs when I use the TnmSnmp::Table
command to create an array from the pnniMapAddrTable.

I have included relevent type defintitions and the mib
table definition as well as the oid that caused the
error.

Relevent (hopefully) Mib Definitions

-- Index Types

PnniNodeId ::= OCTET STRING (SIZE(22))
PnniPortId ::= Unsigned32
AtmAddrPrefix ::= OCTET STRING (SIZE(19))
PnniPrefixLength ::= INTEGER (0..152)

-- address map table

pnniMapAddrTable OBJECT-TYPE
        SYNTAX SEQUENCE OF PnniMapAddrEntry
        ACCESS not-accessible
        STATUS mandatory
        DESCRIPTION
            "The pnniMapAddr MIB Object contains a
list of all reachable
             addresses from each node visible to the
local node. The
             Local Node Index, Advertising Node ID,
Advertised Port ID,
             Reachable Address, and Address prefix
length are combined
             to form an instance ID for this object.
The entire object
             is read-only, reflecting the fact that
reachable addresses
             are discovered during dynamic operation
of the PNNI
             protocol rather than configured."
        ::= { pnniMIBObjects 16 }

pnniMapAddrEntry OBJECT-TYPE
        SYNTAX PnniMapAddrEntry
        ACCESS not-accessible
        STATUS mandatory
        DESCRIPTION
            "An entry in the table, containing
information about an
             address prefix reachable from a node in
the PNNI routing
             domain, as seen from the perspective of a
PNNI logical node
             in this switching system."
        INDEX { pnniNodeIndex,
                        pnniMapAddrAdvertisingNodeId,
                        pnniMapAddrAdvertisedPortId,
                        pnniMapAddrIndex }
        ::= { pnniMapAddrTable 1 }

PnniMapAddrEntry ::=
        SEQUENCE {
                pnniMapAddrAdvertisingNodeId
PnniNodeId,
                pnniMapAddrAdvertisedPortId
PnniPortId,
                pnniMapAddrIndex
INTEGER,
                pnniMapAddrAddress
AtmAddrPrefix,
                pnniMapAddrPrefixLength
PnniPrefixLength
                }

pnniMapAddrAdvertisingNodeId OBJECT-TYPE
        SYNTAX PnniNodeId
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "The node ID of a node advertising
reachability to the
             address prefix."
        ::= { pnniMapAddrEntry 1 }

pnniMapAddrAdvertisedPortId OBJECT-TYPE
        SYNTAX PnniPortId
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "The port identifier used from the
advertising node to reach
             the given address prefix."
        ::= { pnniMapAddrEntry 2 }

pnniMapAddrIndex OBJECT-TYPE
        SYNTAX INTEGER (1..2147483647)
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "An arbitrary index that is used to
enumerate all of the
             addresses advertised by the specified
node."
        ::= { pnniMapAddrEntry 3 }

pnniMapAddrAddress OBJECT-TYPE
        SYNTAX AtmAddrPrefix
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "The value of the ATM End System Address
prefix."
        ::= { pnniMapAddrEntry 4 }

pnniMapAddrPrefixLength OBJECT-TYPE
        SYNTAX PnniPrefixLength
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "The Prefix length to be applied to the
ATM End System
             Address prefix."
        ::= { pnniMapAddrEntry 5 }

Command -
% Tnm::mib unpack
1.3.6.1.4.1.353.5.4.1.1.16.1.1.1.96.160.57.132.15.128.1.188.114.0.1.42.202.153.0.255.42.202.153.0.0.0.36610.34
illegal length of the instance identifier

--- Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
wrote:
>
> >>>>> Tim Westbrook writes:
>
> Tim> I am using Tnm3.0.0 , and when I unpack some
> OIDs I get an
> Tim> 'illegal length of instance identifier'. These
> mib objects use an
> Tim> ATM address prefix (19 bytes) as one of its
> index values.
>
> Tim> Is there anything I can do to fix this easily.
> I can still get
> Tim> the values , I just won't be able to use all of
> the cool TnmSnmp
> Tim> tools.
>
> Please post the OIDs you are trying to unpack plus
> the relevant MIB
> definitions so that we can determine whether the bug
> is in scotty or
> whether the OIDs are indeed illegal.
>
> /js

__________________________________________________
Do You Yahoo!?
Yahoo! Messenger - Talk while you surf! It's FREE.
http://im.yahoo.com/

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.



This archive was generated by hypermail 2b29 : Mon Jan 08 2001 - 15:27:55 MET