EZ5 MIB Catalog

PINT-MIB

2001-02-01

Download PINT-MIB.txt Open PINT-MIB.txt in a new tab

This MIB defines the objects necessary to monitor PINT Services

SCALARS (2) · TABLES (6)

Scalars (2)

NameOID
pintReleaseNumber1.3.6.1.2.1.93.1.1
pintSysContact1.3.6.1.2.1.93.1.2

Tables (6)

NameOID
pintApplInstallPkgTableaugments sysApplInstallPkgTable (SYSAPPL-MIB)1.3.6.1.2.1.93.1.3
pintRegisteredGatewayTableaugments sysApplInstallPkgTable (SYSAPPL-MIB)1.3.6.1.2.1.93.1.4
pintServerGlobalStatsTable1.3.6.1.2.1.93.2.1.1
pintServerClientStatsTable1.3.6.1.2.1.93.2.2.1
pintServerUserIdStatsTable1.3.6.1.2.1.93.2.3.1
pintServerGatewayStatsTable1.3.6.1.2.1.93.2.4.1

END OF TOC

Scalar details

pintReleaseNumber

1.3.6.1.2.1.93.1.1

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

An indication of version of the PINT protocol supported by this agent.

pintSysContact

1.3.6.1.2.1.93.1.2

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

Contact information related to the administration of the PINT services.

Table details

pintApplInstallPkgTable

1.3.6.1.2.1.93.1.3

augments sysApplInstallPkgTable (SYSAPPL-MIB)

Index: sysApplInstallPkgIndex

Table describing the PINT applications that are installed.

from SYSAPPL-MIB

sysApplInstallPkgIndex

Unsigned32 (1..4294967295)

An integer used only for indexing purposes. Generally monotonically increasing from 1 as new applications are installed. The value for each installed application must remain constant at least from one re-initialization of the network management entity which implements this MIB module to the next re-initialization. The specific value is meaningful only within a given SNMP entity. A sysApplInstallPkgIndex value must not be re-used until the next agent entity restart in the event the installed application entry is deleted.

pintApplInstallPkgDescription

1.3.6.1.2.1.93.1.3.1.1

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

Textual description of the installed PINT application.

pintRegisteredGatewayTable

1.3.6.1.2.1.93.1.4

augments sysApplInstallPkgTable (SYSAPPL-MIB)

Index: sysApplInstallPkgIndex

Table describing the registered gateway applications.

from SYSAPPL-MIB

sysApplInstallPkgIndex

Unsigned32 (1..4294967295)

An integer used only for indexing purposes. Generally monotonically increasing from 1 as new applications are installed. The value for each installed application must remain constant at least from one re-initialization of the network management entity which implements this MIB module to the next re-initialization. The specific value is meaningful only within a given SNMP entity. A sysApplInstallPkgIndex value must not be re-used until the next agent entity restart in the event the installed application entry is deleted.

pintRegisteredGatewayName

1.3.6.1.2.1.93.1.4.1.1

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

Name of the registered gateway.

pintRegisteredGatewayDescription

1.3.6.1.2.1.93.1.4.1.2

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

Textual description of the registered gateway.

pintServerGlobalStatsTable

1.3.6.1.2.1.93.2.1.1

Index: pintServerServiceTypeIndex · pintServerPerfStatPeriodIndex

Table displaying the monitored global server statistics.

pintServerServiceTypeIndex

1.3.6.1.2.1.93.2.1.1.1.1

PintServiceType1 = r2C2 = r2F3 = r2FB4 = r2HCThis TC describes the type of a PINT service. · Integer32

The unique identifier of the monitored service.

pintServerPerfStatPeriodIndex

1.3.6.1.2.1.93.2.1.1.1.2

PintPerfStatPeriod1 = last30sec2 = last15min3 = last24Hr4 = sinceRebootThis TC describes the statistics period of time. Note that the values of the counters indexed with a value SinceReboot(4) can be potentially affected by a counter rollover. It is the responsibility of the application using this object to take into account that the counter has been zeroed each time it reached a value of (2**32-1). · Integer32

Time period for which the performance statistics are requested from the pint server.

pintServerGlobalCallsReceived

1.3.6.1.2.1.93.2.1.1.1.3

Counter32

Number of received global calls.

pintServerGlobalSuccessfulCalls

1.3.6.1.2.1.93.2.1.1.1.4

Counter32

Number of global successful calls.

pintServerGlobalDisconnectedCalls

1.3.6.1.2.1.93.2.1.1.1.5

Counter32

Number of global disconnected (failed) calls.

pintServerGlobalDisCUAutFCalls

1.3.6.1.2.1.93.2.1.1.1.6

Counter32

Number of global calls that were disconnected because of client or user authorization failure.

pintServerGlobalDisServProbCalls

1.3.6.1.2.1.93.2.1.1.1.7

Counter32

Number of global calls that were disconnected because of server problems.

pintServerGlobalDisGatProbCalls

1.3.6.1.2.1.93.2.1.1.1.8

Counter32

Number of global calls that were disconnected because of gateway problems.

pintServerClientStatsTable

1.3.6.1.2.1.93.2.2.1

Index: pintServerClientAddress · pintServerServiceTypeIndex · pintServerPerfStatPeriodIndex

Table displaying the monitored server client statistics.

pintServerClientAddress

1.3.6.1.2.1.93.2.2.1.1.1

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

The unique identifier of the monitored client identified by its address represented as as a string.

pintServerClientCallsReceived

1.3.6.1.2.1.93.2.2.1.1.2

Counter32

Number of calls received from the specific client.

pintServerClientSuccessfulCalls

1.3.6.1.2.1.93.2.2.1.1.3

Counter32

Number of calls from the client successfully completed.

pintServerClientDisconnectedCalls

1.3.6.1.2.1.93.2.2.1.1.4

Counter32

Number of calls received from the client, and that were disconnected (failed).

pintServerClientDisCAutFCalls

1.3.6.1.2.1.93.2.2.1.1.5

Counter32

Number of calls from the client that were disconnected because of client authorization failure.

pintServerClientDisEFProbCalls

1.3.6.1.2.1.93.2.2.1.1.6

Counter32

Number of calls from the client that were disconnected because of egress facility problems.

pintServerUserIdStatsTable

1.3.6.1.2.1.93.2.3.1

Index: pintServerUserIdName · pintServerServiceTypeIndex · pintServerPerfStatPeriodIndex

Table displaying the monitored Pint service user statistics.

pintServerUserIdName

1.3.6.1.2.1.93.2.3.1.1.1

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

The unique identifier of the monitored user identified by its name.

pintServerUserIdCallsReceived

1.3.6.1.2.1.93.2.3.1.1.2

Counter32

Number of calls received from the specific user.

pintServerUserIdSuccessfulCalls

1.3.6.1.2.1.93.2.3.1.1.3

Counter32

Number of calls from the user successfully completed.

pintServerUserIdDisconnectedCalls

1.3.6.1.2.1.93.2.3.1.1.4

Counter32

Number of calls received from the user that were disconnected (failed).

pintServerUserIdDiscUIdAFailCalls

1.3.6.1.2.1.93.2.3.1.1.5

Counter32

Number of calls from the user that were disconnected because of user authorization failure.

pintServerUserIdEFProbCalls

1.3.6.1.2.1.93.2.3.1.1.6

Counter32

Number of calls from the user that were disconnected because of egress facility problems.

pintServerGatewayStatsTable

1.3.6.1.2.1.93.2.4.1

Index: pintRegisteredGatewayName · pintServerServiceTypeIndex · pintServerPerfStatPeriodIndex

Table displaying the monitored gateway statistics.

pintServerGatewayCallsReceived

1.3.6.1.2.1.93.2.4.1.1.1

Counter32

Number of calls received at the specified gateway.

pintServerGatewaySuccessfulCalls

1.3.6.1.2.1.93.2.4.1.1.2

Counter32

Number of calls successfully completed at the specified gateway.

pintServerGatewayDisconnectedCalls

1.3.6.1.2.1.93.2.4.1.1.3

Counter32

Number of calls that were disconnected (failed) at the specified gateway.

↑ To TOC