This section briefly describes the major features related to management and operation of Alcatel-Lucent 1850 TSS-5, supported for Release 7.2. It also includes descriptions of features that will be supported in future releases of Alcatel-Lucent 1850 TSS-5.
Alcatel-Lucent 1850 TSS-5 supports terminal and facility loopbacks for DS1/E1 and DS3/E3 interfaces supported by the VLNC50/52/55 circuit pack and DS1/E1 interfaces supported by the VLNC60/61/62 circuit pack. The VLNC35 supports terminal loopbacks on Ethernet interfaces.
A terminal loopback connects the signal that is about to be passed through the tributary interface to the DSX back toward the cross-connect fabric to the optical line (or pseudowire in the case of the VLNC60/61/62). During a terminal loopback, the tributary DSX interface outputs an Alarm Indication Signal (AIS). Terminal loopbacks are used during installation and maintenance procedures to test the integrity of near and far-end interfaces as well as fibers and system circuitry.
A facility loopback loops the signal at the tributary interface so that the signal received from the DS1/E1 facility is transmitted back toward the facility. Facility loopbacks are used for installation and maintenance procedures to test the integrity of the tributary facilities and the DS1/E1 terminal equipment.
Alcatel-Lucent 1850 TSS-5 supports external optical loopbacks on the optical interfaces for the OC-n/STM-n lines.
Alcatel-Lucent 1850 TSS-5 supports Loopback-Opt and Loopback-Eth on the DS1/E1 interfaces of VLNC64. Loopback-Opt is used in maintenance procedures to test the DS1/E1 signal from OC-3/STM-1 interface. Loopback-Eth is used in maintenance procedures to test the DS1/E1 signal received via the Circuit Emulation Pseudowire.
Inband-requested DS1 loopbacks for VLNC50/52/55 SONET Transport and VLNC60/61/62 Circuit Emulator circuit packs are also supported. Inband-requested DS1 loopbacks can be provisioned using either inband signal control (ISC) patterns or a bit-oriented codes (BOC) within the DS1 signal received from the DSX (VLNC50/52/55 and VLNC60/61/62) or optical fiber (VLNC50/52/55).
The VLNC50/52/55 circuit packs also support Far End Alarm Channel (FEAC) requested DS1 and DS3 facility loopbacks on the channelized, cbit-framed, b-3 DS3 port. The FEAC-requested loopbacks are provisioned using FEAC codes within the b-3 DS3 signal received from the DSX. The ability to respond to FEAC loopback requests is provisionable on the b-3 DS3 port only.
Cross-connect loopbacks are supported on the tributaries of the optical SONET/SDH ports of the VLNC50/52/55 circuit pack. A tributary received on an optical interface is looped back, through the cross-connect fabric, to the same-numbered tributary in the transmit optical interface, and AIS is inserted downstream if the tributary is cross connected.
The VLNC40/42/42B supports IEEE 802.3 Clause 57 (802.3ah) active and passive mode Link OAM on the 20 10/100 backplane FE ports and the 4 PTM-based faceplate ports. The remote loopback option is supported, allowing an interface to initiate or respond to loopback requests with compatible link partners. In Active mode, a port can send a loopback command or respond to a loopback request from the remote end. In the Passive mode, a port can only respond to a loopback request from the remote end. The loopback routes frames received from the line back to the transmit direction. This facility loopback can only be operated remotely, with a CLI command at the originating node causing activate/deactivate inband OAMPDU frames to be sent to the remote node. Monitoring associated with the loopback can be done at the originating end of the link allowing tests to be run from one location.
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.
Beginning in Release 7.1, the VLNC40/42/42B circuit packs support VLAN loopbacks. Refer to VLAN loopback for additional information.
When equipped with VLNC2 and VLNC50/52/55 circuit packs, the WaveStar® CIT manages SONET/SDH operations for the Alcatel-Lucent 1850 TSS-5 through the serial RS-232 or IAO/LAN port. It provides TL1 messaging, software download for the VLNC2 and VLNC50/52/55, and full operations and provisioning capability via a Graphical User Interface (GUI) or TL1 command builder. The WaveStar® CIT can run a full-featured GUI or TL1 scripts. Using the GUI, a crafts person can access all Alcatel-Lucent 1850 TSS-5 software functions and context-sensitive help. The TL1 command builder is a flexible TL1 command builder that supports full TL1 management through LAN or RS-232 interfaces. It provides a simple list of TL1 commands and prompts to help complete them more quickly.
Software and software upgrades may be downloaded to the CLI-managed circuit packs (VLNC40/VLNC42/VLNC42B/VLNC60/VLNC61/VLNC62/VLNC64) using a Trivial File Transfer Protocol (TFTP) server. The requirements of a TFTP server depend upon the characteristics (for example, speed and delay) of the customer's management network, and the possible load placed on the server by multiple NEs.
If the TFTP server is on a heavily loaded (or limited bandwidth) network, the server should provide a configurable per-packet timeout of up to approximately 15 seconds. If many NEs will be hosted by a single TFTP server, then the server should support multiple, simultaneous transfers (multi-threaded).
Free TFTP servers that support the features described are available from multiple sources. 3Com provides a free TFTP server, 3CDaemon, that supports the features described. The software package is available for download from the 3Com Support web site, Utilities for Windows 32 Bit.
Beginning in 7.1, the VLNC2 SYSCTL circuit pack supports SSH File Transfer Protocol (SFTP) for software download, database backup, and database restoration. SSH File Transfer Protocol (SFTP) is a new protocol defined by IETF which runs over a secure SSH channel and provides secure file transfers. Network configurations, user names, passwords, FTP commands and transferred files are protected.
Note:
You must have IP connectivity between your NE and your SFTP server, and your NE must have a defined IP address. The WaveStar® CIT is not SSH FTP (SFTP) server. You must have access to an SSH FTP server to use this feature.
Beginning in R6.0 the VLNC4x/VLNC6x circuit packs, copy commands upload and download files to/from the switch using SFTP in addition to TFTP.
The VLNC2 SYSCTL circuit pack supports a new Network layer routing protocol feature: Dual (IP + OSI) DCC interfaces with Intermediate System to Intermediate System (IS-IS). It is an intra-domain routing protocol used in an OSI environment to provide the connectionless-mode network service. This feature applies to all supported SONET optical interfaces including OC-3, OC-12, and OC-48.
ITU-T G.7712 specifies three types of interfaces for the SONET embedded DCN
IP-only interface: IP over DCC
The IP-only interface uses DCC as the Physical layer. The Data Link layer protocol is PPP (RFC 1661 and RFC 1662). The Network layer protocol is IPv4 (RFC 791). The common Network layer routing protocol is OSPF.
OSI-only interface: OSI over DCC
OSI-only interface uses DCC as the Physical layer. The Data Link layer protocol is LAPD as specified in ITU-T Q.921. The Network layer protocol is CLNP (ISO 8473). The Network layer routing protocol is IS-IS (ISO 10589), in conjunction with ES-IS (ISO 9542).
Dual interface: DCC interfaces can carry both IP and OSI packets in parallel.
The Physical layer is DCC. The Data Link layer protocol is user-configurable, as either PPP or LAPD (as specified in ITU-T G.7712). The Network layer protocols are IPv4 and CLNP. A single routing protocol, integrated IS-IS as specified in RFC 1195, in conjunction with ES-IS, are used to route both IP and OSI packets. The integrated IS-IS protocol is based on ISO 10589 IS-IS and uses the same protocol identifier as IS-IS, with IP-specific functions added in the optional field. From the OSI routing perspective, the integrated IS-IS is fully equivalent to and interoperable with IS-IS. Alcatel-Lucent 1850 TSS-5 supports LAPD as the data link protocol on the Dual interface.
When one or more DCC interfaces are provisioned as Dual, (IP + OSI) interface, the system must have a Router ID provisioned. The Router ID parameter is a 32-bit IP address and is used as if it is the IP address of all unnumbered interfaces (Dual interfaces). The Router ID could be the same as or different from the IP address assigned (if there is) to the front LAN interface. However, it is recommended that the Router ID be the same as the IP address assigned (not the default) to the front LAN (LAN-1).
LAN-1 on the SYSCTL supports OSI, IP, and both OSI and IP.
When only OSI is enabled, the routing protocol is IS-IS.
When only IP is enabled, there is no routing protocol running on the LAN interface (no LAN IS to IS Hello PDU).
However, the reachability information (LAN IP address and subnet mask) and the default route/static route(s) if configured are included in LSPs transmitted over dual (IP+OSI) DCC interfaces. When both OSI and IP are enabled, the integrated IS-IS is supported on the LAN interface.
Performance monitoring (PM) data is reported on the VT1.5s/VC-12, STS-1/VC-3 (low-order), STS-3c/VC-4, STS-12c/VC-4-4c, DS1/E1, DS3/E3, OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, Fast Ethernet, and Gigabit Ethernet levels.
Operations supported by the VLNC40, VLNC42/42B, VLNC60, VLNC61, VLNC62, and VLNC64 circuit packs are managed by a separate Command Line Interface (CLI) that is accessed by a serial or network connection to the circuit pack.
You have two options to communicate with the CLI-based packs:
The Web GUI can be used to manage the VLNC42B in both bridge and T-MPLS mode. Bridge mode on the VLNC42B uses CLI commands. In T-MPLS mode, the VLNC42B uses SNMP and TL1 commands.
Note:
Refer to Alcatel-Lucent 1850 Transport Service Switch (TSS-5) CLI User Provisioning Guide.
The Web GUI and CLI messages permit VLNC4x/VLNC6x circuit pack operations to be performed (for example, administration and provisioning). The Web GUI and navigation windows are designed to be straightforward and to contain all information relating to a particular operation.
For a detailed description of the Command Line Interface (CLI) messages and general information about using the Command Line Interface (CLI), refer to the Alcatel-Lucent 1850 Transport Service Switch (TSS-5) Command Line Interface Guide.
To use the Web GUI, each VLNC4x or VLNC6x pack must be connected to the network and have its IP address configured. The user then accesses the pack via the Web GUI by entering the IP address of the pack as the URL in the HTTP-enabled Web browser. The Login screen is displayed next. Once the user enters the valid username and password and connecting to the VLNC4x or VLNC6x pack is successful, then the Web GUI main page is displayed.
Refer to refer to the Alcatel-Lucent 1850 Transport Service Switch (TSS-5) CLI User Provisioning Guide for more information about using the Web GUI.
The Web GUI has been tested with the following browsers:
Mozilla FireFox® 3
Mozilla FireFox® 3.5
Microsoft® Internet Explorer 7.0
Microsoft® Internet Explorer 8.0
When equipped with a VLNC2 and VLNC50/52/55, TL1 management for SONET/SDH operations is supported via the RS-232 and LAN interface using a PC and a windows-based graphical user interface (GUI). The GUI is called the WaveStar® Craft Interface Terminal (WaveStar® CIT) and permits system-level and VLNC50/52/55 circuit pack/port operations to be performed (for example, administration, provisioning, and fault management).
T-MPLS mode on the VLNC42B uses SNMP and TL1 commands. Bridge mode on the VLNC42B uses CLI commands.
Default IP access and addresses on the faceplate LAN ports of the SYSCTL and the self-managed VLNC40/VLNC42/VLNC42B/VLNC60/VLNC61/VLNC62/VLNC64 circuit packs allows a plug-and-play capability for IP communications between the WaveStar® CIT or other PC and the network element initially. You can log in and perform an initial software download to the network element via IP from the WaveStar® CIT or other PC without manually reconfiguring the WaveStar® CIT/PC.
Software and software upgrades can be downloaded to remote NEs via the File Transfer Protocol (FTP) or secure FTP over the IAO LAN connected to the LAN port on the SYSCTL. This requires that FTP is enabled on the NE, and that IP is enabled and properly configured on the SYSCTL LAN port. FTAM and FTTD are also supported for remote software downloads.
Software and software upgrades can also be downloaded to a VLNC40/VLNC42/VLNC42B/VLNC60/VLNC61/VLNC62/VLNC64 circuit pack using a Trivial File Transfer Protocol (TFTP) server.
Software downloads and control of the VLNC40/VLNC42/VLNC42B/VLNC60/VLNC61/VLNC62/VLNC64 circuit packs are independent of the SYSCTL circuit pack. They require IP network connectivity to the VLNC40/VLNC42/VLNC42B/VLNC60/VLNC61/VLNC62/VLNC64 circuit pack as described in Remote software download for non-SYSCTL controlled circuit packs.
The address resolution protocol (ARP) is a method for associating the physical media access code (MAC) of a hardware device on a local physical network with a network address that can be routed for use over the larger overall network. Using this protocol, one network device tries to locate another device associated with a specific network address by broadcasting an ARP request on the on the local physical network. The ARP request contains the IP address of the device being sought. If a device on the local network has been configured with this network address, it responds with to the ARP request its physical MAC address. Once the association between local MAC hardware address and the network address of the device is established it can communicate with other devices on remote networks, using its network address.
ARP requests are not broadcast or routed beyond the local physical network media. Standard ARP cannot resolve addresses for network devices on the single logical network if that logical network consists of multiple physical networks linked by different physical media. Devices on one physical network cannot receive ARP requests from devices on another physical network. Proxy ARP uses a system, called ARP sub-net gateway, to answer ARP requests received from a device on one of its physical (LAN) networks for a target that is located on a different physical network.
Alcatel-Lucent 1850 TSS-5 supports IP tunneling to encapsulate and route IP packets over OSI-based embedded DCN. This allows NTP server and other services located in the IP-based access Data Communication Network (DCN) to communicate with NEs located in the OSI-based DCN. The tunnels also physically separate the devices on the IP network. Proxy ARP support on the Gateway Network Element (GNE) eliminates the need to create static routes to route the IP packets from the access DCN to the embedded DCN.
The ARP Subnet Gateway implementation adheres to RFC1027 which states that, if the IP networks of the source and target hosts of an ARP request are different, an ARP subnet gateway implementation should not reply to the request. This is to prevent the ARP subnet gateway from being used to reach foreign IP networks and possibly bypass security checks provided by IP gateways.
Because of this RFC requirement, the IP addresses of both the GNE and RNE must be in the same network with respect to network class (A, B and C). For example, if the GNE has a class C IP address 192.168.170.1, the RNE must have an IP address in the same Class C network, in the form 192.168.170.x. For proxy ARP to function properly, the Remote NE IP address must be in the same subnet as the IP address of the router, as specified by the network mask on the router. Otherwise, the router will not send the ARP request to the appropriate LAN port, and will instead route the packet through its default IP gateway into the IP cloud.
However, the IP address of the remote NE should not be in the same subnet as the IP address of the GNE, from either the GNEs network mask perspective or the RNEs network mask perspective. An easy way to achieve this on the RNE is to assign a 32-bit network mask to all RNEs.
This feature provides interworking using the Open Systems Interconnection (OSI) seven-layer protocol stack over the data communications channel (DCC). The OSI seven-layer protocol stack refers to the OSI reference model, a logical structure for network operations standardized by the International Standards Organization (ISO).
The independently-managed VLNC40/VLNC42/VLNC42B/VLNC60/VLNC61/VLNC62/VLNC64 circuit packs and the SYSCTL-controlled VLNC50/VLNC52/VLNC55 circuit packs use Simple Network Management Protocol (SNMP). SNMP is the most common protocol used by data network management applications to query a management agent using a supported Management Information Base (MIB). SNMP operates at the OSI Application layer. The IP-based SNMP is the basis of most network management software, to the extent that today the phrase managed device implies SNMP compliance. Alcatel-Lucent 1850 TSS-5 supports SONET, SDH, and Ethernet gets and traps. When in T-MPLS mode, Alcatel-Lucent 1850 TSS-5 also supports sets.
For more information, refer to SNMP interface in Chapter 5, Operations, administration, maintenance, and provisioning of this document.
This feature partitions a subnetwork into maintenance domains (alarm groups). An Alarm Group is a set of NEs that share status information. Alarm groups can be nodes in a ring or any other logical grouping such as a maintenance or geographical group. Each Level 1 area can be identified as a separate Alarm Group, as long as it does not exceed 250 nodes. You must provision one NE in an Alarm Group as an alarm gateway NE (AGNE) to support office alarms and a summary alarm information of remote NEs in the local alarm report. More than one AGNE can be provisioned per alarm group, but this is not recommended.
Security features include 1–999 day password aging, customized login proprietary messages, and up to 150 users.
When the network element is provisioned to use RADIUS authentication, any user TL1/CLI/Web GUI login attempt triggers the network element, if the maximum number of logins is not reached, to query the designated RADIUS server(s) and act on the response.
Alcatel-Lucent 1850 TSS-5 is compatible with any other-vendor NEs that support Target ID Address Resolution Protocol (TARP), OSI, IAO LAN, and TL1 as specified in Telcordia ® GR-253.
Many of the traditional SONET/SDH maintenance, provisioning, operations, control, and synchronization features are included in the Alcatel-Lucent 1850 TSS-5. The flexible SONET and SDH standards provide a formidable foundation for the Alcatel-Lucent 1850 TSS-5 to build upon.
Alcatel-Lucent 1850 TSS-5 supports interoperability with many vendors' equipment; particularly those that support GR-253 standards-based SONET and ITU-T standards-based SDH.
Alcatel-Lucent 1850 TSS-5 supports TARP interoperability with Product Family 2000 nodes such as the FT-2000 OC-48 Lightwave System, the DDM-2000 OC-3/OC-12 Multiplexer, and the DDM-2000 FiberReach Multiplexer.
Alcatel-Lucent 1850 TSS-5 also provides interoperability with all WaveStar® Product Family nodes supporting TARP.
In a typical network, the Alcatel-Lucent 1850 TSS-5 is a remote NE (RNE) interworking with an Alcatel-Lucent 1850 Transport Service Switch 100 or Alcatel-Lucent 1850 Transport Service Switch 320 functioning as the gateway NE (GNE). The Alcatel-Lucent 1850 Transport Service Switch 100/Alcatel-Lucent 1850 Transport Service Switch 320 GNE supports T-TD (TL1 Translation Device) to translate TL1 over TCP/IP to TL1 over OSI. This allows TL1 management of a remote Alcatel-Lucent 1850 TSS-5. However, to fully support IP tunneling interworking between a remote Alcatel-Lucent 1850 TSS-5 and the Alcatel-Lucent 1850 Transport Service Switch 100/Alcatel-Lucent 1850 Transport Service Switch 320 GNE, the Alcatel-Lucent 1850 TSS-5 supports a provisionable NSAP selector parameter that allows software operations (download/backup/restore) to a remote Alcatel-Lucent 1850 TSS-5 using FT-TD (File Transfer Translation Device) to translate FTP over TCP/IP to FTAM over OSI.
When the channelized DS3 (port b-3) of the VLNC50/52/55 circuit pack is provisioned for cbit formatting a limited set of FEAC codes (defined in ANSI T1.107) is transmitted toward the DSX when certain alarm conditions are detected (for example, DS3 loss of signal or equipment failure).
The FEAC requested DS1 and DS3 loopback capability can also be enabled/disabled on the cbit-formatted, channelized b-3 DS3 port of the VLNC50/52/55 circuit pack. The FEAC loopback codes are received on the incoming DS3 from the DSX.
| Copyright © 2011 Alcatel-Lucent. All rights reserved. |