OID reference

subportPortMode

1.3.6.1.4.1.42229.1.2.3.7.1.1.4

Description

The working mode of port. For client side: CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable. Default is 100GBE when card created. CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable; applicable to subport 1 to 4; possible values are: 10GBE, not-applicable. …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.42229.1.2.3.7.1.1 (subportEntry)
Node code
4
Node name
subportPortMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.42229.1.2.3.7.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.42229.1.2.3.7.1.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 42229 1 2 3 7 1 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) coriant(42229) products(1) groove(2) equipment(3) subport(7) subportTable(1) subportEntry(1) subportPortMode(4)}
OID-IRI notation
  • /1/3/6/1/4/1/42229/1/2/3/7/1/1/4
  • /ISO/Identified-Organization/6/1/4/1/42229/1/2/3/7/1/1/4
  • /ISO/3/6/1/4/1/42229/1/2/3/7/1/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/42229/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/identified-organization/dod/internet/private/enterprise/coriant/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/identified-organization/dod/internet/private/enterprises/42229/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/identified-organization/dod/internet/private/enterprises/coriant/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/42229/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/coriant/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/42229/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/coriant/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/org/dod/internet/private/enterprise/42229/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/org/dod/internet/private/enterprise/coriant/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/org/dod/internet/private/enterprises/42229/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/org/dod/internet/private/enterprises/coriant/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/org/dod/internet/private/ldap-enterprise/42229/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/org/dod/internet/private/ldap-enterprise/coriant/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/org/dod/internet/private/vendor-objects/42229/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • /iso/org/dod/internet/private/vendor-objects/coriant/products/groove/equipment/subport/subportTable/subportEntry/subportPortMode
  • Additional combinations skipped.

SNMP properties

Value type
CoriantTypesPortMode
Maximum access defined by MIB
read-only
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.

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

Show 2 published definitions

subportPortMode · current

subportPortMode OBJECT-TYPE
    SYNTAX CoriantTypesPortMode 
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION "
	The working mode of port. 
	For client side:
	CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable.
	Default is 100GBE when card created.
	
	CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable;
	applicable to subport 1 to 4; possible values are: 10GBE, not-applicable.
	Default is not-applicable.
						
	For Line side:
	CHM1/CHM2: possible values are: QPSK_100G, 16QAM_200G, 8QAM_300G.
	Default is 16QAM_200G.
	
	non applicable : there shall not be service created on the port or subport
	subport: the port shall create four subports under the port to support 4x10G.
	40GBE: 40GBE service shall be created on the port with default mapping GMP.
	10GBE: 10GBE service shall be created on the subport with default mapping BMP with fixed stuff.
	100GBE: 100GBE service shall be created on the subport with default mapping GMP.
	QPSK_100G: 100G OTU4 service with DP-QPSK coherent modulation format shall be created on the port.
	16QAM_200G: 200G OTUC2 service with DP-16QAM coherent modulation format shall be created on the port.
	8QAM_300G: 300G OTUC3 service with DP-8QAM coherent modulation format shall be created on the coupled two line ports.
	
	Note 4x10G is to create subport managed objects under the port. Each subport can support a 10G service.
						
	Restrictions:
	Changing Port mode shall be allowed only if the impacted port or subport object is administratively down.
	Changing a 'subport' port mode of a port to be other value shall only be allowed only if port-modes of all the subports under the port are 'not-applicable'.
	If there is explicitly cross-connection is created associated with the ODU of the port, change port mode of the port shall be denied.
	If the port mode is a coupled port mode, e.g. 8QAM_300G, port mode can only be edited on the lower number of port within the coupled ports. The other port (or ports if more than two) will have read-only port mode value same as this lowest number port.
	When port/subport is set to admin down, laser will be shutdown, ingress side will insert proper maintenance signal.
	
		Conditions:(../port-type = 'line') or (../port-type = 'client') or (../port-type = 'client-subport')
		
		default value :not-applicable"
::= { subportEntry 4 }

subportPortMode · current

subportPortMode OBJECT-TYPE
    SYNTAX CoriantTypesPortMode 
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION "
	The working mode of port. 
	For client side:
	CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable.
	Default is 100GBE when card created.
	
	CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable;
	applicable to subport 1 to 4; possible values are: 10GBE, not-applicable.
	Default is not-applicable.
						
	For Line side:
	CHM1/CHM2: possible values are: QPSK_100G, 16QAM_200G, 8QAM_300G.
	Default is 16QAM_200G.
	
	non applicable : there shall not be service created on the port or subport
	subport: the port shall create four subports under the port to support 4x10G.
	40GBE: 40GBE service shall be created on the port with default mapping GMP.
	10GBE: 10GBE service shall be created on the subport with default mapping BMP with fixed stuff.
	100GBE: 100GBE service shall be created on the subport with default mapping GMP.
	QPSK_100G: 100G OTU4 service with DP-QPSK coherent modulation format shall be created on the port.
	16QAM_200G: 200G OTUC2 service with DP-16QAM coherent modulation format shall be created on the port.
	8QAM_300G: 300G OTUC3 service with DP-8QAM coherent modulation format shall be created on the coupled two line ports.
	
	Note 4x10G is to create subport managed objects under the port. Each subport can support a 10G service.
						
	Restrictions:
	Changing Port mode shall be allowed only if the impacted port or subport object is administratively down.
	Changing a 'subport' port mode of a port to be other value shall only be allowed only if port-modes of all the subports under the port are 'not-applicable'.
	If there is explicitly cross-connection is created associated with the ODU of the port, change port mode of the port shall be denied.
	If the port mode is a coupled port mode, e.g. 8QAM_300G, port mode can only be edited on the lower number of port within the coupled ports. The other port (or ports if more than two) will have read-only port mode value same as this lowest number port.
	When port/subport is set to admin down, laser will be shutdown, ingress side will insert proper maintenance signal.
	
		Conditions:(../port-type != 'optical') and (../port-type != 'otdr') and (../port-type != 'optical-nomon')
		
		default value :not-applicable"
::= { subportEntry 4 }

Meaning

Descriptions

2 unique

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

Description 1

The working mode of port. For client side: CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable. Default is 100GBE when card created. CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable; applicable to subport 1 to 4; possible values are: 10GBE, not-applicable. Default is not-applicable. For Line side: CHM1/CHM2: possible values are: QPSK_100G, 16QAM_200G, 8QAM_300G. Default is 16QAM_200G. non applicable : there shall not be service created on the port or subport subport: the port shall create four subports under the port to support 4x10G. 40GBE: 40GBE service shall be created on the port with default mapping GMP. 10GBE: 10GBE service shall be created on the subport with default mapping BMP with fixed stuff. 100GBE: 100GBE service shall be created on the subport with default mapping GMP. QPSK_100G: 100G OTU4 service with DP-QPSK coherent modulation format shall be created on the port. 16QAM_200G: 200G OTUC2 service with DP-16QAM coherent modulation format shall be created on the port. 8QAM_300G: 300G OTUC3 service with DP-8QAM coherent modulation format shall be created on the coupled two line ports. Note 4x10G is to create subport managed objects under the port. Each subport can support a 10G service. Restrictions: Changing Port mode shall be allowed only if the impacted port or subport object is administratively down. Changing a 'subport' port mode of a port to be other value shall only be allowed only if port-modes of all the subports under the port are 'not-applicable'. If there is explicitly cross-connection is created associated with the ODU of the port, change port mode of the port shall be denied. If the port mode is a coupled port mode, e.g. 8QAM_300G, port mode can only be edited on the lower number of port within the coupled ports. The other port (or ports if more than two) will have read-only port mode value same as this lowest number port. When port/subport is set to admin down, laser will be shutdown, ingress side will insert proper maintenance signal. Conditions:(../port-type = 'line') or (../port-type = 'client') or (../port-type = 'client-subport') default value :not-applicable

Sources for this description

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

See 1 matching source record

Description 2

The working mode of port. For client side: CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable. Default is 100GBE when card created. CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable; applicable to subport 1 to 4; possible values are: 10GBE, not-applicable. Default is not-applicable. For Line side: CHM1/CHM2: possible values are: QPSK_100G, 16QAM_200G, 8QAM_300G. Default is 16QAM_200G. non applicable : there shall not be service created on the port or subport subport: the port shall create four subports under the port to support 4x10G. 40GBE: 40GBE service shall be created on the port with default mapping GMP. 10GBE: 10GBE service shall be created on the subport with default mapping BMP with fixed stuff. 100GBE: 100GBE service shall be created on the subport with default mapping GMP. QPSK_100G: 100G OTU4 service with DP-QPSK coherent modulation format shall be created on the port. 16QAM_200G: 200G OTUC2 service with DP-16QAM coherent modulation format shall be created on the port. 8QAM_300G: 300G OTUC3 service with DP-8QAM coherent modulation format shall be created on the coupled two line ports. Note 4x10G is to create subport managed objects under the port. Each subport can support a 10G service. Restrictions: Changing Port mode shall be allowed only if the impacted port or subport object is administratively down. Changing a 'subport' port mode of a port to be other value shall only be allowed only if port-modes of all the subports under the port are 'not-applicable'. If there is explicitly cross-connection is created associated with the ODU of the port, change port mode of the port shall be denied. If the port mode is a coupled port mode, e.g. 8QAM_300G, port mode can only be edited on the lower number of port within the coupled ports. The other port (or ports if more than two) will have read-only port mode value same as this lowest number port. When port/subport is set to admin down, laser will be shutdown, ingress side will insert proper maintenance signal. Conditions:(../port-type != 'optical') and (../port-type != 'otdr') and (../port-type != 'optical-nomon') default value :not-applicable

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

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

Status in source: current.

Names: subportPortMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "subportPortMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "CoriantTypesPortMode",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\" The working mode of port. For client side: CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable. Default is 100GBE when card created. CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable; applicable to subport 1 to 4; possible values are: 10GBE, not-applicable. Default is not-applicable. For Line side: CHM1/CHM2: possible values are: QPSK_100G, 16QAM_200G, 8QAM_300G. Default is 16QAM_200G. non applicable : there shall not be service created on the port or subport subport: the port shall create four subports under the port to support 4x10G. 40GBE: 40GBE service shall be created on the port with default mapping GMP. 10GBE: 10GBE service shall be created on the subport with default mapping BMP with fixed stuff. 100GBE: 100GBE service shall be created on the subport with default mapping GMP. QPSK_100G: 100G OTU4 service with DP-QPSK coherent modulation format shall be created on the port. 16QAM_200G: 200G OTUC2 service with DP-16QAM coherent modulation format shall be created on the port. 8QAM_300G: 300G OTUC3 service with DP-8QAM coherent modulation format shall be created on the coupled two line ports. Note 4x10G is to create subport managed objects under the port. Each subport can support a 10G service. Restrictions: Changing Port mode shall be allowed only if the impacted port or subport object is administratively down. Changing a 'subport' port mode of a port to be other value shall only be allowed only if port-modes of all the subports under the port are 'not-applicable'. If there is explicitly cross-connection is created associated with the ODU of the port, change port mode of the port shall be denied. If the port mode is a coupled port mode, e.g. 8QAM_300G, port mode can only be edited on the lower number of port within the coupled ports. The other port (or ports if more than two) will have read-only port mode value same as this lowest number port. When port/subport is set to admin down, laser will be shutdown, ingress side will insert proper maintenance signal. Conditions:(../port-type = 'line') or (../port-type = 'client') or (../port-type = 'client-subport') default value :not-applicable\"",
    "::=",
    "{",
    "subportEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "CoriantTypesPortMode"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The working mode of port. For client side: CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable. Default is 100GBE when card created. CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable; applicable to subport 1 to 4; possible values are: 10GBE, not-applicable. Default is not-applicable. For Line side: CHM1/CHM2: possible values are: QPSK_100G, 16QAM_200G, 8QAM_300G. Default is 16QAM_200G. non applicable : there shall not be service created on the port or subport subport: the port shall create four subports under the port to support 4x10G. 40GBE: 40GBE service shall be created on the port with default mapping GMP. 10GBE: 10GBE service shall be created on the subport with default mapping BMP with fixed stuff. 100GBE: 100GBE service shall be created on the subport with default mapping GMP. QPSK_100G: 100G OTU4 service with DP-QPSK coherent modulation format shall be created on the port. 16QAM_200G: 200G OTUC2 service with DP-16QAM coherent modulation format shall be created on the port. 8QAM_300G: 300G OTUC3 service with DP-8QAM coherent modulation format shall be created on the coupled two line ports. Note 4x10G is to create subport managed objects under the port. Each subport can support a 10G service. Restrictions: Changing Port mode shall be allowed only if the impacted port or subport object is administratively down. Changing a 'subport' port mode of a port to be other value shall only be allowed only if port-modes of all the subports under the port are 'not-applicable'. If there is explicitly cross-connection is created associated with the ODU of the port, change port mode of the port shall be denied. If the port mode is a coupled port mode, e.g. 8QAM_300G, port mode can only be edited on the lower number of port within the coupled ports. The other port (or ports if more than two) will have read-only port mode value same as this lowest number port. When port/subport is set to admin down, laser will be shutdown, ingress side will insert proper maintenance signal. Conditions:(../port-type = 'line') or (../port-type = 'client') or (../port-type = 'client-subport') default value :not-applicable"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

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

Status in source: current.

Names: subportPortMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "subportPortMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "CoriantTypesPortMode",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\" The working mode of port. For client side: CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable. Default is 100GBE when card created. CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable; applicable to subport 1 to 4; possible values are: 10GBE, not-applicable. Default is not-applicable. For Line side: CHM1/CHM2: possible values are: QPSK_100G, 16QAM_200G, 8QAM_300G. Default is 16QAM_200G. non applicable : there shall not be service created on the port or subport subport: the port shall create four subports under the port to support 4x10G. 40GBE: 40GBE service shall be created on the port with default mapping GMP. 10GBE: 10GBE service shall be created on the subport with default mapping BMP with fixed stuff. 100GBE: 100GBE service shall be created on the subport with default mapping GMP. QPSK_100G: 100G OTU4 service with DP-QPSK coherent modulation format shall be created on the port. 16QAM_200G: 200G OTUC2 service with DP-16QAM coherent modulation format shall be created on the port. 8QAM_300G: 300G OTUC3 service with DP-8QAM coherent modulation format shall be created on the coupled two line ports. Note 4x10G is to create subport managed objects under the port. Each subport can support a 10G service. Restrictions: Changing Port mode shall be allowed only if the impacted port or subport object is administratively down. Changing a 'subport' port mode of a port to be other value shall only be allowed only if port-modes of all the subports under the port are 'not-applicable'. If there is explicitly cross-connection is created associated with the ODU of the port, change port mode of the port shall be denied. If the port mode is a coupled port mode, e.g. 8QAM_300G, port mode can only be edited on the lower number of port within the coupled ports. The other port (or ports if more than two) will have read-only port mode value same as this lowest number port. When port/subport is set to admin down, laser will be shutdown, ingress side will insert proper maintenance signal. Conditions:(../port-type != 'optical') and (../port-type != 'otdr') and (../port-type != 'optical-nomon') default value :not-applicable\"",
    "::=",
    "{",
    "subportEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "CoriantTypesPortMode"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The working mode of port. For client side: CHM1: applicable to port 3 to 6; possible values are: 100GBE, not-applicable. Default is 100GBE when card created. CHM2: applicable to port 3 to 11; possible values are: 40GBE, subport, not-applicable; applicable to subport 1 to 4; possible values are: 10GBE, not-applicable. Default is not-applicable. For Line side: CHM1/CHM2: possible values are: QPSK_100G, 16QAM_200G, 8QAM_300G. Default is 16QAM_200G. non applicable : there shall not be service created on the port or subport subport: the port shall create four subports under the port to support 4x10G. 40GBE: 40GBE service shall be created on the port with default mapping GMP. 10GBE: 10GBE service shall be created on the subport with default mapping BMP with fixed stuff. 100GBE: 100GBE service shall be created on the subport with default mapping GMP. QPSK_100G: 100G OTU4 service with DP-QPSK coherent modulation format shall be created on the port. 16QAM_200G: 200G OTUC2 service with DP-16QAM coherent modulation format shall be created on the port. 8QAM_300G: 300G OTUC3 service with DP-8QAM coherent modulation format shall be created on the coupled two line ports. Note 4x10G is to create subport managed objects under the port. Each subport can support a 10G service. Restrictions: Changing Port mode shall be allowed only if the impacted port or subport object is administratively down. Changing a 'subport' port mode of a port to be other value shall only be allowed only if port-modes of all the subports under the port are 'not-applicable'. If there is explicitly cross-connection is created associated with the ODU of the port, change port mode of the port shall be denied. If the port mode is a coupled port mode, e.g. 8QAM_300G, port mode can only be edited on the lower number of port within the coupled ports. The other port (or ports if more than two) will have read-only port mode value same as this lowest number port. When port/subport is set to admin down, laser will be shutdown, ingress side will insert proper maintenance signal. Conditions:(../port-type != 'optical') and (../port-type != 'otdr') and (../port-type != 'optical-nomon') default value :not-applicable"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.42229)

Peter Litz

Siblings (18)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.42229.1.2.3.7.1.1.1 subportId00
1.3.6.1.4.1.42229.1.2.3.7.1.1.2 subportPortName00
1.3.6.1.4.1.42229.1.2.3.7.1.1.3 subportPortType00
1.3.6.1.4.1.42229.1.2.3.7.1.1.5 subportAdminStatus00
1.3.6.1.4.1.42229.1.2.3.7.1.1.6 subportOperStatus00
1.3.6.1.4.1.42229.1.2.3.7.1.1.7 subportAvailStatus00
1.3.6.1.4.1.42229.1.2.3.7.1.1.8 subportAliasName00
1.3.6.1.4.1.42229.1.2.3.7.1.1.9 subportServiceLabel00
1.3.6.1.4.1.42229.1.2.3.7.1.1.10 subportConnectedTo00
1.3.6.1.4.1.42229.1.2.3.7.1.1.11 subportArcConfig00
1.3.6.1.4.1.42229.1.2.3.7.1.1.12 subportArcState00
1.3.6.1.4.1.42229.1.2.3.7.1.1.13 subportArcSubState00
1.3.6.1.4.1.42229.1.2.3.7.1.1.14 subportArcTimer00
1.3.6.1.4.1.42229.1.2.3.7.1.1.15 subportArcRemainingTime00
1.3.6.1.4.1.42229.1.2.3.7.1.1.16 subportRxOpticalPower00
1.3.6.1.4.1.42229.1.2.3.7.1.1.17 subportTxOpticalPower00
1.3.6.1.4.1.42229.1.2.3.7.1.1.18 subportExternalConnectivity00
1.3.6.1.4.1.42229.1.2.3.7.1.1.19 subportDirectionType00