|
|
Use this chapter to find out about the tasks typically performed to bring up the SES PNNI node. This chapter assumes the following:
After completing the installation and initial configuration tasks, you are ready to bring up the system, using the task sequence shown in Figure 10-1.
This chapter refers to commands that run from the BPX CLI, the SES CLI or CiscoView menus. The BPX CLI commands are documented in detail in the Cisco WAN Switching Command Reference, Release 9.2. The CiscoView menus are described in Chapter 11, "Network Management."
Use this section to find out how to use auto-configuration on the PNNI Controller, to set default PNNI values and ILMI address registration on UNI ports.
 |
Note Auto configuration is enabled only if the attached ATM CPE supports ILMI. If the attached ATM CPE does not support ILMI, you must bring up the port by using the guidelines provided in the section Configuring a Port Without AutoConfiguration and Without ILMI. |
Auto-configuration is comprised of AutoConfigure an UNI Port
Use the following procedure to connect an ATM UNI for auto-configuration using ILMI address registration and the VSI protocol.
At the BPX CLI, perform the following steps:
Step 2 Use the upln command at the BPX CLI to up the line, the physical layer.
Step 3 Use the upport command to up the port.
Step 4 Use the cnfvsiif command at the BPX to configure Service Class Template for the interface. 1 is for MPLS, service template 2 is for ATMF service template on port, and 3 is for ATMF service template on trunk. For PNNI SES UNI interface, the service class template should be set to 2. Detail of service class template is found in Appendix C.
Step 5 Use the cnfrsrc command to set resources on the port.
A system response similar to the following example occurs:
----------------------------------------------------------------------------
oriobpx3 TN StrataCom BPX 8620 9.2.3U Feb. 16 2000 21:39 PST
Port/Trunk :1.3
Maximum PVC LCNS: 256 Maximum PVC Bandwidth:2207
Partition 1
Partition State : Enabled
Minimum VSI LCNS: 2000
Maximum VSI LCNS: 7000
Start VSI VPI: 1
End VSI VPI : 255
Minimum VSI Bandwidth : 100000 Maximum VSI Bandwidth : 250000
VSI ILMI Config : 0
Last Command:cnfrsrc 1.3 256 2207 y 1 e 2000 7000 1 255 100000 250000
-------------------------------------------------------------------------------
|
Note For more information about the configure resources command, refer to the Cisco WAN Switching Command Reference, Release 9.2. |
Step 6 Use the cnfport command to enable ILMI protocol to run on the BXM card and enable VSI ILMI to PNNI controller.
The BXM now sends a VSI trap to the SES PNNI controller.
When the SES PNNI controller receives the trap, it sends a VSI passthrough back to the BXM to enable auto-configuration. The information in the passthrough includes auto-configuration default parameters. Auto-configuration parameters include details such as autoconfiguration on, service registry on, address registration on, node prefix, and others.
The BXM then starts the ILMI protocol with the attached ATM CPE. The BXM will then send the SES PNNI controller the port information: vpi/vci range, interface type, device type, ILMI version, and UNI Signaling version.
Finally, the PNNI Controller starts the UNI signaling stacks.
|
Note All ILMI features on SES PNNI are default to be on, there is NO need to use cnfaddrreg, cnfautocnf to enable ILMI features on SES PNNI. |
To modify port parameters after AutoConfiguration, perform the following steps at the SES PNNI Controller CLI:
|
Note When using service-affecting parameters on a port already configured, the port must be must be brought down prior to attempting modifications to port parameters. |
Use the following procedure to modify port parameters.
This brings down the signaling stacks for the port.
Step 2 Change the appropriate parameter with one of the following cnf commands:
Non-service affecting parameters can be changed without downing the port. For example, you do not need to down the port to execute the following SES CLI commands:
Step 3 Use one of the following display commands to see the current configurations:
Step 4 Use the uppnport command to enable the port.
Use the following procedure to preconfigure specific parameters before a port is brought up with AutoConfiguration.
Use the SES PNNI Controller CLI to perform steps 1 through 3.
|
Note Ports are administratively down, by default. |
Step 2 Modify the appropriate parameter with one of the following PNNI Controller cnf commands:
Step 3 Use the uppnport command to up the PNNI port.
|
Note The signaling stacks are not yet brought up because the port configuration has not yet been received from the BXM. |
Use the BPX CLI to perform steps 4 through 8.
Step 4 Use the upln command at the BPX CLI to bring up the line.
Step 5 Use the upport command to bring up the port.
Step 6 Use the cnfvsiif command at the BPX CLI to configure PNNI service template, 2.
Step 7 Use the cnfrsrc command to set resources on the port.
Step 8 Use the cnfport command to enable ILMI protocol on BXM port.
The following results occur:
a. The BXM now sends a VSI trap to the SES PNNI controller.
b. The PNNI Controller starts the UNI signaling stacks:
If the attached ATM CPE does not support ILMI, you must bring up the port without auto-configuration.
Use the BPX CLI to perform steps 1 through 4.
Step 2 Use the upport command to up the port.
Step 3 Use the cnfvsiif command at the BPX CLI to configure PNNI service template, 2.
Step 4 Use the cnfrsrc command to set resources on the port.
The following results occur:
a. The BXM now sends a VSI trap to the SES PNNI controller.
b. The SES PNNI controller receives the BXM port configuration through VSI with ILMI disabled. The SES PNNI controller brings up the UNI or PNNI signaling stacks.
Use the SES PNNI Controller CLI to perform step 5.
Step 5 Use the addaddr command at the PNNI Controller to set ATM addresses for the port. This step is necessary because there is no automatic address registration from ILMI.
|
Note An address can only be provisioned on a UNI if ILMI address registration is disabled. |
Use this section to find out how to configure a PNNI trunk on BPX and SES PNNI Controller.
Use the following procedure to connect an ATM NNI trunk with auto-configuration using ILMI and the VSI protocol.
At the BPX CLI, perform the following steps:
Make sure the other BPX BXM port is configured for ILMI.
Step 2 Use the uptrk command at the BPX CLI to up the trunk.
uptrk slot.port
Step 3 Use the addtrk command at the BPX CLI to add AutoRoute on the trunk.
addtrk slot.port
Since AutoRoute is needed to provide IP connectivity, Time of Date, and Network Clocking for this release of BPX/SES, it is essential to add AutoRoute partition in a trunk even if there is no "AutoRoute" PVC service to be implemented. Limit resource is needed to be provisioned to carry IP connectivity, Time of Date, and Network Clocking. Notice that when the AutoRoute service is added to the trunk, the VPI = 0 and 1 will be reserved for AutoRoute. The available VPI for VSI (or PNNI) will start from
VPI = 2.
Step 4 Use the cnfvsiif command at the BPX to configure Service Class Template for the interface. 1 is for MPLS, service template 2 is for ATMF service template on port, and 3 is for ATMF service template on trunk. For PNNI SES NNI trunk, the service class template should be set to 3. Detail of service class template can be found in Appendix C.
Step 5 Use the cnfrsrc command to set resources on the port.
A system response similar to the following example occurs:
oriobpx1 TN StrataCom BPX 8620 9.2.3U Feb. 16 2000 21:33 PST
Port/Trunk :1.2
Maximum PVC LCNS: 256 Maximum PVC Bandwidth:2207
(Statistical Reserve:1000)
Partition 1
Partition State : Enabled
Minimum VSI LCNS: 3000
Maximum VSI LCNS: 7000
Start VSI VPI: 2
End VSI VPI : 4095
Minimum VSI Bandwidth : 100000 Maximum VSI Bandwidth : 350000
VSI ILMI Config : 0
Last Command:cnfrsrc 1.2 256 2207 y 1 e 3000 7000 2 4095 100000 350000
|
Note For more information about the configure resources command, refer to the Cisco WAN Switching Command Reference for Release 9.2. |
Step 6 Use the cnftrk command to enable ILMI protocol to run on the BXM card.
----------------------------------------------------------------------------oriobpx3 TN StrataCom BPX 8620 9.2.3U Feb. 17 2000 08:22 PST
TRK 1.2 Config OC3 [353207cps] BXM slot: 1
Transmit Rate: 353208 VPC Conns disabled: No
Protocol By The Card: Yes Line framing: STS-3C
VC Shaping: No coding: --
Hdr Type NNI: Yes recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: --
Connection Channels: 256 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
SVC Vpi Min: 0 HCS Masking: Yes
SVC Channels: 0 Payload Scramble: Yes
SVC Bandwidth: 0 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
----------------------------------------------------------------------------
Step 7 Use the cnfvsipart command to enable VSI ILMI.
Example:
----------------------------------------------------------------------------
oriobpx3 TN StrataCom BPX 8620 9.2.3U Feb. 17 2000 08:25 PST
Trunk:1.2 Partn:1 ILMI:E LCN:1 Topo:BPX NW IP
Last Command: cnfvsipart 1.2 1 y
-------------------------------------------------------------------------------
The BXM now sends a VSI trap to the SES PNNI controller.
When the SES PNNI controller receives the trap, it sends a VSI passthrough back to the BXM to enable auto-configuration. The information in the passthrough includes auto-configuration default parameters.
The BXM then starts the ILMI protocol with the attached BXM port. The BXM will then send the SES PNNI controller the port information: vpi/vci range, interface type, device type, ILMI version, and NNI Signaling version.
Finally, the PNNI Controller starts the PNNI signaling stacks.
Note that all ILMI features on SES PNNI are default to be on, there is NO need to use cnfautocnf to enable ILMI features on SES PNNI.
Step 8 Use the dspvsipartcnf command to view VSI ILMI functionality status (whether enabled or not) for various VSI partitions on the interface.
Example:
----------------------------------------------------------------------------
oriobpx3 TN StrataCom BPX 8620 9.2.3U Feb. 17 2000 08:29 PST
Trunk:1.2 Partn:1 ILMI:E LCN:1 Topo:BPX NW IP
Trunk:1.2 Partn:2 -- VSI partition DISABLED
Trunk:1.2 Partn:3 -- VSI partition DISABLED
Sys_Id generated = 38.33.39.33.36.33
Last Command: dspvsipartcnf 1.2
----------------------------------------------------------------------------
Use the following procedure to preconfigure specific parameters before a trunk is brought up with AutoConfiguration.
Use the SES PNNI Controller CLI to perform steps 1 through 3.
|
Note Ports are administratively down, by default. |
Step 2 Modify the appropriate parameter with one of the following PNNI Controller cnf commands:
|
Note The modified parameters will be used by autoconfiguration to negotiate a common parameters with its peer ILMI IME(Interface Management Entity). |
Step 3 Use the uppnport command to up the PNNI port.
|
Note The signaling stacks are not yet brought up because the port configuration has not yet been received from the BXM. |
Use the BPX CLI to perform steps 4 through 8.
Step 4 Use the uptrk command at the BPX CLI to bring up the trunk.
Step 5 Use the addtrk command at the BPX CLI to add AutoRoute.
Step 6 Use the cnfvsiif command at the BPX CLI to configure PNNI service template, 3.
Step 7 Use the cnfrsrc command to set resources on the port.
Step 8 Use the cnftrk command to enable ILMI protocol on BXM port.
Step 9 Use the cnfvsipart command to bring up the port.
The following results occur:
a. The BXM now sends a VSI trap to the SES PNNI controller.
b. The PNNI Controller starts the PNNI signaling stacks:
Use the BPX CLI to configure VSI on BXM ports or trunks. For more information about the VSI protocol, see "Virtual Switch Interface."
A default Service Class Template is assigned to a logical interface when the interface is upped using the upport and uptrk commands.
For example:
In the above example, the default template has the identifier of 1. You can change the default Service Class Template---from Service Class Template 1---to another Service Class Template by using the cnfvsiif command. Use the dspvsiif command to view a template associated with a specified interface.
For example:
The cnfvsiif command assigns a selected Service Class Template to an interface (VI) by specifying the template number.:
cnfvsiif <slot.port.vtrk> <tmplt_id>The dspvsiif command presents the type of Service Class Template assigned to an interface (VI)
dspvsiif <slot.port.vtrk>The default Service Class Template is assigned to the interface (VI) when an interface (VI) is activated by the uptrk or upport commands. The corresponding Qbin template is then copied into the data structure of that interface at the BXM.
You can change some of the Qbin parameters by using the cnfqbin command. The Qbin is now "user configured" as opposed to "template configured." This information may be viewed on the dspqbin screen.
The available Qbin parameters are shown in Table 10-1.
Qbins available for VSI are restricted to Qbins 10-15 for that interface.
All 32 possible virtual interfaces are provided with 16 Qbins.
| Template Object Name | Template Units | Template Range/Values |
|---|---|---|
QBIN Number | enumeration | 0 -15 (10-15 valid for VSI) |
Max QBIN Threshold | u sec | 1-2000000 |
QBIN CLP High Threshold | % of max Qbin threshold | 0 - 100 |
QBIN CLP Low Threshold | % of max Qbin threshold
| 0 - 100 |
EFCI Threshold | % of max Qbin threshold | 0 - 100 |
Discard Selection | enumeration
| 1 - CLP Hystersis 2 - Frame Discard |
Weighted Fair Queueing | enable/disable | 0: Disable 1: Enable |
Additional Service Class Template commands are described in Table 10-2.
dspsctmplt: | Use this command to view the template number assigned to an interface. The command has three levels of operation: |
| Use this command without arguments to view all current templates. |
| Use this command to view all service classes in the template. |
| Use this command to view all Service Classes in the template. |
cnfqbin | Use this command to set parameters for the Qbin. You can elect to use the card Qbin values from the Qbin templates, by typing yes when prompted. |
dspqbin | Use this command to view Qbin parameters currently configured for the virtual interface. |
dspcd | Use this command to view current card configuration |
Currently, VSI ILMI functionality can be enabled both on line (port) interfaces and trunk interfaces. VSI ILMI functionality cannot be enabled on trunks to which feeders or VSI controllers are attached.
The following commands enable VSI ILMI Functionality on specified line or port.
The following commands enable VSI functionality on specified trunk interfaces.
The following commands enable VSI ILMI functionality on virtual trunk interfaces.
|
Note ILMI automatically runs on the BXM card for virtual trunks and, is therefore not configurable. |
|
Note VSI ILMI can be enabled for only one VSI partition on trunk interfaces. |
The following command enables view of the current VSI ILMI functionality on a specified interface.
The recommended configuration sequence for each SES PNNI node in the switched system is outlined in Figure 10-2.
All tasks are configurable using the SES PNNI Controller CLI. Some of the tasks, as indicated in Figure 10-2, can be configured using CiscoView.
For more information about:
Use the commands in this section to set up the PNNI Node, and to set the following node parameters:
Syntax Description s
addpnni-node <node-index>
cnfpnni-node <node-index>
Before changing a node index configuration, node index must be disabled. Use
cnfpnni-node <node-index> -enable false to disable the node index, and use
cnfpnni-node <node-index> -enable true to enable the node index.
Use dsppnni-node <node-index> to display a PNNI node configuration.
Example:
----------------------------------------------------------------------------
orioses1.1.1.PXM.a > dsppnni-node 1
node index: 1 node name:
Level............... 56 Lowest.............. true
Restricted transit.. off Complex node........ off
Branching restricted on
Admin status........ up Operational status.. up
Non-transit for PGL election.. off
Node id...............56:160:47.00918100000000d058ac26b6.00d058ac26b6.01
ATM address...........47.00918100000000d058ac26b6.00d058ac26b6.01
Peer group id.........56:47.00.9181.0000.0000.0000.0000.00
----------------------------------------------------------------------------
Related Commands
In CiscoView:
Use the command in this section to set the following peer group leader parameters:
Syntax Description
cnfpnni-election <node-index> -<parameter> <number>
Example: set leadership priority
cnfpnni-election 1 -priority 1
Use dsppnni-election <node-index> to display peer group leader election set up.
Example:
-------------------------------------------------------------------------------
ORSES17.1.1.PXM.a > dsppnni-election 1
node index:1
PGL state...... OperPgl Init time(sec)....... 15
Priority....... 51 Override delay(sec).. 30
Re-election time(sec) 15
Pref PGL...............56:160:47.00918100000000d058ac2613.00d058ac2613.01
PGL....................56:160:47.00918100000000d058ac2613.00d058ac2613.01
Active parent node id..40:56:47.009181111111111111111111.00d058ac2613.00
----------------------------------------------------------------------------
In CiscoView:
Use the commands in this section to set the following parameters to define timers and thresholds for the PNNI node:
Syntax Description
cnfpnni-timer <node-index> -<parameter> <number>
Example: set PTSE refresh interval
orioses1.1.1.PXM.a > cnfpnni-timer 1 -ptseRefreshInterval 1000
Use dsppnni-timer <node-index> to display timer set up:
Example:
----------------------------------------------------------------------------
orioses1.1.1.PXM.a > dsppnni-timer 1
node index:1
Hello holddown(100ms)... 10 PTSE holddown(100ms)... 10
Hello int(sec).......... 15 PTSE refresh int(sec).. 1000
Hello inactivity factor. 5 PTSE lifetime factor... 200
Retransmit int(sec)..... 5
AvCR proportional PM.... 50 CDV PM multiplier...... 25
AvCR minimum threshold.. 3 CTD PM multiplier...... 50
Peer delayed ack int(100ms)................... 10
Logical horizontal link inactivity time(sec).. 120
----------------------------------------------------------------------------
Related Commands
In CiscoView:
Use the commands in this section to set the following SVCC-Based RCC-Timer parameters for the PNNI node:
Syntax Description
cnfpnni-svcc-rcc-timer <node-index>
Use the command in this section to set summary address parameters for the PNNI node.
Syntax Description
addpnni-summary-addr <node-index> address-prefix prefix-length
This command is not available in CiscoView.
Example:
orioses1.1.1.PXM.a > addpnni-summary-addr 1 47.0091.8100.0000.1111.2222 88
Use dsppnni-summary-addr <node-index> to display summary addresses.
Example:
-------------------------------------------------------------------------------
orioses1.1.1.PXM.a > dsppnni-summary-addr 1
node index:1
Type.............. internal Suppress.............. false
State............. advertising
Summary address........47.0091.8100.0000.00d0.58ac.26b6/104
node index:1
Type.............. internal Suppress.............. false
State............. inactive
Summary address........47.0091.8100.0000.1111.2222/88
-------------------------------------------------------------------------------
Related Commands
In CiscoView:
Use the commands in this section to set the following routing policy parameters for the lowest level PNNI node.
Syntax Description
cnfpnni-routing-policy
This command is not available in CiscoView
Use the commands in this section to set the following PNNI interface parameters on the PNNI node:
Syntax Description
cnfpnni-intf <slot.port> -<parameter> <number>
This command is not available in CiscoView.
Example: configure CBR AW on an interface
orioses1.1.1.PXM.a > cnfpnni-intf 1.3 -awcbr 10000
Use dsppnni-intf <slot.port> to display an PNNI interface set up.
Example:
-------------------------------------------------------------------------------
orioses1.1.1.PXM.a > dsppnni-intf 1.3
Physical port id:1.3 Logical port id: 66304
Aggr token.......... 0 AW-NRTVBR........... 5040
AW-CBR.............. 10000 AW-ABR.............. 5040
AW-RTVBR............ 5040 AW-UBR.............. 5040
-------------------------------------------------------------------------------
Use the commands in this section to set the following locally reachable address parameters for the lowest level PNNI node:
Syntax Description
dsppnni-reachable-addr <local/network>
|
Note There are three types local addresses: (1) ILMI registered addresses, (2) user provisioned addresses via addaddr CLI, and (3) host application addresses (such as AESA-Ping, PNNI LGN, IP connectivity and similar). |
This command is not available in CiscoView.
Example:
----------------------------------------------------------------------------
orioses1.1.1.PXM.a > dsppnni-reachable-addr local
scope............... 0 port id............. -1
Exterior............ false
ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.0000.0001.0200/152
scope............... 0 port id............. -1
Exterior............ false
ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.0000.0001.0300/152
scope............... 0 port id............. -1
Exterior............ false
ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.0000.0001.0600/152
scope............... 0 port id............. -1
Exterior............ false
ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.0000.0001.0800/152
scope............... 0 port id............. -1
Exterior............ false
ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.00d0.58ac.26b6/152
orioses1.1.1.PXM.a > dsppnni-reachable-addr network
scope............... 0 Advertising node number 2
Exterior............ false
ATM addr prefix.....47.0091.8100.0000.0010.7bc1.54b5/104
Advertising nodeid..56:160:47.00918100000000107bc154b5.00107bc154b5.01
----------------------------------------------------------------------------
Use the commands in this section to display the following link and Hello related information:
Syntax Description
dsppnni-link [node-index [slot.port]]
Example:
----------------------------------------------------------------------------
orioses3.1.1.PXM.a > dsppnni-link 1
node index :1
Local port id: 66048 Remote port id: 66048
Type. lowestLevelHorizontalLink Hello state....... twoWayInside
Derive agg........... 0 Intf index........... 66048
SVC RCC index........ 0 Hello pkt RX......... 1248753
Hello pkt TX......... 1234565
Remote node id.........56:160:47.00918100000000d058ac26b6.00d058ac26b6.01
Upnode id..............0:0:00.000000000000000000000000.000000000000.00
Upnode ATM addr........00.000000000000000000000000.000000000000.00
Common peer group id...00:00.00.0000.0000.0000.0000.0000.00
------------------------------------------------------------------------------
After setting up the UNI ports, NNI trunks, and PNNI, you are ready to setup SVC and SPVC in a network. This section will explain how to set up an SVC. A two-node network is used to describe the SVC set up procedure.
Assuming CPE #1 has ATM address:47.00918100000000d058ac26b6.000000010800.00
Assuming CPE #2 has ATM address:47.00918100000000107bc154b5.000000010300.00
Using the following procedures to set up addresses on orioses1 and orioses3 before place the SVC call.
orioses3.1.1.PXM.a > addaddr 1.3 47.00918100000000d058ac26b6.000000010800.00 160
Add ATM summary address on orioses3:
orioses3.1.1.PXM.a > addpnni-summary-addr 1 47.00918100000000d058ac26b6 104
Step 2 Add CPE #2 ATM address on orioses1 UNI port 1.8:
orioses1.1.1.PXM.a > addaddr 1.8 47.00918100000000107bc154b5.000000010300.00 160
Add ATM summary address on orioses1:
orioses1.1.1.PXM.a > addpnni-summary-addr 1 47.00918100000000107bc154b5 104
Step 3 Use dsppnni-reachable-addr network to see the summary address of the other node.
Step 4 Place a SVC call from CPE #1 to CPE #2
Use dsppncons to display SVC connection between two nodes.
------------------------------------------------------------------------------
orioses3.1.1.PXM.a > dsppncons
Port VPI VCI CallRef X-Port VPI VCI CallRef Type OAM-Type
1.2 1 42 11 1.3 99 999 11 PTP Yes
Calling-Addr:47.00918100000000d058ac26b6.000000010800.00
Called-Addr:47.00918100000000107bc154b5.000000010300.00
1.3 99 999 11 1.2 1 42 11 PTP Yes
Calling-Addr:47.00918100000000d058ac26b6.000000010800.00
Called-Addr:47.00918100000000107bc154b5.000000010300.00
------------------------------------------------------------------------------
Use the following procedures to setup SVC with ILMI address registration:
Configure orioses1 UNI 1.8 with ILMI enabled (cnfport)
Make sure both CPE#1 and CPE#2 have ILMI turned on.
Step 2 Add Address Prefix on orioses3 and orioses1
orioses3.1.1.PXM.a > addprfx 1.3 47.00918100000000d058ac26b6 orioses1.1.1.PXM.a > addprfx 1.8 47.00918100000000107bc154b5
Step 3 Use dsppnni-reachable-addr local to see the registered address
Step 4 Place an SVC call from CPE #1 to CPE #2 with ATM address:
47.00918100000000d058ac26b6.00d058ac4021.00
There are two ways to provision an SPVC: using CLI on PNNI Controller or using CWM. Using CWM to provision an SPVC will be documented in Network Management Chapter. This section will use a step-by-step example to illustrate how to use the PNNI Controller CLI to provision an SPVC.
Before setting up SPVC, user should check if the SPVC Node Prefix has been configured or if the SPVC Node Prefix to be used for SPVCs. If it is not, use the following procedures to change it.
Use the "cnfspvcprfx" command to configure the Nodal SPVC Prefix
pswpop4.1.1.PXM.a > dspspvcprfx
SPVC Node Prefix: 47.00918100000000107bc15339
pswpop4.1.1.PXM.a > cnfspvcprfx -prfx 4700918100000000c043002ddf
pswpop4.1.1.PXM.a > dspspvcprfx
SPVC Node Prefix: 47.00918100000000c043002ddf
One can only configure an SPVC prefix when there is no connection on the node. The SPVC prefix must be unique across the network.
Reference to Figure 10-4 and use the following procedure to add an SPVC in a PNNI network.
pswpop9.1.PXM.a > addcon 9.8 111 111 1 2
LOCAL ADDR: 4700918100000000C043002DDF00000009080000.111.111
The LOCAL ADDR is the slave endpoint ATM address to be used at the master endpoint to setup an SPVC to the slave endpoint. Please note, service_type is selected to be 1 i.e. CBR service. The mastership is 2=slave.
Use "dspcon" to show the slave endpoint configuration.
pswpop9.1.PXM.a > dspcon 9.8 111 111
Port Vpi Vci Owner State
-------------------------------------------------------------------------
Local 9:-1.8:-1 111.111 SLAVE FAIL
Address: 47.00918100000000c043002ddf.000000090800.00
Remote Routed 0.0 MASTER --
Address: 00.000000000000000000000000.000000000000.00
-------------------- Provisioning Parameters --------------------
Connection Type: VCC Cast Type: Point-to-Point
Service Category: CBR Conformance: CBR.1
Bearer Class: BCOB-X
Last Fail Cause: Invalid Attempts: 0
Continuity Check: Disabled Frame Discard: Disabled
L-Utils: 0 R-Utils: 0 Max Cost: 0 Routing Cost: 0
---------- Traffic Parameters ----------
Tx PCR: 50 Rx PCR: 50
Tx SCR: 50 Rx SCR: 50
Tx MBS: 1024 Rx MBS: 1024
Tx CDVT: 250000 Rx CDVT: 250000
Tx CDV: N/A Rx CDV: N/A
Tx CTD: N/A Rx CTD: N/A
Type <CR> to continue, Q<CR> to stop:
------- SES Parameters only ----------
Tx AIS: 1 Rx AIS: 0 Rx Abit:0
lpbk_type : No Loopback
lpbk_dir : ----
lpbk_status : None
round trip delay: 0 usec
Stats : Disabled
Step 2 Use "addcon" command to add an SPVC Master EndPoint.
svcswp20.1.PXM.a > addcon 5.3 111 111 1 1 4700918100000000C043002DDF00000009080000.111.111
When the master endpoint is added, the SPVC Manager on SES controller will use the slave endpoint ATM address to setup an SPVC towards the slave endpoint. The mastership is 1 = master.
#### MASTER END POINT AFTER MASTER SPVC ADDED ####
svcswp20.1.PXM.a > dspcon 5.3 111 111
Port Vpi Vci Owner State
-------------------------------------------------------------------------
Local 5:-1.3:-1 111.111 MASTER OK
Address: 47.009181000000003071f8021e.000000050300.00
Remote Routed 111.111 SLAVE --
Address: 47.00918100000000c043002ddf.000000090800.00
-------------------- Provisioning Parameters --------------------
Connection Type: VCC Cast Type: Point-to-Point
Service Category: CBR Conformance: CBR.1
Bearer Class: BCOB-X
Last Fail Cause: SPVC Established Attempts: 0
Continuity Check: Disabled Frame Discard: Disabled
L-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 10080
---------- Traffic Parameters ----------
Tx PCR: 50 Rx PCR: 50
Tx SCR: 50 Rx SCR: 50
Tx MBS: 1024 Rx MBS: 1024
Tx CDVT: 250000 Rx CDVT: 250000
Tx CDV: N/A Rx CDV: N/A
Tx CTD: N/A Rx CTD: N/A
Type <CR> to continue, Q<CR> to stop:
------- SES Parameters only ----------
Tx AIS: 0 Rx AIS: 0 Rx Abit:0
lpbk_type : No Loopback
lpbk_dir : ----
lpbk_status : None
round trip delay: 0 usec
Stats : Disabled
#### SLAVE END POINT AFTER MASTER SPVC ADDED ####
pswpop9.1.PXM.a > dspcon 9.8 111 111
Port Vpi Vci Owner State
-------------------------------------------------------------------------
Local 9:-1.8:-1 111.111 SLAVE OK
Address: 47.00918100000000c043002ddf.000000090800.00
Remote Routed 111.111 MASTER --
Address: 47.009181000000003071f8021e.000000050300.00
-------------------- Provisioning Parameters --------------------
Connection Type: VCC Cast Type: Point-to-Point
Service Category: CBR Conformance: CBR.1
Bearer Class: BCOB-X
Last Fail Cause: SPVC Established Attempts: 0
Continuity Check: Disabled Frame Discard: Disabled
L-Utils: 0 R-Utils: 0 Max Cost: 0 Routing Cost: 0
---------- Traffic Parameters ----------
Tx PCR: 50 Rx PCR: 50
Tx SCR: 50 Rx SCR: 50
Tx MBS: 1024 Rx MBS: 1024
Tx CDVT: 250000 Rx CDVT: 250000
Tx CDV: N/A Rx CDV: N/A
Tx CTD: N/A Rx CTD: N/A
Type <CR> to continue, Q<CR> to stop:
------- SES Parameters only ----------
Tx AIS: 0 Rx AIS: 0 Rx Abit:0
lpbk_type : No Loopback
lpbk_dir : ----
lpbk_status : None
round trip delay: 0 usec
Stats : Disabled
Use the following procedure to modify an SPVC in a PNNI network. When an SPVC endpoint is modified, SPVC manager will re-establish the SPVC based on the new endpoint setup.
Example:
-------------------------------------------------------------------------------
###### CNFCON for local PCR and remote PCR at Master Endpoint 1.8 ####
orioses1.1.1.PXM.a > cnfcon 1.8 100 1000 -lpcr 5000 -rpcr 5000
orioses1.1.1.PXM.a > dspcon 1.8 100 1000
Port Vpi Vci Owner State
-------------------------------------------------------------------------
Local 1:-1.8:-1 100.1000 MASTER OK
Address:47.00918100000000d058ac26b6.000000010800.00
Remote Routed 99.999 SLAVE OK
Address:47.00918100000000107bc154b5.000000010300.00
-------------------- Provisioning Parameters --------------------
Connection Type:VCC Cast Type:Point-to-Point
Service Category:CBR Conformance:CBR.1
Bearer Class:BCOB-X
Last Fail Cause:SPVC Established Attempts:0
Continuity Check:Disabled Frame Discard:Disabled
L-Utils:100 R-Utils:100 Max Cost:-1 Routing Cost:10080
---------- Traffic Parameters ----------
Tx PCR: 5000 Rx PCR: 5000
Tx SCR: 1000 Rx SCR: 1000
Tx MBS: 1024 Rx MBS: 1024
Tx CDVT:250000 Rx CDVT:250000
Tx CDV: N/A Rx CDV: N/A
Tx CTD: N/A Rx CTD: N/A
Type <CR> to continue, Q<CR> to stop:
------- SES Parameters only ----------
Tx AIS:0 Rx AIS:0
lpbk_type :No Loopback
lpbk_dir :----
lpbk_status :None
round_trip_delay:0
Stats :Disabled
###### CNFCON for local PCR and remote PCR at Slave Endpoint 1.3 ####
orioses3.1.1.PXM.a > cnfcon 1.3 99 999 -lpcr 5000 -rpcr 5000
orioses3.1.1.PXM.a > dspcon 1.3 99 999
Port Vpi Vci Owner State
-------------------------------------------------------------------------
Local 0:0.0:0 99.999 SLAVE OK
Address:47.00918100000000d058ac26b6.000000010800.00
Remote Routed 100.1000 MASTER OK
Address:47.00918100000000107bc154b5.000000010300.00
-------------------- Provisioning Parameters --------------------
Connection Type:VCC Cast Type:Point-to-Point
Service Category:CBR Conformance:CBR.1
Bearer Class:BCOB-X
Last Fail Cause:SPVC Established Attempts:0
Continuity Check:Disabled Frame Discard:Disabled
L-Utils:0 R-Utils:0 Max Cost:0 Routing Cost:0
---------- Traffic Parameters ----------
Tx PCR: 5000 Rx PCR: 5000
Tx SCR: 1000 Rx SCR: 1000
Tx MBS: 1024 Rx MBS: 1024
Tx CDVT:250000 Rx CDVT:250000
Tx CDV: -1 Rx CDV: -1
Tx CTD: -1 Rx CTD: -1
Type <CR> to continue, Q<CR> to stop:
------- SES Parameters only ----------
Tx AIS:0 Rx AIS:0
lpbk_type :No Loopback
lpbk_dir :----
lpbk_status :None
round_trip_delay:0
Stats :Disabled
-------------------------------------------------------------------------------
Use the delcon slot.port <vpi> <vci> to delete an SPVC endpoints.
To delete an SPVC, delete the master endpoint first, then delete the slave endpoint for each SPVC.
Use a VCI of 0 to add an SPVP connection.
Example:
pswpop9.1.PXM.a > addcon 5.3 10 0 1 2 LOCAL ADDR:4700918100000000C043002DDF00000005030000.10.0 pswpop9.1.PXM.a > addcon 5.3 11 0 1 1 4700918100000000C043002DDF00000005030000.10.0 pswpop9.1.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner ----------------------------+-----------------------------+-------+------ 5.3 2 200 5.3 3 300 OK SLAVE Local Addr:47.00918100000000c043002ddf.000000050300.00 Remote Addr:47.00918100000000c043002ddf.000000050300.00 5.3 3 300 5.3 2 200 OK MASTER Local Addr:47.00918100000000c043002ddf.000000050300.00 Remote Addr:47.00918100000000c043002ddf.000000050300.00 5.3 10 0 5.3 11 0 OK SLAVE Local Addr:47.00918100000000c043002ddf.000000050300.00 Remote Addr:47.00918100000000c043002ddf.000000050300.00 5.3 11 0 5.3 10 0 OK MASTER Local Addr:47.00918100000000c043002ddf.000000050300.00 Remote Addr:47.00918100000000c043002ddf.000000050300.00
In this example, the SPVP is looped back on the same port. An SPVP connection can not be added if a VCC connection exists with same VPI.
Use the following configuration to enable SPVC stats collection on an SES:
Check the snmp configuration both on BCC and PXM e.g: community strings and Network IP addresses and ATM IFIP.
Step 2 Setting stats level on BCC:
Syntax: "cnfcdparm <slotId> <stat-level>"
Ensure that there are no connections on the BXM when this command is executed. Reset of the BXM
is required for the new stats level to take effect.
Step 3 Add SPVC connections with stats enabled
Ensure that "-stats enable" option is given to the commands "addcon" to add SPVC connections with stats enabled. If we want to enable stats on existing SPVCs, modify the connections with "cnfcon" and give "-stats enable" option with this command.
Step 4 Stats configuration on CWM:
a. telnet to the PXM card and setup CWM's IP address for stats using "cnfstatsmgr"
In the SCM GUI (e.g. "runScmGui <host>"):
b. click node tab
c. navigate a node; for example, nmsbpx14.
d. telnet nmsbpx14
e. cnfstatmast <your scmctrlsvr host ip>
f. enable stat by edit default parameters.
g. add the required stat id's and start collecting.
h. wait more than 15 minutes to see if any stats file has been collected.
Step 5 If after 30 minutes no file is being collected:
check the error logs for any error messages.
For the installation of SCM GUI check the CWM configuration guide. There should be section on installations e.g:
a. installation CWM.
b. add user information in node_info table.
c. install SCM.
d. Run SCM GUI
Posted: Thu Jul 27 19:46:12 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.