[an error occurred while processing this directive][an error occurred while processing this directive]

Initial Routing Engine Configuration Example

You can use configuration groups to ensure that the correct IP addresses are used for each Routing Engine and to maintain a single configuration file for both Routing Engines.

The following example defines configuration groups re0 and re1 with separate IP addresses. These well-known configuration group names take effect only on the appropriate Routing Engine.

groups {re0 {system {host-name my-re0;}interfaces {fxp0 {description "10/100 Management interface";unit 0 {family inet {address 10.255.2.40/24;}}}}}re1 {system {host-name my-re1;}interfaces {fxp0 {description "10/100 Management interface";unit 0 {family inet {address 10.255.2.41/24;}}}}}}

You can assign an additional IP address to the fxp0 (management) interface on both Routing Engines. The assigned address uses the master-only keyword and is identical for both Routing Engines, ensuring that the IP address for the master Routing Engine can be accessed at any time. The address is active only on the master Routing Engine's fxp0 (management) interface. During a Routing Engine switchover, the address moves over to the new master Routing Engine.

For example, on re0, the configuration is:

[edit groups re0 interfaces fxp0]unit 0 {family inet {address 10.17.40.131/25 {master-only;}address 10.17.40.132/25;}}

On re1, the configuration is:

[edit groups re1 interfaces fxp0]unit 0 {family inet {address 10.17.40.131/25 {master-only;}address 10.17.40.133/25;}}

For more information about the initial configuration of dual Routing Engines, see the JUNOS Software Installation and Upgrade Guide. For more information about assigning an additional IP address to the fxp0 (management) interface with the master-only keyword on both Routing Engines, see the JUNOS CLI User Guide.


Published: 2010-04-28

[an error occurred while processing this directive]