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

Configuring compute settings, Replacing compute sleds

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 50 highlights

• Migrate Profile-You can migrate a profile from one server to another. The system unassigns the identity from the first server before the migration. If the unassignment fails, the system displays a critical error. You can override the error and force the migration to a new server. NOTE: The Migrate Profile option is not supported for slot-based template deployment. • Edit Profile-You can edit the profile characteristics that are unique to the device or slot. If a profile is attached to a compute, the updated profile configuration is propagated to the compute. • Remove slot associations-You can detach the server profile from the slot. • Detach Profile-You can remove profiles that are associated with blade servers. After the server profile is detached, the identity pools are reclaimed from the MAC address pools. Detaching a profile reclaims the Identities from the device, based on the last deployed template or profile. If the last deployed template does not have the MAC Identities association, the MAC Identities that are already deployed are not reclaimed. In MCM environment, if the compute sled on the member chassis is not reachable you can detach the profile from the lead chassis using the Detach profile option. The status of the On Detach profile Reclaim Identities task on the Jobs page in the lead chassis is displayed as Completed. However, the On Detach profile Reclaim Identities job fails in the member chassis. If the compute sled on the stand-alone chassis is not reachable and you try detaching the profile, the On Detach profile Reclaim Identities job fails. NOTE: The Reclaim Identities feature in OME-Modular works for both scenarios. NOTE: When a compute sled is inserted into a chassis, sometimes the message, "No device image found", is displayed. To resolve the issue refresh the inventory of the compute sled, manually. Configuring compute settings You can configure the following compute settings: • Network • Management Configuring compute network settings Once Quick Deploy settings are applied to a compute sled, the settings may be reported after some time due to data refresh in OMEModular. To configure the compute network settings: 1. Click Devices > Compute > View Details > Settings > Network. 2. In the General Settings section, select the LAN Enablement check box to configure the network settings. 3. Configure the IPv4, IPv6, and management VLAN settings. Configuring compute management settings To configure the compute management settings: 1. Click Devices > Compute > View Details > Settings > Management. 2. Configure the password to access the iDRAC console and select IPMI over LAN to enable access from OME-Modular to iDRAC, through BIOS. Replacing compute sleds The rip-and-replace feature of OME-Modular enables you to replace a failed compute sled, storage sled, or IOM, and apply the configuration automatically. NOTE: While replacing compute sleds, ensure that the: • Compute sled is turned off and the compute nodes in the chassis contain PERC or HBA controllers. • SAS IOMs and storage sleds are installed in the chassis. • When you replace a compute sled, with a service tag, with a compute sled of another service tag, and the storage sleds are mapped to the compute node slot, the power on the particular compute sled is turned off. An option to unblock power is displayed on the Devices > Compute > Overview page for the compute sled. 50 Managing compute sleds

  • 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
•
Migrate Profile—You can migrate a profile from one server to another. The system unassigns the identity from the first server
before the migration. If the unassignment fails, the system displays a critical error. You can override the error and force the
migration to a new server.
NOTE:
The Migrate Profile option is not supported for slot-based template deployment.
•
Edit Profile—You can edit the profile characteristics that are unique to the device or slot. If a profile is attached to a compute, the
updated profile configuration is propagated to the compute.
•
Remove slot associations—You can detach the server profile from the slot.
•
Detach Profile—You can remove profiles that are associated with blade servers. After the server profile is detached, the identity
pools are reclaimed from the MAC address pools. Detaching a profile reclaims the Identities from the device, based on the last
deployed template or profile. If the last deployed template does not have the MAC Identities association, the MAC Identities that
are already deployed are not reclaimed.
In MCM environment, if the compute sled on the member chassis is not reachable you can detach the profile from the lead chassis
using the
Detach profile
option. The status of the
On Detach profile Reclaim Identities
task on the
Jobs
page in the lead
chassis is displayed as
Completed
. However, the
On Detach profile Reclaim Identities
job fails in the member chassis.
If the compute sled on the stand-alone chassis is not reachable and you try detaching the profile, the
On Detach profile Reclaim
Identities
job fails.
NOTE:
The Reclaim Identities feature in OME-Modular works for both scenarios.
NOTE:
When a compute sled is inserted into a chassis, sometimes the message, "No device image found", is displayed.
To resolve the issue refresh the inventory of the compute sled, manually.
Configuring compute settings
You can configure the following compute settings:
•
Network
•
Management
Configuring compute network settings
Once Quick Deploy settings are applied to a compute sled, the settings may be reported after some time due to data refresh in OME-
Modular.
To configure the compute network settings:
1.
Click
Devices
>
Compute
>
View Details
>
Settings
>
Network
.
2.
In the
General Settings
section, select the LAN Enablement check box to configure the network settings.
3.
Configure the IPv4, IPv6, and management VLAN settings.
Configuring compute management settings
To configure the compute management settings:
1.
Click
Devices
>
Compute
>
View Details
>
Settings
>
Management
.
2.
Configure the password to access the iDRAC console and select
IPMI over LAN
to enable access from OME–Modular to iDRAC,
through BIOS.
Replacing compute sleds
The rip-and-replace feature of OME-Modular enables you to replace a failed compute sled, storage sled, or IOM, and apply the
configuration automatically.
NOTE:
While replacing compute sleds, ensure that the:
•
Compute sled is turned off and the compute nodes in the chassis contain PERC or HBA controllers.
•
SAS IOMs and storage sleds are installed in the chassis.
•
When you replace a compute sled, with a service tag, with a compute sled of another service tag, and the storage sleds are mapped to
the compute node slot, the power on the particular compute sled is turned off. An option to unblock power is displayed on the
Devices
>
Compute
>
Overview
page for the compute sled.
50
Managing compute sleds