jnxLsysSpSecurewireUsedAmount
1.3.6.1.4.1.2636.3.39.1.17.20.1.2.1
Unsigned32
The secure-wire resource consumption over all LSYS.
JUNIPER-LSYSSP-SECUREWIRE-MIB
2019-03-29
This module defines the secure-wire-specific MIB for Juniper Enterprise Logical-System (LSYS) security profiles. Juniper documentation is recommended as the reference. The LSYS security profile provides various static and dynamic resource management by observing resource quota limits. Security secure-wire resource is the focus in this MIB.
Download JUNIPER-LSYSSP-SECUREWIRE-MIB.txt Open JUNIPER-LSYSSP-SECUREWIRE-MIB.txt in a new tab
Scalars (7)
Tables (1)
| Name | OID |
|---|---|
| jnxLsysSpSecurewireTable | 1.3.6.1.4.1.2636.3.39.1.17.20.1.1.1 |
END OF TOC
Scalar details
jnxLsysSpSecurewireMaxQuota
1.3.6.1.4.1.2636.3.39.1.17.20.1.2.2
Unsigned32
The secure-wire resource maximum quota for the whole device for all LSYS.
jnxLsysSpSecurewireAvailableAmount
1.3.6.1.4.1.2636.3.39.1.17.20.1.2.3
Unsigned32
The secure-wire resource available in the whole device.
jnxLsysSpSecurewireHeaviestUsage
1.3.6.1.4.1.2636.3.39.1.17.20.1.2.4
Unsigned32
The most amount of secure-wire resource consumed of a LSYS.
jnxLsysSpSecurewireHeaviestUser
1.3.6.1.4.1.2636.3.39.1.17.20.1.2.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 (1..64) · OCTET STRING · hint 255a
The LSYS name that consume the most secure-wire resource.
jnxLsysSpSecurewireLightestUsage
1.3.6.1.4.1.2636.3.39.1.17.20.1.2.6
Unsigned32
The least amount of secure-wire resource consumed of a LSYS.
jnxLsysSpSecurewireLightestUser
1.3.6.1.4.1.2636.3.39.1.17.20.1.2.7
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..64) · OCTET STRING · hint 255a
The LSYS name that consume the least secure-wire resource.
Table details
jnxLsysSpSecurewireTable
1.3.6.1.4.1.2636.3.39.1.17.20.1.1.1
Index: IMPLIED jnxLsysSpSecurewireLsysName
LSYSPROFILE secure-wire objects for secure-wire resource consumption per LSYS.
jnxLsysSpSecurewireLsysName
1.3.6.1.4.1.2636.3.39.1.17.20.1.1.1.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..64) · OCTET STRING · hint 255a
The name of the logical system for which secure-wire resource information is retrieved.
jnxLsysSpSecurewireProfileName
1.3.6.1.4.1.2636.3.39.1.17.20.1.1.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 (1..32) · OCTET STRING · hint 255a
The security profile name string for the LSYS.
jnxLsysSpSecurewireUsage
1.3.6.1.4.1.2636.3.39.1.17.20.1.1.1.1.3
Unsigned32
The current resource usage count for the LSYS.
jnxLsysSpSecurewireReserved
1.3.6.1.4.1.2636.3.39.1.17.20.1.1.1.1.4
Unsigned32
The reserved resource count for the LSYS.
jnxLsysSpSecurewireMaximum
1.3.6.1.4.1.2636.3.39.1.17.20.1.1.1.1.5
Unsigned32
The maximum allowed resource usage count for the LSYS.