jnxMbgTotalAuthRequests
1.3.6.1.4.1.2636.3.66.3.1.1.1
Counter64 (0..18446744073709551615)
Total authentication requests made.
JUNIPER-MOBILE-GATEWAY-AAA-MIB
2011-11-15
This module defines objects pertaining to Mobile-Edge AAA Services
Download JUNIPER-MOBILE-GATEWAY-AAA-MIB.txt Open JUNIPER-MOBILE-GATEWAY-AAA-MIB.txt in a new tab
SCALARS (39) · TABLES (9) · TRAPS (12)
Scalars (39)
Tables (9)
Traps (12)
END OF TOC
Scalar details
jnxMbgTotalAuthAccepts
1.3.6.1.4.1.2636.3.66.3.1.1.2
Counter64 (0..18446744073709551615)
Total authentication requests that were accepted.
jnxMbgTotalAuthRejects
1.3.6.1.4.1.2636.3.66.3.1.1.3
Counter64 (0..18446744073709551615)
Total authentication requests that were rejected.
jnxMbgTotalAuthChallenges
1.3.6.1.4.1.2636.3.66.3.1.1.4
Counter64 (0..18446744073709551615)
Total authentication challenges received.
jnxMbgTotalAuthRequestTimeouts
1.3.6.1.4.1.2636.3.66.3.1.1.5
Counter64 (0..18446744073709551615)
Total authentication requests that timed out.
jnxMbgTotalAuthRequestTxErrors
1.3.6.1.4.1.2636.3.66.3.1.1.6
Counter64 (0..18446744073709551615)
Total authentication requests transmit errors.
jnxMbgTotalAuthResponseErrors
1.3.6.1.4.1.2636.3.66.3.1.1.7
Counter64 (0..18446744073709551615)
Total authentication response errors.
jnxMbgTotalAuthPendingRequests
1.3.6.1.4.1.2636.3.66.3.1.1.8
Counter64 (0..18446744073709551615)
Total pending authentication requests.
jnxMbgTotalAcctRequests
1.3.6.1.4.1.2636.3.66.3.1.2.1
Counter64 (0..18446744073709551615)
Total accounting requests made.
jnxMbgTotalAcctResponses
1.3.6.1.4.1.2636.3.66.3.1.2.2
Counter64 (0..18446744073709551615)
Total accounting responses that were received.
jnxMbgTotalAcctRequestTimeouts
1.3.6.1.4.1.2636.3.66.3.1.2.3
Counter64 (0..18446744073709551615)
Total accounting requests that timed out.
jnxMbgTotalAcctRequestTxErrors
1.3.6.1.4.1.2636.3.66.3.1.2.4
Counter64 (0..18446744073709551615)
Total accounting requests transmit errors.
jnxMbgTotalAcctResponseErrors
1.3.6.1.4.1.2636.3.66.3.1.2.5
Counter64 (0..18446744073709551615)
Total accounting response errors.
jnxMbgTotalAcctPendingRequests
1.3.6.1.4.1.2636.3.66.3.1.2.6
Counter64 (0..18446744073709551615)
Total pending accounting requests.
jnxMbgTotalDynAuthReceived
1.3.6.1.4.1.2636.3.66.3.1.3.1
Counter64 (0..18446744073709551615)
Total dyn-req received.
jnxMbgTotalDynAuthCoaReceived
1.3.6.1.4.1.2636.3.66.3.1.3.2
Counter64 (0..18446744073709551615)
Total CoA received.
jnxMbgTotalDynAuthDmReceived
1.3.6.1.4.1.2636.3.66.3.1.3.3
Counter64 (0..18446744073709551615)
Total DM received.
jnxMbgTotalDynAuthCoaAckSent
1.3.6.1.4.1.2636.3.66.3.1.3.4
Counter64 (0..18446744073709551615)
Total CoA Ack sent.
jnxMbgTotalDynAuthCoaNackSent
1.3.6.1.4.1.2636.3.66.3.1.3.5
Counter64 (0..18446744073709551615)
Total CoA Nack sent.
jnxMbgTotalDynAuthDmAckSent
1.3.6.1.4.1.2636.3.66.3.1.3.6
Counter64 (0..18446744073709551615)
Total DM Ack sent.
jnxMbgTotalDynAuthDmNackSent
1.3.6.1.4.1.2636.3.66.3.1.3.7
Counter64 (0..18446744073709551615)
Total DM Nack sent.
jnxMbgTotalDynAuthDropped
1.3.6.1.4.1.2636.3.66.3.1.3.8
Counter64 (0..18446744073709551615)
Total dyn-req that were dropped.
jnxMbgTotalDynAuthDuplicate
1.3.6.1.4.1.2636.3.66.3.1.3.9
Counter64 (0..18446744073709551615)
Total duplicate dyn-req detected.
jnxMbgTotalDynAuthForwarded
1.3.6.1.4.1.2636.3.66.3.1.3.10
Counter64 (0..18446744073709551615)
Total dyn-req forwarded to anchor instance.
jnxMbgTotalDynAuthTimeouts
1.3.6.1.4.1.2636.3.66.3.1.3.11
Counter64 (0..18446744073709551615)
Total dyn-req timed out.
jnxMbgTotalDynAuthDelivered
1.3.6.1.4.1.2636.3.66.3.1.3.12
Counter64 (0..18446744073709551615)
Total dyn-req that were delivered to application.
jnxMbgTotalDynAuthErrors
1.3.6.1.4.1.2636.3.66.3.1.3.13
Counter64 (0..18446744073709551615)
Total dyn-req that had errors during processing.
jnxMbgTotalDynAuthUnknownClnts
1.3.6.1.4.1.2636.3.66.3.1.3.14
Counter64 (0..18446744073709551615)
Total dyn-req received from unknown clients.
jnxMbgTotalDynAuthInvalidCode
1.3.6.1.4.1.2636.3.66.3.1.3.15
Counter64 (0..18446744073709551615)
Total dyn-req received with invalid RADIUS code.
jnxMbgTotalDynAuthInvalidAuth
1.3.6.1.4.1.2636.3.66.3.1.3.16
Counter64 (0..18446744073709551615)
Total dyn-req received with invalid RADIUS authenticator.
jnxMbgTotalDynAuthInvalidChId
1.3.6.1.4.1.2636.3.66.3.1.3.17
Counter64 (0..18446744073709551615)
Total dyn-req received with invalid or missing Charging Id.
jnxMbgTotalDynAuthMapErrors
1.3.6.1.4.1.2636.3.66.3.1.3.18
Counter64 (0..18446744073709551615)
Total dyn-req that had session mapping errors during processing.
jnxMbgTotalDynAuthInvalidTrId
1.3.6.1.4.1.2636.3.66.3.1.3.19
Counter64 (0..18446744073709551615)
Total dyn-req with invalid transaction id during processing.
jnxMbgAAAServerName
1.3.6.1.4.1.2636.3.66.3.1.7.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies the server on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgPendQWaterMarkType
1.3.6.1.4.1.2636.3.66.3.1.7.4
JnxMbgQueueWaterMarkType0 = unknown1 = high2 = lowThe type of a queue threshold - high or low. · Integer32
The type of the pending queue water mark crossed - High or Low.
jnxMbgPendQWaterMarkValue
1.3.6.1.4.1.2636.3.66.3.1.7.5
Integer32
The water mark value for the pending queue.
jnxMbgPendQLength
1.3.6.1.4.1.2636.3.66.3.1.7.6
Counter32
The size of the pending queue.
Table details
jnxMbgRadiusAuthServerTable
1.3.6.1.4.1.2636.3.66.3.1.4
Index: jnxMbgRadiusAuthServerName
The table lists RADIUS servers used for authentication.
jnxMbgRadiusAuthServerName
1.3.6.1.4.1.2636.3.66.3.1.4.1.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..32) · OCTET STRING · hint 255a
A name which uniquely identifies this server on the mobile-gateway.
jnxMbgRadiusAuthServerInetAddressType
1.3.6.1.4.1.2636.3.66.3.1.4.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The type of IP address used for this server.
jnxMbgRadiusAuthServerInetAddress
1.3.6.1.4.1.2636.3.66.3.1.4.1.3
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The IP address used for this server.
jnxMbgRadiusAuthServerInetPort
1.3.6.1.4.1.2636.3.66.3.1.4.1.4
InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d
The UDP port number on the server to which authentication requests are sent.
jnxMbgRadiusAuthServerRoutingInstance
1.3.6.1.4.1.2636.3.66.3.1.4.1.5
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The routing-instance used while contacting this server. If not configured, the default routing-instance will be used.
jnxMbgRadiusAuthServerStatus
1.3.6.1.4.1.2636.3.66.3.1.4.1.6
JnxMbgAAAServerStatus0 = unknown1 = active2 = deadServer status - dead or active. · Integer32
The deprecated status of the server.
jnxMbgRadiusAuthServerRequests
1.3.6.1.4.1.2636.3.66.3.1.4.1.7
Counter64 (0..18446744073709551615)
Number of Access-Requests that have been sent to this server.
jnxMbgRadiusAuthServersRetransmissions
1.3.6.1.4.1.2636.3.66.3.1.4.1.8
Counter64 (0..18446744073709551615)
Number of Access-Requests that have been retransmitted this server.
jnxMbgRadiusAuthServerAccepts
1.3.6.1.4.1.2636.3.66.3.1.4.1.9
Counter64 (0..18446744073709551615)
Number of Access-Accepts that have been received from this server.
jnxMbgRadiusAuthServerRejects
1.3.6.1.4.1.2636.3.66.3.1.4.1.10
Counter64 (0..18446744073709551615)
Number of Access-Rejects that have been received from this server.
jnxMbgRadiusAuthServerChallenges
1.3.6.1.4.1.2636.3.66.3.1.4.1.11
Counter64 (0..18446744073709551615)
Number of Access-Challenges that have been received from this server.
jnxMbgRadiusAuthServerMalformedResponses
1.3.6.1.4.1.2636.3.66.3.1.4.1.12
Counter64 (0..18446744073709551615)
Number of Malformed Responses have been received from this server. A response could either accept, reject or challenge.
jnxMbgRadiusAuthServerBadAuthenticators
1.3.6.1.4.1.2636.3.66.3.1.4.1.13
Counter64 (0..18446744073709551615)
Number of responses with invalid authenticators received from this server. A response could either accept, reject or challenge.
jnxMbgRadiusAuthServerPendingRequests
1.3.6.1.4.1.2636.3.66.3.1.4.1.14
Counter64 (0..18446744073709551615)
Number of requests to this server pending authentication.
jnxMbgRadiusAuthServerTimeouts
1.3.6.1.4.1.2636.3.66.3.1.4.1.15
Counter64 (0..18446744073709551615)
Number of requests to this server that timed out.
jnxMbgRadiusAuthServerUnknownTypes
1.3.6.1.4.1.2636.3.66.3.1.4.1.16
Counter64 (0..18446744073709551615)
Number of responses received from this RADIUS server with unknown types.
jnxMbgRadiusAuthServerPacketsDropped
1.3.6.1.4.1.2636.3.66.3.1.4.1.17
Counter64 (0..18446744073709551615)
Number of responses received from this RADIUS server that were dropped for some other reason.
jnxMbgRadiusAuthServerRTTAvg
1.3.6.1.4.1.2636.3.66.3.1.4.1.18
Integer32
Average round-trip time (in ms) for this server.
jnxMbgRadiusAuthServerRTTMin
1.3.6.1.4.1.2636.3.66.3.1.4.1.19
Integer32
Minimum round-trip time (in ms) seen for this server.
jnxMbgRadiusAuthServerRTTMax
1.3.6.1.4.1.2636.3.66.3.1.4.1.20
Integer32
Maximum round-trip time (in ms) seen for this server.
jnxMbgRadiusAcctServerTable
1.3.6.1.4.1.2636.3.66.3.1.5
Index: jnxMbgRadiusAcctServerName
The table lists RADIUS servers used for accounting.
jnxMbgRadiusAcctServerName
1.3.6.1.4.1.2636.3.66.3.1.5.1.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..32) · OCTET STRING · hint 255a
A name which uniquely identifies this server on the mobile-gateway.
jnxMbgRadiusAcctServerInetAddressType
1.3.6.1.4.1.2636.3.66.3.1.5.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The type of IP address used for this server.
jnxMbgRadiusAcctServerInetAddress
1.3.6.1.4.1.2636.3.66.3.1.5.1.3
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The IP address used for this server.
jnxMbgRadiusAcctServerInetPort
1.3.6.1.4.1.2636.3.66.3.1.5.1.4
InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d
The UDP port number on the server to which accounting requests are sent.
jnxMbgRadiusAcctServerRoutingInstance
1.3.6.1.4.1.2636.3.66.3.1.5.1.5
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The routing-instance used while contacting this server. If not configured, the default routing-instance will be used.
jnxMbgRadiusAcctServerStatus
1.3.6.1.4.1.2636.3.66.3.1.5.1.6
JnxMbgAAAServerStatus0 = unknown1 = active2 = deadServer status - dead or active. · Integer32
The deprecated status of the server.
jnxMbgRadiusAcctServerRequests
1.3.6.1.4.1.2636.3.66.3.1.5.1.7
Counter64 (0..18446744073709551615)
Number of Accounting-Requests that have been sent to this server.
jnxMbgRadiusAcctServersRetransmissions
1.3.6.1.4.1.2636.3.66.3.1.5.1.8
Counter64 (0..18446744073709551615)
Number of Accounting-Requests that have been retransmitted this server.
jnxMbgRadiusAcctServerResponses
1.3.6.1.4.1.2636.3.66.3.1.5.1.9
Counter64 (0..18446744073709551615)
Number of Accounting-Responses that have been received from this server.
jnxMbgRadiusAcctServerMalformedResponses
1.3.6.1.4.1.2636.3.66.3.1.5.1.10
Counter64 (0..18446744073709551615)
Number of Malformed Responses have been received from this server.
jnxMbgRadiusAcctServerBadAuthenticators
1.3.6.1.4.1.2636.3.66.3.1.5.1.11
Counter64 (0..18446744073709551615)
Number of responses with invalid authenticators received from this server.
jnxMbgRadiusAcctServerPendingRequests
1.3.6.1.4.1.2636.3.66.3.1.5.1.12
Counter64 (0..18446744073709551615)
Number of requests to this server which are yet to be sent or waiting for response.
jnxMbgRadiusAcctServerTimeouts
1.3.6.1.4.1.2636.3.66.3.1.5.1.13
Counter64 (0..18446744073709551615)
Number of requests to this server that timed out.
jnxMbgRadiusAcctServerUnknownTypes
1.3.6.1.4.1.2636.3.66.3.1.5.1.14
Counter64 (0..18446744073709551615)
Number of responses received from this RADIUS server with unknown types.
jnxMbgRadiusAcctServerPacketsDropped
1.3.6.1.4.1.2636.3.66.3.1.5.1.15
Counter64 (0..18446744073709551615)
Number of responses received from this RADIUS server that were dropped for some other reason.
jnxMbgRadiusAcctServerRTTAvg
1.3.6.1.4.1.2636.3.66.3.1.5.1.16
Integer32
Average round-trip time (in ms) for this server.
jnxMbgRadiusAcctServerRTTMin
1.3.6.1.4.1.2636.3.66.3.1.5.1.17
Integer32
Minimum round-trip time (in ms) seen for this server.
jnxMbgRadiusAcctServerRTTMax
1.3.6.1.4.1.2636.3.66.3.1.5.1.18
Integer32
Maximum round-trip time (in ms) seen for this server.
jnxMbgDynAuthClientTable
1.3.6.1.4.1.2636.3.66.3.1.6
Index: jnxMbgRadiusAcctServerName
The table lists RADIUS clients sending Dynamic Authorization requests.
jnxMbgDynAuthClientName
1.3.6.1.4.1.2636.3.66.3.1.6.1.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..32) · OCTET STRING · hint 255a
A name which uniquely identifies this client on the mobile-gateway.
jnxMbgDynAuthClientInAddrType
1.3.6.1.4.1.2636.3.66.3.1.6.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The type of IP address used for this client.
jnxMbgDynAuthClientInetAddress
1.3.6.1.4.1.2636.3.66.3.1.6.1.3
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The IP address of this client.
jnxMbgDynAuthClientCoaReceived
1.3.6.1.4.1.2636.3.66.3.1.6.1.4
Counter64 (0..18446744073709551615)
CoA requests received from this client.
jnxMbgDynAuthClientDmReceived
1.3.6.1.4.1.2636.3.66.3.1.6.1.5
Counter64 (0..18446744073709551615)
DM requests received from this client.
jnxMbgDynAuthClientCoaAckSent
1.3.6.1.4.1.2636.3.66.3.1.6.1.6
Counter64 (0..18446744073709551615)
CoA Ack responses sent to this client.
jnxMbgDynAuthClientCoaNackSent
1.3.6.1.4.1.2636.3.66.3.1.6.1.7
Counter64 (0..18446744073709551615)
CoA Nack responses sent to this client.
jnxMbgDynAuthClientDmAckSent
1.3.6.1.4.1.2636.3.66.3.1.6.1.8
Counter64 (0..18446744073709551615)
DM Ack responses sent to this client.
jnxMbgDynAuthClientDmNackSent
1.3.6.1.4.1.2636.3.66.3.1.6.1.9
Counter64 (0..18446744073709551615)
DM Nack responses sent to this client.
jnxMbgDynAuthClientDropped
1.3.6.1.4.1.2636.3.66.3.1.6.1.10
Counter64 (0..18446744073709551615)
Requests received from this server that were dropped.
jnxMbgDynAuthClientDuplicate
1.3.6.1.4.1.2636.3.66.3.1.6.1.11
Counter64 (0..18446744073709551615)
Duplicate requests received from this client.
jnxMbgDynAuthClientForwarded
1.3.6.1.4.1.2636.3.66.3.1.6.1.12
Counter64 (0..18446744073709551615)
Requests received from this client that were forwarded to anchor instance.
jnxMbgDynAuthClientTimeouts
1.3.6.1.4.1.2636.3.66.3.1.6.1.13
Counter64 (0..18446744073709551615)
Requests received from this client that timed out.
jnxMbgDynAuthClientDelivered
1.3.6.1.4.1.2636.3.66.3.1.6.1.14
Counter64 (0..18446744073709551615)
Requests received from this client that were delivered to application.
jnxMbgDynAuthClientErrors
1.3.6.1.4.1.2636.3.66.3.1.6.1.15
Counter64 (0..18446744073709551615)
Requests received from this client that had errors during processing.
jnxMbgDynAuthClientInvalidAuth
1.3.6.1.4.1.2636.3.66.3.1.6.1.17
Counter64 (0..18446744073709551615)
Requests received from this client with invalid RADIUS authenticator.
jnxMbgDynAuthClientInvalidCode
1.3.6.1.4.1.2636.3.66.3.1.6.1.18
Counter64 (0..18446744073709551615)
Requests received from this client with invalid RADIUS code.
jnxMbgDynAuthClientInvalidChId
1.3.6.1.4.1.2636.3.66.3.1.6.1.19
Counter64 (0..18446744073709551615)
Requests received from this client with invalid or missing Charging Id.
jnxMbgDynAuthClientMapErrors
1.3.6.1.4.1.2636.3.66.3.1.6.1.20
Counter64 (0..18446744073709551615)
Requests received from this client that had session mapping errors during processing.
jnxMbgAAAAuthStatsTable
1.3.6.1.4.1.2636.3.66.3.1.8
Index: jnxMbgGwIndex
The table lists authentication counters.
jnxMbgGwIndex
Unsigned32
Gateway Index.
jnxMbgTtlAuthRequests
1.3.6.1.4.1.2636.3.66.3.1.8.1.1
Counter64 (0..18446744073709551615)
Total authentication requests made.
jnxMbgTtlAuthAccepts
1.3.6.1.4.1.2636.3.66.3.1.8.1.2
Counter64 (0..18446744073709551615)
Total authentication requests that were accepted.
jnxMbgTtlAuthRejects
1.3.6.1.4.1.2636.3.66.3.1.8.1.3
Counter64 (0..18446744073709551615)
Total authentication requests that were rejected.
jnxMbgTtlAuthChallenges
1.3.6.1.4.1.2636.3.66.3.1.8.1.4
Counter64 (0..18446744073709551615)
Total authentication challenges received.
jnxMbgTtlAuthRequestTimeouts
1.3.6.1.4.1.2636.3.66.3.1.8.1.5
Counter64 (0..18446744073709551615)
Total authentication requests that timed out.
jnxMbgTtlAuthRequestTxErrors
1.3.6.1.4.1.2636.3.66.3.1.8.1.6
Counter64 (0..18446744073709551615)
Total authentication requests transmit errors.
jnxMbgTtlAuthResponseErrors
1.3.6.1.4.1.2636.3.66.3.1.8.1.7
Counter64 (0..18446744073709551615)
Total authentication response errors.
jnxMbgTtlAuthPendingRequests
1.3.6.1.4.1.2636.3.66.3.1.8.1.8
Counter64 (0..18446744073709551615)
Total pending authentication requests.
jnxMbgAAAAcctStatsTable
1.3.6.1.4.1.2636.3.66.3.1.9
Index: jnxMbgGwIndex
The table lists accounting counters.
jnxMbgGwIndex
Unsigned32
Gateway Index.
jnxMbgTtlAcctRequests
1.3.6.1.4.1.2636.3.66.3.1.9.1.1
Counter64 (0..18446744073709551615)
Total accounting requests made.
jnxMbgTtlAcctResp
1.3.6.1.4.1.2636.3.66.3.1.9.1.2
Counter64 (0..18446744073709551615)
Total accounting Resp that were received.
jnxMbgTtlAcctRequestTimeouts
1.3.6.1.4.1.2636.3.66.3.1.9.1.3
Counter64 (0..18446744073709551615)
Total accounting requests that timed out.
jnxMbgTtlAcctRequestTxErrors
1.3.6.1.4.1.2636.3.66.3.1.9.1.4
Counter64 (0..18446744073709551615)
Total accounting requests transmit errors.
jnxMbgTtlAcctResponseErrors
1.3.6.1.4.1.2636.3.66.3.1.9.1.5
Counter64 (0..18446744073709551615)
Total accounting response errors.
jnxMbgTtlAcctPendingRequests
1.3.6.1.4.1.2636.3.66.3.1.9.1.6
Counter64 (0..18446744073709551615)
Total pending accounting requests.
jnxMbgAAADynAuthStatsTable
1.3.6.1.4.1.2636.3.66.3.1.10
Index: jnxMbgGwIndex
The table lists dynamic request statistics counters.
jnxMbgGwIndex
Unsigned32
Gateway Index.
jnxMbgTtlDynAuthReceived
1.3.6.1.4.1.2636.3.66.3.1.10.1.1
Counter64 (0..18446744073709551615)
Total dyn-req received.
jnxMbgTtlDynAuthCoaReceived
1.3.6.1.4.1.2636.3.66.3.1.10.1.2
Counter64 (0..18446744073709551615)
Total CoA received.
jnxMbgTtlDynAuthDmReceived
1.3.6.1.4.1.2636.3.66.3.1.10.1.3
Counter64 (0..18446744073709551615)
Total DM received.
jnxMbgTtlDynAuthCoaAckSent
1.3.6.1.4.1.2636.3.66.3.1.10.1.4
Counter64 (0..18446744073709551615)
Total CoA Ack sent.
jnxMbgTtlDynAuthCoaNackSent
1.3.6.1.4.1.2636.3.66.3.1.10.1.5
Counter64 (0..18446744073709551615)
Total CoA Nack sent.
jnxMbgTtlDynAuthDmAckSent
1.3.6.1.4.1.2636.3.66.3.1.10.1.6
Counter64 (0..18446744073709551615)
Total DM Ack sent.
jnxMbgTtlDynAuthDmNackSent
1.3.6.1.4.1.2636.3.66.3.1.10.1.7
Counter64 (0..18446744073709551615)
Total DM Nack sent.
jnxMbgTtlDynAuthDropped
1.3.6.1.4.1.2636.3.66.3.1.10.1.8
Counter64 (0..18446744073709551615)
Total dyn-req that were dropped.
jnxMbgTtlDynAuthDuplicate
1.3.6.1.4.1.2636.3.66.3.1.10.1.9
Counter64 (0..18446744073709551615)
Total duplicate dyn-req detected.
jnxMbgTtlDynAuthForwarded
1.3.6.1.4.1.2636.3.66.3.1.10.1.10
Counter64 (0..18446744073709551615)
Total dyn-req forwarded to anchor instance.
jnxMbgTtlDynAuthTimeouts
1.3.6.1.4.1.2636.3.66.3.1.10.1.11
Counter64 (0..18446744073709551615)
Total dyn-req timed out.
jnxMbgTtlDynAuthDelivered
1.3.6.1.4.1.2636.3.66.3.1.10.1.12
Counter64 (0..18446744073709551615)
Total dyn-req that were delivered to application.
jnxMbgTtlDynAuthErrors
1.3.6.1.4.1.2636.3.66.3.1.10.1.13
Counter64 (0..18446744073709551615)
Total dyn-req that had errors during processing.
jnxMbgTtlDynAuthUnknownClnts
1.3.6.1.4.1.2636.3.66.3.1.10.1.14
Counter64 (0..18446744073709551615)
Total dyn-req received from unknown clients.
jnxMbgTtlDynAuthInvalidCode
1.3.6.1.4.1.2636.3.66.3.1.10.1.15
Counter64 (0..18446744073709551615)
Total dyn-req received with invalid RADIUS code.
jnxMbgTtlDynAuthInvalidAuth
1.3.6.1.4.1.2636.3.66.3.1.10.1.16
Counter64 (0..18446744073709551615)
Total dyn-req received with invalid RADIUS authenticator.
jnxMbgTtlDynAuthInvalidChId
1.3.6.1.4.1.2636.3.66.3.1.10.1.17
Counter64 (0..18446744073709551615)
Total dyn-req received with invalid or missing Charging Id.
jnxMbgTtlDynAuthMapErrors
1.3.6.1.4.1.2636.3.66.3.1.10.1.18
Counter64 (0..18446744073709551615)
Total dyn-req that had session mapping errors during processing.
jnxMbgTtlDynAuthInvalidTrId
1.3.6.1.4.1.2636.3.66.3.1.10.1.19
Counter64 (0..18446744073709551615)
Total dyn-req with invalid transaction id during processing.
jnxMbgRadiusAuthSrvrTable
1.3.6.1.4.1.2636.3.66.3.1.11
Index: jnxMbgGwIndex · jnxMbgRadiusAuthSrvrName
The table lists RADIUS servers used for authentication.
jnxMbgGwIndex
Unsigned32
Gateway Index.
jnxMbgRadiusAuthSrvrName
1.3.6.1.4.1.2636.3.66.3.1.11.1.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..32) · OCTET STRING · hint 255a
A name which uniquely identifies this server on the mobile-gateway.
jnxMbgRadiusAuthSrvrInetAddrType
1.3.6.1.4.1.2636.3.66.3.1.11.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The type of IP address used for this server.
jnxMbgRadiusAuthSrvrInetAddress
1.3.6.1.4.1.2636.3.66.3.1.11.1.3
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The IP address used for this server.
jnxMbgRadiusAuthSrvrInetPort
1.3.6.1.4.1.2636.3.66.3.1.11.1.4
InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d
The UDP port number on the server to which authentication requests are sent.
jnxMbgRadiusAuthSrvrRtngInstance
1.3.6.1.4.1.2636.3.66.3.1.11.1.5
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The routing-instance used while contacting this server. If not configured, the default routing-instance will be used.
jnxMbgRadiusAuthSrvrStatus
1.3.6.1.4.1.2636.3.66.3.1.11.1.6
JnxMbgAAAServerStatus0 = unknown1 = active2 = deadServer status - dead or active. · Integer32
The current status of the server.
jnxMbgRadiusAuthSrvrRequests
1.3.6.1.4.1.2636.3.66.3.1.11.1.7
Counter64 (0..18446744073709551615)
Number of Access-requests that have been sent to this server.
jnxMbgRadiusAuthSrvrRetrans
1.3.6.1.4.1.2636.3.66.3.1.11.1.8
Counter64 (0..18446744073709551615)
Number of Access-requests that have been retransmitted this server.
jnxMbgRadiusAuthSrvrAccepts
1.3.6.1.4.1.2636.3.66.3.1.11.1.9
Counter64 (0..18446744073709551615)
Number of Access-Accepts that have been received from this server.
jnxMbgRadiusAuthSrvrRejects
1.3.6.1.4.1.2636.3.66.3.1.11.1.10
Counter64 (0..18446744073709551615)
Number of Access-Rejects that have been received from this server.
jnxMbgRadiusAuthSrvrChallenges
1.3.6.1.4.1.2636.3.66.3.1.11.1.11
Counter64 (0..18446744073709551615)
Number of Access-Challenges that have been received from this server.
jnxMbgRadiusAuthSrvrMalformResp
1.3.6.1.4.1.2636.3.66.3.1.11.1.12
Counter64 (0..18446744073709551615)
Number of Malformed Resp have been received from this server. A response could either accept, reject or challenge.
jnxMbgRadiusAuthSrvrBadAuthen
1.3.6.1.4.1.2636.3.66.3.1.11.1.13
Counter64 (0..18446744073709551615)
Number of Resp with invalid authenticators received from this server. A response could either accept, reject or challenge.
jnxMbgRadiusAuthSrvrPendingRqsts
1.3.6.1.4.1.2636.3.66.3.1.11.1.14
Counter64 (0..18446744073709551615)
Number of requests to this server pending authentication.
jnxMbgRadiusAuthSrvrTimeouts
1.3.6.1.4.1.2636.3.66.3.1.11.1.15
Counter64 (0..18446744073709551615)
Number of requests to this server that timed out.
jnxMbgRadiusAuthSrvrUnknownTypes
1.3.6.1.4.1.2636.3.66.3.1.11.1.16
Counter64 (0..18446744073709551615)
Number of Resp received from this RADIUS server with unknown types.
jnxMbgRadiusAuthSrvrPacketsDrop
1.3.6.1.4.1.2636.3.66.3.1.11.1.17
Counter64 (0..18446744073709551615)
Number of Resp received from this RADIUS server that were dropped for some other reason.
jnxMbgRadiusAuthSrvrRTTAvg
1.3.6.1.4.1.2636.3.66.3.1.11.1.18
Gauge32
Average round-trip time (in ms) for this server.
jnxMbgRadiusAuthSrvrRTTMin
1.3.6.1.4.1.2636.3.66.3.1.11.1.19
Gauge32
Minimum round-trip time (in ms) seen for this server.
jnxMbgRadiusAuthSrvrRTTMax
1.3.6.1.4.1.2636.3.66.3.1.11.1.20
Gauge32
Maximum round-trip time (in ms) seen for this server.
jnxMbgRadiusAcctSrvrTable
1.3.6.1.4.1.2636.3.66.3.1.12
Index: jnxMbgGwIndex · jnxMbgRadiusAcctSrvrName
The table lists RADIUS servers used for accounting.
jnxMbgGwIndex
Unsigned32
Gateway Index.
jnxMbgRadiusAcctSrvrName
1.3.6.1.4.1.2636.3.66.3.1.12.1.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..32) · OCTET STRING · hint 255a
A name which uniquely identifies this server on the mobile-gateway.
jnxMbgRadiusAcctSrvrInetAddrType
1.3.6.1.4.1.2636.3.66.3.1.12.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The type of IP address used for this server.
jnxMbgRadiusAcctSrvrInetAddress
1.3.6.1.4.1.2636.3.66.3.1.12.1.3
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The IP address used for this server.
jnxMbgRadiusAcctSrvrInetPort
1.3.6.1.4.1.2636.3.66.3.1.12.1.4
InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d
The UDP port number on the server to which accounting requests are sent.
jnxMbgRadiusAcctSrvrRtngInstance
1.3.6.1.4.1.2636.3.66.3.1.12.1.5
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The routing-instance used while contacting this server. If not configured, the default routing-instance will be used.
jnxMbgRadiusAcctSrvrStatus
1.3.6.1.4.1.2636.3.66.3.1.12.1.6
JnxMbgAAAServerStatus0 = unknown1 = active2 = deadServer status - dead or active. · Integer32
The current status of the server.
jnxMbgRadiusAcctSrvrRequests
1.3.6.1.4.1.2636.3.66.3.1.12.1.7
Counter64 (0..18446744073709551615)
Number of Accounting-requests that have been sent to this server.
jnxMbgRadiusAcctSrvrRetrans
1.3.6.1.4.1.2636.3.66.3.1.12.1.8
Counter64 (0..18446744073709551615)
Number of Accounting-requests that have been retransmitted this server.
jnxMbgRadiusAcctSrvrResp
1.3.6.1.4.1.2636.3.66.3.1.12.1.9
Counter64 (0..18446744073709551615)
Number of Accounting-Resp that have been received from this server.
jnxMbgRadiusAcctSrvrMalformResp
1.3.6.1.4.1.2636.3.66.3.1.12.1.10
Counter64 (0..18446744073709551615)
Number of Malformed Resp have been received from this server.
jnxMbgRadiusAcctSrvrBadAuthen
1.3.6.1.4.1.2636.3.66.3.1.12.1.11
Counter64 (0..18446744073709551615)
Number of Resp with invalid authenticators received from this server.
jnxMbgRadiusAcctSrvrPendingRqsts
1.3.6.1.4.1.2636.3.66.3.1.12.1.12
Counter64 (0..18446744073709551615)
Number of requests to this server which are yet to be sent or waiting for response.
jnxMbgRadiusAcctSrvrTimeouts
1.3.6.1.4.1.2636.3.66.3.1.12.1.13
Counter64 (0..18446744073709551615)
Number of requests to this server that timed out.
jnxMbgRadiusAcctSrvrUnknownTypes
1.3.6.1.4.1.2636.3.66.3.1.12.1.14
Counter64 (0..18446744073709551615)
Number of Resp received from this RADIUS server with unknown types.
jnxMbgRadiusAcctSrvrPacketsDrop
1.3.6.1.4.1.2636.3.66.3.1.12.1.15
Counter64 (0..18446744073709551615)
Number of Resp received from this RADIUS server that were dropped for some other reason.
jnxMbgRadiusAcctSrvrRTTAvg
1.3.6.1.4.1.2636.3.66.3.1.12.1.16
Gauge32
Average round-trip time (in ms) for this server.
jnxMbgRadiusAcctSrvrRTTMin
1.3.6.1.4.1.2636.3.66.3.1.12.1.17
Gauge32
Minimum round-trip time (in ms) seen for this server.
jnxMbgRadiusAcctSrvrRTTMax
1.3.6.1.4.1.2636.3.66.3.1.12.1.18
Gauge32
Maximum round-trip time (in ms) seen for this server.
jnxMbgDynAuthClntTable
1.3.6.1.4.1.2636.3.66.3.1.13
Index: jnxMbgGwIndex · jnxMbgDynAuthClntName
The table lists RADIUS clients sending Dynamic Authorization requests.
jnxMbgGwIndex
Unsigned32
Gateway Index.
jnxMbgDynAuthClntName
1.3.6.1.4.1.2636.3.66.3.1.13.1.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..32) · OCTET STRING · hint 255a
A name which uniquely identifies this client on the mobile-gateway.
jnxMbgDynAuthClntInAddrType
1.3.6.1.4.1.2636.3.66.3.1.13.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The type of IP address used for this client.
jnxMbgDynAuthClntInetAddress
1.3.6.1.4.1.2636.3.66.3.1.13.1.3
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The IP address of this client.
jnxMbgDynAuthClntCoaReceived
1.3.6.1.4.1.2636.3.66.3.1.13.1.4
Counter64 (0..18446744073709551615)
CoA requests received from this client.
jnxMbgDynAuthClntDmReceived
1.3.6.1.4.1.2636.3.66.3.1.13.1.5
Counter64 (0..18446744073709551615)
DM requests received from this client.
jnxMbgDynAuthClntCoaAckSent
1.3.6.1.4.1.2636.3.66.3.1.13.1.6
Counter64 (0..18446744073709551615)
CoA Ack Resp sent to this client.
jnxMbgDynAuthClntCoaNackSent
1.3.6.1.4.1.2636.3.66.3.1.13.1.7
Counter64 (0..18446744073709551615)
CoA Nack Resp sent to this client.
jnxMbgDynAuthClntDmAckSent
1.3.6.1.4.1.2636.3.66.3.1.13.1.8
Counter64 (0..18446744073709551615)
DM Ack Resp sent to this client.
jnxMbgDynAuthClntDmNackSent
1.3.6.1.4.1.2636.3.66.3.1.13.1.9
Counter64 (0..18446744073709551615)
DM Nack Resp sent to this client.
jnxMbgDynAuthClntDropped
1.3.6.1.4.1.2636.3.66.3.1.13.1.10
Counter64 (0..18446744073709551615)
requests received from this server that were dropped.
jnxMbgDynAuthClntDuplicate
1.3.6.1.4.1.2636.3.66.3.1.13.1.11
Counter64 (0..18446744073709551615)
Duplicate requests received from this client.
jnxMbgDynAuthClntForwarded
1.3.6.1.4.1.2636.3.66.3.1.13.1.12
Counter64 (0..18446744073709551615)
requests received from this client that were forwarded to anchor instance.
jnxMbgDynAuthClntTimeouts
1.3.6.1.4.1.2636.3.66.3.1.13.1.13
Counter64 (0..18446744073709551615)
requests received from this client that timed out.
jnxMbgDynAuthClntDelivered
1.3.6.1.4.1.2636.3.66.3.1.13.1.14
Counter64 (0..18446744073709551615)
requests received from this client that were delivered to application.
jnxMbgDynAuthClntErrors
1.3.6.1.4.1.2636.3.66.3.1.13.1.15
Counter64 (0..18446744073709551615)
requests received from this client that had errors during processing.
jnxMbgDynAuthClntInvalidAuth
1.3.6.1.4.1.2636.3.66.3.1.13.1.16
Counter64 (0..18446744073709551615)
requests received from this client with invalid RADIUS authenticator.
jnxMbgDynAuthClntInvalidCode
1.3.6.1.4.1.2636.3.66.3.1.13.1.17
Counter64 (0..18446744073709551615)
requests received from this client with invalid RADIUS code.
jnxMbgDynAuthClntInvalidChId
1.3.6.1.4.1.2636.3.66.3.1.13.1.18
Counter64 (0..18446744073709551615)
requests received from this client with invalid or missing Charging Id.
jnxMbgDynAuthClntMapErrors
1.3.6.1.4.1.2636.3.66.3.1.13.1.19
Counter64 (0..18446744073709551615)
requests received from this client that had session mapping errors during processing.
Trap details
jnxMbgAAAServerUp
1.3.6.1.4.1.2636.3.66.3.0.1
This notification signifies that the specified server has been marked active again. This could be because the server started to respond again. The ServerName identifies the server and the SPIdentfier identifies the session-pic which originated this notification.
jnxMbgAAAServerName
1.3.6.1.4.1.2636.3.66.3.1.7.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies the server on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAAServerDown
1.3.6.1.4.1.2636.3.66.3.0.2
This notification signifies that the specified server has been marked dead. The ServerName identifies the server and the SPIdentfier identifies the session-pic which originated this notification.
jnxMbgAAAServerName
1.3.6.1.4.1.2636.3.66.3.1.7.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies the server on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAANetworkElementUp
1.3.6.1.4.1.2636.3.66.3.0.3
This notification signifies that the specified Network Element has been marked UP. This could be because atleast one server in the network element is active. SPIdentfier identifies the session-pic which originated this notification.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAANetworkElementDown
1.3.6.1.4.1.2636.3.66.3.0.4
This notification signifies that the specified Network Element has been marked DOWN. This could be because none of the servers in the network element is active. SPIdentfier identifies the session-pic which originated this notification.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAANEPendAuthQStatus
1.3.6.1.4.1.2636.3.66.3.0.5
This notification signifies the crossing-over of a watermark (High or Low) of the pending authentication queue length of network element. The NetworkElementName identifies the network element and SPIdentfier identifies the session-pic which originated this notification. jnxMbgPendQWaterMarkType identifies the water mark type (High/Low). jnxMbgPendQWaterMarkValue is the value that has been crossed over. jnxMbgPendQLength is the size of the queue after crossing over.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgPendQWaterMarkType
1.3.6.1.4.1.2636.3.66.3.1.7.4
JnxMbgQueueWaterMarkType0 = unknown1 = high2 = lowThe type of a queue threshold - high or low. · Integer32
The type of the pending queue water mark crossed - High or Low.
jnxMbgPendQWaterMarkValue
1.3.6.1.4.1.2636.3.66.3.1.7.5
Integer32
The water mark value for the pending queue.
jnxMbgPendQLength
1.3.6.1.4.1.2636.3.66.3.1.7.6
Counter32
The size of the pending queue.
jnxMbgAAANEPendAcctQStatus
1.3.6.1.4.1.2636.3.66.3.0.6
This notification signifies the crossing-over of a watermark (High or Low) of the pending accounting queue length of network element. The NetworkElementName identifies the network element and SPIdentfier identifies the session-pic which originated this notification. jnxMbgPendQWaterMarkType identifies the water mark type (High/Low). jnxMbgPendQWaterMarkValue is the value that has been crossed over. jnxMbgPendQLength is the size of the queue after crossing over.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgPendQWaterMarkType
1.3.6.1.4.1.2636.3.66.3.1.7.4
JnxMbgQueueWaterMarkType0 = unknown1 = high2 = lowThe type of a queue threshold - high or low. · Integer32
The type of the pending queue water mark crossed - High or Low.
jnxMbgPendQWaterMarkValue
1.3.6.1.4.1.2636.3.66.3.1.7.5
Integer32
The water mark value for the pending queue.
jnxMbgPendQLength
1.3.6.1.4.1.2636.3.66.3.1.7.6
Counter32
The size of the pending queue.
jnxMbgAAARadiusServerUp
1.3.6.1.4.1.2636.3.66.3.0.7
This notification signifies that the specified server has been marked active again. This could be because the server started to respond again. The ServerName identifies the server and the SPIdentfier identifies the session-pic which originated this notification.
jnxMbgGwIndex
1.3.6.1.4.1.2636.3.66.4.1.1.1
Unsigned32
Gateway Index.
jnxMbgGwName
1.3.6.1.4.1.2636.3.66.4.1.1.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
Gateway Name.
jnxMbgAAAServerName
1.3.6.1.4.1.2636.3.66.3.1.7.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies the server on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAARadiusServerDown
1.3.6.1.4.1.2636.3.66.3.0.8
This notification signifies that the specified server has been marked dead. The ServerName identifies the server and the SPIdentfier identifies the session-pic which originated this notification.
jnxMbgGwIndex
1.3.6.1.4.1.2636.3.66.4.1.1.1
Unsigned32
Gateway Index.
jnxMbgGwName
1.3.6.1.4.1.2636.3.66.4.1.1.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
Gateway Name.
jnxMbgAAAServerName
1.3.6.1.4.1.2636.3.66.3.1.7.1
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies the server on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAARadiusNetworkElementUp
1.3.6.1.4.1.2636.3.66.3.0.9
This notification signifies that the specified Network Element has been marked UP. This could be because atleast one server in the network element is active. SPIdentfier identifies the session-pic which originated this notification.
jnxMbgGwIndex
1.3.6.1.4.1.2636.3.66.4.1.1.1
Unsigned32
Gateway Index.
jnxMbgGwName
1.3.6.1.4.1.2636.3.66.4.1.1.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
Gateway Name.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAARadiusNetworkElementDown
1.3.6.1.4.1.2636.3.66.3.0.10
This notification signifies that the specified Network Element has been marked DOWN. This could be because none of the servers in the network element is active. SPIdentfier identifies the session-pic which originated this notification.
jnxMbgGwIndex
1.3.6.1.4.1.2636.3.66.4.1.1.1
Unsigned32
Gateway Index.
jnxMbgGwName
1.3.6.1.4.1.2636.3.66.4.1.1.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
Gateway Name.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgAAARadiusNEPendAuthQStatus
1.3.6.1.4.1.2636.3.66.3.0.11
This notification signifies the crossing-over of a watermark (High or Low) of the pending authentication queue length of network element. The NetworkElementName identifies the network element and SPIdentfier identifies the session-pic which originated this notification. jnxMbgPendQWaterMarkType identifies the water mark type (High/Low). jnxMbgPendQWaterMarkValue is the value that has been crossed over. jnxMbgPendQLength is the size of the queue after crossing over.
jnxMbgGwIndex
1.3.6.1.4.1.2636.3.66.4.1.1.1
Unsigned32
Gateway Index.
jnxMbgGwName
1.3.6.1.4.1.2636.3.66.4.1.1.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
Gateway Name.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgPendQWaterMarkType
1.3.6.1.4.1.2636.3.66.3.1.7.4
JnxMbgQueueWaterMarkType0 = unknown1 = high2 = lowThe type of a queue threshold - high or low. · Integer32
The type of the pending queue water mark crossed - High or Low.
jnxMbgPendQWaterMarkValue
1.3.6.1.4.1.2636.3.66.3.1.7.5
Integer32
The water mark value for the pending queue.
jnxMbgPendQLength
1.3.6.1.4.1.2636.3.66.3.1.7.6
Counter32
The size of the pending queue.
jnxMbgAAARadiusNEPendAcctQStatus
1.3.6.1.4.1.2636.3.66.3.0.12
This notification signifies the crossing-over of a watermark (High or Low) of the pending accounting queue length of network element. The NetworkElementName identifies the network element and SPIdentfier identifies the session-pic which originated this notification. jnxMbgPendQWaterMarkType identifies the water mark type (High/Low). jnxMbgPendQWaterMarkValue is the value that has been crossed over. jnxMbgPendQLength is the size of the queue after crossing over.
jnxMbgGwIndex
1.3.6.1.4.1.2636.3.66.4.1.1.1
Unsigned32
Gateway Index.
jnxMbgGwName
1.3.6.1.4.1.2636.3.66.4.1.1.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
Gateway Name.
jnxMbgAAANetworkElementName
1.3.6.1.4.1.2636.3.66.3.1.7.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The name which uniquely identifies a AAA Network Element on the mobile-gateway.
jnxMbgSPIdentifier
1.3.6.1.4.1.2636.3.66.3.1.7.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This identifies the session-pic, in the for sp-a/b/0, where <a> is the slot and <b> could be either 0 or 1.
jnxMbgPendQWaterMarkType
1.3.6.1.4.1.2636.3.66.3.1.7.4
JnxMbgQueueWaterMarkType0 = unknown1 = high2 = lowThe type of a queue threshold - high or low. · Integer32
The type of the pending queue water mark crossed - High or Low.
jnxMbgPendQWaterMarkValue
1.3.6.1.4.1.2636.3.66.3.1.7.5
Integer32
The water mark value for the pending queue.
jnxMbgPendQLength
1.3.6.1.4.1.2636.3.66.3.1.7.6
Counter32
The size of the pending queue.