|
|
This chapter provides procedures for performing the common tasks encountered during the initial installation and operation of a WAN Service Node network. This chapter includes:
Resources on WAN Service Node UNI ports and NNI trunks have to be divided between SVCs and PVCs. This is known as resource partitioning and is done through the Command Line Interface for the BPX 8620 and the MGX 8220.
This section provides procedures for:
The BPX switch's BXM card can be configured as either a trunk or a line card. When it is configured as line card, its interfaces can be configured as either UNI or NNI. When it is configured as a trunk card, its interfaces can be configured only as NNI. These configuration options are illustrated in Table 9-1. An X in the table indicates the configuration is permitted; for instance, in the first row, a BXM card can be configured for UNI.
| BXM | UNI | NNI |
|---|---|---|
| Line card | X | X |
| Trunk card |
| X |
The following UNI Ports, which support ATM or Frame Relay SVCs, will have their resources partitioned:
An AUSM card which will support ATM SVCs will have to be added and upped like a standard PVC port. Complete details on using the MGX 8220 command line interface and applicable commands are described in the Cisco MGX 8220 Reference and MGX 8220 Command Reference manuals. In addition, the Cisco System Overview provides conceptual information about ATM connections and services.These procedures will concentrate on those commands that are specific to SVC resource partitioning.
Before partitioning SVC resources, you must have determined which AUSM module will be connected to ATM CPE equipment for SVCs. The AUSM port must have already been added configured, and upped as described in the MGX 8220 manuals with these commands:
To partition SVC resources on an AUSM UNI port, follow these steps:
Step 1 Log in to the MGX 8220.
Step 2 cc to the AUSM slot you are going to partition.
Step 3 Enter the command cnfsvcrange, the menu shown in Figure 9-1 appears:
MGX8220NAME.1.11.AUSM8.a > cnfsvcrange
cnfsvcrange "num-of-resource [resource-type start-resource [port-num]]
num-of-resource: 1-256
resource-type: LCN, VPID, VCI, or VPI
start-resource: The LCN, VPID, VCI, or VPI where search for contiguous
range started
16 - 1015 if LCN;
1 - (100 for STI, 20 for UNI, 340 for NNI) if VPID
0 -255 if VPI; 1 -1023 if VCI
port-num: Logic port Number
MGX8220NAME.1.11.AUSM8.a >
This command is used to partition the following resources:
Step 4 First you should reserve the desired number of LCNs. For instance, to reserve 100 LCNs starting at number 20 for an AUSM8 in slot 11 you would enter: cnfsvcrange 100 LCN 20, then press Enter. The following example shows the result:
MGX8220NAME.1.11.AUSM8.a > cnfsvcrange 100 LCN 20 num of res = 100, type = 1 start = 20 port = -1
Step 5 Next you have to reserve the desired number of VPIDs. For instance on an AUSM8 in slot 11, to reserve 40 VPIDs starting with number 40, you would enter: cnfsvcrange 40 VPID 40, then press Enter. The following example shows the result:
MGX8220NAME.1.11.AUSM8.a > cnfsvcrange 40 VPID 40 num of res = 40, type = 2 start = 40 port = -1
Step 6 Next you have to reserve the desired number of VPIs. For instance, on a AUSM8 in slot 11, to reserve 35 VPIs starting on number 0 on port 2, you would enter: cnfsvcrange 35 VPI 50 2, the press Enter. (Note that ATM SVC signaling is on VPI 0/VCI 5, so the SVC start range should begin on 0.) The following example shows a typical result of the command:
MGX8220NAME.1.10.AUSM8.a > cnfsvcrange 35 VPI 0 2 num of res = 35, type = 4 start = 0 port = 2
Step 7 Finally, you can see how the SVC resources are partitioned with the dspsvcrange command. This command brings up the display shown Figure 9-2, illustrating the resources reserved on the AUSM:
MGX8220NAME.1.11.AUSM8.a >dspsvcrange LCN: 900, Min: 20, Max: 919 VPID: 20, Min: 1, Max: 20 VPI : 20, Min: 0, Max: 19 Port: 1 VPI : 20, Min: 0, Max: 19 Port: 8 MGX8220NAME.1.11.AUSM8.a >
Repeat the SVC resource partitioning for every AUSM module for which you want SVC support.
An FRSM card which will support Frame Relay SVCs will have to be added and upped like a standard PVC port. Complete details on using the MGX 8220 command line interface and applicable commands are described in the Cisco MGX 8220 Reference and MGX 8220 Command Supplement manuals. In addition, the Cisco System Overview provides conceptual information about Frame Relay connections.These procedures will concentrate on those commands that are specific to SVC resource partitioning.
Although FRSM commands are similar to AUSM commands, they are not identical. You must pay close attention to the syntax of the commands you enter.
Before partitioning SVC resources, you must have determined which FRSM module will be connected to Frame Relay CPE equipment for SVCs. The FRSM port must have already been added configured, and channels added as described in the MGX 8220 manuals with these commands:
You must already have determined which FRSM ports you are going to partition before starting this procedure. To partition Frame Relay SVC resources on an FRSM UNI port, follow these steps:
Step 1 Log in to the MGX 8220.
Step 2 cc to the FRSM slot you are going to partition.
Step 3 You can use the dspports and dspport <port number> to find the port you are going to configure for Frame Relay SVCs and to see how the port is currently configured. The dspport command is a large screen broken in two sections as shown in Figure 9-3 and Figure 9-4:
SlotNum: 12 PortLineNum: 1 PortNum: 1 PortRowStatus: Mod PortDs0Speed: 64k PortDs0ConfigBitMap(1stDS0): 0xffffff(1) PortEqueueServiceRatio: 1 PortFlagsBetweenFrames: 1 PortSpeed: 1536kbps SignallingProtocolType: NoSignalling AsynchronousUpdates: Disable T391LineIntegrityTimer: 10 T392PollingVerificationTimer: 15 N391FullStatusPollingCounter: 6 N392ErrorThreshold: 3 N393MonitoredEventCount: 4 EnhancedLmi: Off PortState: Active PortSignallingState: No Signalling Failure CLLMEnableStatus: Disable CLLMxmtStatusTimer: 0 Type <CR> to continue, Q<CR> to stop:
Pressing return brings up the other half of the display port screen:
portType: frameRelay
PortIngrPercentUtil: 0
PortEgrPercentUtil: 0
PortOversubscribed: False
PortSvcStatus: Enabled
PortSvcInUse: In-Use
PortSvcShareLcn: Card-based
PortSvcLcnLow: 16
PortSvcLcnHigh: 271
PortSvcDlciLow: 1
PortSvcDlciHigh: 256
PortDs0UsedLine1: 0x00ffffff
PortDs0UsedLine2: 0x00000000
PortDs0UsedLine3: 0x00ffffff
PortDs0UsedLine4: 0x00000000
PortNumNextAvailable: 13
Syntax : dspport "port_num"
port number -- values ranging from 1-96 are accepted
MGX8220Name.1.12.FRSM.a >
Note that this screen lists the following Frame Relay SVC parameters:
The Frame Relay SVC resource partitioning parameters are configured with the xcnfrport and cnfsvcrange commands described in the next steps.
Step 4 You would enable Frame Relay SVCs for FRSM port 1 with the xcnfport command as follows:
xcnfport -pt 1-svcen 2
-pt is <PortNum> where port number is 1 -96
-svcen is <PortSvcStatus> where portSvcStatus = 1: Disable, 2: Enable
Step 5 You have to change to the shellConn to configure the SVC range. Enter shellConn.
Step 6 The FRSM cnfsvcrange has the syntax shown in Figure 9-5:
MGX8220Name.1.12.FRSM.a >shellConn
MGX8220Name.1.12.FRSM.a > cnfsvcrange
cnfsvcrange
cnfsvcrange "num-of-resource [resource-type start-resource [port-num]]"
num-of-resource: 1-256
resource-type: LCN or DLCI
start-resource: The LCN or DLCI where search for contiguous range started
16 - 271 if LCN; 1 - 1023 if DLCI
port-num: Logic port Number
value = -1 = 0xffffffff
MGX8220Name.1.12.FRSM.a >
This command is used to partition the following resources:
Step 7 Next you would reserve some LCNs for the FRSM. If you wanted to reserve 50 LCNs, starting with number 16, on the FRSM in slot 12, you would enter:
cnfsvcrange "50 LCN 16"
The following example shows the results of this command:
MGX8220Name.1.12.FRSM.a > cnfsvcrange "50 LCN 16" cnfsvcrange "50 LCN 16" num of res = 50, type = 1 start = 16 port = -1
Step 8 Next you will reserve some DLCIs for Frame Relay SVCs. If you wanted reserve 50 DLCIs starting with number 11 on a FRSM in slot 12, you would enter:
cnfsvcrange "50 DLCI 11"
The following example shows the results of this command:
MGX8220Name.1.12.FRSM.a > cnfsvcrange "50 DLCI 1 1" cnfsvcrange "50 DLCI 1 1" num of res = 50, type = 2 start = 1 port = 1
Step 9 You can check the configured Frame Relay SVC ranges with the following command:
dspsvcrange
which results in a display similar to Figure 9-6:
MGX8220Name.1.12.FRSM.a > dspsvcrange dspsvcrange LCN: 50, Min: 16, Max: 65 DLCI: 50, Min: 1, Max: 50 Port: 1 DLCI: 50, Min: 1, Max: 50 Port: 2 DLCI: 50, Min: 1, Max: 50 Port: 5 DLCI: 50, Min: 1, Max: 50 Port: 6 value = 0 = 0x0 MGX8220Name.1.12.FRSM.a >
Repeat the Frame Relay SVC resource partitioning for each FRSM that you want to support SVCs in your system.
A BPX 8620 BXM card used as a UNI port can be configured to support ATM SVCs and SPVCs. The BXM will have to be added and upped like a standard PVC port. The BXM port will have to upped as a line (upln) to function as a UNI port.
Complete details on using the BPX 8620 command line interface and applicable commands are described in the Cisco BPX 8620 Reference and Command Reference manuals. In addition, the Cisco System Overview provides conceptual information about ATM connections and services. These procedures will concentrate on those commands that are specific to SVC resource partitioning.
Before partitioning SVC resources, you must have determined which BXM UNI ports will support ATM SVCs. The BXM must have its resources partitioned to support SVCs. The following resources must be partitioned:
To partition the BXM port, follow these steps:
Step 1 Log in to the BPX 8620.
Step 2 Up the line and port which is going to be connected to ATM CPE.
Step 3 Make sure the port is configured as UNI.
Step 4 Enter the cnfport <port num> command, shown in Figure 9-7:
svcbpx1 TN Userxxxxx BPX 15 9.1.xx May 26 1998 10:26 PDT
Port: 1.2 [ACTIVE ] Port Load: 0 %
Interface: LM-BXM CAC Override: Enabled
Type: UNI %Util Use: Disabled
Speed: 353208 (cps) Vc Shaping: Disabled
Shift: SHIFT ON HCF (Normal Operation)
SIG Queue Depth: 640
Protocol: ILMI Addr Reg Enab: N
VPI.VCI: 0.16 SVC Channels: 2000
ILMI Polling Enabled: N SVC VPI Min: 0
Trap Enabled: N SVC VPI Max: 102
T491 Polling Interval: 30 SVC Bandwidth: 300000 (cps)
N491 Error Threshold: 3
N492 Event Threshold: 4
This Command: cnfport 1.2
NNI Cell Header Format? [N]:
Configure the SVC Channels, SVC VPI Min, SVC VPI Min/Max, and SVC Bandwidth as necessary. The SVC VPI Min for a UNI port must be 0. Note that when ILMI is the selected protocol for the port, you also can enable ILMI address registration (Addr Reg Enab), and ILMI polling.
Step 5 Next you need to configure the SVC Port Queue depth with the cnfportq <portnum> command shown in Figure 9-8.
spvc24 TN StrataCom BPX 15 9.0.a5 Sep. 25 1997 09:25 GMT
Port: 13.1 [ACTIVE ]
Interface: LM-BXM
Type: UNI
Speed: 353208 (cps)
SVC Queue Pool Size: 5000
CBR Queue Depth: 600
CBR Queue CLP High Threshold: 80%
CBR Queue CLP Low Threshold: 60%
CBR Queue EFCI Threshold: 80%
VBR Queue Depth: 5000 UBR/ABR Queue Depth: 20000
VBR Queue CLP High Threshold: 80% UBR/ABR Queue CLP High Threshold: 80%
VBR Queue CLP Low Threshold: 60% UBR/ABR Queue CLP Low Threshold: 60%
VBR Queue EFCI Threshold: 80% UBR/ABR Queue EFCI Threshold: 30%
This Command: cnfportq 13.1
SVC Queue Pool Size [5000]:
svcbpx1 TN Userxxxxx BPX 15 9.1.xx May 26 1998 10:27 PDT
Port: 1.2 [ACTIVE ]
Interface: LM-BXM
Type: UNI
Speed: 353208 (cps)
SVC Queue Pool Size: 500
CBR Queue Depth: 600
CBR Queue CLP High Threshold: 80%
CBR Queue CLP Low Threshold: 60%
CBR Queue EFCI Threshold: 60%
VBR Queue Depth: 5000 UBR/ABR Queue Depth: 20000
VBR Queue CLP High Threshold: 80% UBR/ABR Queue CLP High Threshold: 80%
VBR Queue CLP Low Threshold: 60% UBR/ABR Queue CLP Low/EPD Threshold:60%
VBR Queue EFCI Threshold: 60% UBR/ABR Queue EFCI Threshold: 20%
This Command: cnfportq 1.2
SVC Queue Pool Size [500]:
Configure the SVC Queue Pool Size parameter to a value greater than 0 (zero); the default is 0 and needs to be changed for SVCs to operate.
Partition the SVC resources for all the BXM which will support ATM SVCs in your WAN Service Node . The BXM SVC partition will also be used to support SPVCs as described in Chapter 5, Soft Permanent Virtual Circuits and in Appendix I, PVC Migration Utility.
The BPX 8620 BXM card is the only trunk card that has resources partitioned to support SVCs in Release 2.2.
When the BXM is used as a trunk in a WAN switching network, it will have to have its resources partitioned to support SVCs. The BXM card will have to upped as a trunk (uptrk).
The BXM is described in detail in the Cisco BPX 8620 Reference. Complete details on using the BPX 8620 command line interface and applicable commands are described in the Cisco BPX 8620 Reference and Cisco WAN Switching Command Reference manuals. In addition, Cisco WAN Switching System Overview provides conceptual information about ATM connections and services. These procedures will concentrate on those commands that are specific to SVC resource partitioning.
The following BXM trunk resources must be partitioned for SVCs:
To partition the BXM trunk resources for SVCs, follow these steps:
Step 1 Log in to the BPX 8620.
Step 2 Make sure the BXM has been upped as a trunk with uptrk <trunk_num> command.
Step 3 Enter the cnftrk <trk num> command, shown in Figure 9-9:
svcbpx1 TN Userxxxxx BPX 15 9.1.xx May 26 1998 10:30 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
SVC VPI Min (2):
Configure the SVC Channels, SVC VPI Min, and SVC Bandwidth as desired. (On the links between two BPX switches the minimum VPI [minVpi] must be in the range 2 - 4095.)
Step 4 Next configure the SVC Queue depth with cnftrkparms <trunk_num> command as shown in Figure 9-10:
svcbpx1 TN Userxxxxx BPX 15 9.1.xx May 26 1998 10:34 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
Configure the SVC Queue Pool Size as desired.
Partition the SVC resources for all the other BXMs in your BPX 8620.
You use the ESP Configuration Interface for the initial configuration and provisioning of the ESP and WAN switching network. The ESP Configuration Interface was described in detail in Chapter 8, Understanding the ESP Configuration Interface. This section concentrates on how the Configuration Interface is used, and the sequence of operations. This section will be primarily cover the following sections of the Configuration Interface:
The next section, PNNI Provisioning and Static Routing, will cover Topology Information and PNNI Information.
The ESP Information menu is used to configure the ESP, and the redundant ESP when there is a redundant pair in the WAN Service Node . One of these menus must be completed for every ESP (that is, WAN Service Node ) in the network. To initially provision your WAN Service Node network, follow these steps:
Step 1 Log in to the ESP and start the Configuration Interface.
Step 2 Select the ESP Information menu and configure:
This menu will have to be completed for every ESP in the network.
Step 3 From the ESP Information menu, press F2 to select Billing Information. Configure the following WAN Service Node billing parameters:
Step 4 For IISP nodes only, configure the Node list; from the ESP Information menu, press F6 to access the Node List menu. Next press F3 to add a Node.
Step 5 For IISP nodes only, add nodes and node prefixes and addresses. Add the Node and the Node Address or Node Prefix. (You will have to add every WAN Service Node in the network to the Node List)
Step 6 From the ESP Information menu, press F7 to access the View Shelf List. Then press F3 to access the Shelf Information menu. Configure the following:
You must add every MGX 8220 shelf attached to the BPX 8620 at this WAN Service Node .
Next you will have to add all the UNI ports at this WAN Service Node .
To add the UNI ports, follow these steps:
Step 1 From the ESP Configuration Interface main menu, select UNI Information.
Step 2 From the UNI Information menu, press F3 to Add a UNI Port.
Step 3 If the port is an ATM UNI port, configure the following:
If the port is a Frame Relay UNI port, configure the following:
You will have to add a Configuration Interface record for every UNI port at this WAN Service Node .
Step 4 Next, from the UNI Information menu, press F1 to View Port Address. From this menu you will add Port Addresses or Port Prefixes. You will have to add a Port Address or Port Prefix for every UNI port at this WAN Service Node .
Step 5 Next, from the UNI Information menu, press F3 to View Egress Screen Addresses. From this menu, you press F4 to add an UNI address or address prefix to the list of Egress Screen Addresses. You have to add every address you want to Egress Screen at this UNI port.
Step 6 Finally, from the UNI Information menu, press F6 to configure UNI port billing. From this menu, you configure:
You must repeat the UNI Configuration for each WAN Service Node.
If ILMI is not supported on a given CPE attached to the WAN Service Node , then the NSAP addresses must be configured manually. When assigning addresses you must assign a unique, valid prefix to the WAN Service Node . This same prefix should be used for all ATM CPE UNI's attached to this Service Node.
Figure 9-11 illustrates a simple network with attached CPE that do not support ILMI.
There are three important steps to remember when configuring CPE without ILMI:
Step 1 Ensure that the WAN Service Node port, this example the MGX 8220 AUSMs, have been configured for no ILMI.
Step 2 Make sure that the ATM UNI Port have been configured for no ILMI with the ESP Configuration Interface ATM UNI Information menus.
Step 3 Manually configure the CPE end station ATM addresses with the ESP Configuration Interface menus. In this case, the 13-byte Node Prefix for WAN Service Node 1 is 45.00.00.00.00.00.00.00.00.00.00.00.11 and the CPE ESI (end system identifier) is 80.000.00.00.40.00.00.11. These two parts will combine to become CPE 1's ATM address. Similarly Node Prefix 2 and CPE ESI 2 will combine to form the ATM address for CPE 2. Note that any CPE attaching to either of the WAN Service Nodes will have to use that node's prefix as the first 13 bytes of its ATM address.
If ILMI is supported on a given CPE attached to the WAN Service Node, the WAN Service Node will discover all the ATM CPE devices attached to it. (Remember that ILMI is not supported for Frame Relay SVCs.) Figure 9-12 illustrates a simple network with attached CPE that support ILMI.
In order for ILMI address registration to take place, you must:
Next you have to create an Configuration Interface record for each NNI trunk in your WAN Service Node network.
To add an NNI record, follow these steps:
Step 1 From the Configuration Interface main menu, select NNI Information.
Step 2 From the NNI Information menu, select F3, Add NNI Port.
Step 3 From the NNI Information menu, configure the following:
Add a record for every NNI port on the WAN Service Node.
The NNI Information records will have to completed at every WAN Service Node in the network.
The WAN Service Node does not support ILMI over IISP links. Thus, when a foreign switch is connected to a WAN Service Node, as is shown in Figure 9-13, the address to CPE 2 will have to configured on the WAN Service Node with the ESP Configuration Interface. This address must include the Foreign Switch's Node Prefix. This address will be added to the ESP PNNI routing table as an exterior reachable address. In this example the address of CPE 1 will be automatically discovered by ILMI. A static route on the Foreign Switch will also have to be configured to the WAN Service Node. Also be sure to configure one end of the IISP link as User, and the other end as Network.
When you are connecting a foreign switch to a WAN Service Node, as shown in Figure 9-14, you have to ensure that PNNI is enabled at both ends, and if applicable that ILMI is enabled at the foreign switch's UNI ports.
You configure PNNI routing from the ESP Configuration Interface using the PNNI Information options.
To configure PNNI routing, follow these steps:
Step 1 From the ESP Configuration Interface main menu, select PNNI Information.
Step 2 From the PNNI Information menu, configure:
Although it is not possible to discuss every type of ATM or Frame Relay CPE that can be connected to a WAN Service Node, this section provides examples of what is involved with connecting two types of Cisco CPE to the WAN Service Node:
A Cisco Frame Relay router is typically connected to a WAN Service Node's Frame Relay UNI. Cisco offers Frame Relay SVC support in the Enterprise image on Cisco platforms that include a serial or HSSI interface (Cisco 7000 and 7500 series, Cisco 4500 and 4700, Cisco 4000, Cisco 3000, and Cisco 2500 platforms).
Figure 9-15 illustrates simple WAN Service Node network with two Frame Relay SVC routers attached.
The two Cisco Frame Relay routers (Router 1 and Router 2) must be configured for proper Frame Relay SVC operation. In this figure each router has one serial interface (s0) to the Cisco WAN switching network, and one Ethernet LAN interface (e0). When configuring these routers for Frame Relay SVC operation, the important things to remember are:
The Light Stream 1010 ATM switch is Cisco System's ATM switch for workgroup and campus backbone deployment. It provides support for the following signaling and interface protocols, making it ideal as an interface for a Cisco WAN Service Node:
The complete features of the LS1010 are described in the Cisco LS1010 manual set.
When connecting an LS1010 to the WAN Service Node, you have to ensure that:
The WAN Service Node with the ESP capability can function as a point-to-multipoint client when connected and configured with an LS1010. This combination allows the LS1010 to be the point-to-multipoint server. The WAN Service Node ESP/LS1010 combination thus supports LAN emulation (LANE).
To configure point-to-multipoint SVCs with the WAN Service Node ESP and the LS1010, you must make sure that:
1 ) The LS1010 exists in the same network as the WAN Service Node.
2 ) There are no other switches (such as FORE) in the same network.
3 ) You want to run point-to-multipoint (P2Mpt)
4 ) That the BPX 8620 is either a leaf or that the BPX 8620 is on at least one of the p2mp distribution trees.
5 ) That you configure LANE Clients with static addresses (not through ILMI) if the clients are Cisco 7500 routers.
6 ) That you configure the LS1010 Pt2Mpt I/W feature to enable point-to-multipoint interworking, through the ESP Configuration Interface. (See the Node ID Menu in Chapter 8. Note that on the ESP, the LS1010 Pt2Mpt feature has a default of no.)
7 ) You ensure that the LS1010 is loaded with Sirius release which supports BPX 8620 P2Mpt (point-to-multipoint) interworking feature.
8 ) You connect the LS1010 to BPX 8620 with an FC3/FC-PFQ card, which supports logical multicast feature in LS1010.
9 ) On the LS1010 at the I/F connected to the BPX 8620, you configure the following:
config
interface atm interface_number (for example, 0/0/1)
asig force_mpt_branch
SPVCs are PVCs which reside in the SVC portion of the WAN Service Node's resource partitions and which use the PNNI routing protocol to be routed within the network. SPVCs are configured with the ESP Configuration Interface. Configure an SPVC, follow these steps:
Step 1 Select Option 6 from the ESP Configuration Interface main menu. The SPVC List Menu appears.
Step 2 Press F2, Add and SPVC and a blank SPVC Menu appears. Complete this menu following the guidelines given in Chapter 8 in the section, Adding an SPVC.
The WAN Service Node network management is divided into three sections:
StrataView Plus provides the WAN Service Node and ESP with:
The Cisco StrataView Plus Operations Guide contains the details for running the StrataView Plus application. This section will just provide brief procedures for using the StrataView Plus features associated with the ESP.
StrataView Plus will display an icon for each ESP in the network. The individual icons are displayed (along with AXIS [MGX 8220] shelf icons) when the BPX switch icon, displayed on the top-level map, is expanded. The ESP icon will be color coded to indicate its status:
To view an ESP icon on StrataView Plus, follow these steps:
Step 1 Log into the StrataView Plus and start HP OpenView and a StrataView Plus Desktop.
Step 2 Double click on the StrataCom Network icon. The StrataView Network Topology window will appear. This map should show all the BPX switches (that is, WAN Service Nodes) in your network.
Step 3 Double click on the BPX switch which has the desired ESP attached. A BPX switch window showing all the attached shelves (both MGX 8220 and ESPs) will appear. These shelves will be color coded to indicate their status.
Figure 9-16 illustrates an expanded BPX switch node with an ESP attached.
To telnet to an ESP from StrataView Plus, follow these steps:
Step 1 Access the ESP icon as described above in Map Display (repeat steps 1 to 3 of the Map Display procedure if necessary.)
Step 2 Click on the ESP icon (or an MGX 8220 icon [that is, MGX 8220] if you wanted to log in to an MGX 8220).
Step 3 Pull down the StrataCom menu from the menu bar on the window. Select Telnet (SV), shown in Figure 9-17. An XTerm window with a log in prompt for the ESP will appear.
Step 4 Log in as espuser.
The StrataView Plus Image Download feature will transfer (tftp) a software image (a compressed tar file with .Z extension) to the ESP. (The *.Z file will have to exist on the StrataView Plus Workstation, of course; this file has the form, ESP_BIN_rel_ver.Z.) These images will have to be uncompressed and untarred and loaded on the ESP using the ApsUpgrade script. (The ApsUpgrade script is described in Appendix F, Upgrading ESP Software.)
To download an image to the ESP from StrataView Plus, follow these steps:
Step 1 Log into the StrataView Plus and start HP OpenView and open a StrataView Plus Desktop.
Step 2 Expand an the appropriate BPX switch icon on the HP OpenView map and select and ESP.
Step 3 Pull down the StrataCom option on the window's menu bar. Select Image Download. The Image Download window will appear with a list of ESPs and image files as shown in Figure 9-18.
Step 4 Select the appropriate file (ESP_BIN_rel_ver.Z) and the Download button will become active. Click on the Download button.
StrataView Plus also provides you with the option to save or restore the configuration files created with the ESP Configuration Interface.
When you are saving ESP Configuration Files from StrataView Plus, you transfer these files, which are converted to flat ASCII files by the process, to the StrataView Plus Workstation. The files are saved by name.
To save an ESP configuration, follow these steps:
Step 1 Log into the StrataView Plus and start HP OpenView and open a StrataView Plus Desktop.
Step 2 Expand a BPX switch icon until attached ESP icons are shown. Select the appropriate ESP icon and pull down the StrataCom menu.
Step 3 Select Configuration Save and an MGX 8220 (an MGX 8220) or ESP selection menu will appear as shown in Figure 9-19.
Step 4 Select ESP and the Configuration Save menu, shown in Figure 9-20, will appear.
With this menu, you complete:
Config Data Name: to name the configuration file using the format ESP_DB_rel_ver
Node Selection to specify the Node or Nodes whose configuration you will save. To select the appropriated ESP:
Select it in the Unselected Node List; the press the right Select button to place it in the Selected Node List, as apslab1 is shown in Figure 9-20.
Step 5 Click the Save button. The ESP configuration file is ftped as a flat ASCII file from the ESP to the StrataView Plus Workstation.
To restore an ESP configuration, which has been previously saved, follow these steps:
Step 1 Log into the StrataView Plus and start HP OpenView and open a StrataView Plus Desktop.
Step 2 Expand a BPX switch icon until the attached ESP icon is shown.
Step 3 Select the ESP icon and pull down the StrataCom menu and select Configuration Restore. The Configuration Restore menu, shown in Figure 9-21, will appear.
Step 4 You will be shown lists of configuration files in the Configuration Data box and the ESP node name in the Node Name box. Select the appropriate configuration file (one that you have previous saved) and click the Restore button.
This section will provide instructions for using the StrataView Plus Network Browser to monitor the ESP status:.
To access the Network Browser, follow these steps:
Step 1 Log in to StrataView Plus and start a Desktop.
Step 2 Click on the Network Browser button. The Network Browser window, shown in Figure 9-22, will appear. This window will report information about all the network elements, including the Alarm State of the ESPs.
For general information on the Network Browser, see the Cisco StrataView Plus Operations Guide.
|
|