Users Guide

Table 6. Top of the Rack Support Matrix for management module and management module uplink
Top of the Rack Switch
Configuration
Management Module
Configuration
Supported for Management Module Uplink (YES
or NO)
10 Mbps (Auto negotiation
OFF)
10 Mbps (Auto negotiation OFF) YES
Auto Neg ON Auto Negotiation ON YES
100 Mbps (Auto negotiation
OFF)
Auto Negotiation ON NO
10 Mbps (Auto negotiation
OFF)
Auto Negotiation ON NO
Auto Negotiation ON 100 Mbps (Auto negotiation OFF) NO
Auto Negotiation ON 10 Mbps (Auto negotiation OFF) NO
5. In the IPv4 Settings section, configure the following:
● Enable IPv4
● Enable DHCP
● IP Address
● Subnet Mask
●
Gateway
● Use DHCP to Obtain DNS Server Addresses
● Static Preferred DNS Server
● Static Alternate DNS Server
6. In the IPv6 Settings section, configure the following:
● Enable IPv6
● Enable Autoconfiguration
● IPv6 Address
● Prefix Length
● Gateway
● Use DHCPv6 to Obtain DNS Server Addresses
● Static Preferred DNS Server
● Static Alternate DNS Server
NOTE:
The static IPv6 IP address that is already configured is applied and displayed in OME–Modular when the
configuration is changed from static to DHCP IP.
7. Enable or disable the VLAN for the chassis. You can configure the VLAN settings only if the Register with DNS check box
is cleared.
You can change from a VLAN network to a non-VLAN network, or move from a non-VLAN network to a VLAN network, only
if Register with DNS check box is cleared.
By default, the IPv4 settings are enabled and the DNS registration is disabled with a default name. You can modify the name
using any local interfaces such as OpenManage Mobile.
NOTE:
Ensure that the network cable is plugged to the correct port when you modify the VLAN state for the change to
be effective.
Isolate the chassis management from the data network as the uptime of a chassis that is improperly integrated into your
environment cannot be supported or guaranteed. Due to the potential of traffic on the data network, the management
interfaces on the internal management network are saturated by traffic that is intended for servers. It results in OME–
Modular and iDRAC communication delays. These delays may cause unpredictable chassis behavior, such as OME–Modular
displaying iDRAC as offline even when it is up and running, which in turn causes other unwanted behavior. If physically
isolating the management network is impractical, the other option is to separate OME–Modular and iDRAC traffic to a
separate VLAN. OME–Modular and individual iDRAC network interfaces can be configured to use a VLAN.
NOTE:
Any change in the attribute settings leads to IP drop or unavailability of the OME–Modular web interface for
some time. However, the OME–Modular web interface recovers automatically.
8. Click Apply to save the chassis network settings.
30
Logging in to OME-Modular