The flag is used for indicating the ftp protocol when downing versions between EMS and NE . It include two protocols:one is ftp and another is sftp.
Sources for this description
ZTE MIB copies (LibreNMS/Observium Community)
OID reference
zxAnFtpProtocolType
1.3.6.1.4.1.3902.1015.2.1.2.1.18
Description
The flag is used for indicating the ftp protocol when downing versions between EMS and NE . It include two protocols:one is ftp and another is sftp.
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.3902.1015.2.1.2.1 (zxAnVerFtpMgmt)
- Node code
- 18
- Node name
- zxAnFtpProtocolType
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.3902.1015.2.1.2.1.18
- URN notation
- urn:oid:1.3.6.1.4.1.3902.1015.2.1.2.1.18
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 3902 1015 2 1 2 1 18}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxAn(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) msag(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxAn(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) msag(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxAn(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) msag(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxAn(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) msag(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxAn(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) msag(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxAn(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) msag(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxAn(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) msag(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxAn(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) msag(1015) zxAnEquipMib(2) zxAnEquipObjects(1) zxAnVerMgmt(2) zxAnVerFtpMgmt(1) zxAnFtpProtocolType(18)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/3902/1015/2/1/2/1/18
- /ISO/Identified-Organization/6/1/4/1/3902/1015/2/1/2/1/18
- /ISO/3/6/1/4/1/3902/1015/2/1/2/1/18
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/3902/zxAn/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprise/3902/msag/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprise/zte/zxAn/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprise/zte/msag/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/zxAn/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/msag/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprises/3902/zxAn/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprises/3902/msag/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprises/zte/zxAn/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprises/zte/msag/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/zxAn/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/msag/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/zxAn/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/msag/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/zxAn/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/msag/zxAnEquipMib/zxAnEquipObjects/zxAnVerMgmt/zxAnVerFtpMgmt/zxAnFtpProtocolType
- Additional combinations skipped.
SNMP properties
- Value type
- INTEGER
- Maximum access defined by MIB
- read-write
- Status in MIB
- current
Enumerated values
| Value | Name |
|---|---|
| 1 | ftp |
| 2 | sftp |
Using this OID with SNMP
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.3902.1015.2.1.2.1.18.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Published definition
The displayed source records contain one distinct definition. Compare its source records.
zxAnFtpProtocolType OBJECT-TYPE
SYNTAX INTEGER
{
ftp(1),
sftp(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION " The flag is used for
indicating the ftp protocol when downing versions between EMS and NE .
It include two protocols:one is ftp and another is sftp.
"
::= { zxAnVerFtpMgmt 18 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1ZTE MIB copies (LibreNMS/Observium Community)
zxAnFtpProtocolType · currentZTE MIB copies (LibreNMS/Observium Community)
Status in source: current.
Names: zxAnFtpProtocolType
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxAnFtpProtocolType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"ftp",
"(",
"1",
")",
",",
"sftp",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\" The flag is used for indicating the ftp protocol when downing versions between EMS and NE . It include two protocols:one is ftp and another is sftp. \"",
"::=",
"{",
"zxAnVerFtpMgmt",
"18",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"ftp",
1
],
[
"sftp",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The flag is used for indicating the ftp protocol when downing versions between EMS and NE . It include two protocols:one is ftp and another is sftp."
],
null,
null,
null,
null
]
}- ZTE MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive. ZTE support.
Module: ZTE-AN-EQUIP-MIB
See published definition above
· Download ZTE-AN-EQUIP-MIBModule imports
{'SNMPv2-TC': ['RowStatus', 'DisplayString', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'IpAddress', 'Counter64', 'Unsigned32', 'NOTIFICATION-TYPE'], 'ZTE-AN-TC-MIB': ['zxAn']}Related source files and packages:
Registration