Normally, on SRX-series devices, the built-in interfaces are numbered as follows:
|
reth0 |
reth1 |
reth2 |
reth3 |
For chassis clustering, SRX-series devices have a built-in management interface named fxp0. For SRX 5600 and 5800 devices, control interfaces are configured on SPCs. Table 60 shows how an example of how these interfaces could be named and numbered for SRX-series chassis clusters.
Table 60: Example of SRX-series Chassis Cluster Interface Naming Scheme
![]() |
Note: See the appropriate Services Gateway Hardware Guide for details about SRX-series devices. The JUNOS Software Interfaces and Routing Configuration Guide provides a full discussion of the interface naming convention. |
After you enable chassis clustering, the two chassis joined together cease to exist as individuals and now represent a single system. Internally, the cluster models a dual Routing Engine device. The primary Routing Engine propagates all its network and configuration settings and the current session information to the secondary. The secondary Routing Engine serves as the backup. As a single system, the cluster now has twice as many FPC slots. (See Figure 69.)
Figure 69: FPC Slot Numbering in an SRX-series Chassis Cluster (SRX 5800 Devices)
