BUNDLE-MIB

All MIBs › BUNDLE-MIB

Organization: Nortel Networks

Last Updated: 1999-07-01

Category: Network Interfaces

Description: Manages link bundling (bonding/aggregation) configuration and member interface status for multi-link connections.

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 BUNDLE-MIB?

BUNDLE-MIB is a vendor MIB, consistent with legacy Nortel-lineage equipment given its object prefix, for managing link bundling, the aggregation of multiple physical links into a single logical multi-link connection. It exposes configuration data for each bundle, including its name, textual description, administrative contact, and Layer 2 encapsulation type, alongside performance/error-seconds counters and a trap/notification framework. Its monitoring emphasis is on link-quality and availability status: drop error-seconds, severely-errored-seconds, unavailable-seconds, and bursty-errored-seconds counters give a standards-style error-seconds profile for the aggregated bundle, letting an operator judge whether the logical bundle is meeting availability targets or experiencing member-link degradation. It parallels the structure of standard performance MIBs (such as RFC 1406-style error-second conventions) even though it is a proprietary bundle-specific module, and it uses its own traps/notifications for fault signaling. It is deployed on multi-link WAN aggregation equipment, such as bundled T1/E1 or serial links, in carrier or enterprise WAN environments. Engineers can download the BUNDLE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BUNDLE-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

Nortel-lineage multi-link WAN aggregation device
bundled T1/E1/serial link equipment

Monitoring Examples

An administrator would poll nnbundleTable/nnbundleTableEntry indexed by nnbundleId to read nnbundleName and nnbundleEncapsulation for inventory, then track nnbundleDropEs and nnbundleDropSes over a reporting interval to gauge link quality. A rising nnbundleDropUas (unavailable seconds) count would reveal the bundle experienced an outage window, while a spike in nnbundleDropBes alongside nnbundleDropEev would indicate a specific member link is flapping or degraded even if the bundle as a whole stayed up. nnbundleTraps would fire to alert on these degradation events in real time.

What Can Be Monitored

bundle name and encapsulation type
errored seconds / severely errored seconds
unavailable seconds
bursty errored seconds
bundle-related trap notifications

Imported Objects

From NT-ENTERPRISE-DATA-MIB

ntEnterpriseDataTasmanMgmt

OBJECT-IDENTITY

From SNMPv2-CONF

NOTIFICATION-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE
TimeTicks
mib-2

From SNMPv2-TC

DisplayString
RowStatus
TruthValue

How to Use in IPNetwork Monitor

Example using nnbundleDropPackets OID:

Select a Nortel multi-link WAN aggregation device (legacy) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type nnbundleDropPackets into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of packets dropped by a WAN interface when the agent encounters packet drops due to lack of buffer availability for transmission etc. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
I32 nnbundleClearCounters	1.3.6.1.4.1.562.73.1.1.1.13.1.1.33	Integer32	read-create	Perform a clearing of the counters operation
STR nnbundleContact	1.3.6.1.4.1.562.73.1.1.1.13.1.1.3	DisplayString	read-create	Name of the person who can be contacted for information about the bundle. The maximum length for this parameter is 15 characters. This parameter can be set after the bundle is named and before the links are assigned.
STR nnbundleContactInfo	1.3.6.1.4.1.562.73.1.1.1.13.5.1.3	DisplayString	accessible-for-notify	Name of the person who can be contacted for information about the bundle.
STR nnbundleDescr	1.3.6.1.4.1.562.73.1.1.1.13.1.1.4	DisplayString	read-create	Brief description of the bundle. The maximum length of this parameter is 25 characters. This parameter can be set after the bundle is named and before the links are assigned.
STR nnbundleDescrInfo	1.3.6.1.4.1.562.73.1.1.1.13.5.1.4	DisplayString	accessible-for-notify	Brief description of the bundle.
INT nnbundleDirectedBcast	1.3.6.1.4.1.562.73.1.1.1.13.1.1.30	INTEGER	read-create	Enable/disable forwarding of directed broadcasts on this interface.
INT nnbundleDownCause	1.3.6.1.4.1.562.73.1.1.1.13.5.1.2	INTEGER	accessible-for-notify	Reason for the bundle going down admin_delete - bundle has been deleted by administrator, admin_down - bundle has been disabled administratively, l1-failure - Layer 1 failures (physical links), including physical alarms, errors,etc. If a bundle is a multilink bundle, then the bundle will go down if all the inks go down. In case of MFR bundles, bundles behave according to the bandwidth class settings. l2-failure - Layer 2 related failures: LCP for PPP and LMI for FR bundles. bcp-negotiation-fail - BCP negotiation failures on PPP bundles. l3-failure - Layer 3 related failures. NCP for PPP. Incase of FR bundles, the layer 3 negotiation failures will not bring the bundle down. bundle-track-down - Bundle is disabled by bundle tracking,
NTF nnbundleDownTrap	1.3.6.1.4.1.562.73.1.1.1.13.5.0.1			Trap being generated when a bundle goes down.
I32 nnbundleDropBbe	1.3.6.1.4.1.562.73.1.1.1.13.1.1.11	Integer32	read-create	The length of time in seconds that the error condition Threshold for Background Blocked Errors (Applicable only for E1 links) exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropBes	1.3.6.1.4.1.562.73.1.1.1.13.1.1.10	Integer32	read-create	The length of time in seconds that the error condition Bursty Errored Seconds (Applicable only for T1 links) exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropBpv	1.3.6.1.4.1.562.73.1.1.1.13.1.1.13	Integer32	read-create	The length of time in seconds that the error condition BiPolar Violation exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropCrc	1.3.6.1.4.1.562.73.1.1.1.13.1.1.16	Integer32	read-create	The length of time in seconds that the error condition Cyclic Redundancy Check exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropCss	1.3.6.1.4.1.562.73.1.1.1.13.1.1.14	Integer32	read-create	The length of time in seconds that the error condition Controlled Slip Second exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropEev	1.3.6.1.4.1.562.73.1.1.1.13.1.1.9	Integer32	read-create	The length of time in seconds that the error condition ESF Error Events exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropEs	1.3.6.1.4.1.562.73.1.1.1.13.1.1.6	Integer32	read-create	The length of time in seconds that the error condition Errored Seconds exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropLofc	1.3.6.1.4.1.562.73.1.1.1.13.1.1.12	Integer32	read-create	The length of time in seconds that the error condition Loss Of Frame Count exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropOof	1.3.6.1.4.1.562.73.1.1.1.13.1.1.15	Integer32	read-create	The length of time in seconds that the error condition Out Of Frame exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
C32 nnbundleDropPacketsEx	1.3.6.1.4.1.562.73.1.1.1.13.1.1.35	Counter32	read-only	The number of packets dropped by a WAN interface when the agent encounters packet drops due to lack of buffer availability for transmission etc. Also, packets may be dropped for various reasons like Buffer over flow, packet too long, CRC errors, invalid packet length, system errors etc. This list is only a subset of the numerous reasons for the packets that can be dropped by the agent per interface
I32 nnbundleDropSes	1.3.6.1.4.1.562.73.1.1.1.13.1.1.7	Integer32	read-create	The length of time in seconds that the error condition Severely Errored Seconds exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
I32 nnbundleDropUas	1.3.6.1.4.1.562.73.1.1.1.13.1.1.8	Integer32	read-create	The length of time in seconds that the error condition Unavailable Seconds exists before a link is dropped. This parameter can be configured only for multilink bundles and after the bundle is encapsulated.
INT nnbundleEncapsulation	1.3.6.1.4.1.562.73.1.1.1.13.1.1.5	INTEGER	read-create	Specifies the type of protocol encapsulation for the bundle. To configure protocol-specific parameters for a bundle, the bundle must first be encapsulated with that protocol. To unconfigure the encapsulation type, this variable should be set to noEncap.
INT nnbundleIcmpRedirect	1.3.6.1.4.1.562.73.1.1.1.13.1.1.32	INTEGER	read-create	Enable/disable ICMP redirect messages on this on this interface
INT nnbundleIcmpUnreachable	1.3.6.1.4.1.562.73.1.1.1.13.1.1.31	INTEGER	read-create	Enable/disable ICMP destination unreachable messages on this interface
I32 nnbundleId	1.3.6.1.4.1.562.73.1.1.1.13.1.1.1	Integer32	not-accessible	bundleId is the identifier of a bundle. To configure a bundle, this parameter must be used as the index. This is assigned internally by the system. Whenever a row creation needs to occur in the bundleTable, the bundleId is entered as 65535.
IP nnbundleIpAddr	1.3.6.1.4.1.562.73.1.1.1.13.1.1.17	IpAddress	read-create	The bundle's source IP address. This is one of the parameters required to set up IP multiplexing for a bundle. This parameter can be configured only when the bundle is encapsulated. Also the parameters bundleIpAddr and bundleSubnetMask have to be set together during the same request. To unconfigure the IP address, a set operation is performed with the value 0.0.0.0
INT nnbundleIpMulticast	1.3.6.1.4.1.562.73.1.1.1.13.1.1.29	INTEGER	read-create	Specifies the Ip multicast operation.
STR nnbundleIpUnnumbered	1.3.6.1.4.1.562.73.1.1.1.13.1.1.28	DisplayString	read-create	Name of the bundle. To configure unnumbered, this parameter must be set. The maximum length of a bundle name is 8 characters.
I32 nnbundleLinkBw	1.3.6.1.4.1.562.73.1.1.1.13.2.1.8	Integer32	read-only	bundleLinkBw indicates the bandwidth of the link. The bandwidth of an individual link depends upon its configuration. For example, in a link of type T1, its bandwidth will depend upon whether the link is a full T1 or a fractional T1 consisting of 24 DS0 timeslots.
I32 nnbundleLinkDiffDelay	1.3.6.1.4.1.562.73.1.1.1.13.2.1.7	Integer32	read-only	bundleLinkDiffDelay specifies the maximum differential delay allowed on the links in a multilink bundle. If the packet delay on any link exceeds the differential delay set for a bundle, that link is dropped from the bundle.
nnbundleLinkEntry	1.3.6.1.4.1.562.73.1.1.1.13.2.1		not-accessible	Link parameters that relate to a given bundle are specified in this table.
T/F nnbundleLinkInvertedData	1.3.6.1.4.1.562.73.1.1.1.13.2.1.5	TruthValue	read-create	Setting bundleLinkInvertedData parameter to true will have the system invert data on all DS0 channels before transmission. Data inversion is used only for HDLC-encapsulated bundles.
I32 nnbundleLinkPhysIfNum	1.3.6.1.4.1.562.73.1.1.1.13.2.1.6	Integer32	read-create	bundleLinkPhysIfNum specifies the interface number of the interface type such as CT3, HSSI, T3 on which this link is being created. This variable holds significance only for link types CT3, HSSI and T3. It is a mandatory variable for row creation for link types CT3, HSSI, and T3.
I32 nnbundleLinkRestoralTime	1.3.6.1.4.1.562.73.1.1.1.13.1.1.22	Integer32	read-create	Error-free time interval (in seconds) that must pass before a link is automatically restored. This parameter can be set when the bundleRestoreMethod is automatic.
OCT nnbundleLinkRestore	1.3.6.1.4.1.562.73.1.1.1.13.1.1.24	OCTET STRING	read-write	bundleLinkRestore specifies the links to be restored manually. This parameter is configured when the value of bundleRestoreMethod is manual. The user needs to specify the link/s to be restored. LSB in the OCTET STRING represents T1 Number 1. For example, to restore links 1-4 the value should be set to 000F
ROW nnbundleLinkRowStatus	1.3.6.1.4.1.562.73.1.1.1.13.2.1.10	RowStatus	read-create	bundleLinkRowStatus is used to add or delete a row in the table. To create a row, this parameter is set to value 4(createAndGo). To delete a row, this parameter is set to a value 6(destroy).
INT nnbundleLinkSpeed	1.3.6.1.4.1.562.73.1.1.1.13.2.1.4	INTEGER	read-create	The bundleLinkSpeed specifies the transmission speed of all DS0 channels in a bundle.
INT nnbundleLinkStatus	1.3.6.1.4.1.562.73.1.1.1.13.2.1.9	INTEGER	read-only	bundleLinkStatus indicates whether a particular link in a bundle is up or down. The link can go down due to various reasons such as differential delay, a broken link, or negotiation problems at the far end.
I32 nnbundleLinkT1Num	1.3.6.1.4.1.562.73.1.1.1.13.2.1.1	Integer32	not-accessible	bundleLinkT1Num is the number of the T1 link being added to a specific bundle. For example, to assign link number 4, the value of this parameter should be set to 4. However, the design of SNMP's link creation is different from that of the system CLI. In SNMP, only one link can be created at a time whereas in the system CLI, multiple links can be configured in a single request. This parameter is mandatory for row creation in the interfaces with CT3 and T1 link types .
nnbundleLinkTable	1.3.6.1.4.1.562.73.1.1.1.13.2		not-accessible	All the parameters related to the assigned links of a bundle are defined in bundleLinkTable. A row in this table can be created when a bundle with the corresponding bundleId already exists in the bundleTable.
OCT nnbundleLinkTimeSlots	1.3.6.1.4.1.562.73.1.1.1.13.2.1.2	OCTET STRING	read-create	bundleLinkTimeSlots indicates the DS0 channels in a fractional T1 link. The LSB in the OCTET STRING represents DS0 channel number 1. For example, to assign DS0 channels 1-4, the value of this parameter should be set to 000F
INT nnbundleLinkType	1.3.6.1.4.1.562.73.1.1.1.13.2.1.3	INTEGER	read-create	bundleLinkType specifies the interface type (i.e.,CT3,T1,T3,HSSI,V35,X21,S530,S530A,S449,S232 etc.,) of the link being assigned to the bundle. This is a mandatory parameter for Row creation in the bundleLinkTable.
nnbundleMib	1.3.6.1.4.1.562.73.1.1.1.13			Bundle MIB for defining bundle parameters
STR nnbundleName	1.3.6.1.4.1.562.73.1.1.1.13.1.1.2	DisplayString	read-create	Name of the bundle. To configure a bundle, this parameter must be set. That is, a descriptive name should be given to a bundle. The maximum length of a bundle name is 8 characters. This parameter is set once during the creation of a bundle. A bundle can not be renamed.
STR nnbundleNameStr	1.3.6.1.4.1.562.73.1.1.1.13.5.1.1	DisplayString	accessible-for-notify	Name of the bundle going UP/DOWN.
I32 nnbundleNoOfLinks	1.3.6.1.4.1.562.73.1.1.1.13.1.1.25	Integer32	read-only	Indicates the number of links configured in the bundle.
nnbundleNotificationGroup	1.3.6.1.4.1.562.73.1.1.1.13.6			The BUNDLE MIB Notification Group.
nnbundleNotifications	1.3.6.1.4.1.562.73.1.1.1.13.5.0
INT nnbundleRestoreMethod	1.3.6.1.4.1.562.73.1.1.1.13.1.1.21	INTEGER	read-write	bundleRestoreMethod defines how a dropped link of a multilink bundle will be restored. It can be done either manually or automatically. If the restore mode is automatic, the parameter bundleLinkRestoralTime should be set (in seconds) during the same request.
ROW nnbundleRowStatus	1.3.6.1.4.1.562.73.1.1.1.13.1.1.27	RowStatus	read-create	bundleRowStatus is used to add/delete a row in the table. Adding or deleting a row corresponds to creating a bundle or deleting a bundle. In order to add a row to the bundle table, a set on this parameter should be done with the value 4 (createAndGo) and bundleId parameter set with the value of 65535. A request to create a row can be completed successfully only if a set on the bundleRowStatus and a set on the bundleName come in the same request. To delete a row this parameter has to be set with the value 6 (destroy).
IP nnbundleSrcForwardingAddrPrimary	1.3.6.1.4.1.562.73.1.1.1.13.1.1.19	IpAddress	read-create	The bundle's destination IP address. This is one of the parameters required to set up IP multiplexing for a bundle. This parameter can be configured when the bundle has been configured for IP multiplexing. To unconfigure the source forwarding address, a set operation is performed with the value 0.0.0.0. This is the primary source forwarding address
IP nnbundleSrcForwardingAddrSecondary	1.3.6.1.4.1.562.73.1.1.1.13.1.1.20	IpAddress	read-create	The bundle's secondary or backup destination address. This address will be used only if the primary address uses an ethernet interface and failover is enabled on that interface and the interface goes down. The secondary source forwarding address is an optional parameter, it should be a gateway on the alternate ethernet This parameter is set along with the primary source forwarding address parameter. To unconfigure this parameter a set operation is performed with the value 0.0.0.0 for the primary address, or a primary address is set with no secondary, or both primary and secondary are set to 0.0.0.0
INT nnbundleStatus	1.3.6.1.4.1.562.73.1.1.1.13.1.1.23	INTEGER	read-write	bundleStatus shutdowns the bundle. Although the default is 'enable,' the bundle remains disabled until all necessary parameters are present
IP nnbundleSubnetMask	1.3.6.1.4.1.562.73.1.1.1.13.1.1.18	IpAddress	read-create	This parameter represents the source subnet mask address. This is one of the parameters required to set up IP multiplexing for a bundle. This parameter is set along with the bundleIpAddr parameter during the same request.
nnbundleTable	1.3.6.1.4.1.562.73.1.1.1.13.1		not-accessible	Bundle management related parameters are defined in this table.
nnbundleTableEntry	1.3.6.1.4.1.562.73.1.1.1.13.1.1		not-accessible	Bundle parameter entries are listed in this table.
I32 nnbundleTotalBw	1.3.6.1.4.1.562.73.1.1.1.13.1.1.26	Integer32	read-only	Indicates the total bandwidth for this bundle. The bundle bandwidth is the aggregated band- widths of all the links assigned to a particular bundle.
nnbundleTrackEntry	1.3.6.1.4.1.562.73.1.1.1.13.3.1		not-accessible	Bundle Track parameters that relate to a given bundle are specified in this table.
INT nnbundleTrackHoldDownTimer	1.3.6.1.4.1.562.73.1.1.1.13.1.1.34	INTEGER	read-create	Indicates the tracking hold down timer.
nnbundleTrackTable	1.3.6.1.4.1.562.73.1.1.1.13.3		not-accessible	All the parameters related to bundle tracking are includede in BundleTrackTable.
nnbundleTraps	1.3.6.1.4.1.562.73.1.1.1.13.5
nnbundleTrapVariables	1.3.6.1.4.1.562.73.1.1.1.13.5.1
NTF nnbundleUpTrap	1.3.6.1.4.1.562.73.1.1.1.13.5.0.2			Trap being generated when a bundle comes up.
T/F nnenableBundleUpDownNotification	1.3.6.1.4.1.562.73.1.1.1.13.5.2	TruthValue	read-write	Indicates whether the system produces the BundleDownTrap & BundleUpTrap . The default is yes.
T/F nnenableLinkUpDownNotification	1.3.6.1.4.1.562.73.1.1.1.13.5.3	TruthValue	read-write	Indicates whether the system produces the linkDownTrap & linkUpTrap . The default is yes.
STR nnlinkBundleName	1.3.6.1.4.1.562.73.1.1.1.13.5.1.9	DisplayString	accessible-for-notify	Name of the bundle in which the link belongs to.
STR nnlinkCircuitId	1.3.6.1.4.1.562.73.1.1.1.13.5.1.10	DisplayString	accessible-for-notify	Configured cuircuit Id of the link
STR nnlinkContactInfo	1.3.6.1.4.1.562.73.1.1.1.13.5.1.11	DisplayString	accessible-for-notify	Configured contact string of the link
STR nnlinkCt3Num	1.3.6.1.4.1.562.73.1.1.1.13.5.1.7	DisplayString	accessible-for-notify	linkCt3Num specifies the interface number of the CT3/CE3 interface. This variable holds significance only for link type t1-within-ct3 and e1-within-ce3.
STR nnlinkDescrInfo	1.3.6.1.4.1.562.73.1.1.1.13.5.1.13	DisplayString	accessible-for-notify	Brief description of link
INT nnlinkDownCause	1.3.6.1.4.1.562.73.1.1.1.13.5.1.8	INTEGER	accessible-for-notify	Reason for the bundle going down admin-delete - link has been removed/deleted from the bundle by the administrator, admin-down - physical link has been disabled administratively from module configuration commands, e.g. 'no enable t1 1' drop-config - link has been removed from the bundle due to event being triggered by the error threshold configuration for the link. e.g. 'drop es 10' command setting from the bundle configuration commands. l1-failure - Layer 1 failures (physical links), including physical alarms, excessive errors,etc.
NTF nnlinkDownTrap	1.3.6.1.4.1.562.73.1.1.1.13.5.0.3			Trap being generated when a link from a bundle goes down.
STR nnlinkNameInfo	1.3.6.1.4.1.562.73.1.1.1.13.5.1.12	DisplayString	accessible-for-notify	Name of the link
STR nnlinkNum	1.3.6.1.4.1.562.73.1.1.1.13.5.1.5	DisplayString	accessible-for-notify	linkNum is the number of the T1/E1 link.
INT nnlinkType	1.3.6.1.4.1.562.73.1.1.1.13.5.1.6	INTEGER	accessible-for-notify	linkType specifies the interface type (i.e., CT3, T1, FT1, T3, E1, FE1, v35 and HSSI) of the link.
NTF nnlinkUpTrap	1.3.6.1.4.1.562.73.1.1.1.13.5.0.4			Trap being generated when a link whihin a bundle comes up.
I32 nnloopbackIfId	1.3.6.1.4.1.562.73.1.1.1.13.4.1.1	Integer32	not-accessible	loopbackIfId is the identifier of a loopback Interface. To configure a loopback, this parameter must be used as the index. This is assigned internally by the system. Whenever a row creation needs to occur in the loopbackIfTable, the loopbackIfId is entered as 65535.
IP nnloopbackIfIpAddr	1.3.6.1.4.1.562.73.1.1.1.13.4.1.3	IpAddress	read-create	The loopback's source IP address. This is one of the parameters required to set up loopback interface. The parameters loopbackIfIpAddr and loopbackIfSubnetMask have to be set together during the same request. To unconfigure the IP address, a set operation is performed with the value 0.0.0.0
STR nnloopbackIfName	1.3.6.1.4.1.562.73.1.1.1.13.4.1.2	DisplayString	read-create	Name of the loopback If. To configure a loopback Interface,this parameter must be set. That is, a descriptive name should be given to a loopback inteface. The maximum length of a name is 8 characters. This parameter is set once during the creation of a loopback If. A loopback can not be renamed.
ROW nnloopbackIfRowStatus	1.3.6.1.4.1.562.73.1.1.1.13.4.1.6	RowStatus	read-create	loopbackIfRowStatus is used to add/delete a row In the table. Adding or deleting a row corresponds to creating a loopback or deleting a loopback. In order to add a row to the loopback table, a set on this parameter should be done with the value 4 (createAndGo) and loopbackIfId parameter set with the value of 65535. A request to create a row can be completed successfully only if a set on the loopbackIfRowStatus and a set on the loopbackIfName come in the same request. To delete a row this parameter has to be set with the value 6 (destroy).
INT nnloopbackIfStatus	1.3.6.1.4.1.562.73.1.1.1.13.4.1.5	INTEGER	read-only	loopbackIfStatus shows the current status of the loopback interface.
IP nnloopbackIfSubnetMask	1.3.6.1.4.1.562.73.1.1.1.13.4.1.4	IpAddress	read-create	This parameter represents the source subnet mask address. This is one of the parameters required to set up loopback interface. This parameter is set along with the loopbackIfIpAddr parameter during the same request.
nnloopbackIfTable	1.3.6.1.4.1.562.73.1.1.1.13.4		not-accessible	A list of Loopback Interface table entries for this entity.
nnloopbackIfTableEntry	1.3.6.1.4.1.562.73.1.1.1.13.4.1		not-accessible	Loopback Interface parameter entries are listed in this table.
I32 nntrackIntfId	1.3.6.1.4.1.562.73.1.1.1.13.3.1.1	Integer32	not-accessible	trackIntfId is the identifier of the bundle being tracked.
STR nntrackIntfName	1.3.6.1.4.1.562.73.1.1.1.13.3.1.2	DisplayString	read-create	Name of the bundle being tracked.
ROW nntrackIntfRowStatus	1.3.6.1.4.1.562.73.1.1.1.13.3.1.4	RowStatus	read-create	Used to configure or delete a tracking interface. To configure a interface, set the value of this object to createAndGo. To delete a interface, set the value of this object to destroy.
INT nntrackIntfStatus	1.3.6.1.4.1.562.73.1.1.1.13.3.1.3	INTEGER	read-only	bundleStatus displays the status of the bundle being tracked.

RFC description

Manages bundle parameters on Nortel Data networks including encapsulation and link restoration settings.

Start monitoring Nortel multi-link WAN aggregation devices (legacy) 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 BUNDLE-MIB