Dell PowerEdge FX2 Dell Chassis Management Controller Version 1.1 for PowerEdg - Page 3

Important Notes, Known Issues - setup

Page 3 highlights

• Safari version 6.0 • Safari version 7.0 • Mozilla Firefox version 29 • Mozilla Firefox version 30 • Google Chrome version 33 • Google Chrome version 34 Important Notes • CMC network default setting is Static with IP address of "192.168.0.120". Complete the CMC network setup by directly connecting a client system on the same network. For more information, see the Chassis Management Controller for PowerEdge FX2 Version 1.10 User's Guide available at dell.com/support/manuals. • Connecting the STK/Gb2 port of the CMC at the back of the chassis to the management network can cause network disruption if not properly cabled and configured in CMC. Before using the STK/Gb2 port of the CMC, see the PowerEdge FX2 Version 1.10 Owner's Manual available at dell.com/support/manuals. • The PCIe cards are allocated to sleds based on the sled type, for more information, see the Chassis Management Controller for PowerEdge FX2 Version 1.10 User's Guide available at dell.com/support/manuals. This is applicable to Dell PowerEdge FX2s chassis. • Some advanced features require CMC enterprise license. For more information about the CMC licenses, see the Chassis Management Controller for PowerEdge FX2 Version 1.10 User's Guide available at dell.com/support/manuals. • When Certificate Validation is Enabled, FQDN of the system should be provided. If IP address of the Domain Controller is specified when certificate validation is enabled, Active Directory login may not work. • The cfgRacTuneIdracDNSLaunchEnable object and "iDRAC Launch Method" settings under Chassis Overview > Setup > General in the CMC GUI require the Chassis Configuration Administrator privilege. • When saving Server Profile under Server Overview > Setup > Profiles in the CMC GUI, the list of characters that are not supported for the Profile Name include the special characters hash(#), comma(,), and question mark(?). Known Issues • Issue (162141): Non-iSCSI MAC addresses may be displayed when you run the racadm getmacaddress command using the "-t iscsi" option. Resolution: None. Extraneous non-iSCSI MAC addresses may be ignored. • Issue (161038): WWN/MAC for IO Identity is displayed incorrectly when you run racadm getmacaddress -c all command and in the CMC Graphical Interface, under Server Overview > Properties > WWN/MAC. This applies only to Intel network adapters. Resolution: The correct value may be viewed in the iDRAC GUI. • Issue (169078): After you unmap the KVM, if you disable and enable it again, the KVM remains mapped to the host to which it was mapped before the unmap operation. The LEDs and racadm will report that it is unmapped. Resolution: If KVM is unmapped after you enabled it, use racadm, CMC Graphical Interface, or Control Panel to map the KVM to a slot ID. • Issue (170029): When using Chassis Group Management, VLAN settings from the leader chassis are not propagated to member chassis. Resolution: In the CMC graphical interface, go to Server Overview > Setup > VLAN and manually set the VLAN for each member chassis.

  • 1
  • 2
  • 3
  • 4
  • 5

Safari version 6.0
Safari version 7.0
Mozilla Firefox version 29
Mozilla Firefox version 30
Google Chrome version 33
Google Chrome version 34
Important Notes
CMC network default setting is Static with IP address of "192.168.0.120". Complete the CMC
network setup by directly connecting a client system on the same network. For more information,
see the
Chassis Management Controller for PowerEdge FX2 Version 1.10 User's Guide
available at
dell.com/support/manuals
.
Connecting the STK/Gb2 port of the CMC at the back of the chassis to the management network
can cause network disruption if not properly cabled and configured in CMC. Before using the
STK/Gb2 port of the CMC, see the
PowerEdge FX2 Version 1.10 Owner's Manual available at
dell.com/support/manuals.
The PCIe cards are allocated to sleds based on the sled type, for more information, see the
Chassis Management Controller for PowerEdge FX2
Version 1.10 User's Guide available at
dell.com/support/manuals.
This is applicable to Dell PowerEdge FX2s chassis.
Some advanced features require CMC enterprise license. For more information about the CMC
licenses, see the
Chassis Management Controller for PowerEdge FX2 Version 1.10 User's Guide
available at
dell.com/support/manuals
.
When Certificate Validation is Enabled, FQDN of the system should be provided. If IP address of
the Domain Controller is specified when certificate validation is enabled, Active Directory login
may not work.
The
cfgRacTuneIdracDNSLaunchEnable
object and "iDRAC Launch Method" settings under
Chassis Overview > Setup > General
in the CMC GUI require the Chassis Configuration
Administrator privilege.
When saving Server Profile under
Server Overview
>
Setup
>
Profiles
in the CMC GUI, the
list of
characters that are not supported for the
Profile Name
include the special characters hash(#),
comma(,), and question mark(?).
Known Issues
Issue (162141):
Non-iSCSI MAC addresses may be displayed when you run the
racadm
getmacaddress
command using the
"-t iscsi
" option.
Resolution:
None. Extraneous non-iSCSI MAC addresses may be ignored.
Issue (161038):
WWN/MAC for IO Identity is displayed incorrectly when you run
racadm
getmacaddress -c all
command and in the CMC Graphical Interface, under
Server
Overview
>
Properties
>
WWN/MAC.
This applies only to Intel network adapters.
Resolution:
The correct value may be viewed in the iDRAC GUI.
Issue (169078):
After you unmap the KVM, if you disable and enable it again, the KVM remains
mapped to the host to which it was mapped before the unmap operation. The LEDs and racadm
will report that it is unmapped.
Resolution:
If KVM is unmapped after you enabled it, use racadm, CMC Graphical Interface, or
Control Panel to map the KVM to a slot ID.
Issue (170029):
When using Chassis Group Management, VLAN settings from the leader chassis
are not propagated to member chassis.
Resolution:
In the CMC graphical interface, go to
Server Overview
>
Setup
>
VLAN
and manually
set the VLAN for each member chassis.