Dell PowerConnect OpenManage Network Manager Release Notes 5.1 - Page 12

12 • You must typically increase the timeout for firmware deployment of multistack devices. Stop the Dell OpenManage Network Manager service in Windows., edit the file powerconnect/lib/dellpc.property, and set PC_NR_TIMEOUT = 10000000. (6681) • To disable LAG Spanning Tree on a 62xx, you must set the Path Cost to a minimum of 1. Leaving path cost at 0 will cause an SNMP error. (6304) • Dell devices have an SNMP Management Station entry in their web pages that specifies a destination for SNMP communication. If this does not include the address of the mediation server (in single host installations this is the application server), discovery will fail on the SNMP get step. (6689) • Supported Powerconnect B-Series Devices Known Issues Supported Powerconnect B-series systems include the following models: Supported PowerConnect B-series systems include the following models: B-MLXe4, B-MLXe8, B-MLXe16, B-FCOE1024, B-FCX624, B-FCX624S, B-FCX648, BFCX648S, B-TI24X, B-RX4, B-RX8, B-RX16, B-8000/8000e, B-DCX4S Supports is included for firmware versions 5.2.0 or higher. • M8428K does not display the correct model number, performance indicators and serial number in the details panel. (17447) • A limited amount of interface data is collected from Powerconnect B-Series Ethernet capable switches. As a result, interface reports and the Interfaces portlet do not contain Ethernet Link data for these devices. This also means Ethernet Links do not appear for these devices.(18800, 18802) • Right-click menu in Performance - Top Ping Response portlet does not appear. Workaround: Right-click in the Managed Resources portlet. (18827) • Network Details VLAN screen for B-RX devices does not display VLAN information since required MIBs are not supported or populated by the device. (16419) • Informs are not supported on these devices. If you check the checkbox to send informs to v3 trap recipients it will send informs rather that v3 traps. Workaround: Don't check the checkbox. (18435) • 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