Configuring physical ports with CLI
This section provides information to configure cards, MDAs, and ports.
Preprovisioning guidelines
7705 SAR Gen 2 platforms have a console port, either located on the CPM or integrated into the chassis, 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. For command syntax for LAG, see Configuring LAG.
Basic configuration
The most basic configuration must specify the following:
-
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 7705 SAR Gen 2.
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
#--------------------------------------------------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 7705 SAR Gen 2.
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
#----------------------------------------------
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//1/c1/1]
A:admin@node-2# info
admin-state enable
description "Ethernet access port"
ethernet {
mode access
encap-type dot1q
}classic CLI
A:node-2>config>port# info
----------------------------------------------
----------------------------------------------
description "Ethernet access port"
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 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
----------------------------------------------