|
|
After you have rack mounted the ESP and connected the power, you must connect the physical interfaces to it and do an initial configuration. The interface connections involve connecting the ESP to the BPX 8620 switch, the MGX 8220, and the StrataView Plus workstation. The initial configuration involves configuring the ESP to operate as part of a WAN Switching Node, but does not involve using the ESP Configuration Interface to configure ATM or Frame Relay SVCs or SPVCs. (Using the ESP Configuration Interface and configuring ATM or Frame Relay SVCs and SPVCs is covered in Chapters 8 and 9.)
This chapter contains the following sections:
The ESP interfaces, which are shown in Figure 7-1, are:
Figure 7-2 shows the location of the connectors for the ESP physical interfaces. Although only an ESP-AC model is shown in Figure 6-2, the connectors will be in the same location on a ESP-DC Model.
You can attach a terminal (or PC running a terminal emulation program, such as, ProComm) to the ESP to perform some of the configuration locally.
Attach your terminal cable, typically a null modem cable, to the A/B (Terminal) connector on the ESP back panel, shown in Figure 7-2. This is an asynchronous ttya port on the UNIX-based ESP. Your terminal (or PC and emulation software) must be set to match the ESP communication parameters:
As described in Chapter 1, ESPs can be added to the WAN Service Node as a stand alone unit or in a redundant pair configuration. You must know before you proceed whether your ESP is going to act as a stand alone unit or in the redundant pair configuration.
The first time you connect an ESP to the BPX 8620 and power it up, you have to run the ESP installation program (ApsInstall) to prompt it with enough configuration information to specific its role and to start the ESP Configuration Interface.
If you are installing it as a redundant system (2 ESPs in the same WAN Service Node), you must know the IP address for both ESPs during this initial configuration.
ApsInstall cannot be run when ESP software is already installed on your system. Before running, ApsInstall, you should run ApsUninstall which is described in Appendix H in the section ApsUninstall. New ESP software is typically made available on Cisco Connection Online (CCO) as described in Appendix F in the sections Loading the New Software onto the StrataView Plus Workstation and Transferring the Software to the ESP. Next uncompress (uncompress filename) and tar (for instance, tar xvf ESP_BIN_8_5) the uncompressed file.
After the ESP software has been uncompressed and tarred on the ESP, to run ApsInstall, follow these steps:
Step 1 Power on the ESP and log in as root.
Step 2 Change to the ESP scripts directory by entering:
cd /opt/aps/scripts
Step 3 Start the ESP configuration program by entering
ApsInstall
and pressing Return.
Step 4 The program will run with the following messages and series of prompts. You will be asked as is shown in the following example to select a start up state, a start up role, and to enter the IP address of the peer ESP. The ESP configuration will prompt you as follows:
################################################################# Installing APS System, Copyright (c) Cisco Systems Inc. 1996-1997 ################################################################# Checking already installed executables... All executables present All directories present ATM driver installed ... ... Is this ESP the (P)rimary or (S)econdary host [P] ? \c P
Enter P or S to configure the Primary or Secondary role.
Do you want to create the APS startup config file now [y] ? \c y
Enter y to create the APS startup config file.
APS startup configuration: Enter startup state (1=OOS, 2=INSRVC) :[0] \c 1
Enter 1 or 2 to select the startup state, either OutOfService (OOS) or InService (INSRVC). This is just an initialization parameter and can be changed with the ESP Configuration Interface, once it is running. You will typically enter 1 for Out of Service here.
Enter startup role (0=STANDALONE, 1=ACTIVE, 2=STANDBY) :[0] \c 1
Select a startup role. Again this is only an initialization parameter and can be changed once the ESP Configuration Interface is running. (If you select 0 for standalone, you will not be asked to enter a peer IP address. Typically during a first-time installation, you will enter 2 for standby here.
Enter network peer ip addr :\c 192.168.4.130
If you are installing a redundant pair of ESPs (or if you are adding a second ESP to the WAN Service Node) you must enter the peer ESP IP address here, for example 192.168.4.130.
Step 5 After you enter the peer IP address, the ApsInstall script concludes with the following messages:
Creating Config file Config file created Changing tftp daemon entry in /etc/inetd.conf file... Changed tftp daemon entry Updating /etc/aarconfig file... Added entries to aarconfig file ################################################################# APS Installation Completed successfully #################################################################
Step 6 Now reboot the ESP by entering the reboot command:
reboot
The ESP will restart and prompt you to login as apsuser. The first time you login as espuser, you will be prompted to change the ESP password. After changing the password, the ESP will start with the ESP processes running and launch the ESP Configuration Interface. (The ESP Configuration Interface is described in detail in Chapter 8, Understanding the ESP Configuration Interface.)
From this time forward, you should log in using your apsuser password.
Appendix H contains a sample of the ApsInstall script.
When the command is running it will produce an output (including some prompts) similar to the following:
################################################################# Installing APS System, Copyright (c) Cisco Systems Inc. 1996-1997 ################################################################# Checking already installed executables... All executables present All directories present ATM driver installed Billing directory present Billing directory exported Daemon scripts being installed... Daemon scripts installed Updating System files... System files updated Adding Logins... apsuser, apslog and apsadmin users added Change password after installation Is this ESP the (P)rimary or (S)econdary host [P] ? \c P Updated atmconfig file Do you want to create the APS startup config file now [y] ? \c y APS startup configuration: Enter startup state (1=OOS, 2=INSRVC) :[0] \c 2 Enter startup role (0=STANDALONE, 1=ACTIVE, 2=STANDBY) :[0] \c 1 Enter network peer ip addr :\c 192.168.4.130 Creating Config file Config file created Changing tftp daemon entry in /etc/inetd.conf file... Changed tftp daemon entry Updating /etc/aarconfig file... Added entries to aarconfig file ################################################################# APS Installation Completed successfully #################################################################
When you have an existing ESP operating in the StandAlone mode, you have to add an a redundant peer in a careful sequence.
Before running ApsInstall on the new ESP, you have to change the Administrative Role of the existing StandAlone ESP to the Active role and provide the Redn ESP IP Address. You do this using the ESP Information menu described in Chapter 8. This makes the existing ESP aware of its redundant peer before you bring the second ESP up.
The ATM NIC has an SC multi-mode fiber (MMF) connector. This molded plastic connector is keyed to accept a multi-mode fiber cable with transmit (TX) on the left and receive (RX) on the right. The ATM NIC connects to an a BXM-155 (an OC3 ATM interface) with one of the following backcards:
ESP ATM Network Interface card connections to a BXM's single-mode fiber (SMF) and single-mode fiber long reach (SMF-LR) backcard require special cable assemblies with an optical attenuator to reduce the transmitted power from the BXM backcard. These cable assemblies are described in Appendix B in the section Fiber Optic Cable Assemblies.
Before connecting your ESP to the BXM, you must have already determined if you are going to use BXM redundancy. If so you, you will need the appropriate Y-cables, depending on which BXM-155 backcards are in place. Remember as shown in Figure 7-3, the Y-cables are connected from the TX (transmit) connector on the ESP ATM NIC to the RX (receive) connector on the two BXM backcards. Also, the RX (receive) connector on the ATM NIC will be connected to the TX (transmit) connectors on the two BXM backcards. Figure 7-4 shows a sample of the Y-end of the cables connected to BXM backcards. BPX 8620 cards must be configured for Y-cable redundancy using the addyred BPX 8620 command.
As described in Chapter 1, there are four ESP ATM NIC-to-BXM redundancy options possible:
1 ) A single ESP with a Y-cable to redundant BXMs.
2 ) Two ESPs (a redundant pair), each attached to a single port on a single BXM.
3 ) Two ESPs (a redundant pair), each attached to a single port on two separate (redundant) BXMs.
4 ) Two ESPs (a redundant pair), each attached to different ports with Y-cables on two separate (redundant) BXMs.
To connect the ATM NIC to the BPX, follow these steps:
Step 1 Identify the BPX 8620 BXM-155 backcard to which you will attach the ESP ATM NIC.
Step 2 Connect the appropriate fiber cable with SC connectors to the ATM NIC and then to the BXM backcard.
Step 3 Log in to the BPX.
Step 4 If appropriate, add Y-cable redundancy with the command addyred.
Step 5 Up the trunk with the uptrk command. (Note that this command configures all the ports on the BXM card to be trunks.)
Step 6 Configure the trunk with cnftrk command. Figure 7-5 illustrates the configuration parameters required between the BXM card and the ESP ATM NIC.
svcbpx1 TN Userxxxxx BPX 15 9.1.xx May 26 1998 10:37 PDT
TRK 3.4 Config OC3 [353207cps] BXM slot: 3
Transmit Rate: 353208 Line framing: STS-3C
Subrate data rate: -- coding: --
Line DS-0 map: -- CRC: --
Statistical Reserve: 1000 cps recv impedance: --
Idle code: 7F hex cable type: --
Max Channels/Port: 256 length: --
Connection Channels: 256 Pass sync: Yes
Traffic: V,TS,NTS,FR,FST,CBR,VBR,ABR Loop clock: No
SVC Vpi Min: 2 HCS Masking: Yes
SVC Channels: 50 Payload Scramble: Yes
SVC Bandwidth: 300000 cps Frame Scramble: Yes
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds
This Command: cnftrk 3.4 353208 1000 7F V,TS,NTS,FR,FST,CBR,VBR,ABR 2 50
SVC Bandwidth (300000):
The standard BXM parameters can be accepted for most parameters on this trunk as shown. You will have to enter a value, however, for SVC Channels (shown as 200) and SVC Bandwidth (shown as 300000 cps). These are SVC resource partitioning parameters. Resource partitioning is described in more detail in Chapter 8. Note that the OC-3 Line framing is the default STS-3C.
Step 7 Next configure the SVC Queue Pool Size with the cnftrkparm command. The Configure Trunk Parameters screen is shown in Figure 7-6.
svcbpx1 TN StrataCom BPX 15 9.1.0E May 26 1998 10:39 PDT
TRK 3.4 Parameters
1 Q Depth - Voice [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - VBR [ 5000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [20000] (Dec)
4 Q Depth - BData A [10000] (Dec) 18 Low CLP - CBR [ 60] (%)
5 Q Depth - BData B [10000] (Dec) 19 High CLP - CBR [ 80] (%)
6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - VBR [ 60] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - VBR [ 80] (%)
8 Red Alm - I/O (Dec) [ 2500 / 10000]22 Low CLP/EPD-ABR [ 60] (%)
9 Yel Alm - I/O (Dec) [ 2500 / 10000]23 High CLP - ABR [ 80] (%)
10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)
11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 500] (Dec)
12 Low CLP - BData B [ 25] (%)
13 High CLP - BData B [ 75] (%)
14 EFCN - BData B [ 30] (Dec)
This Command: cnftrkparm 3.4
Which parameter do you wish to change: 25
The only parameter that needs to be changed with this menu is 25 SVC Queue Pool Size. The shown default is 500.
Since the ESP is a feeder shelf from the BPX's perspective, you still have to add the ESP to the BPX 8620 with the addshelf p command. Adding it as a shelf allows the StrataView Plus discovery mechanism to find the ESP. This should be done, however, after the ESP has been, connected to a LAN, been configured, and rebooted. Using the addshelf p command is described in the section, Adding the ESP Shelf to the BPX.
After the you have run ApsCreateCnfg and started the ESP Configuration Interface, you should add the ESP as a shelf to the BPX. To add the ESP shelf, follow these steps:
Step 1 Log in to the BPX.
Step 2 Add the ESP shelf to the WAN Service Node with the addshelf p command. For the ESP attached to axlab1.13.2, this command would be:
addshelf 13.2 p
This will allow StrataView Plus to discover the ESP as a shelf attached to the BXM. It will also allow the BPX 8620 to exchange its name and IP address with the ESP using the Annex G protocol.
The ESP connects to an Ethernet LAN to communicate with the BPX, the MGX 8220, and with the StrataView Plus (SV+) Workstation. Figure 7-7 illustrates the Ethernet connections.
Normally the ESP is connected from its 10Base-T connector to an Ethernet Hub. Typically, the BPX 8620 BCC's LAN port, and an StrataView Plus Workstation are also connected to this same Ethernet segment.
You may have to modify some of the ESP UNIX operating system (i.e., Solaris 2.5) files for your local LAN environment. To do this, you will need to use a text editor such as vi to modify files and a few simple Sun operating system (Solaris) commands.
vi is a UNIX-based screen editor which can be used to make some minor modifications to the UNIX-based files. You can find out more about vi, by typing man vi at the ESP UNIX prompt and pressing Enter. In vi there is a command mode and an editing (i.e., insertion) mode. Most commands are entered from the command mode; while the file is actually modified in the editing mode. You quit the editing mode with ESC. Since only minor changes need to be made to ESP UNIX files, you should only need to know a few commands:
When you are logged in to the ESP, you can find out the use and syntax of operating system commands with the man page command; for instance, enter man login to find out about the login command.
A quick procedure for editing any of the files:
Step 1 cd to where the file is located
Step 2 vi filename.
Step 3 Position cursor where you want to add or change text (use the arrow keys or h, j, k, l).
Step 4 Enter o to add a new line, i to edit a line, or R to enter overwrite mode.
Step 5 Enter your text.
Step 6 Hit ESC when you are done adding text. You are now back in the command mode.
Step 7 Enter ZZ to save the file. (You can use more filename to check that file has been modified).
Before beginning this procedure, you must know what the IP address for the ESP (and the redundant ESP if they are being installed as a redundant pair) the subnet mask, and the hostname(s) will be.
After checking with your system administrator, set the IP address, hostname, subnetmask, and other parameters necessary for operating the ESP in your local area network environment, as follows:
Step 1 Connect a terminal to the ESP.
Step 2 Log in to ESP as superuser.
Caution Once you start changing host names and IP addresses, you must make sure you complete all the files. Do not turn off power or reboot in the middle of this process or you could disable your ESP.
Step 3 Use vi to screen edit the file /etc/hosts and add the IP address for the ESP and the IP address for the SV+ Workstation.
For direct Ethernet connection where, for example, you have an SV+ Workstation with a hostname of nms and an IP address of 200.1.2.3, a BPX switch with hostname of bpx1 and an IP address of 200.1.2.5, and a ESP with a hostname of esp1 and an IP address of 200.1.2.4, you would add the two lines, shown in bold type, to the hosts file:
Contents of /etc/hosts # 127.0.0.1 localhost #200.1.2.4 esp1 loghost # ESP1 (ESP 1 local Ethernet port)200.1.2.3 nms # SV+ Workstation200.1.2.5 bpx1 # BPX1 LAN Port # End of hosts
Step 4 If required for your local network, use vi to screen edit the file /etc/networks, which will appear similar to the following:
Contents of /etc/networks file:
#
# The loopback network is used only for intra-machine communication
#
loopback 127
#
# Internet networks
#
arpanet 10 arpa # Historical
nms-net 200.1.2 # SV+ network
# End of networks
(For our example, the line in bold text, nms-net . . ., is added to the networks file.)
Step 5 If required for your local network, use vi to screen edit the file /etc/netmasks to add the appropriate subnet mask for your LAN segment.
Step 6 If required for your local network, use vi to screen edit the file /etc/hostname.le0 to name the ESP ethernet port.
Step 7 If required for your local network, use vi to screen edit the file /etc/nodename to name the ESP node, and verify that this name is the same name as /etc/hostname.le0.
Step 8 Use the date command to set the local date and time.
BPX 8620 installation and configuration are covered in the Cisco BPX 8620 Installation and BPX 8620 Reference manuals. During the configuration of Service Node interfaces, you must make sure that the BPX 8620 IP address, SNMP parameters, and Network IP address are set consistent with your local area network (Ethernet LAN). Use the following BPX 8620 commands to set these parameters:
The use of these commands is covered in the Cisco WAN Switching Command Reference or the Cisco WAN Switching Super User Command Reference. Super User commands must only be used by authorized personnel, and must be used carefully.
MGX 8220 installation and configuration are covered in the Cisco MGX 8220 Reference. During the configuration of Service Node interfaces, you must make sure that the MGX 8220 IP address is set up consistent with your local area network (Ethernet LAN). Use the following MGX 8220 command to set the proper IP addresses:
cnfifip "-ip <ip address> -if <interface type> -msk <subnet mask address> -bc <broadcast address>"
The use of this command is covered in the Cisco MGX 8220 Command Reference
After you have connected and configured the ESP(s), you should log in (or have someone log in) to the StrataView Plus Workstation and ping the ESP to ensure that they are communicating. The rest of the configuration and provisioning of the Service Node and SVC services are described in Chapter 9, Operation and Maintenance. Much of this configuration and provisioning is done with the ESP Configuration Interface, which is described in detail in Chapter 8, Understanding the ESP Configuration Interface.
|
|