Alcatel-Lucent 7750 Configuration Manual page 38

Port Types
•
Page 38
continue to be done within the port using the same CLI hierarchy as in existing
implementation. The difference is that a port configured in mode hybrid allows both
ingress and egress contexts to be configured concurrently.
An Ethernet port configured in hybrid mode can have two values of encapsulation
type: dot1q and QinQ. The NULL value is not supported since a single SAP is
allowed, and can be achieved by configuring the port in the access mode, or a single
network IP interface is allowed, which can be achieved by configuring the port in
network mode. Hybrid mode can be enabled on a LAG port when the port is part of a
single chassis LAG configuration. When the port is part of a multi-chassis LAG
configuration, it can only be configured to access mode since MC-LAG is not
supported on a network port and consequently is not supported on a hybrid port. The
same restriction applies to a port that is part of an MC-Ring configuration.
For a hybrid port, the amount of the allocated port buffers in each of ingress and
egress is split equally between network and access contexts using the following
config>port>hybrid-buffer-allocation>ing-weight access access-weight [0..100]
network network-weight [0..100] and config>port>hybrid-buffer-allocation>egr-
weight access access-weight [0..100] network network-weight [0..100] commands.
Adapting the terminology in buffer-pools, the port's access active bandwidth and
network active bandwidth in each ingress and egress are derived as follows (egress
formulas shown only):
−
total-hybrid-port-egress-weights = access-weight + network-weight
−
hybrid-port-access-egress-factor = access-weight / total-hybrid-port-egress-
weights
−
hybrid-port-network-egress-factor = network-weight / total-hybrid-port-egress-
weights
−
port-access-active-egress-bandwidth = port-active-egress-bandwidth x
−
hybrid-port-access-egress-factor
−
port-network-active-egress-bandwidth = port-active-egress-bandwidth x
−
hybrid-port-network-egress-factor
When a named pool policy is applied to the hybrid port's MDA or to the hybrid port,
the port's fair share of total buffers available to the MDA is split into three parts:
default pools, named pools local to the port, and named pools on the ports MDA. This
allocation can be altered by entering the corresponding values in the port-allocation-
weights parameter.
SONET-SDH and TDM — Supported SONET-SDH and TDM port types include:
→ n*DS-0 inside DS-1/E-1
→ DS-1/E-1DS-3/E-3
→ OC3/STM-1
→ OC12/STM-4
→ OC48/STM-16
→ OC192/STM-64 SONET/SDH
7750 SR Interface Configuration Guide