
Customizing ST2 Services
114064 Rev. A 5-9
The ST2 agent on BayNet/ST2 1, using the information in the connection request:
1. Negotiates a hop identifier (HID) with the previous hop, ST2 1
2. Reserves the local and network resources required to support the stream
3. Passes the flowspec to the Bay Networks resource manager
Determining the Next Hop Downstream
An ST2 agent on a Bay Networks router uses two methods to determine the next
downstream hop in the stream:
• IP-inherited routing (the primary method), using the IP routing table
• ST2 exploratory routing (the backup method), using the ST2 neighbor table
Using the IP Routing Table (IP-Inherited Routing)
In IP-inherited routing, the ST2 agent obtains the address of the next-hop router
from the IP routing table. This table consists of entries describing routes that have
been learned by the routing protocols configured on the router (OSPF and BGP,
for example). The routing table also contains entries for static routes -- that is,
routes that have been inserted by the network administrator.
Each entry in the IP routing table includes a target IP network, a next-hop IP
address, an interface address, and other information. There is no information in a
routing table entry, however, to distinguish an ST2 route (that is, a hop with an
ST2-capable router on the other end). For this reason, it is possible for ST2 to
select a route that it cannot use.
If ST2 selects a route that is not ST2 capable (and does not provide a tunnel to an
ST2 agent), ST2 does not use the route and returns an SCMP REFUSE message
upstream with the reason code No Route to Destination.
If the required resources are not available via a path stored in the IP routing table,
ST2 uses exploratory routing. See “Using the ST2 Neighbor Table (Exploratory
Routing)” on page 5-10.
Comentarios a estos manuales