Dell PowerConnect OpenManage Network Manager Release Notes 4.4 - Page 17

PowerConnect J-Series - powerconnect openmanage network manager download

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

Page 17 highlights

Open Manage Network Manager - Release Notes 17 Known Issues Devices with two CPUs may not need to reboot, using failover to transfer the firmware to both processors. (12638, 12394) For RX devices, download and deploy firmware updates as you ordinarily would, registering the OS image in the OS Images manager and deploying them to either a device or group with the action menu. Supported Powerconnect B-series systems include the following models: PowerConnect B-RX4, PowerConnect B-RX8, PowerConnect B-RX16, PowerConnect B8000/8000e, and PowerConnect B-DCX4S. • MLXe does not support ethernet link discovery. (PV-14912) • Deploying firmware to these devices requires an external file server. (12512) • Even though restoring a file is successful, a 4xS device does not send an indication the internal file server can interpret as a successful conclusion to the restore action. In this case, the timeout emitted by the file server can be benign. (12584) • RX devices cannot discover links between the two RX devices or between an RX and a Dell device. This occurs because the device does not populate the LLDP-MIB LocPortTable with unique port IDs. Therefore, link discovery cannot accurately get the port used for a link and hence the end point is the top level device itself. When a device has multiple links, only one of the links can be discovered.The rest are discarded by OpenManage Network Manager as duplicates because the Local Port ID is supposed to be unique. (12464, 12409) • OpenManage Network Manager will not telnet connect to some devices if they use the factory default password. You must set the password to something other than that default. OpenManage Network Manager does not recognize the additional prompt asking that default password be changed each time log in occurs. (12240) • The Advanced Port Report has no data. Workaround: Resync device and run the report again (35544) PowerConnect J-Series This equipment has a slightly different firmware deployment than standard PowerConnect models. Firmware / OS Image Update Procedure Follow these steps to update firmware on the devices: 1. Download the firmware update from www.juniper.net. 2. Include it as an OS image in OpenManage Network Manager. 3. Deploy that image, selecting the device and the file loaded in OpenManage Network Manager. To deploy the image, select the device(s) and select the file in OS Manager. If you have a choice of Image Type in the pick list below the list of supported models between a "jbundle" or "jinstall" file, select "jinstall." Not all models

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
17
Open Manage Network Manager – Release Notes
Devices with two CPUs may not need to reboot, using failover to transfer the
firmware to both processors. (12638, 12394)
For RX devices, download and deploy firmware updates as you ordinarily would,
registering the OS image in the OS Images manager and deploying them to either
a device or group with the
action
menu.
Supported Powerconnect B-series systems include the following models: Power-
Connect B-RX4, PowerConnect B-RX8, PowerConnect B-RX16, PowerConnect B-
8000/8000e, and PowerConnect B-DCX4S.
Known Issues
• MLXe does not support ethernet link discovery. (PV-14912)
• Deploying firmware to these devices requires an external file server. (12512)
• Even though restoring a file is successful, a 4xS device does not send an indi-
cation the internal file server can interpret as a successful conclusion to the
restore action. In this case, the timeout emitted by the file server can be
benign. (12584)
• RX devices cannot discover links between the two RX devices or between an
RX and a Dell device.
This occurs because the device does not populate the LLDP-MIB LocPortTable
with unique port IDs. Therefore, link discovery cannot accurately get the port
used for a link and hence the end point is the top level device itself. When a
device has multiple links, only one of the links can be discovered.The rest are
discarded by OpenManage Network Manager as duplicates because the Local
Port ID is supposed to be unique. (12464, 12409)
• OpenManage Network Manager will not telnet connect to some devices if
they use the factory default password.
You must set the password to some-
thing other than that default.
OpenManage Network Manager does not rec-
ognize the additional prompt asking that default password be changed each
time log in occurs. (12240)
• The Advanced Port Report has no data.
Workaround
: Resync device and run
the report again (35544)
PowerConnect J-Series
This equipment has a slightly different firmware deployment than standard Pow-
erConnect models.
Firmware / OS Image Update Procedure
Follow these steps to update firmware on the devices:
1.
Download the firmware update from www.juniper.net.
2.
Include it as an OS image in OpenManage Network Manager.
3.
Deploy that image, selecting the device and the file loaded in OpenManage
Network Manager. To deploy the image, select the device(s) and select the file
in OS Manager.
If you have a choice of
Image Type
in the pick list below the list of supported
models between a “jbundle” or “jinstall” file, select “jinstall.” Not all models