• Documentation Feedback Objectives This manual provides an overview of the Tellabs 8609 access switch and Tellabs 8611 access switch interface functions and instructions on how to configure them using Command-Line Interface (CLI) and ASCII textual commands with a router’s console or remote terminal (Telnet).
Interface Numbering Conventions To be able to follow more easily the feature descriptions and configuration examples given in this document, see also the Tellabs 8600 system interface numbering and related figures described in Tellabs 8600 Managed Edge System CLI Commands Manual.
1 Overview 1 Overview This document gives an overview of the data service interface features supported by the Tellabs 8609 access switch and Tellabs 8611 access switch. The emphasis is on the software configuration of the interfaces. The existing components, their features and installation instructions are presented in the documents mentioned below.
2.1.2 Fixed Interfaces The Tellabs 8609 access switch supports up to 12 Ethernet interfaces, which are fixed to the chassis of the NE. There are two virtual modules, M0 and M1, with each comprising of 4 Ethernet interfaces that support 100/1000BASE-X modes, in total there are 8 optical Gigabit Ethernet interfaces available.
Ethernet Layer Failure Reporting 2.1.3 Supported Line Modules The Tellabs 8609 access switch provides two line module slots, M3 and M4, for the LMs. Any combination of the supported LMs is allowed in the slots. The following are the LMs currently supported: •...
2.2.2 PLM Combination Rules The Tellabs 8611 access switch provides four PLM slots, numbered M0 through M3 for the LMs and three PLM slots, numbered M4 through M6, for the HMs. The NE architecture set some rules to the PLMs equipping as following: •...
3 Physical Line Modules 3 Physical Line Modules This section describes PLM types supported by the: • Tellabs 8609 access switch • Tellabs 8611 access switch Line Modules This section describes different media type of LMs supported by: • Tellabs 8609 access switch •...
Page 19
3 Physical Line Modules NE and LM Type: Tellabs 8609 Access Switch, Tellabs 8611 Access Switch and 8xchE1/chT1 TLP Type Unframed Framed Nx64k (for ATM and MLPPP N is fixed) Service MPLS PWE3 MPLS PWE3 Routing Switching Routing Switching —...
Page 20
The PPP and Multilink PPP (MLPPP) interface enables the NE to be connected to another Tellabs 8600 NE or third party equipment using a single logical link having capacity of several P12s/DS1 [RFC1990]. Within MLPPP the following features are supported: •...
The 8x10/100BASE-TX LM supports the following configuration options: Configuration Option Ethernet Physical Layer Configuration Ethernet Layer Failure Reporting High Speed Modules The Tellabs 8611 access switch provides support for High speed Modules (HM) covered in this section. 3.2.1 4x100/1000BASE-X HM Overview The 4-port (optical) Gigabit Ethernet HM supports 100/1000BASE-X interfaces.
• Synchronous Ethernet concept where the Ethernet egress can be synchronized to Timing Module. See Tellabs ® 8600 Managed Edge System Synchronization Configuration Guide for more details • Ethernet line and equipment loopbacks • IEEE802.1ag Ethernet OAM Fault Management • Loopback (ping) function •...
Page 24
3 Physical Line Modules The Tellabs 8600 system supports VLAN tagging on Ethernet interfaces. All interfaces can accept VLAN-tagged, priority-tagged and untagged frames. Double tagged VLAN frames 802.1q-in-q are also supported. The interfaces perform input filtering based on the VLAN identifiers. The Ethernet ports can be configured to optionally discard all untagged and priority-tagged frames.
MGMT port on each SCM of the Tellabs 8611 access switch. From configuration and functionality point of view, the MGMT port is as any other Ethernet port of the Tellabs 8600 system. In addition to the local management access, the MGMT port provides access to the network for the management communication traffic.
The f2 and f3 filters are only applied to TDM layer (layer L1) defects by the Tellabs 8600 NE. Failure filter f4 integrates fault cause failures (detected faults) by performing a persistency check on the fault before it declares the fault cause a failure [ETS 300 417-7-1].
5.1.2 Fault Suppression In the Tellabs 8600 system AIS, RDI and SSF faults are suppressed by default. This is based on the principles that in a homogenous Tellabs 8600 NE a network failure is reported only once by the NE which detects the primary reason of the failure.
The operator can invoke a remote loopback by generating a remote loopback command. In the Tellabs 8600 system it is possible to generate the commands only to the line direction of the DS1 interface. The remote loopback request does not contain any dedicated information about the line/equipment loop selection.
10 times to the facility data link. If the far-end is capable of detecting the codes, it performs the loop. The Tellabs 8600 system monitors all the activation/deactivation codes shown in the table above at the time in a particular DS1 interface without any configuration.
• Example d) in the figure below shows how a line loopback is activated remotely. The DS1 inter- faces in the Tellabs 8600 NEs are in unframed modes and therefore only inband commands can be sent and received. However, both unframed and framed inband commands are available.
Tellabs 8630 access switch or Tellabs 8660 edge switch where the line card slot number is part of the interface name (e.g. ge 5/1/0). Card slot is not applicable to Tellabs 8609 access switch , therefore the syntax applied to this NE should follow module#/Interface#.
The following step list contains basic configuration commands that are often used when configuring interfaces in the Tellabs 8600 system. The list is not comprehensive, and there are optional commands that are not necessarily required in order to get an interface working. For more information on how to configure an interface of a certain type, refer to the interface specific sections...
This section shows commands that can be used when looking for information on the status of an interface. See also Tellabs ® 8600 Managed Edge System Test and Measurement Configuration Guide for information on tools for testing connections. Tellabs 8600 Managed Edge System 76.8610-50149A...
Page 39
Description Use this command to check the hw-inventory NODE# show hw-inventory configuration of your Tellabs 8600 equipment. You can use this command to check that all components (IFC, IFM) of the equipment show up in the hw-inventory configuration as expected.
Page 40
For example, use the ether-logical parameter to clear the counters of the Ethernet interface only. Refer to Tellabs 8600 Managed Edge System ® CLI Commands Manual for information on the parameters available for all types of interfaces.
9 Interface Configuration Examples Ethernet Basic Configuration This section shows basic configurations of the Ethernet interface in the Tellabs 8600 system. Basic Configuration Commands for Ethernet Interfaces Command Description connectivity-type Define the connectivity type (routing or tunneling) of the interface.
2/2/0..7 fe 2/3/0..7 pdh 2/3/0..7 9.5.1 Starting Configuration The PDH interface is accessed in the same way as any other interface in the Tellabs 8600 NEs. Command Description Enter the Interface Configuration mode. If the NODE> enable specified interface is valid to be taken into use, the...
The HDLC PWE3 or port protocol HDLC creates an interface that can be attached to pseudowire only and it cannot terminate. The HDLC PWE3 can carry any kind of traffic that uses HDLC protocol, i.e.: PPP. The Tellabs 8600 system implementation of the HDLC PWE3 conforms to [RFC4618].
Page 50
3 lower priority frames. In the Tellabs 8600 NEs the default QoS mapping to DiffServ traffic classes is covered in Mapping Consideration. However in cases where the default QoS mapping needs to be modified (e.g.
For details of the supported commands and options to adjust PDH fault monitoring and reporting, please refer to Tellabs 8600 Managed Edge System CLI Commands Manual. ® The following samples of commands give an example of adjusting fault monitoring and reporting for P12s and DS1.
9 Interface Configuration Examples Management Port of SCM The MGMT port on SCM of Tellabs 8611 access switch automatically becomes protected when another SCM is added to the inventory of the network element and SCM becomes an equipment protected card. Therefore, the Tellabs 8611 access switch does not have separate commands for establishing or removing the MGMT protection group.
RX/TX interface pair. This mode is know as loop timing. Loop timing can be used e.g. when the last element in the edge of the network has an E1/T1 interface but does not have any other reason to use an accurate clock. Refer to Tellabs 8600 ®...
The system monitors the existence of the SFP modules. The Tellabs 8600 NEs generate an alarm (Missing connector module) if the SFP stick of an interface is not present (or it is broken).
Ethernet OAM The Ethernet OAM functionality supported in the Tellabs 8600 system is covered in Tellabs 8600 ® Managed Edge System Ethernet Configuration Guide. Port Protocols ATM Interface (Transmission Convergence) Layer Configuration An ATM interface provides the ATM transmission convergence layer functionality and de-couples the ATM cell processing from TDM frame processing.
Page 60
Tellabs 8600 Managed Edge System ATM and TDM ® Configuration Guide. IMA scalability is shown in the following table. Tellabs 8609 Access Switch and Tellabs 8611 Access Switch IMA Scalability P12s/DS1 Maximum number of IMA groups...
Page 61
PDH interface usage configuration connected connected Timeslot group usage configuration Port protocol The TDM pseudowire functionality is detailed described in Tellabs 8600 Managed Edge System ® ATM and TDM Configuration Guide. Nx64k CESoPSN TDM PWE3 Layer Configuration The framed PDH interface (P12s/DS1) can be configured to have several timeslot groups. Each group can be configured to TDM/CESoPSN mode to terminate CESoPSN PWE3 encapsulation...
Page 62
Layer Descriptions The TDM pseudowire functionality is detailed described in Tellabs ® 8600 Managed Edge System ATM and TDM Configuration Guide. PPP Layer Configuration A Point-to-Point Protocol (PPP) provides a method for transporting multi protocol datagrams by providing encapsulation for different network layer protocols over the same link. PPP is used for multiplexing different network layer protocols such as Internet Protocol (IP), Multiprotocol Label Switching (MPLS) by providing PPP encapsulation over the same link.
Page 63
When frames to be multiplexed are larger than the configured subframe length, the frames are transmitted without multiplexing and hence bandwidth efficiency is not be achieved. The Tellabs 8600 system supports: • Multiplexing/de-multiplexing of CS7 and EF traffic classes •...
Page 64
The receiving side accepts these fragments, reorders and reassembles the fragments into a complete frame using the sequence numbers. Tellabs 8600 Managed Edge System 76.8610-50149A ® Tellabs 8609 Access Switch FP1.0 Tellabs 8611 Access Switch FP1.1 Interface Configuration Guide...
Page 65
When interleaving is enabled in Tellabs 8600 system packets with CS7 and EF traffic classes are interleaved while the packets with other traffic classes are fragmented. Interleaving is also supported with PPPMux to achieve efficient bandwidth and latency improvement.
Page 66
MLPPP group. A frame can be sent further only when all fragments have been received, therefore the slowest path defines the overall delay. Tellabs 8600 Managed Edge System 76.8610-50149A ® Tellabs 8609 Access Switch FP1.0 Tellabs...
Page 67
• Statistical analysis of received frame, i.e. arrival time and sequence numbers The Tellabs 8600 system uses frame based method to measure the MLPPP differential delay. Explicit test frames are used as PPP Echo Request and Echo Reply [RFC1661] payload. A one-way differential delay of links is measured using the hardware based timestamps included in Echo-packets.
Page 68
When Address and Control Field Compression (ACFC) is enabled , the PPP header would exclude the address and control field. When Protocol Field Compression (PFC) is enabled, the leading zeroes in PID would be excluded. The Tellabs 8600 system by default disables ACFC, while PFC is enabled.
Page 69
Fig. 8 MC-MLPPP MP Header QoS Mapping Consideration The Tellabs 8600 system supports a maximum of 4 multi link transmit classes (suspension levels). Maximum up to 3 multi link classes can be enabled at the same time. Depending on the networking conditions 1..7 DiffServ traffic classes can be mapped to 1..3 multi link classes.
Page 70
The latency improvement with MC-MLPPP is more evident, when low priority frames are interrupted frequently by the high priority frames. Tellabs 8600 Managed Edge System 76.8610-50149A ® Tellabs 8609 Access Switch FP1.0 Tellabs...
Page 72
However, the processing delay (typically less than 1 ms) is also present and thus theoretical delays will not be achieved exactly. Configuration Options The available configuration options required for MC-MLPPP are presented below. Tellabs 8609 Access Switch and Tellabs 8611 Access Switch MC-MLPPP Configuration Range TX traffic classes 1–4...
Need help?
Do you have a question about the 8600 and is the answer not in the manual?
Questions and answers