The selection criteria must be set to best-port before standby signaling can be placed in power-off mode. Once the selection criteria is set to best-port , setting the standby-signaling parameter to power-off causes the transmitters on the standby ports to be powered down.
After a switchover caused by a failure on the active link, the transmitters on the standby link are powered on. The switch time for static LAG is typically longer than it is with LACP, due to the time it takes for the transmitters to come up and transmission to be established. When the fault is restored, static LAG causes a revertive switch to take place. The revertive switch is of shorter duration than the initial switchover since the system is able to prepare the other side for the switch and initiate the switchover once it is ready.
Since the transmitters on the standby link are off, it is not possible for the LAG to respond to a physical disconnect fault on the standby link. This means that it is possible to have a failure on the active link result in a switch to a failed standby link. All other Ethernet cards are second-generation Gen-2 adapter cards, except the 8-port Ethernet Adapter card, which is a first-generation Gen-1 card.
See Table 2 for a list of first-, second-, and third-generation Ethernet adapter cards, ports, and platforms. Not all of the generic configuration settings apply to all of the adapter cards; only the settings that apply to the active member port are used. For example, a Gen-3 adapter card does not support CIR rates for second-tier aggregate shapers because CIR is not needed due to the operational behavior of the 4-priority-hqos scheduler.
In addition, the scheduling mode configuration is not applied to the Gen-3 adapter card SAPs since these cards support only one scheduling mode 4-priority-hqos. However, a Gen-2 adapter card does support second-tier CIR rates due to the operational behavior of the priority scheduler.
Per-SAP shaper rates do not apply to Gen-1 cards. When the active link is on a Genbased port, only the PIR portion of the per-SAP aggregate rate is used to enforce shaper rates because CIR is not needed due to the operational behavior of the 4-priority-hqos scheduler. Similar commands exist for SAPs in other services as well as for egress traffic. In addition, the following items describe mix-and-match LAG configuration behavior that is, how the LAG SAP settings are applied or ignored depending on the active member port.
Thus, in order to support unshaped SAPs when the primary port is a Genbased port and the secondary port is a Genbased port, configuring the unshaped-sap-cir on the Genbased port is allowed, even though it does not apply to the Genbased port. This is because unshaped-sap-cir is needed by the secondary Genbased port when it becomes the active port.
The SAR supports per-flow-based hashing, which guarantees that packets within the same traffic flow are not reordered. Per-flow hashing uses information in a packet as an input to the hash function, ensuring that any given traffic flow maps to the same egress ECMP path.
Depending on the type of traffic that needs to be distributed into an ECMP path, different variables are used as input to the hashing algorithm that determines the next-hop selection.
Each label in the stack is then hashed separately with the result of the previous hash, up to a maximum of six labels. The net result is used to select which LDP FEC next hop to send the packet to using a threshold hashing operation of the net result with the number of next hops.
In the first hash round of ECMP, the algorithm parses down the label stack up to six labels , and once it hits the bottom, it checks the next nibble. If the nibble value is 4, the packet is assumed to be an IPv4 packet. The result of the label hash is then fed into another hash along with the source and destination address fields in the IP packet header.
If the nibble value is not 4, it will just use the label stack hash already calculated for the ECMP path selection. Unicast IP traffic routed by a router is hashed using the IP source address and destination address headers in the packet.
If the TEID is present, it is included in the hash algorithm inputs. APS provides protection against a port, signal, or adapter card failure. If the signal on the active working port degrades or fails, the network proceeds through a predefined sequence of steps to transfer or switch over traffic processing to the protection port.
This switchover is done very quickly to minimize lost traffic. Traffic is streamed from the protection port until the working port fault is cleared, at which time the traffic may optionally be reverted to the working port.
In an SC-APS group, both the working and protection circuit must be configured on the same node, whereas an MC-APS group can be on two separate nodes, providing protection from node failure in addition to protection from link and hardware failure.
The working and protection circuits of an SC-APS group must be on two ports on different adapter cards. The working and protection circuit must have compatible configurations, such as the same speed, framing, and port type. The circuits in APS group in both the working and protection nodes must also have the same group ID, but they can have different port descriptions. In order for MC-APS to function correctly, pseudowire redundancy must be configured on both the working and protection circuits.
However, to prevent possible switchover performance issues, it is recommended to avoid mixing different platform types in the same MC-APS group. The SAR does not enforce configuration consistency between the working circuit and the protection circuit. Additionally, no service or network-specific configuration data is signaled or synchronized between the two routers.
A heartbeat protocol can also be used to add robustness. The signaling path verifies that one router is configured as the working circuit and the other is configured as the protection circuit. In case of a mismatch, an incompatible neighbor trap is generated.
Changes in working circuit status are sent across the MC-APS signaling link from the working router to keep the protection router synchronized. External requests such as lockout, force, and manual switches are allowed only on the APS group with the protection circuit. ICB improves switch times, provides additional protection in case of network failures, and reduces packet loss when an active endpoint is switched from a failed MC-APS node to the protection node. If the active link on the access side fails, MC-APS switchover triggers and subsequently triggers pseudowire redundancy switchover.
The switch priority of a request is assigned by bits 1 through 4 of the K1 byte, as shown in Table In bidirectional mode, the highest-priority local request is compared to the remote request received from the far-end node using an APS command , and whichever request has the greater priority is selected.
The channels requesting the switch action are assigned by bits 5 through 8. Only channel number codes 0 and 1 are supported on the SAR. If channel 0 is selected, the condition bits show the received protection channel status.
If channel 1 is selected, the condition bits shows the received working channel status. The K2 byte is used to indicate bridging actions performed at the line termination equipment LTE , the provisioned architecture, and mode of operation, as shown in Table Table 15 outlines the steps that the bidirectional APS process will go through during a typical automatic switching event.
The example is read row by row, from left to right, to provide the complete process of the bidirectional switching event. In revertive mode, the activity is switched back to the working port after the working line has recovered from a failure or the manual switch is cleared. In non-revertive mode, a switch to the protection line is maintained even after the working line has recovered from a failure or the manual switch is cleared.
To prevent frequent automatic switches that result from intermittent failures, a revert-time is defined for revertive switching. The revert-time is configurable from 0 to 60 min in increments of 1 min; the default value is 5 min. In some scenarios, performance issues can occur if the revert-time is set to 0; therefore, it is recommended that the revert-time always be set to a value of 1 or higher. Any change in the revert-time value takes effect upon the next initiation of the wait-to-restore WTR timer.
The change does not modify the length of a WTR timer that has already been started. The WTR timer of a non-revertive switch can be assumed to be infinite.
If both working and protection lines fail, the line that has less-severe errors will be active. If there is signal degradation on both ports, the active port that failed last will stay active. If there is signal failure on both ports, the working port will always be active because signal failure on the protection line is a higher priority than on the working line.
Since the command has the highest priority, a failed working line using the protection line is switched back to itself even if it is in a fault condition.
No switches to the protection line are allowed when the line is locked out. If the active line is already on the protection line, no action takes place. If the active line is already on the working line, no action takes place. When the forced switch of working to protection command is in effect, it may be overridden either by a lockout of protection command or by detecting a signal fault on the protection line.
The Exercise command exercises the protection line by sending an exercise request over the protection line to the far end and expecting a reverse request response back. The switch is not completed during the exercise routine. This failure indicates that the received K1 byte is either invalid or inconsistent. An invalid code defect occurs if the same K1 value is received for three consecutive frames and is either an unused code or irrelevant for the specific switching operation.
An inconsistent code defect occurs when no 3 consecutive received K1 bytes of the last 12 frames are the same. If the failure persists for 2. When this failure is declared, the protection line is treated as if it were in the SF state.
The received signal is then selected from the working line. When the failure is absent for 10 s, the alarm is cleared and the SF state of the protection line is removed.
This failure indicates that there is a channel mismatch between the transmitted K1 bytes and the received K2 bytes. A defect is declared when the received K2 channel number differs from the transmitted K1 channel number for more than 50 ms after 3 identical K1 bytes are sent. The monitoring for this condition is continuous, not just when the transmitted value of K1 changes.
This failure can occur for two reasons. The second reason is that the received K2 byte indicates that unidirectional mode is being used by the far end while the near end is using bidirectional mode. This defect is detected within ms of receiving a K2 byte that indicates either of these conditions.
When this failure is declared, if the defect indicates that the far end is configured for unidirectional mode, then the OC-N port reverts from its current bidirectional mode to unidirectional mode. However, the port continues to monitor the received K2 byte, and if the K2 byte indicates that the far end has switched to bidirectional mode, the OC-N port then reverts to bidirectional mode as well.
The monitoring stops if the user explicitly reconfigures the local port to operate in unidirectional mode. This failure occurs when a K1 byte is received in three consecutive frames that indicates a signal fail SF at the far end of the protection line. This failure forces the received signal to be selected from the working line. This alarm can only be raised by the active port operating in bidirectional mode. When the failure is absent for 10 s, the alarm is cleared.
When a CSM or adapter card is installed in a preprovisioned slot, the system tests for discrepancies between the preprovisioned card and card type configurations and the types actually installed.
Error messages are displayed if there are inconsistencies, and the card will not initialize. When the proper preprovisioned cards are installed into the appropriate chassis slot, then alarm, status, and performance details will be displayed on the CLI. The MPR-e is the zero-footprint outdoor microwave solution offered by Alcatel-Lucent that allows customers to migrate from TDM microwave to pure packet microwave. The following MPR-e radio variants are supported:.
The radio can be configured in standalone mode to provide a basic microwave connection as described in Standalone Mode or in Single Network Element Single NE mode to provide the advanced networking capabilities described in Single NE Mode. The default configuration is Single NE mode.
When connected to an MPR-e radio, these ports, with microwave link configured, operate as Gigabit Ethernet ports and provide the same features as the other ports ports 5 through 8 , except for the following:. If a microwave link is not configured on ports 1 through 4, they provide all of the same features as the other Gigabit Ethernet ports ports 5 through 8. A microwave link from ports 1 through 4 on a Packet Microwave Adapter card to an MPR-e radio that is configured in standalone mode provides a basic microwave connection to the MPR-e radio.
A microwave link from ports 1 through 4 on a Packet Microwave Adapter card to an MPR-e radio that is configured in Single NE mode provides the following networking capabilities to the radio over the microwave link:. The following features are part of Single NE management:. The individual management and IP address of the MPR-e radios are no longer required for network management.
An MPR-e radio generates alarms for fault conditions pertaining to the MPR-e hardware and to the microwave link over which it is connected. There are two TiMOS. MWA annotation in the file name. This means that the MPR-e radio does not need to be reconfigured after a radio hardware replacement. A separate database file is required for each managed MPR-e radio. During an MPR-e radio reset, the microwave link is brought down and an upper layer applications action is triggered, such as message rerouting and clock source switching by the System Synchronization Unit SSU.
The following fault types are detected by FFD:. Additionally, hitless errorless switching provides zero packet loss if a switchover occurs from a main to a spare MPR-e radio. An MPR-e radio that is connected to an odd-numbered port on the Packet Microwave Adapter card must be configured as the main radio.
Upon receiving the baseband traffic, both radios modulate it and up-convert it to signals. RPS is a hitless radio function that provides space diversity protection for the microwave channel. On the receive side, each MPR-e radio monitors the same radio frequency channel, with the main MPR-e radio being the active receiver by default.
Only one microwave frequency channel is active and only the main MPR-e radio is transmitting data to the remote ends; the spare MPR-e radio is acting as a standby. Revertive switching occurs when the MPR-e radio operation switches from the spare radio back to the main radio after a fault condition is cleared. Depending on the type of Gigabit Ethernet microwave link used to connect the Packet Microwave Adapter card and an MPR-e radio, different frequency synchronization mechanisms can be used.
SSM is used as the mechanism to detect a microwave link failure, including loss of frame and MPR-e radio hardware failure. The following steps describe how to perform a remote migration from a standalone mode to a Single NE mode. Your system must be at MPT Release 4. Do not perform the migration if you are running MPT Release 5. The database filename must be first defined in Step 6 before the Single NE mode can be enabled in Step 7.
Once the port is configured for bonded mode, any pairs not included in the bonded groups cannot be used to carry traffic. The 8-port xDSL module supports only one bonding group. ATM bonding adds sequence information to ATM cells, allowing resequencing by adding delay variation to account for speed differences across multiple physical links in one bonding group.
In ATM channel-bonding schemes, the end-user packets are split into byte cells. PTM bonding uses Ethernet packet-based transmission. PTM bonding adds sequence information to transmitted frames or frame fragments, allowing resequencing by adding delay variation to account for speed and PDU size differences across multiple physical links in one bonding group. In PTM channel-bonding schemes, the end-user packets are split into small fragments of up to bytes. At the receiving end, the fragments are realigned to recover from differential delays in the transmission path, then reassembled into packets.
In order to realign correctly, each fragment is prefixed with a header containing a sequence identifier SID , a start of packet SOP indicator, and an end of packet EOP indicator. The receiver side uses the SID to rearrange the incoming cells in the correct order, while the SOP and EOP indications are used to reassemble the stream of cells into complete data packets.
If transmitted Ethernet packets are smaller than the PTM fragment size, they are transmitted inside a single fragment. Pairs within a bonded group must start with pair 1 and are then sequentially added into each module.
For LT-level bonding, the interworking function on the LT board allows non-contiguous ports on the same LT to be bonded. LT-level bonding is used to configure 8-pair bonding on the ISAM, which is also handled by dedicated hardware that incorporates both bonding and xDSL interworking functions. Within a bonding group, the line used to identify the whole group is referred to as the primary link. The other lines in the bonding group are referred to as secondary or slave links.
The supported bit rate over the bonding group is the sum of the actual net bit rates on all lines in the group. All DSL module ports are considered the functional equivalent of an Ethernet port and support many of the same features and configuration commands. Data from the central network processor of the SAR-M transmits and receives Ethernet packets to and from the module slot.
DSL modules automatically detect any existing configuration and will attempt to bring pairs into service. For PTM bonding, the underlying transport mechanism is Ethernet. The event data can be directed to the default log file or to a specific user-configured log file. The SAR supports custom alarms on Ethernet ports without the need to deploy a dry-contact alarm aggregator. Custom alarms can be created and assigned to any RJ port; the port must be configured for Base-Tx operation with autonegotiation disabled.
One alarm input can be configured for each port with the following:. Alarm inputs must be associated with an alarm in order for them to be triggered. Alarm inputs consist of an Ethernet LOS event caused by breaking contact loops between pins 1 and 3 or 2 and 6 on the Ethernet port. Breaking either loop will trigger the port alarm, and reconnecting the loops will clear the alarm. Only EAPOL frames can be exchanged between the aggregation device called the authenticator; for example, the SAR and the customer device called the supplicant until authentication is successfully completed.
The SAR enables the port after successful authentication. An authentication server would negotiate with the Ethernet device through the SAR whose role is authenticator. For example, a technician using a laptop to gain access to his or her network at a cell site would have his or her laptop subject to the In every case, the Ethernet device connected to the SAR must negotiate for network access.
The IEEE The authentication exchange is carried out between the supplicant and the authentication server; the authenticator acts only as a bridge. Figure 18 shows an example of the messages transmitted during an authenticator-initiated One Time Password OTP authentication process. OTP is one of many authentication mechanisms that are available for use between the supplicant and the authentication server. These authentication mechanisms protocols are transparent to the SAR.
The authenticator notifies the supplicant with an EAP-Success message and puts the port in the authorized state. If the supplicant sends and EAP-logoff message, the authenticator puts the supplicant in an unauthorized state. After waiting a number of seconds defined by the quiet-period timer, the authenticator continues searching for supplicants to authenticate.
The SAR supports port-based network access control for Ethernet ports only. Each Ethernet port can be configured to operate in one of three different modes, controlled by the port-control command:.
The Figure 19 shows an example of the timers. The authenticator can also be configured to periodically trigger the authentication process automatically. This is controlled by the enable reauthentication and reauthentication period parameters. Re-auth-period indicates the time in seconds since the last time that the authorization state was confirmed before a new authentication process is started.
The range of re-auth-period is 1 to s the default is s. The port stays in an authorized state during the reauthentication process. It is not possible to dynamically select a service such as a VPLS service depending on the In other words, IEEE LAN emulation and logical topology is applicable to customer bridge scenarios enterprise or carrier of carrier connected to a provider network offering a transparent LAN emulation service to their customers.
LAN emulation helps customers detect intermediate provider misconnections by offering a view of the customer topology where the provider service is represented as a LAN interconnecting customer bridges. Network operators must be able to discover the topology information in order to detect and address network problems and inconsistencies in the configuration. Standards-based tools can address complex network scenarios where multiple devices from different vendors are interconnected using Ethernet interfaces.
Each session can have up to five peers and each peer can store up to three management addresses. The SAR can have a maximum of peers configured. LLDP allows stations attached to an IEEE LAN to advertise to other stations attached to the same LAN, the major capabilities provided by the system incorporating that station, the management address or addresses of the entity or entities that manage these capabilities, and the identification of the station's point of attachment to the LAN required by the management entity or entities.
The information distributed via this protocol is stored on the receiving device in a standard MIB, so that the information can be accessed by a Network Management System NMS.
LLDP does not contain a mechanism for soliciting specific information from other LLDP agents, nor does it provide a specific means of confirming the receipt of information. Each element includes type, length, and value fields known as TLVs. Both the chassis ID and port ID values can be defined in a number of ways.
Once selected, however, the chassis ID and port ID value combination remains the same as long as the particular port remains operable. The associated information is automatically discarded by the receiving LLDP agent if the sender fails to update it before this time. A TTL value of zero can be used, for example, to signal that the sending port has initiated a port shutdown procedure. SCADA systems are used in many strategic industry networks, such as utility and transportation, to monitor and maintain the networks from remote monitoring locations.
The bridge allows a single data message stream to be broadcast from a master to multiple slaves and allows a single slave to communicate back to the master. SCADA systems may use redundant masters, where both masters listen to all traffic that is being transmitted from the slaves but only the active master broadcasts data to the slaves. Each bridge supports 32 branches. Two branches branch 1 and branch 2 are dedicated connections to the SCADA masters; the other 30 branches connect to the slaves.
Larger bridges can be built by cascading individual bridges within a single Integrated Services card and using the master output from one bridge as the master input to another bridge. The connection between the bridges is made using an RS link. A Cpipe SAP is configured for each master and slave branch in order to transmit data to the bridge. A condition may occur where a single slave continues to send data to the master after the normal response period has expired.
This condition locks up the bridge so that no other slave can transmit data back to the master. Squelching blocks the errant slave so that other slaves can continue to use the bridge. The squelch reset command is used to put the bridge back into a normal state. Topics in this chapter include: Configuration Overview. Configuring Adapter Cards and Modules.
Maximum Number of Adapter Cards in a Chassis. Channelized Adapter Card Support. Provisioning Chassis Slots for Adapter Cards A chassis slot and card type must be specified and provisioned before an adapter card can be provisioned.
Maximum Number of Adapter Cards in a Chassis Note: Unless otherwise specified, references to adapter cards with multiple versions include all versions of the cards. When installed in MDA slots 3 through 6, the aggregate fabric rate is 2. The total number of channel groups that can be configured per card and per node is bound by release-specific system limits.
For more information, please contact your Alcatel-Lucent technical support representative. Configuring Ports A port can be configured after the IOM is activated the card slot and card type are designated and the adapter card slot is preprovisioned with an allowed adapter card type.
The SAR supports the port types listed below: Ethernet. Access, Network, and Hybrid Ports. Ethernet Ethernet ports are supported on the following cards, modules, and platforms: 6-port Ethernet 10Gbps Adapter Card. Packet Microwave Adapter Card. FXO supports: profile1 loop start — A-Law companding. A csm-1g csm-1g up up Active. B csm-1g up down Standby. A csmvg csmvg up up Active. B csmvg up down Standby. A csmg csmg up up Active. B csmg up down Standby. A csm Access, Network, and Hybrid Ports All ports must be set to access customer-facing , network, or hybrid mode.
This support is enabled using the mda-mode command see the mda-mode command in the Card, Adapter Card, and Port Command Reference section : access ports — configured for customer-facing traffic on which services are configured.
If a Service Access Point SAP is to be configured on the port or channel, the port or channel must be configured as an access port or channel. On the port Serial Data Interface card, the encapsulation type can be cem, ipcp, frame-relay, hdlc, or cisco-hdlc.
RS ports and X. RS ports operating at subrate speeds support only cem encapsulation. The Packet Microwave Adapter card supports qinq only when the card is not in mw-link mode. The 6-port Ethernet 10Gbps Adapter card supports qinq only when the card is in access mode.
The encapsulation type for DS3 channelized ports can be cem or frame-relay. Hybrid ports can support access and network modes simultaneously over different VLANs. The SAR supports both copper and fiber uplinks. Note: The unshaped-if-cir command does not apply to Gen-3 adapter cards, such as the 6-port Ethernet 10Gbps Adapter card, since it uses the 4-priority-hqos scheduler.
Hybrid Ports Hybrid ports are supported on Ethernet ports, where they provide the capabilities and features of access and network mode ports on a per-VLAN basis. The following hardware supports hybrid ports: 6-port Ethernet 10Gbps Adapter card. Figure 1: Hybrid Port Application. Network Synchronization on Ports and Circuits. Flow Control on Ethernet Ports. Ethernet Port Down-When-Looped. Ethernet Ring Adapter Card and Module.
Automatic Protection Switching. Deploying Preprovisioned Components. Custom Alarms on Ethernet Ports. The system indicates the following capabilities. The system offering the option is capable of combining multiple physical links into one logical link. The system is capable of receiving upper layer protocol data units PDUs that are fragmented using the MP header and then reassembling the fragments back into the original PDU for processing.
The system is capable of receiving PDUs of size N octets, where N is specified as part of the option, even if N is larger than the maximum receive unit MRU for a single physical link. Sequence Number Sequence numbers can be either 12 or 24 bits long. Information Field The Information field is zero or more octets. Padding On transmission, the Information field of the ending fragment may be padded with an arbitrary number of octets up to the MRRU. MP is somewhat different from PPP, and therefore the following options are set for MP and are not negotiated: no async control character map.
Address field—supports unicast 0x0F and broadcast 0x8F addresses. FCS field—can be 16 or 32 bits. The default is 16 bits for ports with a speed equal to or lower than OC3, and 32 bits for all other ports.
Ethernet OAM Overview EFM loopbacks are always line loopbacks line Rx to line Tx. Line loopbacks are not supported on DSL ports. When a port is in loopback, all frames except EFM frames are discarded. If all signaling and routing protocols are static static routes, LSPs, and service labels , the frames are discarded but services stay up. Line and Internal Ethernet Loopbacks A line loopback loops frames received on the corresponding port back towards the transmit direction.
For these ports, cfm-loopback is configured, optionally, using dot1p and match-vlan to create a list of up to 16 VLANs. The null VLAN is always applied. Based on the assigned ring-type network queue policy, dot1p-to-queue mapping is handled using the same mapping rule that applies to all other user frames. The desired QoS treatment is selected by enabling the CFM loopback and specifying high-priority , low-priority, or dot1p.
Ethernet Port Down-When-Looped Newly provisioned circuits are often put into loopback with a physical loopback cable for testing and to ensure the ports meet the SLA. The ports that will be designated as network ports intended to carry service traffic must be identified. IP Fragmentation IP fragmentation is used to fragment a packet that is larger than the MTU of the egress interface, so that the packet can be transported over that interface.
As a source of self-generated traffic, the SAR can perform packet fragmentation. If the arriving packet is bytes, then forward the packet. If the arriving packet is bytes, then forward the packet, which will be fragmented by the egress adapter card.
If the arriving packet is fragmented and the fragments are bytes, then forward the packet. If the arriving packet is bytes, then send an ICMP error message because the egress adapter card has a maximum port MTU of bytes.
If the arriving packet is fragmented and the fragment size is bytes, then there is an ICMP error. Multicast Support for Jumbo Frames Jumbo frames are supported in a multicast configuration as long as all adapter cards in the multicast group support jumbo frames. Notes : The maximum MTU value is supported only on cards that have buffer chaining enabled; therefore, it is not supported on the SAR-F and the 8-port Ethernet Adapter card, version 1.
MWA ports do not support QinQ. Access Ingress Fabric Shaping. Each link in a LAG is assigned to a subgroup. If both subgroups satisfy the selection criteria, the subgroup currently active remains active. Initially, the subgroup containing the highest priority lowest value eligible link is selected as active.
An eligible member refers to a link which can potentially become active. This means it is operationally up, and if the slave-to-partner flag is set, the remote system did not disable its use by signaling standby. The selection algorithm works in a revertive mode for details, refer to the IEEE This means that every time the configuration or status of a subgroup changes, the selection algorithm reruns. Access Ingress Fabric Shaping In order to avoid traffic congestion and ease the effects of possible bursts, a fabric shaper is implemented on each adapter card.
Note: Even though the multipoint shaper is used to set the fabric shaping rate for traffic switched to a LAG SAP, it is the per-destination unicast counters that are incremented to show the fabric statistics rather than the multipoint counter.
Note: Since the transmitters on the standby link are off, it is not possible for the LAG to respond to a physical disconnect fault on the standby link. The agg-rate is a PIR rate. Gen-3 Ethernet adapter cards use an implicit default scheduler mode called 4-priority-hqos, which is not user-configurable and is the only scheduler mode available on the card.
On a Gen-2 adapter card, the aggregate rate only applies when the port is in priority scheduler mode. This behavior implies the following points:. The scheduler mode can be set to priority or 4-priority. When servicing packets, the Genbased datapath uses the configured scheduler mode priority or 4-priority , while the Genbased datapath uses 4-priority-hqos scheduling.
When the traffic is transported over a Genbased port that is, the active link is on a Genbased adapter card , the aggregate rate agg-rate is used to enforce a maximum shaper rate while the aggregate rate CIR cir-rate is ignored. The aggregate rate enforces the per-SAP bandwidth limit and the CIR is used to identify in-profile and out-of-profile packets for aggregate scheduling purposes. Scheduler-mode can be set to 4-priority or priority, regardless of the LAG member port combination, except when one member is a port on a Gen-1 adapter card.
In this case, only 4-priority scheduling is available. Agg-rate and cir-rate can be set whether scheduler-mode is set to 4-priority or priority. Gen-3 cards always use 4-priority-hqos scheduler mode and Gen-1 cards always use 4-priority scheduler mode.
The Genbased or Genbased adapter card is configured with 4-priority scheduling, while agg-rate and cir-rate are not applied, and H-QoS is not enabled.
The Genbased adapter card is configured with agg-rate , while scheduler-mode and cir-rate are ignored. The Genbased adapter card is configured with priority scheduling mode, agg-rate and cir-rate.
This means that H-QoS is enabled. If scheduler-mode is priority mode on the LAG SAP, the combination of a Genbased port and a Genbased or Genbased port is blocked because Gen-1 adapter cards do not support priority mode. The only valid option for this combination of ports is 4-priority scheduling mode. Optional Layer 4 Load Balancing. Even if all flows are distributed equally among the available number of next hops, bandwidth on each link is correlated with the bandwidth of individual flows.
Part of the input to the hashing algorithm is based on the flow itself that is, source, IP, destination IP, label, and so on. Therefore, increasing variety in the input that is, in the flows drastically increases the chances of better distribution among all available next hops. Increasing variety also implies increasing the number of flows. Unidirectional and bidirectional modes are supported: unidirectional APS Uni-1Plus1 — in unidirectional mode, only the port in the failed direction switches to the protection port.
Deploying Preprovisioned Components When a CSM or adapter card is installed in a preprovisioned slot, the system tests for discrepancies between the preprovisioned card and card type configurations and the types actually installed. Standalone Mode A microwave link from ports 1 through 4 on a Packet Microwave Adapter card to an MPR-e radio that is configured in standalone mode provides a basic microwave connection to the MPR-e radio. The following fault types are detected by FFD: a radio signal failure.
Note: FFD does not cause the SSU to disqualify the microwave link as a clock source if a fault condition is detected; SSM must be enabled in order to provide this function. The microwave link hold time hold-up time and hold-down time must be configured in order to suppress link flapping.
The hold-time range is between 0 and s. Note: An MPR-e radio that is connected to an odd-numbered port on the Packet Microwave Adapter card must be configured as the main radio. A forced switch operation overrides any automatic or manual switch operation that is in place. An automatic switch operation overrides any manual switch operation that is in place.
Frequency Synchronization Depending on the type of Gigabit Ethernet microwave link used to connect the Packet Microwave Adapter card and an MPR-e radio, different frequency synchronization mechanisms can be used. This must be done within 60 s of resetting the radio if the microwave link is the only network link for management access to the SAR-8 or SAR Layer 3 Protocol Support and Service Provisioning. Pairs Within a Bonded Group Pairs within a bonded group must start with pair 1 and are then sequentially added into each module.
Configuration All DSL module ports are considered the functional equivalent of an Ethernet port and support many of the same features and configuration commands. One alarm input can be configured for each port with the following: name. This section describes the following: Figure Note: OTP is one of many authentication mechanisms that are available for use between the supplicant and the authentication server.
Figure Authentication Scenario. Each Ethernet port can be configured to operate in one of three different modes, controlled by the port-control command: auto — enables The port starts in the unauthorized state, allowing only EAPOL frames to be sent and received through the port. Both the authenticator and the host supplicant can initiate an authentication process as described earlier. The port will remain in the unauthorized state until the first supplicant is authenticated successfully.
After this, traffic is allowed on the port for all connected hosts. The port transmits and receives normal traffic without requiring This is the default setting. The authenticator cannot provide authentication services to the host through the interface. The default value is 30 s. The range is 1 to s. If the timer expires, the The timer is started after logoff, after sending an EAP-Failure message, or after expiry of the supplicant timeout timer. The default value is 2. The range is 1 to Very Good.
Get it tomorrow. Get it next 2 business days. Controller Card. PCI Express to Card. PCI Express to M. PCI to Card. Riser Card. Serial Header Adapter. PCI Express.
Lucky Zone. Famous Microgreens. XQ Tech and Data. Ports n Wire Computing. Airlink Tech. Electronic new century. ADP Tech. Premium Wholesale. Direct from Manufacturer. Less than 1 Year. More than 5 years. Free Shipping. Top Sellers. Price Match Guarantee. Discount Item. Volume Savings. Clearance Item. United States. Hong Kong.
0コメント