Quantcast
Channel: Systems Management - Wiki
Viewing all 335 articles
Browse latest View live

BMC SEL Log

$
0
0
Current Revision posted to Systems Management - Wiki by Peter Tsai on 11/7/2011 6:17:18 PM
What are These Baseboard Management Controller (BMC) System Event Log (SEL) Records Logged by Windows?
By Steven Grigsby
iDRAC6 SEL Log
Introduction
Did you ever notice a bunch of entries in the Baseboard Management Controller (BMC) System Event Log (SEL) that seem to be coming from Windows? Not the Windows system event log, but the SEL that is accessible from the Baseboard Management Controller (BMC).

It may seem that this log is only intended for hardware events and errors, but there is an OS driver that also logs events to it. Starting with Windows Server 2003 R2, Microsoft began shipping the Intelligent Platform Management Interface (IPMI) driver. One of its functions is to log certain OS events to the SEL. The IPMI driver writes multiple records to the SEL for these three types of events: boot up, shutdown and bugcheck events.

The BMC SEL log is accessible via the sideband BMC interface using tools like ipmitool or impish. It is also accessible from OpenManage Server Assistant (OMSA), the Dell Remote Access Controller (DRAC) console, and <CTRL-E> during boot. Many different types of events, which can be useful in troubleshooting, are logged in the SEL. Each SEL record packs a lot of information in only 16 bytes, and given their limited size, they can be hard to decode.

Decoding the SEL Record


Dell BMC SEL record, pulled by racadm command line tool
The SEL record above was pulled using the Dell racadm command line tool available on the Dell Systems Management Tools and Documentation DVD.


Each SEL record is 16 bytes in length and the format is defined in the IPMI spec. The table below summarizes the format of the SEL record, as
defined by the IPMI spec. At the highest level, the Record Type field indicates whether it is a System Event Record or an OEM defined event record. System Event records are defined in the IPMI specification, and OEM records are defined by the OEM.

Each event logged by the IPMI driver (whether boot up, shutdown, or bugcheck) will cause one system event record and one or more OEM records to be logged to the SEL. The type 02h system event record format is defined in the table below.

BytesFieldDescription
1:0SEL Record ID16 bit record identifier

0000h: Reserved
0001h to FFFEh: SEL Record ID
FFFFh: Reserved
2Record Type02h: System Event Record

C0h to DFh: OEM Time stamped Record
Bytes 8-16 are OEM Defined

E0h to FFh: OEM Non-Time stamped Record
Bytes 4-16 are OEM Defined
6:3SEL TimestampTime when event was logged
8:7Generator ID Byte 8: System Software ID or IPMB Slave Address=============

[7:1]: System Software ID, or 7-bit I2C slave address
[0]: 0b means bits 7-1 are the IPMB Slave Address
1b means bits 7-1 are the System Software ID

Byte 7: Channel/LUN=============

[7:4]: Channel Number. Must be 0000b if the event was received via the system interface, primary IPMB, or internally generated by the BMC

[3:2]: Reserved. Must be 00b

[1:0]: IPMB device LUN if Byte 0 holds a slave address. 00b if Byte 0 holds a System Software ID
9 EvMRev 03h: IPMI 1.0 0

4h: IPMI 2.0
10 Sensor Type Sensor type code as specified in the IPMI spec
11 Sensor Number Number of the sensor that generated the event
12 Event Type [7]: Event Direction
0b: Assertion Event
1b: De-assertion Event


[6:0]: 7 bit Event/Reading Type Code
00h: Event/Reading Type unspecified
01h: Threshold
02h-0Ch: Generic Discrete
6Fh: Sensor-Specific Discrete
70h-7Fh: OEM Discrete. Indicates the discrete state info is specific to the OEM identified by the Manufacturer ID for the IPMI device that is providing access to the sensor
13 Event Data 1: Event Field Contents
14 Event Data 2 Event Field Contents
15 Event Data 3 Event Field Contents
Boot Up Events
During a system boot, two records are written to the SEL. The first is a type 02h System Event, and the second is an OEM event.

Type 02h Boot Up Record

The first 10 bytes of the type 02h System boot up record are general header information, and the boot-relevant information starts at byte 10.

BytesValue Field Name Meaning of Value
1:0SEL Record ID record identifier
202h Record Type 02h indicates a system event record
6:3SEL Timestamp
8:70041hGenerator ID 0041h indicates the event comes from system software whose ID 20h
9 04h EvMRev IPMI 2.0 Event Message Revision
10 1Fh Sensor Type:OS boot Sensor type 1Fh is OS Boot as specified in the IPMI spec
11 00h Sensor Number
12 6FhEvent Type [7]: 0b: indicates an assertion event

[6:0]: 6Fh indicates a Sensor-specific Discreet Type code. This means use the sensor specific offsets to interpret the event data bytes
13 01h Event Data 1: C: Boot Completed[7:6]:00b = unspecified byte 2 event data

[5:4]: 00b = unspecified byte 3 event data

[3:0]: Offset from Event/Reading Code
0h: A: boot completed 1h: C: boot completed
2h: PXE boot completed
3h: Diagnostic boot completed
4h: CD-ROM boot completd
5h: ROM boot completed
6h: boot completed-boot device not specified
14 FFh Event Data 2 Not specified per bits 7-6 in event data 1
15 FFh Event Data 3 Not specified per bits 5-4 in event data 1

Type DCh Boot Up OEM Event Record

The OEM Event record for bootup does not provide much more information. Nevertheless, the type DCh OEM Boot up event record looks similar to this:

Bytes Value Field Name Description
1:0SEL Record ID
2 DCh Record Type OEM Time stamped Record (bytes 7-15 are OEM Defined)DCh: OS Boot up
6:3 SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10 Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11 Boot Time The OS Boot time
1500h Reserved Reserved
Shutdown Events
System shutdown events can cause many records to be logged to the SEL. There is one type 02h System Event record, one OEM type DDh record for the shutdown reason code, and zero or more OEM type DDh records for the shutdown comment.

Whenever a user shuts down a system using shutdown.exe, the reason and comment entered by the user are saved in the registry. Then the IPMI driver reads them from the registry and logs them to the SEL with OEM type DDh records. The shutdown reason is a 4 byte code which fits within SEL entry. The shutdown comment, however, is a user-entered string of variable length.

The IPMI driver saves the comment string to the SEL in multiple OEM type DDh records, concatenated using the sequence number. This can be problematic because there are only 4 bytes available for the comment per SEL entry, and the comment is saved as a Unicode string.

This can quickly fill the SEL log. During a manual shutdown (Start | Shutdown), even though the user is required to enter a reason and comment, the comment is never saved to the registry, and therefore not logged to the SEL. Furthermore, an incorrect reason code is saved. See Microsoft KB200106 (http://support.microsoft.com/kb/2001061).

Type 02h System Shutdown Event Record

Again, the first 10 bytes of the type 02h System Event Record is all header information. The information relevant to the system shutdown starts at byte 10.

BytesValue Field Name Description
1:0SEL Record ID record identifier
202hRecord Type 02h indicates a system event record
6:3SEL Timestamp
8:70041hGenerator ID 0041h indicates the event comes from system software whose ID 20h
9 04h EvMRev IPMI 2.0 Event Message Revision
10 20h Sensor Type:OS Stop/Shutdown Sensor type 1Fh is OS Boot as specified in the IPMI spec
11 00h Sensor Number
12 6FhEvent Type [7]: 0b: indicates an assertion event
[6:0]: 6Fh: indicates a Sensor-specific Discreet Type code. This means use the sensor specific offsets to interpret the event data bytes
13 03hEvent Data 1: [7:6]: 00b = unspecified byte 2 event data

[5:4]: 00b = unspecified byte 3 event data

[3:0]: Offset from Event/Reading Code
0h: Critical stop during OS load/initialization. Unexpected error during system startup. Stopped waiting for input or power cycle/reset
1h: Run-time critical stop (aka ‘core dump’ or ‘blue screen’
2h: OS Graceful stop (system powered up, but normal OS operation has shut down and system is awaiting reset pushbutton, power-cycle or other external input) 3h: OS Graceful Shutdown (system graceful power down by OS)
4h: Soft Shutdown initiated by PEF
5h: Agent Not Responding. Graceful shutdown request to agent via BMC did not occur due to missing or malfunctioning local agent
14 FFh Event Data 2 Not specified per bits 7-6 in event data 1
15 FFh Event Data 3 Not specified per bits 5-4 in event data 1

Type DDh Shutdown Reason OEM Event Record

The IPMI driver reads the shutdown reason code is from the DWORD registry value at

HKLM/Software/Microsoft/Windows/CurrentVersion/Reliability/shutdown/ReasonCode (DWORD)

The reason code is then logged to the SEL with the following OEM Type DDh record:

Bytes Value Field Name Description
1:0SEL Record ID
2 DDh Record Type OEM Time stamped Record (bytes 7-15 are OEM Defined)DDh: OS Shutdown
6:3 SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10 Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11 Shutdown Reason Shutdown Reason which is read from the registry:HKLM/Software/Microsoft/Windows/CurrentVersion/Reliability/shutdown/ReasonCode (DWORD)
1500hReserved

Type DDh Shutdown Comment OEM Event Record

Similarly, the shutdown comment is a REG_SZ value read from the same registry key.

HKLM/Software/Microsoft/Windows/CurrentVersion/Reliability/shutdown/Comment (REG_SZ)

Bytes Value Field Name Description
1:0SEL Record ID
2 DDh Record Type OEM Time stamped Record (bytes 7-15 are OEM Defined)DDh: OS Shutdown
6:3 SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10 Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11 Shutdown Comment Shutdown Comment which is read from the registry:HKLM/Software/Microsoft/Windows/CurrentVersion/Reliability/shutdown/Comment (REG_SZ)
1500h Reserved

Disabling the Type DDh Shutdown Comment records

Because the shutdown comment can take so many records to log, it can cause the SEL to become full very quickly. Microsoft released a hotfix to allow for disabling the shutdown log comments for Windows Server 2008 SP1. This hotfix can be found at:

http://support.microsoft.com/kb/962920

Starting with Windows Server 2008 R2, the functionality is present in the OS without applying the hotfix. So for windows Server 2008 SP1, you must apply the hotfix before modifying the registry, but for Windows Server 2008 SP2 and later you can modify the registry without applying the hotfix.

1.Open regedit and navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\IPMI
2.Create a new DWORD Value named DisableSELShutdownComment
3.Right-click DisableSELShutdownComment, and then click Modify.
4.In the Value data box, type 1, and then click OK.
5.Close regedit and reboot

Bugcheck Events
A system bugcheck (bluescreen) will cause six records to be written to the event log. A type 02h System Event records is written, followed by five type DEh OEM event records: One for the bugcheck code, and one for each of the four parameters to the bugcheck.

Type 02h Bugcheck System Event Record

Like the other Type 02h System event records logged by the IPMI driver, the relevant information starts after the header at byte 10. In the case of the bugcheck, the sensor type is 20h which is the same as the Shutdown system event record, but the event data byte at byte 13 indicates runtime critical stop.

BytesValue Field Name Description
1:0SEL Record ID record identifier
202hRecord Type 02h indicates a system event record
6:3SEL Timestamp
8:70041hGenerator ID 0041h indicates the event comes from system software whose ID 20h
9 04h EvMRev IPMI 2.0 Event Message Revision
10 20h Sensor Type: OS Stop/Shutdown Sensor type 1Fh is OS Boot as specified in the IPMI spec
11 00h Sensor Number
12 6FhEvent Type [7]: 0b: indicates an assertion event

[6:0]: 6Fh: indicates a Sensor-specific Discreet Type code. This means use the sensor specific offsets to interpret the event data bytes
13 01hEvent Data 1[7:6]: 00b = unspecified byte 2 event data

[5:4]: 00b = unspecified byte 3 event data

[3:0]: Offset from Event/Reading Code 0h:Critical stop during OS load/initialization. Unexpected error during system startup. Stopped waiting for input or power cycle/reset

1h:Run-time critical stop (aka ‘core dump’ or ‘blue screen’

2h:OS Graceful stop (system powered up, but normal OS operation has shut down and system is awaiting reset pushbutton, power-cycle or other external input)

3h:OS Graceful Shutdown (system graceful power down by OS)

4h:Soft Shutdown initiated by PEF

5h:Agent Not Responding. Graceful shutdown request to agent via BMC did not occur due to missing or malfunctioning local agent
14 FFh Event Data 2 Not specified per bits 7-6 in event data 1
15 FFh Event Data 3 Not specified per bits 5-4 in event data 1

Type DEh Bugcheck Code OEM Event Record

The bugcheck code is the stop code displayed on the bluescreen. It is used to indicate the type of failure that caused the bugcheck. The OEM Type DEh event record saves the bugcheck code to the SEL.

Bytes Value Field Name Description
1:0SEL Record ID
2 DEhRecord Type OEM Time stamped Record (bytes 7-15 are OEM Defined)DEh: OS Bugcheck
6:3 SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10 Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11 Bugcheck Stop Code Stop code listed on the BSOD
15System Architecture 00: 32bit OS
01: 64bit OS

Type DEh Bugcheck Parameter OEM Event Record

When the system encounters a condition or error it can’t handle, a system call is made to bugcheck the system. In addition to the bugcheck code described above, four parameters are passed to further describe the failure. This information can be used to debug the system and figure out why the crash occurred. The OEM Type DEh Bugcheck Parameter Event record is described below:

Bytes Value Field Name Description
1:0SEL Record ID
2 DEhRecord Type OEM Time stamped Record (bytes 7-15 are OEM Defined)

DEh: OS Bugcheck
6:3 SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10 Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11 Bugcheck Parameter Argument to Bugcheck. These are the same arguments listed on the BSOD
15System Architecture 00h: 32bit OS
01h: 64bit OS


This document is also available in Microsoft Word format as well, and it can be downloaded by clicking here.


BMC SEL Log

$
0
0
Revision 25 posted to Systems Management - Wiki by Peter Tsai on 11/16/2010 1:54:05 PM
What are These Baseboard Management Controller (BMC) System Event Log (SEL) Records Logged by Windows?

iDRAC6 SEL Log
Introduction
Did you ever notice a bunch of entries in the Baseboard Management Controller (BMC) System Event Log (SEL) that seem to be coming from Windows? Not the Windows system event log, but the SEL that is accessible from the Baseboard Management Controller (BMC).

It may seem that this log is only intended for hardware events and errors, but there is an OS driver that also logs events to it. Starting with Windows Server 2003 R2, Microsoft began shipping the Intelligent Platform Management Interface (IPMI) driver. One of its functions is to log certain OS events to the SEL. The IPMI driver writes multiple records to the SEL for these three types of events: boot up, shutdown and bugcheck events.

The BMC SEL log is accessible via the sideband BMC interface using tools like ipmitool or impish. It is also accessible from OpenManage Server Assistant (OMSA), the Dell Remote Access Controller (DRAC) console, and <CTRL-E> during boot. Many different types of events, which can be useful in troubleshooting, are logged in the SEL. Each SEL record packs a lot of information in only 16 bytes, and given their limited size, they can be hard to decode.

Decoding the SEL Record


Dell BMC SEL record, pulled by racadm command line tool
The SEL record above was pulled using the Dell racadm command line tool available on the Dell Systems Management Tools and Documentation DVD.


Each SEL record is 16 bytes in length and the format is defined in the IPMI spec. The table below summarizes the format of the SEL record, as
defined by the IPMI spec. At the highest level, the Record Type field indicates whether it is a System Event Record or an OEM defined event record. System Event records are defined in the IPMI specification, and OEM records are defined by the OEM.

Each event logged by the IPMI driver (whether boot up, shutdown, or bugcheck) will cause one system event record and one or more OEM records to be logged to the SEL. The type 02h system event record format is defined in the table below.

BytesFieldDescription
1:0 SEL Record ID 16 bit record identifier

0000h: Reserved
0001h to FFFEh: SEL Record ID
FFFFh: Reserved
2 Record Type 02h: System Event Record

C0h to DFh: OEM Time stamped Record
Bytes 8-16 are OEM Defined

E0h to FFh: OEM Non-Time stamped Record
Bytes 4-16 are OEM Defined
6:3 SEL Timestamp Time when event was logged
8:7Generator ID Byte 8: System Software ID or IPMB Slave Address=============

[7:1]: System Software ID, or 7-bit I2C slave address
[0]: 0b means bits 7-1 are the IPMB Slave Address
1b means bits 7-1 are the System Software ID

Byte 7: Channel/LUN=============

[7:4]: Channel Number. Must be 0000b if the event was received via the system interface, primary IPMB, or internally generated by the BMC

[3:2]: Reserved. Must be 00b

[1:0]: IPMB device LUN if Byte 0 holds a slave address. 00b if Byte 0 holds a System Software ID
9 EvMRev 03h: IPMI 1.0 0

4h: IPMI 2.0
10 Sensor Type Sensor type code as specified in the IPMI spec
11 Sensor Number Number of the sensor that generated the event
12 Event Type [7]: Event Direction
0b: Assertion Event
1b: De-assertion Event


[6:0]: 7 bit Event/Reading Type Code
00h: Event/Reading Type unspecified
01h: Threshold
02h-0Ch: Generic Discrete
6Fh: Sensor-Specific Discrete
70h-7Fh: OEM Discrete. Indicates the discrete state info is specific to the OEM identified by the Manufacturer ID for the IPMI device that is providing access to the sensor
13 Event Data 1: Event Field Contents
14 Event Data 2 Event Field Contents
15 Event Data 3 Event Field Contents

Boot Up Events
During a system boot, two records are written to the SEL. The first is a type 02h System Event, and the second is an OEM event.

Type 02h Boot Up Record

The first 10 bytes of the type 02h System boot up record are general header information, and the boot-relevant information starts at byte 10.

BytesValue Field Name Meaning of Value
1:0
SEL Record ID record identifier
2 02h Record Type 02h indicates a system event record
6:3
SEL Timestamp
8:70041hGenerator ID 0041h indicates the event comes from system software whose ID 20h
9 04h EvMRev IPMI 2.0 Event Message Revision
10 1Fh Sensor Type:OS boot Sensor type 1Fh is OS Boot as specified in the IPMI spec
11 00h Sensor Number
12 6FhEvent Type [7]: 0b: indicates an assertion event

[6:0]: 6Fh indicates a Sensor-specific Discreet Type code. This means use the sensor specific offsets to interpret the event data bytes
13 01h Event Data 1: C: Boot Completed[7:6]:00b = unspecified byte 2 event data

[5:4]: 00b = unspecified byte 3 event data

[3:0]: Offset from Event/Reading Code
0h: A: boot completed 1h: C: boot completed
2h: PXE boot completed
3h: Diagnostic boot completed
4h: CD-ROM boot completd
5h: ROM boot completed
6h: boot completed-boot device not specified
14 FFh Event Data 2 Not specified per bits 7-6 in event data 1
15 FFh Event Data 3 Not specified per bits 5-4 in event data 1

Type DCh Boot Up OEM Event Record

The OEM Event record for bootup does not provide much more information. Nevertheless, the type DCh OEM Boot up event record looks similar to this:

Bytes Value Field Name Description
1:0
SEL Record ID
2 DCh Record Type OEM Time stamped Record (bytes 7-15 are OEM Defined)DCh: OS Boot up
6:3
SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10
Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11
Boot Time The OS Boot time
1500h Reserved Reserved


Shutdown Events
System shutdown events can cause many records to be logged to the SEL. There is one type 02h System Event record, one OEM type DDh record for the shutdown reason code, and zero or more OEM type DDh records for the shutdown comment.

Whenever a user shuts down a system using shutdown.exe, the reason and comment entered by the user are saved in the registry. Then the IPMI driver reads them from the registry and logs them to the SEL with OEM type DDh records. The shutdown reason is a 4 byte code which fits within SEL entry. The shutdown comment, however, is a user-entered string of variable length.

The IPMI driver saves the comment string to the SEL in multiple OEM type DDh records, concatenated using the sequence number. This can be problematic because there are only 4 bytes available for the comment per SEL entry, and the comment is saved as a Unicode string.

This can quickly fill the SEL log. During a manual shutdown (Start | Shutdown), even though the user is required to enter a reason and comment, the comment is never saved to the registry, and therefore not logged to the SEL. Furthermore, an incorrect reason code is saved. See Microsoft KB200106 (http://support.microsoft.com/kb/2001061).

Type 02h System Shutdown Event Record

Again, the first 10 bytes of the type 02h System Event Record is all header information. The information relevant to the system shutdown starts at byte 10.

BytesValue Field Name Description
1:0
SEL Record ID record identifier
2 02hRecord Type 02h indicates a system event record
6:3
SEL Timestamp
8:70041hGenerator ID 0041h indicates the event comes from system software whose ID 20h
9 04h EvMRev IPMI 2.0 Event Message Revision
10 20h Sensor Type:OS Stop/Shutdown Sensor type 1Fh is OS Boot as specified in the IPMI spec
11 00h Sensor Number
12 6FhEvent Type [7]: 0b: indicates an assertion event
[6:0]: 6Fh: indicates a Sensor-specific Discreet Type code. This means use the sensor specific offsets to interpret the event data bytes
13 03hEvent Data 1: [7:6]: 00b = unspecified byte 2 event data

[5:4]: 00b = unspecified byte 3 event data

[3:0]: Offset from Event/Reading Code
0h: Critical stop during OS load/initialization. Unexpected error during system startup. Stopped waiting for input or power cycle/reset
1h: Run-time critical stop (aka ‘core dump’ or ‘blue screen’
2h: OS Graceful stop (system powered up, but normal OS operation has shut down and system is awaiting reset pushbutton, power-cycle or other external input) 3h: OS Graceful Shutdown (system graceful power down by OS)
4h: Soft Shutdown initiated by PEF
5h: Agent Not Responding. Graceful shutdown request to agent via BMC did not occur due to missing or malfunctioning local agent
14 FFh Event Data 2 Not specified per bits 7-6 in event data 1
15 FFh Event Data 3 Not specified per bits 5-4 in event data 1

Type DDh Shutdown Reason OEM Event Record

The IPMI driver reads the shutdown reason code is from the DWORD registry value at

HKLM/Software/Microsoft/Windows/CurrentVersion/Reliability/shutdown/ReasonCode (DWORD)

The reason code is then logged to the SEL with the following OEM Type DDh record:

Bytes Value Field Name Description
1:0
SEL Record ID
2 DDh Record Type OEM Time stamped Record (bytes 7-15 are OEM Defined)DDh: OS Shutdown
6:3
SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10
Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11
Shutdown Reason Shutdown Reason which is read from the registry:HKLM/Software/Microsoft/Windows/CurrentVersion/Reliability/shutdown/ReasonCode (DWORD)
1500hReserved

Type DDh Shutdown Comment OEM Event Record

Similarly, the shutdown comment is a REG_SZ value read from the same registry key.

HKLM/Software/Microsoft/Windows/CurrentVersion/Reliability/shutdown/Comment (REG_SZ)

Bytes Value Field Name Description
1:0
SEL Record ID
2 DDh Record Type OEM Time stamped Record (bytes 7-15 are OEM Defined)DDh: OS Shutdown
6:3
SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10
Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11
Shutdown Comment Shutdown Comment which is read from the registry:HKLM/Software/Microsoft/Windows/CurrentVersion/Reliability/shutdown/Comment (REG_SZ)
1500h Reserved

Disabling the Type DDh Shutdown Comment records

Because the shutdown comment can take so many records to log, it can cause the SEL to become full very quickly. Microsoft released a hotfix to allow for disabling the shutdown log comments for Windows Server 2008 SP1. This hotfix can be found at:

http://support.microsoft.com/kb/962920

Starting with Windows Server 2008 R2, the functionality is present in the OS without applying the hotfix. So for windows Server 2008 SP1, you must apply the hotfix before modifying the registry, but for Windows Server 2008 SP2 and later you can modify the registry without applying the hotfix.

1.Open regedit and navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\IPMI
2.Create a new DWORD Value named DisableSELShutdownComment
3.Right-click DisableSELShutdownComment, and then click Modify.
4.In the Value data box, type 1, and then click OK.
5.Close regedit and reboot

Bugcheck Events
A system bugcheck (bluescreen) will cause six records to be written to the event log. A type 02h System Event records is written, followed by five type DEh OEM event records: One for the bugcheck code, and one for each of the four parameters to the bugcheck.

Type 02h Bugcheck System Event Record

Like the other Type 02h System event records logged by the IPMI driver, the relevant information starts after the header at byte 10. In the case of the bugcheck, the sensor type is 20h which is the same as the Shutdown system event record, but the event data byte at byte 13 indicates runtime critical stop.

BytesValue Field Name Description
1:0
SEL Record ID record identifier
2 02hRecord Type 02h indicates a system event record
6:3
SEL Timestamp
8:70041hGenerator ID 0041h indicates the event comes from system software whose ID 20h
9 04h EvMRev IPMI 2.0 Event Message Revision
10 20h Sensor Type: OS Stop/Shutdown Sensor type 1Fh is OS Boot as specified in the IPMI spec
11 00h Sensor Number
12 6FhEvent Type [7]: 0b: indicates an assertion event

[6:0]: 6Fh: indicates a Sensor-specific Discreet Type code. This means use the sensor specific offsets to interpret the event data bytes
13 01hEvent Data 1[7:6]: 00b = unspecified byte 2 event data

[5:4]: 00b = unspecified byte 3 event data

[3:0]: Offset from Event/Reading Code 0h:Critical stop during OS load/initialization. Unexpected error during system startup. Stopped waiting for input or power cycle/reset

1h:Run-time critical stop (aka ‘core dump’ or ‘blue screen’

2h:OS Graceful stop (system powered up, but normal OS operation has shut down and system is awaiting reset pushbutton, power-cycle or other external input)

3h:OS Graceful Shutdown (system graceful power down by OS)

4h:Soft Shutdown initiated by PEF

5h:Agent Not Responding. Graceful shutdown request to agent via BMC did not occur due to missing or malfunctioning local agent
14 FFh Event Data 2 Not specified per bits 7-6 in event data 1
15 FFh Event Data 3 Not specified per bits 5-4 in event data 1

Type DEh Bugcheck Code OEM Event Record

The bugcheck code is the stop code displayed on the bluescreen. It is used to indicate the type of failure that caused the bugcheck. The OEM Type DEh event record saves the bugcheck code to the SEL.

Bytes Value Field Name Description
1:0
SEL Record ID
2 DEhRecord Type OEM Time stamped Record (bytes 7-15 are OEM Defined)DEh: OS Bugcheck
6:3
SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10
Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11
Bugcheck Stop Code Stop code listed on the BSOD
15
System Architecture 00: 32bit OS
01: 64bit OS

Type DEh Bugcheck Parameter OEM Event Record

When the system encounters a condition or error it can’t handle, a system call is made to bugcheck the system. In addition to the bugcheck code described above, four parameters are passed to further describe the failure. This information can be used to debug the system and figure out why the crash occurred. The OEM Type DEh Bugcheck Parameter Event record is described below:

Bytes Value Field Name Description
1:0
SEL Record ID
2 DEhRecord Type OEM Time stamped Record (bytes 7-15 are OEM Defined)

DEh: OS Bugcheck
6:3
SEL Timestamp
9:7137hIPMI Manufacturer ID 137h (311d) is the IANA enterprise number for Microsoft
10
Sequence Number Sequence number used to concatenate the OEM Data bytes from multiple SEL entries
14:11
Bugcheck Parameter Argument to Bugcheck. These are the same arguments listed on the BSOD
15
System Architecture 00h: 32bit OS
01h: 64bit OS

This document is also available in Microsoft Word format as well, and it can be downloaded by clicking here.

CMC for Dell PowerEdge FX platform

$
0
0
Current Revision posted to Systems Management - Wiki by steven_zessin_Dell on 4/14/2015 2:32:28 PM

Quick Links:

What is CMC for FX?Blades Wiki
Release HistoryiDRAC8 Home
FX ManualsLifecycle Controller Home
White PapersCMC Home 
FX Useful LinksFX Home

What is CMC for FX?

The Dell PowerEdge FX architecture lets you precisely tailor, quickly deploy, and easily manage your infrastructure. With compute, storage and I/O modules in just 2U of rack space and 50% more available server-side storage, you can build a software-defined converged infrastructure that scales quickly and easily. In order to manage this platform, Dell is using its proven Chassis Management Controller (CMC) to manage the overall platform as well as its servers, networking components, and storage devices. With its familiar, easy-to-learn and use interface, Dell CMC lets you choose and use the system management style that best fits your needs. Manage FX servers individually via each embedded iDRAC with Lifecycle Controller as you would with traditional rack servers to integrate easily into server-level processes. Or manage FX servers collectively as you might already do with blade servers, using the Dell Chassis Management Controller (CMC) to manage FX. Either way, you can view and manage up to 20 separate FX systems from a single CMC management console for simplified collective management. As is the case with VRTX, Dell provides licensing choices for either comprehensive Enterprise or entry-level Express CMC options, whichever best suits a customer's needs.

 

FX Release History

Version 1.10

  • Initial release,  Dell Chassis Management Controller (CMC) for Dell PowerEdge FX2

 9 DEC 2014 (v1.10)

FX CMC Docs 

Dell Chassis Management Controller Version 1.1 for PowerEdge FX2/FX2s User's Guide 

HTML / PDF
RACADM Command Line Reference Guide PDF

FX White Papers
Chassis Management at Server
CMC Deployment Guide
Front Panel Guide
FX Power Management

 

FX Useful Links
Dell Enterprise Demo Tools
PowerEdge FX Platform Page
Tags: PowerEdge FX Converged CMC OpenManage

Dell EqualLogic Storage Management Pack Suite

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Deepak K on 4/15/2015 11:47:57 AM

 

Contents: Download - Documentation - Whitepapers - Forum


The Dell EqualLogic Storage Management Pack Suite for Microsoft System Center Operations Manager enables monitoring of Dell EqualLogic PS Arrays on System Center Operations Manager. The Management Packs provide a list of Dell-specific views that you can use to observe and drill down the system status in a network.

The latest version is 6.0 (released November 2014)

 Key new features in Dell EqualLogic Management Pack 6.0:

- Added support for Dell EqualLogic PS6210, PS-6500, and PS-6510.

- Supports EqualLogic firmware versions 6.0.x and 7.0.x

Key new features in Dell EqualLogic Management Pack 5.0:

- Support for Microsoft System Center 2012 Operations Manager R2 (Update: 11/15/13)

- Support for System Center Operations Manager 2012 and System Center 2012 Operations Manager SP1.
- Support for EqualLogic PS-M4100 Blade Array.
- Support for new Dell EqualLogic PS-Series Arrays PS4110 and PS6110.
- Support for new Equal Logic firmware versions 6.0.x, 5.1.x, 5.2.x.
- Feature Monitoring Dashboard simplifies the Import, Upgrade, Maintenance and Removal of   Dell Management Pack Suite features from the OpsMgr console.
- Support for monitoring Dell EqualLogic PS Series Arrays on SCOM 2007 R2 clustered RMS configurations.
- Support for RFC 1155 and SCSI & iSCSI SNMP Alerts.
- Newly added Inventory attributes
    - Storage Pool Borrowing Enabled (for Storage Pool).
    - Volume Recovery Enabled (for Group).
    - Member Chassis Flags (for Member Array).
    - Data Center Bridging Capability (for Ethernet Interface).

Key new features in Dell EqualLogic Management Pack 4.1 :

- Support for Storage Pool Monitoring and inventory.
- Health state change notification alerts are displayed for Volume and Disk groups.
- Network Interface alerts.
- Support for IPv6.
- Option for Scalable or Detailed Monitoring.   

 


Product Download

                                Download Other Versions : OpenManage Integrations Installer Downloads

 


Product Documentation

Version 6.0 Documentation

 

v4.0v4.1 v5.0

N/A

Installation Guide

Installation Guide

User's Guide

User's Guide

User's Guide

Readme

Readme

Readme

 


 Technical Article & Wikis

Tags: management pack, SCOM, MP, integrations, System Center

OpenManage Storage Services (OMSS)

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Amol B on 4/15/2015 11:56:01 AM

OM 7.2-Dell OpenManage-Enhancements in Virtual Disk Creation Wizard on Dell OpenManage Storage Services (OMSS)

Dell OpenManage Server Administrator Storage Management is designed for system administrators
who implement hardware RAID solutions and understand corporate and small business storage environments. Storage Management enables you to configure the storage components attached to your system. These components include RAID and non-RAID controllers and the channels, ports, enclosures, and disks attached to them.

Using Storage Management, you can configure and manage controller functions without accessing
the BIOS. These functions include configuring virtual disks and applying RAID levels and hot spares for data protection. You can initiate many other controller functions like rebuilds, troubleshooting, setting thresholds, and so on. Most functions can be configured and managed while the system remains
online and continues to process requests.

Enhancements in Virtual Disk Creation Wizard feature from OpenManage Storage Services (OMSS) are available from OpenManage v7.2 onwards.

  • This features provides an improved algorithm that allows you to create RAID volumes in a more usable and effective approach.
  • The feature has been developed keeping legacy compatibility in mind therefore retaining all other feature and support which were available in the previous versions.

For detailed information on the Storage Management Service, see the Dell OpenManage
Server Administrator Storage Management User's Guide at

http://support.dell.com/support/edocs/software/svradmin/

Downloads

The OpenManage System Tools and Documentation DVD ISO can be downloaded here:

 

Whitepaper -Video

The video link given below demonstrates a few scenarios of how to use Fluid Cache in OpenManage Storage Services (OMSS).

As a new feature of OM7.1.2 – OMSS – Fluid Cache is a solution that creates a large-scale, low-latency cache by using PCIe-SSD. It also includes features to prevent data loss or corruption while using caching techniques to increase performance.

The video demonstrates the following scenarios:

  • Loading a license
  • Configuring Fluid cache 
  • Removing Fluid cache
  • Enabling Fluid cache on Virtual Disk
  • Disabling Fluid cache on Virtual Disk
  • Enabling Fluid cache on Virtual Disk Partition
  • Disabling Fluid cache on Virtual Disk Partition
  • Removing Fluid cache from Fluid Cache Pool
  • Viewing the Statistics of the Cache Pool

(Please visit the site to view this video)

Below whitepaper Video explaining the methods of OpenManage Storage Services(OMSS) aided Virtual Disk creation via Express and Advanced Wizard on Dell PowerEdge™ systems. 


As a new feature of OM7.2 – OMSS – Virtual Disk Creation Wizard,an improved algorithm that allows ustomers to create (any supported) RAID volumes in a more usable and effective approach is implemented. This video primarily showcase the user interactive pages of the same.

Video shows screen by screen deep dive for:

  • Virtual Disk creation using the Express Wizard
  • Virtual Disk creation using the Advanced Wizard with Dedicated Hot spare
  • Virtual Disk creation using the Advanced Wizard with Dedicated Hot spare and Encryption

(Please visit the site to view this video)

OpenManage Storage Services 7.2 - Enhancements in virtual Disk Creation Wizard 


 

Tags: openmanage

Dell Catalogs

$
0
0
Revision 55 posted to Systems Management - Wiki by DELL-Deepak R on 4/16/2015 8:51:48 AM

Under Construction

What is Catalog ?
What's New + Downloads

 

What is Catalog?

Biz Client Catalog

Biz Client Catalog is an aggregation of all Dell Update Packages’ (DUP) metadata carried for Dell Optiplex, Dell Latitude, Dell Precision and Dell Tablet brands of systems. These are utilized through end-user products like Dell Command Update/ Dell Client System Update, Dell Repository Manager and Software Centre Configuration Manager / Software Center Update Publisher.

Biz Client Catalogs are released every fortnight on the 2nd and 4th Tuesday of every month.

DatePDK CatalogSDP Catalog
2/11/2014PDK Catalog FileSDP Catalog File

Enterprise Catalog

Enterprise Catalog is an aggregation of all Bundles and Dell Update Packages’ metadata carried for Dell PowerEdge, Dell PowerVault and Dell EqualLogic Servers

 

Enterprise Catalogs are released every month 2nd Friday

What's New + Downloads

DatePDK Catalog
03/13/2015FOLDER02866069M
02/13/2015FOLDER02824900M
01/09/2015FOLDER02757636M
12/12/2014FOLDER02730016M
11/14/2014FOLDER02680305M
10/10/2014FOLDER02536758M
09/12/2014FOLDER02471331M
08/08/2014FOLDER02370107M
07/11/2014FOLDER02301814M
06/13/2014FOLDER02255069M
05/09/2014FOLDER02181628M
04/11/2014FOLDER02079336M
03/14/2014FOLDER02070005M

 

 

 

 

 

 

 

 

 

 

Date            LC Catalog         LC Catalog sign file  
04/10/2015FOLDER02928477MFOLDER02928478M
03/13/2015FOLDER02866087MFOLDER02866088M
02/13/2015FOLDER02824898MFOLDER02824899M
01/09/2015FOLDER02757653MFOLDER02757654M
12/12/2014FOLDER02729985MFOLDER02729986M
11/14/2014FOLDER02680325MFOLDER02680326M
10/10/2014FOLDER02536777MFOLDER02536781M
09/12/2014FOLDER02471328MFOLDER02471329M
08/08/2014FOLDER02370118MFOLDER02370119M
07/11/2014FOLDER02301820MFOLDER02301821M
06/13/2014FOLDER02255076MFOLDER02255078M
05/09/2014FOLDER02181630MFOLDER02181631M
04/11/2014FOLDER02078462MFOLDER02078463M
03/14/2014FOLDER02069991MFOLDER02069992M

DateSDP Catalog
02/13/2015FOLDER02823528M
01/09/2015FOLDER02764618M
12/12/2014FOLDER02729544M
11/14/2014FOLDER02679396M
10/10/2014FOLDER02548895M
09/12/2014FOLDER02474216M
08/08/2014FOLDER02354058M
07/25/2014FOLDER02332832M
06/27/2014FOLDER02272303M
05/22/2014FOLDER02210207M
04/25/2014FOLDER02158841M

 

Dell OpenManage Deployment Toolkit

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Amol B on 4/16/2015 3:47:07 PM

The Dell OpenManage Deployment Toolkit (DTK) includes a set of utilities, sample scripts, and sample configuration files that you can use to deploy and configure the Dell systems. You can use DTK to build script-based and RPM-based installation for deploying large number of systems on a pre-operating system environment in a reliable way, without changing their current deployment processes. Using DTK you can install operating systems on Dell systems in BIOS or Unified Extensible Firmware Interface (UEFI) mode.

In addition to the command line utilities used to configure various system features, DTK also provides sample scripts and configuration files to perform common deployment tasks and documentation. These files and scripts describe the use of the DTK in Microsoft Windows Pre-installation Environment (Windows PE) and Linux environments.

The benefits of the DTK:

  • Provides the tools necessary to automate the pre-operating system configuration tasks and the unattended operating system installation tasks when deploying PowerEdge systems.
  • Scales to support from one to many system deployment efforts.
  • Facilitates consistent system configurations across multiple systems.
  • Provides diverse and useful deployment tools that can be utilized in many different ways.

Downloads

The Dell OpenManage Deployment Toolkit is free of charge and can be downloaded here:

Whitepaper - Documents

Configuring Dell server deployments end to end with Deployment Took Kit

Above whitepaper targets the below functionalities

  • Use DTK to configure a bare metal server with both native and advanced options.
  • Proceed on to deploy an operating system (unattended). 
  • Continue Keeping your Dell Server's driver and firmware updated with System Update Utility (SUU).

Whitepaper - Videos

(Please visit the site to view this video)
Creating a WinPE 5.0 ISO file using Dell Open Manage Deployment Toolkit
(Please visit the site to view this video)
Dell OpenManage Deployment Toolkit 4.2 - RPM Installation on Linux Redhat
 
(Please visit the site to view this video)
Dell OpenManage Deployment Toolkit (DTK) Version 4.1 Linux OS Installation
 
 
(Please visit the site to view this video)
DTK Windows OS Installation - Dell OpenManage Toolkit 4.1
 
 
Tags: bios, WinPE 5.0, Deployment ToolKit, ISO IMAGE, dtk 4.4 dtk 7.4, openmanage, DTK, whitepapers, videos

DCIM.Library.Profile

$
0
0
Revision 166 posted to Systems Management - Wiki by steven_zessin_Dell on 4/16/2015 3:56:52 PM

Quick Links:

iDRAC8 13GiDRAC8 Home
iDRAC7 1.55.55 with LC2 1.4.0iDRAC7 Home
iDRAC7 1.51.51 with LC2 1.3.0Lifecycle Controller 2 Home
CMC for VRTX 1.0 & 1.2.5 & 1.3CMC for M1000e & VRTX Home
CMC for M1000eManaged Object File (MOF) Home
iDRAC7 - LC2 1.1Other Profile Documents
iDRAC7 - LC2 1.0
iDRAC6 - LC1 1.5.1 
iDRAC6 - LC1 1.4

 

iDRAC6 - LC1 1.3

iDRAC6 - LC1 1.2

 

DCIM Extensions Library Profile Collection

iDRAC8 (13th Generation PowerEdge)

DCIM Base Metrics Profile 1.3

DCIM Base Server and Physical Asset Profile 1.2

DCIM BIOS and Boot Management Profile 1.3.1

DCIM CPU Profile 1.2

DCIM Fiber Channel Profile 1.0.1

DCIM iDRAC Card Profile 1.5

DCIM LC Management Profile 1.8

(DMTF DSP1108) Physical System View Profile 1.0

DCIM Sensors Profile 1.1.2

DCIM Simple RAID Profile 1.6

DCIM System Info Profile 1.5.1

DCIM System Quick Sync Profile 1.1.0

DCIM USB Device Profile 1.0

 

 

 

iDRAC7 1.55.55 with Lifecycle Controller 2 1.4.0

iDRAC7 1.51.51 with Lifecycle Controller 2 1.3.0

The same set of profiles are applicable for both the above releases. 

DCIM CPU Profile 1.1

DCIM Fan Profile 1.1

DCIM LC Management Profile 1.7

DCIM Memory Profile 1.1

DCIM PCI Device Profile 1.1.0

DCIM Power Supply Profile 2.1.1

DCIM Record Log Profile 1.1.1

DCIM Simple NIC Profile 1.3

DCIM Software Update Profile 1.1.0

DCIM System Info Profile 1.4.1

DCIM Video Profile 1.0.1

DCIM Fibre Channel Profile 1.0

DCIM iDRAC Card Profile 1.3.1

DCIM OS Deployment Profile 1.6

DCIM Simple RAID Profile 1.5

 

CMC  for VRTX  1.3.0

Chassis System Info Profile 1.2.0

Chassis PCI Management Profile 1.1.0

Chassis RAID Profile 1.1.0

CMC  for VRTX  1.2.5

Chassis System Info Profile 1.1

CMC  for VRTX  1.0

Chassis Event Filter Profile

Chassis Job Control Profile

Chassis License Management Profile

Chassis PCI Management Profile

Chassis RAID Profile

Chassis Record Log Profile

Chassis Software Inventory Profile

Chassis System Info Profile

CMC Profile

 

CMC  for M1000e

 Active Directory Client (Dell)

Base Metrics (DMTF)

Base Server (DMTF)

Boot Control (DMTF)

Modular System (DMTF)

Physical Asset (DMTF)

Power State Management (DMTF)

Power Supply (Dell)

Power Supply (DMTF)

 Power Topology (Dell)

 Profile Registration (DMTF)

 Record Log (DMTF)

 Role Based Authorization (DMTF)

Sensors (DMTF)

Service Processor (Dell)

Simple Identity Management (DMTF)

 Simple NIC (Dell)

 

iDRAC7 with Lifecycle Controller Technology   2.1.0

DCIM Base Metrics Profile 1.2

DCIM Base Server and Physical Asset Profile 1.1

DCIM BIOS and Boot Management Profile 1.3

DCIM CPU Profile 1.1

DCIM Event Filter Profile 1.0

DCIM Fan Profile 1.0

DCIM Fiber Channel Profile 1.0

DCIM iDRAC Card Profile 1.3

DCIM Job Control Profile 1.3 

DCIM License Management Profile 1.0

DCIM LC Management 1.6

DCIM Memory Profile 1.1

DCIM OS Deployment Profile 1.5

DCIM PCI Device Profile 1.0

DCIM Persistent Storage Profile 1.0

DCIM Power State Management Profile 1.0

DCIM Power Supply Profile 2.1

DCIM Profile Registration Profile 1.1

DCIM RAID Profile 1.3

DCIM Record Log Profile 1.0

DCIM Role Based Authorization Profile 1.0

DCIM Sensors Profile 1.1

DCIM Service Processor Profile 1.1

DCIM Simple Identity Management Profile 1.0

DCIM Simple NIC Profile 1.3

DCIM Software Inventory Profile 1.1

DCIM Software Update Profile 1.0

DCIM System Info Profile 1.4

DCIM Video Profile 1.0

 

 

  iDRAC7 with Lifecycle Controller Technology 2.0.0

DCIM Base Metrics Profile 1.0

DCIM Base Server and Physical Asset Profile 1.0

DCIM BIOS and Boot Management Profile 1.2

DCIM CPU Profile 1.0

DCIM Event Filter Profile 1.0

DCIM Fan Profile 1.0

DCIM iDRAC Card Profile 1.2

DCIM Job Control Profile 1.2

DCIM License Management Profile 1.0

DCIM LC Management 1.5

DCIM Memory Profile 1.1

DCIM OS Deployment Profile 1.4

DCIM PCI Device Profile 1.0

DCIM Persistent Storage Profile 1.0

DCIM Power State Management Profile 1.0

DCIM Power Supply Profile 2.1

DCIM Profile Registration Profile 1.0

DCIM RAID Profile 1.2

DCIM Record Log Profile 1.0

DCIM Role Based Authorization Profile 1.0

DCIM Sensors Profile 1.0

DCIM Simple Identity Management Profile 1.0

DCIM Service Processor Profile 1.0

DCIM Simple NIC Profile 1.2

DCIM Software Inventory Profile 1.1

DCIM Software Update Profile 1.0

DCIM System Info Profile 1.2

DCIM Video Profile 1.0

 

 

 iDRAC6 with Lifecycle Controller Technology  1.5.1

DCIM BIOS and Boot Management Profile 1.1

DCIM CPU Profile 1.0

DCIM Fan Profile 1.0

DCIM iDRAC Card Profile 1.1

DCIM Job Control Profile 1.1

DCIM LC Management Profile 1.3

DCIM Memory Profile 1.0

DCIM OS Deployment Profile 1.2

DCIM RAID Profile 1.1

DCIM PCI Device Profile 1.0

DCIM Persistent Storage Profile 1.0

DCIM Power Supply Profile 2.0

DCIM Simple NIC Profile 1.1

DCIM Software Inventory Profile 1.0

DCIM Software Update Profile 1.0

DCIM System Info Profile 1.1

 

 iDRAC6 with Lifecycle Controller Technology  1.4.0

DCIM BIOS and Boot Management Profile 1.0

DCIM CPU Profile 1.0

DCIM Fan Profile 1.0

DCIM iDRAC Card Profile 1.0

DCIM Job Control Profile 1.0

DCIM LC Management Profile 1.0

DCIM Memory Profile 1.0

DCIM OS Deployment Profile 1.1

DCIM RAID Profile 1.0

DCIM PCI Device Profile 1.0

DCIM Persistent Storage Profile 1.0

DCIM Power Supply Profile 2.0

DCIM Simple NIC Profile 1.0

DCIM Software Inventory Profile 1.0

DCIM Software Update Profile 1.0

DCIM System Info Profile 1.0

 

 iDRAC6 with Lifecycle Controller Technology  1.3.0

DCIM Job Control Profile 1.0

DCIM LC Management Profile 1.0

DCIM OS Deployment Profile 1.1

DCIM Software Inventory Profile 1.0

DCIM Software Update Profile 1.0

 

 

 iDRAC6 with Lifecycle Controller Technology  1.2.0

DCIM OS Deployment Profile 1.0

                                                               

 

Other profile documents currrently published in this library (in alphabetical order by title):


 

Tags: profile, Dell CIM, DCIM

Install and Configure OMSA on ESX

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Amol B on 4/16/2015 4:21:58 PM

Here's a script that will install and configure the Dell™ OpenManage Server Administrator (OMSA) agent on VMware ESX 4.x It will also configure the SNMP settings and open the default ports in the firewall to allow communication.

This page covers OMSA support for EX 4.x - for OpenManage support for VMware ESXi 5, please visit
OpenManage Support for VMware ESXi 5.0

The current version as of January 2011 is 6.4
- OpenManage Server Administrator Managed Node for ESX 4.1
- OpenManage Server Administrator Managed Node for ESX 4.0



The current version as of 11/2010 is 6.3 :
- Download for ESX 4.0


You can also search ftp.dell.com/sysman for the latest

If you've never installed OMSA on ESX, don't start with this script! Read the documentation first: "Installing Dell OpenManage in a VMware ESX Server Software Environment. After you have a grasp of the steps necessary, you can use this script as a stand-alone, or integrate it as part of your standard installation procedures.

Script to Install OMSA on ESX

# scott_hanson@dell.com - www.delltechcenter.com
#
# Script to install OMSA on ESX 4.x, configure firewall, and snmp settings
#
# PreReq : OMSA tar from support.dell.com, as of 8-6-2009 the latest is the
# one listed below in the OMSA_TAR variable.
#
# Create a working directory (WD) and copy this script and
# the tarball there, then execute the script.
#
# WARNING : If you've never installed OMSA on ESX, DON'T start with
# this script. Walk before you run, read the DOCS
#


# Some variables you might like to change
WD=/root/om63
OMSA_TAR=OM-SrvAdmin-Dell-Web-LX-6.3.0-2075.ESX40.i386_A00.11.tar.gz
COMMUNITY_NAME=public
SNMP_TRAP_DEST=192.168.50.118


# Creating working directory and untar OMSA
mkdir $WD/working
cd $WD/working
tar -zxvf $WD/$OMSA_TAR

# Installing and starting OMSA
# NOTE: With ver 6.1 the "b" option changed to the "d" option
#
# x = express - Install all components
# d = Dell Agent
# w = web interface
# r = DRAC services
# s = storage management

echo '*** Installing and starting OMSA Agent ***'
$WD/working/linux/supportscripts/srvadmin-install.sh -x
$WD/working/linux/supportscripts/srvadmin-services.sh restart


# Open port in firewall for OMSA web interface
echo '*** Opening port 1311 for OMSA web interface ***'
esxcfg-firewall -o 1311,tcp,in,OpenManageRequest


# Configuration of snmp settings
echo '*** Configuring snmp and restarting snmp service ***'
cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.BACKUP
sed -i "s/rocommunity.*/rocommunity $COMMUNITY_NAME/g" /etc/snmp/snmpd.conf

sed -i "s/trapcommunity.*/trapcommunity $COMMUNITY_NAME/g" /etc/snmp/snmpd.conf
sed -i "s/trapsink.*/trapsink $SNMP_TRAP_DEST/g" /etc/snmp/snmpd.conf
service snmpd restart


# Configuration of firewall for snmp
echo '*** Configuring firewall to allow snmp traffic ***'
esxcfg-firewall -e snmpd


# Cleanup
echo '*** Removing working files and directory ***'
rm -rf $WD/working
echo '*** OMSA installation and configuration complete ***'

OpenManage Essentials

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Rob C on 4/16/2015 4:46:04 PM

Contents: Download - Documentation - Whitepapers - Videos - Forum - Blogs - FAQ 

OpenManage Essentials (OME) is a systems management console that provides simple, basic Dell hardware management and is available as a free download.

The latest release is OME 2.0 and it launched on September 8, 2014.  It brings a lot of great new features to the product.

OpenManage Essentials is an easy to install, intuitive and simple to use, systems management console solution optimized for monitoring and managing Dell enterprise and remote office/business office-class hardware.  New features available with OpenManage Essentials v2.0 include 13th generation server support, enhancements in server discovery and agent-free update operations for legacy PowerEdge servers, and for 12G/13G servers, processes that enable automated bare-metal server and OS deployments and rapid detection of server configuration drift in production environments.     

 

Key benefits of Dell OpenManage Essentials v2.0: 

  • Comprehensive monitoring and control of Dell servers, storage, networking, business client hardware, firewall appliances, and supported 3rd party hardware, through a single systems management console 
  • Automation of basic management tasks that deliver increased productivity, fewer errors, continuity in processes, consistency in configurations, and operational cost savings     
  • Automated, agent-free implementations that enable uniform discovery, inventory, monitoring and update operations for Dell PowerEdge servers in physical  and virtual, multi-vendor operating system and hypervisor environments
  • Faster time from inactivity to productivity and value with automated PowerEdge bare-metal server and OS deployments (more details at this link)
  • Improved availability through rapid detection and resolution of issues related to server configuration drift from customer-defined baselines   

 

Key new features available with Dell OpenManage Essentials v2.0: 

  • Support for the new 13th generation PowerEdge servers
  • Guided discovery wizard that simplifies and speeds server discovery and setup operations
  • Deployment and update of iDRAC Service Modules (ISM)
  • Removal of OpenManage Server Administrator (OMSA) dependencies when updating pre-11th generation PowerEdge servers and windows drivers
  • Enhanced scalability to support 4,000 devices and 40,000 alerts in the console
  • Launch the virtual console of an IDRAC configured for Single Sign-On (SSO)
  • Additional inventory and reporting data
  • Displayof Warranty pop-up notification for devices
  • Deploy 64-bit Dell Update Packages (DUPs)
  • Discovery of CMC via the WSMan protocol now supported with CMC v5.x.
  • Server Configuration Management - available as a fee-based license for use with 12G/13G iDRAC Enterprise or iDRAC Express 

  • Template-based server/chassis configuration and OS deployment for bare-metal 12G/13G PowerEdge servers
  • Automated detection and notification of PowerEdge server(s)/chassis’ drift from a customer-defined  baseline configuration during server operation
  • Boot a system from a network-mounted ISO using iDRAC
  • Licenses are available at server point of sale (POS) as well as after point of sale (APOS)   
  • Feature/functionality is activated by entering the Server Configuration Management license key on iDRAC Enterprise or iDRAC Express

Existing OpenManage Essentials features also available now in OME v2.0:

  • Anytime, anywhere mobile access to data center health status information with OpenManage Mobile
  • Integration with Dell ProSupport SupportAssistforproactive remote support, automated support case creation and hardware failure notification sent securely to Dell technical support for intelligent issue analysis, diagnosis, and part-replacements upon customer request
  • Comprehensive, deep management visibility and control for Dell blades and Chassis Management Controller (CMC), Dell storage and networking devices, and Dell AppAssurethrough a context sensitive link and launch of the respective element management interface
  • Geographic View at-a-glance visibility of VRTX systems’ physical locations geographically mapped
  • Agent-free OOB inventory and update of Dell 11G and 12G PowerEdge servers
  • Agent-free monitoring of Dell PowerEdge 12G servers
  • Traditional agent-based systems management functionality in all supported 9-12G servers
  • Management of Dell PowerEdge C platforms with IPMI
  • Monitoring of non-Dell HW devices through import of 3rd party HW SNMP MIBs
  • Reporting of Warranty expiration and comprehensive inventory reports
  • Hardware component-level monitoring and updates for Dell PowerEdge servers, blade systems and internal storage arrays
  • Support and control of Dell hardware in Windows, Linux, VMware, Hyper-V and OpenSource  environments
  • Enhanced management functionality through integration with the following Dell solutions :
  • Dell KACE K1000 Appliance– comprehensive, economical and straightforward management of both clients and servers through a single interface
  • Dell Repository Manager– version control and scheduling of PowerEdge server updates 
  • Dell OpenManage Power Center– optimization of  PowerEdge power usage

 

Dell OpenManage Essentials Core Features:

Simple and effective

  • Modern UI and Faster responsiveness
  • Easy to install & low touch maintenance
  • Simple to use and learn

Basic Hardware Element Management

  •  Discover, Inventory & Monitoring Dell Servers, storage and networking switches.
  •  Update & Configure Dell Servers
  •  Asset reporting (ServiceTag, FRU and Warranty, etc)

Agent-free Management

  •  Discover and Correlate IDRAC / Server and Blades / Chassis
  •  Agent Free Monitoring on Dell 12th generation Dell servers.
  •  Update 11th and 12th Generation Dell PowerEdge servers (starting with OME v1.1)

OpenManage Essentials is available as a free download from the Dell Support Site. The OME console's inventory function integrates with the Dell Repository Manager to automatically facilitate the creation of custom repositories of new updates for your systems.  

If you are new to the product, Take the Quick Tour or watch the OME Overview Video below:

Download  

Discuss

Learn

Whitepapers and Best Practices

 
Setup / Settings
Discover
 
Configure
Monitor
Manage
Deploy / Update
Videos 
 
OME 2.0 Server Configuration Tutorial Videos
 
(Please visit the site to view this video)

Video 1: Adding Devices to the Bare Metal and Re-purpose Device Group

 

 (Please visit the site to view this video)

Video 2: Configuring Credentials and Scheduling Inventory

 

 (Please visit the site to view this video)

Video 3: Configuring a Deployment Share

 

 (Please visit the site to view this video)

Video 4: Creating a Configuration Template

 

 (Please visit the site to view this video)

Video 5: Deploying a Bare Metal Device

 

 (Please visit the site to view this video)

Video 6: Detecting Configuration Drift

 

 (Please visit the site to view this video)

Video 7: Auto Deploying Bare Metal Devices


 
General OME Tutorial Videos
 
(Please visit the site to view this video)
OpenManage Essentials 1.2 New Features 
(Please visit the site to view this video)
OpenManage Essentials 1.2 Search Bar
 

 
 
(Please visit the site to view this video)
OpenManage Essentials Overview Demo 
0:08 - Installing OpenManage Essentals 
0:56 - Discovery and Inventory
2:03 - Monitoring Health of Devices
2:43 - Using the Home Portal
5:58 - Deploying Updates
7:03 - KACE Integration + MonitoringOpenManage

 OpenManage Essentials and Repository Manager Integration
 Enable SNMP on OpenManage Server Administrator for ESXi4
 Enable SNMP on OpenManage Server Administrator for Windows
 Enable SNMP on OpenManage Server Administrator for Linux (RHEL)
 Dell OpenManage Essentials with KACE Integration 
 OpenManage Essentials Custom Alerts
 OpenManage Essentials Apply System Updates
 Installing Dell OpenManage Essentials
 OpenManage Essentials Discovery and Inventory
 Dell OpenManage Essentials Discovery

 

Archives / Historical downloads

Tags: OME, Essentials, openmanage

Dell Remote Access Controller - DRAC / iDRAC

$
0
0
Revision 110 posted to Systems Management - Wiki by Dell - John Abrams on 4/16/2015 6:59:22 PM

Welcome to 13G!iDRAC7 Home
iDRAC8 Current ReleaseiDRAC6 Home
iDRAC8 ManualsDRAC5 Home
iDRAC8 VideosLifecycle Controller Home
iDRAC8 Useful Links
White Papers
Licensing

  

What is iDRAC?

The integrated Dell Remote Access Controller (iDRAC) with Lifecycle Controller is embedded within every Dell PowerEdge™ server and provides functionality that helps IT administrators deploy, update, monitor, and maintain Dell servers with no need for any additional software to be installed. The Dell iDRAC works regardless of operating system or hypervisor presence because from a pre-OS or bare-metal state, iDRAC is ready to work because it is embedded within each server from the factory.

The Integrated Dell Remote Access Controller (iDRAC) is designed to make server administrators more productive and improve the overall availability of Dell servers. iDRAC alerts administrators to server issues, helps them perform remote server management, and reduces the need for physical access to the server.

   


iDRAC8 Quick Sync with OpenManage Mobile

(Please visit the site to view this video)

 

iDRAC8 Releases

iDRAC8 Release Information

iDRAC8

2.10.10.10

Enhancements:
- Support for the following PowerEdge systems:
 - PowerEdge FC430
 - PowerEdge M830
 - PowerEdge FC830
 - PowerEdge FD332

- Support for using single iDRAC firmware across Dell 12th and 13th generation PowerEdge servers.

- Support to switch the controller mode from RAID to HBA and back on PERC 9.1 and later controllers.

- Enables SSL encryption between client and server using 256 bit or higher.

- Added racadm proxy support for PowerEdge FX2 chassis. Allows an iDRAC administrator utilizing Chassis Management at Server (CMAS) to issue a racadm command to CMC using iDRAC.

- Added event proxy support for PowerEdge FX2 chassis. Allows an iDRAC managing a PowerEdge FX2 CMC utilizing CMAS to display CMC events.

- Added support for iDRAC Shared LOM on PowerEdge FX2 chassis.

- Upgraded OpenSSL v1.0.1j; response to CVE-2014-3566 for the "POODLE" issue.

- Upgraded OpenSSH v6.6; response to CVE-2010-5107, CVE-2014-2532.

- Added support for QLogic BCM57xx and BCM57xxx NIC cards.

- Added support for Intel Ethernet Network Adapters X710.

- Added support for the following Emulex network cards:
 - Emulex OneConnect OCe14102-U1-D 2-port PCIe 10GbE CNA
 - Emulex OneConnect OCm14104-U1-D 4-port 10GbE rNDC CNA
 - Emulex OneConnect OCm14102-U5-D 2-port 10GbE Mezz CNA
 - Emulex OneConnect OCm14102-U4-D 2-port 10GbE bNDC CNA
 - Emulex OneConnect OCe14102-N1-D 2-port PCIe 10GbE NIC
 - Emulex OneConnect OCm14104-N1-D 4-port 10GbE rNDC NIC
 - Emulex OneConnect OCm14102-N5-D 2-port 10GbE Mezz NIC
 - Emulex OneConnect OCm14102-N6-D 2-port 10GbE bNDC NIC

Fixes:
- VNC password is not retained in iDRAC after an iDRAC reboot.

- Assertion of PSx-PG-Fail in the SEL will be automatically de-asserted upon recovery of PSU-Good or removal of related PSU

7 April 2015

Update Package for Microsoft® Windows® 64-Bit. 

MD5 checksum: 4ee7ba5485071b9731e85af65a1898d1                                                           

Application

MD5 checksum: 42d449c2fffdd20416d7b0b592baa42a                                                           

iDRAC8

2.06.05

This build includes:

  • Support for PowerEdge R430 and R530

  • Configure CMC firmware update settings to perform firmware update for CMC
      and its shared components from iDRAC. This is applicable only for
      FX2/FX2s chassis.
  • Support for DNS domain name in SNMP traps.

12/9/2014

(Download)

iDRAC8 2.00.00.00

 

This build includes:

  • iDRAC8 with Lifecycle Controller delivers revolutionary systems management capabilities:

    -        Quick Sync bezel provides at-the-server management through NFC-enabled Android devices.  Configure a server and collect server inventory with a simple “tap” between the server bezel and mobile device.

    -        Zero-Touch Auto Configuration can deploy a server out of the box with no intervention required; reducing server configuration time by as much as 99%.  Just rack, cable, and walk away.

    -        iDRAC Direct lets customers use a USB cable or a USB key to provide configuration information to the iDRAC.  No more crash cart!

    -        Simplify motherboard replacement with Easy Restore: key settings, such as BIOS, NIC, and iDRAC as well as licenses are automatically restored from the front panel.

    -        Agent-free, real-time RAID management and configuration: use iDRAC to create and manage virtual disks, without reboots!

    -        Increase datacenter security: Support for UEFI Secure Boot, and new System Erase capabilities for server repurpose/retirement, and new SNMP v3 Trap support.

    -        Built-in Tech Support Report replaces the need for downloaded support tools; health reports are built right into iDRAC and can be uploaded to Dell Support.

9/12/2014

(Download)

  

iDRAC8 Manuals (high level)
User Guide2.0.0
RACADM ReferenceRACADM Command Line Reference Guide (2.0.0)

( top )

 

iDRAC8 Videos

Configure Network Settings

RAID Configuration

RAID Configuration - Break Mirror

RAID Configuration - Key Encryption

Firmware Update Using Local Drive (CD or DVD or USB)

Backup Server Profile

Freedom (OpenManage Mobile and iDRAC8 Quick Sync)

Staying above the flood (Big Data)

Simplified Management at the box (iDRAC Direct)

 ( top )

  

iDRAC8 Useful Links
Simplifying Systems Management with Dell OpenManage on 13G Dell PowerEdge Servers (OME Home)
Dell 13th Generation PowerEdge Server Resources
CMC Manuals (including User's Guides)
Online License Management Portal
RACADM Command Line Interface (RACADM vs WSMAN page)

  ( top )

  

iDRAC with Lifecycle Controller Technology Licensing Summary

Dell provides three main offerings: Basic Management, Express, and Enterprise. As in Dell’s 11th generation servers, Basic Management (called BMC in 11th generation) is the default for servers 200-500 series. For 600 series and above, iDRAC Express is the default offering that is part of the base configuration. It does not require a license to be installed, backed up, or managed. Express offers embedded tools, console integration, and simplified remote access.

However, most IT administrators want a deeper, more inclusive solution that allows them to manage servers as if they were physically near the server, and this is available by upgrading to the Enterprise license level, which is fully digital. Dell also stores a copy of the key and makes it available to you in an online License Management portal (https://www.dell.com/support/licensing/).

Tags: Lifecycle, DRAC5, Integrated Dell Remote Access Controller Enterprise, DRAC, iDRAC7, iDRAC6, web services, Systems Management, iDRAC7 Troubleshooting, LC Management, iDRAC, ws-man, DRAC script, Integrated Dell Remote Access Controller, system management, Wsman, lc

iDRAC7 Home

$
0
0
Current Revision posted to Systems Management - Wiki by Dell - John Abrams on 4/16/2015 7:04:33 PM

What is iDRAC?iDRAC8 Home
iDRAC7 Current/Recent ReleaseiDRAC6 Home
Dell iDRAC Service ModuleDRAC5 Home
iDRAC7 ManualsiDRAC7 White Papers Home
iDRAC7 Useful linksiDRAC Related Blog Posts
Licensing Lifecycle Controller 2 Home
iDRAC7 Video DemosiDRAC7 Troubleshooting

  

What is iDRAC?

The Integrated Dell Remote Access Controller with Lifecycle Controller (iDRAC6 with Lifecycle Controller 1 or iDRAC7 with Lifecycle Controller 2) is an embedded device in all Dell PowerEdge™ servers that helps IT administrators manage, monitor, update, and deploy Dell servers.

The Integrated Dell Remote Access Controller (iDRAC) is designed to make server administrators more productive and improve the overall availability of Dell servers. iDRAC alerts administrators to server issues, helps them perform remote server management, and reduces the need for physical access to the server.

iDRAC7 with Lifecycle controller technology is part of a larger datacenter solution that helps keep business critical applications and workloads available at all times. The technology allows administrators to deploy, monitor, manage, configure, update, troubleshoot and remediate Dell servers from any location, and without the use of agents. It accomplishes this regardless of operating system or hypervisor presence or state.   


iDRAC7 Video Overview

(Please visit the site to view this video)

 

iDRAC7 Releases

iDRAC7 Release Information

iDRAC7

2.10.10.10

This release supports both iDRAC7 and iDRAC8. Please refer to iDRAC8 page for details and download information.

April 2015
iDRAC7 1.66.65

Fixed:
1.When using iDRAC dedicated network port, if auto-negotiation time-out occurs, the iDRAC forces the network interface to 100Mbps full duplex.
2.Intermittent connection issues with iDRAC shared LOM network port.
3.In M1000e chassis, if QuickDeploy feature is enabled, the iDRAC IP address was intermittently not working from CMC.
4.iDRAC is not redirecting HTTP port connections to HTTPS port.
5.iDRAC responsiveness issues observed with hardware inventory and Lifecycle log display commands.
6.Firmware update process for backplane is not successful.
7.Hardware inventory command output does not display a few components for fully populated systems.
8.iDRAC performance issues observed during stress conditions with web interface, WSMAN, or RACADM commands.

12/2014 (Download)
iDRAC7 1.57.57

UPDATE - iDRAC7 firmware version 1.57.57 is now an URGENT update for all rack and tower-model server customers with redundant power supply units (PSUs)

This build includes:

  • Fix for SNMP v2 and SNMP v3 walk of the iDRAC7 MIB time out
  • Support for Delta HVDC PSU hot plug
  • Fix for SNMP v3 only working with the default password for USER2

note: this release also contains cumulative enhancements and updates from prior releases, including a fix for issues causing sluggish iDRAC7 response after a prolonged period of uptime (approx 45-100 days, depending on the usage). In some cases, if the iDRAC is not reset, it could become unresponsive and require a server power-off/on reset. This issue exists on firmware releases 1.50.50 through those prior to 1.56.55).

5/7/2014 (Download)

( top )

 

NEW -- Dell iDRAC Service Module

The integrated Dell Remote Access Controller (iDRAC) Service Module is an optional, lightweight software application that can be installed on Dell 12th Generation Servers with iDRAC7 to provide additional systems management information. This lightweight agent runs in the host operating system and provides monitoring functionality similar to OpenManage Server Administrator (OMSA). This new offering bridges the gap between iDRAC's monitoring coverage and that which the full OMSA agent provides today. Some of the key features include:

  • Lifecycle Controller Log replication in OS log (for Server Hardware Information via the OS/Hypervisor Log itself)
  • Watchdog functions for dependent iDRAC monitoring functions:
    • Host name
    • OS Name
    • OS Version

n.b. the memory footprint of the iSM is 3-5MB. For comparison, OMSA occupies 100+ MB.

Download version 1.0 (includes release notes and Windows and Linux versions)

The new iSM page in the iDRAC GUI can be used to select the monitoring functions required. For more installation information, please review the Dell iDRAC Service Module 1.0 Installation Guide. You can also take a look at this blog post about installing and configuring iSM.

iDRAC7 Manuals (high level)
User GuideiDRAC7 Manuals [1.0.0, 1.06.06, 1.10.10, 1.20.20, 1.23.23, 1.30.30, 1.40.40, 1.50.50)
RACADM ReferenceRACADM Command Line Reference Guide (1.0.01.06.06, 1.10.10, 1.20.20, 1.23.23, 1.30.30, 1.40.40, 1.50.50)

 ( top )

  

iDRAC7 Useful Links
iDRAC7 with Lifecycle Controller Quick Start Guide
OpenManage System Management SW Compatibility Matrix
CMC Manuals (including User's Guides)
Online License Management Portal
RACADM Command Line Interface (RACADM vs WSMAN page)
 iDRAC7 Alert Notification Enhancements Paper

  ( top )

  

iDRAC7 12th Generation Licensing Summary

At a high level, the features and offerings for iDRAC are similar between iDRAC6 and iDRAC7. Dell provides three main offerings: Basic Management, Express, and Enterprise. As in Dell’s 11th generation servers, Basic Management (called BMC in 11th generation) is the default for servers 200-500 series. For 600 series and above, iDRAC Express is the default offering that is part of the base configuration. It does not require a license to be installed, backed up, or managed. Express offers embedded tools, console integration, and simplified remote access.

However, most IT administrators want a deeper, more inclusive solution that allows them to manage servers as if they were physically near the server, and this is available by upgrading to the Enterprise license level, which is fully digital.

Because all 600-series servers ship with iDRAC7 Express enabled, customers can take advantage of the features and benefits provided by iDRAC7 with Lifecycle Controller 2.0 technology. Customers with 200-500 series can also upgrade their systems to either Express or Enterprise by simply installing a license key. A physical part is required on 200-500 series to enable dedicated NIC and vFlash. Dell offers an online portal to keep track all of your iDRAC licenses; for example, which servers have Express, Enterprise, or even Trial licenses. In the unlikely event of motherboard failure, Dell also stores a copy of the key and makes it available to you in an online License Management portal (https://www.dell.com/support/licensing/).   

DCIM.Library.MOF

$
0
0
Current Revision posted to Systems Management - Wiki by ajay_shenoy on 4/17/2015 8:16:13 AM

Quick Links:

iDRAC8 HomeProfile's Home
iDRAC7 HomeLifecycle Controller Home
iDRAC6 Home

 

DCIM Extensions Library MOF Collection

DCIM is a schema that describes Dell extensions to the DMTF Common Information Model (CIM). DCIM schema describes the classes that represent various Dell management domains such as monitoring, inventory, update and configuration. These classes are exposed through Dell platform management access points such as iDRAC and CMC.  

The DCIM schema classes are described in the below MOF (Managed Object Format) files. Console developers and script writers can take advantage of the MOF files to process the objects returned from Dell platform management access points. Since DCIM schema extends from DMTF CIM schema, DCIM MOF files must be used in conjunction with DTMF CIM MOF files. DCIM MOF files together with DMTF CIM MOF files yield the full description DCIM class attributes such as properties and methods.


You may freely download and use the MOFs on this page and referring pages as long as you do not change the notice included in the files. If not already included, this notice will apply.

MOFs per Release
DCIM MOFsRequired DMTF CIM MOFs
iDRAC8 with LC MOFs (2.10.10.10)DMTF CIM Schema 2.26 Experimental MOF
iDRAC8 with LC MOFs (2.00.00.00)DMTF CIM Schema 2.26 Experimental MOF
Lifecycle Controller 2 1.4.0 MOFsDMTF CIM Schema 2.26 Experimental MOF
Lifecycle Controller 2 1.1.5 MOFs DMTF CIM Schema 2.26 Experimental MOF
Lifecycle Controller 2.1 MOFsDMTF CIM Schema 2.26 Experimental MOF
Lifecycle Controller 2.0 MOFsDMTF CIM Schema 2.26 Experimental MOF
Lifecycle Controller 1.5 MOFsDMTF CIM Schema 2.26 Experimental MOF
Lifecycle Controller 1.4 MOFsDMTF CIM Schema 2.26 Experimental MOF


Back to DCIM Library page.

Tags: Lifecycle, DCIM_VirtualDiskView.MOF, DCIM_View, LifecycleController, Integrated Dell Remote Access Controller Enterprise, DCIM, DCIM_RAIDInteger, DCIM_RAIDString, DCIM_View.MOF, iDRAC7, iDRAC6, DCIM_PhysicalDiskView.MOF, DCIM_RAIDService.MOF, winrm, Lifecycle Controller, Lifecycle Controller Management Profile, web services, MOF, iDRAC Card Profile, LC Integrations, LC Management, DCIM RAIDEnumeration, iDRAC, Integrated Dell Remote Access Controller, LC Management Profile, dmtf, lc

Lifecycle Controller

$
0
0
Revision 354 posted to Systems Management - Wiki by ajay_shenoy on 4/17/2015 8:25:28 AM

 



Quick Links: 

Executive SummaryiDRAC8 (13G) Home
Lifecycle Controller ReleasesWhite Papers
Web Services Integration ToolsOther References
Reference SpecsLifecycle Controller 2 (LC2) Home
Attribute Registries and Event/Error ReferenceLifecycle Controller 1 (LC1) Home
Lifecycle Controller BlogsCMC for M1000e & VRTX Home

  


Executive Summary

With the launch of the Dell PowerEdge 13th generation servers on Sept 9th, 2014, Dell has enhanced our embedded management without the need to install a software based agent within the host operating system. At the heart of the 13th generation servers embedded management is the iDRAC8 with Lifecycle Controller technology, which allows users to perform useful tasks such as configure BIOS and hardware settings, deploy operating systems, update drivers, change RAID settings, and save hardware profiles. Together, they provide a robust set of management functions that can be leveraged throughout the entire server lifecycle.

 

Faster, More Efficient, More Secure Local and Remote Deployment, Configuration and Updates
Dell Lifecycle Controller simplifies server lifecycle management— from provisioning, deployment, patching and updating to servicing and user customization—for servers located both locally and remotely. It was delivered as part of the Dell Remote Access Controller or iDRAC (Express, Enterprise and vFlash) starting with Dell PowerEdge 11G servers. On 12G servers, the vFlash feature is included with the iDRAC7 Enterprise License, so you no longer have to separately license vFlash starting with Lifecycle Controller 2. Dell’s 12G servers only use Express or Enterprise licensing. Lifecycle Controller includes managed and persistant storage that embeds systems management features and Operating System device drivers directly on the server, thus eliminating the media-based system management tools and utilities traditionally needed for systems management.  

Lifecycle Controller reduces the time and number of steps taken to accomplish tasks, reduces potential for error, enhances server and application uptime and security, and results in more efficient IT management. Developed on the industry standard Unified Extensible Firmware Interface (UEFI) platform and Web Services for Management (WSMan) interfaces, Lifecycle Controller provides an open environment for console integration that also allows for custom scripting for Lifecycle Controller. Leading systems management consoles (e.g., Microsoft® System Center Configuration Manager, BMC Software BladeLogic® Operations Manager, Symantec™ Deployment Solution, Dell™ Management Console) have integrated Dell Lifecycle Controller, thus offering its features and capabilities to existing infrastructures where those consoles are installed.  


Why did Dell develop Lifecycle Controller?
When Dell examined common management tasks and the inefficiencies associated with them, we discovered something interesting – it wasn’t the tools that were making management tasks take so long, it was how they were delivered. The most common activities like provisioning, deploying, and updating required multiple tools, multiple forms of media and scouring the Web for the latest enablement tools, including drivers and firmware. This traditional delivery model resulted in inefficient use of time, a potential for error and potential exposure to security risks.

 

Embedded Management
Lifecycle Controller - Local GUILifecycle Controller - Web Services API

Lifecycle controller supports local 1-to-1 system management tasks via a graphical user interface (GUI) on the servers KVM for operating system install, updates, configuration, and for performing diagnostics, on single, local servers. This eliminates the need for multiple option ROMs for hardware configuration

  

 

 

Remote Services are standards-based interfaces that enable consoles to integrate, for example, bare-metal provisioning and one-to-many OS deployments, for servers locatedremotely. Dell’s Lifecycle Controller takes advantage of the capabilities of both USC and Remote Services to deliver significant advancement and simplification of server deployment.

Lifecycle Controller Serviceability aims at simplifying server reprovision and/or replacing failed parts and thus reduces maintenance downtime

  ( top )


Lifecycle Controller Release Summary

  • Beginning with the first release of iDRAC8 in September 2014, there will no longer be a separate stand alone Lifecycle Controller (LC) firmware. Instead, the LC firmware image will be a part of the iDRAC firmware image, which can be found here.

 

 

( top )

 Highlighted White Papers

Quick Start Guide about Lifecycle Controller (LC) and using LC documentation

Consolidated LC and iDRAC white paper page

 ( top )

 Web Services Integration Tools
Best Practice GuideBest Practice scripts
Web Service Interface Guide for WindowsWinRM scripts
Web Service Interface Guide for LinuxWSMAN scripts

 ( top )

Reference Specifications
ProfilesDescribes the behavior for each 12G feature and necessary classes, properties and methods as well as configurable management attributes that represent the feature.
MOFsFiles that contain the normative description for DCIM classes, properties and method in the MOF format.
WSMAN Licenses and PrivilegesLists all licensing and privilege requirements
LC XML Schema Guide

Contains various schema descriptions including: LCL log, hardware inventory, message registry, attribute registry, and dependency XML

(Associated XSD file location)

WSDLs

iDRAC8 2.00.00.00

iDRAC8 2.10.10.10

The Web Services Description Language is an XML-based language that is used for describing the functionality offered by a Web service. A WSDL description of a web service (also referred to as a WSDL file) provides a machine-readable description of how the service can
be called, what parameters it expects, and what data structures it returns.

 ( top )

 

Attribute Registries (what are these?)

RAID, NIC, iDRAC, BIOS, PCIe SSD, FC HBA

iDRAC8 2.00.00.00

iDRAC8 2.10.10.10

Lists all attributes and properties for these components in XML format
 

(Previous Attribute Registries)

  ( top )

 

Dell Event / Error Message Reference

Dell Test Event Nofification Message Reference

Contains the notification message content generated by the Dell iDRAC8 with Lifecycle Controller using the Test Event Generation feature for the following event action notification types:

  1. Email
  2. SNMP
  3. Remote Syslog

iDRAC8 with LC

Version 2.00.00.00

Dell Event  Message Reference (2.0)

Describes all event and error message content from all DCIM Profiles in one document.

iDRAC8 with LC

Version 2.00.00.00

Dell Message Registry - English (2.0)

iDRAC and Lifecycle Controller event / error message data in XML with Dell XSL for viewing.

iDRAC8 with LC

Version 2.00.00.00

  ( top )

Other References

Additional Scripting Examples

 













Tags: iDRAC White Papers, openmanage, DRAC, LC Videos, Lifecycle Controller, iDRAC, lc

Dell OpenManage Downloads Explained

$
0
0
Revision 95 posted to Systems Management - Wiki by DELL-Amol B on 4/20/2015 10:02:58 AM

This page will help you understand the features of and the various components that make up the Dell OpenManage Systems Management suite. Below, the page also provides quick links to the latest OpenManage downloads from support.dell.com. To learn more about OpenManage products visit the main OpenManage page on Dell TechCenter.

If you need help knowing which OpenManage solution works best for your needs, you can also consult the Dell Systems Management Advisor.

Openmanage Quick Download Links

The following links will help you get the latest versions of the OpenManage Tools.

Dell OpenManage Essentials (OME) - Management Console 

Dell OpenManage Power Center (OMPC) - Power Monitoring Management Console 

Dell OpenManage Server Administrator (OMSA)

The current version of OpenManage is version v8.0.2 & v7.4.1.

Dell Server Update Utility (SUU)

Dell Systems Build and Update Utility (SBUU)

  • Systems Build and Update Utility (S[[ |]]BUU) 2.4

Dell Systems Service and Diagnostics Tools

Dell Repository Manager

OpenManage Product Descriptions

OpenManage Essentials (OME)

OME is a systems management console that provides simple, basic Dell hardware management and is available as a free download. The product officially launched on Feb 28th, 2012 and it will replace Dell IT Assistant (ITA). Click here for OME improvements over ITA 8.9.

For complete information about OME including download links, visit www.DellTechCenter.com/OME

Dell IT Assistant (ITA)

Update 12/02/2011 - ITA is being replaced by OpenManage Essentials. Last release version is ITA 8.9.1

OpenManage Server Administrator Managed Node (OMSA)

OMSA is a software agent that allows for management and administration of local and remote systems. Server Administrator resides on the system being managed and is accessible both locally and remotely from the Server Administrator home page in ITA/OME. If you read OpenManage 101, you know that you will either need to install OMSA on your managed server or have an iDRAC installed in the server for it to be discovered by OME.
 
The Dell OpenManage offline bundle and VIB (Virtual Install Bundle) allows for OMSA to run on a VMware hypervisor. The OpenManage VIB package can be installed / layered on a host or can be injected into an ESXi ISO install image. To know more about OMSA, refer www.delltechcenter.com/omsa.

Dell Systems Build and Update Utility (SBUU)

The Dell Systems Build and Update Utility is a bootable utility that allows for a single server Operating System install, pre-OS firmware updates and pre-OS system configuration. On 11G servers and newer, SBUU is replaced by the Unified Server Configurator (USC), whch is a component of Lifecycle Controller that can be accessed by pressing F10 during post / BIOS boot.

Systems Service and Diagnostics Tools

The Dell Systems Service and DiagnosticTools DVD provides operating system level diagnostics and software components to detect and help resolve hardware issues. It enables user to perform system troubleshooting using Dell Online Diagnostics and provides utilities for installing the latest drivers.

Dell Systems Management Tools and Documentation

A 2 DVD all-in-one set that includes all of the OpenManage tools mentioned above including the following: Dell Systems Build and Update Utility, the IT Assistant console, the OpenManage Server Administrator agent, Systems Service and Diagnostics Tools and Systems Documentation. These two files must be merged / concatenated - directions on how to do this can be found under "Installation Instructions" on the download page.

Dell Repository Manager

Repository Manager is an application that allows IT Admins more easily manage system updates. Repository Manager provides an easy to use, searchable interface used to create custom collections known as bundles and repositories of Dell Update Packages (DUPs).

Dell Management Plug-in for VMware vCenter

The Dell Management Plug-in for VMware vCenter is designed to streamline the management processes in your data center environment by allowing you to use VMware vCenter to manage your entire infrastructure- both physical and virtual. From firmware updates to bare metal deployment, the Dell Management Plug-In for VMware vCenter will expand and enrich your data center management experience with Dell PowerEdge servers. 

For full information, visit www.DellTechCenter.com/DMPVV

Historic OpenManage Download Links

OpenManage 7.0

OpenManage 6.5

Older Versions of OpenManage

  • For historical information on Previous Versions of OpenManage downloads, click on the current version (near the top of this page), then click on the "Previous Versions" link.  For example, here are all of the 

Dell Client Configuration Utility

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Amol B on 4/20/2015 10:11:33 AM

The Dell Client Configuration Utility is no longer being updated. Use DCC or DCM instead.

The Dell™ Client Configuration Utility software provides the ability to configure BIOS settings on Dell OptiPlex™, Latitude™, and Dell Precision™ systems. This version provides significant changes to the Administrator interface and adds some more flexible options for deployment. Many new BIOS settings are made available as well.

Installation

The DCCU 3.1.1230 A00 can be downloaded here. The installation requires that the .NET Framework be installed first. The DCCU will only run under the Microsoft® Internet Explorer browser.

User Interface and Backend

The new user interface is completely modified from previous versions.

  • The application resides in a normal browser window.
  • DCCU can be accessed with a link: http://localhost:1000/
  • A tray applet is now available for quick access to the application.
  • Sections can be collapsed from view for a cleaner look.

Functions and Options

BIOS Update: The BIOS update still functions the same as before but with some new options. The biggest burden here is gathering the various BIOS installers from the Dell support site. This task is outlined in my article on BIOS upgrades. Once those are saved to a convenient location you can import them with the DCCU. There are three new options that improve on the standard BIOS installers:

  • Allow version downgrades – By default the DCCU-created installer will not downgrade the BIOS if a newer version is found. You would generally leave this check box unchecked. In the past it would always upgrade no matter what version it was. This is a really nice additional feature.
  • Collect BIOS settings inventory after update – This option will drop an XML file with the current settings into the directory where it is running. If you have a tool such as Dell Client Manager, it can pick up this file and incorporate the data into the Altiris backend. Other tools such as Microsoft System Center Configuration Manager cannot take advantage of this file.
  • Time-out period before restart– This option allows you to specify the length of time after the update before the system forcibly restarts. There is no end-user notification or interaction during this period.
BIOS Inventory: No substantial changes from the previous version. This simple option creates an executable that you can run on the client. Running the executable creates a results file (TaskResult.xml) in the same directory as the executable that you can import into the DCCU to view the current settings and their various options. The only change now is that the executable file no longer self destructs, and this change allows you to run it multiple times.

BIOS Settings: This option allows you to modify the settings. There have been some substantial additions to the number of settings and an improvement in that you no longer need to import a results file to see what your options are. Additionally, a search box has been added and the settings have been categorized for ease of use in the interface. Another much-improved part of the interface is the pop-up for the boot order. While a reboot is not required for most BIOS settings, it is recommended.

Deploying Packages

The DCCU creates lightweight stand-alone executables that can be used with all major software distribution products. There is some additional functionality available with Altiris products as well that revolve around collecting inventory. Previous versions of the tool would perform a cleanup routine after executing that would remove the tool from the system that was being modified. The DCCU 3.0 version of the executable will now persist, and you can run them multiple times if needed. A major feature of the executables is that there is no end-user interaction, which includes reboots. If a reboot is configured in your package there will not be any warning; you will need to configure your deployment tool to provide any end-user feedback, such as a countdown. For example, in Microsoft SCCM you would instruct the SCCM client to perform the reboot as part of the program object properties. I suggest removing the reboot from any DCCU-created executables and instead allow your enterprise tool to perform the reboots.

Optional Command-Line Parameters

This feature is probably the best new one in DCCU 3.0, as it provides the ability to change properties on the command line. This option allows you to add some rough programmable logic into your deployments. The idea here is to incorporate a general settings executable into a scripted environment. The DCCU help file provides an excellent example of modifying the asset tag for individual systems. The script would perform the task of matching up the unique asset tag, whether that comes from end-user input or a database lookup. The script can then dynamically modify the parameter when it executes the DCCU-created executable. This effort requires an in-depth knowledge of scripting but should be simple enough for most enterprise administrators.

Step by Step

How to Enable Wake on LAN BIOS Settings Using Software Distribution and DCCU

Screenshots

BIOS Upgrade

BIOS Inventory


BIOS Settings

Tags: bios, DCCU, Dell Client Configuration Utility

Updates using USB with Lifecycle Controller

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Amol B on 4/20/2015 10:47:46 AM

The Dell™ Lifecycle Controller embedded technology on Dell PowerEdge™ 11G servers gives administrators and managers the ability to easily update the system from within the system. Pressing F10 during the boot process opens System Services, which includes Platform Updates, and the first option is to connect through File Transfer Protocol (FTP) to ftp.dell.com and download the latest updates. For connections in a secure area, there is a second option to perform the update process through a USB-connected storage device.

View these demos of the Lifecycle Controller to become more familiar with the interface. This page provides information on the process used for USB updates and helps with building a USB update device that can be used inside a secure facility.



USB Updates Using Repository Manager with Lifecycle Controller

The process for using a USB device to update system drivers via Lifecycle controller used to be a more complicated, manual process, but Dell Repository Manager has simplified the steps compared the old process.

The following video outlines the steps involved in exporting Dell Update Packages from within Repository Manager to a USB key and then installing those updates via Dell Lifecycle Controller 1.4. The video assumes that you are already somewhat familiar with Repository Manager and Lifecycle controller. For an introduction to both of those tools, please visit the Lifecycle Controller Demo and Repository Manager Demo pages on Dell TechCenter.

(Please visit the site to view this video)

Basically the process involves using Repository Manager to export a Server Update Utility (SUU) Bundle to the root directory of a USB key. That USB key is then inserted into the server that will be updated. In this case, we used a PowerEdge R710 and we exported the entire Windows System bundle for that system.

Repository Manager SUU


We then boot to the United Server Configurator (USC) interface of Lifecycle Controller by pressing F10 during boot, and select the Platform Update option from the USC interface. We then select the USB drive as the location of the update packages.

Unified Server Configurator Local Drive
At that point, USC displays which drivers are on the USB key and which ones are currently installed. In this demo, we update the Dell OS Drivers Pack and the Broadcom NIC drivers. After the updates are applied, the system reboots and automatically returns to USC.

Unified Server Configurator Apply Updates

After the updates are applied, we can compare the versions of the update packages on the USB stick we created earlier in the process with the currently installed updates on our system. The image below shows that all of the installs have been applied and that our currently installed updates are up to date.

United Server Configurator Apply Updates finished










Depricated Lifecycle Controller USB Update Install Process

The following describes the old method of creating a USB key for updates via LifeCycle Controller.

The Legacy USB Update Process

The update process begins by first looking for the existence of two files in the \catalog directory of the root of the USB key:

  • catalog.xml.gz
  • catalog.xml.gz.sign

If they don't exist, or have been changed in any way, the update process will exit with an error.

After the files have passed verification, the catalog.xml.gz is decompressed and the catalog is parsed. Then a screen shows the current version of existing updates and any applicable newer versions. It will automatically select updates that are newer and provide the choice of deselecting to apply an update at a later time. The update packages will then be installed from their respective locations off the root of the USB key.

Creating the USB Key via the Legacy Process

At first glance one might think, "Hmmm, easy enough; I'll just replicate what I need from ftp.dell.com to the USB key." The problem is that the files are not separated by machine types. Drill down through the \BIOS folder alone and there are more than 5,000 files and more than 8 GB of data. Trying to replicate the entire ftp.dell.com site would require replicating more than 40 GB of data, which isn't the best use of Internet bandwidth to go that route.

Luckily, it is possible to reuse a recommended tool, Content Manager, which provides the ability to create a custom repository. Using this feature helps replicate the updates specific to the servers in a data center environment. Copying the files to the USB key and copying the catalog.xml.gz and catalog.xml.gz.sign files creates a working USB key.

Here are step-by-step instructions:

1.Install Content Manager from the Systems Management Tools and Documentation DVD. The current version as of this writing is 6.0.1.
2.Run Content Manager and select Create Custom Server Update Utility.


Updates using USB with Lifecycle Controller - The Dell TechCenter

3.Select a destination—in this example, C:\USB_Updates.


Updates using USB with Lifecycle Controller - The Dell TechCenter

4.Use the Shift or Ctrl key to select the servers to update.
Important: Make sure to select the Linux packages.


Updates using USB with Lifecycle Controller - The Dell TechCenter

5.Wait for the files to download.


Updates using USB with Lifecycle Controller - The Dell TechCenter

6.Locate the files just downloaded. They will be in \CustomRepository\repository under the directory just created. In the example shown here they are located in C:\USB_Updates\CustomRepository\repository.


Updates using USB with Lifecycle Controller - The Dell TechCenter

7.Copy all these directories and files to the root of the USB key, with the exception of the Catalog.xml file—this is not the correct file for the Lifecycle Controller.
8.Create a catalog directory off the root of the USB key.
9.Download catalog.xml.gz and catalog.xml.gz.sign from ftp.dell.com, and copy these files to the \catalog directory on the USB key.


After creating a custom USB key for updates with the Lifecycle Controller, the contents should look similar to the following:

Updates using USB with Lifecycle Controller - The Dell TechCenter

10.Reboot the server, select F10 for System Services, select Platform Updates...USB Device, and then select the updates to apply.

.
Updates using USB with Lifecycle Controller - The Dell TechCenter

Updates using USB with Lifecycle Controller - The Dell TechCenter

Tags: maser, dups, Lifecycle Controller, Systems Management

Lifecycle Controller 2

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Amol B on 4/20/2015 10:48:50 AM

 

iDRAC7 with LifeCycle Controller Technology

Quick Links: 

Executive SummaryLooking for 13G Content?
LC 2 - iDRAC7 Firmware MatrixLC2 and iDRAC Video Demos
Lifecycle Controller BlogsCMC for M1000e & VRTX Home
ManualsLifecycle Controller Home
LC2 Reference SpecsLifecycle Controller 1 (LC1) Home
LC2 Dell Event Message Reference

  


Executive Summary

With the launch of the Dell PowerEdge 12th generation servers on Feb 27th, 2012, Dell has enhanced our embedded management without the need to install a software based agent within the host operating system. At the heart of the 12th generation servers embedded management is the iDRAC7 with Lifecycle Controller technology, which allows users to perform useful tasks such as configure BIOS and hardware settings, deploy operating systems, update drivers, change RAID settings, and save hardware profiles. Together, they provide a robust set of management functions that can be leveraged throughout the entire server lifecycle. For information on the latest version of Lifecycle Controller on Dell’s 13th generation PowerEdge servers, click here.

   ( top )


LC 2 Release Summary

LC2 1.4.2

  • Support for R920
  • New OS support
  • Support for Emulex NICs
  • Support for Samsung SSD

13 May 2014

(Download)

LC2

1.4.0

  • Support for new servers
  • Support for Samsung SSD 
  • Support for Emulex NICs

11 Mar 2014

LC2 1.3.0

  • Performance Improvements
  • Feature Enhancements

 2 Dec 2013

LC2 1.1.5
  • Performance Improvements
  • Test Event simulation methods added
  • Feature Enhancements

06/11/2013

LC2 1.1.1
  • Performance Improvements
  • Feature Enhancements

2/1/2013

LC2 1.1.0
  • Configuration XML feature added
  • Additional hardware support

12/5/2012

LC2 1.0.8
  • Feature Enhancements
  • Performance Enhancements

 9/2012

LC2 1.0.6
  • Feature Enhancements
  • Performance Enhancements

06/2012

LC2 1.0.0
  • First LC2 release

3/2012

 

 

LC2 - iDRAC7 FW Matrix
LC 2 VersioniDRAC7 Monolithic FW VersioniDRAC7 Blade FW Version
1.4.01.56.55 (Download)
1.3.01.56.55 (Download)
1.1.51.40.40 (Download)
1.1.11.37.35 (Download)
1.1.01.31.30 (Download)
1.0.81.23.23 (Download)
1.0.61.10.10 (Download)
1.0.01.00.00 (Download)

 ( top )

iDRAC7 / LC2 Reference Specifications
12G WSMAN API Changes Describes the configurable management attributes and methods that have been added, deleted or changed in behavior per platform component.
WSMAN Licenses and PrivilegesLists all licensing and privilege requirements
LC XML Schema GuideContains various schema descriptions including: LCL log, hardware inventory, message registry, attribute registry, and dependency XML
WSDLs

The Web Services Description Language is an XML-based language that is used for describing the functionality offered by a Web service. A WSDL description of a web service (also referred to as a WSDL file) provides a machine-readable description of how the service can
be called, what parameters it expects, and what data structures it returns.

MOF-HTML

The HTML version of the Lifecycle Controller 2 MOF files. It contains DMTF and DCIM classes in HTML format for easier search and browsing.

iDRAC7 / LC2 Attribute Registries (what are these?)

RAID 

(4/2014)

Lists all attributes and properties for the RAID component in XML format

NIC

(4/2014)

Lists all attributes and properties for the NIC component in XML format

iDRAC

(4/2014)

Lists all attributes and properties for the iDRAC component in XML format

BIOS

(4/2014)

Lists all attributes and properties for the BIOS component in XML format

PCIe SSD

(4/2014) 

Lists all attributes and properties for the PCIe SSD component in XML format

FC HBA 

(4/2014)

Lists all attributes and properties for the FC HBA component in XML format
 

(Previous Attribute Registries)

  ( top )

   

Dell Event / Error Message Reference
Dell Event Message Reference (3.0)

Describes all event and error message content from all DCIM Profiles, iDRAC, Lifecycle Controller, and OpenManage products in one document. (link to all OpenManage 7.3 docs)

 OpenManage 7.3, iDRAC7,

LC2 Version 1.1

Dell Event Message Reference (2.0)

Describes all event and error message content from all DCIM Profiles, iDRAC, Lifecycle Controller, and OpenManage products in one document.

OpenManage 7.2, iDRAC7,

LC2 Version 1.1

Dell Event  Message Reference (1.0)

Describes all event and error message content from all DCIM Profiles in one document.

OpenManage 7.0, iDRAC7,

LC2 Version 1.0

Dell Test Event Notification Message Reference

Contains the notification message content generated by the Dell iDRAC7 with Lifecycle Controller using the Test Event Generation feature for the following event action notification types:

  1. Email
  2. SNMP
  3. Remote Syslog

iDRAC7,

LC2 Version 1.1

Dell Message Registry - English (2.1)

iDRAC and Lifecycle Controller event / error message data in XML with Dell XSL for viewing.

iDRAC7,

LC2 Version 1.1

Dell Message Registry - English (2.0)

iDRAC and Lifecycle Controller event / error message data in XML with Dell XSL for viewing.

iDRAC7,

LC2 Version 1.0

CMC for VRTX

$
0
0
Revision 43 posted to Systems Management - Wiki by DELL-Amol B on 4/20/2015 11:14:40 AM

Quick Links:

What is CMC for VRTX?Blades Wiki
What's New?iDRAC8 Home
VRTX ManualsLifecycle Controller Home
VRTX Video DemosCMC Home 
VRTX White PapersM1000e Home
VRTX Useful Links
VRTX Hardware

What is CMC for VRTX?

The newly announced Dell PowerEdge VRTX is a revolutionary, easy-to-manage, remote and office-optimized platform that converges servers, storage and networking into a compact package. It can hold up to 4 server nodes, up to 48TB of integrated, shared storage, and network switching.

Unique VRTX Features

More than simply a small blade server, the Dell PowerEdge VRTX offers something that no other blade server solution has: the ability to use PCIe slots. By combining the density of blade servers with the flexibility of rack server I/O options with PowerEdge VRTX, Dell gives you the flexibility to use less expensive PCIe cards while still being managed through shared chassis management. Another exciting new feature is VRTX's shared storage and on-board RAID controller. Pulling this all together into one, easy-to-manage platform is where VRTX shines.

CMC's role

Part of each VRTX platform, CMC is a dedicated, hot-pluggable module (a second, redundant unit is optional) within the platform that provides a secure web/browser-based interface that is used to take inventory, perform configuration and monitoring tasks, remotely power on/off blades and enable alerts for events on servers and components in the blade chassis. CMC integrates with each of the VRTX server nodes’ embedded iDRAC module, so users can perform iDRAC functions such as opening a remote console session from the CMC interface. Chief among those configuration tasks is setting up shared storage, creating virtual disks and managing PCI slot assignments. Like iDRAC7, CMC for VRTX is licensed in two different varieties: Express and Enterprise. More details on the difference between what comes with each license for both CMC and iDRAC7 for VRTX is available here.

What's New

VRTX Release Summary
VRTX 1.30
  • Ivy Bridge support for M820 
  • Fault Tolerant (Redundant) PERCs 
  • Support for Windows Server 2012 R2  
  • Support for NVIDIA K2 GPGPU  
  • Broadcom 10GbE quad port NIC 
  • Emulex SeaHawk (FH) PCIe Adapter 
  • Emulex 10G NDC 

 3/17/2014 (Download)

VRTX 1.25

  • Ivy bridge support for M520 and M620
  • Support for fiber channel PCIe card
  • Quick deploy of Profiles to slots

2/07/2014 (Download)

VRTX 1.0
  • Ability to assign/use Shared PCIe slots
  • Can hold up to 4 server nodes

  • Supports 12 x 3.5"or 25 x 2.5" shared hot-swap drives 

  • Integrated shared RAID controller (SPERC)

6/28/2013
(Download)

( top )

VRTX Manuals (home)& Docs 
User GuideCMC for PowerEdge VRTX [1.0]
RACADM ReferenceRACADM Command Line Reference Guide [1.0]
Event Message ReferenceDescribes all messages, message IDs, and message arguments from all profiles in one document [ 1.0 ]
WSMAN ProfilesDescribes the behavior for each 12G feature and necessary classes, properties and methods as well as configurable management attributes that represent the feature. Also see Managed Object Files (MOFs).
Fault ToleranceUpgrading PowerEdge VRTX to support Fault Tolerant Shared PERC 8 [NEW]

 

( top )

VRTX Videos & Demos
Upgrade PowerEdge VRTX to Dual Controller Configuration[NEW]
How to replace the VRTX blade partition [NEW]
CMC for VRTX Overview
PowerEdge VRTX Shared Storage Deployment
PowerEdge VRTX PCIe Deployment
PowerEdge VRTX Front Panel / LCD Orientation
PowerEdge VRTX CMC License Management: Delete Enterprise License
PowerEdge VRTX CMC License Management: Replace Enterprise License 
PowerEdge VRTX CMC License Management: Import Enterprise License
PowerEdge VRTX CMC License Management: Export Enterprise License 

( top )

VRTX White Papers
VRTX RAID Cloning
Updating M1000e Servers and Using in Chassis Management Controller (CMC) VRTX
Chassis
Using VRTX KVM and DVD
PowerEdge VRTX Alert Management
PowerEdge VRTX CMC Feature Guide
PowerEdge VRTX Diagnostics
PowerEdge VRTX Firmware Updates and Dell Repository Manager

 

VRTX Useful Links
A look at the Dell PowerEdge VRTX
Dell Enterprise Demo Tools
VRTX Platform Page

 

( top )

Hardware

 

Supported PCIe
Cards (low profile and full
height)
AMD FirePro W70006Gb/s SAS HBA
Broadcom Dual Port 1Gb6Gb/s SAS HBA
Intel Dual Port 1GbIntel Dual Port 10Gb Base-T
Intel Dual Port 10Gb Base-SFP+Broadcom Quad Port 1Gb
Intel Quad Port 1GbBroadcom Dual Port 10Gb Base-SFP+

( top )

Supported Hard
Drives
500GB 7.2k NLSAS 2.5” HDD1TB 7.2k NLSAS 2.5” HDD
600GB 10k SAS 2.5”900GB 10k SAS 2.5”
1.2TB 10k NLSAS 2.5” HDD146GB 15k SAS 2.5”
300GB 15k SAS 2.5”1TB 7.2k NLSAS 3.5”
2TB 7.2k NLSAS 3.5”3TB 7.2k NLSAS 3.5”
300GB 15k SAS 3.5”450GB 15k SAS 3.5”
600GB 15k SAS 3.5”200GB SAS SSD 2.5”
400GB SAS SSD 2.5”4TB 7.2k NLSAS 3.5”

  ( top )

Tags: Updated Server Module, VRTX, openmanage, chassis management controller, CMC, m1000e

Systems Edge

$
0
0
Current Revision posted to Systems Management - Wiki by DELL-Amol B on 4/20/2015 12:43:57 PM
SystemsEdge was a blog that ran from October 2007 - September 2008. It is now known as the Dell TechCenter blog, which resides on the Dell Community site.

On the Power"Edge" of Systems Management
RSS Feed

Start Blog Entry

Blade Config Is Easy
11/3/2008 - Comments

I spent part of today getting a new Dell PowerEdge M1000e blade chassis up and running. We've been limping along on a beta chassis for a while and finally found some time to move to the new one.

Sometimes I forget how easy we make things. I used to work at IBM and did many things around that blade solution. When I brought a new IBM blade chassis up I had to run a crossover cable from my laptop to the management module of the blade, and it would boot up with a default IP address. So then I had to configure the laptop to be on the same subnet and then reconfigure the management module to be on the "real" network. Quite a pain.

On the Dell Blade chassis, I get access to the Chassis Management Controller (CMC) right through the KVM. When you hit PRNT SCRN to change blades the CMC shows up as an option. It's just like you were telnet'd or ssh'd into the CMC. I can configure the IP right from the keyboard. Soooo much easier.

Here's a picture of the CMC in the KVM interface and the single command I had to run to configure the CMC IP address.

11-3-08 - Blade Config is Easy - Comments - The Dell TechCenter

Scott - Comments
End Blog Entry
Start Blog Entry

SCVMM 2008 RTM
10/30/2008 - Comments

Microsoft's System Center Virtual Machine Manager (SCVMM) 2008 was released to manufacturing last week. Todd downloaded it and will have some findings on the new version posted on his blog soon.

I've been working with one of our folks in PG to help put out some more demos on SCVMM 2008. They should be up and available in the next few weeks. We did some demos with the beta version that you can see here.

I was pleased with the ease of use in the beta version. I'm hoping to see much more stability in the RTM version. I'll let you know once I have the new blade chassis up and running with the new PowerEdge M905 blades, which will also be used for some Dell Management Console (DMC) testing as I've gotten my hands on the latest code drop for that beta.


Scott - Comments
End Blog Entry
Start Blog Entry

OM 5.5
10/22/2008 - Comments

OpenManage 5.5 is available for download from the support site. Here's a link that will take you to the downloads for the Dell PowerEdge 2950. This page will help if you are new to OpenManage and need help in figuring out what to download.

If you need the full-blown Systems Management Tools and Documentation DVD, here’s a quick tip: you can use any Dell Service Tag for the download—it doesn't have to be a Server System. I use my laptop service tag. :-)


Scott - Comments
End Blog Entry
Start Blog Entry

DMC Reporting
10/15/2008 - Comments

Still creating more content and demos over at the Dell Management Console (DMC) beta site. We’re trying out some of the reporting functionality. Here's a screenshot of one of the reports showing the Dell PowerEdge Server model types.

If you're interested in joining the beta site, let me know.

10-15-08 - DMC Reporting - Comments - The Dell TechCenter

Scott - Comments
End Blog Entry
Start Blog Entry

DMC Inventory Screenshots
10/10/2008 - Comments

The Dell Management Console (DMC) is actively collecting inventory information on our lab machines. Thought I'd take a minute to show you a screenshot of the Inventory Summary screen.

The icons are really nice looking.

10-08-08 - DMC Inventory Screenshots - Comments - The Dell TechCenter

Scott - Comments
End Blog Entry
Start Blog Entry

Testing DMC Beta
10/3/2008 - Comments

Getting around to playing with the new Dell Management Console (DMC), which is still in beta—can't say too much about when it will release. We are just finishing up the beta site that will have some demos and docs—and then code later to download.

One thing that was cool to see is a link to the Dell TechCenter OpenManage homepage from within the product! Kudos to all our followers and members out there that are making this a great destination site. If you didn't make it and find it valuable, I don't think we would have made it into the product. Pretty neat. I'll try to sneak as many screenshots out as I can, until they find us and tell me to stop. Heck, I probably won't even stop then...sometimes you just want to buck the system. :-)

DMC

So if you happen to be one of the three people that read my blog, send me a note and I'll sneak you into the back door of the DMC beta site when it goes live.

Scott - Comments
End Blog Entry
Start Blog Entry

My Thoughts on the vCloud
09/26/2008 - Comments

At the VMworld 2008 keynote there was an emphasis on vEverything, and in particular the vCloud. At the high level, the idea is a great one: be able to seamlessly move workloads in and out of the cloud, no matter where the resources exist in the cloud—my data center, your data center, their data center.

In my previous life I was lucky enough to work on the team at IBM that was engaged in the beginning of the TeraGrid project—a great project with a goal of uniting several academic HPC Cluster sites across the U.S., so they could share the computational resources.

We thought the biggest challenges would be of a technical nature, but it turned out the political and trust challenges far outweighed the technical challenges.

How can I trust my data is secure at your site? Who will have access to the data? I need admin rights on your site. How do we charge back for your hogging all the bandwidth with your project?

I would encourage Paul Maritz to meet with the leaders of TeraGrid and discuss those challenges and how they deal with those issues. It's the natural order of the world for us to learn from academia.

Scott - Comments
End Blog Entry
Start Blog Entry

VMworld 2008 Highlights
09/24/2008 - Comments

I had a great time out at VMworld 2008. Met up with some old friends and met many new ones this year—thanks to all the twittering.

I just uploaded all the photos from my phone and added them to Todd's album that he created for VMworld. If you look closely, you'll see several screen shots of the new vCenter product and some interesting ones on the layout of ESXi on the flash storage device.

The demo of the vAppSpeed was one of the coolest things I saw at the show.

Todd and I will discuss this demo and more in next week's chat session.

Scott - Comments
End Blog Entry
Start Blog Entry

VMworld Coverage
09/12/2008 - Comments

Todd and I will be covering the VMworld show next week. I've been spending much time over at our Virtual Exhibitor Booth on the VMworld.com site; that's why you haven't seen many updates from me over here lately. Funny how you talk about "spending time" at a virtual site, but that's really what it is when you get down to it -- where do you "hang out" on the web?

Same thing we've always done as human beings, just new media and different platform these days. They have even set up a virtual bar over at the VMworld.com Virtual Pavilion. Already had a few bar fights :-) ... and no I didn't start it!

So all next week, plan on following Todd and me on Twitter and at the virtual booth. That's where you'll find us hanging out -- well, maybe the Palms Hardwood Suite as well :-)

Roger will be pulling back some of the more interesting tweets and content. Ping us on Twitter, here, or email if you want some particular pics or information from the show.

Scott - Comments
End Blog Entry
Start Blog Entry

DUPs Script for ESX
09/05/2008 - Comments

I wrote a script a few months back to automate the deployment of Dell Update Packages, DUPs on ESX servers.

Got a message today that it might be broken with the new version of SUU.
Testing now. Will update here if it can be fixed, or if it is beyond repair.

** Update ** - Is working on my test server with ESX 3.5 and SUU 5.4.1 , anyone else experiencing problems ?

Scott - Comments
End Blog Entry
Start Blog Entry


ITA Mess
08/22/2008 - Comments

Shelley from the EBC, is always telling our customers, "It's great to have the tools, but if you don't have the people and processes in place, the tools will do you no good." .. very true

Being a lab, and one that reacts to test anything and everything from random tweets, I'd say our processes are pretty much shot, as evidenced from this ITA screen shot from my server :

ITA Mess

Looks like I'll be taking some time to apply some patches and updates ! Can anyone top this ?

Scott - Comments
End Blog Entry
Start Blog Entry

The Next Thing to Come in Dell Systems Management
08/04/2008 - Comments

I'm not so good at keeping secrets. Apparently neither are some others, or this guy either, or this one. As part of the activites around this new product, we need some volunteers to take a peek at the new product and provide some feedback. You might even be able to test it out on your own systems, depending on your enthusiasm and ability to PayPal me enough cash :-)

We're in the beginning stages of setting up a private site for the beta. Let me know if you'd like to join, and I'll forward details on getting you hooked in.

UPDATE - to request access for the beta - send a private message to this ID

Scott - Comments
End Blog EntryStart Blog Entry

SCVMM 08 Demo
07/28/2008 - Comments

Just finished a demo on using Microsoft's System Center Virtual Machine Manager 2008 to initiate a VMware VMotion on ESX hosts. If you were following us on Twitter, you would already know that :-)

Scott - Comments
End Blog Entry
Start Blog Entry

We're Tweeting
07/22/2008 - Comments

In order to be as cool as you, we're now using Twitter at work. So if you want to know where we're headed for lunch, or what's going on in the lab, or what we're seeing at some of the geek conferences, come follow us !

DellTechCenter Twitter

Scott - Comments
End Blog Entry
Start Blog Entry

SCVMM 2008 and Hyper-V
07/18/2008 - Comments

We are gearing up for our Hyper-V management topic next week. Todd installed SCVMM 2008 on a system in the lab and handed my the keys. First thing I did was to add our VMware Virtual Center Server into SCVMM's console. That was very easy to do. I've posted some screenshots on this page.

Then I noticed when right clicking on a VM it had the "Migrate Virtual Machine" option ... you guessed it ! .. it performed a Vmotion through SCVMM. Pretty cool. But of course, there was no magic to Vmotion from the ESX host to the Hyper-V host :-(

I'm going to slap together a quick demo to show you what it looks like. Keep an eye out for it.

Scott - Comments
End Blog Entry
Start Blog Entry

Blade FlexAddress Demo
07/17/2008 - Comments

If you just see a big blank section on the screen, you are behind the Dell firewall. Go watch it at home :-) .. or download it from here.



Scott - Comments
End Blog Entry
Start Blog Entry

Blades and vfd
07/09/2008 - Comments

So yesterday I needed to update the bootcode on our Qlogic mezzanine cards on the blades in the lab. I downloaded the file, your standard zip file with some files and a readme. Instructions seem simple enough, "boot to DOS, Run update.bat" .....I don't know about you, but then I see something that simple, my mind starts racing. Where am I going to find a floppy ? .... where's my DOS boot disk ? ... will these files even fit on the floppy after I make it bootable ?

So no I can't find a floppy, I don't have a DOS boot disk, and of course these files are too big to fit ! ... I'm not even in the lab, I was working from my desk. I don't want to drive over there, I'm trying to save the environment ... well actually I'm just really lazy most days :-)

There's a handy little tool in my toolbox called "virtual floppy drive" .. aka vfd. I wasn't sure if the virtual media of the Blade iDRAC would see it, but it was worth a try. Loaded it up, formatted with the "Create MS-DOS startup disk", then attached to the Blade via virtual media, and it booted ! Then I simply changed virtual disks in vfd to an image with the Qlogic bootcode and ran update.bat. Worked like a charm.



Scott - Comments
End Blog Entry
Start Blog Entry

Follow the Yellow Brick Road ...
07/01/2008 - Comments

Our manager (somebody bug her about a profile pic !) was traveling the world couple weeks back and evangalising the TechCenter. She was explaining how she was "showing" the site to people, and I thought, "quick 10 minute demo of the site would be right".

It's easy enough for us to say, "we got that on the TechCenter", but the response is usually, "Where ?" Search is good, we're tagging with keywords, but people want to know where stuff is "happening" on the site. So I did a quick demo that is posted on the home page at the bottom right. It's YouTube - so if you're inside Dell - tuff luck -- until the Windows Media file gets linked in a few days. If you are new to our site, check it out, should help you follow our thought process as we put new content on the site.

And no, it's not a how-to-use-the-web demo, although my mom still needs help with that ! -- How frustrating is it to watch her single click when she should double-click and vice-versa? You know what I'm talking about :-)

Scott - Comments
End Blog Entry
Start Blog Entry

New Blade Demos
06/18/2008 - Comments

I wish we could send out a new Dell PowerEdge M1000E Blade chassis to everyone ! ... but I guess the next best thing are demos of the Chassis Management Controller and iDRAC in action. I know .. the YouTube versions embedded in the page are grainy, that's why there is a link to download the WMV file, which is better..

I've received requests to see more features. I'll keep plugging away and you tell me what else you'd like to see.

Scott - Comments
End Blog Entry
Start Blog Entry

TechCenter Shirt ? Anyone ?
06/10/2008 - Comments

tvieson is looking for some help. First person to provide a WORKING solution, gets a TechCenter shirt. You can see it proudly modeled here by myself and Roger ( I don't think Todd is wearing any clothes under that Wookiee costume ! ).

If you're a writer on the community, simply add your code to the page. If your a regular member, you can simply respond to the thread. You will then have proven yourself worthy and be elevated to writer status ! A shirt and more power, can't ask for much more.

Scott - Comments
End Blog Entry
Start Blog Entry

Blade Systems Management
06/06/2008 - Comments

Beginning next week our focus area for the TechCenter is around Blade Systems Management. I'll keep that link updated with the information that is most relevant to architecting and using a systems managment strategy in a Dell PowerEdge Blade environment. We've got several guest speakers in the wings ready to talk about some exciting new enhancements to the Dell PowerEdge M1000e Blade chassis that are quickly nearing release.

Join us in the weekly chats and if you can't make the chats, be sure to review the transcripts. If you have anything you want queued up for discussion, drop me a comment.

Scott - Comments
End Blog Entry
Start Blog Entry

The community works !
06/03/2008 - Comments

I tested my script for installing OMSA on VMware ESX several times on multiple machines, so when I see a thread titled - "I don't think this script is going to work very well" - I tend to say, "Arrrggghhh, what did I copy and paste wrong ?!"

Happily, stoggy, had pointed out a better way to perform the snmpd.conf changes that was much more elegant than my hack. My linux skills are slowly fading, and I hate to RTFM .... I like it better when the community works and we all gain in the knowledge.

Thanks !

Scott - Comments
End Blog Entry
Start Blog Entry

Ooooooooommmm ....
05/28/2008 - Comments

No this is not your relaxation chant for Friday afternoon, but I want to clue you in on what seems to be a little secret when you install the OMSA agent on a server. There was a thread on the TechCenter this week about thermal monitoring. Of course, I read too much into the question like I always do, and answered the wrong question at first , won't be the first or last time I do that :-)

The question boiled down to, "How can I read the temp probes of my server and write them to a file for trend analysis ?"

When you install OMSA it also installs a command line utility called "omreport". Open a CMD window and type "omreport -?" , from there you can walk the tree, or get this ... there is documentation ! I'm leaving the script writing part as an exercise for the reader. If you're in linux, it's easy enough to grep out what you need, slap to the end of a file and repeat. In the Windows world, it takes a bit more work. If one of you comes up with an elegant solution, post it on the OpenManage Scripts and Tools section, and I'll send you kudos, a badge, and a shirt !

And here's another little secret I'll let you in on, I didn't find out about the omreport CLI until I had worked with OMSA for three months !

Scott - Comments
End Blog Entry
Start Blog Entry

OpenManage Suggestions for Improvements
05/28/2008 - Comments

Thanks for all the cards and letters coming in on suggested improvements for OpenManage !

You haven't seen any responses on the threads yet, but that doesn't mean their isn't a flurry of activity going on behind the scenes. You can also "Vote" for any of the suggestions by clicking the yes/no boxes on the "Do you find this valuable ?" option. I'll keep poking people on this side, and you keep the suggestions coming.

Thanks !

Scott - Comments
End Blog Entry
Start Blog Entry

OMSA on ESX can be Scriptalicious
05/19/2008 - Comments

We've already got some great documentation from the Dell Virtualization Engineering team on how to install Dell OpenManage on VMware ESX. Definitely the first place to start.

Shelley, who talks to customers in the Executive Briefing Center daily, came by and mentioned that it would be great if we could package up the steps in the documentation. Write a script so customers could reuse it easily in their deployment processes and eliminate typo problems. DING DING DING, Thud (that's the sound of my head banging against the wall), of course that's what we should do !

For your viewing pleasure, I give you the Scriptalicious method for deploying OMSA on VMware ESX. Look through the code, about mid-way through you'll see me begging for help :-) ... of course I know all you admins just want to use what works and to heck with writing elegant code :-)

Scott - Comments
End Blog Entry
Start Blog Entry

Can I interest you in a tooth pulling ?
05/13/2008 - Comments

Quick raise your hand if you love to patch your servers ! .... anyone, anyone, Bueller, Bueller ? ... yeah, I didn't think so. It's something we have to do as admins. If you come from the HP or IBM management domain, I'm sure you've developed a methodology using their tools to bring some fun to this chore.

I've created a page on Patching Dell Servers. It will help you with the Dell terminology and the tools that we've developed to assist you in patch management of servers. If you have some tips and tricks in this arena, please feel free to add to the conversation. We've also got a place where you can show off any scripts or tricks you've developed.

Scott - Comments
End Blog Entry
Start Blog Entry

Starting Smart with Dell OpenManage
05/9/2008 - Comments

Yes, you should start smart with Dell OpenManage :-)

Scott - Comments
End Blog Entry
Start Blog Entry

Icons in ITA
05/7/2008 - Comments

Back in January I blogged about trying to figure out what the icons in the ITA interface meant. A few others on the Dell Community Forums had the same thoughts. I had the grand idea that we would all update a page and contribute our meanings to the icons. That quickly fell to the bottom of my list of things to do.

As I was looking through the DCF OpenManage section, I happened across this entry. Awesome, now it's as simple as reading the docs to interpret the icons.

I will hence forth call this the OpenManage Icon Interpreter.

Thanks documentation team !

Scott - Comments
End Blog Entry
Start Blog Entry

Dell OpenManage Suggestions for Improvements
05/6/2008 - Comments

Of course we want to hear from you ! We've already gotten some great email input and I should of thought of creating a page earlier, but that credit goes to Stuart that started a thread on the topic.

I created a page for Dell OpenManage Suggestions for Improvements. Now it is up to you to create the threads with the ideas. I'll point the Product Managers, Developers, and Development Managers in that direction. Many of them already lurk here, so don't be suprised if they respond directly to your thread.

Scott - Comments
End Blog Entry
Start Blog Entry

The Effect of Removing Server Power Supplies
05/1/2008 - Comments

We had a great chat session a few weeks back that took us down a strange path. A customer on the chat informed us that they remove one of the redundant power supplies from their servers in order to reduce power consumption. His original question was how to remove the Red-X from the ITA console so they would stop getting error messages.

Then the discussion turned into a, "how much can you save by doing this ?" discussion. Since both Todd an I were in the lab at the time, and we had the server in question and power monitoring equipment, we decided to do a quick gut check of the difference in power consumption. This first very "unscientific" test consisted of Todd yelling out numbers from behind the rack and me typing stuff in the chat box.

The discussion came up again with Fred. Fred talks to customers at the Briefing Center on a daily basis. Fred told me that he's had other customers who are doing the same thing.

That discussion prompted me to spend some more time in the lab and do a more thorough investigation of the differences. The results are about what we expected. Older servers have more inefficient power supplies, so they see a greater difference than newer servers with more efficient supplies. Also, as the workload increases, the percentage difference decreases because the inefficiences represent a larger portion of the measurement at idle workloads.

Can someone tell me where this trend started ?

Scott - Comments
End Blog Entry
Start Blog Entry

Monitoring HP Servers in Dell ITA
04/30/2008 - Comments

My thanks to Philip for kicking off the conversation and asking how we can use Dell IT Assistant to manage HP systems.

There are two Dell PowerSolutions articles that explain how this can be accomplished. I'm currently in the process of adding our HP DL385 system to my ITA Console. I'll be using these articles as reference and documenting the process along the way.

If you've done this before, please feel free to give me your two cents on the topic.

Scott - Comments
End Blog Entry
Start Blog Entry

Switching to Dell OpenManage
04/28/2008 - Comments

For the next three weeks, I'll be focusing on helping you switch from HP's systems management platform to the Dell OpenManage platform.

Now of course it would be mighty arrogant of me to think that we've replaced all your HP gear with Dell gear. So I'd like to hear from those of you that have a mixed environment. How are you handling management of the servers ? Have you setup separate management servers for each vendor type ? What resources have you found helpful in making the switch, or integrating the gear ?

I've create a landing page that you can bookmark to keep engaged in the conversation. Currently it has some resources to help point you in the right direction if you are new to Dell OpenManage.

Looking forward to your input.

Scott - Comments
End Blog Entry
Start Blog Entry

Welcome Dell IT !
04/25/2008 - Comments

Seems that Dell IT has found us. Luckily instead of wanting to shut us down, they want to contribute :-)

I truly believe that one of the best things about our TechCenter community is that you have access to all kinds of resources "on the inside". Where else in such a big company are you able to talk to the people that write the code, author the documents, and design the solutions ?

So thank you Dell IT for coming to our community and sharing your best practices. Dennis has already authored a great article on doing mass bios updates with Microsoft's System Center Configuration Manager.

Greg is also lurking around here, he's a Microsoft MVP, and frequent contributor on myitforum.com

There's also Donnie, Angie and some others lurking around here. Keep an eye out for a new section on Microsoft System Center and I'm sure you'll find the rest of them hanging out.

Hey, can I get some more disk space for my Exchange mailbox now ? :-)

Scott - Comments
End Blog Entry
Start Blog Entry

Applying updates to older PowerEdge Servers
04/21/2008 - Comments

I was checking out the Dell Community Forums this morning, and following up on one of the threads I answered. Towards the end of the thread, it was pointed out that some of the older Dell PowerEdge servers don't have DVD drives, and the SUU image is larger than can fit on a CD image.

Luckily we have many tools in the toolbox to work our way around problems. You can use Content Manager from the SUU image to create a custom repository. The custom repository will include the SUU GUI and CLI tools to apply the patches, and you'll only have those updates that you selected, not the entire repository.

If you haven't had a chance to use Content Manager, I've got a demo you can check out.

Scott - Comments
End Blog Entry
Start Blog Entry

Script for applying Dell Server Updates in ESX 3.x
04/10/2008 - Comments

Doing the daily blog search and came across this entry on the Lone Sysadmin blog, talking about SUU 5.4 working with ESX 3.5. Turns out there's a little confusion as to what works from the SUU DVD on ESX. The DUPs (Dell Update Packages) install, but if you try to install them through the SUU CLI (./suu -u) it will error out.

The ./suu -c command however, does work. So doing a little scripting and with a little help on regular expressions from an old friend, I was able to write a script that will use SUU to do the comparison, and then apply the .BIN files.

Use at your own risk, and modify to your hearts content. If you have other scripts you've found useful in the OpenManage world, please feel free to contribute.

Scott - Comments
End Blog Entry
Start Blog Entry

Secret Decoder Ring
04/03/2008 - Comments

You ever find yourself trying to explain something and no matter what you say, it's just not coming across ? When that happens to me I try to find a frame of reference that is familiar to that person. Take Systems Management, for example. You can define terms, show some examples, talk about OpenManage, ITA, SBUU, ContentManager, but it usually never clicks until they can relate it to something they are already familiar with.

In the systems management space, you are usually talking to a someone that is familiar with the HP or IBM offerings.

So now I give you, totally free of charge, the Systems Management Secret Decoder Ring.

Systems Edge - The Dell TechCenter

Use it wisely and now you too can compress a 30 minute conversation to 2 minutes.

Scott - Comments
End Blog EntryStart Blog Entry

MD3000i - Blinky Blinky
03/28/2008 - Comments

One of our PowerVault MD3000i's in the lab has been blinking at me for the last few weeks. I could stand it no longer and it moved to the top of my list of things to do.

The MD Storage Array Manager is easy enough to use and told me, "some I/O was lost for extended period, we collected diagnostic data". It further explained that all I needed to do was reset the diagnostic data bit with a simple command and the light would go off, "reset storageArray diagnosticData;"

Hmmm easy enough, I connected my serial cable to the box and logged into the console of the storage controller and tried to execute the command. The serial shell promptly told me, "reset is overloaded ...... undefined symbol : storageArray". Maybe I had a typo ? ... tried again, no joy.

A note was sent to an engineering contact, with a quick reply of "right command, wrong environment. Run it using the SMCLI command." So, if I just would of RTFM'd a little closer, it clearly states to run the command from the CLI.

Ohhhh the little things in life that bring us pleasure. Now the light is again glowing a soothing shade of blue. I once heard from someone that studies were done around calming affects of different colors. The results of those studies resulted in the shade of blue light that you now find on servers, storage, stereo equipment, and many other things. Of course it could also be an urban legend.

Scott - Comments
End Blog Entry
Start Blog Entry

Dell and Altiris
03/26/2008 - Comments

Todd and I had lunch with Jordan from Altiris last week. Discussed a few things in the pipe between our two companies. I haven't worked much with Altiris in the past, so I'm going to install the Altiris suite of products on my Dell PowerEdge 2970 that I'm using for my systems management server. I've got OM, the Microsoft Systems Center suite of products, VMware Virtual Center, and some other SNMP tools on that box. We'll see how nicely it all plays together on the same box. Definitely not recommended best practices, but I'm in a lab and that == freedom :-)

Working on that this week and will install the Altiris Management Suite for Dell Servers and see what that is all about.

And btw, if you've worked with Altiris much, I'm sure you're familiar with the Juice Community. Be sure to check out Dell's section on Juice.

Scott - Comments
End Blog EntryStart Blog Entry

OpenManage 5.4 Released for Download Yesterday
03/19/2008 - Comments

OM 5.4 is released and available on the support download site. Look for everything dated 3/18/2008 and that will help you narrow down the search. Also see my post below - "Download OpenManage - or - How to Navigate the Maze to OpenManage Downloads" - if you're new to OpenManage.

Here's the link to the Systems Management downloads for the Dell PowerEdge 2950 as an example. Again, look for everything dated 3/18/2008.

- Scott - Comments
End Blog Entry
Start Blog Entry

ESX 3i on Dell PowerEdge 2950 III
03/13/2008 - Comments
I installed ESX 3i on one of our Dell PowerEdge 2950 III's in the lab to see what Virtual Center would show me from a management point of view. I pulled our latest image from our internal source, dd'd it to a USB flash drive. Then just slipped it into the internal USB port of the machine and changed the boot order and voila, ESX 3i was up and running.

Configured the IP address and that was it. I followed some simple instructions documented by our Dell Virtualization Engineering team (document link coming soon - once it's published) and the server showed up in my ITA console under "VMware ESX Servers".

One useful thing that ITA allows you to do is add a Favorite Application. You can define a .exe or a URL and then assign that to the ITA groups so it shows up when you right click. You can also pass parameters as arguments to give it more functionality. I added the Virtual Center Client, so I can right click on any of the VMware ESX hosts and launch the VC client. Here's what it looks like in the ITA console :



One thing I can't find is how to pass the userid and password as parameters. Searched a little on VMTN but couldn't find anything. If anybody knows, or has ideas, please let me know.

The Favorite Application feature is nice because you can launch any tool in your toolbox from a single pane of glass. I'm a fan of using the right tool for the right job, and this feature lets you launch the right tool. In the VC Client, there is some new information you can see from the Configuration tab. ESX 3i has the CIM layer built in so you can see some health status information from the server. Here's what we see with ESX 3i on the 2950 III :



So you can see Fan, Temp and Power Supply information. I'm getting my arms around when the status changes from Green to Yellow to Red, and where the alerts get generated. I'll followup with another blog entry on my findings.

We've also got another yet-to-be-named machine in the lab with ESX 3i, it apparently has more instrumentation, because here's the screen shot of what you see in its Health Status screen :

VESO Health Status screen on VMware ESX 3i

Scott - Comments
End Blog Entry


Start Blog Entry
Job Opening - Chat - and some Vacation
03/03/08 - Comments

Just got back from some vacation in Sydney Australia, great time highly recommend a trip. Didn't get to see any of the outback, have to do that next time. Mainly spent time in the city and on the beaches. Also made it to the Hunter Valley wine region. The whole coastal area really reminded me of the California coast.

Logged on this morning and saw that we have a job posting ! .... geez guys it was only a vacation :-) Looks like Brian really wants the job.

The chat sessions have been picking up, we've got one tomorrow on OpenManage and VMware. We've been testing some things in the lab around 3i and will talk about our findings. As always, the discussion is also open to anything you want to bring up around that topic.

I'll have pictures up on my personal blog from the Australia trip soon. Looking forward to chatting with everyone tomorrow.

Scott - Comments
End Blog Entry

Start Blog Entry
Download OpenManage - or - How to Navigate the Maze to OpenManage Downloads
02/08/2007 -- Comments

We use Google Analytics to monitor the traffic on our website. Great tool, I also use it on my personal blog. I was looking through the keyword searches that people use to get here and it looks like quite a few people are searching on "Download OpenManage" or "openmanage download". Actually, for Jan 8th -Feb 8th the top keyword for the entire site was "openmanage 5.3 download".

Since that is what is bringing you here, I thought I'd take a few moments to help you navigate the maze. Let's examine the multiple ways to get what you want.

First - the most obvious - go to http://support.dell.com and drill through your machine type. For example, if we choose the Dell PowerEdge 2950 and select "Systems Management" for the Category we get this list of files to download.

Now comes the fun part of deciphering these file names to what you may commonly know them as.

"OpenManage Server Administrator Managed Node" - This is more commonly know as OMSA. This is the agent that is installed on the server and can then be accesed via web over port 1311. You will see two different download packages, one with a .exe extension, and one with a .msp. The .exe is the full version, the .msp is a Microsoft Service Pack to upgrade an existing OMSA installation.

"Dell CD ISO - PowerEdge Updates" - This is the Server Update Utility aka SUU. Double check the dates, this one is usually the 5.2 older version.

"Dell DVD ISO - Dell Server Updates" - This is also SUU, but in DVD format because SUU is cumulative. This is a standalone bootable image that will apply Dell Update Packages (DUPs) to your server

"Dell OpenManage Management Station" - This is IT Assistant (ITA). This link also has two versions, the .exe is the full version, and the .msp is the upgrade from version 5.2.0 and above.

"Dell OpenManage Deployment Toolkit" - Commonly called DTK. Used to create scripts for mass deployment. See some of the functionality in my demo called "Scripting with Systems Build and Update Utility"

"Dell CD ISO - Dell Systems Build and Update Utility" - Ahhhh this one is easier to decipher. You see this commonly referred to as SBUU or SBU. I've got a couple of demos using this image.

"Dell DVD ISO - Dell Systems Management Tools and Documentation" - a 3GB bandwidth choking download of SBUU, OMSA, ITA, DUPs, Service/Diagnostic tools, and Systems Documentation. Everything you need. You sometimes see this called SMTD.

Secondly - the more old school way - drop into the ftp site at http://ftp.us.dell.com/sysman/ , now if you hit that link through your browser, you will be lost. It's a little overwhelming to see about 1,000 filenames all in alphabetical order. The better way is through an ftp client so you can sort by date. I use FileZilla. Now when you sort by date and have the knowledge of the naming conventions that we just learned, you can easily interpret the screen shot below.



Hope that helps. Should be enough to get you started.

Scott -- Comments
End Blog Entry

Start Blog Entry
Power Monitoring in ITA - ITA Icons
01/24/2008 -- Comments

Dave finished some testing on the 10G Blades, and I finally got some dedicated access to an M600 blade in our chassis. I've been wanting to look at some of the power monitoring capabilities. Here's a very preliminary look at some of the attributes you can measure. You need to have latest OMSA, I installed 5.3.1 on this blade.

I used a simple CPU load generator to ramp up the power. It's a single threaded app, so had to run a few instances of it. So weird to see 8 CPUs show up in Task Manager for a blade ! .... who remembers some of the big honking floor standing servers with 4 CPUs that took up the space of a small fridge ?

We are about to get our 2950 III. Todd has first dibs on it, but I'll get the OMSA agent installed and do some more power monitoring and report back those findings.

I also saw an interesting thread in the Dell Community Forums. A similar question I had when I started working with ITA, and actually a question I still have about some parts of it. What do all the icons mean ?? .... yes you can hover over some of them, and most of them make sense, but some are not so easy to interpret what they are trying to say to me. So I figured we could just do a wiki page on the ITA Icons and you could help me fill out the chart. I'll update this page with a link to it. I just got screen shots, now I need to pull out the icons and build the page.

Please help me with it. We can have the developers fix any of our misinterpretations.

Scott -- Comments
End Blog EntryStart Blog Entry

Using ITA to update OMSA agents
1/11/2008 -- Comments

Last week I got an email asking about updating OMSA agents through ITA. Since I had just done some testing with the firmware and BIOS updates, I simply shot back a quick, "Yeah just generate a compliance report in the Software Updates and go from there."

Then of course I went to the interface to double check myself and bzzzzzzzt, incorrect answer. Which was quickly confirmed when the customer replied to the email with the same conclusion. So this just proves that I'm learning as I go, just like some of you.

An email back from one of the developers confirmed that OMSA agents get filtered out of the Repository because of some issues.

The workaround is to create a Report that is filtered on Agent name and Version, like this ...

Systems Edge - The Dell TechCenter

Then you can create a Software Deployment task for OMSA in ITA to perform the updates.

I guess I better get to work, look at the version on ora2650a ! -- 1.2.0

Scott -- Comments

End Blog Entry
Start Blog Entry
Happy New Year !

1/4/2008 -- Comments

Welcome to 2008 ! Got a chance before the break to get the demos posted on our main site -- www.dell.com/techcenter - check them out in the right hand frame. Although they got magically squished to 16:9 format in the player. I've got an open ticket on that and should be fixed soon.

Also we are now linked off the main Dell OpenManage site. Look for the link in the right hand navigation.

How was ya'lls break ? I had a ton of projects to do around the house. Luckily, Todd let me borrow his compound mitre saw. I had "borrowed" it for about a month and he told me that his father-in-law bought him a new one. So he let me buy the old one so I could quit borrowing it ! Thanks Todd ! ... .I've already got a a new laser guide on it.

That saw allowed me to put my mathematics degree to use. Anyone ever try to put up crown moulding ? Thank goodness for Google and people that share their information and insights. Kind of like what we are doing around here :-)

Which leads us to say thanks for all your contributions and please feel free to let your colleagues know we are here.

Scott -- Comments
End Blog Entry


Start Blog Entry
OpenManage 5.3 Demos are here !
12/11/2007 -- Comments

Got the demos up on the site. Check them out here.

But I'm sure what you are really interested in is the Vegas trip. You'll have to check out my profile on the wiki and find the link to my personal blog if you want that story !

I'm seeking input on other demos that would be of use. Just use the comments section and throw any ideas at me. I'm open and have some time the week before the Holidays to crank some more out.

Scott -- Comments

End Blog Entry


Start Blog Entry
OpenManage 5.3 Demos coming next week
12/6/2007 -- Comments

Just finished getting my head around all the new features in OpenManage 5.3. Great to have a lab with plenty of machines to test. Didn't even get yelled at once for rebooting any of my teammate's servers !

I took some time with my testing to capture screenshows. They are almost ready to go, getting some feedback from the team and then have to get them posted on Dell.com. So as soon as they get posted, I'll update you here with the links.

The first demo shows Systems Build and Update utility laying down an OS image on a bare metal PowerEdge server. SBU has other great functionality for deploying multiple systems. In the coming weeks I'll have other demos around that capability.

The second demo shows how to use Content Manager to download server updates to a centralized location for use with the Server Update Utility (SUU) over a network drive to update PowerEdge systems.

The third demo shows IT Assistant and the new Online Repository feature to keep servers up to date with the latest firmware/bios/drivers from the Dell support site.

Now that I've got a dedicated ITA machine, I plan on getting all the lab machines into ITA. Of course the lab has grown from a few machines to several racks of equipment. We've got maybe 4 different active directory domains, at least 3 different network segments, various versions of all the OSes. So it will be a ton of fun trying to architect the solution around all this. Maybe similar to how your environment has grown over the years.

So if you have any ideas on how I can tackle this problem in an easy way, I'm all ears. Luckily we have a lab tech, so I can put a lot of things on his to-do list :-) .... let me know how you've tackled this problem, maybe we can come up with some ideas together. Looking forward to hearing from you.

Ohhhh, just don't expect to get a response tomorrow. I'm headed to Vegas for a long weekend !

Scott -- Comments
End Blog Entry

Start Blog Entry
OpenManage 5.3 Released Today
11/20/2007 -- Comments

OpenManage 5.3 officially hit the streets today ! Download the bits from http://support.dell.com/ , just look for everything that has a release date of 11/20/07, under the "Systems Management" section.

I'm testing the new Systems Build and Update Utility that combines deployment, scripting, and updating all in one tool. I'll have a demo of the deployment portion of this on the wiki next week, with more demos soon after.

Let me know if you have any suggestions for demos you would like, or things we could test in the lab to aid in the understanding and use of the product. We've got a full complement of Dell hardware, storage, and software and are always looking to put it through the paces.


Scott -- Comments
End Blog Entry


Start Blog Entry
Welcome to the Edge
10/30/2007 -- Comments

Welcome to the "edge" of systems management. A discussion and collaboration place to share your thoughts and ideas on systems management topics. We will bring you the latest happenings in Dell's OpenManage line, along with what is happening in our partner space, from Microsoft, Altiris, VMware, and others.

We've got an entire lab of the latest Dell hardware ready to test all the latest releases. We can also try out your scripts other ideas.

We welcome you to join the discussion and participate on our wiki.

Scott -- Comments
End Blog Entry

Start Blog Entry
Welcome!
10/29/2007 -- Comments

Welcome to the Systems Edge blog !

Scott -- Comments
End Blog Entry

Tags: SystemEdge, Blog
Viewing all 335 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>