Академический Документы
Профессиональный Документы
Культура Документы
GSR7
GSR7
Prerequisites
A 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.
GSR7
The router
The 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
GSR7
Table 14-1 Recommended slot usage on the Cisco 3662 Slot Number 1 Port Type Port Number 0 1 2 3 2 Four Port Serial I/F 0 1 2 3 3-4 Two Port E1 Module 0 1 5-6 Two Port E1 Modules for expansion NOTE: Connected System OMC OMC OMC Interconnect OMC OMC OMC Interconnect GSM NE GSM NE GSM NE Cable Type Electrical Spec / Clock Source X.21 / DCE X.21 / DCE X.21 / DCE X.21 / DTE X.21 / DCE X.21 / DCE X.21 / DCE X.21 / DTE E1 E1 E1
EIA/TIA-449 EIA/TIA-449 EIA/TIA-449 RS-530/X21 EIA/TIA-449 EIA/TIA-449 EIA/TIA-449 RS-530/X21 DB-15 to RJ-45 DB-15 to RJ-45 DB-15 to RJ-45
24 May 2004
68P02901W47-Q
GSR7
expansion.
Router capacity
Any 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 used
DB-[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.
Console Cable Kit (supplied by Cisco). Rollover Console cable. RJ-45 to DB-9 Adapter.
GSR7
Prerequisites
A 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.
GSR7
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
GSR7
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.
GSR7
Initial configuration
Once 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.
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.
GSR7
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.
2.
NOTE:
The hostname X25-3662 is used in the examples throughout this document. Please change this to conform to the network operators naming convention. The new hostname is now displayed.
GSR7
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.
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
GSR7
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 X25-3662(config)# CTRL-z X25-3662#
The first line identifies if the Fast Ethernet link is up by displaying the following:
FastEthernet0/0 is up, line protocol is up
GSR7
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.
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.
GSR7
GSR7
CTRL-z
NOTE:
X.121 Address
GSR7
Field
Comments OMC_BL indicates Bootload OMC_EI indicates Event Interface OMC_RL indicates Remote Login OMC_PU indicates Upload
Set to X25. For example, 128. For example, 2. For example, 50 or 500. Table 14-3 Sample X25_config file for an OMC
1 2 3 4 5 6 7 8 9
x25_chan1 x25_chan2 x25_chan3 x25_chan4 x25_chan5 x25_chan6 x25_chan7 x25_chan8 x25_chan9 NOTE:
0 4 1 5 1 0 4 2 6
H H H H H H H H H
2 2 2 2 2 2 2 2 2
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.
GSR7
GSR7
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:
X25-3662# configure terminal
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.
NOTE:
The recommended clock rate for an E3x00 OMC is 256000. The recommended clock rate for a Netra / SunFire OMC is 356000. 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-if)# no shutdown
NOTE:
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 interface serial 1/1 interface serial 1/2 interface serial 2/0 interface serial 2/1 interface serial 2/2
GSR7
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)# X25-3662#
^Z
write memory
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.
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 * FastEthernet0/0 FastEthernet0/1 * Serial1/0 * Serial1/1 ... Serial2/3 0 0 0 0 0 0 0 0 0 IHQ 0 0 0 0 IQD OHQ 663 0 0 0 0 0 0 0 OQD RXBS RXPS 0 0 0 4000 0 0 TXBS TXPS TRTL 10 0 0 44 3000 0 0 2000 3 0 0 97 0 0 0 0
---------------------------------------------------------------------
0 31000
GSR7
GSR7
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 1 Command reference (do not execute) controller E1 <slot number/port number> channel group <channel #> timeslots <timeslot number(s)> Purpose To enter the controller to be configured. The prompt changes to reflect the new configuration level. 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 point step 1 and 2 can be repeated to create channel
Installation & Configuration:OMC-R Clean Install 24 May 2004 68P02901W47-Q 21
GSR7
Step
Command reference (do not execute) 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. This step configures the serial interface to use the GSM profile created at the start of this section. 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.
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
GSR7
<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 channel group 1 timeslots 2 channel group 2 timeslots 3 To configure all timeslots in the controller, continue to: channel group 30 timeslots 31 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
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:
X25-3662(config)#
^Z
GSR7
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 no ip address ! interface Serial3/0:1 no ip address ! interface Serial3/0:2 no ip address etc
(For Timeslot 1)
(For Timeslot 2)
(For Timeslot 3)
2. Use the following commands to configure the encapsulation on the serial interface:
X25-3662(config)#
number:channel #> NOTE: The channel number is the timeslot number minus 1. encapsulation x25 profile GSM exit
X25-3662(config-if)# X25-3662(config-if)#
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(config)# X25-3662#
^Z
write memory
#> 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
GSR7
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#
GSR7
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.
GSR7
^Z
GSR7
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 x25huntgroup.
GSR7
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
GSR7
vc-count
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
^Z
write memory
GSR7
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 traffic(out/in) BOOTLOAD vc-count Target uses status
=========================================================================== Serial1/0 Serial2/0 Serial1/1 Serial2/1 Serial1/2 Serial2/2 0 0 0 0 0 0 1 VC 1 VC 1 VC 1 VC 0 VC 0 VC 280555/370 2657/132 7862/197 2651/132 0/0 0/0
EVENTS
vc-count
1 1 1 1 0 0
1 VC 1 VC 1 VC 1 VC 0 VC 0 VC
X25-3662#
GSR7
X.121 addresses
In 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: aaa nn dd c Is: the country code the network code the location code the type code: 1 BSS (EEHH = BSS Number), (XX should be 00) 2 RXCDR 3 OMC ee hh xx the number of the OMC-R the HSI card and port number the function sub-address: 41 & 42 Event Interface 61 & 62 Boot Loader 00 Rlogin 99 Uploader
GSR7
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 [ ].
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
GSR7
2. Repeat this command for all routes to the NE equipment, including secondary OMLs:
X25-3662(config)# x25 route [# position] <X.121 address> interface
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
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-
^Z
GSR7
Please refer to the commands in the later section Useful Cisco commands to verify that the X.25 network is up.
GSR7
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
GSR7
Creating an X.25 profile for the serial interfaces that connect to the 6560
Follow these steps to create the profile used on the connection to the Vanguard 6560: 1. Enter global configuration mode from the privilege level:
X25-3662# configure terminal
^Z
Please refer to the section Establishing OMC and GSM connections for further information on X.25 profiles.
GSR7
6560 7 8 2
3 Cisco 3662 1
6560 7 8 2
6560 7 8 2
6560 7 8 2
GSR7
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:
X25-3662# configure terminal
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-if)# no shutdown X25-3662(config-if)# exit X25-3662(config)#
NOTE:
3. Once all interfaces are configured, save the configuration by doing the following:
X25-3662(config)# X25-3662(config)# X25-3662#
^Z
write memory
GSR7
[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/ Installation & Configuration:OMC-R Clean Install 24 May 2004 68P02901W47-Q 40
GSR7
[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.
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.
GSR7
^Z
write memory
GSR7
Making changes to the Cisco configuration: Deleting routes. Deleting channel groups.
To display the CPU utilization: show processes To set the date and time: clock set <HH:MM:SS DD MONTH YYYY>
Installation & Configuration:OMC-R Clean Install
24 May 2004
68P02901W47-Q
43
GSR7
To show the date and time: 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:
Installation & Configuration:OMC-R Clean Install 24 May 2004 68P02901W47-Q 44
GSR7
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.
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.
<timeslot number(s)>