Configuring VCS virtual IP addresses
A virtual IP address is assigned for each VCS cluster. This virtual IP address is tied to the principal switch in the cluster. The management interface of the principal switch can be accessed by means of this virtual IP address. Because the virtual IP address is a property of the fabric cluster and logical chassis cluster, in the event that the principal switch goes down, the next principal switch is assigned this address.
Virtual IP address can be configured by means of the vcs virtual ip address command:
switch(config)# vcs virtual ip address 10.0.0.23/24
This command can be used in logical chassis cluster and fabric cluster modes only. When the virtual IP address is configured for the first time, the current principal switch in the cluster is assigned this IP address.
Virtual IP configuration is global in nature. All the nodes in the cluster are configured with the same virtual IP address, but address is bound to the current principal switch only. Make sure that the assigned virtual IP address is not a duplicate of an address assigned to any other management port in the cluster or network.
Brocade recommends that you use a /32 address in the same subnet as the IP address of the management interface. For example, if you are using inband management via rbridge interface ve 100 with the ip address 192.168.100.10/24, set your vcs virtual ip address as a /32 address in this subnet by using the command vcs virtual ip address 192.168.100.1/32. To display the currently configured virtual IP address, use the show vcs virtual ip command:
switch# show vcs virtual ip Virtual IP : 10.21.87.2/20 Associated rbridge-id : 2
To remove the currently configured virtual IP address, use the no vcs virtual ip address command.
switch(config)# no vcs virtual ip address switch# show running-config vcs virtual ip address % No entries found.
If you wish to rebind this virtual IP address to this management interface, remove the currently configured virtual IP address and reconfigure it. This situation can arise when the virtual IP address is not bound to management interface of the principal switch as a result of duplicate address detection.
A separate gateway cannot be configured for virtual IP address. The default gateway is the same as the gateway address for the management port of the same switch.