Subject: tewg-mib revision 3

From: "Wijnen, Bert (Bert)" <[email-masked]>
Date: Mon, 3 Feb 2003 14:54:04 +0100

I should do an AD or MIB-doctor review of this MIB again
I think. But for now, I see things like:

   tePathTunnelIndex OBJECT-TYPE
       SYNTAX     Unsigned32
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
           "An index that identifies the Tunnel to which this path
            belongs.  A Tunnel Path index MUST NOT be zero."
       ::= { tePathEntry 1 }

   tePathIndex OBJECT-TYPE
       SYNTAX     Unsigned32
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
           "An index that uniquely identifies a path within a Tunnel.
            The combination of <tePathTunnelIndex, tePathIndex> thus
            uniquely identifies a path among all paths on this router.
            This index MUST NOT be zero."
       ::= { tePathEntry 2 }

The way to specify that an INDEX (or actually any object) MUST NOT
be zero is with a range, as follows:

   tePathTunnelIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
           "An index that identifies the Tunnel to which this path
            belongs."
       ::= { tePathEntry 1 }

   tePathIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
           "An index that uniquely identifies a path within a Tunnel.
            The combination of <tePathTunnelIndex, tePathIndex> thus
            uniquely identifies a path among all paths on this router."
       ::= { tePathEntry 2 }

That way, it is programmatically parsable too!

Thanks,
Bert