CISCO-IP-RAN-BACKHAUL-MIB

CirbhProtocol1 = undefined2 = gsmAbis3 = umtsIubThe protocol used between BSC and BTS. 'undefined' : Protocol not defined. 'gsmAbis' : Global System for Mobile communications A-bis Interface between BSC and BTS. 'umtsIub' : Universal Mobile Telecommunications System Node B to RNC interface. · Integer32

Reference: GSM-Abis - 3GPP TS 08.60 V8.2.1 (Rel99) GSM A-bis specification for FR, EFR and AMR UMTS-Iub - 3GPP TS 25.302

Protocol used to indicate type of shorthaul.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

The type of address specified in the corresponding instance of cirbhConfigLocalIpAddr object.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

The local address used to route traffic across backhaul.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

The local port number used to distinguish traffic from this interface when transported over backhaul connection.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

The type of address in the in the corresponding instance of the cirbhInfoRemoteAddr object.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

The remote IP address used to route traffic across backhaul.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

The remote port number used to distinguish traffic from this interface when transported over backhaul connection.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object provides the serial number of the adjacent device supporting the other side of this shorthaul. This object contains the same value as the corresponding entPhysicalSerialNum object on the adjacent device. The type of object like chassis or module is provided by the cirbhInfoAdjectVendorType object.

AutonomousTypeRepresents an independently extensible type identification value. It may, for example, indicate a particular sub-tree with further MIB definitions, or define a particular type of protocol or hardware. · OBJECT IDENTIFIER

This object provides the vendor type of the adjacent device supporting other end of this shorthaul. This objectcontains the same value as the corresponding entPhysicalVendorType object on the adjacent device.

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

This object provides the ifIndex of the interface used to receive traffic from destination.

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

This object provides the ifIndex of the interface used to sent traffic to destination.

CirbhHistoryIndexThe system maintains a system wide counter that is incremented once a second. All tables that store historical informations should use the provided integer to that data from different tables can be easily compared and referenced. The implementations should ensure that the counters will not wrap and is only reset when device is reloaded. (1..4294967295) · Unsigned32 · hint d

The latest value of the cirbhShortHaulBulkHistory object from the cirbhShortHaulBulkHistory table.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicate whether the traffic received and sent for this shorthaul interface is optimized.

CirbhConnectGsmState1 = connected2 = disconnected3 = sendConnect4 = recConnect5 = connectedRej6 = ackConnect7 = connectedCheckThe state of the GSM connection: 'connected' - The device is monitoring local and remote alarm status. 'disconnected' - The system ignores the local alarm status. The local transmitter on the short-haul is disabled. Capability messages are transmitted to the remote describing the provisioning. The system stays disconnected until the remote capabilities are known and the peer state is transitioned to connected. 'sendConnect' - One or more attempts have been made to connect to remote peer. 'recConnect' - The local-peer has received a connect request from the remote-peer. 'connectedRej' - Connection was rejected. 'ackConnect' - The initial connect request was sent and acknowledged by remote-peer. The local-peer is now waiting for a connect request from the remote-peer. 'connectedCheck' - The local-peer has reason to believe its remote-peer has failed. Additional tests are being processed to verify peer's state. · Integer32

The state of the connection for GSM interface.

CirbhAlarmState1 = blue2 = green3 = red4 = yellow5 = unavailableAlarm states of local and remote interfaces. These states apply to both GSM and UMTS interfaces. 'blue' - Indicates a problem at the remote end. The alarm generate by the remote interface in the E1/T1 data stream is sent and no other action is required. 'green' - No alarm. 'red' - Indicates local interface problem. A-bis: The interface has not received synchronization from the GSM device. Device stops transmitting backhaul samples. 'yellow' - Indicates receive problem in the local device. The remote device stops transmitting backhaul data and indicates a blue alarm. 'unavailable' - Indicates the alarms state is not available. This state only applies to remote and occurs when peer connection is inactive. · Integer32

The local alarm state.

CirbhAlarmState1 = blue2 = green3 = red4 = yellow5 = unavailableAlarm states of local and remote interfaces. These states apply to both GSM and UMTS interfaces. 'blue' - Indicates a problem at the remote end. The alarm generate by the remote interface in the E1/T1 data stream is sent and no other action is required. 'green' - No alarm. 'red' - Indicates local interface problem. A-bis: The interface has not received synchronization from the GSM device. Device stops transmitting backhaul samples. 'yellow' - Indicates receive problem in the local device. The remote device stops transmitting backhaul data and indicates a blue alarm. 'unavailable' - Indicates the alarms state is not available. This state only applies to remote and occurs when peer connection is inactive. · Integer32

The remote alarm state.

CirbhRedundancyState1 = active2 = standbyThe Redundancy State of an interface. Used to indicate which device was current owner of interface. 'active' - Active owner of interface. 'standby' - Standby owner of interface. · Integer32

The redundancy state of the interface

CirbhConnectUmtsState1 = init2 = starting3 = closed4 = stopped5 = closing6 = stopping7 = connectSent8 = ackReceived9 = ackSent10 = openThe state of the UMTS connection: 'init' - The connection is starting initialization process. 'starting' - The shorthaul interface is administratively active but the backhaul interface is down. 'closed' - The backhaul interface is active but shorthaul is administratively closed. 'stopped' - Unable to connect to peer in specified time interval. Additional attempts will be tried based on peer request or restart timers. 'closing' - Connection closed by administration request. 'stopping' - Connection shutdown by peer's Term-Request. Will transition to stopped state. 'connectSent' - Connection request sent to peer. 'ackReceived' - Connection request sent and acknowledgement has been received from peer. Now waiting for peer's connection request. 'ackSent' - Connection request received and acknowledgement has been sent to peer. Connection request sent and waiting for peer's acknowledgement. 'open' - Connection open and available for traffic. · Integer32

The state of the connection between the UMTS interfaces.

CirbhRedundancyState1 = active2 = standbyThe Redundancy State of an interface. Used to indicate which device was current owner of interface. 'active' - Active owner of interface. 'standby' - Standby owner of interface. · Integer32

The redundancy state of the interface.

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

The root interface used to transport and receive UMTS traffic as follows. ATM: ATM0/0.0-aal5 layer -> ATM0/0-atm layer. IMA ATM0/IMA0.1-aal5 layer -> ATM0/IMA0

CirbhAlarmState1 = blue2 = green3 = red4 = yellow5 = unavailableAlarm states of local and remote interfaces. These states apply to both GSM and UMTS interfaces. 'blue' - Indicates a problem at the remote end. The alarm generate by the remote interface in the E1/T1 data stream is sent and no other action is required. 'green' - No alarm. 'red' - Indicates local interface problem. A-bis: The interface has not received synchronization from the GSM device. Device stops transmitting backhaul samples. 'yellow' - Indicates receive problem in the local device. The remote device stops transmitting backhaul data and indicates a blue alarm. 'unavailable' - Indicates the alarms state is not available. This state only applies to remote and occurs when peer connection is inactive. · Integer32

The local receive alarm state.

CirbhAlarmState1 = blue2 = green3 = red4 = yellow5 = unavailableAlarm states of local and remote interfaces. These states apply to both GSM and UMTS interfaces. 'blue' - Indicates a problem at the remote end. The alarm generate by the remote interface in the E1/T1 data stream is sent and no other action is required. 'green' - No alarm. 'red' - Indicates local interface problem. A-bis: The interface has not received synchronization from the GSM device. Device stops transmitting backhaul samples. 'yellow' - Indicates receive problem in the local device. The remote device stops transmitting backhaul data and indicates a blue alarm. 'unavailable' - Indicates the alarms state is not available. This state only applies to remote and occurs when peer connection is inactive. · Integer32

The remote receive alarm state.

CirbhAlarmState1 = blue2 = green3 = red4 = yellow5 = unavailableAlarm states of local and remote interfaces. These states apply to both GSM and UMTS interfaces. 'blue' - Indicates a problem at the remote end. The alarm generate by the remote interface in the E1/T1 data stream is sent and no other action is required. 'green' - No alarm. 'red' - Indicates local interface problem. A-bis: The interface has not received synchronization from the GSM device. Device stops transmitting backhaul samples. 'yellow' - Indicates receive problem in the local device. The remote device stops transmitting backhaul data and indicates a blue alarm. 'unavailable' - Indicates the alarms state is not available. This state only applies to remote and occurs when peer connection is inactive. · Integer32

The local transmit alarm state.

CirbhAlarmState1 = blue2 = green3 = red4 = yellow5 = unavailableAlarm states of local and remote interfaces. These states apply to both GSM and UMTS interfaces. 'blue' - Indicates a problem at the remote end. The alarm generate by the remote interface in the E1/T1 data stream is sent and no other action is required. 'green' - No alarm. 'red' - Indicates local interface problem. A-bis: The interface has not received synchronization from the GSM device. Device stops transmitting backhaul samples. 'yellow' - Indicates receive problem in the local device. The remote device stops transmitting backhaul data and indicates a blue alarm. 'unavailable' - Indicates the alarms state is not available. This state only applies to remote and occurs when peer connection is inactive. · Integer32

The remote transmit alarm state.

Counter32

For GSM-Abis interfaces, the count of samples received on interface. For UMTS interfaces, the number of packets received on interface.

Counter32

For GSM-Abis interfaces, the count of samples sent on interface. For UMTS interfaces, the number of packets sent on this interface.

Counter32 · packets

The count of packets received from backhaul that contained data for this interface.

Counter32 · packets

The count of packets transmitted on backhaul that contained data from this interface.

Counter32 · bytes

The count of bytes received from backhaul that contained data for this interface.

Counter32 · bytes

The count of bytes transmitted on backhaul that contained data from this interface.

Counter32 · packets

The count of packets dropped on backhaul because peer was not ready.

Counter32 · packets

The count of packets dropped on backhaul because peer was reachable but not in active state.

Counter32 · packets

The number of backhaul packets that were received and dropped because they contained invalid information.

Counter32 · packets

The number of backhaul packets expected to be received but never arrived.

Counter32 · packets

The number of backhaul packets sent but never were received by peer.

Counter32 · packets

The value of this object is the sum total of the values of the corresponding instances of the following objects: cirbhErrorsBhMissedLatePackets cirbhErrorsBhMissedLostPackets cirbhErrorsBhMissedNoMemPackets cirbhErrorsBhMissedResetPackets

Counter32 · packets

The number of packets missed on backhaul because they arrived past the allowed time frame.

Counter32 · packets

The number of packets missed on backhaul because they were lost on backhaul.

Counter32 · packets

The number of packets missed on backhaul for lack of available memory to allocate packet.

Counter32 · packets

The number of packets missed on backhaul because the of a reset event.

Counter32 · failures

The number of times information contained in packet could not be decompressed.

Counter32 · failures

The number of times the information contained in the packet could not be compressed. This counter is incremented for all types of compression errors.

Counter32 · failures

The number of times compression failed because packet was unavailable.

Counter32 · failures

The number of times compression failed because route to peer was not available.

Counter32 · failures

The number of times compression failed because interface was down.

Counter32 · failures

The number of times compression failed because of encapsulation errors.

Counter32 · drops

The number of times compression failed because of quality of service errors or traffic load.

CirbhHistoryIndexThe system maintains a system wide counter that is incremented once a second. All tables that store historical informations should use the provided integer to that data from different tables can be easily compared and referenced. The implementations should ensure that the counters will not wrap and is only reset when device is reloaded. (1..4294967295) · Unsigned32 · hint d

An index used to access history of cirbhShortHaulHistoryTable objects.

CirbhRawInterfaceRateThe rate of traffic, in bits per second, on an interface in a particular direction prior to optimization for the following flows: Traffic received on UMTS or GSM-Abis interface prior to compression and placement on backhaul interface(Multilink). Traffic received from backhaul interface(Multilink) after decompression prior to transmittion on UMTS or GSM-Abis interface. · Unsigned32 · hint d · bytes/second

The rate of traffic received from this interface to be sent on backhaul prior to compression.

CirbhRawInterfaceRateThe rate of traffic, in bits per second, on an interface in a particular direction prior to optimization for the following flows: Traffic received on UMTS or GSM-Abis interface prior to compression and placement on backhaul interface(Multilink). Traffic received from backhaul interface(Multilink) after decompression prior to transmittion on UMTS or GSM-Abis interface. · Unsigned32 · hint d · bytes/second

The rate of traffic sent out from this interface after traffic was decompressed.

CirbhCommpressInterfaceRateThe traffic rate of data received from GSM or UMTS interface after data has been compressed. The transmission compressed interface rate is calculated after data compression and prior to transmission on backhaul. The receive compression interface rate is calculated after data is received and prior to decompression. · Unsigned32 · hint d · bytes/second

The rate of traffic received into this interface to be sent on backhaul after compression.

CirbhCommpressInterfaceRateThe traffic rate of data received from GSM or UMTS interface after data has been compressed. The transmission compressed interface rate is calculated after data compression and prior to transmission on backhaul. The receive compression interface rate is calculated after data is received and prior to decompression. · Unsigned32 · hint d · bytes/second

The rate of traffic received from backhaul and prior to decompression.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

Time when sample was collected.

CirbhShortHaulUtilizationA percentage representing the average load over one second as a percent of E1 or T1. (0..255) · Integer32 · hint d · percent of DS load

Amount of traffic that was receive from backhaul before decompression express as load on E1 or T1.

CirbhShortHaulUtilizationA percentage representing the average load over one second as a percent of E1 or T1. (0..255) · Integer32 · hint d · percent of DS load

Amount of traffic that was send on after compression express as load on E1 or T1.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates congestion mechanisms have been enabled for shorthaul interface.

Counter32

This object provide the number packets or cells that were dropped due to congestion. When the cirbhInfoProtocol is 'gsmAbis' object indicates the number of packets dropped. When the cirbhInfoProtocol is 'umtsIub' object indicates the number of cells dropped.

Counter32 · bytes

The number of bytes dropped due to congestion control mechanisms.

Counter32 · occurences

The number of times congestion mechanism was engaged.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether congestion mechanism is active.

Counter32 · seconds

This object provides number of seconds interface was congested.

Counter32 · packets

The count of packets dropped on backhaul because peer was not ready.

Counter32 · packets

The count of packets dropped on backhaul because peer was reachable but not in active state.

Counter32 · packets

The number of backhaul packets that were received and dropped because they contained invalid information.

Counter32 · packets

The number of backhaul packets expected to be received but never arrived.

Counter32 · packets

The number of backhaul packets sent but never were received by peer.

Counter32 · packets

The value of this object is the sum total of the values of the corresponding instances of the following objects: cirbhGsmErrorsMissedLatePackets cirbhGsmErrorsMissedLostPackets cirbhGsmErrorsMissedNoMemPackets cirbhGsmErrorsMissedResetPackets

Counter32 · packets

The number of packets missed on backhaul because they arrived past the allowed time frame.

Counter32 · packets

The number of packets missed on backhaul because they were lost on backhaul.

Counter32 · packets

The number of packets missed on backhaul for lack of available memory to allocate packet.

Counter32 · packets

The number of packets missed on backhaul because the of a reset event.

Counter32 · failures

The number of times information contained in packet could not be decompressed.

Counter32 · failures

The number of times the information contained in the packet could not be compressed.

Counter32 · failures

The number of times compression failed because packet was unavailable.

Counter32 · failures

The number of times compression failed because route to peer was not available.

Counter32 · failures

The number of times compression failed because interface was down.

Counter32 · failures

The number of times compression failed because of encapsulation errors.

Counter32 · drops

The number of times compression failed because of quality of service errors or traffic load.

Counter32 · occurences

Fast send failures.

Counter32 · occurences

Unable to transmit GSM packet.

Counter32 · occurences

Unable to allocate buffer for transmission.

Counter32 · occurences

Transmission interface resets.

Counter32 · occurences

Packet was missed because backhaul jitter buffer was ran out of available space.

Counter32 · Failures

Packet was lost because of interrupt failure.

Counter32 · packets

Count of GSM packets that arrived later than the allowed time.

Counter32 · packets

Count of GSM packets that arrived earlier than the allowed time.

Counter32 · packets

The count of packets dropped on backhaul because peer was not ready.

Counter32 · packets

The number of backhaul packets that were received and dropped because they contained invalid information.

Counter32 · failures

The number of times information contained in packet could not be decompressed.

Counter32 · failures

The number of times the information contained int the packet could not be compressed.

Counter32 · failures

The number of times compression failed because packet was unavailable.

Counter32 · failures

The number of times compression failed because route to peer was not available.

Counter32 · failures

The number of times compression failed because interface was down.

Counter32 · failures

The number of times compression failed because of encapsulation errors.

Counter32 · drops

The number of times compression failed because of quality of service errors or traffic load.

Counter32 · occurrences

Unable to allocate packet used to send data on shorthaul interface.

Counter32 · occurences

The UMTS encapsulate failures.

Counter32 · packets

Packet dropped because local PVC was unavailable.

Counter32 · packets

Packet dropped because remote PVC was unavailable.

Counter32 · packets

Packets dropped on backhaul.

CirbhHistoryIndexThe system maintains a system wide counter that is incremented once a second. All tables that store historical informations should use the provided integer to that data from different tables can be easily compared and referenced. The implementations should ensure that the counters will not wrap and is only reset when device is reloaded. (1..4294967295) · Unsigned32 · hint d

An index used to access history of cirbhShortHaulBulkDataTable objects.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

Time when sample was collected.

Unsigned32 (256..2147483647) · Bytes

The Base Unit is an integer used to provide a range of bytes rates provided in the cirbhShortHaulBulkUtil object. All values in the cirbhShortHaulBulkUtil object share the same base unit.

OCTET STRING SIZE (0..256) · Bytes/Second

This object provides the amount of traffic transmitted in a particular shorthaul. The object contains 1 to 128 pairs. The length of the octet string can be used to calculate number of pairs. The information is in the following format were each rate is stored as single byte. [rx,tx] * 128 The approximated rate can be calculated by multiplying value from cirbhShortHaulBulkUtil times value in the cirbhShortHaulBulkBaseUnit.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object provides the serial number of the adjacent device supporting the backhaul connection. This object contains the same value as the corresponding entPhysicalSerialNum object. The type of object like chassis or module is provided by the cirbhBackHaulAdjectVendorType object.

AutonomousTypeRepresents an independently extensible type identification value. It may, for example, indicate a particular sub-tree with further MIB definitions, or define a particular type of protocol or hardware. · OBJECT IDENTIFIER

This object provides the vendor type of the adjacent device supporting backhaul connection. This object contains the same value as the corresponding entPhysicalVendorType object.

CirbhBackHaulUtilizationState1 = acceptable2 = warning3 = overloadedBackHaul Utilization State: 'acceptable' - traffic for a specified direction is at the acceptable level. 'warning' - traffic for a specified direction is above acceptable level but below the overloaded level. 'overloaded' - traffic for a specified direction has reached or exceeds overloaded level · Integer32

The utilization state for traffic received on backhaul multilink. The following objects will be used to calculate link utilization state: cirbhBackHaulAcceptableThreshold cirbhBackHaulWarningThreshold cirbhBackHaulOverloadedThreshold

CirbhBackHaulUtilizationState1 = acceptable2 = warning3 = overloadedBackHaul Utilization State: 'acceptable' - traffic for a specified direction is at the acceptable level. 'warning' - traffic for a specified direction is above acceptable level but below the overloaded level. 'overloaded' - traffic for a specified direction has reached or exceeds overloaded level · Integer32

The utilization state for traffic transmitted on backhaul multilink. The following objects will be used to calculate link utilization state: cirbhBackHaulAcceptableThreshold cirbhBackHaulWarningThreshold cirbhBackHaulOverloadedThreshold

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d · percent

The average receive utilization of the link over the last second.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d · percent

The average transmit utilization of the link over the last second.

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

This object indicates the backhaul interface.

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

This object indicates the shorthaul interface.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object indicates the value of sysUpTime when the entry was created.

CirbhHistoryIndexThe system maintains a system wide counter that is incremented once a second. All tables that store historical informations should use the provided integer to that data from different tables can be easily compared and referenced. The implementations should ensure that the counters will not wrap and is only reset when device is reloaded. (1..4294967295) · Unsigned32 · hint d

An index used to access history of cirbhBackHaulHistoryTable objects.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d · percent

The average receive utilization of link over the last second.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d · percent

The average transmit utilization of link over the last second.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d · percent

The average receive utilization of link over the last second that consisted of GSM-Abis traffic.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d · percent

The average transmit utilization of link over the last second that consisted of GSM-Abis traffic.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d · percent

The average receive utilization of link over the last second that consisted of UMTS traffic.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d · percent

The average transmit utilization of link over the last second that consisted of UMTS traffic.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

Time when sample was collected.

CirbhTrafficDirection1 = receive2 = transmitDirection of traffic on an interface. · Integer32

The direction of traffic on backhaul.

CirbhTrafficType1 = all2 = gsm3 = umtsThe types of traffic on backhaul interface. 'all' - All types of traffic 'gsm' - Only GSM based traffic 'umts' - Only UMTS based traffic · Integer32

The type of traffic.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 0 to 9 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 10 to 19 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 20 to 29 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 30 to 39 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 40 to 49 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 50 to 59 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 60 to 69 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 70 to 79 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 80 to 89 percent.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 90 to 100 percent.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

Time when sample was collected.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d

The maximum utilization encountered within interval.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

Time when cirbhStatsMaxUtilization was recorded.

CirbhHistoryIndexThe system maintains a system wide counter that is incremented once a second. All tables that store historical informations should use the provided integer to that data from different tables can be easily compared and referenced. The implementations should ensure that the counters will not wrap and is only reset when device is reloaded. (1..4294967295) · Unsigned32 · hint d

An index used to access each 15 minute entry.

CirbhTrafficDirection1 = receive2 = transmitDirection of traffic on an interface. · Integer32

The direction of traffic on backhaul.

CirbhTrafficType1 = all2 = gsm3 = umtsThe types of traffic on backhaul interface. 'all' - All types of traffic 'gsm' - Only GSM based traffic 'umts' - Only UMTS based traffic · Integer32

The type of traffic in backhaul history table.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 0 to 9 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 10 to 19 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 20 to 29 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 30 to 39 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 40 to 49 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 50 to 59 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 60 to 69 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 70 to 79 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 80 to 89 percent.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32 · seconds

The total numbers of seconds during which the backhaul link was utilized from 90 to 100 percent.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

End time when sample was collected.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d

The maximum utilization encountered within interval.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

Time when cirbhStatsHistoryMaxUtilization was recorded.

CirbhBackHaulUtilizationA percentage representing the average utilization of backhaul interface. (0..100) · Integer32 · hint d

The average utilization over the specified time period.