11-37
ATM Switch Router Software Configuration Guide
OL-7396-01
Chapter11 Configuring ATM Routing and PNNI
Advanced PNNI Configuration
Node IDs can be entered either with the full 22-byte length address or as a Node ID prefix with a length
of 15 or more bytes. To specify routes that include higher level nodes (parent LGNs) for ot her peer
groups, we recommend that you enter exactly 15 bytes so that the address remains valid in the event of
a PGL update.
Node IDs appear in the following format:
dec : dec : 13-20 hex digits
Node names can be entered instead of Node IDs. If names are used to identify higher level LGNs, the
resulting explicit paths are not guaranteed to remain valid if the PGL changes in the neighboring peer
group. To prevent invalid paths, configure all parent LGNs (for all potential PGL nodes) with the same
node name.
Optionally, an exit port can be specified for any entry. The port should be specified as a hex-port-id rather
than a port-name. For excluded entries, only this port is excluded from the path.
Since the port ID could change if the following neighbor peer group changes PGL leaders, the
aggregation token is used in place of the port ID for nod es with higher level LGNs. The LGN aggregation
token can only identify the port uniquely if the following entry is a next-node entry. Aggregation tokens
are not allowed for excluded nodes.
Example
The following example shows how to configure an explicit path list consisting of four entries. The first
two are adjacent nodes and, in one case, an exit port is specified. Next, a partially-specified segment to
the node chicago_2 is configured, several hops away. Finally, a higher level LGN node adjacent to
chicago_2 is configured, which is specified by its 15-byte Node ID prefix.
Switch(cfg-pnni-expl-path)# next-node dallas_2
Switch(cfg-pnni-expl-path)# next-node dallas_4 port 80003004
Switch(cfg-pnni-expl-path)# segment-target chicago_2
Switch(cfg-pnni-expl-path)# next-node 40:72:47.009181000000106000000000
Displaying Node IDs
To display the node IDs that correspond to named nodes in a network, use either of the following EXEC
commands:
Displaying Hex-Port-IDs
Since the explicit path subcommands require a hex-port-id rather than a port name, use either of the
following EXEC commands to display the corresponding hex-port-ids for a node:
Command Purpose
show atm pnni identifier Displays the node IDs.
show atm pnni topology node
name-or-number
Displays the node IDs.
Command Purpose
show atm pnni identifiers node-number port Displays hex-port-ids for a node.
show atm pnni topology node node-number
hex-port-id
Displays hex-port-ids for a node.