Cisco 3662 Installation

14. Cisco 3662 installation GSR7

Chapter 14

Cisco 3662 installation

Installation & Configuration:OMC-R Clean Install

24 May 2004 68P02901W47-Q 1


The Cisco 3662 router

BackgroundAll communication between the OMC-R and BSS is based on the X.25 protocol. The Cisco 3662 Router is used to establish the X.25 communication circuits (Virtual Circuits) between the OMC-R and BSS. This chapter has the following sections:

The Cisco 3662 router (this section).

Connectivity, configuration and LAN connection.

Establishing OMC and GSM connections.

Enabling X.25 routing and creating Hunt Groups.

Creating X.25 routes.

Integration with the existing Vanguard 6560 router.

Useful Cisco commands.

NOTE: This Cisco 3662 router may have been pre-configured before leaving Motorola staging.

PrerequisitesA PC or laptop is required to perform the initial and basic router setup.

The following information is required to complete the Cisco 3662 setup.

New IP address and subnet mask for the Cisco 3662.

Default Gateway to communicate with other Local Area Networks.

X25 configuration information for the OMC-R. All of the necessary X.25 information can be retrieved from the x25_config file on the live OMC-R. This file is located in the /usr/omc/config/global directory of the OMC platform.The following information is required for each GSM Network Element being connected:

The timeslot being used.

The DTE address of the Network Element.

Introduction to the Cisco 3662 router hardwareThe Cisco 3662 router contains serial ports and channelized E1 ports for connecting the OMC-R to the GSM network. This section gives a brief overview of the hardware and cables used, and details the capacity of the 3662. Please use this section to become familiar with the slot numbering in the 3662 and port numbering on the interfaces that are contained in these slots.


24 May 2004 68P02901W47-Q 2


The routerThe 3662 router contains six modular expansion slots. Each slot is capable of hot-swapping network modules to allow for high availability. The configuration of the router dynamically updates upon insertion or removal of network modules. The Console port located on slot 0 of the router is used for the initial and basic configuration. There are two Fast Ethernet ports on Slot 0 (top of the chassis).

Once the initial and basic configuration steps have been completed, we recommend connecting through the Ethernet 0/0 port to perform the rest of the configuration. However, this can also be achieved through the Console connection. This Ethernet connection can also be used to debug, troubleshoot and monitor the X.25 packet switching if necessary.

The Cisco 3662 router contains 256Mb of SDRAM and 16Mb of flash to store the Internetworking Operating System (IOS). Please refer to Figure 14-1 to identify the positions of the different slots on the 3662 router.

Figure 14-1 The 3662 router

Four Port Serial InterfaceThe Four Port Serial Interface module has four ports numbered from 0 to 3. Each port can have a data rate of 2Mbps. The ports are identified in the Cisco configuration file by <slot number / port number>. Refer to Table 14-1 to identify the required number of modules for OMC connectivity and the recommended slots used. Figure 14-2 is a pictorial view of the module.

Figure 14-2 Four Port Serial Interface module to connect to the OMC


24 May 2004 68P02901W47-Q 3


Two Port Channelized E1 InterfaceThe channelized E1 ports are used to connect the GSM BSS equipment. Each E1 port can receive and transmit data bi-directionally at 2.048 Mbps, and provide up to 31 virtual channels. Each individual channel or time slot can be configured as a separate serial interface. Each E1 card contains two physical 120 Ohm E1 ports. To connect 75 Ohm Network Elements, a 75-120 Ohm Adapter Cable is used. These ports are identified in the Cisco configuration file by <slot number / port number>. For consistency, the first E1 card is inserted in slot 3, the second into slot 4 and so on (we recommend that slots 1 and 2 are reserved for Four Port Serial Interface modules).

Refer to Table 14-1 for information on the recommended slots usage. The port numbers on the E1 card are labeled as CTRLR 0 and CTRLR 1. Please refer to Figure 14-3 for a pictorial view of the channelized E1 module.

Figure 14-3 Two Port Channelized E1 Interface to connect GSM network elements

Table 14-1 Recommended slot usage on the Cisco 3662

Slot Number

Port Type Port Number

Connected System

Cable Type Electrical Spec / Clock

Source

1 Four Port Serial I/F

0 OMC EIA/TIA-449 X.21 / DCE



3 Interconnect RS-530/X21 X.21 / DTE

2 Four Port Serial I/F




3 Interconnect RS-530/X21 X.21 / DTE

3 - 4 Two Port E1 Module

0 GSM NE DB-15 to RJ-45 E1

1 GSM NE DB-15 to RJ-45 E1

5 - 6 Two Port E1 Modules for expansion

GSM NE DB-15 to RJ-45 E1


24 May 2004 68P02901W47-Q 4


NOTE: The Interconnect connections are optional for redundancy or expansion.

Router capacityAny of the six available slots in the 3662 router can host either a Four Port Serial module or a Two Port E1 module. Refer to Table 14-1 for the recommended slot usage.

Two Four Port Serial modules are used for OMC connectivity, leaving the remaining four slots for E1 connections. This is equivalent to eight Vanguard 6560s in E1 timeslots capacity and four Vanguard 6560s in physical E1 connections.

Cables usedDB-[Number] is an indication of the connector type. The number refers to the number of pins in the connector.

Six different cable types are used on the 3662:

DB-60 to DB-37-Female (EIA/TIA – 449 DCE).

Cable connection from the Serial ports in slots 1 & 2 to the OMC HSI.

DB-15 to RJ-45 (Cable for Balanced 120-Ohm).

Cable connection from the E1 modules to the GSM equipment.

120 - 75 Ohm Adapter Cable (RJ – 45 to BNC).

Only necessary for 75 Ohm BSC connections.

DB-60 to DB-25-Male (RS-530 DTE).

Used to inter-connect 3662 router with existing Vanguard 6560 router.

DB-60 to DB-15 (CAB-X21).

Used to inter-connect 3662 router with another 3662 router.

CAT 5 Ethernet cable.

Connection for LAN communications.

Console Cable Kit (supplied by Cisco).

Rollover Console cable.

RJ-45 to DB-9 Adapter.


24 May 2004 68P02901W47-Q 5


Connectivity, configuration and LAN connection

IntroductionThe following are covered in this section:

Prerequisites.

Establishing console connection.

Initial configuration.

Configuring the hostname and passwords.

Connecting and configuring the LAN connections.

PrerequisitesA PC or laptop computer running Windows NT or 2000 is required. The Console roll-over cable and RJ-45 to DB-9 adapter is used in this section.

Establishing console connectionTo establish the console connection, follow this procedure:

1. Plug one end of the Cisco Console cable into the port labelled Console on Slot 0 at the rear of the router.

2. Plug the other end of the cable into the RJ45 port of the DB-9 adapter, and plug the DB-9 connector into the COM serial port of the PC or laptop.

3. On the connected PC or laptop start a Terminal Emulator. In this example, the emulator is HyperTerminal, which comes as standard with Microsoft Windows. To start HyperTerminal, select the following after logging on to the PC or laptop:

Start -> Programs -> Accessories -> [Communications] -> HyperTerminal

The Communications menu is in brackets as it may not be present in all Windows Operating Systems.

The Connection Description dialogue box is displayed.

4. Enter a name and choose an icon from the Connection Description dialogue box. In this example, the name is Cisco 3662. Click on OK to proceed.

The Connect To dialogue box (Figure 14-4) is displayed.


24 May 2004 68P02901W47-Q 6


5. In the Connect To dialogue box (Figure 14-4), expand the options available in the Connect Using field and select the appropriate COM port. Click on OK to proceed.

Figure 14-4 Connect To dialogue box

The COM Properties dialogue box is displayed.


24 May 2004 68P02901W47-Q 7


6. Set the COM Properties dialogue box fields to the values shown in Figure 14-5 and click OK:

Figure 14-5 COM Properties dialogue box

7. HyperTerminal automatically connects to the configured port. The Connected status and time can be seen at the bottom of the HyperTerminal screen. If the status is Disconnected, the port can be reconnected by selecting the following from the menu bar: Call -> Call. The prompt is not seen until the router is turned on in the next step.


24 May 2004 68P02901W47-Q 8


Initial configurationOnce the previous section is complete, perform the initial configuration by following this procedure:

1. Power on the 3662 router.

NOTE: The 3662 router must be physically close to the OMC and Local Area Network to accommodate the length of the cables.

When the Cisco router is first powered on, it goes through the Power On Self Tests (POST). Several messages are displayed on the Console.

Once these have completed successfully, the router looks for an Internetworking Operating System (IOS) to boot. The IOS to boot from can be specified in the configuration file that is stored in the routers non-volatile RAM. However, because this is the first time the router is powered on, the configuration in NVRAM is empty. This causes the router to search for a valid operating system in the flash memory. The first valid IOS that is available in the flash memory is loaded.

Once the IOS has been identified and loaded, the router starts an interactive session with the user to configure the router, and displays this prompt:

Would you like to enter the initial configuration dialog? [yes/no]:no

2. The interactive configuration session is not used when the router is installed. Therefore, please answer no at the above prompt.

NOTE: If you inadvertently choose yes at this point, return to the above prompt by powering the router off and then on again.

The router displays this prompt:

Would you like to terminate autoinstall? [yes]:

3. Press Return to terminate auto install.

The router proceeds to complete the boot up. Several interface state change messages are displayed until the router completes its boot up.

4. Once boot up is complete, press the Return key.

The following prompt is displayed:

Router>

This is the basic user level prompt. At this user level, basic router commands can be used to show interfaces that exist, the IOS version that is running, memory status and other information. The router must be in privilege execution mode to perform any configuration changes.


24 May 2004 68P02901W47-Q 9


5. To enter privilege mode, enter the following command at the Router prompt:

Router> enable

The router prompt changes to the prompt below, signifying that it is now at a level whereby the administrator has full privileges. This is known as the privilege level. Privileged mode includes user mode functionality and provides unrestricted access. It is used exclusively for router configuration, debugging, setting Operating System (OS) parameters, and retrieving detailed router status information.

Router#

The basic router configuration in the next section can now be performed.

Configuring the hostname and passwords The following configuration steps show the commands that need to be entered in bold

text.

Prompts and messages are displayed for indication purposes only.

Text within the <> characters are user-specific.

Setting the hostname

From the privilege prompt that was established at the end of the last section (Router#) perform the following steps:

1. Enter the following command to enter global configuration:

Router# configure terminal

Enter configuration commands, one per line. End with CTRL/Z.

Router(config)#

2. Enter the following command to set the hostname:

Router(config)# hostname <X25-3662>

X25-3662(config)#

NOTE: The hostname X25-3662 is used in the examples throughout this document. Please change this to conform to the network operator’s naming convention. The new hostname is now displayed.


24 May 2004 68P02901W47-Q 10


Setting the passwords

Passwords can be set at three different points of the Cisco configuration:

Console password: Users are prompted for this password when connected directly to the Console port of the router.

Telnet line password: Users are prompted for this password after initiating a telnet session to the router.

Enable password: This password is requested on entering privilege level to configure the router.

NOTE: Console and telnet passwords give user level access to the router. At this level, the operator can use the show commands to view the status of the router. The enable password gives the operator full privileges on the router.

While remaining in global configuration mode from Setting the hostname, perform the following procedure:

1. Enter the following commands to set the console password:

X25-3662(config)# service password-encryption

X25-3662(config)# line console 0

X25-3662(config-line)# password 0 <password>

X25-3662(config-line)# login

X25-3662(config-line)# exit

NOTE: Notice how the router prompt changes to identify the current configuration level. The exit command is used to exit the line configuration mode to return to global configuration.

2. Enter the following commands to set the telnet passwords:

X25-3662(config)# line vty 0 4

X25-3662(config-line)# password 0 <password>

X25-3662(config-line)# login

X25-3662(config-line)# exit

3. Enter the following commands to set the enable password:

X25-3662(config)# enable password 0 <password>

X25-3662(config)# CTRL-z

CTRL-z ends the configuration session and exits the user to the privilege router level. The following message is displayed:

Configured from console by console


24 May 2004 68P02901W47-Q 11


Connecting and configuring the LAN connectionAt this point the Ethernet connection to the Local Area Network (LAN) can be established. Connect the port labelled Ethernet 0/0 at the back of the 3662 to a LAN Hub or switch to which there is a workstation connected. The CAT 5 twisted pair cable is used to establish the physical connection.

NOTE: It is also possible to configure the router through the existing console connection, in which case this procedure can be skipped.

Configuring the LAN connection

From the router privilege prompt, perform the following:

1. Configure the FastEthernet connection by entering the following at the prompt:

X25-3662# configure terminal

X25-3662(config)# interface fastEthernet 0/0

X25-3662(config-if)# ip address <IP Address> <Subnet Mask>

X25-3662(config-if)# no shutdown

X25-3662(config-if)# exit

NOTE: The following message should be seen on the console indicating that the link has come up:

Line protocol on Interface FastEthernet0/0, changed state to up

2. Use the following command to set a default route. This allows the router to communicate with other Local Area Networks. Please refer to the network administrator for these parameters if necessary:

X25-3662(config)# ip route 0.0.0.0 0.0.0.0 <Gateway Address>


X25-3662#

3. Verify that the LAN connection is up by entering the following command:

X25-3662# show interface fastEthernet 0/0

The first line identifies if the Fast Ethernet link is up by displaying the following:

FastEthernet0/0 is up, line protocol is up


24 May 2004 68P02901W47-Q 12


4. A telnet session can now be established to the Cisco 3662 router from a workstation on the same LAN. To establish a telnet session, perform the following from a workstation:

NOTE: Remain connected on the console while testing telnet connectivity from another workstation. This is a safe way to verify that all passwords are set correctly.

telnet <IP Address set in step 1 above>

User Access Verification

Password: <Password set for line vty 0 to 4>

X25-3662> enable

Password: <enable password>

X25-3662#

5. After completing the previous step, all configuration to this point has been verified. The configuration changes made in all previous steps can now be saved to Non-Volatile RAM on the router to make them permanent. Without doing this a router reboot loses all configuration set in previous steps. To save these changes do the following:

X25-3662# write memory

6. The console connection that was established to do the basic router configuration can now be disconnected after exiting.


24 May 2004 68P02901W47-Q 13


Establishing OMC and GSM connections


Configuring X.25 profiles.

Establishing serial connections to the OMC.

Connecting the router to the OMC.

Configuring the serial interfaces to the OMC.

Establishing and configuring connections to the GSM equipment.

Controllers and channel groups.

Creating channel groups.

Configuring the serial interfaces.

Configuring X.25 profilesProfiles are used to configure X.25 parameters that are common to several interfaces. Two profiles are created in this sub-section, one for the OMC and one for the GSM equipment. Further X.25 parameter changes will only need to be changed once within the appropriate profile. These changes will then take effect in all interfaces using this profile.

Perform the following from privilege level to configure the X.25 profiles:

1. To configure the OMC X.25 profile perform the following:


X25-3662(config)# x25 profile OMC dce

X25-3662(config-x25)# no x25 security crcdn

X25-3662(config-x25)# x25 htc 64

X25-3662(config-x25)# lapb T4 4

X25-3662(config-x25)# lapb N2 10

X25-3662(config-x25)# exit

X25-3662(config)#


24 May 2004 68P02901W47-Q 14


2. To configure the GSM X.25 profile perform the following:

X25-3662(config)# x25 profile GSM dce

X25-3662(config-x25)# x25 ltc 1024

X25-3662(config-x25)# x25 htc 1055






NOTE: The default packet size is 128 and window size is 2.

Establishing serial connections to the OMC

The X25_config file

The X.25 configuration file, configured during the OMC-R installation, defines which HSI (High Speed serial Interface) lines are used. The x25_config file is located in the /usr/omc/config/global directory of the OMC-R. Each line in this file contains eleven fields.

These fields are defined in Table 14-2. A sample configuration file for a typical OMC can be seen in Table 14-3.

Table 14-2 Fields in the x25_config file

Field Comments

Record Number This is the sequential record number.

X.25 Channel Number The format is x25_chan<nn>, where nn equates to the record number.

Sunlink X.25 link number For the HSI/S configuration, the link numbers in the x25_config file must correspond to the SunLink X.25 link numbers.

X.121 Address The recommended X.121 address format is as follows:

Digits 1 to 5 relate to Mobile Country Code followed by Mobile Network Code.

Digits 6 to 10 are equipment specific indicators.

Digits 11 and 12 reflect the HSI Card and Port.

Digits 13 and 14 relate to the subnet address of the X.25 process.

Interface Type A value of H relates to SunLink HSI/S.

Process Call Characteristic A value of - relates to a calling process. Any other value in this field relates to a listening process.


24 May 2004 68P02901W47-Q 15


Field Comments

OMC-R Process The type of X.25 application process:

OMC_BL indicates BootloadOMC_EI indicates Event InterfaceOMC_RL indicates Remote LoginOMC_PU indicates Upload

Protocol Set to X25.

Packet Size For example, 128.

Window Size For example, 2.

Time Out Parameter For example, 50 or 500.

Table 14-3 Sample X25_config file for an OMC

1 x25_chan1 0 2020130000061 H g_bootload OMC_BL X25 128 2 50

2 x25_chan2 4 2020130001062 H g_bootload OMC_BL X25 128 2 50

3 x25_chan3 1 2020130000241 H g_ei OMC_EI X25 128 2 500

4 x25_chan4 5 2020130001142 H g_ei OMC_EI X25 128 2 500

5 x25_chan5 1 2020130000200 H - OMC_RL X25 128 2 500

6 x25_chan6 0 2020130001299 H - OMC_PU X25 128 2 50

7 x25_chan7 4 2020130001299 H - OMC_PU X25 128 2 50

8 x25_chan8 2 2020130001299 H - OMC_PU X25 128 2 50

9 x25_chan9 6 2020130001299 H - OMC_PU X25 128 2 50

NOTE: Please refer to the x25_config that is customized to your network.

OMC platforms have two HSI cards. Each HSI card has four serial ports. With two HSI cards, redundancy is built into the X.25 network. Table 14-3 shows which ports (column 3) are defined for each process (column 7). The Upload processes are initiated from the OMC and use links 0, 2, 4 and 6. The Rlogin Process uses link 1. Later in this section there is a procedure for using the Upload and Rlogin HSI ports for Bootload and Event Interface traffic, increasing overall performance and capacity of the X.25 network.


24 May 2004 68P02901W47-Q 16


Connecting the router to the OMCDB-60 to DB-37 (EIA/TIA – 449 DCE) cables are used to make the connection between the router and the OMC. The female ends of the 449 DCE cables are connected to the female HSI connectors using 37-way to 37-way gender changers.

Before making the physical connections between the OMC and router, refer to Table 14-4 to determine the physical port connections at either end.

To complete the physical connections, repeat this procedure for each HSI port used in the x25_config file:

1. Determine the first physical port to be used on the OMC HSI (refer to the third column on the first line of the x25_config file). In this case (from Table 14-3), port 0 is the first port to be used. Connect the DB-37 male gender changer to this port, connect the DB-37 female end of the 449 DCE cable to the other side of the gender changer.

2. Refer to Table 14-4 to identify the corresponding router port. In this case port 0 on the OMC side connects to 1/0 on the router.

3. Connect the DB-60 end of the 449 DCE cable to the appropriate port on the Cisco 3662.

Table 14-4 Physical Port connections at the OMC and Cisco 3662

OMC-R HSI Port Number

Defined in column 3 of the x25_config file

Cisco 3662 {Slot Number/Link Number}

Port 0 Connects to 1/0



Port 3 (Not Used) Connects to 1/3




Port 7 (Not Used) Connects to 2/3


24 May 2004 68P02901W47-Q 17


Configuring the serial interfaces to the OMCEach of the serial interfaces that connect to the OMC has the same configuration. Perform the following from privilege level for each of the interfaces that connect to the OMC:

1. If a telnet session is used to configure the router, enter the following from privilege level:

X25-3662# terminal monitor

This command is used to monitor messages that are displayed on the Console port. Once this command is entered, all Console messages for the period of this telnet session are seen. This is useful to see the interface state changing as they are configured.

2. Enter global configuration mode:


3. Execute these commands for each serial interface that is connected to the OMC. The only parameter change necessary is the physical interface number:

X25-3662(config)# interface serial <slot number/port number>

NOTE: The physical interface number is the same format as shown in Table 14-4. The first interface to be configured is interface 1/0.

X25-3662(config-if)# encapsulation x25 profile OMC

X25-3662(config-if)# clockrate <clock rate>

NOTE: The recommended clock rate for an E3x00 OMC is 256000. The recommended clock rate for a Netra / SunFire OMC is 356000.


NOTE: The following lines should be displayed indicating that the serial line is up:

Interface Serial{Slot # / Port #}, changed state to up

Line protocol on Interface Serial{Slot # / Port #}, changed state to up.


X25-3662(config)#

NOTE: Repeat step 3 for all OMC connected interfaces. Using the x25_config file in Table 14-3 as an example, the following interfaces on the router need to be configured as above:

interface serial 1/0







24 May 2004 68P02901W47-Q 18



24 May 2004 68P02901W47-Q 19


4. Once all interfaces are configured, save the configuration and verify that the interfaces are up by doing the following:

X25-3662(config)#

X25-3662(config)# ^Z


X25-3662# show interface serial <slot number/port number>

The first line of the output indicates that the serial Interface link is up by displaying this message:

Serial1/0 is up, line protocol is up.

Show interface summary

The following command can also be used to identify the link status:

X25-3662# show interface summary

Each line output contains information about one interface. All interfaces that are up have an asterisk (*) displayed to the left of the line. Table 14-5 is an example of the output showing interface states.

Table 14-5 Interface states

Interface IHQ IQD OHQ OQD RXBS RXPS TXBS TXPS TRTL

---------------------------------------------------------------------

* FastEthernet0/0 0 663 0 0 4000 10 3000 3 0

FastEthernet0/1 0 0 0 0 0 0 0 0 0

* Serial1/0 0 0 0 0 0 0 0 0 0

* Serial1/1 0 0 0 0 31000 44 2000 97 0

...

Serial2/3 0 0 0 0 0 0 0 0 0


24 May 2004 68P02901W47-Q 20


Establishing and configuring connections to the GSM equipment

Prerequisites

The number of physical E1 connections required depends on the topology of the GSM network. In this section it is necessary to know the following:

Which GSM network elements need to be connected to the router? The total number of network elements that can be connected to the router depends on the number of channelized E1 cards in the router. Each channelized E1 card has two E1 interfaces and each E1 interface supports 31 DS0 (64K) timeslots.

The type of physical cables to use depends on the GSM Network Elements. These are either 120 Ohm or 75 Ohm. For 75 Ohm Network Elements the 120 - 75 Ohm Adapter Cable is required.

The timeslots to which the NEs are mapped on each E1 connection.

Establishing the connection

The DB-15 to RJ-45 cables are used to connect 120 Ohm GSM Network Elements to the router. The Interface pinouts for the 120 Ohm cable are shown in Table 14-6. To connect 75 Ohm GSM Network Elements to the router, the 120 - 75 Ohm Adapter Cable is required. Connect the RJ-45 plug at the end of the DB-15 to RJ-45 cable to the RJ-45 socket on the 120 - 75 Ohm Adapter Cable.

Make all the necessary connections, taking note of which GSM Network Element is connected to which physical E1 port. Once a proper connection has been established, the Local Alarm light on the physical E1 interface should disappear and the Carrier Detect light should go green. The E1 port numbers follow the same numbering scheme as the serial ports that connect to the OMC with the exception that there are only two ports. Once all physical connections have been established, the interfaces to the Network Elements can be created.

Table 14-6 DB-15 to RJ-45 120 Ohm cable Pinouts

2 Port Channelized E1 End Network End

DB-15 RJ-45

Pin Signal Pin Signal

9 Tx Tip 1 Tx Tip

2 Tx Ring 2 Tx Ring

10 Tx Shield 3 Tx Shield

8 Rx Tip 4 Rx Tip

15 Rx Ring 5 Rx Ring

7 Rx Shield 6 Rx Shield


24 May 2004 68P02901W47-Q 21


Controllers and channel groupsEach physical E1 interface is logically created on the Cisco 3662 as a controller. Each controller has 31 64K timeslots available to it. In this section, multiple channel groups are created within each controller (one channel group per NE). The purpose of the channel group is to define the associated timeslot(s). Table 14-7 summarizes the steps taken to create connections to the NE.

NOTE: Use Table 14-7 for reference purposes only.

To view the controllers that exist on the Cisco 3662, use the following command from privilege level:

X25-3662# show running-config

Following is excerpt from a sample configuration file showing two controllers, the first controller is port 0 in slot 3 of the router, and the second is port one in slot 3:

controller E1 3/0

!

controller E1 3/1

Press the space bar to page through the rest of the running configuration file.

Table 14-7 Sequence of steps to create serial interfaces

Step Command reference(do not execute)

Purpose

1 controller E1 <slot number/port number>

To enter the controller to be configured. The prompt changes to reflect the new configuration level.

2 channel group <channel #> timeslots <timeslot number(s)>

A separate channel group is required for every NE that is connected to this controller.

It is possible to allocate several timeslots to one channel group. However, only one 64K timeslot is allocated to each NE.

<channel #> starts at 0 and continues to 30. <timeslot number(s)> starts at 1 and continues to 31.

The fist channel group that we create uses channel # 0 and timeslots 1, the second uses channel # 1 and timeslots 2 and so on (timeslots 2 refers to timeslot 2, not 2 timeslots).

Each channel group created automatically creates a serial interface. This interface is configured in a later step for the X.25 profile created for GSM.

3 exit This step exits controller configuration level and return to global configuration mode. At this


24 May 2004 68P02901W47-Q 22


Step Command reference(do not execute)

Purpose

point step 1 and 2 can be repeated to create channel groups in other controllers.

4 interface serial <port number / slot number: channel #>

To enter the serial interface created from the associated channel group.

<port number / slot number> indicates the controller (physical E1 port)

<:channel #> indicated the channel group.

5 encapsulation x25 profile GSM

This step configures the serial interface to use the GSM profile created at the start of this section.

6 exit This step exits serial configuration level and return to global configuration mode. At this point step 4 can be repeated to configure other serial interfaces.

Creating channel groupsUse the following steps to create the channel groups in the controllers. These in turn automatically create the serial interfaces which tie into the appropriate timeslot.



2. Enter the appropriate controller:

X25-3662(config)# controller E1 <slot number/port number>

NOTE: For example, the first available controller is typically 3/0, assuming the E1 Interface resides in slot 3. The following command is used:

controller E1 3/0

By default CRC4 framing is turned on. To turn CRC4 framing off, use the following command inside the controller:

framing no-crc4


24 May 2004 68P02901W47-Q 23


3. Create the channel group:

X25-3662(config-controller)#channel group <channel #> timeslots <timeslot number(s)>

NOTE: Timeslot numbering starts at 1 for timeslot 1 and work up to 31 for timeslot 31. Channel # is always one less than the timeslot number. For example, to configure the first three timeslots the following needs to be entered in step 3:

channel group 0 timeslots 1



To configure all timeslots in the controller, continue to:


Motorola recommends that you only create channel groups for timeslots being used, that is, for connected NEs.

For further information on this command refer to Table 14-7.

As the interfaces are created, the following message is displayed for each Serial Interface created:

Line protocol on Interface Serial{port number/slot number:channel #}, changed state to down

Repeat step 3 for all timeslots in this controller.

4. Exit Controller:

X25-3662(config-controller)# exit

5. To create further channel groups (serial interfaces) on other controllers repeat steps 2 through 4. Once all of the necessary channel groups have been created do the following:




24 May 2004 68P02901W47-Q 24


6. To verify that the channel groups have been established within the controller and that the serial interfaces have been created in the configuration file, do the following:

X25-3662# show running-config

NOTE: The channel groups configured in the previous Note have the following serial interfaces created in the configuration file (assuming that controller 3/0 was used):

The Channel number is the timeslot number minus 1.

interface Serial3/0:0 (For Timeslot 1)

no ip address

!


no ip address

!


no ip address etc…

Configuring the serial interfaces (to the GSM Network Elements)Each serial interface just created needs to be configured to use the GSM X.25 profile created at the start of this section. Perform the following from privilege level.



2. Use the following commands to configure the encapsulation on the serial interface:

X25-3662(config)# interface serial <port number / slot number:channel #>

NOTE: The channel number is the timeslot number minus 1.

X25-3662(config-if)# encapsulation x25 profile GSM


3. Repeat step 2 for all serial interfaces created. Once all interfaces are configured, save the configuration and verify that the interfaces are up by using the following commands:

X25-3662(config)#



X25-3662# show interface serial <slot number/port number:channel #>

Refer to Figure 14-6 for sample output of this command. The first line of the output indicates that the serial Interface is up with this message:

Serial3/0:0 is up, line protocol is up

The last line identifies the timeslot being used.


24 May 2004 68P02901W47-Q 25


Figure 14-6 Show interface serial <slot number/port number:channel #> O/P

X25-3662#show interfaces serial 3/0:0

Serial3/0:0 is up, line protocol is up

Hardware is DSX1

MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation X25, loopback not set

X.25 DCE, address <none>, state R1, modulo 8, timer 0

Defaults: idle VC timeout 0

cisco encapsulation

input/output window sizes 2/2, packet sizes 128/128

Timers: T10 60, T11 180, T12 60, T13 60

Channels: Incoming-only none, Two-way 1024-1055, Outgoing-only none

RESTARTs 0/0 CALLs 0+0/0+0/0+0 DIAGs 0/0

LAPB DCE, state CONNECT, modulo 8, k 7, N1 12056, N2 10

T1 3000, T2 0, interface outage (partial T3) 0, T4 4

VS 3, VR 4, tx NR 4, Remote VR 3, Retransmissions 0

Queues: U/S frames 0, I frames 0, unack. 0, reTx 0

IFRAMEs 0/0 RNRs 0/0 REJs 0/0 SABM/Es 0/0 FRMRs 0/0 DISCs 0/0

Last input never, output 00:00:02, output hang never

Last clearing of "show interface" counters 00:00:08

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

2 packets input, 4 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

2 packets output, 4 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions

Timeslot(s) Used:1, Transmitter delay is 0 flags

X25-3662#


24 May 2004 68P02901W47-Q 26


Show interface summary

The following command can also be used to identify the link status

X25-3662# show interface summary

Each line output contains information about one interface. All interfaces that are up have an asterisk (*) displayed to the left of the line. Use the space bar to page through the output.


24 May 2004 68P02901W47-Q 27


Enabling X.25 routing and creating Hunt Groups

IntroductionX.25 routing is enabled on the 3662 router to allow Virtual Circuits to be routed from one serial interface to another.

Once X.25 routing has been enabled, the X.25 routes can be created. X.25 routes are created in the next section.

Hunt Groups are used as a method of load balancing across several serial links. In this section Hunt Groups are created to load balance the NE Virtual Circuits across the serial interfaces that connect the OMC.

Enabling X.25 routingTo enable X.25 routing, do the following from privilege level on the 3662 router:



2. Enable X.25 routing by entering the following:

X25-3662(config)# x25 routing

3. Save the configuration:




24 May 2004 68P02901W47-Q 28


Creating X.25 Hunt GroupsTwo Hunt Groups are created for load sharing the serial connections to the OMC.

BOOTLOAD: This Hunt Group shares the serial connections that are used for bootload. For example, if six NEs are bootloading at the same time, they are evenly distributed across all interfaces that are defined in this Hunt Group.

EVENTS: This Hunt Group shares the serial connections that are defined for event interface.

There are two types of Hunt Group available, vc-count and rotary. Motorola recommends the use of vc-count, as this method sends calls to the interface that has the largest number of available logical channels. This method ensures a good load balance when lines are of equal speed.

At least two serial interfaces participate in each of these Hunt Groups. This is because two lines in the x25_config file are defined for Bootload (lines 1 and 2) and two lines are defined for Event Interface (3 and 4). However, because the OMC can route Bootload and Event data to the correct process from any of the HSI ports, all of the connected serial lines (that connect to the OMC) can participate in each Hunt Group.

NOTE: If any of the serial interfaces participating in the Hunt Group are down or not connected, the interface shows as being unavailable in the Hunt Group upon entering the command show x25hunt-group.


24 May 2004 68P02901W47-Q 29


Creating the BOOTLOAD Hunt GroupSerial 1/0 and Serial 2/0 are the two bootload channels defined in the x25_config example in Table 14-3 (column 6 in the x25_config file defined the process, g_bootload for BOOTLOAD and g_ei for EVENTS). Refer to the x25_config file on the live OMC to determine these ports. Minimally, the two ports defined for g_bootload participate in the BOOTLOAD Hunt Group. However, Motorola recommends that all serial connections to the OMC are included in the Hunt Group, making better use of the serial interfaces, increasing redundancy and capacity.

For example, if the two g_bootload serial lines are disconnected, the Network Element can still bootload from one of the other available lines participating in the Hunt Group.

Perform the following steps from privilege level to create the BOOTLOAD Hunt Group:



2. Create the Hunt Group:

X25-3662(config)# x25 hunt-group BOOTLOAD vc-count

X25-3662(config-x25-huntgroup)# interface serial <slot number / port number>

NOTE: Repeat the last command for all serial interfaces participating in

the Hunt Group.

The following ports participate in the Hunt Group for a typical

OMC-R: 1/0, 1/1, 1/2, 2/0, 2/1, 2/2.

3. Exit global configuration mode:

X25-3662(config-x25-huntgroup)# exit


24 May 2004 68P02901W47-Q 30


Creating the EVENTS Hunt GroupSerial 1/1 and Serial 2/1 are the two event channels in the x25_config example in Table 14-3. Refer to x25_config file on the live OMC to determine these ports. Minimally, these two ports participate in the EVENT Hunt Group. Motorola recommends that all serial connections to the OMC are included in the Hunt Group, making better use of the serial interfaces, increasing redundancy and capacity.

Perform the following steps from privilege level to create the EVENTS Hunt Group:


X25-3662(config)# x25 hunt-group EVENTS vc-count

X25-3662(config-x25-huntgroup)# interface serial <slot number / port number

NOTE: Repeat the last command for all serial interfaces participating in

the Hunt Group.

The following ports participate in the Hunt Group for a typical

OMC-R: 1/0, 1/1, 1/2, 2/0, 2/1, 2/2.

X25-3662(config-x25-huntgroup)# exit





24 May 2004 68P02901W47-Q 31


Verifying the X.25 Hunt GroupsMake sure that the Hunt Groups have been created properly by using the following command:

X25-3662# show x25 hunt-group

The output displays information about each Hunt Group. Using Figure 14-7 as an example, we can see that four NEs have EVENT connections each using a different serial connection back to the OMC platform, and no BSSs are BOOTLOADING (notice the 0 uses):

Figure 14-7 X.25 Hunt Groups example

X25-3662#sh x25 hunt

ID Type Target uses status traffic(out/in)

===========================================================================

BOOTLOAD vc-count Serial1/0 0 1 VC 280555/370

Serial2/0 0 1 VC 2657/132

Serial1/1 0 1 VC 7862/197

Serial2/1 0 1 VC 2651/132

Serial1/2 0 0 VC 0/0


EVENTS vc-count Serial1/1 1 1 VC 7862/197

Serial2/1 1 1 VC 2651/132

Serial1/0 1 1 VC 280555/370

Serial2/0 1 1 VC 2657/132



X25-3662#


24 May 2004 68P02901W47-Q 32


Creating X.25 routes

IntroductionIn this section the X.25 routing table is created. When the 3662 router receives an X.25 call that must be forwarded, the X.25 routing table determines which destination to use. The routing table is scanned sequentially from top to bottom and the first route that matches the address criteria is used for the X.25 call. The user determines the order of the routing table when entering new routes. This way the user can control which routes should take precedence when creating secondary or redundant links (that is, dual OMLs to the BSS).

X.121 addressesIn this section it is important to know the addresses being used and the port-timeslot that they are associated with. These addresses are referred to as X.121 addresses. An X.121 address is assigned to each Network Element and each channel on the OMC. The X.121 address for the OMC is defined in the x25_config file (column 4) and can be identified on the GSM NEs by using the disp_dte command at the NE MMI prompt. The address is displayed in the NE DTE addresses section. X.121 addresses are typically 14 digits in length.

An example of an addressing scheme is:

aaannddceehhxx

Where: Is:

aaa the country code

nn the network code

dd the location code

c the type code:

1 – BSS (EEHH = BSS Number), (XX should be 00)

2 – RXCDR

3 – OMC

ee the number of the OMC-R

hh the HSI card and port number

xx the function sub-address:

41 & 42 – Event Interface

61 & 62 – Boot Loader

00 – Rlogin

99 – Uploader


24 May 2004 68P02901W47-Q 33


Adding routes into the routing tableFollow these steps to create the routing table on the router:

The routes that use the Hunt Groups are established.

The routes to the GSM equipment are established.

The remaining routes are established to the OMC or Vanguard (that do not use Hunt Groups or timeslots).

The optional position parameter allows the user to define the position of a route in the routing tables.

The routing table is scanned from top to bottom, hence the first matching address is used to establish virtual connections. If this connection fails the next route that matches the address criteria is used. If the position option is not used, then by default the first route added would be in position 1, the next route would take position 2 and so forth.

NOTE: Optional parameters are in brackets [ ].

Creating routes to the OMCThe following commands set the routes to the OMC using the BOOTLOAD and EVENTS Hunt Groups created in the last section. Refer to the x25_conf file for the x.121 addresses:



2. Add the route:

X25-3662(config)# x25 route [# position] <X.121 address> hunt-group <Hunt Group Name>

NOTE: The following is an example of the routes that would be necessary if using the x25_config file in Table 14-3 and the Hunt Groups created in the last section:

X25 route 2020130000061 hunt-group BOOTLOAD

X25 route 2020130001062 hunt-group BOOTLOAD

X25 route 2020130000241 hunt-group EVENTS

X25 route 2020130001142 hunt-group EVENTS

3. Repeat step two for all Hunt Group routes. To return to privilege level, type the following:

X25-3662(config)#exit


24 May 2004 68P02901W47-Q 34


Creating routes to the GSM equipmentTo create routes to the GSM equipment, perform the following:



2. Repeat this command for all routes to the NE equipment, including secondary OMLs:

X25-3662(config)# x25 route [# position] <X.121 address> interface serial <slot number/port number:channel #>

NOTE: The channel # is only necessary when connecting to GSM network elements on the E1 lines. In the following example, the primary OML is routed out of timeslot 6 (channel 5) on controller 3/1. The secondary OML is routed out of timeslot 6 on controller 4/1.

X25 route 41503002010000 interface serial 3/1:5

X25 route 41503002010000 interface serial 4/1:5

Remaining routes to be createdOther routes may need to be created when interconnecting Vanguard 6560s. To add further routes to the routing table, perform the following:



2. Repeat this command for each route that is required:

X25-3662(config)# x25 route [# position] <X.121 address> interface serial <Slot Number/Port Number>

Or, where Hunt Groups have been created to load-share across multiple connections back to the Vanguard, use the following syntax:

X25-3662(config)# x25 route [# position] <X.121 address> hunt-group <Hunt Group Name>

Saving the ConfigurationOnce all routes have been created, exit and save the configuration by doing the following:




24 May 2004 68P02901W47-Q 35


Verifying the routesTo verify that the routes have been established, use the following command from privilege level:

X25-3662# show x25 route

Please refer to the commands in the later section Useful Cisco commands to verify that the X.25 network is up.


24 May 2004 68P02901W47-Q 36


Integration with the existing Vanguard 6560 router

IntroductionThis section explains how to integrate the Cisco 3662 router with the Vanguard 6560 packet switch. This may be necessary for expansion. For example, if the Vanguard 6560 X.25 network has reached its E1 timeslot limit for connecting GSM network elements, the Cisco 3662 can be connected to give further E1 capacity. The following are covered in this section:

Creating an X.25 profile for the serial interfaces that connect to the 6560.

Configuring the necessary serial interfaces to use this profile.

Configuring the X.25 port of the Vanguard 6560.

Making the connection.

Enabling X.25 routing.

Creating the x25 routes.

It is necessary to have a console (or PAD) connection to the Vanguard(s) being used. Port number 2 on the Vanguard 6560 is used to connect the Cisco 3662. This port should be an unused X.21 DCE port. If port 2 on the Vanguard 6560 does not have a DCE X.21 DIMM, please contact CNRC. Please refer to the 6560 Installation chapter for further information on this port and establishing a console connection.

If the only purpose of the Cisco 3662 router is to integrate with the Vanguard, please ensure that the following sections have been completed:

The Cisco 3662 router

Connectivity, configuration and LAN connection

Once the Cisco has been integrated with the Vanguard (this section), the following sections can be completed:

Establishing OMC and GSM connections (for the GSM parts)

Creating routes to the GSM equipment


24 May 2004 68P02901W47-Q 37


Creating an X.25 profile for the serial interfaces that connect to the 6560Follow these steps to create the profile used on the connection to the Vanguard 6560:

1. Enter global configuration mode from the privilege level:


2. Create the X.25 profile:

X25-3662(config)# x25 profile CODEX dte

X25-3662(config-x25)# x25 htc 256






Please refer to the section Establishing OMC and GSM connections for further information on X.25 profiles.


24 May 2004 68P02901W47-Q 38


Configuring the necessary serial interfaces to use this profileDetermine the number of serial connections being made between the Cisco and the Vanguard. Two serial interfaces can be used for redundancy. This number of serial connections needs to be available on the Cisco serial interfaces. Figure 14-8 gives an example of the possible connections between the Cisco 3662 and two Vanguards.

Figure 14-8 Cisco 3662 connected to two Vanguards


24 May 2004 68P02901W47-Q 39

HSI 0 0

1

2

3

HSI 0 4

5

6

7

E3X00

6560 3

7

8

1

6560 3

7

8

1

6560 3

7

8

1

6560 3

7

8

1

2

2

2

2

Cisco 3662

E1 Cards for Expansion

2/3 2/2 2/1 2/0 1/3 1/2 1/1 1/0

Serial Interface 2 Serial Interface 1


Configuration procedure

Complete the following steps to configure the interfaces on the Cisco 3662 that connect to the Vanguard(s):

1. From the privilege level, enter global configuration mode:


2. Repeat these commands for each serial interface that is connected to the Vanguard 6560. The only parameter change necessary is the physical interface number:

X25-3662(config)# interface serial <slot number/port number>

NOTE: The physical interface number is the same format as shown in Table 14-4.

X25-3662(config-if)# encapsulation x25 profile CODEX



X25-3662(config)#

NOTE: Repeat step 2 for all Vanguard connected interfaces.

3. Once all interfaces are configured, save the configuration by doing the following:

X25-3662(config)#



Configuring the X.25 port of the Vanguard 6560A login session to the Vanguard 6560 must be established before proceeding. It is necessary to have the password to the Vanguard.

Once you have logged in, perform the following steps to configure port 2:

1. From the Main Menu type 6 and press Enter to display the Configure Menu.

2. From the Configure Menu type 2 and press Enter to display the prompt for the Port Number.

3. Enter Port Number 2 and press Enter.

4. Modify the port settings to match the following settings, using the Enter key to step forward and the Delete key to step back if necessary:

[2] *Port Type: X25/

[2] Connection Type: SIMP/

[2] Port Control: NONE/

[2] Clock Source: INT/

[2] Clock Speed: 2048000/

[2] Invert TX Clock: NO/

[2] Link Address: DCE/


24 May 2004 68P02901W47-Q 40


[2] *Number of PVC Channels: 0/

[2] *Starting PVC Channel Number: 1/

[2] *Number of Two Way SVC Channels: 256/

[2] *Starting Two Way SVC Channel Number: 1/

[2] *Number of One Way Incoming SVC Channels: 0/

[2] *Starting One Way Incoming SVC Channel Number: 1/

[2] *Number of One Way Outgoing SVC Channels: 0/

[2] *Starting One Way Outgoing SVC Channel Number: 1/

[2] Initial Frame: SABM/

[2] T1 Transmission Retry Timer (1/10 sec): 30/

[2] T4 Poll Timer: 40/

[2] N2 Transmission Tries: 10/

[2] Frame Sequence Counting: NORM/

[2] K Frame Window: 7/

[2] Packet Sequence Counting: NORM/

[2] W Packet Window: 2/

[2] P Packet Size: 128/

[2] Maximum Negotiated Packet Size: 1024/

[2] Data Queue Upper Threshold: 5/

[2] Data Queue Lower Threshold: 0/

[2] Restart Timer: 180/

[2] Reset Timer: 180/

[2] Call Timer: 200/

[2] Clear Timer: 180/

[2] Facilities to delete from Outbound Calls: NONE/

[2] Facilities to add to Outbound Calls: NONE/

[2] Facilities to bar in Outbound Calls: NONE/

[2] Facilities to bar in Inbound Calls: NONE/

[2] X.25 Options: CAUSE/

[2] Number of Routing Digits in Call User Data: 5/

[2] Number of prefix Address Digits stripped from Outgoing Calls: 0/

[2] Number of prefix Address Digits stripped from Incoming Calls: 0/

[2] Restricted Connection Destination: (blank)/

[2] Port Address: (blank)/

[2] CUG Membership: --,--,--,--,--,--,--,--/

[2] Billing Records: OFF/

[2] Number of Subaddress Digits in X.25 Address: 2/

[2] Idle Disconnect Timer (sec): 0/


24 May 2004 68P02901W47-Q 41


[2] Call Security: DISABLE/

[2] *Protection Level: NONE/

[2] Reconnection Timeout: 2/

[2] Reconnection Tries Limit: 4/

[2] Facility Subscription Control: NONE/

[2] Alarm Priority: NETWORK/

[2] Charging Information Subscription Control: /

[2] NUI Verification Timer: 10/

[2] Max NUI Violations : 0/

[2] Action Type for NUI Violations: NONE/

[2] Line Idle Mode: FLAG/

[2] Address Translation Options: NONE/

[2] Conformance Control Options: NONE/

5. Press ; to save the new port settings and return to the Main Menu by pressing the Escape key twice.

6. Press 7 to enter the Boot Menu.

7. Select 4 to Warm Boot the Vanguard.

NOTE: This causes the Vanguard to reboot.

Making the connectionThe DB-60 to DB-25 cable is used to connect the Cisco router to the Vanguard 6560. Follow this procedure:

1. Connect the DB-60 end of the cable into the serial port configured to use the CODEX X.25 profile on the Cisco 3662.

2. Plug the DB-25 end into port 2 on the appropriate Vanguard 6560.

Once this connection is established, the port should change its status to “up” on the Cisco3662.

3. Use the following command to verify that the link is up:

X25-3662# show interface serial <slot number/portnumber>

The first line identifies if the serial Interface link is up, that is: Serial1/3 is up, line protocol is up.

If there is a second connection, repeat this step.


24 May 2004 68P02901W47-Q 42


Enabling X.25 routingFor further information on X.25 routing please refer to the section Enabling X.25 routing and creating Hunt Groups. If X.25 routing has not already been enabled, do the following from privilege level on the 3662 router:



2. Enable X.25 routing by entering the following:

X25-3662(config)# x25 routing




Creating the X.25 routesAll new connections to the Cisco 3662 require routing table updates to both the Cisco routing table and Vanguard 6560 routing tables.

To add new routes to the Cisco 3662, refer to the Creating X.25 routes section. Routes must be added for any NE being connected to the Cisco 3662, and for the OMC that is connected to the Vanguards. If two ports on the Cisco 3662 are connected to two different Vanguards (for redundancy) a Hunt Group may be created to share the traffic over the two links. Please refer to the section Creating X.25 Hunt Groups for information on creating Hunt Groups. A Hunt Group could be created with a Hunt Group name “codex” and participating interfaces 1/3 and 2/3.

New routes are also required on the Vanguard 6560. Motorola recommends using a different Location Code (dd) on the NE DTE addresses that are directly connected to the Cisco router. This way, only one route needs to be added to each of the Vanguards. The following is an example route that would be added to an interconnected Vanguard:

[xx]aaanndd,x25-2,1,x25-3,15,x25-1,15…


24 May 2004 68P02901W47-Q 43


Useful Cisco commands


Useful Cisco Commands:

Router level commands.

Interface commands.

X25 Commands to verify the X.25 network.

Backup and restore configuration.

Making changes to the Cisco configuration:

Deleting routes.

Deleting channel groups.

Useful Cisco operating system commands

Router level commands

The following commands can be typed from the privilege level to view the status of the 3662 router. To get a full list of commands available, use the ? key. For example, the command show ? displays all show options available:

To display the current live configuration in running memory:

show running-config

To display the configuration in NVRAM :

show startup-config

To copy the current live configuration from running memory to NVRAM:

write memory

To display the operating system version that is running:

show version

This command also displays:

The number of serial interfaces configured.

System up time.

Amount of NVRAM and Flash available.

To display the CPU utilization:

show processes

To set the date and time:

clock set <HH:MM:SS DD MONTH YYYY>

To show the date and time:


24 May 2004 68P02901W47-Q 44


show clock

To clear all interface counters:

clear counter all

To show the contents of Flash:

show flash all

This command also shows the free space on Flash.

Interface commands

The following commands are useful to view the status of the 3662 interfaces.

To show the Interface status and characteristics:

show interface <slot number/port number<:channel number>>

This command also displays:

X25 characteristics.

Encapsulation Type.

To show interface summary information, including status:

show interface summary

To show the controller information:

show controller

This command is useful for identifying the line framing and coding. It also displays:

Link Speed.

Physical connection type.

Framing Error counts.

X25 commands

The following commands are useful to verify and monitor the X.25 network:

To show routing tables and usage:

show x25 route [| include <string>]

To show number of Virtual Circuits established:

show x25 services

To show Virtual Circuits that have been established:

show x25 vc [| include <string>]

This command also shows window size and packet size.

NOTE: The [include <string>] option can be used to search for text within the output. This is useful as there are typically pages of output. For example, you could use the following command to view all upload virtual circuits currently active:

show x25 vc | include 2020130000061


24 May 2004 68P02901W47-Q 45


Backup and restore configuration

To back up the running configuration on the Cisco router to a tftp server, perform the following:

copy running-config tftp:

Enter address of the tftp server when prompted

Enter destination filename when prompted.

NOTE: Depending on the setup of the tftp server, you may need to:

Create this file (as a blank file) with appropriate permissions on the tftp server.

Enter the full path at the Cisco prompt (This depends on the root directory set on the tftp server).

To restore the running configuration from a tftp server, perform the following:

copy tftp running-config:

Enter address of the tftp server when prompted.

Enter full path and filename when prompted.

Making changes to the Cisco configuration

Deleting routes

Use the following command to delete a route from the running configuration:

X25-3662(config)# no x25 route [ # position ] <X.121 address> interface serial <Slot Number / Port Number>

OR

X25-3662(config)# no x25 route [ # position ] <X.121 address> hunt-group <Hunt Group Name>

NOTE: To delete a route that was previously added, put no before the command that was previously used to add the route while in global configuration mode.

Deleting channel groups

Use the following commands to delete a channel group:

X25-3662(config)# controller E1 <slot number/port number>

X25-3662(config-controller)# no channel group <channel #> timeslots <timeslot number(s)>


24 May 2004 68P02901W47-Q 46

Cisco 3662 Installation

Documents

Transcript of Cisco 3662 Installation