Troubleshooting. Dell EMC OpenManage Enterprise

Add to My manuals
215 Pages

advertisement

Troubleshooting. Dell EMC OpenManage Enterprise | Manualzz

A

Troubleshooting

Definitions about some of the commonly displayed fields in OpenManage Enterprise are listed and defined here as well as other useful information.

Topics:

Configuring a local network share for offline update

Troubleshooting connectivity

Firmware and DSU requirement for HTTPS

Firmware schedule reference

Firmware baseline field definitions

Supported and unsupported actions on proxied sleds

Schedule job field definitions

Alert categories after EEMI relocation

Token substitution in remote scripts and alert policy

Field service debugging

Catalog Management field definitions

PowerEdge server naming conventions

Devices with unknown compliance status

Configuring a local network share for offline update

Best practice is to use the automatic online update and backup features whenever possible. However, if your company is in a dark site or doesn't have access to the internet, you will need to structure and configure a local network share.

To configure a network share for

Updating the console and plugins

:

1.

Create the directory structure and download the update bundles .

2. Configure the share for offline update:

Configure an NFS network share on a Windows server

.

Configure an NFS network share on a Linux server .

Configure an HTTP network share on a Windows server .

Create the directory structure and download the update bundles

Create the directory structure required for offline software updates.

Prerequisites

Ensure you are a Windows user with administrator privileges.

About this task

For Updating the console and plugins , your network share directory structure should be the same as the structure

of the folder containing the required update files in the upgrade repository at https://downloads.dell.com/ openmanage_enterprise/ .

Steps

1. Open https://downloads.dell.com/openmanage_enterprise/ in a browser to display the contents of the upgrade repository.

2. Click the folder of the OpenManage Enterprise version that you want to upgrade to, and note whether the update contains a full or a minimal folder.

Troubleshooting 201

NOTE: Depending on the size of the update file (and subsequently, the time it would take to update the software), some OpenManage Enterprise versions will contain a full folder and others will contain a minimal folder. The full update bundle contains the full upgrade packages and typically takes much longer than a minimal update. The minimal update bundle is typically a patch release and only contains specific upgrade packages.

3. Create a folder on your local network share for <OMEUpdates> .

4. Copy the structure of the version folder in the upgrade repository to the <OMEUpdates> folder on your local network share.

In your local network share <OMEUpdates> folder: a. Create a folder for the OpenManage Enterprise software version that you want to upgrade to.

Make sure your local version folder is named the same as it is in the upgrade repository. For example, to update to

OpenManage Enterprise version 3.10, create ...<NetworkShare>/<OMEUpdates>/3.10/ .

b. Copy the latest LexingtonUpdates.xml

and LexingtonUpdates.xml.asc

files from the upgrade repository to your local software version folder.

c. Create either a full or a minimal folder, depending on which of these folders is in the required version folder in the upgrade repository.

For example, to update to OpenManage Enterprise:

● Version 3.9.2

, create ...<NetworkShare>/<OMEUpdates>/3.9.2/minimal .

● Version 3.10

, create ...<NetworkShare>/<OMEUpdates>/3.10/full .

d. Copy the OpenManage Enterprise update files from the upgrade repository to your local network share full or minimal folder.

Results

Your directory is structured correctly and contains the files required for updating OpenManage Enterprise and plugin software from a local network share.

Next steps

Configure the share:

Configure an NFS network share on a Windows server .

Configure an NFS network share on a Linux server

.

Configure an HTTP network share on a Windows server

.

Configure an NFS network share on a Windows server

When your network share is Windows-based, use Microsoft Windows Server Manager for offline software update and backing up OpenManage Enterprise appliances.

Prerequisites

● Ensure you are a Windows user with administrator privileges.

● If this share will contain your update bundles,

Create the directory structure and download the update bundles

.

Steps

1. Open Windows Server Manager .

2. Click File and Storage Services > Shares , select the share, and right-click Properties .

3. In the Share Properties screen: a. In the Authentication screen, select No server authentication and Allow unmapped user access by UID/GID .

b. In the Share Permissions screen, click Add...

, add a Host (IP address) for each OpenManage Enterprise appliance, and provide Read/Write access to each appliance.

4. Click OK .

202 Troubleshooting

Results

Your Windows network share is ready for Updating the console and plugins .

Next steps

If this share will contain your appliance backups,

Enable read and write access to your network share

.

Configure an NFS network share on a Linux server

Configure a network share on a Linux server with a Network File System (NFS) for offline software update and backing up

OpenManage Enterprise appliances.

Prerequisites

● Ensure you are a Linux user with administrator privileges.

● Ensure that an NFS package is not already installed by running rpm -qa nfs at the server Command Line Interface (CLI).

If there is no output, start with step 1. Otherwise, start with step 2.

● If this share will contain your offline update bundles,

Create the directory structure and download the update bundles

.

Steps

1. Install the NFS package by running: yum install nfs-utils libnfsidmap -y

2. Enable the NFS service by running: a.

systemctl enable rpcbind b.

systemctl enable nfs-server

3. Start the NFS service by running: a.

systemctl start rpcbind to convert the RPC program numbers into universal addresses.

b.

systemctl start nfs-server to enable the clients to access NFS shares.

c.

systemctl start rpc-statd to recover locked files when an NFS server crashes and reboots.

d.

systemctl start nfs-idmapd to translate user and group IDs into names and vice versa.

4. Create NFS under the / partition by running: mkdir /NFSSHARE

5. Allow the client to read and write data in the NFS you created by running: chmod 777 /NFSSHARE

Results

Your NFS network share is ready for

Updating the console and plugins .

Next steps

If this share will contain your appliance backups,

Enable read and write access to your network share

.

Configure an HTTP network share on a Windows server

Configure an HTTP or HTTPS network share on a Windows server for offline software update and backing up OpenManage

Enterprise appliances.

Prerequisites

● Ensure you are a Windows user with administrator privileges.

● If this share will contain your update bundles,

Create the directory structure and download the update bundles

.

Steps

1. Open Windows Server Manager , and select Add roles and features .

Troubleshooting 203

In the Add roles and features wizard : a.

Before You Begin screen, click Next .

b.

Installation Type screen, select Role-based or feature-based installation , and click Next .

c.

Server Selection screen, select Select a server from the server pool , select a server, and click Next .

d.

Server Roles screen, select the options in the screenshot below, and click Install .

Wait for installation to complete.

2. Restart the Windows server.

3. Open the Internet Information Services (IIS) application. In IIS:

● Change the Multipurpose Internet Mail Extensions (MIME) types:

○ Change the .xml

MIME type to application/octet-stream .

○ Add new .xml.asc

and tar.gz

MIME types: a. Open the Windows command prompt.

b. Enter cd \Windows\System32\inetsrv .

c. Enter appcmd.exe set config /section:staticContent /+

[fileExtension='.xml.asc',mimeType='application/octet-stream'] .

d. Enter appcmd.exe set config /section:staticContent /

+"[fileExtension='.tar.gz',mimeType='application/octet-stream']

● Enable read, source, and write access to the content on the network share: a. Click Add Authoring Rule . In the Add Authoring Rule dialog box: i.

Allow access to: section, select All content .

ii.

Allow access to this content to: section, select All users .

204 Troubleshooting

iii.

Permissions section, select all of the options; Read , Source and Write .

iv. Click OK .

b. Select Enable Rule .

● Configure the user authentication method: a. Click Select Authentication .

b. Enable both Allow Basic Authentication and Anonymous Authentication.

Results

Your HTTP or HTTPS network share is ready for Updating the console and plugins .

Next steps

If this share will contain your appliance backups,

Enable read and write access to your network share

.

Enable read and write access to your network share

To backup and restore appliances, you will need to enable both read and write access to a Common Internet File System (CIFS) or a Network File System (NFS) network share on a Windows server.

Prerequisites

● Ensure you are a Windows user with administrator privileges.

● Configure the share:

Configure an NFS network share on a Windows server

.

Configure an NFS network share on a Linux server .

Configure an HTTP network share on a Windows server .

Steps

1. In Windows, right-click on your <OMEUpdates> folder and select Properties .

● For CIFS file systems, click the Sharing tab.

● For NFS file systems, click the NFS Sharing tab.

2. Click the Share button.

The Network access dialog box is displayed.

3. Add an Administrator user with Read/Write permissions.

Results

You can Backup and restore from a local offline folder when there is no external connectivity.

Troubleshooting 205

Troubleshooting connectivity

From the Monitor > Troubleshoot page, you can perform various device connectivity tests, test appliance connectivity to external Dell resources, restart the appliance, test accessibility to network shares, generate a console log bundle, and enable/ disable field service debug (FSD).

NOTE:

To perform any tasks on OpenManage Enterprise, you must have necessary role-based user privileges and scope-based operational access to the devices. See

Role and scope-based access

.

Test protocol availability for any undiscovered device

Verify if the following protocols are available for an undiscovered device: SNMP, WS-Man, Redfish, IPMI, SSH, VMware, or

Rest_Storage.

Steps

1. On the Monitor > Troubleshoot page click on Device .

2. Select Test Protocol Connection .

3. In the IP Address/HostName box , enter the IP address or the hostname of the device.

4. From the Additional Settings > Protocol list, select one of the following: SNMP, WSMAN, REDFISH, IPMI, SSH,

VMWARE, REST_STORAGE

NOTE: SNMP testing can take longer to complete than other protocols due to the number of internal tests required.

5. Click Test .

Results

The result is displayed as 'Success' or 'Failed' with the details of the attempt.

Test protocol availability for a discovered device

Verify if the following protocols are available for a discovered device: SNMP, WS-Man, Redfish, IPMI, SSH, VMware, or

Rest_Storage.

Steps

1. On the Monitor > Troubleshoot page click on Device .

2. Select Test Protocol Connection .

3. In the IP Address/HostName box , enter the IP address or the hostname of the device.

4. Click Test .

Results

The result is displayed as 'Success' or 'Failed' with the details of the attempt.

Ping any device

Ping a device to see if it is accessible.

Steps

1. On the Monitor > Troubleshoot page click on Device .

2. Select Ping Device .

3. Under Additional Settings select values for Retries (1-31) and Timeout in seconds (1-100). The default values for Retries is 3 and for Timeout is 60 seconds.

206 Troubleshooting

4. Click Test .

Test appliance connectivity

This functionality can be used to verify that the appliance is connected to all web resources required to download MIBs, upgrade bundles etc.

Steps

1. On the Monitor > Troubleshoot page click on Appliance .

2. From the Sites list:

● Select Select All Sites to check connectivity with both Dell Online and Dell Warranty sites.

● Select Dell Online to check connectivity with Dell Online.

● Select Dell Warranty Information to check connectivity with the Dell Warranty site.

3. Choose the number of Retries (1-31). The default value is three.

4. Choose the Timeout seconds (1-100). The default is set at 60 seconds.

5. Click Test .

Restart the appliance

This option enables administrators to restart the appliance from within the user interface without the need to use the Text User

Interface (TUI).

Steps

1. On the Monitor > Troubleshoot page, click on Appliance .

2. Select Restart .

3. Click Restart .

This action logs out the user and restarts the appliance.

Test connection with network share

This functionality can be used to verify that the appliance is connected to all network shares and can access their contents.

Steps

1. On the Monitor > Troubleshoot page click on Network Share .

2. Select Share Type as CIFS or NFS .

3. Enter the Share Path linked to the Network drive to be tested.

4. Enter the Share IP Address . If you are using CIFS, enter the Workgroup , Username , and Password .

5. Click on Test Connection .

Generate and download console log archive

Generate archived console log data and download to a specified location.

Steps

On the Monitor > Troubleshoot page click on Logs .

a. To generate the console log archive file, click Generate Log .

b. To download the generated console log archive file, click Download Log .

Troubleshooting 207

Field service debug

Field service debug is only used to internally debug issue within the OpenManage Enterprise appliance, and can only be enabled with assistance from a certified Dell support representative.

Steps

On the Monitor > Troubleshoot page click on Field Service Debug .

● Click on Download .dat File to download the .dat file.

● Click on Upload Signed .dat File, SSH Public Key to upload the signed DAT.ini file or SSH Public Key.

● Click on Invoke Debug Capability to disable the debug capability on the console.

● Click on Disable FSD to invoke the debug capability on the console.

NOTE:

● When you invoke the debug capability, a Warning banner indicating the debug log collection is activated is displayed.

This warning banner is removed only when you disable FSD.

● Before you invoke the debug capability, ensure that the DAT.ini file is signed, returned by a certified Dell support representative, and uploaded to OpenManage Enterprise.

● Once you disable FSD, ensure that you stop any SSH daemon or SSH sessions that are currently using the debug capability.

Firmware and DSU requirement for HTTPS

If you have enabled the use of HTTPS for network share operations, then the servers must have the following minimum firmware and DSU to support the HTTPS-enabled device operations:

Use Case / Operation

Firmware Update

Driver Update

Server Configuration Profile (SCP) for template capture, deployment, configuration inventory, and remediation)

Technical Support Report (TSR)

Remote Diagnostics

YX2X (12G) or YX3X (13G) servers

FW v. 2.70.70.70

DSU v.1.9.1

FW v. 2.70.70.70

N/A

N/A

YX4X (14G) and above servers

FW v. 3.00.00.00

DSU v.1.9.1

FW v. 3.00.00.00

FW v. 3.21.21.21

FW v. 3.00.00.00

Firmware schedule reference

Schedule a firmware update to run immediately or at a later point of time.

● Update Now : The firmware version is updated and matched to the version available in the associated catalog. To make the update become effective during the next device restart, select the Stage for next server reboot check box.

● Schedule Later : Select to specify a date and time when the firmware version must be updated.

Firmware baseline field definitions

Defines the fields used while creating an OpenManage Enterprise firmware baseline.

● COMPLIANCE : The health status of the firmware baseline. Even if one device associated with a firmware baseline is in critical health status, the baseline health itself is declared as critical. This is called the rollup health status, which is equal to the status of the baseline that has high severity. For more information about Rollup Health status, see the Managing The

Rollup Health Status By Using iDRAC On The Dell 14th Generation And Later Poweredge Servers white paper on the Dell

TechCenter.

208 Troubleshooting

● NAME : The firmware baseline name. Click to view the baseline compliance report on the Compliance Report page. For more information about creating a firmware baseline, see

Create a baseline

.

● CATALOG : The firmware catalog to which the firmware baseline belongs to. See

Manage firmware and driver catalogs

.

● LAST RUN TIME

: The time when the baseline compliance report is last run. See Check the compliance of firmware and drivers

.

Supported and unsupported actions on proxied sleds

Some device actions are not available for sleds in a proxied state. The following table shows supported and unsupported

Redfish- actions on the proxied sleds.

ID Action

1 POWER_CONTROL_ON

Description

Power up

2 POWER_CONTROL_OFF Power Down hard/graceful

Power reset hard/graceful 3 POWER_CONTROL_RESE

T

4 SENSOR_DETAILS

5 POWER_MONITOR

6 TEMPERATURE_MONITO

R

8 FW_UPDATE

Get Sensor Info, sub system health details No

Power statistics retrieval

Temp statistics retrieval

YES

YES

Remote Firmware update capability.

Identify function on server

RedFish

YES

YES

YES

YES

YES 9 BLINK LED

11 HW_LOGS

12 DIAGS

System Hardware logs

Diagnostics

YES

No

13 TSR

16 VIRTUAL_CONSOLE

30 REMOTE_RACADM

31 REMOTE_IPMI

32 REMOTE_SSH

Tech Support Report

Ability to execute RACADM tasks

14G specific features

14G specific features

14G specific features

No

No

No

No

No

Schedule job field definitions

Defines fields used to create a job.

● Run now to start the job immediately.

● Run Later to specify a later date and time.

● Run On Schedule to run repeatedly based on a selected frequency. Select Daily , and then select the frequency appropriately.

NOTE:

● By default, the job scheduler clock is reset at 12:00 A.M. everyday. The cron format does not consider the job creation time while calculating the job frequency. For example, if a job is started at 10:00 A.M. to run after every 10 hours, the next time the job runs is at 08:00 P.M. However, the subsequent time is not 06:00 A.M. next day but 12:00 A.M. This is because the scheduler clock is reset at 12:00 A.M. everyday.

● Post deleting and re-creating a specific user, scheduled jobs created with the user may fail due to changes in the internal identification of the user. Re-create the recurring task from the active user to avoid failure.

Troubleshooting 209

Alert categories after EEMI relocation

Provides a list of previous alert categories and subcategories and their corresponding new categories and subcategories after

EEMI relocation.

Table 32. Alert categories

Previous Category

Audit

Previous Subcategory

Devices

Audit

Audit

Audit

Audit

Audit

Audit

Audit

Audit

Audit

Audit

Audit

Audit

Audit

Audit

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Miscellaneous

Miscellaneous

Miscellaneous

Miscellaneous

Miscellaneous

Miscellaneous

Miscellaneous

Miscellaneous

Miscellaneous

Miscellaneous

Inventory

Inventory

Inventory

Inventory

Inventory

Inventory

Firmware

Firmware

Jobs

Jobs

Jobs

Generic

Generic

Generic

Generic

Generic

Generic

Generic

Devices

Devices

Devices

Devices

Application

Application

Application

Application

Devices

Templates

Templates

Templates

Templates

Templates

New Category

System Health

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Audit

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Jobs

Jobs

Jobs

Jobs

Job

Job

Job

Devices

Devices

Devices

Jobs

Generic

Generic

Generic

Generic

Generic

Generic

Generic

New Subcategory

Devices

Devices

Devices

Devices

Devices

Application

Application

Application

Application

Users

Templates

Templates

Templates

Templates

Templates

210 Troubleshooting

Table 32. Alert categories (continued)

Previous Category

Miscellaneous

Previous Subcategory

Generic

Miscellaneous

Miscellaneous

Audit

Audit

Audit

Devices

Devices

Security

Security

Security

New Category

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

New Subcategory

Generic

Devices

Devices

Security

Security

Security

Token substitution in remote scripts and alert policy

OpenManage Enterprise supports use of tokens to enhance remote scripting and creation of the alert policies.

Table 33. Tokens supported in OpenManage Enterprise

Tokens

$IP

Description

Device IP Address

$MSG

$DATE

$TIME

$SEVERITY

$SERVICETAG

$RESOLUTION

$CATEGORY

$ASSETTAG

$MODEL

$HOSTNAME

Message

Date

Time

Severity

Service tag

Recommended Resolution

Alert Category Name

Asset tag

Model Name

FQDN or Hostname (if FQDN is not present)

Field service debugging

In OpenManage Enterprise, you can authorize console debugging by using the Field Service Debug (FSD) option.

About this task

By using FSD, you can perform the following tasks:

● Allow enabling and copying of debug logs

● Allow copying of real-time logs

● Allow backing up or restoring of database to VM.

Steps

1. Unblock FSD capability. See Unblock the FSD capability

.

2. Install or grant signed FSD DAT.ini file. See

Install or grant a signed FSD DAT.ini file

.

3. Invoke FSD. See

Invoke FSD

.

4. Disable FSD. See Disable FSD

.

Troubleshooting 211

Unblock the FSD capability

By using the OpenManage Enterprise TUI page, disable the FSD feature.

About this task

You can unblock the FSD capability through the TUI screen.

Steps

1. Navigate to the TUI main menu.

2. On the TUI screen, to use the FSD option, select Enable Field Service Debug (FSD) Mode .

3. To generate a new FSD unblock request, on the FSD Functions screen, select Unblock FSD Capabilities

4. To determine the duration of the debug capabilities being requested, select a start and end date.

5. On the Choose Requested Debug Capabilities screen, select a debug capability from a list of debug capabilities unique to the console. In the lower-right corner, select Generate .

NOTE: The debug capability that is currently supported is RootShell .

a. You can download the generated .dat file from the Monitor > Troubleshoot > FSD menu on the UI. Then, to complete

FSD enablement, upload the signed .dat file and SSH public key using the Upload options on the FSD screen.

b. If you have enabled CIFS share using the Enable CIFS share for FSD (emergency use only) option in TUI, then, use

Install/Grant Signed FSD DAT File on the FSD Functions screen. See

Install or grant a signed FSD DAT.ini file

6. On the Download DAT file screen, view the signing instructions and the URL address of the share where the DAT.ini file exists.

7. Use an external client to extract the DAT.ini file from the URL address of the share mentioned in step 6.

NOTE:

● The download share directory has read-only privileges and supports only one DAT.ini file at a time.

● If the DAT file is downloaded as DAT.txt, you must rename it to DAT.ini.

8. Perform either of the following tasks depending on whether you are an external user or an internal Dell user:

● Send the DAT.ini file to a Dell contact for signing if you are an external user.

● Upload the DAT.ini file to appropriate Dell Field Service Debug Authentication Facility (FSDAF) and submit.

9. Wait for a Dell signed and approved DAT.ini file to be returned.

Install or grant a signed FSD DAT.ini file

Download the Dell approved DAT.ini file, and then upload the DAT file to a file share URL or shared location.

Prerequisites

● If the DAT file is downloaded as DAT.txt, you must rename it to DAT.ini.

● Ensure that you have received the DAT.ini file, which is signed and approved by Dell .

● After Dell approves the DAT.ini file, you must upload the file to the console appliance that generated the original unblock command.

Steps

1. To upload a signed DAT.ini file, on the FSD Functions screen, select Install/Grant Signed FSD DAT File .

NOTE: The upload share directory has write-only privileges and supports only one DAT.ini file at a time. The DAT.ini file size limit is 4 KB.

2. On the Upload signed DAT file screen, follow the instructions about uploading the DAT.ini file to a given file share URL.

3. Use an external client to upload the DAT.ini file to a share location.

4. On the Upload signed DAT file screen, select I have uploaded the FSD DAT file .

212 Troubleshooting

Results

If there are no errors during DAT.ini file upload, a message confirming the successful installation of the certificate is displayed.

To continue, click OK .

The DAT.ini file upload can fail because of any of the following reasons:

● The upload share directory has insufficient disk space.

● The uploaded DAT.ini file does not correspond to the previous debug capability request.

● The signature provided by Dell for the DAT.ini file is not valid.

Invoke FSD

Invoke the FSD capabilities for using the debugging capability. Currently, RootShell is supported.

Prerequisites

Ensure that the DAT.ini file is signed, returned by Dell, and uploaded to OpenManage Enterprise.

Steps

1. To invoke a debug capability, on the FSD Functions screen, select Invoke FSD Capabilities .

2. On the Invoke Requested Debug Capabilities screen, select a debug capability from a list of debug capabilities that is approved in the Dell signed DAT.ini file. In the lower-right corner, click Invoke .

NOTE: The debug capability that is currently supported is, RootShell .

Next steps

While the invoke command is run, OpenManage Enterprise can start an SSH daemon. The external SSH client can attach with

OpenManage Enterprise for debugging purposes.

Disable FSD

Stop the debugging capabilities by disabling the FSD feature.

About this task

After you invoke a debug capability on a console, it continues to operate until the console is restarted, or the debug capability is stopped. Else, the duration determined from the start and end date exceeds.

Steps

1. To stop the debug capabilities, on the FSD Functions screen, select Disable Debug Capabilities .

2. On the Disable Invoked Debug Capabilities screen, select a debug capability or capabilities from a list of currently invoked debug capabilities. From the lower right corner of the screen, select Disable .

Results

Ensure that you stop any SSH daemon or SSH sessions that are currently using the debug capability.

Catalog Management field definitions

Defines the fields on the Catalog Management page.

CATALOG NAME : Name of the catalog. Built-in catalogs cannot be edited.

DOWNLOAD : Indicates the download status of catalogs from its repository folder. Statuses are: Completed, Running, and

Failed.

REPOSITORY : Repository types such as Dell.com, CIFS, and NFS.

Troubleshooting 213

REPOSITORY LOCATION : Location where the catalogs are saved. Examples are Dell.com, CIFS, and NFS. Also, indicates the completion status of a job running on the catalog.

CATALOG FILE : Type of catalog file.

CREATED DATE : Date when the catalog file was created.

PowerEdge server naming conventions

Based on the generation of a PowerEdge server, the server is identified with a unique name.

To cover a range of server models, the PowerEdge servers are now be referred to using a generic naming convention and not their generation. Use this topic to understand how to identify the generation of a PowerEdge server that is being referred to using the generic naming convention.

Table 34. PowerEdge server naming examples

YX3X servers YX4X systems

PowerEdge M630 PowerEdge M640

PowerEdge M830

PowerEdge T130

PowerEdge R440

PowerEdge R540

For example

The R740 server model is a rack, two processor system from the 14th generation of servers with Intel processors. In the documentation, to refer to R740, generic naming convention YX4X server is used, where:

● The letter Y (alphabet) is used to denote the following server form factors:

○ C = Cloud - Modular server nodes for hyper-scale environments

○ F = Flexible - Hybrid rack-based sleds for rack-based FX2/FX2s enclosure

○ M or MX* = Modular - Blade servers for the modular enclosure MX7000, M1000e and/or VRTX

○ R = Rack-mountable servers

○ T = Tower Servers

● The letter X (digit) denotes the class (number of processors) of the server.

● The digit 4 denotes the generation of the server.

● The letter X (digit) denotes the make of the processor.

Devices with unknown compliance status

The firmware or driver compliance status of the following storage, networking, and hyperconverged infrastructure (HCI) devices in the firmware/driver baseline compliance reports is displayed as Unknown as the Dell firmware/driver catalog does not support the firmware or software updates for these devices.

Table 35. False compliant devices

Device Category

Storage

Network devices in the FX2, VRTX, and M1000e chassis

Hyperconverged Appliances (HCI)

Device List

● SC Series

● MD Series

● ME Series

● F10 switches

● IOAs (Input/Output Aggregators)

● IOMs (Input/Output Modules)

● VXRail

● XC Series

214 Troubleshooting

Table 35. False compliant devices (continued)

Device Category

Devices updatable using individual device's Dell Update

Package (DUP) but not directly supported on Dell catalog

Devices that cannot be updated using the Dell catalog or the individual DUP

NOTE: For firmware/driver update of these devices, please refer the respective device's Installation Guide.

Device List

● MX9116n Fabric Engine

● MX5108n Ethernet Switch

● PowerEdge MX5000s

● MX7116n Fabric Expander Module

● PowerEdge MX 25GbE PTM

NOTE: For the complete list of devices in the SC, MD, ME, and XC series, refer https://topics-cdn.dell.com/pdf/dellopenmanage-enterprise_compatibility-matrix2_en-us.pdf

Troubleshooting 215

advertisement

Related manuals

Download PDF

advertisement

Table of contents