OID reference

zxAnFileServerEntry

1.3.6.1.4.1.3902.1015.17.2.3.1

Description

File server configuration entry. The multi-variables binding rule should be complied with when a manager configure a file server. According to this rule, all the related mib variables must be included in one SNMP set operation. There are two types of variables: mandatory and optional. All of the mandatory variables mu…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3902.1015.17.2.3 (zxAnFileServerTable)
Node code
1
Node name
zxAnFileServerEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3902.1015.17.2.3.1
URN notation
urn:oid:1.3.6.1.4.1.3902.1015.17.2.3.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxAn(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) msag(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxAn(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) msag(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxAn(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) msag(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxAn(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) msag(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxAn(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) msag(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxAn(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) msag(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxAn(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) msag(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxAn(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) msag(1015) zxAnFileServerMib(17) zxAnFileServerObjects(2) zxAnFileServerTable(3) zxAnFileServerEntry(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3902/1015/17/2/3/1
  • /ISO/Identified-Organization/6/1/4/1/3902/1015/17/2/3/1
  • /ISO/3/6/1/4/1/3902/1015/17/2/3/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/3902/zxAn/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprise/3902/msag/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zte/zxAn/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zte/msag/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/zxAn/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/msag/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprises/3902/zxAn/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprises/3902/msag/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zte/zxAn/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zte/msag/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/zxAn/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/msag/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/zxAn/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/msag/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/zxAn/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/msag/zxAnFileServerMib/zxAnFileServerObjects/zxAnFileServerTable/zxAnFileServerEntry
  • Additional combinations skipped.

SNMP properties

Value type
ZxAnFileServerEntry
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.

zxAnFileServerEntry   OBJECT-TYPE
        SYNTAX          ZxAnFileServerEntry
        MAX-ACCESS      not-accessible
        STATUS          current
        DESCRIPTION     
            "File server configuration entry.
            
            The multi-variables binding rule should be complied with when a 
            manager configure a file server. According to this rule, all the 
            related mib variables must be included in one SNMP set operation.
                    
            There are two types of variables: mandatory and optional.
            All of the mandatory variables must be included in one SNMP set 
            operation. Optional variables may be included in one SNMP set 
            operation with the mandatory variables, but must not be used alone. 
                    
            To configure a file server, there are several cases based on the 
            variable zxAnFileServerGroupUsage and zxAnFileServerIndex. 
            The mandatory and optional variables are same in each case.
             
            mandatoty: zxAnFileServerIpAddressType, zxAnFileServerIpAddress,
                       zxAnFileServerProtocolType,zxAnFileServerUserName,
                       zxAnFileServerUserPwd 
            optional : none
            "           
            
        INDEX   { zxAnFileServerGroupUsage, zxAnFileServerIndex}
        ::=  { zxAnFileServerTable 1 }

Meaning

Descriptions

1 unique

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

File server configuration entry. The multi-variables binding rule should be complied with when a manager configure a file server. According to this rule, all the related mib variables must be included in one SNMP set operation. There are two types of variables: mandatory and optional. All of the mandatory variables must be included in one SNMP set operation. Optional variables may be included in one SNMP set operation with the mandatory variables, but must not be used alone. To configure a file server, there are several cases based on the variable zxAnFileServerGroupUsage and zxAnFileServerIndex. The mandatory and optional variables are same in each case. mandatoty: zxAnFileServerIpAddressType, zxAnFileServerIpAddress, zxAnFileServerProtocolType,zxAnFileServerUserName, zxAnFileServerUserPwd optional : none

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

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

Status in source: current.

Names: zxAnFileServerEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zxAnFileServerEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "ZxAnFileServerEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"File server configuration entry. The multi-variables binding rule should be complied with when a manager configure a file server. According to this rule, all the related mib variables must be included in one SNMP set operation. There are two types of variables: mandatory and optional. All of the mandatory variables must be included in one SNMP set operation. Optional variables may be included in one SNMP set operation with the mandatory variables, but must not be used alone. To configure a file server, there are several cases based on the variable zxAnFileServerGroupUsage and zxAnFileServerIndex. The mandatory and optional variables are same in each case. mandatoty: zxAnFileServerIpAddressType, zxAnFileServerIpAddress, zxAnFileServerProtocolType,zxAnFileServerUserName, zxAnFileServerUserPwd optional : none \"",
    "INDEX",
    "{",
    "zxAnFileServerGroupUsage",
    ",",
    "zxAnFileServerIndex",
    "}",
    "::=",
    "{",
    "zxAnFileServerTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "ZxAnFileServerEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "File server configuration entry. The multi-variables binding rule should be complied with when a manager configure a file server. According to this rule, all the related mib variables must be included in one SNMP set operation. There are two types of variables: mandatory and optional. All of the mandatory variables must be included in one SNMP set operation. Optional variables may be included in one SNMP set operation with the mandatory variables, but must not be used alone. To configure a file server, there are several cases based on the variable zxAnFileServerGroupUsage and zxAnFileServerIndex. The mandatory and optional variables are same in each case. mandatoty: zxAnFileServerIpAddressType, zxAnFileServerIpAddress, zxAnFileServerProtocolType,zxAnFileServerUserName, zxAnFileServerUserPwd optional : none"
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "zxAnFileServerGroupUsage"
        ],
        [
          0,
          "zxAnFileServerIndex"
        ]
      ]
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3902)

Xianlin Luo

Direct children (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3902.1015.17.2.3.1.1 zxAnFileServerIndex00
1.3.6.1.4.1.3902.1015.17.2.3.1.2 zxAnFileServerIpAddressType00
1.3.6.1.4.1.3902.1015.17.2.3.1.3 zxAnFileServerIpAddress00
1.3.6.1.4.1.3902.1015.17.2.3.1.4 zxAnFileServerProtocolType00
1.3.6.1.4.1.3902.1015.17.2.3.1.5 zxAnFileServerUserName00
1.3.6.1.4.1.3902.1015.17.2.3.1.6 zxAnFileServerUserPwd00
1.3.6.1.4.1.3902.1015.17.2.3.1.7 zxAnFileServerPath00