Users Guide

The Network conguration section is expanded.
2 In the General Settings section, you can enable or disable NIC, Register with DNS and Auto Negotiation.
If you enable Register with DNS, then enter the DNS Name and enable or disable the Use DHCP for DNS Domain Name option.
If Auto Negotiation is false or disabled, you can choose network port speed.
If the Use DHCP for DNS Domain Name is disabled, then enter the DNS Domain Name.
NOTE: You can enable Use DHCP for DNS Name only if IPv4 or IPv6 has DHCP congured. OME–Modular obtains its
DNS domain name from either a DHCP or DHCPv6 server when Use DHCP for DNS Name is enabled.
3 In the IPv4 Settings section, congure 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
4 In the IPv6 Settings section, congure the following:
• Enable IPv6
• Enable Autoconguration
• IPv6 Address
• Prex Length
• Gateway
• Use DHCPv6 to Obtain DNS Server Addresses
• Statis Preferred DNS Server
• Static Alternate DNS Server
5 Enable or disable the VLAN for the chassis. You can congure the VLAN settings only if the Register with DNS check box is cleared.
You can change the VLAN settings, that is, move 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 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 eective.
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 trac on the data network, the management interfaces on the internal
management network can be saturated by trac that is intended for servers. This results in OME–Modular and iDRAC communication
delays. These delays may cause unpredictable chassis behavior, such as
OME–Modular displaying iDRAC as oine 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 trac to a separate VLAN. OME–Modular and individual iDRAC network interfaces
can be congured 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.
Conguring chassis network services
The chassis network services conguration comprises of SNMP, SSH, and remote RACADM settings.
Logging in to OME-Modular
19