
Configuring Bridging Services
2-8 114060 Rev. A
IP Encapsulation Features
Bay Networks implementation of IP encapsulation allows you to:
• Configure redundant IP interfaces.
You can configure redundant IP interfaces on the same router for critical
network connections (for example, interfaces 1.1.2.2 and 1.1.3.3 on Bridge
B). That way, if you disable one of the interfaces, the other interface can still
accept IP traffic for the network. (When you enable redundant IP interfaces,
you also increase explorer traffic on the network. Therefore, enable redundant
interfaces selectively to reduce the impact on your network performance.)
• Expand your IP backbone network.
You can expand your IP backbone to include any Bay Networks IP router on
the network. You specify the router’s IP address in the IP explorer list for each
bridge.
For example, Bridge A currently forwards all traffic destined for Ring 7 to IP
interface 1.1.3.3. That router then forwards the traffic toward Ring 6 so that
the router can source route it to Ring 7. If you add IP address 1.1.4.4. to the IP
Explorer list for Bridge A, then Bridge A forwards all traffic destined for Ring
7 directly to IP interface 1.1.4.4. By expanding your IP backbone, the source
routing bridge can route through more stations, but it still can only add a
single hop to a packet’s RIF.
• Reduce excess broadcast traffic on your IP network.
You can reduce the number of broadcast and explorer packets that traverse the
network by constructing directed explorer filters. (Refer to Configuring
Traffic Filters and Protocol Prioritization for information on how to create
filters that forward IP explorer frames to specific addresses.)
• Configure both IP encapsulation support and source route endstation support
on the same interface.
IP encapsulation support works independently of source route endstation
support. However, you can enable both on the same circuit.
Comentarios a estos manuales