Configuring a Redundant Interface on the controller.
KB ARTICLE TYPE: Configuration
RELATED PRODUCTS: Controller
RELATED SOFTWARE VERSIONS: N/A
KEYWORDS: Controller, redundant
The second Ethernet interface can be configured as redundant or active, in the Meru controller.
CONFIGURATION STEPS:
Redundancy can be configured only through CLI.
CLI Steps :
Step 1 : Do not connect any Ethernet cable to the second Ethernet interface (G2) until we finish configuring the second interface(G2)
Step 2 : Log into the console session, telnet or SSH and run the following commands :
Meru# configure terminal
Meru(config)# bonding dual
Meru(config)# exit
Meru# copy running‐config startup‐config
Meru(config)# interface FastEthernet 2
Meru(config-if-FastEth)# type redundant
Meru(config-if-FastEth)# exit
Meru(config)# exit
Meru#copy running-config startup-config
Step 3 : Once after saving the configuration, we need to reboot the controller for the changes to take effect.
Step 4 : We need not specify an ip for secondary interface as it will receive the IP address of the primary interface when the failover occurs.
EXPECTED BEHAVIOUR : Once when the primary interface of the controller goes down, the secondary interface would take over the network with the same ip as that of primary interface.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.