IISP

This section covers IISP configuration. A new PNNI node that is part of a PNNI private network will be joined to your network using an IISP interface. The topology is shown in Figure 11-9.

Figure 11-9. IISP Configuration

The LS-1010 has the following ATM address, as Example 11-23 shows.

Example 11-23. Changing the ATM Address

 IOS_pnni_node(config)#atm address 49.FEE4DECAFC0FFEE4BED2FEED.DAD000001010.00 

The first configuration step is to bring up a line, port, and resource partition in interface 12.1 in BPX-SES PNNI node. An ATMF service class template (SCT) also needs to be assigned to the VSI resource partition.

As soon as the physical and ATM layers are up, you can start the IISP-specific configuration. Essentially, two tasks are required for IISP configuration:

• Configure the PnPort signaling to IISP, selecting a side (IISP is asymmetric. It has network and user sides).

• Configure a static route pointing to the remote prefix out of the IISP interface.

In IISP, the network side allocates VPI/VCI to avoid collisions. IISP's routing face supports crankback generation and load balancing over multiple IISP links and multiple addresses. IISP's signaling side supports simple call-control mechanisms to provide QoS support.

To carry out the first step and configure IISP signaling, you use the command cnfpnportsig in the SES controller with the PnPort administratively down to select the IISP version 3.1 side network. See Example 11-24.

Example 11-24. Configuring IISP Signaling

 SES-3a.1.PXM.a > dnpnport 12.1 SES-3a.1.PXM.a > cnfpnportsig 12.1 -nniver iisp31 -side network SES-3a.1.PXM.a > uppnport 12.1 SES-3a.1.PXM.a > dsppnportsig 12.1 provisioned IF-type: nni   version:     iisp31 sigType:  private          side:        network addrPlan:  aesa VpiVciAllocator:  n/a      HopCounterGen:  n/a PassAlongCapab:  enable sigVpi:          0         sigVci:             5 rccVpi:        n/a         rccVci:           n/a svc routing priority: 8 SES-3a.1.PXM.a > 

On the Cisco IOS Software PNNI node, you need to disable autoconfiguration and use the interface-level command atm iisp, as Example 11-25 shows.

Example 11-25. Configuring IISP Signaling

 IOS_pnni_node#conf t Enter configuration commands, one per line.  End with CNTL/Z. IOS_pnni_node(config)#interface ATM0/0/0 IOS_pnni_node(config-if)#no atm auto-configuration IOS_pnni_node(config-if)#atm iisp side user version 3.1 IOS_pnni_node(config-if)#exit 

The first task is complete.

In the second task, you need to configure a static route. In the SES controller, this task is accomplished with the command addaddr. For IISP configuration, the configured protocol needs to be static, and the type needs to be external. Also, the static route needs to be redistributed into the PNNI routing process so that remote PNNI nodes learn this route. You do this by setting the parameter redst to yes. See Example 11-26. In this case, 8 bits is enough to make this prefix unique, because the remote network uses a different address plan.

Example 11-26. Configuring Static Routes for IISP

 SES-3a.1.PXM.a > addaddr 12.1 49 8 -proto static -type ext -redst yes SES-3a.1.PXM.a > dspaddr 12.1 49 length: 8      type: exterior      proto: static scope: 0       plan: nsap_e164     redistribute: true transit network id: SES-3a.1.PXM.a > 

The second task is performed in the Cisco IOS Software platform using the command atm route (see Example 11-27). The static ATM route also needs to be redistributed under the PNNI process. You can see the redistribution status of static routes within the PNNI routing process using the command show atm pnni local-node.

Example 11-27. Configuring Static Routes for IISP

 IOS_pnni_node(config)#atm route 47 ATM 0/0/0 IOS_pnni_node(config)#atm router pnni IOS_pnni_node(config-atm-route)#node 1 IOS_pnni_node(config-pnni-node)#redistribute atm-static IOS_pnni_node(config-pnni-node)#^Z IOS_pnni_node# IOS_pnni_node#show atm pnni local-node 1 | incl static   Redistributing static routes: Yes IOS_pnni_node# 

The IISP link is now ready. You can go to the MGX-8950 and check the PNNI routing table as well as reachability to the IISP linked PNNI network. See Example 11-28.

Example 11-28. Checking the PNNI Routing Table

 m8950-7b.7.PXM.a > dsppnni-reachable-addr network scope...............         0     Advertising node number         5 Exterior............     false ATM addr prefix.....47.0000.0000.0000.0100.01/80 Transit network id.. Advertising nodeid..64:80:47.000000000000010001000000.00d058ac2828.00 Node name...........SES-3a-02 scope...............         0     Advertising node number         2 Exterior............     false ATM addr prefix.....47.0000.0000.0000.0100.0200.8850/104 Transit network id.. Advertising nodeid..80:160:47.000000000000010002008850.00309409f6ba.01 Node name...........m8850-7a scope...............         0     Advertising node number         5 Exterior............      true ATM addr prefix.....49/8 Transit network id.. Advertising nodeid..64:80:47.000000000000010001000000.00d058ac2828.00 Node name...........SES-3a-02 m8950-7b.7.PXM.a > 

The output of the command dsppnni-reachable-addr is also a good way to check address summarization.

You can also use the command aesa_ping to verify connectivity with the other network.

The closing portion of the IISP configuration includes creating an SPVC with each endpoint in a different PNNI network traversing the IISP link. SPVC signaling also goes across the IISP link. As Example 11-29 shows, you need only a master SPVC endpoint, because the remote PNNI node implements a single-endpoint SPVC model.

Example 11-29. Adding an SPVC Traversing the IISP Link

 SES-3a.1.PXM.a > addcon 12.2 10 100 11 1   49FEE4DECAFC0FFEE4BED2FEEDDAD00000101000.10.100 -lpcr 1000 -rpcr 1000 SES-3a.1.PXM.a > dspcon 12.2 10 100 Port                   Vpi Vci             Owner      State      Persistency ---------------------------------------------------------------------------- Local  12:-1.2:-1      10.100              MASTER     OK         Persistent        Address: 47.000000000000010001008600.0000000c0200.00        Node name: SES-3a Remote Routed          10.100              SLAVE       --        Persistent        Address: 49.FEE4DECAFC0FFEE4BED2FEED.DAD000001010.00        Node name: <SNIP> SES-3a.1.PXM.a > 

The remote SPVC endpoint can be seen from the remote node, as shown in Example 11-30.

Example 11-30. Looking at the SPVC Endpoint

 IOS_pnni_node#show atm vc interface ATM 0/0/0 10 100 Interface: ATM0/0/0, Type: oc3suni VPI = 10  VCI = 100 Status: UP Time-since-last-status-change: 00:01:21 Connection-type: SoftVC Cast-type: point-to-point Hold-priority: none  Soft vc location: Destination  Remote ATM address: 47.0000.0000.0000.0100.0100.8600.0000.000c.0200.00  Remote VPI: 10  Remote VCI: 100  Soft vc call state: Active Packet-discard-option: disabled Usage-Parameter-Control (UPC): pass Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states:  Not-applicable Cross-connect-interface: ATM0/0/0, Type: oc3suni Cross-connect-VPI = 0 Cross-connect-VCI = 90 Cross-connect-UPC: pass Cross-connect OAM-configuration: disabled Cross-connect OAM-state:  Not-applicable Rx cells: 0, Tx cells: 0 Rx connection-traffic-table-index: 2147483641 Rx service-category: CBR (Constant Bit Rate) Rx pcr-clp01: 424 Rx scr-clp01: none Rx mcr-clp01: none Rx      cdvt: 1024 (from default for interface) Rx       mbs: none Tx connection-traffic-table-index: 2147483641 Tx service-category: CBR (Constant Bit Rate) Tx pcr-clp01: 424 Tx scr-clp01: none Tx mcr-clp01: none Tx      cdvt: none Tx       mbs: none IOS_pnni_node# 

Because you configured 1000 cells per second (CPS) for the local and remote PCR values, the Cisco IOS Software PNNI node shows 424 kilobits per second (Kbps).