Interface Configuration Guide 7705 SAR Interfaces
Edition: 01 3HE 11011 AAAC TQZZA 261
• When one port is on a first- or second-generation Ethernet adapter card and the
other port is on a third-generation Ethernet adapter card, mix-and-match traffic
management occurs. The LAG SAP uses a generic QoS configuration where
scheduler-mode, agg-rate, and cir-rate are configured for the SAP, but only
those applicable parameters needed by the active adapter card are used to set
the QoS values of the active port. See LAG Support on Mixed-Generation
Hardware for details. See Table 2 for a list of adapter card generations.
• The primary port configuration settings are applied to both the primary and
secondary LAG ports. Thus in order to support unshaped SAPs when the
primary port is a Gen-3-based port and the secondary port is a Gen-2-based
port, configuring the unshaped-sap-cir on the Gen-3-based port is allowed,
even though it does not apply to the Gen-3-based port. This is because
unshaped-sap-cir is needed by the (secondary) Gen-2-based port when it
becomes the active port. The full command is
config>port>ethernet>access>egress>unshaped-sap-cir cir-rate.
• When a LAG contains a port on a first-generation Ethernet adapter card, the
scheduler mode can only be 4-priority.
Additional general rules for LAG configuration are as follows.
• Most port features (port commands) can only be configured on the primary
member port. The configuration, or any change to the configuration, is
automatically propagated to any remaining ports within the same LAG.
Operators cannot modify the configurations on non-primary ports.
• When adding the first port member to a LAG group, its port configuration
becomes the configuration of the LAG group.
• Once a LAG group has been created, new ports can be added to the LAG group
only if their port configurations match with the LAG group configurations
inherited from the group’s existing primary port. A newly added port may
become the primary port or a non-primary port, depending on the setting of the
LAG selection criteria, priorities, and so on.
• Not all configurations follow the conventions above. Some exceptions include
the commands loopback (internal or line), cfm-loopback, mac, lldp, dot1x,
efm-oam, and so on.
• At boot-up, port configuration is applied before LAG configuration is applied.
Therefore, configuration values are allowed or prohibited for both a standalone
port and a port attached to a LAG group; otherwise, a database restore or exec
command will fail. For example, if the scheduler mode profile command option
is supported on a Gen-2 port that is the primary member of a LAG, operators are
allowed to change scheduler-mode on other member links, including Gen-1
and Gen-3 ports. If the scheduler mode profile command option is blocked for
a standalone Gen-2 port, then after issuing an admin>save command followed
by a reboot command, the node will fail to reload the database file.
To Next Page
Loading...
