[j-nsp] ERX Mibs Question
Jeronimo Diez de Sollano Velazco Aceves
jdiez at bestel.com.mx
Fri May 30 16:57:36 EDT 2003
Aviva.... or someone else
Thank you very much for the answer, i thought that the bits in/out MIB was
standard. Do you know if future releases of the ERX will have this MIB
deployed?
The solution you propose of multiply by 8 is not so accurate because the
sampling of an octet is different than the bit sampling.
Do you have (or know where can i get)the object ID tree for the IF-MIB (RFC
2863)??? The information i got from Juniper.net is not very legible, i´m
having troubles to get the last positions of the object id's.
Thanyou again. You have been very helpful.
Best Regards
Jeronimo
-----Original Message-----
From: Aviva Garrett [mailto:aviva at juniper.net]
Sent: Viernes, 30 de Mayo de 2003 02:31 p.m.
To: Jeronimo Diez de Sollano Velazco Aceves
Cc: 'juniper-nsp at puck.nether.net'; aviva at juniper.net
Subject: Re: [j-nsp] ERX Mibs Question
Hi Jeronimo,
Here's the answer from the ERX engineering group:
: We are sorry, but there are no SNMP objects that provide the count of
: bits in/out on the ERX.
: We use the IETF standard IF-MIB (RFC 2863) to count interface octets
: in/out.
: There are 8 bits to an octet, so you can multiple the octet counts by 8
: to get the number of bits.
: The counters you want to look at are:
: ifInOctets OBJECT-TYPE
: SYNTAX Counter32
: MAX-ACCESS read-only
: STATUS current
: DESCRIPTION
: "The total number of octets received on the interface,
: including framing characters.
:
: Discontinuities in the value of this counter can occur
: at re-initialization of the management system, and at
: other times as indicated by the value of
: ifCounterDiscontinuityTime."
: ::= { ifEntry 10 }
:
: ifOutOctets OBJECT-TYPE
: SYNTAX Counter32
: MAX-ACCESS read-only
: STATUS current
: DESCRIPTION
: "The total number of octets transmitted out of the
: interface, including framing characters.
:
: Discontinuities in the value of this counter can occur
: at re-initialization of the management system, and at
: other times as indicated by the value of
: ifCounterDiscontinuityTime."
: ::= { ifEntry 16 }
:
: As for discarded bits, that is a little more difficult, since those
: IF-MIB counters are in terms of packets and not octets.
: Since on some interface types the number of octets in a packet is
: variable, there really is no way to tell how many bits are discarded.
: The IF-MIB objects are:
: ifInDiscards OBJECT-TYPE
: SYNTAX Counter32
: MAX-ACCESS read-only
: STATUS current
: DESCRIPTION
: "The number of inbound packets which were chosen to be
: discarded even though no errors had been detected to
: prevent their being deliverable to a higher-layer
: protocol. One possible reason for discarding such a
: packet could be to free up buffer space.
:
: Discontinuities in the value of this counter can occur
: at re-initialization of the management system, and at
: other times as indicated by the value of
: ifCounterDiscontinuityTime."
: ::= { ifEntry 13 }
:
: ifOutDiscards OBJECT-TYPE
: SYNTAX Counter32
: MAX-ACCESS read-only
: STATUS current
: DESCRIPTION
: "The number of outbound packets which were chosen to
: be discarded even though no errors had been detected
: to prevent their being transmitted. One possible
: reason for discarding such a packet could be to free
: up buffer space.
:
: Discontinuities in the value of this counter can occur
: at re-initialization of the management system, and at
: other times as indicated by the value of
: ifCounterDiscontinuityTime."
: ::= { ifEntry 19 }
:
: You may want to reconsider what you are trying to use this information
: for and come up with a way to use the standard counters.
Thanks,
..Aviva
More information about the juniper-nsp
mailing list