VPLS-BGP-DRAFT-01-MIB
Updated Dec 6, 2006The VPLS-BGP-DRAFT-01-MIB module provides managed object definitions for monitoring BGP-signalled Virtual Private LAN Services (VPLS) and associated pseudo-wire states on network devices supporting RFC 4761. It enables the tracking of BGP session parameters, VPLS instance attributes, and underlying pseudo-wire connectivity metrics across any supported transport network.
Imported Objects
Objects
17 total| Object Name |
|---|
jnxVplsBgpDraft01MIBCopyright (C) The IETF Trust (2010). 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
BGP signalled Virtual Private LAN Services as in
[RFC4761]
This MIB module enables the use of any underlying PseudoWire
network. MODULE-IDENTITY .1.3.6.1.4.1.2636.5.10 |
jnxVplsBgpObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2636.5.10.1 |
jnxVplsBgpConfigTableThis table specifies information for configuring
and monitoring BGP specific parameters for
Virtual Private Lan Services(VPLS). SEQUENCE OF JnxVplsBgpConfigEntry .1.3.6.1.4.1.2636.5.10.1.1 |
jnxVplsBgpConfigEntryA row in this table represents BGP specific information
for Virtual Private Lan Service(VPLS) in a packet network.
It is indexed by jnxVplsConfigIndex, which uniquely
identifies a single instance of a VPLS service.
A row is automatically created when a VPLS service is
configured using BGP signalling.
None of the read-create objects values can be
changed when jnxVplsRowStatus is in the active(1)
state. Changes are allowed when the jnxVplsRowStatus
is in notInService(2) or notReady(3) states only.
If the operator need to change one of the values
for an active row the jnxVplsConfigRowStatus should be
first changed to notInService(2), the objects may
be changed now, and later to active(1) in order to
re-initiate the signaling process with the new
values in effect. JnxVplsBgpConfigEntry .1.3.6.1.4.1.2636.5.10.1.1.1 |
jnxVplsBgpConfigVERangeSizeSpecifies the size of the range of VE ids in this
VPLS service. This number controls the size of the
label block advertised for this VE by the PE.
A value of 0 indicates that the range is not
configured and the PE derives the range value
from received advertisements from other PEs.ro Unsigned32 .1.3.6.1.4.1.2636.5.10.1.1.1.1 |
jnxVplsBgpVETableThis table associates VPLS Edge devices to a VPLS service SEQUENCE OF JnxVplsBgpVEEntry .1.3.6.1.4.1.2636.5.10.1.2 |
jnxVplsBgpVEEntryAn entry in this table is created for each VE Id
configured on a PE for a particular VPLS service
instance. JnxVplsBgpVEEntry .1.3.6.1.4.1.2636.5.10.1.2.1 |
jnxVplsBgpVEIdA secondary index identifying a VE within an
instance of a VPLS service. Unsigned32 .1.3.6.1.4.1.2636.5.10.1.2.1.1 |
jnxVplsBgpVENameDescriptive name for the site or u-PE assciated with
this VE Id.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.2636.5.10.1.2.1.2 |
jnxVplsBgpVEPreferenceSpecifies the preference of the VE Id on this PE
if the site is multi-homed and VE Id is re-used.ro Unsigned32 .1.3.6.1.4.1.2636.5.10.1.2.1.3 |
jnxVplsBgpVERowStatusThis 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 except jnxVplsBgpSiteRowStatus.ro RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2636.5.10.1.2.1.5 |
jnxVplsBgpVEStorageTypeThis variable indicates the storage type for this row.ro StorageType (SNMPv2-TC) .1.3.6.1.4.1.2636.5.10.1.2.1.6 |
jnxVplsBgpPwBindTableThis table provides BGP specific information for
an association between a VPLS service and the
corresponding Pseudo Wires. A service can have more
than one Pseudo Wire association. Pseudo Wires are
defined in the pwTable. SEQUENCE OF JnxVplsBgpPwBindEntry .1.3.6.1.4.1.2636.5.10.1.3 |
jnxVplsBgpPwBindEntryEach row represents an association between a
VPLS instance and one or more Pseudo Wires
defined in the pwTable. Each index is unique
in describing an entry in this table. However
both indexes are required to define the one
to many association of service to pseudowire.
An entry in this table in instantiated only when
BGP signalling is used to configure VPLS service.
Each entry in this table provides BGP specific
information for the VPlS represented by
jnxVplsConfigIndex. JnxVplsBgpPwBindEntry .1.3.6.1.4.1.2636.5.10.1.3.1 |
jnxVplsBgpPwBindLocalVEIdIdentifies the local VE that this Pseudo Wire
is associated with.ro Unsigned32 .1.3.6.1.4.1.2636.5.10.1.3.1.1 |
jnxVplsBgpPwBindRemoteVEIdIdentifies the remote VE that this Pseudo Wire
is associated with.ro Unsigned32 .1.3.6.1.4.1.2636.5.10.1.3.1.2 |
jnxVplsBgpConformance OBJECT IDENTIFIER .1.3.6.1.4.1.2636.5.10.2 |
More MIBs from Juniper Networks
Browse all Juniper NetworksMIBs →The JUNIPER-CHASSIS-DEFINES-MIB establishes the foundational Object Identifier (OID) namespace and data type definitions required to map and identify specific Juniper chassis hardware platforms and their internal physical components. This module serves as the structural prerequisite for the JUNIPER-CHASSIS-MIB, enabling the retrieval of inventory data, component status, and hardware topology details for Juniper MX, PTX, and EX series devices.
The JUNIPER-MOBILE-GATEWAY-GTP-MIB provides SNMP objects for monitoring GTP (GPRS Tunneling Protocol) session states, tunnel endpoints, and protocol counters on Juniper mobile gateway platforms. It enables administrators to track GTP-C and GTP-U traffic statistics, error conditions, and active tunnel metrics essential for validating mobile core network connectivity.
SNMP MIB module
SNMP MIB module
The JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB module enables monitoring of GTP (GPRS Tunneling Protocol) session states and traffic counters on Juniper Mobile Gateway Serving Gateways (SGW). It provides specific objects for tracking GTP-C and GTP-U tunnel establishment, teardown, and packet throughput metrics essential for validating mobile core network connectivity.
The JUNIPER-IPSEC-FLOW-MON-MIB monitors Juniper Networks IPsec VPN infrastructure by exposing tables for IKE tunnels, IPSec tunnels, and IPSec security associations to track tunnel states, association parameters, and flow statistics. This module facilitates the management of IPsec security policies and the operational status of encrypted traffic flows within the device's security architecture.