Cabletron Systems 6500 Manual Do Utilizador

5-2   SmartSwitch 6500 User Guide

IISP Routes

  Routing

The 

 command allows you to specify a set of metrics to be used with 

the route. For more information on metrics and metric tags, see Section 5.4, Route 
Metrics.

Enter the 

 command to determine whether the route was created:

Smart6500 # show atmroute

AddressNumber(ALL)                        :

No. Port Route Address                                            Type Protocol

================================================================================

1   7B4  39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:d4:14:41:80   I   MGMT

2   7B4  39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:d4:14:41:81   I   MGMT

3    --  39:00:00:00:00:00:00:00:00:00:14:59:00                     I   PNNI

4    --  39:00:00:00:00:00:00:00:00:00:28:e9:80                     I   PNNI

5    --  39:00:00:00:00:00:00:00:00:00:28:f5:00                     I   PNNI

6   7B4  47:00:79:00:00:00:00:00:00:00:00:00:00:00:a0:3e:00:00:01   I   MGMT

7   5B2  52:00:00:00:00:00:00:00:00:00:14:51:80                     I   MGMT  

< This is our route

Smart6500 #

The route to the IISP device appears as 

, and with Protocol Type of 

 (management).

Create a route on the IISP device that refers to the netprefix 
(

39:00:00:00:00:00:00:00:00:00:14:41:80

) of port 

 on the SmartSwitch 6500.

For IISP routes to work with certain devices, ILMI may also need to be disabled 
on the SmartSwitch 6500. Use the 

 command to disable ILMI on 

the SmartSwitch 6500 on a per-port basis.

5.2.1

IISP Routing Considerations

When creating routes between the SmartSwitch 6500 (running PNNI) and IISP devices, the criteria that characterize 
IISP connectivity still apply. To reach a SmartSwitch 6500 within the PNNI domain, the IISP device must have a 
configured route that points directly to a port on the target SmartSwitch 6500. Conversely, there must be a SmartSwitch 
6500 that has a direct physical link (and a route over that link) to the IISP device. The following two examples illustrate 
this point.

IISP Routing Example One

In Figure 5-1 Switch A is an IISP device connected to the PNNI domain through Switch B. Switch A contains an LEC, 
which is a member of an ELAN whose LECS is on Switch C (within the PNNI domain). If the LEC on Switch A is to 
make contact with the LECS on Switch C, Switch A must contain an IISP route directly to switch C. Furthermore, 
Switch B must contain a route to switch A over the physical link that connects the two switches.