BUNDLE-MIB: View SNMP OID List / Download MIB

Bundle MIB for defining bundle parameters

Bundle management related parameters are defined in this table.

Bundle parameter entries are listed in this table.

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.

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.

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.

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.

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. Enumeration: 'hdlc': 3, 'ppp': 2, 'frameRelay': 4, 'noEncap': 1.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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

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. Enumeration: 'automatic': 2, 'manual': 1.

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.

bundleStatus shutdowns the bundle. Although the default is 'enable,' the bundle remains disabled until all necessary parameters are present Enumeration: 'enable': 1, 'disable': 2.

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

Indicates the number of links configured in the bundle.

Indicates the total bandwidth for this bundle. The bundle bandwidth is the aggregated band- widths of all the links assigned to a particular bundle.

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).

Name of the bundle. To configure unnumbered, this parameter must be set. The maximum length of a bundle name is 8 characters.

Specifies the Ip multicast operation. Enumeration: 'noMcast': 0, 'ospfrip2': 3, 'block': 2, 'pass': 1.

Enable/disable forwarding of directed broadcasts on this interface. Enumeration: 'enable': 1, 'disable': 0.

Enable/disable ICMP destination unreachable messages on this interface Enumeration: 'enable': 1, 'disable': 0.

Enable/disable ICMP redirect messages on this on this interface Enumeration: 'enable': 1, 'disable': 0.

Perform a clearing of the counters operation

Indicates the tracking hold down timer.

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

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.

Link parameters that relate to a given bundle are specified in this table.

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 .

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

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. Enumeration: 'ft1': 7, 's232': 13, 's530A': 11, 's449': 12, 'v35': 6, 'ct3': 1, 'x21': 9, 't3': 5, 't1': 2, 's530': 10, 'fe1': 8, 'hssi': 4, 'e1': 3.

The bundleLinkSpeed specifies the transmission speed of all DS0 channels in a bundle. Enumeration: 'kbps64': 2, 'notApplicable': 3, 'kbps56': 1.

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.

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.

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.

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.

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. Enumeration: 'down': 2, 'up': 1.

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).

All the parameters related to bundle tracking are includede in BundleTrackTable.

Bundle Track parameters that relate to a given bundle are specified in this table.

trackIntfId is the identifier of the bundle being tracked.

Name of the bundle being tracked.

bundleStatus displays the status of the bundle being tracked. Enumeration: 'down': 2, 'up': 1.

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.

A list of Loopback Interface table entries for this entity.

Loopback Interface parameter entries are listed in this table.

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.

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.

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

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.

loopbackIfStatus shows the current status of the loopback interface. Enumeration: 'down': 2, 'up': 1.

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).

Trap being generated when a bundle goes down.

Trap being generated when a bundle comes up.

Trap being generated when a link from a bundle goes down.

Trap being generated when a link whihin a bundle comes up.

Name of the bundle going UP/DOWN.

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, Enumeration: 'bundle-track-down': 7, 'l3-negotiation-fail': 6, 'bcp-negotiation-fail': 5, 'l1-failures': 3, 'admin-down': 2, 'l2-negotiation-fail': 4, 'admin-delete': 1.

Name of the person who can be contacted for information about the bundle.

Brief description of the bundle.

linkNum is the number of the T1/E1 link.

linkType specifies the interface type (i.e., CT3, T1, FT1, T3, E1, FE1, v35 and HSSI) of the link. Enumeration: 'ft1': 8, 't1-within-ct3': 2, 'e1-within-ce3': 4, 's449': 13, 'v35': 7, 'x21': 10, 't3': 5, 't1': 1, 's530': 11, 's530A': 12, 'fe1': 9, 's232': 14, 'hssi': 6, 'e1': 3.

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.

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. Enumeration: 'admin-down': 2, 'drop-config': 3, 'diffdelay': 4, 'l1-failures': 5, 'admin-delete': 1.

Name of the bundle in which the link belongs to.

Configured cuircuit Id of the link

Configured contact string of the link

Name of the link

Brief description of link

Indicates whether the system produces the BundleDownTrap & BundleUpTrap . The default is yes.

Indicates whether the system produces the linkDownTrap & linkUpTrap . The default is yes.

The BUNDLE MIB Notification Group.