Dell OpenManage Network Manager Release Notes 5.1 - Page 9

Workaround - force10

Get Dell OpenManage Network Manager PDF manuals and user guides View all Dell OpenManage Network Manager manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

9 • When you upload a Force 10 image into OpenManage Network Manager, then Deploy it to a group of devices, then you will see five options for image type. Choose only the first option for this to work. (18952) • You may see multiple options for selecting the configuration file to backup for PowerConnect (not Force10) devices. Layer 2 Powerconnect switches have just running and startup options while the Layer 3 router has running, startup and backup options, so different options appear for the two sets of switches. When you do file backup for a group of devices, all those options are combined. Select only the top entry selection for execution. (18944) • For C series and E series devices, the management interlace appears as a port, though it should appear as an interface. (18949 18945) • Sometimes Force10 devices may not respond to ICMP pings. Reports or applications would appear without data if you are only monitoring Force10. For example, the performance portlet for "Top Ping Response" would appear without data if you are only monitoring Force10 devices. To monitor the network status of the Force 10 devices, you can create "Force10 SNMP" monitor to poll Force10 devices using SNMP (sysUpTime). When this "Force10 SNMP" monitor receives a valid response, the network status appears as Responding. (18881) • Combining the discovery of different kinds of links may produce errors. So discovering Fiber Channel alone or Ethernet alone is problem free. However, combining discovery of both makes Ethernet link discovery display an error. Workaround: run the types of link discovery by themselves. (18819) • OMNM supports downloading OS images for all devices it supports. Downloading OS images for one device downloads OS images for all devices. (18777) • The firmware report displays unnecessary entries showing firmware changes from empty to a firmware number. (18719) • The Add Stack Management ACLI is not supported for PowerConnect 35xx models (13793) • CPU and Memory usage values do not appear for PC 5524P (17505) • The Dell Force10 S50AC device appears as a Dell Force10 S50DC device (17890). • For Dell Force10 devices, interfaces like management and loopback may appear as both ports and interfaces. (18309) • For Dell PowerConnect 8024/F, restoring a configuration for a stack of devices may fail (16953) • The OS image portlet may report "Invalid Device class" for the devices. (17114) • For Dell PowerConnect M8024-k and 8024/F user ports that are used for stacking ports do not appear in the Network View (16944, 16951) • 8024/F fibre channel link discovery is not supported. (16943) • Some devices do not respond to commands unless they are in the correct state. For example, some Dell devices must not be in "Simple" mode to respond to Adaptive CLIs. Take account of this as you create Adaptive CLIs. (17153)

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
9
• When you upload a Force 10 image into OpenManage Network Manager,
then Deploy it to a group of devices, then you will see five options for image
type. Choose only the first option for this to work. (18952)
• You may see multiple options for selecting the configuration file to backup
for PowerConnect (not Force10) devices. Layer 2 Powerconnect switches have
just running and startup options while the Layer 3 router has running, star-
tup and backup options, so different options appear for the two sets of
switches. When you do file backup for a group of devices, all those options
are combined. Select only the top entry selection for execution. (18944)
• For C series and E series devices, the management interlace appears as a port,
though it should appear as an interface. (18949 18945)
• Sometimes Force10 devices may not respond to ICMP pings. Reports or appli-
cations would appear without data if you are only monitoring Force10. For
example, the performance portlet for “Top Ping Response” would appear
without data if you are only monitoring Force10 devices. To monitor the net-
work status of the Force 10 devices, you can create “Force10 SNMP” monitor
to poll Force10 devices using SNMP (sysUpTime). When this “Force10 SNMP”
monitor receives a valid response, the network status appears as Responding.
(18881)
• Combining the discovery of different kinds of links may produce errors. So
discovering Fiber Channel alone or Ethernet alone is problem free. However,
combining discovery of both makes Ethernet link discovery display an error.
Workaround:
run the types of link discovery by themselves. (18819)
• OMNM supports downloading OS images for all devices it supports. Down-
loading OS images for one device downloads OS images for all devices.
(18777)
• The firmware report displays unnecessary entries showing firmware changes
from empty to a firmware number. (18719)
• The Add Stack Management ACLI is not supported for PowerConnect 35xx
models (13793)
• CPU and Memory usage values do not appear for PC 5524P (17505)
• The Dell Force10 S50AC device appears as a Dell Force10 S50DC device
(17890).
• For Dell Force10 devices, interfaces like management and loopback may
appear as both ports and interfaces. (18309)
• For Dell PowerConnect 8024/F, restoring a configuration for a stack of devices
may fail (16953)
• The OS image portlet may report “Invalid Device class” for the devices.
(17114)
• For Dell PowerConnect M8024-k and 8024/F user ports that are used for
stacking ports do not appear in the Network View (16944, 16951)
• 8024/F fibre channel link discovery is not supported. (16943)
• Some devices do not respond to commands unless they are in the correct
state. For example, some Dell devices must not be in “Simple” mode to
respond to Adaptive CLIs. Take account of this as you create Adaptive CLIs.
(17153)