Cabletron Systems 04-0053-01 Switch User Manual


 
4-2 SmartSwitch ATM User Guide
IISP Routes Routing
Note For IISP routes, always set the Type parameter of the add atmroute command to
external. This indicates that the route is external to the PNNI domain.
Note The add atmroute command allows you to specify a set of metrics to be used with
the route. Metrics are created using the
add pnnimetric command, and are
assigned to routes by metric tag numbers. By setting the appropriate
administrative weights within metrics, it’s possible to create parallel load-sharing
or fail-over routes. For more information about metrics, administrative weights,
and metric tags, see Section 4.4, Route Metrics.
5. Enter the show atmroute command to determine whether the route was created:
SmartSwitch # 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
SmartSwitch #
The route to the IISP device appears as Route 7, and with Protocol Type of MGMT (management).
6. 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 5b2 on the SmartSwitch 6500.
Note For IISP routes to work with certain devices, ILMI may need to be disabled on the
ATM SmartSwitch. Use the
set portconfig command to disable ILMI on the
ATM SmartSwitch on a per-port basis.
4.2.1 IISP Routing Considerations
When creating routes between an ATM SmartSwitch (running PNNI) and IISP devices, the criteria that characterize
IISP connectivity still apply. To reach an ATM SmartSwitch within the PNNI domain, the IISP device must have a
configured route that points directly to a port on the target ATM SmartSwitch. Conversely, there must be an ATM
SmartSwitch that has a direct physical link (and a route over that link) to the IISP device. The following two examples
illustrate this point.