Reference record for OID 1.3.6.1.4.1.2636.3.52.1.2.3



parent
1.3.6.1.4.1.2636.3.52.1.2 (jnxIpSecFlowMonPhaseTwo)
node code
3
node name
jnxIpSecSaMonTable
dot oid
1.3.6.1.4.1.2636.3.52.1.2.3
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) juniperMIB(2636) jnxMibs(3) jnxIpSecMibRoot(52) jnxIpSecFlowMonMIB(1) jnxIpSecFlowMonPhaseTwo(2) jnxIpSecSaMonTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) juniperMIB(2636) jnxMibs(3) jnxIpSecMibRoot(52) jnxIpSecFlowMonMIB(1) jnxIpSecFlowMonPhaseTwo(2) jnxIpSecSaMonTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) juniperMIB(2636) jnxMibs(3) jnxIpSecMibRoot(52) jnxIpSecFlowMonMIB(1) jnxIpSecFlowMonPhaseTwo(2) jnxIpSecSaMonTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) juniperMIB(2636) jnxMibs(3) jnxIpSecMibRoot(52) jnxIpSecFlowMonMIB(1) jnxIpSecFlowMonPhaseTwo(2) jnxIpSecSaMonTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) juniperMIB(2636) jnxMibs(3) jnxIpSecMibRoot(52) jnxIpSecFlowMonMIB(1) jnxIpSecFlowMonPhaseTwo(2) jnxIpSecSaMonTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) juniperMIB(2636) jnxMibs(3) jnxIpSecMibRoot(52) jnxIpSecFlowMonMIB(1) jnxIpSecFlowMonPhaseTwo(2) jnxIpSecSaMonTable(3)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/juniperMIB/jnxMibs/jnxIpSecMibRoot/jnxIpSecFlowMonMIB/jnxIpSecFlowMonPhaseTwo/jnxIpSecSaMonTable
  • /iso/identified-organization/dod/internet/private/enterprises/juniperMIB/jnxMibs/jnxIpSecMibRoot/jnxIpSecFlowMonMIB/jnxIpSecFlowMonPhaseTwo/jnxIpSecSaMonTable
  • /iso/org/dod/internet/private/enterprise/juniperMIB/jnxMibs/jnxIpSecMibRoot/jnxIpSecFlowMonMIB/jnxIpSecFlowMonPhaseTwo/jnxIpSecSaMonTable
  • /iso/org/dod/internet/private/enterprises/juniperMIB/jnxMibs/jnxIpSecMibRoot/jnxIpSecFlowMonMIB/jnxIpSecFlowMonPhaseTwo/jnxIpSecSaMonTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/juniperMIB/jnxMibs/jnxIpSecMibRoot/jnxIpSecFlowMonMIB/jnxIpSecFlowMonPhaseTwo/jnxIpSecSaMonTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/juniperMIB/jnxMibs/jnxIpSecMibRoot/jnxIpSecFlowMonMIB/jnxIpSecFlowMonPhaseTwo/jnxIpSecSaMonTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/2636/3/52/1/2/3

    Description by mibdepot

    The IPsec Phase-2 Security Association Table.
    This table identifies the structure (in terms of
    component SAs) of each active Phase-2 IPsec tunnel.
    This table contains an entry for each active and
    expiring security association and maps each entry
    in the active Phase-2 tunnel table (ipSecTunTable)
    into a number of entries in this table.

    SA contains the information negotiated by IKE. The SA
    is like a contract laying out the rules of the VPN
    connection for the duration of the SA. An SA is assigned
    a 32-bit number that, when used in conjunction with the
    destination IP address, uniquely identifies the SA. This
    number is called the Security Parameters Index or SPI.

    IPSec SAs area unidirectional and they are unique in
    each security protocol. A set of SAs are needed for a
    protected data pipe, one per direction per protocol.

    Parsed from file mib-jnx-ipsec-flow-mon.txt
    Company: None
    Module: JUNIPER-IPSEC-FLOW-MON-MIB

    Description by circitor

    The IPsec Phase-2 Security Association Table.
    This table identifies the structure (in terms of
    component SAs) of each active Phase-2 IPsec tunnel.
    This table contains an entry for each active and
    expiring security association and maps each entry
    in the active Phase-2 tunnel table (ipSecTunTable)
    into a number of entries in this table.

    SA contains the information negotiated by IKE. The SA
    is like a contract laying out the rules of the VPN
    connection for the duration of the SA. An SA is assigned
    a 32-bit number that, when used in conjunction with the
    destination IP address, uniquely identifies the SA. This
    number is called the Security Parameters Index or SPI.

    IPSec SAs area unidirectional and they are unique in
    each security protocol. A set of SAs are needed for a
    protected data pipe, one per direction per protocol.

    Parsed from file JUNIPER-IPSEC-FLOW-MON-MIB.mib
    Module: JUNIPER-IPSEC-FLOW-MON-MIB

    Information by oid_info

    Vendor: Juniper Networks, Inc.
    Module: JUNIPER-IPSEC-FLOW-MON-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    jnxIpSecSaMonTable OBJECT-TYPE SYNTAX SEQUENCE OF JnxIpSecSaMonEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IPsec Phase-2 Security Association Table. This table identifies the structure (in terms of component SAs) of each active Phase-2 IPsec tunnel. This table contains an entry for each active and expiring security association and maps each entry in the active Phase-2 tunnel table (ipSecTunTable) into a number of entries in this table. SA contains the information negotiated by IKE. The SA is like a contract laying out the rules of the VPN connection for the duration of the SA. An SA is assigned a 32-bit number that, when used in conjunction with the destination IP address, uniquely identifies the SA. This number is called the Security Parameters Index or SPI. IPSec SAs area unidirectional and they are unique in each security protocol. A set of SAs are needed for a protected data pipe, one per direction per protocol. " ::= { jnxIpSecFlowMonPhaseTwo 3 }

    Information by circitor

    jnxIpSecSaMonTable OBJECT-TYPE SYNTAX SEQUENCE OF JnxIpSecSaMonEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IPsec Phase-2 Security Association Table. This table identifies the structure (in terms of component SAs) of each active Phase-2 IPsec tunnel. This table contains an entry for each active and expiring security association and maps each entry in the active Phase-2 tunnel table (ipSecTunTable) into a number of entries in this table. SA contains the information negotiated by IKE. The SA is like a contract laying out the rules of the VPN connection for the duration of the SA. An SA is assigned a 32-bit number that, when used in conjunction with the destination IP address, uniquely identifies the SA. This number is called the Security Parameters Index or SPI. IPSec SAs area unidirectional and they are unique in each security protocol. A set of SAs are needed for a protected data pipe, one per direction per protocol. " ::= { jnxIpSecFlowMonPhaseTwo 3 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.2636)

    Cheng Jeff

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.2636.3.52.1.2.3.1 jnxIpSecSaMonEntry 14 14 Each entry contains the attributes associated with
    active and expiring IPsec Phase-2
    security associations.

    Brothers (2)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.2636.3.52.1.2.1 jnxIpSecNumOfTunnels 1 1 jnxIpSecNumOftunnels
    1.3.6.1.4.1.2636.3.52.1.2.2 jnxIpSecTunnelMonTable 1 25 The IPsec Phase-2 Tunnel Table.
    There is one entry in this table for each active IPsec Phase-2
    Tunnel. If the tunnel is terminat…