OID reference

zxAnLctAccessEntry

1.3.6.1.4.1.3902.1015.1.1.150.2.1.1.1

Description

zxAnLctAccessEntry,A list of the LCT accessing the NE information. There are two variables is mandatory when creat the entry. All of the mandatory variables must be included in one SNMP set operation.and must comply with the multi-variables binding rule. The multi-variables binding rule should be complied with when a …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3902.1015.1.1.150.2.1.1 (zxAnLctAccessTable)
Node code
1
Node name
zxAnLctAccessEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3902.1015.1.1.150.2.1.1.1
URN notation
urn:oid:1.3.6.1.4.1.3902.1015.1.1.150.2.1.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3902 1015 1 1 150 2 1 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxAn(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) msag(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxAn(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) msag(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxAn(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) msag(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxAn(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) msag(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxAn(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) msag(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxAn(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) msag(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxAn(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) msag(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxAn(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) msag(1015) zxAnSysMib(1) zxAnSysObjects(1) zxAnLctMib(150) zxAnLctObjects(2) zxAnLctAccessObjects(1) zxAnLctAccessTable(1) zxAnLctAccessEntry(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3902/1015/1/1/150/2/1/1/1
  • /ISO/Identified-Organization/6/1/4/1/3902/1015/1/1/150/2/1/1/1
  • /ISO/3/6/1/4/1/3902/1015/1/1/150/2/1/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/3902/zxAn/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprise/3902/msag/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zte/zxAn/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zte/msag/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/zxAn/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/msag/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprises/3902/zxAn/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprises/3902/msag/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zte/zxAn/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zte/msag/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/zxAn/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/msag/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/zxAn/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/msag/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/zxAn/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/msag/zxAnSysMib/zxAnSysObjects/zxAnLctMib/zxAnLctObjects/zxAnLctAccessObjects/zxAnLctAccessTable/zxAnLctAccessEntry
  • Additional combinations skipped.

SNMP properties

Value type
ZxAnLctAccessEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

zxAnLctAccessEntry           OBJECT-TYPE
        SYNTAX          ZxAnLctAccessEntry
        MAX-ACCESS      not-accessible
        STATUS          current
        DESCRIPTION     
           "zxAnLctAccessEntry,A list of the LCT accessing the NE information.
            
            There are two variables is mandatory when creat the entry. 
            All of the mandatory variables must be included in one SNMP set
            operation.and must comply with the multi-variables binding rule.
            
            The multi-variables binding rule should be complied with when a 
            manager creates an entry. According to this rule, all the related 
            mib variables must be included in one SNMP set operation.                            
                    
            There are two cases based on the variable zxAnLctAccessRowStatus. 
            The mandatory and optional variables are different in each case.
             
            Case 1: to create an entry when LCT user login:
                mandatory: zxAnLctAccessDetailInfo, zxAnLctAccessRowStatus,
                optional : none

            Case 2: to destroy the session when LCT user logout:
                mandatory: zxAnLctAccessRowStatus,
                optional : none
             
            After an entry is created, no variable can be modified. 
            If a manager tries to modify any variables in this entry, 
            agent will return error with SNMP error code inconsistentValue."
        INDEX           { zxAnLctAccessSessionId }
        ::=  { zxAnLctAccessTable 1 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

zxAnLctAccessEntry,A list of the LCT accessing the NE information. There are two variables is mandatory when creat the entry. All of the mandatory variables must be included in one SNMP set operation.and must comply with the multi-variables binding rule. The multi-variables binding rule should be complied with when a manager creates an entry. According to this rule, all the related mib variables must be included in one SNMP set operation. There are two cases based on the variable zxAnLctAccessRowStatus. The mandatory and optional variables are different in each case. Case 1: to create an entry when LCT user login: mandatory: zxAnLctAccessDetailInfo, zxAnLctAccessRowStatus, optional : none Case 2: to destroy the session when LCT user logout: mandatory: zxAnLctAccessRowStatus, optional : none After an entry is created, no variable can be modified. If a manager tries to modify any variables in this entry, agent will return error with SNMP error code inconsistentValue.

Sources for this description

ZTE MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1ZTE MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

zxAnLctAccessEntry · currentZTE MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: zxAnLctAccessEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zxAnLctAccessEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "ZxAnLctAccessEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"zxAnLctAccessEntry,A list of the LCT accessing the NE information. There are two variables is mandatory when creat the entry. All of the mandatory variables must be included in one SNMP set operation.and must comply with the multi-variables binding rule. The multi-variables binding rule should be complied with when a manager creates an entry. According to this rule, all the related mib variables must be included in one SNMP set operation. There are two cases based on the variable zxAnLctAccessRowStatus. The mandatory and optional variables are different in each case. Case 1: to create an entry when LCT user login: mandatory: zxAnLctAccessDetailInfo, zxAnLctAccessRowStatus, optional : none Case 2: to destroy the session when LCT user logout: mandatory: zxAnLctAccessRowStatus, optional : none After an entry is created, no variable can be modified. If a manager tries to modify any variables in this entry, agent will return error with SNMP error code inconsistentValue.\"",
    "INDEX",
    "{",
    "zxAnLctAccessSessionId",
    "}",
    "::=",
    "{",
    "zxAnLctAccessTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "ZxAnLctAccessEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "zxAnLctAccessEntry,A list of the LCT accessing the NE information. There are two variables is mandatory when creat the entry. All of the mandatory variables must be included in one SNMP set operation.and must comply with the multi-variables binding rule. The multi-variables binding rule should be complied with when a manager creates an entry. According to this rule, all the related mib variables must be included in one SNMP set operation. There are two cases based on the variable zxAnLctAccessRowStatus. The mandatory and optional variables are different in each case. Case 1: to create an entry when LCT user login: mandatory: zxAnLctAccessDetailInfo, zxAnLctAccessRowStatus, optional : none Case 2: to destroy the session when LCT user logout: mandatory: zxAnLctAccessRowStatus, optional : none After an entry is created, no variable can be modified. If a manager tries to modify any variables in this entry, agent will return error with SNMP error code inconsistentValue."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "zxAnLctAccessSessionId"
        ]
      ]
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3902)

Xianlin Luo

Direct children (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3902.1015.1.1.150.2.1.1.1.1 zxAnLctAccessSessionId00
1.3.6.1.4.1.3902.1015.1.1.150.2.1.1.1.2 zxAnLctAccessDetailInfo00
1.3.6.1.4.1.3902.1015.1.1.150.2.1.1.1.3 zxAnLctAccessSourceIpAddress00
1.3.6.1.4.1.3902.1015.1.1.150.2.1.1.1.4 zxAnLctAccessUserName00
1.3.6.1.4.1.3902.1015.1.1.150.2.1.1.1.50 zxAnLctAccessRowStatus00