Administrator Guide

• ip-address mask: enter an address in dotted-decimal format (A.B.C.D). The mask must be in /prefix format (/x).
You can configure two global IPv6 addresses on the system in EXEC Privilege mode. To view the addresses, use the show interface
managementethernet command, as shown in the following example. If you try to configure a third IPv6 address, an error message
displays. If you enable auto-configuration, all IPv6 addresses on that management interface are auto-configured. The first IPv6 address
that you configure on the management interface is the primary address. If deleted, you must re-add it; the secondary address is not
promoted.
The following rules apply to having two IPv6 addresses on a management interface:
• IPv6 addresses on a single management interface cannot be in the same subnet.
• IPv6 secondary addresses on management interfaces:
• across a platform must be in the same subnet.
• must not match the virtual IP address and must not be in the same subnet as the virtual IP.
If there are 2 RPMs on the system, each Management interface must be configured with a different IP address. Unless the management
route command is configured, you can only access the Management interface from the local LAN. To access the Management interface
from another LAN, the management route command must be configured to point to the Management interface.
Alternatively, you can use virtual-ip to manage a system with one or two RPMs. A virtual IP is an IP address assigned to the system (not to
any management interfaces) and CONFIGURATION command. When a virtual IP address is assigned to the system, the active
management interface of the RPM is recognized by the virtual IP address—not by the actual interface IP address assigned to it. During an
RPM failover, you do not have to remember the IP address of the new RPM’s management interface— the system will still recognizes the
virtual-IP address.
DellEMC#show interfaces managementethernet 0/0
ManagementEthernet 0/0 is up, line protocol is up
Hardware is DellForce10Eth, address is 00:01:e8:a0:bf:f3
Current address is 00:01:e8:a0:bf:f3
Pluggable media not present
Interface index is 302006472
Internet address is 10.16.130.5/16
Link local IPv6 address: fe80::201:e8ff:fea0:bff3/64
Global IPv6 address: 1::1/
Global IPv6 address: 2::1/64
Virtual-IP is not set
Virtual-IP IPv6 address is not set
MTU 1554 bytes, IP MTU 1500 bytes
LineSpeed 1000 Mbit, Mode full duplex
ARP type: ARPA, ARP Timeout 04:00:00
Last clearing of "show interface" counters 00:06:14
Queueing strategy: fifo
Input 791 packets, 62913 bytes, 775 multicast
Received 0 errors, 0 discarded
Output 21 packets, 3300 bytes, 20 multicast
Output 0 errors, 0 invalid protocol
Time since last interface status change: 00:06:03
If there are two RPMs on the system, configure each Management interface with a different IP address. Unless you configure the
management route command, you can only access the Management interface from the local LAN. To access the Management
interface from another LAN, configure the management route command to point to the Management interface.
Alternatively, you can use the virtual-ip command to manage a system with one or two RPMs. A virtual IP is an IP address assigned
to the system (not to any management interfaces) and is a CONFIGURATION mode command. When a virtual IP address is assigned to
the system, the active management interface of the RPM is recognized by the virtual IP address — not by the actual interface IP address
assigned to it. During an RPM failover, you do not have to remember the IP address of the new RPM’s management interface — the
system still recognizes the virtual-IP address.
• virtual-ip is a CONFIGURATION mode command.
• When applied, the management port on the primary RPM assumes the virtual IP address. Executing the show interfaces and
show ip interface brief commands on the primary RPM management interface displays the virtual IP address and not the
actual IP address assigned on that interface.
• A duplicate IP address message is printed for the management port’s virtual IP address on an RPM failover. This behavior is a harmless
error that is generated due to a brief transitory moment during failover when both RPMs’ management ports own the virtual IP
address, but have different MAC addresses.
• The primary management interface uses only the virtual IP address if it is configured. The system cannot be accessed through the
native IP address of the primary RPM’s management interface.
• After the virtual IP address is removed, the system is accessible through the native IP address of the primary RPM’s management
interface.
360
Interfaces