interface
Syntax
Release Information
This command was introduced prior to release 2.1.1.
Starting with release 2.1.1, this command can be used for mgt interfaces.
Starting with release 4.1, this command can be used for interfaces on the UFM6.
Starting with release 4.2, this command supports QPSK modulation for an optical channel interface on the 400G Coherent MSA XCVR on a UFM6.
Description
This command configures an interface. If the interface does not exist, the interface is created.
Options
Table 1: Interface Definition Parameters
Parameter | Description | Range | Default Value |
|---|---|---|---|
name:location | The interface name followed by the location identifier. | The following names are allowed:
| None |
type type | The interface type. The interface type must be consistent with the interface name. | The following types are allowed:
| None |
Table 2: Physical Layer Parameters (Varies with Interface)
Parameter | Description | Range | Default Value |
|---|---|---|---|
cprws size | Carrier phase recovery window size (applicable to interfaces on the 100G Coherent MSA XCVR, 400G Coherent MSA XCVR, and the 100G Coherent CFP only). Note: For the 400G Coherent MSA XCVR, this attribute is configured on the optical channel interface only. | 100G Coherent MSA XCVR:
400G Coherent MSA XCVR:
100G Coherent CFP:
| 100G Coherent MSA XCVR: 32-symbols 400G Coherent MSA XCVR: 32-symbols 100G Coherent CFP: 48-symbols |
expected-section-trace string | The section level trace message expected in the received SONET/SDH signal. This applies to SONET/SDH interfaces only. | 0 to 62 characters | An empty string, which means no section trace expected. |
expected-trace string | The trace message expected in the received OTU signal. | 0 to 64 characters | An empty string, which means no trace message expected. |
fec-type type | The forward error correction (FEC) type used in the OTU link. Note: This attribute is not supported on an OTU4 interface on the UFM6 400G Coherent MSA XCVR. You cannot configure the FEC on an individual OTU4 on the UFM6. You can only configure the FEC for the optical channel interface only. | The following are the allowed types:
Note: Not all FEC types are supported for all protocols and transceivers. See Forward Error Correction (FEC) Types for more details. | 100G Coherent MSA XCVR: soft-fec 400G Coherent MSA XCVR: sd-fec-25pc 100G Coherent CFP: soft-fec |
fpsd {true | false} | Enables or disables fault propagation shutdown (FPSD) for ethernetCsmacd interfaces. If a fault is detected upstream (in the receive from backplane direction) and this parameter is set to true, the system turns off the laser to propagate the fault signal. If this parameter is set to false, the system transmits a Local Fault indication instead. In either case, the signal in the link receive direction is unaffected. | true false | true |
frequency frequency | The frequency of the optical signal in THz. For a single-channel transceiver, this indicates the frequency at which the transceiver operates. For a multi-channel transceiver, this indicates the frequency of the first channel (channel with the highest frequency number). Note: A frequency or wavelength value is required to create an interface on tunable transceivers. You do not need to configure both a frequency and a wavelength. If you configure both a frequency and a wavelength, the values must be consistent. Note: For the 400G Coherent MSA XCVR, this attribute is configured on the optical channel interface only. | Refer to DWDM 50-GHz Wavelength Plan for valid DWDM frequency and wavelength grid values. The specified frequency must match a valid grid frequency. | None |
grid {f50GHz|f100GHz|f200GHz} | The frequency spacing of channels on the WDM composite signal. | f50GHz: 50 GHz grid spacing f100GHz: 100 GHz grid spacing f200GHz: 200 GHz grid spacing | None |
lldp-snoop {disable|enable} | Configures LLDP snooping. Note: Supported only on Ethernet interfaces. | disable enable | disable |
loopback-mode {facility|noLoopback|terminal} | Configures or releases loopback of traffic on an interface. | facility noLoopback terminal | noLoopback |
mapping {asynchronous|bit-synchronous} | Specifies the type of mapping of the SONET/SDH signal onto an ODU payload. | asynchronous synchronous | asynchronous |
multiplex-mode {no-multiplex|gmp-capable} | This is used to configure the OPU payload of the ODU for multiplexing lower order OPUs. When set to gmp-capable, the ODU multiplex structure supports multiplexing of ODTUk.ts or ODTUk.ts and ODTUjk (payload type 0x21). | no-multiplex gmp-capable | no-multiplex |
odtg | This is the list of optical data tributary groups (ODTG) that are configured on the ODU if the payload type is set to gmp-capable. Each ODTG contains a lower order ODU. | ||
prbs-mode {egress|ingress|no-prbs} | Configures PRBS signal generation on the interface. Refer to prbs-mode for usage. Note: This parameter is not supported on UFM6 interfaces. | egress ingress no-prbs | no-prbs |
sd-deg-thr percent | The threshold used to evaluate whether a 1-second interval is considered a degraded interval for OTU interfaces. The threshold is the percentage of errored blocks in a 1-second interval. If the percentage of errored blocks detected in a 1-second interval exceeds this threshold, the interval is considered degraded. | 0.0001 to 100.0 | 0.1 |
sd-degm num_intervals | The number of consecutive degraded intervals required to raise a signal degrade fault for OTU interfaces. When the value is set to 0, signal degrade monitoring is disabled. | 0, 2 to 10 | 8 |
sd-thr neg_exponent | The threshold used to evaluate whether a SONET/SDH signal degrade fault has occurred. If the bit error rate exceeds the specified threshold, a signal degrade fault is raised. The value entered is a negative exponent. For example, a value of 4 is interpreted as 10 x 10-4. When the value is set to 0, signal degrade monitoring is disabled. | 0, 4 to 12 | 6 |
signaling-mode {legacy|standard} | The signaling mode for interworking with legacy equipment on Ethernet interfaces. See the BTI7800 Series Software Configuration Guide for details. | legacy standard | standard |
tx-power power | The desired output signal power in dBm (applicable to interfaces on the 100G Coherent MSA XCVR, the 400G Coherent MSA XCVR, and the 100G Coherent CFP only). Note: For the 400G Coherent MSA XCVR, this attribute is configured on the optical channel interface only. | Varies depending on the transceiver. See the transceiver specifications in the BTI7800 Series Hardware Overview and Installation Guide for details. | Varies depending on the transceiver. |
tx-trace string | The trace message inserted into the transmitted OTU signal. | 0 to 64 characters | UFM6: A combination of the management IP address and the ifIndex. Other UFMs: A combination of the management IP address and the interface identifier. |
wavelength wavelength | Wavelength of the optical signal (nm). This attribute is set automatically when you set the frequency. For a single-channel transceiver, this indicates the wavelength at which the transceiver operates. For a multi-channel transceiver, this indicates the wavelength of the first channel (channel with the lowest wavelength number). Note: A frequency or wavelength value is required to create an interface on tunable transceivers. You do not need to configure both a frequency and a wavelength. If you configure both a frequency and a wavelength, the values must be consistent. Note: For the 400G Coherent MSA XCVR, this attribute applies to the optical channel interface only. | Refer to DWDM 50-GHz Wavelength Plan for valid DWDM frequency and wavelength grid values. The specified wavelength does not need to match a valid grid wavelength. The BTI7800 converts the specified wavelength to a frequency rounded to the nearest 50 GHz. The resulting frequency is then checked against valid grid values. If the frequency matches a valid grid value, the CLI updates the frequency attribute with the resulting frequency when you commit the change. If the frequency does not match a valid grid value (that is, outside the range), the CLI returns an error when you try to commit the change. | None |
Table 3: Parameters Specific to an Interface Type (Varies with Interface)
Parameter | Description | Range | Default Value |
|---|---|---|---|
Interfaces of type mgt (releases 2.1.1 and higher) | |||
channel {odcc | mcc} | The channel to be used for management traffic on this interface. Management traffic can be carried on the optical data communications channel, which is carried within the OSC on optical interfaces. | mcc: not supported odcc: optical data communications channel | odcc |
l1-interface interface | The physical interface on which the management channel resides. | An existing physical interface, subject to the following: The interface must match the channel selection. If the channel is odcc, then the l1-interface must be an OSC interface. | None |
Parameter | Description | Range | Default Value |
|---|---|---|---|
Interfaces of type opticalChannel | |||
modulation {16-qam | qpsk} | The modulation format. | 16-qam: two OTU4 signals are modulated onto the single optical carrier qpsk: not supported (releases lower than release 4.2) qpsk: one OTU4 signal is modulated onto the single optical carrier (releases 4.2 and higher) | 16-qam |
Required Privilege Level
Sample Output
bti7800(config)# interface 100ge:1/13/1/1
type ethernetCsmacd bti7800(config-interface-100ge:1/13/1/1)# frequency 191.35 bti7800(config-interface-100ge:1/13/1/1)# commit Commit complete
