Extreme Networks EPICenter Guide Spécifications télécharger pdf (Page 23)

Issues Resolved in the Initial 7.0 Release

EPICenter Release Note

35 If you created an EPICenter script to save the primary and secondary configurations on a device, the

configurations were saved successfully, but the script inserted an invalid character that generated an

error message, which caused EPICenter to report that the script was unsuccessful. (PD4-664418801)

36 Resizing the Upload Configuration from Devices window caused the Device Group box in the

window to display incorrectly. (PD4-664418938)

37 When EPICenter saved the configuration file for a device, it incorrectly used the system type as part

the file name instead of the system name. (PD4-696015881)

38 In the EPICenter Telnet window, if you pressed the Esc key to exit a command that automatically

refreshes the screen, such as show port util, you had to click within the Telnet window again in

order to enter text in the window. (PD4-700544461)

39 If you closed the EPICenter Admin window, then clicked Users, Roles, and Servers under the

EPICenter Administration folder, it did not reopen the EPICenter Admin window. (PD4-700544495)

40 Running the Network Status Summary report resulted in a “Report server Timed out” message.

(PD4-681710347)

41 The Save window did not list the folders in the current directory unless “All files” was selected in

the Files of Type box. (PD4-624968761)

42 The Device Group box in the Download Configuration window was displayed incorrectly. (PD4-

544326151)

43 Composite links consisting of 25 or more links did not get updated in the Navigation Table after

clicking the Refresh active window icon. (PD4-435697730)

Issues Resolved in the Initial 7.0 Release

1 Alarm Manager: For ExtremeXOS devices, this release of EPICenter now supports the “CPU

Utilization” alarm threshold setting using the extremeCPUMonitorThreshold MIB OID. (PD3-

212215991)

2 Alarm Manager: When an RMON threshold configuration was applied to a port group consisting of

a large number of ports (more than 5000 ports), the configuration was unsuccessful, and the

EPICenter client was disconnected. (PD3-184163421)

3 Alarm Manager: On a topology map, EPICenter incorrectly reported the status of an alarm that was

acknowledged then unacknowledged as active. (PD3-206059203)

4 Configuration Manager: A scheduled configuration upload failed with an SSH error message:

“Could not establish connection via ssh due to error : null reference is not allowed” (PD3-

157373545)

5 Configuration Manager: A scheduled configuration upload failed with an SSH error message:

“Could not establish connection via ssh due to error Java heap space” (PD4-368008904)

6 Inventory: An 8-node stack of Summit X-series switches could not be added to EPICenter with full

functionality. (PD4-344038211)

7 Inventory: The G48Te2 module with PoE configured on BlackDiamond 8800-series switches was not

correctly recognized and displayed in EPICenter. (PD4-386837791)

Clarifications and Known Problems

This section describes known problems and clarifications that apply to this EPICenter release.

1 2 ... 18 19 20 21 22 23 24 25 26 27 28 ... 31 32

Pas de commentaire

Extreme Networks EPICenter Guide Spécifications Page 23