® Extreme Management Center Release Notes Version 8.4.4 5/2020 9036572-05 Rev.
Table of Contents Extreme Management Center® Release Notes Version 8.4.4 1 Table of Contents 2 Extreme Management Center Version 8.4 Release Notes 6 1. Enhancements in Version 8.4 6 1.1 Engines 7 1.2 Extreme Management Center 7 1.3 ExtremeAnalytics 13 1.4 ExtremeCompliance 14 1.5 ExtremeConnect 15 1.6 ExtremeControl 15 1.7 ExtremeWireless 17 2. Deprecated Features 17 3. Known Issues and Vulnerabilities Addressed 17 3.1 Known Issues Addressed in 8.4.4.26 17 3.
4.1.3 Custom MIBs and Images 4.2 Important Upgrade Considerations 49 49 4.2.1 License Renewal 51 4.2.2 Upgrading Hardware 51 4.2.3 Free Space Consideration 51 4.2.4 Site Discover Consideration 51 4.3 ExtremeAnalytics Upgrade Information 52 4.4 ExtremeControl Upgrade Information 52 4.4.1 General Upgrade Information 52 4.4.2 ExtremeControl Version 8.0 and later 53 4.4.3 Other Upgrade Information 53 4.5 Fabric Configuration Information 54 4.5.1 Certificate 54 4.5.
.6.4 SLX Device Configuration 57 4.6.5 ExtremeXOS Device Configuration 58 4.7 Firmware Upgrade Configuration Information 58 4.8 ExtremeWireless Upgrade Information 59 5. System Requirements 59 5.1 Extreme Management Center Server and Client OS Requirements 59 5.1.1 Extreme Management Center Server Requirements 59 5.1.2 Extreme Management Center Client Requirements 60 5.2 Extreme Management Center Server and Client Hardware Requirements 60 5.2.
.12.1 Guest and IoT Manager Server OS Requirements 67 5.12.2 Guest and IoT Manager Outlook Add-in Client Requirements 67 5.12.3 Guest and IoT Manager Virtual Engine Requirements 68 5.12.4 Guest and IoT Manager Supported Browsers 68 6.
Extreme Management Center Version 8.4 Release Notes 8.4.4.26 May, 2020 The Extreme Management Center Release Notes provide information on the new features and enhancements included in version 8.4, as well as issues that have been resolved and configuration changes for this release. IMPORTANT: For upgrade and installation requirements, as well as configuration considerations, please see Extreme Management Center Configuration and Requirements.
1. Enhancements in Version 8.4 1.1 Engines l Upgrades Accessible to Engines without Internet Connectivity l Operating Systems Upgrade to Ubuntu 18.04 Upgrades Accessible to Engines without Internet Connectivity Upgrades for the Extreme Management Center server, the ExtremeAnalytics engine, and the ExtremeControl engine are now accessible without internet connectivity. Operating Systems Upgrade to Ubuntu 18.
1. Enhancements in Version 8.4 l Ability to Sort Multiple Columns in FlexViews Table l Improvements to Extreme Management Center Filter Tool Fabric Enhancements in Extreme Management Center Version 8.4.4 Extreme Management Center version 8.4.4 includes the following fabric enhancements: l l l l SUNI and TUNI services are now included when importing a device's configuration into a Service Application. In version 8.4.
1. Enhancements in Version 8.4 ExtremeCloud Appliance VE6125 Model Supported Extreme Management Center now supports the ExtremeCloud Appliance VE6125 model. Enhancement to Sites on the Devices Tab The Tasks menu is now available for sites on the Network > Devices tab in Device Trees and the Device Grid to allow the execution of Script and Workflow tasks.
1. Enhancements in Version 8.4 l l l Layer 2 VSN Service Creation - Automatically maps VLAN entries to Layer 2 VSNs. VLAN Pruning - Prevents the unnecessary configuration of VLANs that have no egress. Import to Service Definition - Enables you to import a device's active configuration into a Service Application, which you can then use as a configuration template for other devices managed by Extreme Management Center. Added Support for Additional Device Types in Version 8.
1. Enhancements in Version 8.4 Additional Device Types Can Now Be Managed via ZTP+ The following device types can now be managed via ZTP+: l l l ExtremeXOS devices, in a stacked configuration, running ExtremeXOS Cloud Connector version 3.4.x or later. ERS3600 on which firmware version 6.4 or later is installed. ERS4900/5900 on which firmware version 7.8 or later is installed support discovery via ZTP+.
1. Enhancements in Version 8.4 Enhancements to Inventory Dashboard and Reports Enhancements to the Inventory Dashboard (accessible via the Network tab) include new pie charts and reports that you can use to view the activity and status of the devices and ports that comprise your network. The following charts are included on the Inventory Dashboard: Devices By Operating System - Categorizes devices by network operating systems.
1. Enhancements in Version 8.4 Port Statistic Collection Status - categorizes the ports, at the site you select, that currently are and are not collecting statistics. The criteria for each chart is configurable, and selecting each chart opens a report displaying details about the device and port activity. The Inventory Dashboard also includes Asset and Device Tracking tabs. Use these tables to monitor changes made to assets and devices in your network.
1. Enhancements in Version 8.4 work with Splunk and files that you can copy to the Splunk server to facilitate integration. Improvements to Response Time Dashboard The ExtremeAnalytics Response Time dashboard, when grouping by interface, displays only the device IP address for received Application Telemetry flow data when it is lacking sampled packet information. 1.4 ExtremeCompliance The Information Governance Engine is now ExtremeCompliance. When you install Extreme Management Center 8.
1. Enhancements in Version 8.4 l VSP1480 l VSP4900 l VSP 7400-48Y Regimes and audit tests created in versions 8.1, 8.2, and 8.3 are retained following the upgrade. 1.5 ExtremeConnect l New End-System and OS Fields Added l ExtremeConnect Configurations Included in Extreme Management Center Backups New End-System and OS Fields Added New custom end-system data fields and additional operating system data fields have been added to ExtremeConnect.
1. Enhancements in Version 8.4 Enhanced Enforce Preview Functionality for ExtremeControl The Enforce Preview functionality is enhanced for the ExtremeControl engine configuration, displaying additional details about the enforce. ExtremeCloud Appliance Uses CoA for Reauthentication ExtremeCloud Appliances now use Change-Of-Authorization (CoA) by default for reauthentication. Enhancement to Scheduled Backup Functionality in Guest & IoT Manager In versions of Extreme Management Center prior to 8.4.
2. Deprecated Features 1.7 ExtremeWireless 11ax Radio for AP5xx Models Supported ExtremeWireless now supports 11ax Radio for AP5xx models. 2. Deprecated Features Beginning in Extreme Management Center version 8.4, the legacy Java applications (Console, MIB Tools, NAC Manager, and Policy Manager) are deprecated and disabled by default. These applications will no longer be available in version Extreme Management Center 8.5. To use the legacy Java applications in version 8.
3. Known Issues and Vulnerabilities Addressed Unsupported configuration options were available for devices set as DVR Leaf nodes. ------ Fomerly, the Source for SUNI/TUNI services was inconsistent. Now, the Source for SUNI/TUNI services is Inherited when mapping the port template to some ports. Services change to Local, when a port is manually mapped to the services via port picker (or Ports/LAGs column) on the Services tab.
3. Known Issues and Vulnerabilities Addressed Workflows triggered by an alarm or event were not running for devices that did not exist in the Extreme Management Center database. ------ The VLAN Grid on the Site tab was missing the Always Write to Device column, which was preventing the user from re-enabling the VLAN. This caused other features like ZTP+ to fail if Always Write to Device is not selected for the Default VLAN.
3. Known Issues and Vulnerabilities Addressed After upgrading to Extreme Management Center versions 8.4.1 or 8.4.2, saving a site did not complete successfully as the result of VRF/VLAN issues. 1997288 Creating an L2 Switched UNI service in the Service Application incorrectly required a port template selection when no CVID was entered. ------ Creating multiple L2 Switched UNI services using the same port was not allowed when selecting ports for an L2 service.
3. Known Issues and Vulnerabilities Addressed Policy enforce was failing in the following circumstances: l l ------ Attempting to create or rename VLANs on Wireless Controllers. Attempting to create more than 128 VLANs on Wireless Controllers with an SNMP error. Additionally, Policy enforce was incorrectly indicating success when enforcing to High Availability paired Wireless Controllers in the same domain with synchronization enabled.
3. Known Issues and Vulnerabilities Addressed The Networks > Archives tree was sorted alphabetically, which does not respect the logical (or numerical) system date and time format. 01946495 The packages needed to install libpam-cracklib on the Extreme Management Center server, the ExtremeAnalytics engine, and the ExtremeControl engine were not available. These packages are included when you upgrade to version 8.4.2.
3. Known Issues and Vulnerabilities Addressed When downloading an archive that is a compressed file, the extension was not .tgz. ------ PortView was showing incorrect results when the port name resolved to a numeric value. 1982771 AP7602, AP7612, AP7622, AP7632, AP7662, AP505, and AP510 were not displaying correctly in License Diagnostics.
3. Known Issues and Vulnerabilities Addressed ExtremeControl Issues Addressed ID Policy was not supported on ExtremeXOS X435 and X465 devices. ------ ExtremeControl was failing to enforce Inbound User-Based (IUB) and Outbound User-Based (OUB) rate-limits to the ExtremeCloud Appliance when the rate-limiters were mapped to an IUB or OUB reference index of 0. ------ When searching for and selecting an end-system in ExtremeControl, the Port View and associated tabs were rendering slowly.
3. Known Issues and Vulnerabilities Addressed Policy enforce to an Extreme Wireless Controller was failing when Policy VLAN Island (PVI) VLANs (that were not already created on the device) were used by a rule in the domain. ------ Enforcing a policy domain with IPv6 rules mapped to Network Resources was failing. 01979124 The Outbound User-Based Rate Mappings panel in the ExtremeControl Policy Enforce Preview window was not displaying any rate mappings for ExtremeCloud Appliance.
3. Known Issues and Vulnerabilities Addressed 3.3 Known Issues Addressed in 8.4.1.24 Extreme Management Center Issues Addressed The SLX TFTP upgrade from slxos18r.1.0 was failing if a full install was required. ID ------ In-place upgrades were failing due to obsolete packages. 01957868 The Extreme Management Center engine was improperly updating system files ownership to non-root users.
3. Known Issues and Vulnerabilities Addressed The ExtremeXOS CLI failsafe command was causing scripts in Extreme Management Center to time out. 01902921 Changing the Start Time for a scheduled archive on the Network > Archives tab was causing the Save button to be grayed out and unselectable. 1739514 1765473 Scheduled tasks with a Type of Scripting Task and Workflow Task incorrectly required Extreme Management Center to send an email when a scheduled task completed.
3. Known Issues and Vulnerabilities Addressed Restarting nssnmptrapd manually was saving the process ID to a file named 162. The process ID is now saved to the nssnmptrapd.pid file. 1184370 Port collection was unable to display interface history data on a port with an alias that contained a Plus symbol '+’. 1783878 The system log file was filling up the local disk in highly utilized environments.
3. Known Issues and Vulnerabilities Addressed It was not possible to disassociate a service definition from a site. Service definitions can now be dissociated from a site. Some of the GUI scenarios are as follows: ------ 1. Service definitions can be dissociated from a site only if they are not inherited from their parent site. 2. Only the site that directly has the service definition assignment can dissociate it. 3.
3. Known Issues and Vulnerabilities Addressed Extreme Management Center was attempting to prune VLANs that were dynamically created on the device by MVRP or Policy when VLAN pruning was enabled. This was only a display issue in the enforce preview window. The dynamic VLANs were properly being filtered out during the actual enforce operation. IP addresses that were removed from Extreme Management Center were included in a Statistics Collection target.
3. Known Issues and Vulnerabilities Addressed Importing a policy from an ExtremeCloud Appliance in to Extreme Management Center Policy was incorrectly setting the roles' default access control to permit when the actual configuration on the device was containing to a VLAN. The Access Control Configuration Evaluation Tool was not selecting the current NAC Configuration, AAA Configuration, and AAA Overwrite in the launch dialog when selecting an end system.
3. Known Issues and Vulnerabilities Addressed When using "Add Device" from the Devices tab when in the context of a group, the device was not being added to the group and could only be seen by switching to another device context (for example, Sites). 01953687 Extreme Management Center was displaying unexpected error counts in the SNMP Details view. Also, "end of table" was being included as an error.
3. Known Issues and Vulnerabilities Addressed When executing CLI commands, if some devices were not reachable, no exception was seen in the results. 01873061 The Port Duplex mode was incorrect on VSP and Summit Series switches. ------ Inventory Manager settings for SCP/SFTP had an incorrect default root path when Extreme Management Center was installed as non-root. ------ Discovered devices were not being automatically added even though the Automatically Add Devices Action was selected.
3. Known Issues and Vulnerabilities Addressed IP Addresses or device names had to be entered manually when adding entries to a Location Group in the Group Editor panel. A new Select Devices button, which allows users to select from a list of network devices, has been added. 1738208 01868775 The flow collector was attempting to apply a port-based IDs to flows with no identification without checking if the matching port-based fingerprint was enabled.
3. Known Issues and Vulnerabilities Addressed Users were not notified when VSP archive/restore was used with a non-admin CLI profile. ------ The Archive option for VSP devices to download the device backup file did not include the full backup, it only included the text file. ------ Extreme Management Center users with multipart usernames were incorrectly restricted from editing other users in the Authorized Users table. ------ Extreme Management Center access of Juniper switches was not working.
3. Known Issues and Vulnerabilities Addressed The Port Usage Details table was not displaying properly. To resolve the issue, the Collection status per port was added as this is also required to have a valid used percent statistic created. Extreme Management Center does not allow for PVID to be a tagged vid. 01935642 ------ Searching for alarm history By Source was not showing alarms if a device has a nickname and the device tree option for Device Tree Name Format is set to Nickname.
3. Known Issues and Vulnerabilities Addressed Tracking SNMP PDU errors was confusing. To address this, the following changes were made: l l l 01863719 Capture SNMP PDU error details by IP. Use List of IPs and check SnmpTrace in Configure Network Monitor Diagnostics. Reset the view to start. Alias information was missing from Endpoint Locations after importing them from a CSV file.
3. Known Issues and Vulnerabilities Addressed Scheduling an inventory task (for example, creating a device archive) and then applying an Extreme Management Center license (for example, NMS Advanced) was causing Extreme Management Center to create an identical inventory task. 01941537 01944216 Floor plan maps using rectangle objects to specify exterior walls were not displaying wireless coverage properly.
3. Known Issues and Vulnerabilities Addressed Applying a port template was a one-time import of settings to that port. Ports assigned a port template now always reflect that port template's settings. To override port settings, you must create a new template and assign it to the port or set the port's template value to Use Local Settings, which enables you to apply any setting to that port.
3. Known Issues and Vulnerabilities Addressed Creating a port template in a sub-site was potentially creating a port template with the same name in /World with an invalid configuration. ------ Syslog or SNMP Trap messages received from a device that had a source IP address that was not the same as the primary management address for that device was causing Alarm Mail notifications to be sent without a Device ID.
3. Known Issues and Vulnerabilities Addressed The ExtremeAnalytics engine was running out of storage space as a result of duplicate entries saved in the log. 01909813 After running the Configure VOSS App-Telemetry script, no status indicating whether the device was reachable was displayed. 01897718 ExtremeAnalytics did not allow you to disable the Virtual Sensor integration. You can now disable this integration to improve performance.
3. Known Issues and Vulnerabilities Addressed When the input/output interface was unavailable, Analytics was not showing any device information in the Response Time dashboard. 01846836 When uninstalling a virtual sensor, the Analytics Virtual Sensor grid was not marking it as Uninstalling, and there was no progress shown in the operation panel. ------ When installing a new virtual sensor, the tree panel was not getting updated as soon as the installation finished.
3. Known Issues and Vulnerabilities Addressed 802.1x authentication was occasionally allowing 0 length passwords to successfully authenticate. 01878461 In the Guest and IoT Manager (GIM), a username created using an email address was not authenticating in ExtremeControl. 01888057 Hexadecimal representations of integer type attributes were not encoded in Disconnect or CoA RADIUS frames.
3. Known Issues and Vulnerabilities Addressed Inbound/outbound rate limits for Policy Manager CoS were not supported for ExtremeCloud Appliance. ------ The End-System Application Details window would not populate with data when opened using Global Search for an end-system. 01877808 ExtremeControl engines running assessment and remediation sometimes caused SQL exceptions in the Extreme Management Center sever log when accessing a deprecated database table.
3. Known Issues and Vulnerabilities Addressed Creating unique Captive Portal registration buttons was not possible. To allow further customization the following CSS classes were added to the NAC Captive Portal buttons: l portalButtonLogin l portalButtonRegister l portalButtonCompleteRegistration l portalButtonAssessmentAcknowledge l portalButtonReattemptAccess 01861530 The old 'portalButton' class can still be used to modify all of the above buttons.
3. Known Issues and Vulnerabilities Addressed Simultaneously enforcing configuration to the NAC while configuring users on the Guest and IoT Manager sometimes resulted in the NAC returning an Internal Server Error message. 01916208 The Use RADIUS Accept Policy link in the Control authorization rules configuration opened an empty Edit Policy Mapping dialog. ------ The Auth. Access Type for ExtremeControl engine devices was not set to Manual Radius Configuration.
4.
4. Installation, Upgrade, and Configuration Changes For complete installation instructions, refer to the installation documentation located on the Documentation web page: https://www.extremenetworks.com/support/documentation/. If you have requested an Extreme Management Center evaluation license, you received an Entitlement ID. This Entitlement ID allows you to generate a product evaluation license key. Refer to the instructions included with the Entitlement ID to generate the license key.
4. Installation, Upgrade, and Configuration Changes 4.1.1 Installing Without an Internet Connection If your Linux system requires an operating system upgrade, you are prompted to upgrade using either an internet connection or locally (without an internet connection) if no additional Ubuntu packages need to be installed. !!! ATTENTION !!! We can attempt to upgrade the OS without using the internet if there were no extra Ubuntu packages installed.
4. Installation, Upgrade, and Configuration Changes upgrading from version 8.1 or earlier of NetSight/Extreme Management Center, you must perform an intermediate upgrade. For example, if you are upgrading from NetSight 7.1, you must first upgrade to the latest Extreme Management Center 8.1 release, then upgrade to the latest Extreme Management Center 8.2 or 8.3 release, then to 8.4.3.
4. Installation, Upgrade, and Configuration Changes 4.2.1 License Renewal Upgrading to Extreme Management Center version 8.4 requires you to renew your NMS license if generated prior to November 24, 2019. Licenses generated prior to November 24, 2019 expire 90 days after upgrading to Extreme Management Center version 8.4. 4.2.2 Upgrading Hardware When attempting to upgrade the Extreme Management Center server, the ExtremeAnalytics engine, or the ExtremeControl engine to version 8.4.
4. Installation, Upgrade, and Configuration Changes 4.3 ExtremeAnalytics Upgrade Information Enabling or disabling the disk flow export feature might cause enforce operations to time out. Enforcing again resolves the issue. When you delete an ExtremeXOS device that is configured as a flow source via the Flow Sources table of the Analytics > Configuration > Engines > Configuration tab from the Devices list on the Network > Devices tab, an error message is generated in the server.log.
4. Installation, Upgrade, and Configuration Changes In addition, if your ExtremeControl solution utilizes a Nessus assessment server, upgrade your assessment agent adapter to version 8.4.3 if you upgrade to the ExtremeControl engine 8.4.3. Version 8.4.3 of the assessment agent adapter requires an operating system with a 64-bit architecture. 4.4.2 ExtremeControl Version 8.0 and later Beginning in version 8.
4. Installation, Upgrade, and Configuration Changes 4.5 Fabric Configuration Information 4.5.1 Certificate Fabric Manager might be unavailable via Extreme Management Center after upgrading if the certificate is missing in Extreme Management Center Trust store. To ensure Fabric Manager is available, enter the Fabric Manager certificate in the Extreme Management Center Trust store using Generate Certificate option. 4.5.
4. Installation, Upgrade, and Configuration Changes 4.5.5 Gateway Address Configuration Change In versions of Extreme Management Center prior to 8.4.3, the Default Gateway IP Address is configured as part of the VLAN. In 8.4, the Default Gateway IP Address is configured as part of the VRF. When enforcing VRFs to a device after upgrading to version 8.4, merge any Default Gateway IP Addresses from the device into the configuration of Extreme Management Center to prevent incorrect configuration of the device.
4. Installation, Upgrade, and Configuration Changes 4.6 Device Configuration Information 4.6.1 VDX Device Configuration To properly discover interfaces and links for VDX devices in Extreme Management Center, enable three-tuple-if on the device. NOTE: To enable three-tuple-if on the device in Extreme Management Center: 1. Access the Network > Devices tab. 2. Right-click on the device in the Devices table. 3. Select Tasks > Config > VDX Config Basic Support.
4. Installation, Upgrade, and Configuration Changes The Status of LAG links in maps will start working after the next polling following an upgrade to Extreme Management Center version 8.4. You can initiate the polling of a device by performing a refresh/rediscovery of the device. 4.6.3 ERS Device Configuration ERS devices might automatically change VLAN configurations you define in Extreme Management Center.
4. Installation, Upgrade, and Configuration Changes 4.6.5 ExtremeXOS Device Configuration ExtremeXOS devices on which firmware version 30.3.1.6 is installed do not download and install new firmware versions successfully via the ZTP+ process. To correct the issue, access the Network > Firmware tab in Extreme Management Center, select the ExtremeXOS device you are updating via ZTP+, and change the Version field in the Details right-panel from builds/xos_ 30.3/30.3.1.6 to 30.3.1.6. 4.
5. System Requirements 4.8 ExtremeWireless Upgrade Information An ExtremeWireless High Availability pair cannot be added as a flow source if the WLAN(s) selected are not in common with both wireless controllers. Following a Wireless Manager upgrade, clear the Java Cache before starting the Extreme Management Center client. 5. System Requirements IMPORTANT: Extreme Management Center version 8.4.3 only runs on a 64-bit engine image.
5. System Requirements 5.1.2 Extreme Management Center Client Requirements These are the operating system requirements for remote Extreme Management Center client machines. Manufacturer Operating System Windows (qualified on the English version of the operating systems) Windows ® 10 Linux Red Hat Enterprise Linux WS and ES v6 and v7 Ubuntu 18.04 Mac OS X ® El Capitan Sierra 5.
5. System Requirements IMPORTANT: For optimal performance the CPU and Memory needs to reserved in the ESX Client and the virtual machine needs to be deployed using Thick Disk provisioning. 5.2.2 Extreme Management Center Client Requirements Specifications Requirements CPU Speed 3.
5.
5. System Requirements Specifications Small Medium Enterprise Memory 12 GB 32 GB 64 GB Disk Size 40 GB 480 GB 960 GB IOPS 200 10,000 10,000 Flows Per Minute 250,000 500,000 750,000 End-Systems 10,000 20,000 30,000 Recommended scale based on server configuration: IMPORTANT: The ESXi free license supports a maximum of 8 CPU cores, and the medium and enterprise ExtremeAnalytics virtual engine installations require 16 CPU cores.
5. System Requirements Manufacturer Operating System Operating System Disk Space Available/Real Memory Windows 1 Windows Vista Windows XP Windows 2008 Windows 2003 Windows 7 Windows 8 Windows 8.
5. System Requirements Medium Browser Version Desktop Microsoft Edge Microsoft Internet Explorer Mozilla Firefox Google Chrome 41 and later 11 and later 34 and later 33.0 and later Mobile Internet Explorer Mobile Microsoft Edge Microsoft Windows 10 Touch Screen Native (Surface Tablet) iOS Native Android Chrome Android Native Dolphin Opera 11 and later (Windows Phone) All versions N/A 9 and later 4.0 and later 4.
5. System Requirements 5.6 ExtremeControl Engine Version Requirements For complete information on ExtremeControl engine version requirements, see the Extreme Management Center Version 8.4 Release Notes section of these Release Notes. 5.7 ExtremeControl VPN Integration Requirements VPN concentrators are supported for use in ExtremeControl VPN deployment scenarios.
5. System Requirements Cingular Metro PCS Rogers (Canada) US Cellular Verizon Virgin Mobile (US and Canada) 5.10 ExtremeAnalytics Requirements To use an ExtremeSwitching X440-G2 switch as an Application Telemetry source for ExtremeAnalytics, install firmware version 22.4.1.4-patch2-5 or higher. 5.11 Ekahau Maps Requirements Extreme Management Center supports importing Ekahau version 8.x maps in .ZIP format. 5.12 Guest and IoT Manager Requirements 5.12.
5. System Requirements 5.12.3 Guest and IoT Manager Virtual Engine Requirements The VMWare Guest and IoT Manager virtual engines are packaged in the .OVA file format (defined by VMware) and needs an x86, 64-bit capable environment Specifications Minimum Recommended Total CPU Cores 2 4 Memory 2 GB 4 GB Disk Size 80 GB 80 GB Interfaces 1 Physical NIC 3 Physical NICs 5.12.
6. Getting Help cases. This is only applicable for Microsoft Edge and Microsoft Internet Explorer browsers. 6. Getting Help If you require assistance, contact Extreme Networks using one of the following methods: Extreme Portal Search the GTAC (Global Technical Assistance Center) knowledge base, manage support cases and service contracts, download software, and obtain product licensing, training, and certifications.