|
|
This chapter provides an overview of the physical and logical connectivity to CTM ConnectWay, describes the features of CTM ConnectWay, and offers configuration guidelines.
CTM ConnectWay is an optional standalone component application that provides EMS-to-NE protocol mediation for Cisco ONS 15303 and Cisco ONS 15304 network elements (NEs) within multivendor network configurations. CTM ConnectWay enables service providers to use their existing heterogeneous SONET or SDH management communications infrastructure to manage Cisco ONS 15303 and Cisco ONS 15304 NEs by using CTM or a third-party SNMP manager.
 |
Note In CTM ConnectWay Release 2.0, Cisco offers TL1 (Cisco ONS 15303 applications only) and CLNP interface options. |
 |
Tips See the "System Requirements" section for the appropriate platform to run CTM ConnectWay. |
CTM ConnectWay/CLNP enables SNMP-based applications to communicate with the Cisco ONS 15303 and Cisco ONS 15304 over an Open System Interconnection (OSI) network.
CLNP is an OSI network layer protocol that does not require a circuit to be established before data is transmitted.
To configure CTM ConnectWay/CLNP end-to-end:
clns routing clns holding-time 60000 clns configuration-time 30000 interface CTunnel0 ip address 10.10.10.101 255.255.255.0 no shutdown ctunnel destination 39.840f.8000.0000.0000.0001.1001.0000.0a0a.0a01.cc router isis net 39.840f.8000.0000.0000.0001.1001.0000.0a0a.0a65.00 ip route 1.18.0.0 255.255.0.0 CTunnel0
Step 2 Set up the Cisco 3600 router configuration by entering the following commands:
clns routing interface Ethernet0/0 ip address 1.18.18.52 255.255.0.0 no ip directed-broadcast clns net 39.840f.8000.0000.0000.0001.1001.eeee.ffff.cccc.00 clns router isis router isis net 39.840f.8000.0000.0000.0001.1001.eeee.ffff.cccc.00
Step 3 Set up the CTM server configuration by entering the following command:
route add net 10.10.10.0 1.18.18.51
Step 4 Set up the CTMIPCLNP server configuration by entering the following commands:
Ethernet port0: 1.18.18.51 CLNS/odlp0 address: 10.10.10.1
Step 5 Set up the foreign GNE configuration. The GNE must have CLNS enabled on the section DCC and must act as an ES-IS or IS-IS router.
|
Note The IP addresses listed in Figure 4-2 are examples only. |
To add or remove a network element, enter the following command:
CTMSHOME/cwconfig {add | delete} IP address NSAP address
For example:
CTMSHOME/cwconfig add 10.10.10.101 39840F8000000000000001100100000a0a0a65cc
CTM ConnectWay/TL1 can be deployed in a service provider's network as a standalone application for use with a third-party SNMP manager. CTM ConnectWay/TL1 provides EMS-to-NE (Cisco ONS 15303) protocol mediation, allowing service providers to leverage their existing network management communications architecture.
TL1 is a standard man-machine language (MML) developed by Telcordia Technologies (formerly Bellcore) in the mid 1980s as a basis for interoperability across multivendor technologies. In a series of published standards, Telcordia defined the TL1 language and a number of messages specific to technology, such as transport and access NEs. As deployment of TL1-based NEs increased throughout North America, Telcordia and other vendors developed OSS software applications by using TL1 as the NE management protocol.
The CTM ConnectWay/TL1 application encapsulates Cisco ONS 15303 SNMP-based traps and commands in a native TL1 format that complies with Telcordia specifications. CTM ConnectWay does not perform protocol conversion, but wraps SNMP messages in a TL1 wrapper to access the Cisco ONS 15303 elements on the SONET OC-3 ring through a TL1-based foreign gateway network element (GNE), such as an Add Drop Multiplexer (ADM) or digital cross-connect system (DCS).
|
Note In Figure 4-3, the CLNP tunnel shown is not required for CTM ConnectWay/TL1 operation. The CLNP tunnel is an option for service providers that require remote Cisco ONS 15303 login from either Cisco ONS 15303 on the ring. |
As shown in Figure 4-3, the CTM server and clients communicate with the Cisco ONS 15303 by using IP packets that contain SNMP messages and commands. In the foreign GNE architecture shown in Figure 4-3, CTM ConnectWay/TL1 encapsulates the IP packets as TL1 messages and forwards them through the data communications network (DCN) to the GNE. The GNE acts as a TL1 gateway, accepting TL1 messages and routing them to the target Cisco ONS 15303 on the SONET OC-3 ring. The GNE routes TL1 messages by using Intermediate System to Intermediate System (IS-IS) on the SONET overhead data communications channel (DCC) by using a TP4-over-CLNP session.
|
Note The SONET DCC must be a seven-layer OSI protocol implementation that complies with Section 8 of Telcordia Technologies (formerly Bellcore) GR-253, Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria, Issue 2, December 1995, Revision 1, December 1997. |
The CTM server uses the following IP packets:
The CTM clients (through the CTM server) use the following IP packets:
|
Note All CTM ConnectWay/TL1 clients ---namely the CTM server, the CTM client, or a third-party SNMP network manager---require a static IP route to each Cisco ONS 15303 through the CTM ConnectWay/TL1 interface. |
The following example describes a typical interaction between a CTM client and a remote Cisco ONS 15303 (through a foreign GNE) by using CTM ConnectWay/TL1:
1. CTM client composes an IP packet (SNMP, Telnet, or TFTP packet) destined for a remote Cisco ONS 15303 identified by its IP address. Due to the static route configuration set up for this Cisco ONS 15303, the IP packet is sent to the CTM ConnectWay/TL1 server.
2. When the CTM ConnectWay/TL1 server's IP module receives an IP packet from the CTM client, it encodes the packet in a TL1 message. For an X.25-based DCN, CTM ConnectWay/TL1 forwards the TL1 message through a pre-established TCP/IP connection to an external X.25 packet assembler/disassembler (PAD).
3. The X.25 PAD maintains an X.25 session to the GNE through a virtual circuit and sends the TL1 packet to the GNE.
4. The GNE parses the TL1 packet, which contains the target identifier (TID) of the destination Cisco ONS 15303. The GNE routes the TL1 message by using IS-IS over a TP4-over-CLNP session.
5. The target Cisco ONS 15303 decodes the TL1 message and extracts the IP packet.
|
Note The Cisco ONS 15303 has embedded CTM ConnectWay/TL1 software that performs TL1 encoding and decoding, enabling the Cisco ONS 15303 to receive and send TL1 messages within the SONET overhead DCC. |
The ConnectWay.cfg configuration file contains the required network configuration parameters and is in the directory /opt/CiscoTransportManagerServer/cfg with the existing CTMServer.cfg file.
Step 2 Restart CTM ConnectWay/TL1 for the new configuration to take effect.
Table 4-1 describes the CTM ConnectWay/TL1 configuration parameter syntax used in the file ConnectWay.cfg.
|
Note The term southbound refers to the direction of information that is transferred from CTM ConnectWay/TL1 to the Cisco ONS 15303. The term northbound refers to the direction of information transferred from the Cisco ONS 15303 to CTM ConnectWay/TL1. |
| Section | Definition | ||||
|---|---|---|---|---|---|
| <nesysid> = <neipaddr>, <nedbaccessid>, <gneid> where:
Example: ONS1 = 91.0.1.2, 1, 1 ONS2 = 90.0.0.2, 2, 2 | ||||
| <gnesysid> = <gneid>, <nexthopipaddr>, <tcpportnum>, <encodingscheme>, <northboundverb>, <southboundverb>, <southboundaid>, <northboundMsgType> where:
| ||||
Example: OC3ADM1 = 1,192.168.120.23,8000,3,REPT EXT EQPT,WRT-MEM-FILE,,2 |
| Parameter | Possible Values (default in bold text) | Description | ||
|---|---|---|---|---|
encodingscheme | 1 | Denotes Binary encoding where the IP PDU is directly encoded in a TL1 message. | ||
| 2 | Denotes Binary 36 encoding where the IP PDU is encoded by using base 36 encoding; then, placed in a TL1 message. | ||
encodingscheme | 3 (default) | Denotes alphanumeric encoding where the IP PDU is encoded in an alphanumeric string; then, sent as part of a TL1 message. | ||
| 4 | Denotes uuencoding where the IP PDU is encoded by using the uuencode method; then, sent as part of a TL1 message.
| ||
northboundverb | Verb-Modifier[-Modifier] REPT^EXT^EQPT | Denotes the TL1 verb to use for northbound communications. | ||
southboundverb | Verb-Modifier[-Modifier] WRT-MEM-FILE | Denotes the TL1 verb to use for southbound communications. | ||
southboundaid | AID Null (default) | Denotes the TL1 access identifier to use for southbound communications. | ||
northboundMsgType | 1 | Indicates that a TL1 command will be used for northbound communications. | ||
| 2 (default) | Indicates that a TL1 autonomous message will be used for northbound communications. |
Any third-party SNMP management software that uses CTM ConnectWay/TL1 to communicate with a Cisco ONS 15303 through a foreign GNE must be configured with static routes for each Cisco ONS 15303, or configured with a subnet address for Cisco ONS 15303s by using a common foreign GNE. This establishes IP connectivity to the Cisco ONS 15303 from the third-party SNMP manager by using the TL1 tunnel (TTunnel) address.
|
Note If the third-party SNMP manager is running on a separate workstation, the next hop for each route is the IP address of the CTM ConnectWay/TL1 Sun Solaris server. |
In order for CTM ConnectWay/TL1 to operate, configure the following information on each Cisco ONS 15303:
Step 2 Configure the TL1 tunnel (TTunnel) interface (foreign GNE to Cisco ONS 15303).
Step 3 (Optional) Configure the CLNP tunnel (CTunnel) interface (Cisco ONS 15303 to Cisco ONS 15303).
|
Tips For details, refer to the Cisco Optical Networking System 15303 Software Configuration Guide. |
Posted: Thu Jun 29 15:21:52 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.