For a list of applications and services that dedicated and shared tunnel-server modules
support on ERX-7xx models, ERX-14xx models, and the ERX-310 router, see
ERX
Module Guide, Appendix A, Module Protocol Support
.
For a list of applications and services that dedicated tunnel-server modules support
on the E120 and E320 routers, see
E120 and E320 Module Guide, Appendix A, IOA
Protocol Support
.
Redundancy and Interface Distribution of Tunnel-Service Interfaces
The redundancy and distribution mechanisms supported for tunnel-service ports
configured on ISMs differ from those supported for SMs, the ES2-S1 Service IOA,
and shared tunnel-server ports.
This section describes the redundancy and interface distribution mechanisms for all
tunnel-server ports.
SMs, ES2-S1 Service IOA, and Shared Tunnel-Server Modules
You can install multiple modules to provide redundancy. If you install multiple
modules at the same time, the router automatically distributes the tunnel-service
interfaces over the modules in proportion to the available tunnel-service interfaces.
Even distribution of tunnel-service interfaces is not critical to router performance.
However, the number of modules that you install must be able to support the extra
tunnel if one of the modules becomes unavailable.
NOTE:
When both dedicated tunnel-server ports (on SMs) and shared tunnel-server
ports (on shared tunnel-server modules) are configured on ERX-7xx models, ERX-14xx
models, and the ERX-310 router, the router performs load balancing across all
available server ports of the same type. For this purpose, dedicated tunnel-server
ports (on SMs) and shared tunnel-server ports (on shared tunnel-server modules) are
considered one type of server port, whereas server ports on ISMs are considered a
different type.
Interface allocation depends on the types of tunnel-service interface created on the
router. For more information about the types of tunnel-service interfaces, see “Types
of Tunnel-Service Interfaces” on page 212
.
Static IP Tunnel-Service Interfaces
You can configure and delete static IP tunnel-service interfaces.
When you configure a static tunnel-service interface, the router automatically assigns
that interface to a particular module. If that module becomes unavailable, the router
attempts to reassign the interface to an available module. If no module is currently
available, the router keeps track of the interface and assigns it to a module when
one become available.
Redundancy and Interface Distribution of Tunnel-Service Interfaces
■
217
Chapter 6: Managing Tunnel-Service and
IPSec-Service Interfaces
Содержание JUNOSE 10.0.X PHYSICAL LAYER
Страница 6: ...vi...
Страница 8: ...viii JUNOSe 10 0 x Physical Layer Configuration Guide...
Страница 16: ...xvi List of Figures JUNOSe 10 0 x Physical Layer Configuration Guide...
Страница 18: ...xviii List of Tables JUNOSe 10 0 x Physical Layer Configuration Guide...
Страница 28: ...2 Chapters JUNOSe 10 0 x Physical Layer Configuration Guide...
Страница 98: ...72 Monitoring Interfaces JUNOSe 10 0 x Physical Layer Configuration Guide...
Страница 200: ...174 Monitoring Interfaces JUNOSe 10 0 x Physical Layer Configuration Guide...
Страница 253: ...Part 2 Index Index on page 229 Index 227...
Страница 254: ...228 Index JUNOSe 10 0 x Physical Layer Configuration Guide...
Страница 262: ...236 Index JUNOSe 10 0 x Physical Layer Configuration Guide...