Dell PowerConnect OpenManage Network Manager Release Notes 5.0 - Page 11
Service Tag and Asset Tag by OpenManage Network Manager. This includes - powerconnect openmanage network manager download
View all Dell PowerConnect OpenManage Network Manager manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 11 highlights
11 Known Issues • In the Image Repository portlet, clicking on Download > Firmware for Dell PowerConnect may download out of date firmware for Dell PowerConnect classic devices. Workaround: OpenManage Network Manager has pre-seeded firmware for devices and you can download firmware for each device from the Dell support site. (16561) • Some Dell devices and firmware revisions may not support the collection of Service Tag and Asset Tag by OpenManage Network Manager. This includes recent firmware revisions of Force10, PowerConnect B-Series, and PowerConnect W-series along with older revisions of PowerConnect firmware. (16098) • For Force10 S50V devices OpenManage Network Manager may show total memory to be less than memory used. (18301) • JUNOS event definitions are not supported in this release. (18869) • When ACLs are configured on Force10 S4810 devices, when copying a restored configuration to the running configuration, an error may appear during restoration. (18905) • 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) • sFlow data captured may not appear, or may appear incorrectly. For this build, sFlow data is for representational purposes and the issues will be resolved in a future build (17935, 18212)