In this case, chassis cluster makes use of its asymmetric routing capability. Traffic received by a node is matched against that node’s session table. The result of this lookup determines whether that node processes the session or forwards it to the other node over the fabric link. Sessions are anchored on the node in which the first packet created the session, and the session is synced to the other node. If traffic is received on the node in which the session is not anchored, those packets are forwarded over the fabric link.
Figure 62: Asymmetric Routing Chassis Cluster Scenario
Figure 62 illustrates how asymmetric routing is supported in a chassis cluster. In this scenario, two Internet connections are used, with one being preferred. The connection to the Trust zone is done by using a reth interface to provide LAN redundancy for the devices in the Trust zone. This scenario describes two failover cases in which sessions originate in the Trust zone with a destination of the Internet (Untrust zone).
 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |