CISCO-SESS-BORDER-CTRLR-EVENT-MIB

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

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..30) · OCTET STRING · hint 255t

This MIB object represents the name of the virtual media gateway. The length of this object will be zero if the virtual media gateway is not defined.

Unsigned32

This MIB object represents the context identifier for a particular SIP/H.248 call flow. The context identifier for each call is unique. The context identifier is also called as gate identifier for the SIP/H.248 call flow.

Unsigned32

This MIB object represents the stream identifier given to a particular SIP/H.248 call flow. The stream identifier for each call is unique. The stream identifier is also called as flow pair identifier for the SIP/H.248 call flow.

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

This MIB object represents the address type of local source on which the media (RTP/RTCP) packets from an unexpected source was received during a SIP/H.248 call flow. The IP address could be IPv4 as well as IPv6.

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 (4 | 16) · OCTET STRING

This MIB object represents the local address on which the media (RTP/RTCP) packets from an unexpected source was received during a SIP/H.248 call flow. The IP address could be of type csbSrcAlertLocalAddressType.

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

This MIB object represents the local RTP port number for the flow on which the unexpected source packet was received. Note the RTP port number is reported in the case where the unexpected packet was received on the RTCP port for the flow.

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

This MIB object represents the type of address for the source address in media packets received from an unexpected source (not received from the source with which SIP/H.248 call is already established but are received from some other IP address).

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 (4 | 16) · OCTET STRING

This MIB object represents the source address from which unexpected media packets are received during a SIP/H.248 call flow, i.e., media packets are not received from the source with which SIP/H.248 call is already established but are received from some other IP address. The IP address could be of type csbSrcAlertRemoteAddressType.

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

This MIB object represents the source port from which unexpected media packets are received during a SIP/H.248 call flow (i.e. media packets are not received from the source with which SIP/H.248 call is already established but are received from some other IP address).

OCTET STRING SIZE (0..32)

This MIB object represents the VPN Identifier for the Virtual Private Network within which the source flow is allocated. As this is an OCTET STRING, the MIB object will populate a NULL string if the source flow is not part of a VPN and in this case its length will be 0.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbDynamicBlackListedSrcSubFamily1 = blackVPN2 = blackAddress3 = blackPortThis textual convention represents the type of the source being blacklisted. Here source is the entity that sends the SIP call packets to SBC during a SIP call. The semantics are as follows. blackVPN - Represents the VPN identifier of the blacklisted source. blackAddress - Represents the IP address of the blacklisted source. blackPort - Represents the port number of the blacklisted source. · Integer32

This MIB object represents the subfamily to which a blacklist source belongs.

OCTET STRING SIZE (0..32)

This MIB object represents the VPN Identifier for the Virtual Private Network that the source flow is allocated in. The value of this MIB object will be 0 if the source flow is not part of a VPN.

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

This MIB object represents the type of the address of the source. This MIB object is not applicable for subfamilies of type 'blackVpn' and hence a value of 'unknown' will be populated.

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

This MIB object represents the address of the source. This object could be if type csbDynamicBlackListAddressType. This MIB object is not applicable for subfamilies of type 'blackVpn' and hence a value of 'unknown' will be populated.

CsbDynamicBlackListedTransPortType1 = none2 = udp3 = tcpThis textual convention describes the mode of the transport for the source that has been blacklisted. The semantics are as follows: None - None is used if mode of transport of the packets being sent to SBC is not defined. UDP - This type is used when mode of transport of the packets being sent to SBC is UDP. TCP - This type is used when mode of transport the packets being sent to SBC is TCP. · Integer32

This MIB object represents the transport type of the source port. This MIB object is not applicable for subfamilies of type 'blackVpn' and 'blackAddr', hence a value 'unknown' will be populated.

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

This MIB object represents the source port number. This MIB object is not applicable for subfamilies of type 'blackVpn' and 'blackAddr' and hence a value of 'unknown' will be populated.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This MIB object represents the access control imposed on the blacklisted source by the controller. A value of 'true' indicates access is blocked and A value of 'false' indicates that the access is unblocked.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

INTEGER1 = attached2 = detached · Integer32

This MIB object represents the adjacency state. The adjacency state can either be attached or detached.

INTEGER1 = sip2 = h323 · Integer32

This MIB object represents the protocol type of the adjacency. The adjacency are of two types - SIP and H.323.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

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 MIB object represents the account name associated with the adjacency.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

INTEGER1 = active2 = standby3 = offline · Integer32

This MIB object represents the current state of the service card. SBC service is in active state if it is configured on the primary card and the service card is in active state. The SBC service is in standby state if the service card on which the service is configured goes to standby mode. The SBC service is in offline mode if the service card on which the service is configured is in reset state or reboot state.

Integer32

This MIB object represents the slot identifier of the service card.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

INTEGER1 = unknown2 = cpu3 = memory · Integer32

This MIB object represents the type of the CSB system congestion alarm. The alarm is raised either due to 'high CPU usage' or 'high memory usage'.

INTEGER1 = raised2 = cleared · Integer32

This MIB object represents the CSB system congestion alarm state. The state is either 'raised' or 'cleared'.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

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 MIB object represents the account name of the source which was involved in policy violation.

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 MIB object represents the scope of the SLA policy which has been violated.

Integer32

This MIB object represents the currently defined policy limits.

Integer32

This MIB object represents the actual usage value for the event which leads to the SLA violation, like if maximum number of calls are more than SLA policy then actual value of this parameter/event.

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 MIB object represents the type of SLA policy violation event.

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 MIB object represents the SLA policy restriction description means the violation of the call policy has resulted into which type of restriction, like if maximum number of calls exceeds then it will restrict the number of concurrent calls.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

INTEGER1 = up2 = down · Integer32

This MIB object represents the RADIUS server connection state. The connection state can either be up or down.

INTEGER1 = accounting2 = authentication · Integer32

This MIB object represents the type of RADIUS either for accounting or for authentication.

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 MIB object represents the name of the RADIUS server.

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

This MIB object represents the address type of RADIUS server (IPv4 or IPv6).

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 (4 | 16) · OCTET STRING

This MIB object represents address of the RADIUS server. This object could be of type csbRadiusServerAddressType.

Integer32

This MIB object represents the priority of the RADIUS server in case of the multiple servers. Higher the number, the higher is its priority.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

INTEGER1 = up2 = down · Integer32

This MIB object represents the diameter server connection state. The connection state can either be up or down.

INTEGER1 = accounting2 = authentication · Integer32

This MIB object represents the type of diameter server used which can be either for accounting or for authentication here.

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 MIB object represents the diameter group name. The length of this object is zero if the diameter type is authentication.

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 MIB object represents the diameter server name.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

INTEGER1 = attached2 = detached · Integer32

This MIB object represents the current state of H.248 controller with respect to SBC which is attached or detached state.

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

This MIB object represents the address type of the H.248 controller.

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 (4 | 16) · OCTET STRING

This MIB object represents the address of the H.248 controller. This object is of the type csb248ControllerAddressType.

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

This MIB object represents the port of the H.248 controller.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

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 MIB object represents the account name of the source which was involved in policy violation.

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 MIB object represents the scope of the SLA policy which has been violated.

Counter64 (0..18446744073709551615)

This MIB object represents the currently defined policy limits. If the SLA is for max-num-calls, this value is the configured maximum number of calls. If the SLA is for max-call-rate, this value is the configured maximum number of calls per minute. If the SLA is for max-bandwidth, this value is the configured maximum bidirection bandwidth in bps. This object replaces the csbSLAPolicyLimit object.

Counter64 (0..18446744073709551615)

This MIB object represents the actual usage value for the event which leads to the SLA violation, like if maximum number of calls are more than SLA policy then actual value of this parameter/event. If the SLA is for max-num-calls, this value is the current number of calls. If the SLA is for max-call-rate, this value is the current number of calls per minute. If the SLA is for max-bandwidth, this value is the current bidirection bandwidth in bps. This object replaces the csbSLACurrentUsage object.

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 MIB object represents the type of SLA policy violation event.

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 MIB object represents the SLA policy restriction description means the violation of the call policy has resulted into which type of restriction, like if maximum number of calls exceeds then it will restrict the number of concurrent calls.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The current Threshold Level of the measured object. The levels are Major, Minor, Critical.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The current Threshold Level of the measured object. The levels are Major, Minor, Critical.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The current Threshold Level of the measured object. The levels are Major, Minor, Critical.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The current Threshold Level of the measured object. The levels are Major, Minor, Critical.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The current Threshold Level of the measured object. The levels are Major, Minor, Critical.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The current Threshold Level of the measured object. The levels are Major, Minor, Critical.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The current Threshold Level of the measured object. The levels are Major, Minor, Critical.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.

INTEGER1 = signaling2 = media3 = cac · Integer32

This object identifies the subsystem or application module which generated the alarm. The subsystem which is involved in call establishment only is of type signaling. The subsystem which handles the traffic/data (RTP/RTCP packets) is of type media. The subsystem which is involved in call admission control is of type CAC.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object identifies the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities except that info is added. cleared - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate - Indicates that the severity level cannot be determined. critical - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.

Integer32 (0..2147483647)

This object identifies the alarm identification number. It is a unique number generated by agent in the incremented order like for the first alarm it is 1, for second alarm it is 2 and so on.

OCTET STRING SIZE (0..80)

This object identifies the time when alarm was generated. It is in the form: dow mon dd hh:mm:ss zzz yyyy where: dow is the day of the week (Sun, Mon, Tue, Wed, Thu, Fri, Sat). mon is the month (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). dd is the day of the month (01 through 31), as two decimal digits. hh is the hour of the day (00 through 23), as two decimal digits. mm is the minute within the hour (00 through 59), as two decimal digits. ss is the second within the minute (00 through 61), as two decimal digits. zzz is the time zone (and may reflect daylight savings time). Standard time zone abbreviations include those recognized by the method parse. If time zone information is not available, then zzz is empty - that is, it consists of no characters at all. yyyy is the year, as four decimal digits.

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 MIB object represents the name of the SBC service configured on the service card.

CsbQOSAlertScopeType1 = global2 = adjacencyThis textual convention describes the scope to which value of QOS parameter is applicable. There are two scopes supported. QOS parameters can be reported for these two scopes global scope and adjacency scope. The values are: global - This scope represents the global level and does not corresponds to individual adjacency level scope. adjacency - This scope represents the QOS notifications for one particular adjacency. · Integer32

This object represents that the value of QOS parameter is applicable at which scope. QOS parameters can be calculated both at global as well as adjacency scope.

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 MIB object represents the name of the adjacency. The length of this object will be zero if the adjacency name is not defined.

CiscoSbcPeriodicStatsInterval1 = fiveMinute2 = fifteenMinute3 = oneHour4 = oneDayThis textual convention represents the interval values for which the periodic stats and history stats are to be displayed. fiveMinute - Interval to display current/previous 5 minutes statistics information. fifteenMinute - Interval to display current/previous 15 minutes statistics information. oneHour - Interval to display current/previous one hour statistics information. oneDay - Interval to display current/previous one day statistics information. · Integer32

This object indicates the interval for which the periodic statistics information is to be displayed. The interval values can be 5 min, 15 mins, 1 hour or 1 day.

Unsigned32

This object indicates the current measured value of the QOS object.

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

The previous threshold level of the measured object. The levels are Major, Minor, Critical.

Counter32 · occurrences

This object represents the number of times this QOS object, has entered normal level.

Counter32 · occurrences

This object represents number of times the QOS object, has entered minor level.

Counter32 · occurrences

This object represents the number of times the QOS object, has entered critical level.

OCTET STRING

This MIB object represents the description of the conditions due to which the notification is raised.

Counter32 · occurrences

This object represents number the of times the QOS object, has entered major level.