OID reference

h3cCfgOperateProtocol

1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.3

Description

If the value of h3cCfgOperateType is running2Net,net2Running,net2Startup or startup2net, this node specify the protocol to be used for file transfer . The default protocol is ftp if no protocol is specified. And for other value of h3cCfgOperateType , this object may be ignored by the implementation. when clusterftp or…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1 (h3cCfgOperateEntry)
Node code
3
Node name
h3cCfgOperateProtocol
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.3
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 6 10 1 2 4 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) h3cConfig(10) h3cConfigManObjects(1) h3cCfgOperate(2) h3cCfgOperateTable(4) h3cCfgOperateEntry(1) h3cCfgOperateProtocol(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/6/10/1/2/4/1/3
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/6/10/1/2/4/1/3
  • /ISO/3/6/1/4/1/43/45/1/6/10/1/2/4/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/huaweiUtility/h3cConfig/h3cConfigManObjects/h3cCfgOperate/h3cCfgOperateTable/h3cCfgOperateEntry/h3cCfgOperateProtocol
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-create
Status in MIB
current

Enumerated values

ValueName
1ftp
2tftp
3clusterftp
4clustertftp

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In A3COM-HUAWEI-CONFIG-MAN-MIB, the row index h3cCfgOperateIndex is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.3.<h3cCfgOperateIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.3

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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cCfgOperateProtocol · current

h3cCfgOperateProtocol OBJECT-TYPE
    SYNTAX INTEGER
        {
            ftp(1),
            tftp(2),
            clusterftp(3),
            clustertftp(4)
        }
    MAX-ACCESS read-create
    STATUS current
    DESCRIPTION
        "If the value of h3cCfgOperateType is running2Net,net2Running,net2Startup
         or startup2net,  this node specify the protocol to be
        used for file transfer .
        The default protocol is ftp if no protocol is specified.
        And for other value of h3cCfgOperateType , this object may
        be ignored by the implementation.

        when clusterftp or clustertftp is selected,
        the h3cCfgOperateServerAddress needn't be set,
        the server address can be acquired automatically, the value of h3cCfgOperateServerAddress
        is uncertain during operation.
        both member switch and commander switch can use them if they support HGMP v2.
        "
    ::= { h3cCfgOperateEntry 3 }

h3cCfgOperateProtocol · current

h3cCfgOperateProtocol OBJECT-TYPE
    SYNTAX INTEGER
        {
            ftp(1),
            tftp(2),
            clusterftp(3),
            clustertftp(4)
        }
    MAX-ACCESS read-create
    STATUS current
    DESCRIPTION
        "If the value of h3cCfgOperateType is running2Net,net2Running,net2Startup
         or startup2net,  this node specify the protocol to be
        used for file transfer .
        The default protocol is ftp if no protocol is specified.
        And for other value of h3cCfgOperateType , this object may
        be ignored by the implementation.

        when clusterftp or clustertftp is selected,
        the h3cCfgOperateServerAddress needn't be set,
        the server address can be acquired automatically, the value of h3cCfgOperateServerAddress
        is uncertain during operation.
        both member switch and commander switch can use them if they support HGMP v2.
        "
    ::= { h3cCfgOperateEntry 3 }

Meaning

Descriptions

1 unique

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

If the value of h3cCfgOperateType is running2Net,net2Running,net2Startup or startup2net, this node specify the protocol to be used for file transfer . The default protocol is ftp if no protocol is specified. And for other value of h3cCfgOperateType , this object may be ignored by the implementation. when clusterftp or clustertftp is selected, the h3cCfgOperateServerAddress needn't be set, the server address can be acquired automatically, the value of h3cCfgOperateServerAddress is uncertain during operation. both member switch and commander switch can use them if they support HGMP v2.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

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 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cCfgOperateProtocol · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cCfgOperateProtocol

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cCfgOperateProtocol",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "ftp",
    "(",
    "1",
    ")",
    ",",
    "tftp",
    "(",
    "2",
    ")",
    ",",
    "clusterftp",
    "(",
    "3",
    ")",
    ",",
    "clustertftp",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"If the value of h3cCfgOperateType is running2Net,net2Running,net2Startup or startup2net, this node specify the protocol to be used for file transfer . The default protocol is ftp if no protocol is specified. And for other value of h3cCfgOperateType , this object may be ignored by the implementation. when clusterftp or clustertftp is selected, the h3cCfgOperateServerAddress needn't be set, the server address can be acquired automatically, the value of h3cCfgOperateServerAddress is uncertain during operation. both member switch and commander switch can use them if they support HGMP v2. \"",
    "::=",
    "{",
    "h3cCfgOperateEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "ftp",
            1
          ],
          [
            "tftp",
            2
          ],
          [
            "clusterftp",
            3
          ],
          [
            "clustertftp",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "If the value of h3cCfgOperateType is running2Net,net2Running,net2Startup or startup2net, this node specify the protocol to be used for file transfer . The default protocol is ftp if no protocol is specified. And for other value of h3cCfgOperateType , this object may be ignored by the implementation. when clusterftp or clustertftp is selected, the h3cCfgOperateServerAddress needn't be set, the server address can be acquired automatically, the value of h3cCfgOperateServerAddress is uncertain during operation. both member switch and commander switch can use them if they support HGMP v2."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (12)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.1 h3cCfgOperateIndex00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.2 h3cCfgOperateType00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.4 h3cCfgOperateFileName00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.5 h3cCfgOperateServerAddress00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.6 h3cCfgOperateUserName00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.7 h3cCfgOperateUserPassword00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.8 h3cCfgOperateEndNotificationSwitch00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.9 h3cCfgOperateRowStatus00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.10 h3cCfgOperateServerPort00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.11 h3cCfgOperateSrvAddrType00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.12 h3cCfgOperateSrvAddrRev00
1.3.6.1.4.1.43.45.1.6.10.1.2.4.1.13 h3cCfgOperateSrvVPNName00