JNX-MPLS-TE-P2MP-STD-MIB
Updated Apr 17, 2009Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html
This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in:
1. Signaling Requirements for Point-to-Multipoint
Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006.
2. Extensions to Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007.
Main OID:
jnxMplsTeP2mpStdMIB.jnxP2mpExperiment.1
56
Objects
Active
Status
9
Dependencies
Imported Objects
Objects
56 total| Object Name |
|---|
jnxMplsTeP2mpStdMIBCopyright (c) 2009 IETF Trust and the persons identified as
the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's
Legal Provisions Relating to IETF Documents in effect on the
date of publication of this document
(http://trustee.ietf.org/license-info). Please review these
documents carefully, as they describe your rights and
restrictions with respect to this document.
The initial version of this MIB module was published in
RFC XXXX. For full legal notices see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html
This MIB module contains managed object definitions
for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE)
defined in:
1. Signaling Requirements for Point-to-Multipoint
Traffic-Engineered MPLS Label Switched Paths (LSPs),
S. Yasukawa, RFC 4461, April 2006.
2. Extensions to Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) for Point-to-Multipoint TE Label
Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D.,
and Yasukawa, S., RFC 4875, May 2007. MODULE-IDENTITY .jnxP2mpExperiment.1 |
jnxMplsTeP2mpNotifications OBJECT IDENTIFIER .jnxP2mpExperiment.1.0 |
jnxMplsTeP2mpTunnelDestUpThis notification is generated when a
mplsTeP2mpTunnelDestOperStatus object for one of the
destinations of one of the configured tunnels is about to
leave the down(2) state and transition into some other
state. This other state is indicated by the included value
of mplsTeP2mpTunnelDestOperStatus.
This reporting of state transitions mirrors mplsTunnelUp. NOTIFICATION-TYPE .jnxP2mpExperiment.1.0.1 |
jnxMplsTeP2mpTunnelDestDownThis notification is generated when a
mplsTeP2mpTunnelDestOperStatus object for one of the
destinations of one of the configured tunnels is about to
enter the down(2) state from some other state. This other
state is indicated by the included value of
mplsTeP2mpTunnelDestOperStatus.
This reporting of state transitions mirrors mplsTunnelDown. NOTIFICATION-TYPE .jnxP2mpExperiment.1.0.2 |
jnxMplsTeP2mpScalars OBJECT IDENTIFIER .jnxP2mpExperiment.1.1 |
jnxMplsTeP2mpTunnelConfiguredThe number of P2MP tunnels configured on this device. A
tunnel is considered configured if the mplsTunnelRowStatus
in MPLS-TE-STD-MIB is active(1).ro Unsigned32 .jnxP2mpExperiment.1.1.1 |
jnxMplsTeP2mpTunnelActiveThe number of P2MP tunnels active on this device. A
tunnel is considered active if the mplsTunnelOperStatus
in MPLS-TE-STD-MIB is up(1).ro Unsigned32 .jnxP2mpExperiment.1.1.2 |
jnxMplsTeP2mpTunnelTotalMaxHopsThe maximum number of hops that can be specified for an
entire P2MP tunnel on this device. This object should be
used in conjunction with mplsTunnelMaxHops in
MPLS-TE-STD-MIB that is used in the context of P2MP tunnels
to express the maximum number of hops to any individual
destination of a P2MP tunnel that can be configured on this
device. mplsTeP2mpTunnelTotalMaxHops would normally be set
larger than or equal to mplsTunnelMaxHops.ro Unsigned32 .jnxP2mpExperiment.1.1.3 |
jnxMplsTeP2mpObjects OBJECT IDENTIFIER .jnxP2mpExperiment.1.2 |
jnxMplsTeP2mpTunnelTableThe mplsTeP2mpTunnelTable allows new P2MP MPLS tunnels to be
created between an LSR and one or more remote end-points,
and existing P2MP tunnels to be reconfigured or removed.
This table sparse augments mplsTunnelTable in
MPLS-TE-STD-MIB such that entries in that table can be
flagged as point-to-multipoint, and can be configured and
monitored appropriately. SEQUENCE OF JnxMplsTeP2mpTunnelEntry .jnxP2mpExperiment.1.2.1 |
jnxMplsTeP2mpTunnelEntryAn entry in this table represents a P2MP MPLS tunnel.
An entry can be created by a network administrator or by an
SNMP agent as instructed by an MPLS signaling protocol.
An entry in this table MUST correspond to an entry in the
mplsTunnelTable in MPLS-TE-STD-MIB. This table shares index
objects with that table and sparse augments that table.
Thus, an entry in this table can only be created at the same
time as or after a corresponding entry in mplsTunnelTable,
and an entry in mplsTunnelTable cannot be deleted while a
corresponding entry exists in this table.
This table entry includes a row status object, but
administrative and operational statuses should be taken from
mplsTunnelAdminStatus and mplsTunnelOperStatus in the
corresponding entry in mplsTunnelTable. JnxMplsTeP2mpTunnelEntry .jnxP2mpExperiment.1.2.1.1 |
jnxMplsTeP2mpTunnelP2mpIntegrityDenotes whether or not P2MP Integrity is required for this
tunnel.
If P2MP integrity is operational on a P2MP tunnel then the
failure of the path to any of the tunnel destinations should
cause the teardown of the entire P2MP tunnel.rw TruthValue (SNMPv2-TC) .jnxP2mpExperiment.1.2.1.1.2 |
jnxMplsTeP2mpTunnelBranchRoleThis value supplements the value in the object
mplsTunnelRole in MPLS-TE-STD-MIB that indicates the role
of this LSR in the tunnel represented by this entry in
mplsTeP2mpTunnelTable.
mplsTunnelRole may take any of the values:
head(1),
transit(2),
tail(3),
headTail(4)
If this LSR is an ingress and there is exactly one
out-segment, mplsTunnelRole should contain the value
head(1), and mplsTeP2mpTunnelBranchRole should have the
value notBranch(1).
If this LSR is an ingress with more than one out segment,
mplsTunnelRole should contain the value head(1), and
mplsTeP2mpTunnelBranchRole should have the value branch(2).
If this LSR is an ingress, an egress, and there is one or
more out-segments, mplsTunnelRole should contain the value
headTail(4), and mplsTeP2mpTunnelBranchRole should have the
value bud(3).
If this LSR is a transit with exactly one out-segment,
mplsTunnelRole should contain the value transit(2), and
mplsTeP2mpTunnelBranchRole should have the value
notBranch(1).
If this LSR is a transit with more than one out-segment,
mplsTunnelRole should contain the value transit(2), and
mplsTeP2mpTunnelBranchRole should have the value branch(2).
If this LSR is a transit with one or more out-segments and
is also an egress, mplsTunnelRole should contain the value
transit(2), and mplsTeP2mpTunnelBranchRole should have the
value bud(3).
If this LSR is an egress with no out-segment and is not the
ingress, mplsTunnelRole should contain the value tail(3),
and mplsTeP2mpTunnelBranchRole should have the value
notBranch(1).
If this LSR is an egress and has one or more out-segments,
mplsTunnelRole should contain the value transit(1), and
mplsTeP2mpTunnelBranchRole should have the value bud(3).rw Enumeration .jnxP2mpExperiment.1.2.1.1.3 |
jnxMplsTeP2mpTunnelP2mpXcIndexThis object contains the value of mplsXCIndex, the primary
index of the mplsXCTable for all cross-connect entries for
this P2MP LSP.
If no XC entries have been created yet, this object must
return zero.
The set of entries in the mplsXCTable for this P2MP LSP can
be walked by reading Get-or-GetNext starting with the three
indexes to mplsXCTable set as:
mplsXCIndex = the value of this object
mplsXCInSegmentIndex = 0x0
mplsXCOutSegmentIndex = 0x0ro MplsIndexType (MPLS-LSR-STD-MIB) .jnxP2mpExperiment.1.2.1.1.4 |
jnxMplsTeP2mpTunnelRowStatusThis variable is used to create, modify, and/or delete a row
in this table. When a row in this table is in active(1)
state, no objects in that row can be modified by the agent
except mplsTeP2mpTunnelRowStatus and
mplsTeP2mpTunnelStorageType.
This object and mplsTunnelRowStatus in the corresponding
entry in mplsTunnelTable in MPLS-TE-STD-MIB should be
managed together. No objects in a row in this table can be
modified when the mplsTunnelRowStatus object in the
corresponding row in mplsTunnelTable has value active(1).
Note that no admin or oper status objects are provided in
this table. The administrative and operational status of
P2MP tunnels is taken from the values of
mplsTunnelAdminStatus and mplsTunnelOperStatus in the
corresponding row mplsTunnelTable.rw RowStatus (SNMPv2-TC) .jnxP2mpExperiment.1.2.1.1.5 |
jnxMplsTeP2mpTunnelStorageTypeThe storage type for this tunnel entry.
Conceptual rows having the value 'permanent' need not allow
write-access to any columnar objects in the row.rw StorageType (SNMPv2-TC) .jnxP2mpExperiment.1.2.1.1.6 |
jnxMplsTeP2mpTunnelSubGroupIDNextThis object contains an unused value for
mplsTeP2mpTunnelDestSubGroupID, or a zero to indicate that
none exists. Negative values are not allowed, as they do not
correspond to valid values of
mplsTeP2mpTunnelDestSubGroupID.
Note that this object offers an unused value for an
mplsTeP2mpTunnelDestSubGroupID value at the local LSR when
it is a sub-group originator. In other cases, the value of
mplsTeP2mpTunnelDestSubGroupID SHOULD be taken from the
received value signaled by the signaling protocol and
corresponds to the value in
mplsTeP2mpTunnelDestSrcSubGroupID.ro IndexIntegerNextFree .jnxP2mpExperiment.1.2.2 |
jnxMplsTeP2mpTunnelDestTableThe mplsTeP2mpTunnelDestTable allows new destinations of
P2MP MPLS tunnels to be added to and removed from P2MP
tunnels. SEQUENCE OF JnxMplsTeP2mpTunnelDestEntry .jnxP2mpExperiment.1.2.3 |
jnxMplsTeP2mpTunnelDestEntryAn entry in this table represents a destination of a P2MP
MPLS tunnel. An entry can be created by a network
administrator or by an SNMP agent as instructed by an MPLS
signaling protocol.
Entries in this table share some index fields with the
mplsTeP2mpTunnelTable and the mplsTunnelTable in
MPLS-TE-STD-MIB. Entries in this table have no meaning
unless there is a corresponding entry in
mplsTeP2mpTunnelTable (which, itself, depends on a
corresponding entry in mplsTunnelTable).
Note that the same destination may be present more than once
if it is in more than one sub-group as reflected by the
mplsTeP2mpTunnelDestSrcSubGroupOriginType,
mplsTeP2mpTunnelDestSrcSubGroupOrigin,
mplsTeP2mpTunnelDestSrcSubGroupID,
mplsTeP2mpTunnelDestSubGroupOriginType,
mplsTeP2mpTunnelDestSubGroupOrigin, and
mplsTeP2mpTunnelDestSubGroupID, index objects.
Entries in this table may be created at any time. If created
before an entry in the mplsTeP2mpTunnelTable the entries
have no meaning, but may be kept ready for the creation of
the P2MP tunnel. If created after the entry in
mplsTeP2mpTunnelTable, entries in this table may reflect the
addition of destinations to active P2MP tunnels. For this
reason, entries in this table are equipped with row, admin,
and oper status objects. JnxMplsTeP2mpTunnelDestEntry .jnxP2mpExperiment.1.2.3.1 |
jnxMplsTeP2mpTunnelDestSrcSubGroupOriginTypeThis object identifies the type of address carried in
mplsTeP2mpTunnelDestSrcSubGroupOrigin.
Since the object mplsTeP2mpTunnelDestSrcSubGroupOrigin must
conform to the protocol specification, this object must
return either ipv4(1) or ipv6(2) at a transit or egress LSR.
At an ingress LSR, there is no source sub-group and this
object should return the value unknown(0). InetAddressType (INET-ADDRESS-MIB) .jnxP2mpExperiment.1.2.3.1.1 |
jnxMplsTeP2mpTunnelDestSrcSubGroupOriginThe TE Router ID (reachable and stable IP address) of the
originator of the P2MP sub-group as received on a Path
message by a transit or egress LSR.
This object is interpreted in the context of
mplsTeP2mpTunnelDestSrcSubGroupOriginType.
The value of the sub-group originator used on outgoing Path
messages is found in mplsTeP2mpTunnelDestSubGroupOrigin and
is copied from this object unless this LSR is responsible
for changing the sub-group ID.
At an ingress LSR there is no received Path message.
mplsTeP2mpTunnelDestSrcSubGroupOriginType should return
unknown(0), and this object should return a zero-length
string. InetAddress .jnxP2mpExperiment.1.2.3.1.2 |
jnxMplsTeP2mpTunnelDestSrcSubGroupIDThe unique identifier assigned by the sub-group originator
for this sub-group of this P2MP tunnel as received on a Path
message by a transit or egress LSR.
The value of the sub-group identifier used on outgoing Path
messages is found in mplsTeP2mpTunnelDestSubGroupID and is
copied from this object unless this LSR is responsible for
changing the sub-group ID.
At an ingress LSR there is no received Path message, and
this object should return zero. IndexInteger .jnxP2mpExperiment.1.2.3.1.3 |
jnxMplsTeP2mpTunnelDestSubGroupOriginTypeThis object identifies the type of address carried in
mplsTeP2mpTunnelDestSubGroupOrigin.
This object must return either ipv4(1) or ipv6(2) in keeping
with the protocol specification. InetAddressType (INET-ADDRESS-MIB) .jnxP2mpExperiment.1.2.3.1.4 |
jnxMplsTeP2mpTunnelDestSubGroupOriginThe TE Router ID (reachable and stable IP address) of the
originator of the P2MP sub-group. In many cases, this will
be the ingress LSR of the P2MP tunnel and will be the
received signaled value as available in
mplsTeP2mpTunnelDestSrcSubGroupOrigin.
When a signaling protocol is used, this object corresponds
to the Sub-Group Originator field in the SENDER_TEMPLATE
object.
This object is interpreted in the context of
mplsTeP2mpTunnelDestSubGroupOriginType. InetAddress .jnxP2mpExperiment.1.2.3.1.5 |
jnxMplsTeP2mpTunnelDestSubGroupIDThe unique identifier assigned by the sub-group originator
for this sub-group of this P2MP tunnel.
An appropriate value for this object during row creation
when the sub-group origin in
mplsTeP2mpTunnelDestSubGroupOrigin is the local LSR can
be obtained by reading mplsTeP2mpTunnelSubGroupIDNext.
At an egress, there is no downstream sub-group ID. This
object should return the value received from upstream and
reported in mplsTeP2mpTunnelDestSrcSubGroupID. IndexInteger .jnxP2mpExperiment.1.2.3.1.6 |
jnxMplsTeP2mpTunnelDestDestinationTypeThis object identifies the type of address carried in
mplsTeP2mpTunnelDestDestination.
This object forms part of the index of this table and can,
therefore, not return the value unknown(0). Similarly, since
the object mplsTeP2mpTunnelDestDestination must conform to
the protocol specification, this object must return either
ipv4(1) or ipv6(2). InetAddressType (INET-ADDRESS-MIB) .jnxP2mpExperiment.1.2.3.1.7 |
jnxMplsTeP2mpTunnelDestDestinationA single destination of this P2MP tunnel. That is, a
routable TE address of a leaf. This will often be the TE
Router ID of the leaf, but can be any interface address.
When a signaling protocol is used, this object corresponds
to the S2L Sub-LSP destination address field in the
S2L_SUB_LSP object.
This object is interpreted in the context of
mplsTeP2mpTunnelDestDestinationType. InetAddress .jnxP2mpExperiment.1.2.3.1.8 |
jnxMplsTeP2mpTunnelDestBranchOutSegmentThis object identifies the outgoing branch from this LSR
towards the destination represented by this table entry. It
must be a unique identifier within the scope of this tunnel.
If MPLS-LSR-STD-MIB is implemented, this object should
contain an index into mplsOutSegmentTable.
If MPLS-LSR-STD-MIB is not implemented, the LSR should
assign a unique value to each branch of the tunnel.
The value of this object is also used as an index into
mplsTeP2mpTunnelBranchPerfTable.ro MplsIndexType (MPLS-LSR-STD-MIB) .jnxP2mpExperiment.1.2.3.1.9 |
jnxMplsTeP2mpTunnelDestHopTableIndexIndex into the mplsTunnelHopTable entry that specifies the
explicit route hops for this destination of the P2MP tunnel.
This object represents the configured route for the branch
of the P2MP tree to this destination and is meaningful only
at the head-end (ingress or root) of the P2MP tunnel. Note
that many such paths may be configured within the
mplsTunnelHopTable for each destination, and that the object
mplsTeP2mpTunnelDestPathInUse identifies which path has been
selected for use.rw MplsPathIndexOrZero (MPLS-TC-STD-MIB) .jnxP2mpExperiment.1.2.3.1.10 |
jnxMplsTeP2mpTunnelDestPathInUseThis value denotes the configured path that was chosen as
the explicit path to this destination of this P2MP tunnel.
This value reflects the secondary index into
mplsTunnelHopTable where the primary index comes from
mplsTeP2mpTunnelDestHopTableIndex.
The path indicated by this object might not exactly match
the one signaled and recorded in mplsTunnelCHopTable as
specific details of the path might be computed locally.
Similarly, the path might not match the actual path in use
as recorded in mplsTunnelARHopTable due to the fact that
some details of the path may have been resolved within the
network.
A value of zero denotes that no path is currently in use or
available.rw MplsPathIndexOrZero (MPLS-TC-STD-MIB) .jnxP2mpExperiment.1.2.3.1.11 |
jnxMplsTeP2mpTunnelDestCHopTableIndexIndex into the mplsTunnelCHopTable that identifies the
explicit path for this destination of the P2MP tunnel.
This path is based on the chosen configured path identified
by mplsTeP2mpTunnelDestHopTableIndex and
mplsTeP2mpTunnelDestPathInUse, but may have been modified
and automatically updated by the agent when computed hops
become available or when computed hops get modified.
If this destination is the destination of the 'first S2L
sub-LSP' then this path will be signaled in the Explicit
Route Object. If this destination is the destination of a
'subsequent S2L sub-LSP' then this path will be signaled in
a Secondary Explicit Route Object.ro MplsPathIndexOrZero (MPLS-TC-STD-MIB) .jnxP2mpExperiment.1.2.3.1.12 |
jnxMplsTeP2mpTunnelDestARHopTableIndexIndex into the mplsTunnelARHopTable that identifies the
actual hops traversed to this destination of the P2MP
tunnel. This is automatically updated by the agent when the
actual hops becomes available.
If this destination is the destination of the 'first S2L
sub-LSP' then this path will be signaled in the Recorded
Route Object. If this destination is the destination of a
'subsequent S2L sub-LSP' then this path will be signaled in
a Secondary Recorded Route Object.ro MplsPathIndexOrZero (MPLS-TC-STD-MIB) .jnxP2mpExperiment.1.2.3.1.13 |
jnxMplsTeP2mpTunnelDestTotalUpTimeThis value represents the aggregate up time for all
instances of this tunnel to this destination, if this
information is available.
If this information is not available, this object MUST
return a value of 0.ro TimeTicks (SNMPv2-SMI) .jnxP2mpExperiment.1.2.3.1.14 |
jnxMplsTeP2mpTunnelDestInstanceUpTimeThis value identifies the total time that the currently
active tunnel instance to this destination has had its
operational status (mplsTeP2mpTunnelDestOperStatus) set to
up(1) since it was last previously not up(1).ro TimeTicks (SNMPv2-SMI) .jnxP2mpExperiment.1.2.3.1.15 |
jnxMplsTeP2mpTunnelDestPathChangesThis object counts the number of times the actual path for
this destination of this P2MP tunnel instance has changed.
This object should be read in conjunction with
mplsTeP2mpTunnelDestDiscontinuityTime.ro Counter32 .jnxP2mpExperiment.1.2.3.1.16 |
jnxMplsTeP2mpTunnelDestLastPathChangeSpecifies the time since the last change to the actual path
for this destination of this P2MP tunnel instance.ro TimeTicks (SNMPv2-SMI) .jnxP2mpExperiment.1.2.3.1.17 |
jnxMplsTeP2mpTunnelDestCreationTimeSpecifies the value of sysUpTime when the first instance of
this tunnel came into existence for this destination. That
is, when the value of mplsTeP2mpTunnelDestOperStatus was
first set to up(1).ro TimeStamp (SNMPv2-TC) .jnxP2mpExperiment.1.2.3.1.18 |
jnxMplsTeP2mpTunnelDestStateTransitionsThis object counts the number of times the status
(mplsTeP2mpTunnelDestOperStatus) of this tunnel instance to
this destination has changed.
This object should be read in conjunction with
mplsTeP2mpTunnelDestDiscontinuityTime.ro Counter32 .jnxP2mpExperiment.1.2.3.1.19 |
jnxMplsTeP2mpTunnelDestDiscontinuityTimeThe value of sysUpTime on the most recent occasion at which
any one or more of this row's Counter32 objects experienced
a discontinuity. If no such discontinuity has occurred since
the last re-initialization of the local management
subsystem, then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .jnxP2mpExperiment.1.2.3.1.20 |
jnxMplsTeP2mpTunnelDestAdminStatusIndicates the desired operational status of this
destination of this P2MP tunnel.rw Enumeration .jnxP2mpExperiment.1.2.3.1.21 |
jnxMplsTeP2mpTunnelDestOperStatusIndicates the actual operational status of this destination
of this P2MP tunnel. This object may be compared to
mplsTunnelOperStatus that includes two other values:
dormant(5)
notPresent(6)
These states do not apply to an individual destination of a
P2MP MPLS-TE LSP and so are not included in this object.ro Enumeration .jnxP2mpExperiment.1.2.3.1.22 |
jnxMplsTeP2mpTunnelDestRowStatusThis object is used to create, modify, and/or delete a row
in this table. When a row in this table is in active(1)
state, no objects in that row can be modified by SET
operations except mplsTeP2mpTunnelDestAdminStatus and
mplsTeP2mpTunnelDestStorageType.rw RowStatus (SNMPv2-TC) .jnxP2mpExperiment.1.2.3.1.23 |
jnxMplsTeP2mpTunnelDestStorageTypeThe storage type for this table entry.
Conceptual rows having the value 'permanent' need
not allow write-access to any columnar objects in
the row.rw StorageType (SNMPv2-TC) .jnxP2mpExperiment.1.2.3.1.24 |
jnxMplsTeP2mpTunnelBranchPerfTableThis table provides per-tunnel branch MPLS performance
information.
This table is not valid for switching types other than
packet. SEQUENCE OF JnxMplsTeP2mpTunnelBranchPerfEntry .jnxP2mpExperiment.1.2.4 |
jnxMplsTeP2mpTunnelBranchPerfEntryAn entry in this table is created by the LSR for each
downstream branch (out-segment) from this LSR for this P2MP
tunnel.
More than one destination as represented by an entry in the
mplsTeP2mpTunnelDestTable may be reached through a single
out-segment. More than one out-segment may belong to a
single P2MP tunnel represented by an entry in
mplsTeP2mpTunnelTable.
Each entry in the table is indexed by the four identifiers
of the P2MP tunnel, and the out-segment that identifies the
outgoing branch. JnxMplsTeP2mpTunnelBranchPerfEntry .jnxP2mpExperiment.1.2.4.1 |
jnxMplsTeP2mpTunnelBranchPerfBranchThis object identifies an outgoing branch from this LSR
for this tunnel. Its value is unique within the context of
the tunnel.
If MPLS-LSR-STD-MIB is implemented, this object should
contain an index into mplsOutSegmentTable.
Under all circumstances, this object should contain
the same value as mplsTeP2mpTunnelDestBranchOutSegment for
destinations reached on this branch. MplsIndexType (MPLS-LSR-STD-MIB) .jnxP2mpExperiment.1.2.4.1.1 |
jnxMplsTeP2mpTunnelBranchPerfPacketsNumber of packets forwarded by the tunnel onto this branch.
This object should represents the 32-bit value of the least
significant part of the 64-bit value if both
mplsTeP2mpTunnelBranchPerfHCPackets is returned.
This object should be read in conjunction with
mplsTeP2mpTunnelBranchDiscontinuityTime.ro Counter32 .jnxP2mpExperiment.1.2.4.1.2 |
jnxMplsTeP2mpTunnelBranchPerfHCPacketsHigh capacity counter for number of packets forwarded by the
tunnel onto this branch.
This object should be read in conjunction with
mplsTeP2mpTunnelBranchDiscontinuityTime.ro Counter64 .jnxP2mpExperiment.1.2.4.1.3 |
jnxMplsTeP2mpTunnelBranchPerfErrorsNumber of packets dropped because of errors or for other
reasons, that were supposed to be forwarded onto this
branch for this tunnel. This object should be read in
conjunction with mplsTeP2mpTunnelBranchDiscontinuityTime.ro Counter32 .jnxP2mpExperiment.1.2.4.1.4 |
jnxMplsTeP2mpTunnelBranchPerfBytesNumber of bytes forwarded by the tunnel onto this branch.
This object should represents the 32-bit value of the least
significant part of the 64-bit value if both
mplsTeP2mpTunnelBranchPerfHCBytes is returned.
This object should be read in conjunction with
mplsTeP2mpTunnelBranchDiscontinuityTime.ro Counter32 .jnxP2mpExperiment.1.2.4.1.5 |
jnxMplsTeP2mpTunnelBranchPerfHCBytesHigh capacity counter for number of bytes forwarded
by the tunnel onto this branch.
This object should be read in conjunction with
mplsTeP2mpTunnelBranchDiscontinuityTime.ro Counter64 .jnxP2mpExperiment.1.2.4.1.6 |
jnxMplsTeP2mpTunnelBranchDiscontinuityTimeThe value of sysUpTime on the most recent occasion at which
any one or more of this row's Counter32 or Counter64 objects
experienced a discontinuity. If no such discontinuity has
occurred since the last re-initialization of the local
management subsystem, then this object contains a zero
value.ro TimeStamp (SNMPv2-TC) .jnxP2mpExperiment.1.2.4.1.7 |
jnxMplsTeP2mpTunnelNotificationEnableIf this object is true(1), then it enables the generation of
mplsTeP2mpTunnelDestUp and mplsTeP2mpTunnelDestDown
notifications. Otherwise these notifications are not
emitted.
Note that when tunnels have large numbers of destinations,
setting this object to true(1) may result in the generation
of large numbers of notifications.rw TruthValue (SNMPv2-TC) .jnxP2mpExperiment.1.2.5 |
jnxMplsTeP2mpConformance OBJECT IDENTIFIER .jnxP2mpExperiment.1.3 |
jnxMplsTeP2mpGroups OBJECT IDENTIFIER .jnxP2mpExperiment.1.3.1 |
jnxMplsTeP2mpCompliances OBJECT IDENTIFIER .jnxP2mpExperiment.1.3.2 |