Node Interfaces on Services Gateways

Normally, on services gateways, the built-in interfaces are numbered as follows:

Chassis clusters using SRX-series services gateways have built-in management and control interfaces named fpc0 and fpc1, respectively. Table 53 shows how an example of how these interfaces could be named and numbered for chassis clusters for the SRX-series services gateways.

Table 54: Example of Services Gateway Cluster Interface Naming Scheme

Note: See the SRX 5600 Services Gateway Hardware Guide and SRX 5800 Services Gateway Hardware Guide for details about SRX-series routers. 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 a Chassis Cluster (SRX–series 5800 Services Gateways)