OID reference

saCmMtaProvisioningMode

1.3.6.1.4.1.1429.78.1.7

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1429.78.1 (saCmMta)
Node code: 7
Node name: saCmMtaProvisioningMode
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1429.78.1.7
URN notation: urn:oid:1.3.6.1.4.1.1429.78.1.7

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 1429 78 1 7}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ciscoSPVTG(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) sa(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ciscoSPVTG(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) sa(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ciscoSPVTG(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) sa(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ciscoSPVTG(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) sa(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ciscoSPVTG(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) sa(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ciscoSPVTG(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) sa(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ciscoSPVTG(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) sa(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ciscoSPVTG(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) sa(1429) saVoip(78) saCmMta(1) saCmMtaProvisioningMode(7)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/1429/78/1/7
/ISO/Identified-Organization/6/1/4/1/1429/78/1/7
/ISO/3/6/1/4/1/1429/78/1/7

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1429/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/enterprise/ciscoSPVTG/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/enterprise/sa/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/enterprises/1429/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/enterprises/ciscoSPVTG/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/enterprises/sa/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/ldap-enterprise/1429/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/ldap-enterprise/ciscoSPVTG/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/ldap-enterprise/sa/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/vendor-objects/1429/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/vendor-objects/ciscoSPVTG/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/identified-organization/dod/internet/private/vendor-objects/sa/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/org/dod/internet/private/enterprise/1429/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/org/dod/internet/private/enterprise/ciscoSPVTG/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/org/dod/internet/private/enterprise/sa/saVoip/saCmMta/saCmMtaProvisioningMode
/iso/org/dod/internet/private/enterprises/1429/saVoip/saCmMta/saCmMtaProvisioningMode
Additional combinations skipped.

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-only
Status in MIB: current
Default value: 0

Enumerated values

Value	Name
0	packetCable
1	oneConfigFile
2	twoConfigFilesDHCP
3	twoConfigFilesSNMP
4	twoConfigFilesDHCPmacAddress
5	twoConfigFilesMacAddressOnly
6	webPage

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.

saCmMtaProvisioningMode OBJECT-TYPE
    SYNTAX INTEGER {
          packetCable(0),
          oneConfigFile(1),
          twoConfigFilesDHCP(2),
          twoConfigFilesSNMP(3),
          twoConfigFilesDHCPmacAddress(4),
          twoConfigFilesMacAddressOnly(5),
          webPage(6)
          }
    MAX-ACCESS    read-only
    STATUS        current
    DESCRIPTION
        "This object must only be set via the CM configuration
         file during the provisioning process.
         After CM is operational, this object can not be set
         via SNMP.
         MTA provisioning modes:
         0: MTA follows the PacketCable provisioning specifications
            and supports BASIC, HYBRID and SECURE flows.
         1: MTA will provision using only the CM config file. VoIP
            parameters MUST be included in the CM config file as
            VSIFs. This option will become obsolete.
         2: MTA will learn the MTA config file name and location
            from the MTA DHCP OFFER.
            If the filename or location is missing, MTA will switch
            to mode 3.
         3: MTA will learn the MTA config file name and location via
            SNMP.  The MTA will send an SNMP inform to the
            provisioning server specified in DHCP option 122.3 or
            177.3, depending on saCmMtaDhcpPktcOption (note: MTA
            will not provision if saCmMtaDhcpPktcOption = requireNone(1)
            and no option 122.3 or 177.3 is specified).
         4: MTA will learn the MTA config file name and location and
            the MTA host name from the MTA DHCP OFFER/ACK.
            If the filename is missing in the DHCP OFFER/ACK, the MTA
            will request a config file name based on the MTA mac
            address (example: 000f21c4e145.bin).
            If the MTA host name is missing in the DHCP OFFER/ACK the
            MTA will use a host name of MAC_ADDR (example: 000f21c4e145).
         5: MTA will request a config file name based on the MTA mac
            address (example: 000f21c4e145.bin).  
            MTA will learn the MTA config file location via DHCP.  
            MTA will use a host name of MAC_ADDR (example: 000f21c4e145).  
            MTA will NOT use the file name and host name in the
            DHCP ACK even if the parameters are present.
         6: Web page provisioning. Parameters from a web page will be used
            rather than from config file. All the web page parameters are
            stored in non-vol. Base provisioning method is 2 above.
         For modes other than 0, MTA DHCP options 122, 177 are not required.
         Note:  This object can be set via the CM configuration file ONLY."
    DEFVAL    { 0 }
    ::= { saCmMta 7 }

Meaning

Descriptions

1 unique

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

This object must only be set via the CM configuration file during the provisioning process. After CM is operational, this object can not be set via SNMP. MTA provisioning modes: 0: MTA follows the PacketCable provisioning specifications and supports BASIC, HYBRID and SECURE flows. 1: MTA will provision using only the CM config file. VoIP parameters MUST be included in the CM config file as VSIFs. This option will become obsolete. 2: MTA will learn the MTA config file name and location from the MTA DHCP OFFER. If the filename or location is missing, MTA will switch to mode 3. 3: MTA will learn the MTA config file name and location via SNMP. The MTA will send an SNMP inform to the provisioning server specified in DHCP option 122.3 or 177.3, depending on saCmMtaDhcpPktcOption (note: MTA will not provision if saCmMtaDhcpPktcOption = requireNone(1) and no option 122.3 or 177.3 is specified). 4: MTA will learn the MTA config file name and location and the MTA host name from the MTA DHCP OFFER/ACK. If the filename is missing in the DHCP OFFER/ACK, the MTA will request a config file name based on the MTA mac address (example: 000f21c4e145.bin). If the MTA host name is missing in the DHCP OFFER/ACK the MTA will use a host name of MAC_ADDR (example: 000f21c4e145). 5: MTA will request a config file name based on the MTA mac address (example: 000f21c4e145.bin). MTA will learn the MTA config file location via DHCP. MTA will use a host name of MAC_ADDR (example: 000f21c4e145). MTA will NOT use the file name and host name in the DHCP ACK even if the parameters are present. 6: Web page provisioning. Parameters from a web page will be used rather than from config file. All the web page parameters are stored in non-vol. Base provisioning method is 2 above. For modes other than 0, MTA DHCP options 122, 177 are not required. Note: This object can be set via the CM configuration file ONLY.

Sources for this description

Cisco 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 1Cisco MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

saCmMtaProvisioningMode · currentCisco MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: saCmMtaProvisioningMode

Technical details

{
"smi_kind": "OBJECT-TYPE",
"definition": [
"saCmMtaProvisioningMode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"packetCable",
"(",
"0",
")",
",",
"oneConfigFile",
"(",
"1",
")",
",",
"twoConfigFilesDHCP",
"(",
"2",
")",
",",
"twoConfigFilesSNMP",
"(",
"3",
")",
",",
"twoConfigFilesDHCPmacAddress",
"(",
"4",
")",
",",
"twoConfigFilesMacAddressOnly",
"(",
"5",
")",
",",
"webPage",
"(",
"6",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"This object must only be set via the CM configuration file during the provisioning process. After CM is operational, this object can not be set via SNMP. MTA provisioning modes: 0: MTA follows the PacketCable provisioning specifications and supports BASIC, HYBRID and SECURE flows. 1: MTA will provision using only the CM config file. VoIP parameters MUST be included in the CM config file as VSIFs. This option will become obsolete. 2: MTA will learn the MTA config file name and location from the MTA DHCP OFFER. If the filename or location is missing, MTA will switch to mode 3. 3: MTA will learn the MTA config file name and location via SNMP. The MTA will send an SNMP inform to the provisioning server specified in DHCP option 122.3 or 177.3, depending on saCmMtaDhcpPktcOption (note: MTA will not provision if saCmMtaDhcpPktcOption = requireNone(1) and no option 122.3 or 177.3 is specified). 4: MTA will learn the MTA config file name and location and the MTA host name from the MTA DHCP OFFER/ACK. If the filename is missing in the DHCP OFFER/ACK, the MTA will request a config file name based on the MTA mac address (example: 000f21c4e145.bin). If the MTA host name is missing in the DHCP OFFER/ACK the MTA will use a host name of MAC_ADDR (example: 000f21c4e145). 5: MTA will request a config file name based on the MTA mac address (example: 000f21c4e145.bin). MTA will learn the MTA config file location via DHCP. MTA will use a host name of MAC_ADDR (example: 000f21c4e145). MTA will NOT use the file name and host name in the DHCP ACK even if the parameters are present. 6: Web page provisioning. Parameters from a web page will be used rather than from config file. All the web page parameters are stored in non-vol. Base provisioning method is 2 above. For modes other than 0, MTA DHCP options 122, 177 are not required. Note: This object can be set via the CM configuration file ONLY.\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"saCmMta",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"packetCable",
0
],
[
"oneConfigFile",
1
],
[
"twoConfigFilesDHCP",
2
],
[
"twoConfigFilesSNMP",
3
],
[
"twoConfigFilesDHCPmacAddress",
4
],
[
"twoConfigFilesMacAddressOnly",
5
],
[
"webPage",
6
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object must only be set via the CM configuration file during the provisioning process. After CM is operational, this object can not be set via SNMP. MTA provisioning modes: 0: MTA follows the PacketCable provisioning specifications and supports BASIC, HYBRID and SECURE flows. 1: MTA will provision using only the CM config file. VoIP parameters MUST be included in the CM config file as VSIFs. This option will become obsolete. 2: MTA will learn the MTA config file name and location from the MTA DHCP OFFER. If the filename or location is missing, MTA will switch to mode 3. 3: MTA will learn the MTA config file name and location via SNMP. The MTA will send an SNMP inform to the provisioning server specified in DHCP option 122.3 or 177.3, depending on saCmMtaDhcpPktcOption (note: MTA will not provision if saCmMtaDhcpPktcOption = requireNone(1) and no option 122.3 or 177.3 is specified). 4: MTA will learn the MTA config file name and location and the MTA host name from the MTA DHCP OFFER/ACK. If the filename is missing in the DHCP OFFER/ACK, the MTA will request a config file name based on the MTA mac address (example: 000f21c4e145.bin). If the MTA host name is missing in the DHCP OFFER/ACK the MTA will use a host name of MAC_ADDR (example: 000f21c4e145). 5: MTA will request a config file name based on the MTA mac address (example: 000f21c4e145.bin). MTA will learn the MTA config file location via DHCP. MTA will use a host name of MAC_ADDR (example: 000f21c4e145). MTA will NOT use the file name and host name in the DHCP ACK even if the parameters are present. 6: Web page provisioning. Parameters from a web page will be used rather than from config file. All the web page parameters are stored in non-vol. Base provisioning method is 2 above. For modes other than 0, MTA DHCP options 122, 177 are not required. Note: This object can be set via the CM configuration file ONLY."
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}

Cisco MIB copies (LibreNMS/Observium Community) · Publisher's source file: SA-CM-MTA-MIB
Vendor MIB copy from the LibreNMS archive. Cisco support.

Module: SA-CM-MTA-MIB

See published definition above
Module imports
```
{'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Integer32'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
```
· Download SA-CM-MTA-MIB
Related source files and packages:
Same file in Observium Community.

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1429)

Pechman Tamsen

Siblings (10)

OID	Name	Direct children	Descendants
1.3.6.1.4.1.1429.78.1.1	saCmMtaDevice	0	0
1.3.6.1.4.1.1429.78.1.3	saCmMtaIpFilters	0	0
1.3.6.1.4.1.1429.78.1.5	saCmMtaSidCount	0	0
1.3.6.1.4.1.1429.78.1.8	saCmMtaDhcpPktcOption	0	0
1.3.6.1.4.1.1429.78.1.10	saCmMtaRequireTod	0	0
1.3.6.1.4.1.1429.78.1.13	saCmMtaDecryptMtaConfigFile	0	0
1.3.6.1.4.1.1429.78.1.14	saCmMtaSwUpgradeControlTimer	0	0
1.3.6.1.4.1.1429.78.1.20	saCmMtaDhcpOptionSixty	0	0
1.3.6.1.4.1.1429.78.1.26	saCmMtaProvSnmpSetCommunityString	0	0
1.3.6.1.4.1.1429.78.1.1001	saCmMtaCliAccess	1	1