This section briefly describes the major networking capabilities supported for Release 7.2 of Alcatel-Lucent 1850 TSS-5.
Alcatel-Lucent 1850 TSS-5 supports unprotected and protected OC-3, OC-12 and OC-48 linear optical extensions. Single-homed and dual-homed ring extensions are supported. UPSR switching can be used at the STS-1, STS-3c and VT1.5 level with the VLNC50/52/55 circuit pack. UPSR switching can also be used at the STS-12c level with the VLNC55 circuit pack. For additional information see Optical topologies.
Alcatel-Lucent 1850 TSS-5 interfaces can be equipment protected, network (SONET) protected, or unprotected. In order to have network protection the MAIN packs must be equipment protected. Equipment protection is accomplished by virtue of circuit pack redundancy in MAIN1 and MAIN2 slots. This redundancy allows for traffic restoration and circuit pack replacement without loss of TDM/FE service. SONET protection is accomplished via UPSR and 1+1 capabilities.
When the Slot Protection State is UNPROT (protection-not-allowed), a VLNC50/52/55 circuit pack is supported in the Main 1 slot only. If a VLNC50/52/55 circuit pack is inserted in the Main 2 slot, the system reports an unexpected CP type alarm. Protection is between the two optical lines on the VLNC50/52/55 circuit pack in Main slot 1 (that is, main-1-1 and main-1-2). For unprotected 0x1 applications the values of the port Signal Type parameters are independent. For protected UPSR applications the values of the port Application and Signal Type parameters for both optical lines on the circuit pack are the same value.
When the Slot Protection State is PROT (equipment-protection-allowed), VLNC50/52/55 circuit packs are supported in the Main 1 and Main 2 slots. The optical lines support unprotected 0x1 applications and protected 1+1/UPSR applications. Protection is between the equivalent optical lines on the circuit packs (for example, main-1-1 and main-2-1). For unprotected 0x1 applications the values of the port Signal Type parameters are independent. For protected 1+1/UPSR/SNCP applications the values of the port Application and Signal Type parameters for both optical lines are the same value. If the Main 2 slot is unequipped, the VLNC50/52/55 circuit pack in Main slot 1 operates unprotected.
The VLNC50/52/55 circuit pack supports OC-3 and OC-12 interfaces.
The VLNC55 circuit pack also supports OC-48 interfaces.
The VLNC64 circuit pack supports OC-3 interfaces.
Alcatel-Lucent 1850 TSS-5 supports DS1/E1 and DS3/E3 interfaces.
The VLNC50 circuit pack supports 8 DS1/E1 ports and 3 DS3/E3 interfaces.
The VLNC52/55 circuit pack supports 28 DS1/21 E1 ports and 3 DS3/E3 interfaces.
The VLNC60 circuit pack supports 8 DS1/E1 interfaces.
The VLNC61 circuit pack supports 16 DS1/E1 interfaces.
The VLNC62 circuit pack supports 8 DS1/E1 interfaces.
Note:
On the VLNC50/52/55, one of the DS3 interfaces (port b-3) may be used for TMUX (channelized with DS1s).
Alcatel-Lucent 1850 TSS-5 supports unprotected STM-1, STM-4, and STM-16 linear optical extensions. SNCP switching can be used at the VT1.5, VC-12, VC-3 (low-order), VC-4, VC-4-4C levels with the VLNC50/52/55 circuit pack.
Alcatel-Lucent 1850 TSS-5 interfaces can be equipment protected, network (SDH) protected, or unprotected. In order to have network protection the MAIN packs must be equipment protected. Equipment protection is accomplished by virtue of circuit pack redundancy in MAIN1 and MAIN2 slots. This redundancy allows for traffic restoration and circuit pack replacement without loss of SDH/FE service. SONET protection is accomplished via SNCP and 1+1 capabilities.
When the Slot Protection State is UNPROT (protection-not-allowed), a VLNC50/52/55 circuit pack is supported in the Main 1 slot only. If a VLNC50/52/55 circuit pack is inserted in the Main 2 slot, the system reports an unexpected CP type alarm. Protection is between the two optical lines on the VLNC50/52/55 circuit pack in Main slot 1 (that is, main-1-1 and main-1-2). For unprotected 0x1 applications the values of the port Signal Type parameters are independent. For protected SNCP applications the values of the port Application and Signal Type parameters for both optical lines on the circuit pack are the same value.
When the Slot Protection State is PROT (equipment-protection-allowed), VLNC50/52/55 circuit packs are supported in the Main 1 and Main 2 slots. The optical lines support unprotected 0x1 applications and protected 1+1/SNCP applications. Protection is between the equivalent optical lines on the circuit packs (for example, main-1-1 and main-2-1). For unprotected 0x1 applications the values of the port Signal Type parameters are independent. For protected 1+1/SNCP applications the values of the port Application and Signal Type parameters for both optical lines are the same value. If the Main 2 slot is unequipped, the VLNC50/52/55 circuit pack in Main slot 1 operates unprotected.
The VLNC50/52/55 circuit pack supports STM-1 and STM-4 interfaces.
The VLNC55 circuit pack also supports STM-16 interfaces.
The VLNC64 circuit pack supports STM-1 interfaces.
The Link Access Protocol on the D-channel (LAPD)/Unacknowledged Information Transfer Service (UITS) mode is supported on the VLNC50/52/55 to allow DCC interworking with SDH products.
The VLNC50/52/55 circuit pack supports full VT1.5 granularity on OC-3/OC-12/OC-48 interfaces and full VC-12 granularity on STM-1/STM-4/STM-16 interfaces. The VLNC50/52/55 circuit pack supports 63 VT1.5/VC-12 cross-connections to the GbE Ethernet port. The VLNC50 supports VT1.5 cross-connections to 8 DS1 ports or VC-12 cross-connections to 8 E1 ports. The VLNC52/55 supports VT1.5 cross-connections to 28 DS1 ports or VC-12 cross-connections to 21 E1 ports.
The VLNC64 circuit pack recovers DS1/E1 signals from the Ethernet LAN inputs, maps them (based on pseudowire provisioning) into VT1.5/VC-12s, which are then transported over the channelized OC-3/STM-1 interface. The VLNC64 circuit pack supports up to 84 DS1 signals or up to 63 E1 signals.
The VLNC50/52/55 circuit pack can be provisioned to support a channelized DS3 signal on port b-3. The channelized DS3 signal can be mapped into 28 DS1 signals. Each of the 28 DS1 signals can be cross-connected to an VT1.5 tributary or a DS1 port. Because these packs support a maximum of 28 DS1s split between the A group and the B-3 group, if a port is used as an electrical DS1 port, the corresponding DS1 port number within the TMUXed DS3 cannot be used. For example, if DS1 port a-1-3 is being used, TMUXed DS1 port b-3-1-3 cannot be used.
The VLNC50/52/55 circuit pack supports dedicated Private Line links between two Ethernet end-points. Private Line service requires minimal provisioning, typically just SONET/SDH cross-connections. The VLNC50/52/55 circuit pack supports only fractional Private Line, not full rate Private Line. For additional information see Ethernet services and Appendix A, Ethernet. Fractional Private Line uses a fractional portion of SONET/SDH bandwidth to provide an Ethernet link with limited bandwidth. It is a form of rate control that also improves efficiency by only consuming the required SONET/SDH bandwidth in increments. For information about how STS-1/VC-3 (low-order), STS-3c/VC-4, or VT1.5/VC-12 tributaries can be virtually concatenated to provide Private Line service, refer to Virtual concatenation.
The intermediate link of an Ethernet Private Line connection prohibits Layer 2 functionality between the two end-points. The performance of a Fractional Private Line with limited bandwidth may be improved using flow control. Because flow control is a layer 2 mechanism, it must be managed across the Private Line by the devices terminating the physical Ethernet links on either end. For information about flow control functionality, refer to Flow control.
The VLNC35 circuit pack supports Gbe/FE Private Line links to the VLNC50/52/55 circuit packs. For more information, refer to Fast Ethernet Private Line over SONET/SDH.
The VLNC40/42/42B Ethernet aggregator circuit pack supports the aggregation of traffic from up to 20 10/100BASE-T ports onto one or more of 4 100/1000BASE-X or 1000BASE-T PTM-based ports. For additional information, see Ethernet aggregation, and 10/100/1G-T/F (VLNC40)/ 10/100/1G-T/F (VLNC42/42B).
The VLNC60/61/62 Circuit Emulator and VLNC64 Circuit Emulation Mini-Hub circuit packs support circuit emulation to preserve the context and nature of TDM services, using the pseudowire technology, over an Ethernet network. The VLNC60 circuit pack supports 8 DS1/E1 access ports, and 2 PTM-based Ethernet LAN ports as uplinks to the EATN or connections to a VLNC40/42/42B. The VLNC61 circuit pack supports 16 DS1/E1 access ports, and 2 PTM-based Ethernet LAN ports as uplinks to the EATN or connections to a VLNC40/42/42B. The VLNC62 circuit pack supports 8 DS1/E1 access ports, and 2 PTM-based Ethernet LAN ports as uplinks to the EATN or connections to a VLNC40/42/42B. The VLNC64 supports 1 channelized OC-3/STM-1 port, and 2 PTM-based Ethernet LAN ports as uplinks to the EATN or connections to a VLNC40/42/42B.
For additional information, see Circuit emulation service (CES), and ML-PPP termination.
The VLNC60/61/62 Circuit Emulator circuit pack terminates ML-PPP sessions at base transceiver stations and transmits the IP traffic directly over the packet network using Ethernet 802.1Q encapsulation. This reduces frame overhead associated with data backhaul over DS1/E1, and reduces the number of ML-PPP sessions that must be terminated by the MLS router at the mobile switching center.
Layer 2 Control Protocols (L2CPs) are used for several purposes in IEEE 802 standard networks, including link maintenance, aggregation, [fllig ]ow control, authentication, identity/capability discovery and management. L2CPs are also used for managing the behavior of LAN bridges, including STP/RSTP/MSTP and GARP/MRP. The VLNC40/42/42B circuit packs support L2CP tunneling. A L2CP frame is identified by the destination MAC address.
On the VLNC40/42/42B, L2CP Tunneling (l2cp-tunnel) can be enabled or disabled on a port-by-port basis. When the mode is disabled, all the rules and characteristics described for the peering of supported protocols apply. When the l2cp-tunnel mode is enabled on a port, all customer L2CP frames/messages for supported and unsupported protocols that are received at that port are forwarded. Because the tunneled protocol is either disabled or unsupported, VLNC40/42/42B does not interpret any of the frames associated with a tunneled protocol.
L2CP Tunneling and Link OAM are allowed simultaneously. However, the loopback cannot be operated and remote loopback capability cannot be enabled when L2CP Tunneling and Link OAM are both enabled on a port.
Note:
Refer to Layer 2 control protocol tunneling for more information.
Transport Multi-protocol Label Switching (T-MPLS) is a network layer technology that uses a subset of the existing MPLS standards and is designed specifically for application in packet networks. It is a connection-oriented packet-switched (CO-PS) technology, well-suited to support Ethernet services. It offers a simpler implementation than MPLS by removing features that are not relevant to CO-PS applications and adding mechanisms that provide support of critical transport functionality (T-MPLS = MPLS - IP + OAM).
T-MPLS uses the same architectural principles of layered networking that are used in other technologies like SDH and OTN and provides a reliable packet-based technology that is familiar and aligned with circuit-based transport networking. It can run on any physical layer.
The VLNC42B circuit pack supports T-MPLS:
Faceplate Ethernet ports (d1-1, d1-2) can be T-MPLS-enabled as GbE Label Edge Router (LER) or Label Switch Router (LSR) Network to Network Interfaces (NNI).
Faceplate Ethernet ports (d1-3, d1-4) can be T-MPLS-enabled either as GbE Label Edge Router (LER) or Label Switch Router (LSR) Network to Network Interfaces (NNI), or as GbE Label Edge Router (LER) User to Network Interfaces (UNI).
20 100BASE-TX Ethernet User to Network Interface (UNI) ports.
Note:
Up to 2 T-MPLS rings can be supported by enabling T-MPLS on all 4 faceplate ports (d1-x) and as NNIs.
According to G.8112, the Alcatel-Lucent 1850 TSS-5 supports reserved label space [Label Range: 0..15] with label 14 for T-MPLS OAM and label space [16...1048575] as T-MPLS Label Range. Both label static allocation.
Ethernet over T-MPLS encapsulation (LER functionality). Circuit Emulation traffic from VLNC6x is carried as Circuit Emulation over Ethernet over T-MPLS
1588 ToD and 1PPS capabilities is supported on the VLNC62 circuit pack. With 1588 transparent clock for 1588/VLAN/Eth PW/T-MPLS/EthPHY. 1588 packets will be carried in a tunnel provisioned with a special, reserved label number range.
The VLNC62 also supports 1588 SYNC distribution without a GPS input. A option is available in CLI and Web GUI to configure the pack in ToD or non-ToD (without GPS) mode.
Point-to-point (E-LINE) connections
Support for a maximum of 750 bidirectional MPLS TUSegment; up to 250 may be terminated Tunnels.
64 protection groups (exactly 2 tunnels per group)
250 bidirectional psuedowires per shelf
Connectivity Verification (CV) capability to be used as a trigger for tunnel protection switching
Automatic Protection Switching (APS) capability needed to support protection switching in 1:1 APS
Forward Defect Indication (FDI) and Remote Defect Indicator (RDI) capability to be used as a trigger for protection of for APS 1:1 protection and dual homed E-LAN configurations
Ring Automatic Protection Switching (R-APS) is used to signal the need for MAC table flushing in a dual-homed network configuration.
T-MPLS Quality Of Servic: T-MPLS supports either 8 classes of service (8p0d) or 5 classes of service (5p3d) depending on the PHB profile configured on the T-MPLS tunnels and pseudo-wires.
Tunnels and pseudo-wires are either color-aware (in 5p3d mode) or color-blind (in 8p0d mode). Dual-rate metering (CIR [les ] PIR and CBS [les ] PBS) on the ETS Flows supports color-awareness. Single-rate metering (CIR=PIR and CBS=PBS) to be used with color-blind tunnels and pseudo-wires.
ETS Component management (the connection between the Ethernet UNI and the T-MPLS Pseudowire), including Ethernet Port provisioning.
This functionality to be supported by OpticsIM MIB SNMP and includes provisioning and alarming. NML T-MPLS service provisioning is included.
OpticsIM MIB SNMP support for ETS provisioning and Ethernet port provisioning. SNMP Get/Trap support for Circuit Emulation functionality.
TL1 commands support T-MPLS provisioning and TL1 autonomous message support for T-MPLS alarms.
Refer to Alcatel-Lucent 1850 Transport Service Switch (TSS-5) TL1 Command Guide for T-MPLS for details.
E-LAN support (including Dual Homing support) – with TSS-5 as a PWE3 spoke; supports RDI, FDI, and R-APS as protection switching criteria.
Signal Degrade (derived from Digital Diagnostic Monitoring of SFP received optical power levels) as a protection-switching trigger
Simple Call Admission Control (CAC) functionality
CAC verifies that the system resources and all the traffic descriptor parameters of T-MPLS PW and Tunnels and of Ethernet ETS flows are coherent. The CAC checks not only the Committed Rate (CIR), but also the Peak Rate (PIR) and the burst sizes, in order to verify that they comply with the available bandwidth/resources.
PM on T-MPLS tunnels and PWs
PM on Ethernet ports and ETS flows
Bundling of PM data into files (one for T-MPLS data and one for Ethernet/ETS data)
Ethernet Service OAM: 802.1ag CFM (CC, LB, and LT)
802.3ah link OAM on UNI and NNI ports
Note: Loopbacks are not supported on NNI ports.
Egress rate shaping per port (UNI and NNI)
Support for Optical FE SFPs for Ethernet UNI.
Support for Electrical GE SFPs and Optical/Electrical FE SFPs for NNI ports
Ethernet services over T-MPLS or Ethernet (system-level mode selection)
The C-VLAN push/pop feature allows a C-VLAN to be popped at ingress, and allows a C-VLAN to be pushed at egress. The C-VLAN IS considered to be “service delimiting”. Rather than tunneling the C-VLAN, it is mapped to a selected pseudo-wire.
Configuring C-VLAN push/pop on a flow can only be done when the flow is disabled. The C-VLAN pop functionality is configured per ETS Inflow, and the C-VLAN push functionality is configured per ETS Outflow. Per pseudo-wire, all ETS inflows should have the same C-VLAN pop setting, and per pseudo-wire/Forwarding Class combination. All ETS outflows should have the same C-VLAN push settings (VLANid, p-bits, etc). Configuring C-VLAN pop on an inflow is only allowed with VID-related inFlow classifiers : VID, VID+p-bits, VID+ethertype, VID+pbits+ethertype.
The C-VLAN-id to be pushed is configurable (per ETS outflow), as well as the VLAN tag p-bits to be pushed. The p-bits represent the Ethernet Forwarding Class (guaranteed/regulated forwarding class) configured for the NNI-to-UNI direction flow. A separate p-bit value can be configured to be used for yellow packets if color is supported depending on the pseudo-wire PHB profile.
In-band management software of the VLNC42B requires the presence of a management VLAN tag within the T-MPLS payload of the psuedo-wire that is used for in-band management. Remote systems at the far-end of the in-band management psuedo-wire may not always be prepared to have the psuedo-wire carry a management VLAN tag. Allowing for C-VLAN push/pop locally on the VLNC42B for in-band management psuedo-wires removes the need for far-end systems to insert the management VLAN. Therefore, C-VLAN push/pop is also possible when applied to inFlows and outFLows that terminate on the in-band management port a-100.
| Copyright © 2011 Alcatel-Lucent. All rights reserved. |