CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Total number of subscribers.
jnxSubscriberActiveCount
1.3.6.1.4.1.2636.3.64.1.1.1.2
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Number of active subscribers.
jnxSubscriberAccountingTotalCount
1.3.6.1.4.1.2636.3.64.1.1.1.7
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Total number of subscribers with accounting.
jnxSubscriberLogicalSystemTotalCount
1.3.6.1.4.1.2636.3.64.1.1.2.1
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
The number of total subscribers on the logical system.
jnxSubscriberLogicalSystemActiveCount
1.3.6.1.4.1.2636.3.64.1.1.2.2
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
The number of active subscribers on the logical system.
jnxSubscriberRoutingInstanceTotalCount
1.3.6.1.4.1.2636.3.64.1.1.3.1
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
The number of total subscribers on the routing instance.
jnxSubscriberRoutingInstanceActiveCount
1.3.6.1.4.1.2636.3.64.1.1.3.2
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
The number of active subscribers on the routing instance.
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the most significant 32 bit of the 64 bit subscriber id.
jnxSubscriberHandleLoWord
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.2
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the least significant 32 bit of the 64 bit subscriber id.
jnxSubscriberUserName
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.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 userName associated with this subscriber.
jnxSubscriberClientType
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.4
JnxSubscriberClientTypeThe set of possible AAA subscriber client types:
none None of the following
dhcp DHCP clients only
l2tp L2TP clients only
ppp PPP clients only
pppoe PPPoE clients only
vlan VLAN clients only
generic Generic clients only
mobileIp Mobile Ip clients only
vplsPw VPLS pseudowires only
static Static clients only
mlppp MLPPP clients only
xauth XAUTH clients only
fwauth FWAUTH clients only
dot1x DOT1X clients only
essm ESSM clients only
l2ald L2ALD clients only
gre GRE clients only
vlanOob Out-of-band VLAN clients only
hagTunnel Hag Tunnel clients only
hagBundle Hag Bundle clients only
fwa FWA clients only · BITS
The client type for this subscriber.
jnxSubscriberIpAddress
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.5
IpAddress SIZE (4)
The client IP Address assigned to this subscriber.
jnxSubscriberIpAddressMask
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.6
IpAddress SIZE (4)
The client IP Address Mask assigned to this subscriber.
jnxSubscriberLogicalSystem
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.7
OCTET STRING SIZE (0..63)
The logical system associated with this subscriber.
jnxSubscriberRoutingInstance
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.8
OCTET STRING SIZE (0..128)
The routing instance associated with this subscriber.
jnxSubscriberInterface
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.9
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 textual name of the interface associated with this subscriber.
jnxSubscriberInterfaceType
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.10
INTEGER0 = none1 = static2 = dynamic · Integer32
The type of the interface associated with this subscriber.
jnxSubscriberMacAddress
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.11
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The MAC address of the interface associated with this subscriber.
jnxSubscriberState
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.12
JnxSubscriberState0 = init1 = configured2 = active3 = terminating4 = terminated5 = unknownThe set of possible AAA subscriber states, expressed as a bit map:
init INIT state only
configured CONFIGURED state only
active ACTIVE state only
terminated TERMINATED state only
terminating TERMINATING state only
unknown Unknown state · Integer32
The state of this subscriber.
jnxSubscriberLoginTime
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.13
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 time this subscriber logged in to the server.
jnxSubscriberAcctSessionId
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.14
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 accounting session id associated with this subscriber.
jnxSubscriberUnderlyingInterface
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.15
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 underlying interface associated with this subscriber interface.
jnxSubscriberPhysicalInterface
1.3.6.1.4.1.2636.3.64.1.1.1.3.1.16
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 physical interface associated with this subscriber interface.
The entries in this table represent subscribers Interface Hardware Index.
jnxSubscriberInterfaceHardwareIndexHandleHiWord
1.3.6.1.4.1.2636.3.64.1.1.1.4.1.1
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the most significant 32 bit of the 64 bit subscriber id.
jnxSubscriberInterfaceHardwareIndexHandleLoWord
1.3.6.1.4.1.2636.3.64.1.1.1.4.1.2
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the least significant 32 bit of the 64 bit subscriber id.
jnxSubscriberInterfaceHardwareIndex
1.3.6.1.4.1.2636.3.64.1.1.1.4.1.3
Unsigned32
The subscriber interface hardware index.
jnxSubscriberPortCountTable
1.3.6.1.4.1.2636.3.64.1.1.1.5
Index: jnxSubscriberPort
The entries in this table represent each port. Each entry contains the port name and the number of active subscribers present on that port.
jnxSubscriberPort
1.3.6.1.4.1.2636.3.64.1.1.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
Name of the port in string
jnxSubscriberPortTunneledCounter
1.3.6.1.4.1.2636.3.64.1.1.1.5.1.2
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Number of active Tunneled subscribers present on the port
jnxSubscriberPortTerminatedCounter
1.3.6.1.4.1.2636.3.64.1.1.1.5.1.3
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Number of active Tunneled subscribers present on the port
jnxSubscriberPortL2CrossConnectCounter
1.3.6.1.4.1.2636.3.64.1.1.1.5.1.4
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Number of Layer-2 cross-connected subscribers present on the port
The entries in this table represent subscribers with accounting.
jnxSubscriberAccountingHandleHiWord
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.1
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the most significant 32 bit of the 64 bit subscriber id.
jnxSubscriberAccountingHandleLoWord
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.2
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the least significant 32 bit of the 64 bit subscriber id.
jnxSubscriberAccountingUserName
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.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 userName associated with this subscriber.
jnxSubscriberAccountingClientType
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.4
JnxSubscriberClientTypeThe set of possible AAA subscriber client types:
none None of the following
dhcp DHCP clients only
l2tp L2TP clients only
ppp PPP clients only
pppoe PPPoE clients only
vlan VLAN clients only
generic Generic clients only
mobileIp Mobile Ip clients only
vplsPw VPLS pseudowires only
static Static clients only
mlppp MLPPP clients only
xauth XAUTH clients only
fwauth FWAUTH clients only
dot1x DOT1X clients only
essm ESSM clients only
l2ald L2ALD clients only
gre GRE clients only
vlanOob Out-of-band VLAN clients only
hagTunnel Hag Tunnel clients only
hagBundle Hag Bundle clients only
fwa FWA clients only · BITS
The client type for this subscriber.
jnxSubscriberAccountingIpAddress
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.5
IpAddress SIZE (4)
The client IP Address assigned to this subscriber.
jnxSubscriberAccountingIpAddressMask
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.6
IpAddress SIZE (4)
The client IP Address Mask assigned to this subscriber.
jnxSubscriberAccountingLogicalSystem
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.7
OCTET STRING SIZE (0..63)
The logical system associated with this subscriber.
jnxSubscriberAccountingRoutingInstance
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.8
OCTET STRING SIZE (0..128)
The routing instance associated with this subscriber.
jnxSubscriberAccountingInterface
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.9
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 textual name of the interface associated with this subscriber.
jnxSubscriberAccountingInterfaceType
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.10
INTEGER0 = none1 = static2 = dynamic · Integer32
The type of the interface associated with this subscriber.
jnxSubscriberAccountingMacAddress
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.11
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The MAC address of the interface associated with this subscriber.
jnxSubscriberAccountingState
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.12
JnxSubscriberState0 = init1 = configured2 = active3 = terminating4 = terminated5 = unknownThe set of possible AAA subscriber states, expressed as a bit map:
init INIT state only
configured CONFIGURED state only
active ACTIVE state only
terminated TERMINATED state only
terminating TERMINATING state only
unknown Unknown state · Integer32
The state of this subscriber.
jnxSubscriberAccountingLoginTime
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.13
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 time this subscriber logged in to the server.
jnxSubscriberAccountingAcctSessionId
1.3.6.1.4.1.2636.3.64.1.1.1.6.1.14
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 accounting session id associated with this subscriber.
jnxSubscriberPicCountTable
1.3.6.1.4.1.2636.3.64.1.1.1.8
Index: jnxSubscriberPic
The entries in this table represent each PIC. Each entry contains the PIC name and the number of active subscribers present on that PIC.
jnxSubscriberPic
1.3.6.1.4.1.2636.3.64.1.1.1.8.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
Name of the PIC in string
jnxSubscriberPicTotalCounter
1.3.6.1.4.1.2636.3.64.1.1.1.8.1.2
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Number of active subscribers present on the PIC
jnxSubscriberSlotCountTable
1.3.6.1.4.1.2636.3.64.1.1.1.9
Index: jnxSubscriberSlot
The entries in this table represent each slot. Each entry contains the slot name and the number of active subscribers present on that slot.
jnxSubscriberSlot
1.3.6.1.4.1.2636.3.64.1.1.1.9.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
Name of the slot in string
jnxSubscriberSlotTotalCounter
1.3.6.1.4.1.2636.3.64.1.1.1.9.1.2
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
The entries in this table sort subscribers within the logical system.
The logical system name must be provided in the SNMP query. The logical system will be identified by either the context field in V3 requests, or it will be encoded in the community string in V1 or V2c requests.
User can query for logical-system/routing-instance specific data by prefixing the community string with <logical-system>/<routing-instance>@, where '@' acts as a separator between community name and routing-instance name.
If no logical system is specified, this table shows data for the default logical system. The name of the routing instance is ignored for this table.
jnxSubscriberLogicalSystemHandleHiWord
1.3.6.1.4.1.2636.3.64.1.1.2.3.1.1
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the most significant 32 bit of the 64 bit subscriber id.
jnxSubscriberLogicalSystemHandleLoWord
1.3.6.1.4.1.2636.3.64.1.1.2.3.1.2
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the least significant 32 bit of the 64 bit subscriber id.
jnxSubscriberLogicalSystemState
1.3.6.1.4.1.2636.3.64.1.1.2.3.1.3
JnxSubscriberState0 = init1 = configured2 = active3 = terminating4 = terminated5 = unknownThe set of possible AAA subscriber states, expressed as a bit map:
init INIT state only
configured CONFIGURED state only
active ACTIVE state only
terminated TERMINATED state only
terminating TERMINATING state only
unknown Unknown state · Integer32
The entries in this table sort subscribers within routing instance.
The routing instance name must be provided in the SNMP query. The routing instance will be identified by either the context field in V3 requests, or it will be encoded in the community string in V1 or V2c requests.
User can query for logical-system/routing-instance specific data by prefixing the community string with <logical-system>/<routing-instance>@, where '@' acts as a separator between community name and routing-instance name.
If no routing instance is specified, this table shows data for the default routing instance. The name of the logical system is ignored for this table.
jnxSubscriberRoutingInstanceHandleHiWord
1.3.6.1.4.1.2636.3.64.1.1.3.3.1.1
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the most significant 32 bit of the 64 bit subscriber id.
jnxSubscriberRoutingInstanceHandleLoWord
1.3.6.1.4.1.2636.3.64.1.1.3.3.1.2
Unsigned32
The subscriber handle associated with this subscriber. A subscriber handle is a monotonically increasing number.
This object is equal to the least significant 32 bit of the 64 bit subscriber id.
jnxSubscriberRoutingInstanceState
1.3.6.1.4.1.2636.3.64.1.1.3.3.1.3
JnxSubscriberState0 = init1 = configured2 = active3 = terminating4 = terminated5 = unknownThe set of possible AAA subscriber states, expressed as a bit map:
init INIT state only
configured CONFIGURED state only
active ACTIVE state only
terminated TERMINATED state only
terminating TERMINATING state only
unknown Unknown state · Integer32