Beta Draft Confidential
About SVCs
About Route Determination
ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 1/19/0516-11
Table 16-5 shows an example of the node to which the SVC request is routed for
certain called-party addresses, and describes why the request is routed to that node:
Table 16-5. Called-party Address SVC Routing
Called Party
Address
Node Reason
5085511234 1 Port prefix 508551 on Node 1 is a longer match than port
prefix 5085 on Node 2 and node prefix 508 on Node 3.
5085555555 1 This calling party address is an exact match for a port address
defined on Node 1. This is a longer match than port prefix
5085 on Node 2 and port prefix 508555 on Node 3.
5085555557 3 Port prefix 508555 on Node 3 is a longer match than port
prefix 5085 on Node 2 and node prefix 508 on Node 1.
5085561111 2 Port prefix 5085 on Node 2 is a longer match than node prefix
508 on Node 1 and node prefix 508 on Node 3.
6175551111 1 Node prefix 6 on Node 1 is the only match.
6035551111 2 Port prefix 6035 on Node 2 is a longer match than node prefix
6 on Node 1 and node prefix 603 on Node 3.
6038558888 3 Node prefix 603 on Node 3 is a longer match than node prefix
6 on Node 1. There is no matching prefix or address on Node 2.
5085531111 1 or 2 Since the longest match occurs on both Nodes 1 and 2, the
Admin Cost value assigned to port prefix 508553 on each node
determines where the call is routed. The call is routed to the
node with the lowest Admin Cost value for port prefix 508553.
5145551234 None The call is not routed to any of these nodes because there are no
matching node prefixes, port prefixes, or port addresses. If,
however, you set up a default route on a port being used for
network-to-network connections, all non-matching calls are
routed to that port (see “Defining Default Routes for
Network-to-Network Connections” on page 17-52).
To Next Page
Loading...
Need help?
General
