Dell PowerEdge MX7000 EMC OpenManage Enterprise-Modular Edition Version 1.10.2 - Page 22

Con chassis management network

Get Dell PowerEdge MX7000 PDF manuals and user guides View all Dell PowerEdge MX7000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

Power redundancy policies facilitate management of power consumption and power failure tolerance in the chassis. The available options are: • No Redundancy-This policy distributes the enclosure power load across all PSUs. There are not any specific PSU population requirements for No Redundancy. The intent of the No Redundancy policy is to have the highest possible limit for power enablement of devices added to the enclosure. If there are single or multiple PSU failures, then the enclosure limits the performance to operate within the power capabilities of the remaining PSUs. • Grid Redundancy-This policy distributes the enclosure power load across all PSUs. The six PSUs are organized into two groups: Grid A consists of PSUs 1, 2, 3, and Grid B consists of PSUs 4, 5, 6. It is recommended that the PSUs are populated in the following order: 1, 4, 2, 5, 3, 6, where an equal number of PSUs on each grid is optimized for Grid Redundancy. The grid with the largest PSU capacity determines the limit for power enablement of devices added to the enclosure. If there is a grid or PSU failure, then the enclosure power is distributed among the remaining PSUs with the intent that a single healthy grid continues to provide power to the system without degrading the performance. • PSU Redundancy-This policy distributes the enclosure power load across all PSUs. There are no specific PSU population requirements for redundant PSUs. PSU redundancy is optimized for a population of six PSUs, and the enclosure limits the power enablement of devices to fit within five PSUs. If there is a single PSU failure, then the enclosure power is distributed among the remaining PSUs without degrading the performance. If there are less than six PSUs, then the enclosure limits the power enablement of devices to fit within all populated PSUs. If there is a single PSU failure, then the enclosure limits the performance to operate within the power capabilities of the remaining PSUs. 4. In the Hot Spare Configuration section, select the Enable Hot Spare configure the Hot Spare primary grid. The Hot Spare feature facilitates voltage regulation when power utilization by Power Supply Unit (PSUs) is low, considering the total output capacity of the PSU. By default, the Hot Spare is enabled. When the Hot Spare is enabled, a redundant PSU is put in sleep state when the power utilization is low. The Hot Spare is not enabled if the: • PSU redundancy is inactive. • Power budget of the system configuration exceeds the PSU output capacity. • Grid Redundancy Policy is not selected. The MX7000 PSUs support the Hot Spare feature with three PSU pairs. The feature enables a PSU pair to have one active PSU and one PSU in sleep mode while the enclosure power consumption is low, and the three PSU pairs meet all the power requirements for the enclosure. This enables efficient power utilization when the overall enclosure power requirement is low. The partner PSU wakes the paired PSU from sleep mode by sending a WAKE signal when the enclosure power requirement increases. The PSU pairs for MX7000 are PSUs: 1 & 4, 2 & 5, and 3 & 6. 5. From the Primary Grid option, select the PSU where you want to enable the Hot Spare, from the drop-down. 6. Click Apply to save the chassis power settings. Configure chassis management network You can configure the network settings for the management modules that are inserted into an MX7000 chassis. • LAN/NIC interface • IPv4 • IPv6 • DNS Information • Management VLAN To configure the chassis network: 1. Click Devices > Chassis > View Details > Settings > Network. The Network configuration section is expanded. 2. In the General Settings section, you can enable or disable NIC, Register with DNS, and Auto Negotiation. By default, the Enable NIC check box is selected. If you enable Register with DNS, then enter the DNS Name of the chassis that you want to register with a DNS server. You can access OME-Modular using the existing FQDN even after the Register with DNS option is disabled in the application. This is because the earlier option remains in the Network cache or the DNS Server cache, based on the configured Time to live (TTL). NOTE: You can only access the FQDN temporarily. NOTE: Clear the cache in the DNS after the Register with DNS is disabled, to prevent logging in with the FQDN address. NOTE: If the Register with DNS option is enabled, you cannot modify the Enable VLAN option. 3. Enter the DNS Name. The DNS name can have a maximum of 58 characters. The first character must be an alphanumeric character (a-z, A-Z, 0-9), followed by numeric characters or a hyphen (-). 22 Logging in to OME-Modular

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
Power redundancy policies facilitate management of power consumption and power failure tolerance in the chassis. The available
options are:
•
No Redundancy
—This policy distributes the enclosure power load across all PSUs. There are not any specific PSU population
requirements for
No Redundancy
. The intent of the
No Redundancy
policy is to have the highest possible limit for power
enablement of devices added to the enclosure. If there are single or multiple PSU failures, then the enclosure limits the
performance to operate within the power capabilities of the remaining PSUs.
•
Grid Redundancy
—This policy distributes the enclosure power load across all PSUs. The six PSUs are organized into two groups:
Grid A consists of PSUs 1, 2, 3, and Grid B consists of PSUs 4, 5, 6. It is recommended that the PSUs are populated in the
following order: 1, 4, 2, 5, 3, 6, where an equal number of PSUs on each grid is optimized for Grid Redundancy. The grid with the
largest PSU capacity determines the limit for power enablement of devices added to the enclosure. If there is a grid or PSU failure,
then the enclosure power is distributed among the remaining PSUs with the intent that a single healthy grid continues to provide
power to the system without degrading the performance.
•
PSU Redundancy
—This policy distributes the enclosure power load across all PSUs. There are no specific PSU population
requirements for redundant PSUs. PSU redundancy is optimized for a population of six PSUs, and the enclosure limits the power
enablement of devices to fit within five PSUs. If there is a single PSU failure, then the enclosure power is distributed among the
remaining PSUs without degrading the performance. If there are less than six PSUs, then the enclosure limits the power
enablement of devices to fit within all populated PSUs. If there is a single PSU failure, then the enclosure limits the performance to
operate within the power capabilities of the remaining PSUs.
4.
In the
Hot Spare Configuration
section, select the
Enable Hot Spare
configure the Hot Spare primary grid.
The Hot Spare feature facilitates voltage regulation when power utilization by Power Supply Unit (PSUs) is low, considering the total
output capacity of the PSU. By default, the Hot Spare is enabled. When the Hot Spare is enabled, a redundant PSU is put in sleep
state when the power utilization is low. The Hot Spare is not enabled if the:
•
PSU redundancy is inactive.
•
Power budget of the system configuration exceeds the PSU output capacity.
•
Grid Redundancy Policy is not selected.
The MX7000 PSUs support the Hot Spare feature with three PSU pairs. The feature enables a PSU pair to have one active PSU and
one PSU in sleep mode while the enclosure power consumption is low, and the three PSU pairs meet all the power requirements for
the enclosure. This enables efficient power utilization when the overall enclosure power requirement is low. The partner PSU wakes
the paired PSU from sleep mode by sending a WAKE signal when the enclosure power requirement increases. The PSU pairs for
MX7000 are PSUs: 1 & 4, 2 & 5, and 3 & 6.
5.
From the
Primary Grid
option, select the PSU where you want to enable the Hot Spare, from the drop-down.
6.
Click
Apply
to save the chassis power settings.
Configure chassis management network
You can configure the network settings for the management modules that are inserted into an MX7000 chassis.
•
LAN/NIC interface
•
IPv4
•
IPv6
•
DNS Information
•
Management VLAN
To configure the chassis network:
1.
Click
Devices
>
Chassis
>
View Details
>
Settings
>
Network
.
The
Network
configuration section is expanded.
2.
In the
General Settings
section, you can enable or disable NIC,
Register with DNS
, and
Auto Negotiation
. By default, the
Enable
NIC
check box is selected.
If you enable
Register with DNS
, then enter the
DNS Name
of the chassis that you want to register with a DNS server. You can
access OME-Modular using the existing FQDN even after the
Register with DNS
option is disabled in the application. This is because
the earlier option remains in the Network cache or the DNS Server cache, based on the configured Time to live (TTL).
NOTE:
You can only access the FQDN temporarily.
NOTE:
Clear the cache in the DNS after the Register with DNS is disabled, to prevent logging in with the FQDN
address.
NOTE:
If the Register with DNS option is enabled, you cannot modify the Enable VLAN option.
3.
Enter the
DNS Name
. The DNS name can have a maximum of 58 characters. The first character must be an alphanumeric character
(a-z, A-Z, 0-9), followed by numeric characters or a hyphen (-).
22
Logging in to OME-Modular