PRVT-TEMIB-ENTITY-MIB

All MIBs › PRVT-TEMIB-ENTITY-MIB

Organization: BATM Advanced Communication

Last Updated: 2007-12-06

Category: System Management

Description: Manages BATM Advanced Communication entity MIB extensions for hardware inventory, physical component hierarchy, and asset tracking.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is PRVT-TEMIB-ENTITY-MIB?

PRVT-TEMIB-ENTITY-MIB is a private extension of the standard Entity MIB used by BATM Advanced Communication, a telecom and networking equipment vendor, to describe the physical component hierarchy inside its devices. It exposes physical inventory data such as chassis, card, module, port, and sensor entries along with their containment relationships. This makes it useful for monitoring hardware status: confirming which physical components are installed, tracking their identity and revision, and detecting when a component is removed, added, or fails. It builds directly on the IETF ENTITY-MIB (RFC 4133) framework, extending its physical-entity table structure with vendor-specific attributes. It is typically deployed by network management systems polling BATM chassis-based switching or transport equipment to maintain an accurate hardware inventory and detect physical-layer hardware changes. Engineers can download the PRVT-TEMIB-ENTITY-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in PRVT-TEMIB-ENTITY-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

BATM Advanced Communication telecom/networking equipment

Monitoring Examples

No sample objects were supplied for this module, so specific table names cannot be verified from the given data. Given its description as covering 'management of TE-MIB entities' and its Entity MIB heritage, it would be expected to extend a physical-entity table (analogous to entPhysicalTable) with BATM-specific card or module rows. An administrator would poll such a table to confirm expected hardware is present and correctly identified, and to detect unexpected removal or insertion of a module. Further concrete detail would be speculative without object names.

Imported Objects

From PRVT-CR-LDP-MIB

mpls	OBJECT-IDENTITY

From PRVT-LMGR-MIB

PrvtLmgrIndex
PrvtLmgrPartnerStatus

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
prvtTeMibEntityMib	1.3.6.1.4.1.738.1.6.5.8			The MIB module for management of TE-MIB entities.
prvtTeMibEntityObjects	1.3.6.1.4.1.738.1.6.5.8.1
prvtMplsTeMibEntityTable	1.3.6.1.4.1.738.1.6.5.8.1.1		not-accessible	The table of TE-MIB entities.
prvtMplsTeMibEntityEntry	1.3.6.1.4.1.738.1.6.5.8.1.1.1		not-accessible	Each entry represents a TE-MIB entity.
PRV prvtMplsTeMibEntityIndex	1.3.6.1.4.1.738.1.6.5.8.1.1.1.1	PrvtTeMibEntityIndex	not-accessible	The index of this TE-MIB entity table entry. This is the HAF entity index passed on the entity create parameters.
PRV prvtMplsTeMibEntityAdminStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.2	PrvtTeMibAdminStatus	read-create	The desired administrative state of the TE-MIB entity. When prvtMplsTeMibEntityRowStatus is 'active' and prvtMplsTeMibEntityAdminStatus is 'up' the TE-MIB entity is active and only these two fields can be modified.
PRV prvtMplsTeMibEntityOperStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.3	PrvtTeMibOperStatus	read-only	The current operational state of the TE-MIB entity.
ROW prvtMplsTeMibEntityRowStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.4	RowStatus	read-create	The row status for the TE-MIB entity table entry, used to create and destroy TE-MIB entities. When prvtMplsTeMibEntityRowStatus is 'active' and prvtMplsTeMibEntityAdminStatus is 'up' the TE-MIB entity is active and only these two fields can be modified.
U32 prvtMplsTeMibTunnelRetryInterval	1.3.6.1.4.1.738.1.6.5.8.1.1.1.5	Unsigned32	read-create	The persistent tunnel retry interval. This is the interval between the first failure of a persistent tunnel and the first attempt to re-establish the tunnel. A value of 0 indicates retrying is not supported. A management agent may preempt a retry by resetting mplsTunnelAdminStatus for the tunnel in question.
U32 prvtMplsTeMibTunnelRetryDecayRate	1.3.6.1.4.1.738.1.6.5.8.1.1.1.6	Unsigned32	read-create	The persistent tunnel decay rate. This is a percentage. Thus a value of 10 increases the retry interval by ten per cent of the previous value. A value of 0 indicates a constant retry rate.
I32 prvtMplsTeMibTunnelRetryMax	1.3.6.1.4.1.738.1.6.5.8.1.1.1.7	Integer32	read-create	The maximum number of retry attempts that will be made before a persistent tunnel is deemed inoperable. Once in this state, a management agent should set mplsTunnelAdminStatus to 'up' to attempt to reestablish the tunnel. A value of -1 indicates infinite retry, so a persistent tunnel will continue to be retried until it is successfully established.
U32 prvtMplsTeMibTnnlBufPoolSize	1.3.6.1.4.1.738.1.6.5.8.1.1.1.8	Unsigned32	read-create	The maximum number of buffers available for tunnel management messages. This is used to limit the number of tunnel management messages to avoid buffer shortage conditions.
PRV prvtMplsTeMibLsrIndex	1.3.6.1.4.1.738.1.6.5.8.1.1.1.9	PrvtLmgrIndex	read-create	The index of the PRVT-LMGR product instance which this TE-MIB is to join to as its LDB interface provider. If this value is not specified, or the value of this object is 0, TE-MIB will use the prvtMplsTeMibEntityIndex value as the Lsr index when joining on the LDB interface.
PRV prvtMplsTeMibLdbStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.10	PrvtTeMibPartnerStatus	read-only	Diagnostic Field providing information about the status of the Label Database Interface user as seen by the TE-MIB entity.
PRV prvtMplsTeMibLraStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.11	PrvtLmgrPartnerStatus	read-only	Diagnostic Field providing information about the status of the LRAPI user as seen by the TE-MIB entity.
PRV prvtMplsTeMibLdiStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.12	PrvtTeMibPartnerStatus	read-only	A diagnostic value which reports the state of the LDI join.
T/F prvtMplsTeMibRsvpEnable	1.3.6.1.4.1.738.1.6.5.8.1.1.1.13	TruthValue	read-create	A boolean indicating whether the PRVT-TE-MIB should expect a join from PRVT-RSVP across the LRAPI. This indicates whether RSVP-TE LSP tunnels are supported or not.
T/F prvtMplsTeMibCrldpEnable	1.3.6.1.4.1.738.1.6.5.8.1.1.1.14	TruthValue	read-create	A boolean indicating whether the PRVT-TE-MIB should join to PRVT-CR-LDP or not across the LDI, and therefore support CR-LDP LSP tunnels or not.
U32 prvtMplsTeMibCrldpIndex	1.3.6.1.4.1.738.1.6.5.8.1.1.1.15	Unsigned32	read-create	The index of the PRVT-MPLS product instance which this TE-MIB is to join to as its LDI interface provider. If this value is not specified, or the value of this object is 0, TE-MIB will use the prvtMplsTeMibEntityIndex value as the CR-LDP product index when joining on the LDI interface.
BIT prvtMplsTeMibUseRsvpResvConf	1.3.6.1.4.1.738.1.6.5.8.1.1.1.16	Bits	read-create	Flags field indicating whether a RESV_CONFIRM object should be included in RSVP Resv messages. The possible bit values are as follows. - useResvConfForUNI: RESV_CONFIRM objects should be inserted into all UNI Resv messages. - useResvConfForGMPLS: RESV_CONFIRM objects should be inserted into all standard GMPLS Resv messages.
T/F prvtMplsTeMibAllowGracefulDeletion	1.3.6.1.4.1.738.1.6.5.8.1.1.1.17	TruthValue	read-create	A boolean indicating whether the TE-MIB should allow tunnels to be deleted using the graceful deletion procedure.
T/F prvtMplsTeMibShowTransitTunnels	1.3.6.1.4.1.738.1.6.5.8.1.1.1.18	TruthValue	read-create	A flag to indicate whether RSVP should inform TE-MIB about LSPs for which this node is transit.
T/F prvtMplsTeMibSupportCHopTable	1.3.6.1.4.1.738.1.6.5.8.1.1.1.19	TruthValue	read-create	A flag to indicate whether TE-MIB should support the mplsTunnelCHopTable.
U32 prvtMplsTeMibNhrIndex	1.3.6.1.4.1.738.1.6.5.8.1.1.1.20	Unsigned32	read-create	The index of the PRVT-MPLS product instance which this TE-MIB is to join to as its NHR interface provider. If this value is not specified, or the value of this object is 0, TE-MIB will use the prvtMplsTeMibEntityIndex value as the LSR index when joining on the NHR interface.
U32 prvtMplsTeMibNhrBufPoolSize	1.3.6.1.4.1.738.1.6.5.8.1.1.1.21	Unsigned32	read-create	The maximum number of buffers available for Next Hop Routing Interface messages. This is used to limit the number of tunnel management messages to avoid buffer shortage conditions.
PRV prvtMplsTeMibNhrStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.22	PrvtTeMibPartnerStatus	read-only	A diagnostic value which reports the state of the NHR join.
PRV prvtMplsTeMibExtPrtSuppAdminStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.23	PrvtTeMibAdminStatus	read-create	The desired operational state of support for the extended PROTECTION object defined in draft-lang-ccamp-gmpls-recovery-e2e-signaling.
PRV prvtMplsTeMibRsvpIpv6AdminStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.24	PrvtTeMibAdminStatus	read-create	Specifies whether the local node supports IPv6 LSPs. Setting this to UP means that this node supports IPv6 LSPs being set up to, from and through this node. Setting this to DOWN means that IPv6 LSPs are NOT supported by this node. Existing IPv6 LSPs for which this node is the ingress are torn down. This field can be modified while TE-MIB is oper_status UP or DOWN. The value of this field MUST match the value of the dcRsvpProductIpv6AdminStatus field in the dcRsvpProductTable.
PRV prvtMplsTeMibRsvpIpv6OperStatus	1.3.6.1.4.1.738.1.6.5.8.1.1.1.25	PrvtTeMibOperStatus	read-only	The current operational status for IPv6 support. When this is UP IPv6 LSPs can be set up from this node. When this is DOWN there will be no active IPv6 LSPs.
T/F prvtMplsTeMibDynFacilityBypass	1.3.6.1.4.1.738.1.6.5.8.1.1.1.26	TruthValue	read-write	This object gives the user ability to globally enable/disable automatically creation of bypass tunnels for all LSPs. Bypass tunnels will be created on FRR tunnel request automatically. The default value is true. The creation of Dynamic bypass tunnels is enabled
prvtTeMibEntityConformance	1.3.6.1.4.1.738.1.6.5.8.2
prvtTeMibEntityCompliances	1.3.6.1.4.1.738.1.6.5.8.2.1
prvtTeMibEntityMibCompliance	1.3.6.1.4.1.738.1.6.5.8.2.1.1			The compliance statement for the PRVT-TEMIB product.
prvtTeMibEntityGroups	1.3.6.1.4.1.738.1.6.5.8.2.2
mplsTeMibMandatoryGroup	1.3.6.1.4.1.738.1.6.5.8.2.2.2			Mandatory Objects.
mplsTeMibOptionalGroup	1.3.6.1.4.1.738.1.6.5.8.2.2.3			Optional Objects.
mplsTeMibCrldpGroup	1.3.6.1.4.1.738.1.6.5.8.2.2.4			Group of objects relating to CR-LDP

RFC description

BATM Advanced Communications (ProView) private MIB for T-Metro switch entity and provisioning management.

Start monitoring BATM Advanced Communication telecom/networking equipment (ENTITY-MIB extension) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download PRVT-TEMIB-ENTITY-MIB

What Is PRVT-TEMIB-ENTITY-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description