2005-01-21
This MIB provides information on Building Integrated Timing Supply(BITS) clocking sources and modes of operations. It is used to generate notifications to indicate when clocking sources change roles or become unavailable. GR-1233CORE sections 8.1.2 Major Alarms and 8.1.3 Critical Alarms
Download CISCO-BITS-CLOCK-MIB.txt Open CISCO-BITS-CLOCK-MIB.txt in a new tab
SCALARS (1) · TABLES (1) · TRAPS (3)
| Name | OID |
|---|---|
| cBitsClkNotifEnabled | 1.3.6.1.4.1.9.9.459.1.2 |
| Name | OID |
|---|---|
| cBitsClkSourceTable | 1.3.6.1.4.1.9.9.459.1.1 |
| Name | OID |
|---|---|
| ciscoBitsClockSource | 1.3.6.1.4.1.9.9.459.0.1 |
| ciscoBitsClockFreerun | 1.3.6.1.4.1.9.9.459.0.2 |
| ciscoBitsClockHoldover | 1.3.6.1.4.1.9.9.459.0.3 |
END OF TOC
1.3.6.1.4.1.9.9.459.1.2
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
The BITS clocking notification truth value. 'true' Indicates that all notification contained within this MIB are to be generated. 'false' Indicates that all notification contained within this MIB are disabled.
1.3.6.1.4.1.9.9.459.1.1
Index: entPhysicalIndex
This table contains one row per clock source and is a sparse augmentation of the entPhysicalTable. This table provides additional information for each entry of the entPhysicalTable that acts as clock source.
from ENTITY-MIB
PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d
The index for this entry.
1.3.6.1.4.1.9.9.459.1.1.1.1
INTEGER1 = primary2 = secondary3 = tertiary · Integer32
Indicates the role of this clock source as defined by system administrator.
1.3.6.1.4.1.9.9.459.1.1.1.2
INTEGER0 = unavailable1 = primary2 = secondary3 = tertiary · Integer32
The current role of BITS clock source. Also, indicates when clock source is unavailable. The 'unavailable' value indicates that the external source of clock signal has failed and indicates that this entry can not serve as clock source.
1.3.6.1.4.1.9.9.459.1.1.1.3
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
Timestamp used it indicate when this clock source entered the current role defined by cBitsClkSourceRoleCurrent object
1.3.6.1.4.1.9.9.459.1.1.1.4
Counter32 · seconds
The total number of seconds that this clock source was active and able to serve role as specified as cBitsClkSourceRoleCurrent object.
1.3.6.1.4.1.9.9.459.1.1.1.5
Counter32 · seconds
The total number of seconds that this clock source was inactive and unable to serve role as specified as cBitsClkSourceRoleCurrent object.
1.3.6.1.4.1.9.9.459.1.1.1.6
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 will provide description in addition to entPhysicalDescr or ifDescr(if available) for the clock source.
1.3.6.1.4.1.9.9.459.0.1
Indicates the clock source has switch roles as clock source as indicated by cBitsClkSourceRoleCurrent
1.3.6.1.2.1.47.1.1.1.1.2
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
A textual description of physical entity. This object should contain a string that identifies the manufacturer's name for the physical entity and should be set to a distinct value for each version or model of the physical entity.
1.3.6.1.4.1.9.9.459.1.1.1.6
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 will provide description in addition to entPhysicalDescr or ifDescr(if available) for the clock source.
1.3.6.1.4.1.9.9.459.1.1.1.1
INTEGER1 = primary2 = secondary3 = tertiary · Integer32
Indicates the role of this clock source as defined by system administrator.
1.3.6.1.4.1.9.9.459.1.1.1.2
INTEGER0 = unavailable1 = primary2 = secondary3 = tertiary · Integer32
The current role of BITS clock source. Also, indicates when clock source is unavailable. The 'unavailable' value indicates that the external source of clock signal has failed and indicates that this entry can not serve as clock source.
1.3.6.1.4.1.9.9.459.0.2
An external clock source is unavailable. The internal clock will operate in freerun mode using appropiate local oscillator. Therefore, it does not provide synchronous clocking. This is the least stable of all operating modes.
1.3.6.1.2.1.47.1.1.1.1.2
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
A textual description of physical entity. This object should contain a string that identifies the manufacturer's name for the physical entity and should be set to a distinct value for each version or model of the physical entity.
1.3.6.1.4.1.9.9.459.0.3
An external clock source is unavailable. The internal clock will operate in holdover mode. The network clock module has stored information about the incoming clock signal, it can faithfully reproduce the lost signal while in holdover mode until a switchover to another clock source occurs.
1.3.6.1.2.1.47.1.1.1.1.2
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
A textual description of physical entity. This object should contain a string that identifies the manufacturer's name for the physical entity and should be set to a distinct value for each version or model of the physical entity.