OID reference

apType

1.3.6.1.4.1.161.19.3.3.2.216

Description

In standard mode, all possible sync sources will be made availble and usedfor autoSync operation. In remote mode, sync over power port will not be available as a sync source. Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable. In this mode, GPS data is unava…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.161.19.3.3.2 (whispBoxConfig)
Node code
216
Node name
apType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.161.19.3.3.2.216
URN notation
urn:oid:1.3.6.1.4.1.161.19.3.3.2.216
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 161 19 3 3 2 216}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mot(161) whispRoot(19) whispProducts(3) whispBox(3) whispBoxConfig(2) apType(216)}
OID-IRI notation
  • /1/3/6/1/4/1/161/19/3/3/2/216
  • /ISO/Identified-Organization/6/1/4/1/161/19/3/3/2/216
  • /ISO/3/6/1/4/1/161/19/3/3/2/216
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/identified-organization/dod/internet/private/enterprises/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/identified-organization/dod/internet/private/vendor-objects/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/org/dod/internet/private/enterprise/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/org/dod/internet/private/enterprises/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/org/dod/internet/private/ldap-enterprise/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/org/dod/internet/private/vendor-objects/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/iso-identified-organization/dod/internet/private/enterprise/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/iso-identified-organization/dod/internet/private/enterprises/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/iso-organization/dod/internet/private/enterprise/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/iso-organization/dod/internet/private/enterprises/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType
  • /iso/iso-organization/dod/internet/private/vendor-objects/mot/whispRoot/whispProducts/whispBox/whispBoxConfig/apType

SNMP properties

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

Enumerated values

ValueName
0standard
1remote

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.161.19.3.3.2.216.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.

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

Show 2 published definitions

apType · current

apType	OBJECT-TYPE
		SYNTAX		INTEGER {
					standard(0),
					remote(1)}
		MAX-ACCESS	read-write
		STATUS		current
		DESCRIPTION		
			"In standard mode, all possible sync sources will be made availble and usedfor autoSync operation.
                         In remote mode, sync over power port will not be available as a sync source.
                         Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable.  In this mode,
                         GPS data is unavailable and sync over power port shouldn't be used.  If sync over power is desired, and a CMM or other
                         sync over power device is in use, then select standard mode.                        
						 This should really be named deviceType because this applies to both AP and BHM, but left this as apType for legacy purposes."
		::={whispBoxConfig 216}

apType · current

apType	OBJECT-TYPE
		SYNTAX		INTEGER {
					standard(0),
					remote(1)}
		MAX-ACCESS	read-write
		STATUS		current
		DESCRIPTION		
			"In standard mode, all possible sync sources will be made availble and usedfor autoSync operation.
                         In remote mode, sync over power port will not be available as a sync source.
                         Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable.  In this mode,
                         GPS data is unavailable and sync over power port shouldn't be used.  If sync over power is desired, and a CMM or other
                         sync over power device is in use, then select standard mode.
                         On 450b PTP BHM, this mode cannot be enabled while Sync Aux Port Config is set to Output or Alignment Tone, because these
                         signals share a physical pin with the sync input signal.
                         On MicroPoP, this feature does not have hardware support."
		::={whispBoxConfig 216}

Meaning

Descriptions

2 unique

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

Description 1

In standard mode, all possible sync sources will be made availble and usedfor autoSync operation. In remote mode, sync over power port will not be available as a sync source. Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable. In this mode, GPS data is unavailable and sync over power port shouldn't be used. If sync over power is desired, and a CMM or other sync over power device is in use, then select standard mode. This should really be named deviceType because this applies to both AP and BHM, but left this as apType for legacy purposes.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Description 2

In standard mode, all possible sync sources will be made availble and usedfor autoSync operation. In remote mode, sync over power port will not be available as a sync source. Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable. In this mode, GPS data is unavailable and sync over power port shouldn't be used. If sync over power is desired, and a CMM or other sync over power device is in use, then select standard mode. On 450b PTP BHM, this mode cannot be enabled while Sync Aux Port Config is set to Output or Alignment Tone, because these signals share a physical pin with the sync input signal. On MicroPoP, this feature does not have hardware support.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

apType · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: apType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "apType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "standard",
    "(",
    "0",
    ")",
    ",",
    "remote",
    "(",
    "1",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"In standard mode, all possible sync sources will be made availble and usedfor autoSync operation. In remote mode, sync over power port will not be available as a sync source. Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable. In this mode, GPS data is unavailable and sync over power port shouldn't be used. If sync over power is desired, and a CMM or other sync over power device is in use, then select standard mode. This should really be named deviceType because this applies to both AP and BHM, but left this as apType for legacy purposes.\"",
    "::=",
    "{",
    "whispBoxConfig",
    "216",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "standard",
            0
          ],
          [
            "remote",
            1
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "In standard mode, all possible sync sources will be made availble and usedfor autoSync operation. In remote mode, sync over power port will not be available as a sync source. Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable. In this mode, GPS data is unavailable and sync over power port shouldn't be used. If sync over power is desired, and a CMM or other sync over power device is in use, then select standard mode. This should really be named deviceType because this applies to both AP and BHM, but left this as apType for legacy purposes."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

apType · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: apType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "apType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "standard",
    "(",
    "0",
    ")",
    ",",
    "remote",
    "(",
    "1",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"In standard mode, all possible sync sources will be made availble and usedfor autoSync operation. In remote mode, sync over power port will not be available as a sync source. Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable. In this mode, GPS data is unavailable and sync over power port shouldn't be used. If sync over power is desired, and a CMM or other sync over power device is in use, then select standard mode. On 450b PTP BHM, this mode cannot be enabled while Sync Aux Port Config is set to Output or Alignment Tone, because these signals share a physical pin with the sync input signal. On MicroPoP, this feature does not have hardware support.\"",
    "::=",
    "{",
    "whispBoxConfig",
    "216",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "standard",
            0
          ],
          [
            "remote",
            1
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "In standard mode, all possible sync sources will be made availble and usedfor autoSync operation. In remote mode, sync over power port will not be available as a sync source. Remote Device mode is where the AP or BHM timing port is connected to an SM or BHS timing port via a sync cable. In this mode, GPS data is unavailable and sync over power port shouldn't be used. If sync over power is desired, and a CMM or other sync over power device is in use, then select standard mode. On 450b PTP BHM, this mode cannot be enabled while Sync Aux Port Config is set to Output or Alignment Tone, because these signals share a physical pin with the sync input signal. On MicroPoP, this feature does not have hardware support."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.161)

Joe Schaeffer

Siblings (298)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.161.19.3.3.2.151 httpPort00
1.3.6.1.4.1.161.19.3.3.2.152 httpsPort00
1.3.6.1.4.1.161.19.3.3.2.153 snmpPort00
1.3.6.1.4.1.161.19.3.3.2.154 snmpTrapPort00
1.3.6.1.4.1.161.19.3.3.2.155 webAccess00
1.3.6.1.4.1.161.19.3.3.2.156 syslogDomainNameAppend00
1.3.6.1.4.1.161.19.3.3.2.157 syslogServerAddr00
1.3.6.1.4.1.161.19.3.3.2.158 syslogServerPort00
1.3.6.1.4.1.161.19.3.3.2.159 syslogMinLevel00
1.3.6.1.4.1.161.19.3.3.2.160 allIpv6Filter00
1.3.6.1.4.1.161.19.3.3.2.161 ipv6smbFilter00
1.3.6.1.4.1.161.19.3.3.2.162 ipv6snmpFilter00
1.3.6.1.4.1.161.19.3.3.2.163 ipv6bootpcFilter00
1.3.6.1.4.1.161.19.3.3.2.164 ipv6bootpsFilter00
1.3.6.1.4.1.161.19.3.3.2.165 ipv6MultFilter00
1.3.6.1.4.1.161.19.3.3.2.166 allOtherIpv6Filter00
1.3.6.1.4.1.161.19.3.3.2.167 snmpStatus00
1.3.6.1.4.1.161.19.3.3.2.168 telnetStatus00
1.3.6.1.4.1.161.19.3.3.2.169 ftpStatus00
1.3.6.1.4.1.161.19.3.3.2.170 tftpStatus00
1.3.6.1.4.1.161.19.3.3.2.171 userMode00
1.3.6.1.4.1.161.19.3.3.2.172 tcpAckPriority00
1.3.6.1.4.1.161.19.3.3.2.173 codePointSelect00
1.3.6.1.4.1.161.19.3.3.2.174 prioritySelect00
1.3.6.1.4.1.161.19.3.3.2.175 auxPortEnable00
1.3.6.1.4.1.161.19.3.3.2.176 poeAuxEnable00
1.3.6.1.4.1.161.19.3.3.2.177 whispUsrAuth00
1.3.6.1.4.1.161.19.3.3.2.178 ipv6State00
1.3.6.1.4.1.161.19.3.3.2.179 dhcpv6State00
1.3.6.1.4.1.161.19.3.3.2.180 lan1Dhcpv6Release00
1.3.6.1.4.1.161.19.3.3.2.181 lan1Dhcpv6Renew00
1.3.6.1.4.1.161.19.3.3.2.201 lan1DhcpRelease00
1.3.6.1.4.1.161.19.3.3.2.202 lan1DhcpRenew00
1.3.6.1.4.1.161.19.3.3.2.203 lan3DhcpRelease00
1.3.6.1.4.1.161.19.3.3.2.204 lan3DhcpRenew00
1.3.6.1.4.1.161.19.3.3.2.205 natDhcpRelease00
1.3.6.1.4.1.161.19.3.3.2.206 natDhcpRenew00
1.3.6.1.4.1.161.19.3.3.2.207 region00
1.3.6.1.4.1.161.19.3.3.2.208 regionAsia00
1.3.6.1.4.1.161.19.3.3.2.209 regionEurope00
1.3.6.1.4.1.161.19.3.3.2.210 regionNorthAmerica00
1.3.6.1.4.1.161.19.3.3.2.211 regionOceania00
1.3.6.1.4.1.161.19.3.3.2.212 regionSouthAmerica00
1.3.6.1.4.1.161.19.3.3.2.213 regionOtherRegulatory00
1.3.6.1.4.1.161.19.3.3.2.214 interleave00
1.3.6.1.4.1.161.19.3.3.2.215 receiveQualityDebug00
1.3.6.1.4.1.161.19.3.3.2.217 regionAfrica00
1.3.6.1.4.1.161.19.3.3.2.218 addCustomFreqMimo00
1.3.6.1.4.1.161.19.3.3.2.219 removeCustomFreqMimo00
1.3.6.1.4.1.161.19.3.3.2.220 timedSpectrumAnalysisDurationBox00