Configuring physical ports with CLI
This section provides information to configure cards, MDAs, and ports.
Preprovisioning guidelines
SR OSs have a console port, either located on the CPM or CCM, or integrated into the chassis (on the 7750 SR-c4 models), to connect terminals to the router.
Configure command options from a system console connected to a router console port, using Telnet to access a router remotely or SSH to open a secure shell connection.
Predefining entities
To initialize a card, the chassis slot, line card type, and MDA type must match the preprovisioned command options. In this context, preprovisioning means to configure the entity type (such as the card type, MDA type, port, and interface) that is planned for a chassis slot, card, or MDA. Preprovisioned entities can be installed but not enabled or the slots can be configured but remain empty until populated. Provisioning means that the preprovisioned entity is installed and enabled.
You can:
Preprovision ports and interfaces after the line card and MDA types are specified.
Install line cards in slots with no pre-configuration command options specified. After the card is installed, the card and MDA types must be specified.
Install a line card in a slot provisioned for a different card type (the card does not initialize). The existing card and MDA configuration must be deleted and replaced with the current information.
Preprovisioning a port
Before a port can be configured, the slot must be preprovisioned with an allowed card type and the MDA must be preprovisioned with an allowed MDA type. Some recommendations to configure a port include:
-
Ethernet
-
Configure an access port for customer facing traffic on which services are configured.
-
An encapsulation type may be specified to distinguish services on the port or channel. Encapsulation types are not required for network ports.
-
To configure an Ethernet access port, see Configuring Ethernet access ports.
-
Maximizing bandwidth use
After ports are preprovisioned, Link Aggregation Groups (LAGs) can be configured to increase the bandwidth available between two nodes.
All physical links or channels in a LAG/bundle combine to form one logical connection. A LAG/bundle also provides redundancy in case one or more links that participate in the LAG/bundle fail.
Basic configuration
The most basic configuration must specify the following:
-
chassis slot
-
line card type (must be an allowed card type)
-
MDA slot
-
MDA (must be an allowed MDA type)
-
specific port to configure
The following is an example of card configuration for the 7750 SR.
MD-CLI
[ex:]
A:admin@node-2# admin show configuration
configure {
card 6 {
card-type iom4-e
mda 1 {
mda-type me1-100gb-cfp2
}
fp 1 {
}
}
card 7 {
card-type iom4-e
mda 1 {
mda-type me10-10gb-sfp+
}
mda 2 {
mda-type me1-100gb-cfp2
}
fp 1 {
}
}
card 8 {
card-type iom4-e
mda 1 {
mda-type me10-10gb-sfp+
}
}classic CLI
A:node-2> admin display-config
echo "Card Configuration"
#--------------------------------------------------
card 6
card-type iom4-e
no shutdown
exit
card 7
card-type iom4-e
mda 1
mda-type me10-10gb-sfp+
no shutdown
exit
mda 2
mda-type me1-100gb-cfp2
no shutdown
exit
no shutdown
exit
card 8
card-type iom4-e
no shutdown
exit
#--------------------------------------------------The following is an example of card configurations for the 7950 XRS.
MD-CLI
[ex:/configure card 1]
A:admin@node-2# info
card-type xcm-x20
mda 1 {
mda-type x2-100g-tun
}
mda 2 {
mda-type x40-10g-sfp
}
fp 1 {
}classic CLI
A:node-2>configure card 1# info
----------------------------------------------
card-type xcm-x20
mda 1
mda-type x2-100g-tun
no shutdown
exit
mda 2
mda-type x40-10g-sfp
no shutdown
exit
no shutdown
----------------------------------------------Common configuration tasks
The following sections are basic system tasks that must be performed.
Configuring cards and MDAs
Card configurations include a chassis slot designation. A slot must be preconfigured with the type of cards and MDAs which are allowed to be provisioned.
The following example shows card and MDA configurations for the 7750 SR or 7450 ESS.
MD-CLI
[ex: /configure card 8]
A:admin@node-2# info
card-type iom4-e
mda 1 {
mda-type me10-10gb-sfp+
}
mda 2 {
mda-type me1-100gb-cfp2
}
fp 1 {
}
classic CLI
A:node-2>config>card# info
#--------------------------------------------------
card 8
card-type iom4-e
mda 1
mda-type me10-10gb-sfp+
no shutdown
exit
mda 2
mda-type me1-100gb-cfp2
no shutdown
exit
no shutdown
exit
#----------------------------------------------
The following example shows card configurations for the 7950 XRS.
MD-CLI
[ex:/configure card 1]
A:admin@node-2# info
card-type xcm-x20
mda 1 {
mda-type x40-10g-sfp
}
mda 2 {
mda-type x2-100g-tun
}
fp 1 {
}classic CLI
A:node-2>config>card# info
----------------------------------------------
card-type xcm-x20
mda 1
mda-type x40-10g-sfp
no shutdown
exit
mda 2
mda-type x2-100g-tun
no shutdown
exit
no shutdown
----------------------------------------------
Configuring FP network pools
configure qosThe following example shows an FP pool configuration for 7750 SR or 7450 ESS.
MD-CLI
[ex:/configure card 1 fp 1]
A:admin@node-2# info
ingress {
network {
queue-policy "10"
pool "default" {
slope-policy "slope1"
resv-cbs {
cbs 50
}
}
}
}classic CLI
A:node-2>config>card>fp# info
----------------------------------------------
ingress
network
pool "default"
resv-cbs 50
slope-policy "slope1"
exit
queue-policy "10"
exit
exit
----------------------------------------------Configuring ports
This section provides the CLI and examples to configure port command options.
Configuring port pools
The buffer space is portioned out on a per port basis. Each port gets an amount of buffering which is its fair-share based on the port’s bandwidth compared to the overall active bandwidth.
This mechanism takes the buffer space available and divides it into a portion for each port based on the port’s active bandwidth relative to the amount of active bandwidth for all ports associated with the buffer space. The number of ports sharing the same buffer space depends on the type of MDAs populated on the IOM. An active port is considered to be any port that has an active queue associated. After a queue is created for the port, the system allocates the appropriate amount of buffer space to the port. This process is independently performed for both ingress and egress.
Normally, the amount of active bandwidth is considered as opposed to total potential bandwidth for the port when determining the port’s fair share. If a port is channelized and not all bandwidth is allocated, only the bandwidth represented by the configured channels with queues configured is counted toward the bandwidth represented by the port. Also, if a port may operate at variable speeds (as in some Ethernet ports), only the current speed is considered. Based on the above, the number of buffers managed by a port may change because of queue creation and deletion, channel creation and deletion and port speed variance on the local port or other ports sharing the same buffer space.
- MD-CLI
configure port modify-buffer-allocation percentage-of-rate egress configure port modify-buffer-allocation percentage-of-rate ingress - classic
CLI
configure port modify-buffer-allocation egr-percentage-of-rate configure port modify-buffer-allocation ing-percentage-of-rate
To modify (in this example, to double) the size of buffer allocated on ingress for a port.
MD-CLI
configure port 1/2/1 modify-buffer-allocation-rate percentage-of-rate ingress 200classic CLI
configure port 1/2/1 modify-buffer-allocation-rate ing-percentage-of-rate 200To modify (in this example, to double) the size of buffer allocated on egress for a port.
MD-CLI
configure port 1/2/1 modify-buffer-allocation-rate percentage-of-rate egress 200classic CLI
configure port 1/2/1 modify-buffer-allocation-rate egr-percentage-of-rate 200The default buffer allocation has the following characteristics:
-
Each port manages a buffer according to its active bandwidth (ports with equal active bandwidth get the same buffer size).
-
An access port has 2 default pools created: access-ingress and access-egress.
-
A network port has 2 default pools created: ingress-FP (common pool for all ingress network ports) and network-egress.
-
All queues defined for a port receive buffers from the same buffer pool.
The following example shows port pool configurations.
MD-CLI
[ex:/configure port 1/1/1]
A:admin@node-2# info
admin-state enable
access {
egress {
pool "default" {
slope-policy "slopePolicy1"
}
}
}
network {
egress {
pool "default" {
slope-policy "slopePolicy2"
}
}
}classic CLI
A:node-2>config>port# info
----------------------------------------------
access
egress
pool
slope-policy "slopePolicy1"
exit
exit
exit
network
egress
pool
slope-policy "slopePolicy2"
exit
exit
exit
no shutdown
----------------------------------------------
The following shows a CBS configuration over subscription example.
MD-CLI
[ex:/configure port 1/1/1]
A:admin@node-2# info
admin-state enable
access {
ingress {
pool "default" {
amber-alarm-threshold 10
resv-cbs {
cbs 10
amber-alarm-action {
step 1
max 30
}
}
}
}
}
ethernet {
mode access
encap-type dot1q
}
classic CLI
A:node-2>config>port# info
----------------------------------------------
access
ingress
pool
amber-alarm-threshold 10
resv-cbs 10 amber-alarm-action step 1 max 30
exit
exit
exit
ethernet
mode access
encap-type dot1q
exit
no shutdown
Changing hybrid-buffer-allocation
The following example shows a hybrid-buffer-allocation value change (from default) for ingress. In this example, the network-egress buffer pool is two times the size of the access-egress.
MD-CLI
[ex:/configure port 1/1/2 hybrid-buffer-allocation]
A:admin@node-2# info
egress-weight {
access 20
network 40
}
classic CLI
A:node-2config>port>hybrid-buffer-allocation# info
----------------------------------------------
egr-weight access 20 network 40
Configuring Ethernet ports
Configuring Ethernet network ports
A network port is network-facing and participates in the service provider transport or infrastructure network processes.
The following example shows a network port configuration.
MD-CLI
[ex:/configure port A/3]
A:admin@node-2# info
admin-state enable
description "Ethernet network port"
classic CLI
A:node-2config>port# info
----------------------------------------------
description "Ethernet network port"
ethernet
exit
no shutdown
----------------------------------------------
Configuring Ethernet access ports
Services are configured on access ports that are used for customer-facing traffic. If a SAP is to be configured on a port, it must be configured as access mode. When a port is configured for access mode, the appropriate encapsulation type can be specified to distinguish the services on the port. After a port has been configured for access mode, multiple services can be configured on the port.
The following example shows an Ethernet access port configuration.
MD-CLI
[ex:/configure port 1/2/3]
A:admin@node-2# info
admin-state enable
description "Ethernet access port"
access {
egress {
pool "default" {
slope-policy "slopePolicy1"
}
}
}
ethernet {
mode access
encap-type dot1q
}
network {
egress {
pool "default" {
slope-policy "slopePolicy2"
}
}
}classic CLI
A:node-2>config>port# info
----------------------------------------------
description "Ethernet access port"
access
egress
pool
slope-policy "slopePolicy1"
exit
exit
exit
network
egress
pool
slope-policy "slopePolicy2"
exit
exit
exit
ethernet
mode access
encap-type dot1q
exit
no shutdown
----------------------------------------------Configuring an 802.1x authentication port
The following example shows an 802.1x port configuration.
MD-CLI
[ex:/configure port 1/2/4 ethernet dot1x]
A:admin@node-2# info detail
...
admin-state enable
max-authentication-requests 2
port-control auto
quiet-period 60
radius-policy dot1xpolicy
server-timeout 30
supplicant-timeout 30
transmit-period 30
tunneling false
tunnel-dot1q true
tunnel-qinq true
re-authentication {
period 3600
}
...
classic CLI
A:node-2>config>port>ethernet>dot1x# info detail
----------------------------------------------
port-control auto
radius-plcy dot1xpolicy
re-authentication
re-auth-period 3600
max-auth-req 2
transmit-period 30
quiet-period 60
supplicant-timeout 30
server-timeout 30
no tunneling
no shutdown
----------------------------------------------
Configuring OTU port command options
The following example shows an OTU port configuration:
MD-CLI
[ex:/configure port 3/2/1 otu]
A:admin@node-2# info detail
...
fec enhanced
otu2-lan-data-rate 11.049
sd-threshold 7
sf-threshold 5
sf-sd-method fec
report-alarm {
loc true
los true
lof true
lom true
otu-ais false
otu-ber-sf true
otu-ber-sd false
otu-bdi true
otu-tim false
otu-iae false
otu-biae false
fec-sf true
fec-sd false
fec-fail false
fec-uncorr false
odu-ais false
odu-oci false
odu-lck false
odu-bdi false
odu-tim false
opu-plm false
}
...
path-monitoring {
trail-trace-identifier {
## mismatch-reaction
expected {
auto-generated
## string
## bytes
}
transmit {
auto-generated
## string
## bytes
}
}
}
payload-structure-identifier {
payload {
expected auto
## mismatch-reaction
transmit auto
}
}
section-monitoring {
trail-trace-identifier {
## mismatch-reaction
expected {
auto-generated
## string
## bytes
}
transmit {
auto-generated
## string
## bytes
}
}
}classic CLI
A:node-2>config>port>otu# info detail
----------------------------------------------
otu2-lan-data-rate 11.049
sf-sd-method fec
sf-threshold 5
sd-threshold 7
fec enhanced
no report-alarm otu-ais otu-ber-sd otu-tim otu-iae otu-biae fec-sd
no report-alarm fec-fail fec-uncorr odu-ais odu-oci odu-lck odu-bdi
no report-alarm odu-tim opu-plm
report-alarm loc los lof lom otu-ber-sf otu-bdi fec-sf
sm-tti
tx auto-generated
expected auto-generated
no mismatch-reaction
exit
pm-tti
tx auto-generated
expected auto-generated
no mismatch-reaction
exit
psi-payload
tx auto
expected auto
no mismatch-reaction
exit
----------------------------------------------
The following example shows the show port port-id otu detail for the preceding default OTU configuration.
show port 3/2/1 otu detail===============================================================================
OTU Interface
===============================================================================
OTU Status : Enabled FEC Mode : enhanced
Async Mapping : Disabled Data Rate : 11.049 Gb/s
Cfg Alarms : loc los lof lom otu-ber-sf otu-bdi fec-sf
Alarm Status :
SF/SD Method : FEC SF Threshold : 1E-5
SD Threshold : 1E-7
SM-TTI Tx (auto) : ALA-A:3/2/1/C44
SM-TTI Ex (bytes) : (Not Specified)
SM-TTI Rx : ALA-A:5/2/1/C34
OTU-TIM reaction : none
PM-TTI Tx (auto) : ALA-A:3/2/1/C44
PM-TTI Ex (bytes) : (Not Specified)
PM-TTI Rx : ALA-A:5/2/1/C34
ODU-TIM reaction : none
PSI-PT Tx (auto) : 0x03 (syncCbr)
PSI-PT Ex (auto) : 0x03 (syncCbr)
PSI-PT Rx : 0x03 (syncCbr)
OPU-PLM reaction : none
===============================================================================
OTU Statistics
===============================================================================
Elapsed Seconds 10
-------------------------------------------------------------------------------
Near End Statistics Count
-------------------------------------------------------------------------------
FEC Corrected 0s 0
FEC Corrected 1s 0
FEC Unrrectable Sub-rows 0
FEC ES 0
FEC SES 0
FEC UAS 0
Pre-FEC BER 0.000E+00
Post-FEC BER 0.000E+00
-------------------------------------------------------------------------------
SM BIP8 0
SM ES 0
SM SES 0
SM UAS 0
SM-BIP8-BER 0.000E+00
-------------------------------------------------------------------------------
PM BIP8 0
PM ES 0
PM SES 0
PM UAS 0
PM-BIP8-BER 0.000E+00
-------------------------------------------------------------------------------
NPJ 0
PPJ 0
-------------------------------------------------------------------------------
Far End Statistics Count
-------------------------------------------------------------------------------
SM BEI 0
PM BEI 0
===============================================================================
The window over which the Bit Error Rate (BER) determined is based on the configured threshold level. The higher the error rate the shorter the window and as the error rate decreases the window increases. Configured BER thresholds and window lengths lists the configured BER thresholds and corresponding window lengths.
| Configured BER threshold | Window length |
|---|---|
|
10^-3 |
8ms |
|
10^-4 |
8ms |
|
10^-5 |
8ms |
|
10^-6 |
13ms |
|
10^-7 |
100ms |
|
10^-8 |
333ms |
|
10^-9 |
1.66s |
Configuring LAG
LAG configurations should include at least two ports. Other considerations include the following.
-
A maximum of 64 ports (depending on the lag-id) can be included in a LAG. All ports in the LAG must share the port characteristics inherited from the primary port.
-
Auto-negotiation must be disabled or set to limited mode for ports that are part of a LAG, to guarantee a specific port speed.
-
Ports in a LAG must be configured as full duplex.
The following example shows the LAG configuration output.
MD-CLI
[ex:/configure lag "lag-2"]
A:admin@node-2# info
description "LAG2"
mac-address 04:68:ff:00:00:01
dynamic-cost true
port-threshold {
value 4
action down
}
port 1/1/1 {
}
port 1/3/1 {
}
port 1/5/1 {
}
port 1/7/1 {
}
port 1/9/1 {
} classic CLI
A:node-2>config>lag# info detail
----------------------------------------------
description "LAG2"
mac 04:68:ff:00:00:01
port 1/1/1
port 1/3/1
port 1/5/1
port 1/7/1
port 1/9/1
dynamic-cost
port-threshold 4 action down
----------------------------------------------Configuring BFD on LAG links
BFD can be configured under the LAG context to create and establish the micro-BFD session per link after the LAG and associated links have been configured. An IP interface must be associated with the LAG or a VLAN within the LAG, if dot1q encapsulation is used, before the micro-BFD sessions can be established.
The following contexts are used to configure BFD over LAG links:
- MD-CLI
configure lag bfd-liveness family - classic
CLI
configure lag bfd family
When configuring the local and remote IP address for the BFD over LAG link sessions, the local-ip-address value should always match an IP address associated with the IP interface to which this LAG is bound. In addition, the remote-ip-address value should match an IP address on the remote system and should also be in the same subnet as the local-ip-address. If the LAG bundle is re-associated with a different IP interface, the local-ip-address and remote-ip-address values should be modified to match the new IP subnet. The local-ip-address and remote-ip-address values do not have to match a configured interface in the case of tagged LAG/ports.
Configuring the following optional command options for the BFD over LAG links is supported.
-
transmit-interval
This command option specifies the transmit timer interval used for micro-BFD session over the associated LAG links.
-
receive-interval
This command option specifies the receive interval timer used for micro-BFD session over the associated LAG links.
-
multiplier
This command option specifies the detect multiplier used for a micro-BFD session over the associated LAG links.
-
max-setup-time
This command option specifies how long a link remains active if BFD is enabled after the LAG and associated links are active and in a forwarding state.
-
max-admin-down-time
This command option specifies how long the system waits before bringing the associated link out of service if an ADMIN-DOWN state message is received from the far end.
Perform the following steps to enable and configure BFD over the individual LAG links:
- Enable BFD within the LAG context, which also enters the CLI into the BFD context.
- Configure the address family for the micro-BFD sessions. Only one address family can be configured per LAG.
- Configure the local IP address for the BFD sessions.
-
Configure the remote IP address for the BFD sessions.
MD-CLI
[ex:/configure] A:admin@node-2# info ... lag "lag-2" { admin-state enable bfd-liveness { ipv4 { admin-state enable receive-interval 1000 transmit-interval 1000 local-ip-address 10.120.1.2 remote-ip-address 10.120.1.1 } } }classic CLIA:node-2config>lag# info ---------------------------------------------- bfd family ipv4 local-ip-address 10.120.1.2 receive-interval 1000 remote-ip-address 10.120.1.1 transmit-interval 1000 no shutdown exit exit no shutdown
Configuring G.8031 protected Ethernet tunnels
Ethernet tunnel configuration can include at most two paths. Other considerations include:
-
A path contains one member port and one control-tag (backbone VLAN ID/BVID).
-
If the user wants to replace an existing member port or a control-tag, the whole path needs to be shutdown first. The alternate path is activated as a result keeping the traffic interruption to a minimum. Then the whole path must be deleted and re-created. To replace an existing member port or control tag, the whole path needs to be shutdown first. The alternate path is activated as a result keeping traffic interruption to a minimum. Then the whole path must be deleted, the alternate path precedence modified to primary before re-creating the new path.
-
The Ethernet tunnel inherits the configuration from the first member port. The following port-level configuration needs to be the same between member ports of an Ethernet tunnel:
configure port ethernet access egress queue-group configure port access egress pool configure port ethernet dot1q-etype configure port ethernet qinq-etype configure port ethernet pbb-etype configure port ethernet mtu- MD-CLI
configure port ethernet egress port-scheduler-policy - classic
CLI
configure port ethernet egress-scheduler-policy
- MD-CLI
-
The user can update these port command options only if the port is the sole member of an Ethernet tunnel. This means that in the example that follows, the user needs to remove port 1/1/4 and port 1/1/5 before being allowed to modify 1/1/1 for the preceding command options.
classic CLI
A:node-2>config# eth-tunnel 1
path 1
member 1/1/1
path 2
member 1/1/4
A:node-2>config# eth-tunnel 2
path 1
member 1/1/1
path 2
member 1/1/5
The following example shows eth-tunnel configuration output.
classic CLI
A:node-2>config# port 1/1/1
ethernet
encap-type dot1q
A:node-2>config> port 2/2/2
ethernet
encap-type dot1q
A:node-2>config# eth-tunnel 1
path 1
member 1/1/1
control-tag 100
precedence primary
eth-cfm
mep 51 domain 1 association 1
ccm-enable
low-priority-defect allDef
mac-address 00:AE:AE:AE:AE:AE
control-mep
no shutdown
no shutdown
path 2
member 2/2/2
control-tag 200
eth-cfm
mep 52 domain 1 association 2
ccm-enable
low-priority-defect allDef
mac-address 00:BE:BE:BE:BE:BE
control-mep
no shutdown
no shutdown
Configuring connectors and connector ports
Some assemblies have support for QSFP28 or QSFP-DD transceiver modules. These modules have different variants, some of which provide multiple physical ports out of a single module (breakout modules). There is a QSFP28 breakout module that supports ten physical 10 Gb Ethernet ports. On assemblies that support these breakout variants, the front panel cages are modeled as connectors instead of as direct ports. The connector must be configured for the type of breakout module that is to be inserted and then the appropriate ports are created and can be configured. The options for breakout on specific connectors depend on both the card type and level (or XMA type and level). See the applicable installation guides for details.
The connector reference is in the format slot/mda/connector (for example, 1/1/c3) and the ports owned by the connector use the format slot/mda/connector/port. For example, in a 7750 SR-1 with the 6-port QSFP28 mda-e-xp installed in the first MDA slot, initially there are no ports available, only six connectors:
Use the following command to display the MDA information.
show mda===============================================================================
MDA Summary
===============================================================================
Slot Mda Provisioned Type Admin Operational
Equipped Type (if different) State State
-------------------------------------------------------------------------------
1 1 me6-100gb-qsfp28 up upUse the following command to display the port information.
show port===============================================================================
Ports on Slot 1
===============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
1/1/c1 Up No Down - unkn unkn conn
1/1/c2 Up No Down - unkn unkn conn
1/1/c3 Up No Down - unkn unkn conn
1/1/c4 Up No Down - unkn unkn conn
1/1/c5 Up No Down - unkn unkn conn
1/1/c6 Up No Down - unkn unkn conn
===============================================================================
After configuring a module with four 10 Gb breakout ports in connector position 1/1/c1 and a module with one 100 Gb breakout port in connector position 1/1/c2, the physical ports are created.
Use the following commands to configure the port.
configure port 1/1/c1 connector breakout c4-10g
configure port 1/1/c2 connector breakout c1-100gUse the following command to display the updated port information.
show port===============================================================================
Ports on Slot 1
===============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
1/1/c1 Up No Link Up - unkn unkn conn 40GBASE-SR4
1/1/c1/1 Down No Down 9212 9212 - netw null xgige
1/1/c1/2 Down No Down 9212 9212 - netw null xgige
1/1/c1/3 Down No Down 9212 9212 - netw null xgige
1/1/c1/4 Down No Down 9212 9212 - netw null xgige
1/1/c2 Down No Link Up - unkn unkn conn 100GBASE-LR4
1/1/c2/1 Down No Down 1578 1578 - netw null cgige
1/1/c3 Up No Down - unkn unkn conn
1/1/c4 Up No Down - unkn unkn conn
1/1/c5 Up No Down - unkn unkn conn
1/1/c6 Up No Down - unkn unkn conn
These physical ports can now be used as Ethernet port references in other commands.
Use the following command to display the transceiver information that is shown under the connector.
show port 1/1/c1===============================================================================
QSFP28 Connector
===============================================================================
Description : QSFP28 Connector
Interface : 1/1/c1
Admin State : up
Oper State : up
IfIndex : 104939520
Last State Change : 10/31/2017 13:23:22
Last Cleared Time : N/A DDM Events : Enabled
Breakout : c4-10g
Transceiver Data
Transceiver Status : operational
Transceiver Type : QSFP28
Model Number : 3HE10551AARA01 NOK IPU3BFVEAA
TX Laser Wavelength: 850 nm Diag Capable : yes
Number of Lanes : 4
Connector Code : MPO 1x12 Vendor OUI : 44:7c:7f
Manufacture date : 2017/03/12 Media : Ethernet
Serial Number : INHAG8480890
Part Number : TR-FC85S-NNO
Optical Compliance : 100GBASE-SR4 or 25GBASE-SR
Link Length support: 70m for OM3; 100m for OM4
===============================================================================
Transceiver Digital Diagnostic Monitoring (DDM)
===============================================================================
Value High Alarm High Warn Low Warn Low Alarm
-------------------------------------------------------------------------------
Temperature (C) +29.8 +80.0 +75.0 -5.0 -10.0
Supply Voltage (V) 3.29 3.63 3.46 3.14 2.97
===============================================================================
===============================================================================
Transceiver Lane Digital Diagnostic Monitoring (DDM)
===============================================================================
High Alarm High Warn Low Warn Low Alarm
-------------------------------------------------------------------------------
Lane Tx Bias Current (mA) 12.0 10.0 4.5 3.0
Lane Tx Output Power (dBm) 5.40 2.40 -8.40 -11.40
Lane Rx Optical Pwr (avg dBm) 5.40 2.40 -10.30 -13.30
-------------------------------------------------------------------------------
Lane ID Temp(C)/Alm Tx Bias(mA)/Alm Tx Pwr(dBm)/Alm Rx Pwr(dBm)/Alm
-------------------------------------------------------------------------------
1 - 7.1 -0.08 -4.56
2 - 0.0/L-WA -40.00/L-WA -40.00/L-WA
3 - 0.0/L-WA -40.00/L-WA -40.00/L-WA
4 - 0.0/L-WA -40.00/L-WA -40.00/L-WA
===============================================================================Use the following command to display the Ethernet-related items under the connector ports.
show port 1/1/c1/1===============================================================================
Ethernet Interface
===============================================================================
Description : 10-Gig Ethernet
Interface : 1/1/c1/1 Oper Speed : 10 Gbps
Link-level : Ethernet Config Speed : N/A
Admin State : up Oper Duplex : full
Oper State : up Config Duplex : N/A
Physical Link : Yes MTU : 9212
Single Fiber Mode : No Min Frame Length : 64 Bytes
IfIndex : 104939521 Hold time up : 0 seconds
Last State Change : 10/31/2017 13:23:23 Hold time down : 0 seconds
Last Cleared Time : N/A
Phys State Chng Cnt: 1 RS-FEC Mode : None
Configured Mode : network Encap Type : null
Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
PBB Ethertype : 0x88e7
Ing. Pool % Rate : 100 Egr. Pool % Rate : 100
Ing. Pool Policy : n/a
Egr. Pool Policy : n/a
Net. Egr. Queue Pol: default
Egr. Sched. Pol : n/a
HS Scheduler Plcy : default
HS Port Pool Plcy : default
Monitor Port Sched : Disabled
Monitor Agg Q Stats: Disabled
Auto-negotiate : N/A MDI/MDX : N/A
Oper Phy-tx-clock : not-applicable
Accounting Policy : None Collect-stats : Disabled
Acct Plcy Eth Phys : None Collect Eth Phys : Disabled
Egress Rate : Default Ingress Rate : Default
Load-balance-algo : Default LACP Tunnel : Disabled
Access Bandwidth : Not-Applicable Booking Factor : 100
Access Available BW: 0
Access Booked BW : 0
Sflow : Disabled
Suppress Threshold : 2000 Reuse Threshold : 1000
Max Penalties : 16000 Max Suppress Time: 20 seconds
Half Life : 5 seconds
Down-when-looped : Disabled Keep-alive : 10
Loop Detected : False Retry : 120
Use Broadcast Addr : False
Sync. Status Msg. : Disabled Rx Quality Level : N/A
Tx DUS/DNU : Disabled Tx Quality Level : N/A
SSM Code Type : sdh
Down On Int. Error : Disabled DOIE Tx Disable : N/A
CRC Mon SD Thresh : Disabled CRC Mon Window : 10 seconds
CRC Mon SF Thresh : Disabled
EFM OAM : Disabled EFM OAM Link Mon : Disabled
Ignr EFM OAM State : False
Configured Address : 00:03:fa:2b:ef:1a
Hardware Address : 00:03:fa:2b:ef:1a
Cfg Alarm : remote local
===============================================================================
===============================================================================
Traffic Statistics
===============================================================================
Input Output
-------------------------------------------------------------------------------
Octets 0 0
Packets 0 0
Errors 0 0
Utilization (300 seconds) 0.00% 0.00%
===============================================================================
Port Statistics
===============================================================================
Input Output
-------------------------------------------------------------------------------
Unicast Packets 0 0
Multicast Packets 0 0
Broadcast Packets 0 0
Discards 0 0
Unknown Proto Discards 0
===============================================================================
===============================================================================
Ethernet-like Medium Statistics
===============================================================================
Alignment Errors : 0 Sngl Collisions : 0
FCS Errors : 0 Mult Collisions : 0
SQE Test Errors : 0 Late Collisions : 0
CSE : 0 Excess Collisns : 0
Too long Frames : 0 Int MAC Tx Errs : 0
Symbol Errors : 0 Int MAC Rx Errs : 0
In Pause Frames : 0 Out Pause Frames : 0
===============================================================================
Configuring GNSS ports
Some 7750 SR FP5 CPMs are equipped with an integrated GNSS receiver and GNSS RF port for retrieval and recovery of GPS and Galileo signals.
Use the commands in the following context to configure integrated GNSS RF ports including antenna-cable delay, signal recovery, and elevation-mask angle.
configure port gnss