100 Innovative Way- Suite 3322 Nashua, NH Tel PLEX (7539) Plexxi Release Notes

Transcription

1 100 Innovative Way- Suite 3322 Nashua, NH Tel PLEX (7539) Plexxi Release Notes Release March 30, 2016

2 Introduction This document contains information about the Plexxi release, which delivers software updates for both Plexxi Switch and Plexxi Control. Software Versions Included The following versions of software updates are included: Plexxi Switch Plexxi Control Supported Hardware Plexxi Switch release is supported on the following hardware: Switch 1 (PX-S1) Switch 1x (PX-S1X) Switch 2 (PX-S2) Switch 2s (PX-S2S) Switch 2p (PX-S2P) Switch 2sp (PX-S2SP) Switch 2e (PX-S2E) New in this Release List of new features: Switch 2e DCI Mode Replication Paths PlexxiControl Read-Only User Plexxi Terminal User-Defined Transceiver Names and Descriptions Extended SNMP MIB Support The following sections describe these new features.

3 Switch 2e DCI mode The Switch 2e DCI (Data Center Interconnect) mode remaps the front panel ports used for Plexxi fabric uplinks from the 6 QSFP ports to the rightmost 24 SFP+ ports. The use of SFP+ ports for data center interconnect provides simpler and more flexible cabling options. In DCI mode, the QSFP ports are used as access ports, therefore no switch capacity is lost. Operation Using CLI commands, Switch 2e QSFP ports can be remapped to SFP+ ports that can be used in DCI environments to connect data centers. This enables you to extend the Plexxi ring fabric out to multiple data centers. Normally, the QSFP interfaces (and the 10 GbE ports behind them) are uplink (fabric) ports while the SFP+ ports are access ports. To attach the Plexxi fabric to a remote data center, it may be more convenient to use SFP+ ports as uplinks. This requires that some or all of the Plexxi fabric on the switch be remapped from QSFP ports to SFP+ ports. Modes of operation Modes of Operation determine the use of the QSFP ports and the right-most 24 SFP ports in a Switch 2e. The mode used determines how the Plexxi fabric is configured on that switch and how that switch connects to switches within the local data center as well as to other data centers. Switch 2e ports can be operated in Normal mode or in DCI mode as defined in the following table: Modes Normal mode DCI mode west-east east-sfp west-sfp west-sfp-east Ports West = QSFP East = QSFP West = SFP East = QSFP West = QSFP East = SFP West = SFP East = SFP A switch in east-sfp mode, connects to its east neighbor using its west SFP ports, and it connects to its west neighbor using east QSFP ports. A switch in west-sfp mode does the exact opposite the west neighbor is connected via east SFP ports and the east neighbor is connected via west QSFP ports. Finally, a switch in west-sfp-east mode connects to both neighbors using SFP ports. Plexxi Release Notes 3

4 Confluent Ring In any Plexxi environment, a set of ports is used to provide hop-by-hop connectivity between switches to create a Plexxi ring. The set of ports providing this connectivity is placed into a Link Aggregation Group (LAG) and is referred to as the confluent ring. The confluent ring size is selectable by the user and ranges from 1 to 4 ports. The default size is 2. For the Plexxi ring to operate correctly, the confluent ring must extend through all switches. It is highly recommended that the ring is cabled in a whole fashion; i.e. the confluent ring creates a contiguous physical ring. The following table identifies the possible confluent ring ports in both Normal and DCI modes. Note that the ports used are the smallest port numbers matching the ring size. Mode WEST EAST Normal mode west-east QSFP = Q1 Ports = xp49, xp50, xp51, xp52 QSFP = Q2 Ports = xp53, xp54, xp55, xp56 east-sfp SFP = 25, 27, 29, 31 Ports = xp25, xp27, xp29, xp31 QSFP = Q2 Ports = xp53, xp54, xp55, xp56 DCI mode west-sfp QSFP = Q1 Ports = xp49, xp50, xp51, xp52 SFP = 26,28,30,32 Ports = xp26, xp28, xp30, xp32 west-sfp-east SFP = 25,27,29,31 Ports = xp25, xp27, xp29, xp31 SFP = 26,28,30,32 Ports = xp26, xp28, xp30, xp32 4 Plexxi Release Notes

5 DCI Example: 3 DCs The diagram below illustrates the confluent ring cabling required to connect three data centers. Note that up to 12 connections can be made between sites and no restrictions on port selection are made beyond the confluent ring. In this example, there are two 1G connections between DC1 and DC2, a single 10G link between DC1 and DC3, and a 1G physical link restricted to 400 MBs between DC2 and DC3. DC1 Plexxi 1 Port 25 SFP+ east-sfp Port Q1 Plexxi 2 west-sfp Port Q2 Ports 26, 28 SFP+ 1 Gb/s 10 Gb/s Plexxi Fabric Data Center (DC) DC2 SFP+ Ports 25, 27 Plexxi 3 east-sfp Port Q1 west-sfp Plexxi 4 Port Q2 SFP+ Port 26 Plexxi 5 west-sfp-east Port 25 SFP+ 400 Mb/s Port 26 SFP+ DC3 In the example, data centers DC1 and DC2 contain two Plexxi switches and DC3 just one. With two or more switches in a site, two of the switches operate in DCI mode; if more than two all but two operate in normal mode. One of the two switches is placed in east-sfp mode; the second is placed in west-sfpmode. Site DC3 s single switch is placed in west-sfp-east mode. Plexxi Release Notes 5

6 Building the example network To build the example 3-DC network, the following commands need to be issued on the switches as identified. Switch Plexxi 1 Plexxi 2 Plexxi 3 CLI Command ring redirect west-sfp ring redirect east-sfp west-speed 1G ring redirect west-sfp east-speed 1G Plexxi 4 ring redirect west-sfp east-speed 1G east-egress-rate 400 Plexxi 5 ring redirect west-sfp-east west-speed 1G west-egress-rate 400 CLI for Switch2e DCI mode To support DCI mode on Switch 2e, the ring redirect command is added to the Priv-Exec commands in the Plexxi CLI. ring redirect Syntax ring redirect (west-sfp east-sfp west-sfp-east west-east) (east-speed westspeed) (east-egress-rate west-egress-rate) Argument Description Values west-east From West to East (default). west-sfp east-sfp west-sfp-east Remaps the twelve 10GbE uplinks represented by the top 3 QSFP ports (Q1, Q3, Q5) to the last 12 SFP+ top ports (odd-numbered ports 25-47). The QSFP ports become access ports. Remaps the twelve 10GbE uplinks represented by the bottom 3 QSFP ports (Q2, Q4, Q6) to the last 12 bottom SFP+ ports (even-numbered ports 26-48). The Q2, Q4 and Q6 become access ports Remaps both west and east QSFP ports to the corresponding SFP+ ports. All QSFP ports become access ports. Also set the west and east speeds and egress rates. 6 Plexxi Release Notes

7 east-speed west-speed east-egress-rate west-egress-rate Set the line speed of the East or West confluent ring. Configure the east or west confluent ring egress shaping. Set the value of egress rate in Mbps;; it cannot be more than the line speed. 10G Set speed to 10 Gb/s. 1G Set speed to 1 Gb/s. The default is 10G. < > Set to the provisioned rate for the service = 1 Gb/s and 400 = 400 Mb/s. These commands require a value. Once set, to remove any shaping on a link, the command must be given with the full line speed as the value. Description When used on a Switch 2e, this command configures (remaps or redirects) all Switch 2e east, west, or east-and-west Plexxi fabric pathways from QSFP ports to corresponding SFP+ ports, as defined by the following mapping arguments: QSFP west port To SFP+ west ports QSFP east port To SFP+ east ports Q1 25, 27, 29, 31 Q2 26, 28, 30, 32 Q3 33, 35, 37, 39 Q4 34, 36, 38, 40 Q5 41, 43, 45, 47 Q6 42, 44, 46, 48 When you execute the ring redirect command and modify the redirect mode, the switch must be rebooted for the configuration to be updated. Changing the speed or egress shaping does not require a reboot. For example, reboot the switch as prompted when the following command is issued: ring redirect west-sfp The ring engagement mode is being changed. This will cause a reboot. You want to reboot? (y/n)y Note that a reboot is required only when changing the ring engagement mode. Changing speed and/or egress rate for a switch using the current engagement mode will take effect immediately. For example, to change the speed and egress shaping on a switch currently in west-sfp enter the following command. ring redirect west-sfp east-speed 1G east-egress-rate 400 A reboot is not required. Plexxi Release Notes 7

8 Switch 2e front panel ports The following figure shows the Switch 2e front panel QSFP and SFP ports and identifies ports used for redirection from QSFP to SFP. Switch 2e SFP+ ports Upper = Odd ports 1-23 Lower = Even ports 2-24 Access ports SFP+ ports Upper = Odd ports Lower = Even ports Normal mode: Access ports DCI mode: half or all ports become Uplink ports. QSFP ports Upper = Q1, Q3, Q5 Lower = Q2, Q4, Q6 Normal mode: Uplink ports DCI mode: half or all ports become Access ports. Q1 = ports Q2 = ports Q3 = ports Q4 = ports Q5 = ports Q6 = ports Plexxi Release Notes

9 Replication Paths The Plexxi optical fabric supports configurable point-to-point and point-to-multipoint L1 optical paths that can be used to efficiently carry unicast, multicast and broadcast traffic at extremely low latencies. The replication feature enables users to provision a point-to-multipoint optical distribution tree between switches that can carry a 10G stream of traffic from a single source to multiple destinations within a Plexxi-enabled data center. For each switch along a replication path, the user can select L1 or L2 egress points (i.e. Flexx ports or access ports, respectively). Configuring replication Configure replication using Plexxi Control as follows: IMPORTANT: When creating an L1 replication path with ingress or egress ports on a Switch 2s, it is important to realize that you are changing an access port to a Flexx port and detaching it from the internal switching element. It is recommended that you remove current configurations on those ports - e.g. VLAN assignments or LAG membership - before creating the replicated path. Failure to do so may result in unexpected alarms and/or dormant configuration in the system. 1. Open and log into Plexxi Control. 2. Select the Configuration tab. 3. Select Replication Paths from the left side menu. 4. Click Edit, in the upper right corner of the window. Plexxi Release Notes 9

10 5. Name the path to be created. In the Path field, enter a path identifier name (for example, Replication_2) and click Add. The path will appear in the Results column below the Path input field. 6. Configure the ingress switch: a) In the Path Settings section, click the Add button. b) In the popup window, activate the Plexxi Switch drop-down and select the ingress switch: c) Select the ingress port (for example, 56) by clicking on the appropriate port; a checkmark appears in the selected port. The ingress port must be a Flexx port. d) Click OK. 10 Plexxi Release Notes

11 7. Link State Port. Configuring the Link State Port selects the internal switching element port which provides the Link State signal to the ingress endpoint. The ingress endpoint requires link information provided through the Link State Port. In most cases, including replication on a Switch 2s or for any replication that traverses multiple switches, the system automatically selects the Link State Port. On a Switch 2, Flexx ports are not connected to an internal switch element until configured. If you are configuring replication paths that span a single switch and if the switch is a Plexxi Switch 2, you need to manually select the Link State Port. Select the Link State Port from the drop-down located in Path Destination Settings. 8. Select the Egress Ports. As you add switches, you can add egress ports to each switch by clicking on the appropriate ports in the front panel view, so that a checkmark appears in that port. Both Flexx ports and access ports are selectable. The type of egress port determines the end-to-end latency for the replicated stream. Selecting a Flexx port allows L1 replication along the entire path with the lowest possible latency. Selecting an access port incurs a single switching hop resulting in higher latency. 9. Add switches. If the replication will traverse multiple switches, for each additional switch: a) Use the Plexxi Switch drop-down to select the switch to add. Only switches with direct links to existing switches in the path will be selectable. The Add button will become active. Plexxi Release Notes 11

12 b) Click Add. c) Select the Ingress from Switch. Any switch already in the path with a direct peer link to the added switch is available as the replication point. Your selection should be based on the number of peering links available and the projected inter-switch traffic. d) For the Peer Link, either accept the default or select one of the listed peer links. For example, East1.11 -> West1.11. Note: Note: An * next to a peer link indicates that the link was previously selected as a peer link in the for a replication in the reverse direction, and is now the preferred peer link for the new replication. For example, this might occur if: a replication from Switch_1 to Switch_2 uses peer link West1.3 -> East1.3, and you are now configuring a new replication from Switch_2 to Switch_1 (reverse direction), the preferred peer link will be *East1. 3 -> West1.3, labeled with the *. This is the preferred peer link for the new replication. The peer link that you select determines which port is used as the ingress port for the switch you are adding. e) In the switch front panel view, select the egress ports on that switch. For example, ports 9, 10, 61 and 62. f) Repeat these steps for each switch to add. 10. To apply and save the new replication, click Apply in the upper right corner of the replication window. 12 Plexxi Release Notes

13 Replication Examples This section defines two sample L1 replications within a Plexxi ring containing six Plexxi2 switches. The switches are named Plexxi 1 through Plexxi 6. Switch Plexxi 3 contains a replication that does not traverse to other switches, named Replication_1. Another replication, Replication_2, is a multipleswitch replication that traverses 4 switches (Plexxi 1 and Plexxi 4 Plexxi 6). The following sections show how these replications appear in Plexxi Control. Plexxi Release Notes 13

14 Example: Replication through a Single Plexxi Switch In this example, named Replication_1, the replication path remains on a single Plexxi switch (Plexxi 3) and replicates to four endpoints. Two endpoints are premium service (out ports 65 and 67 which are Flexx ports for L1 replication) and two are standard service (ports 9 and 10 which are access ports for L2 replication). The Link State Port is port xp Plexxi Release Notes

15 Example: Replication through Multiple Plexxi Switches This example, named Replication_2, traverses four Plexxi switches and replicates to 16 endpoints. The replication path ingresses through Plexxi 1 which distributes the replication to 4 endpoints and forwards it to switches Plexxi 4 and Plexxi 6. Plexxi 4 distributes the replication to 4 endpoints. Plexxi 6 distributes the replication to 4 endpoints and forwards it to Plexxi 5, which distributes the replication to four endpoints. The switch configurations are shown in the following Plexxi Control sample screens. Plexxi Release Notes 15

16 Switch Plexxi_1 Plexxi 1 is the ingress switch for Replication_2. Port 65 is selected as the Ingress Port. It appears greyed out in the figure because it is not selectable as an egress port. The Link State Port xp70 is automatically selected. Plexxi_1 provides replication to switches Plexxi_4 and Plexxi_6. Plexxi 1 replicates endpoint paths through access ports 25 and 26 and Flexx ports 73 and 75. Switch Plexxi_4 The replication path to Plexxi_4 exits through East1.11 and enters Plexxi_4 through West1.11. The replication endpoint paths egress through Flexx ports 61 and 62 and access ports 9 and 10. Switch Plexxi_6 16 Plexxi Release Notes

17 Plexxi_6 receives the replicated stream from Plexxi_1 and provides replication to switch Plexxi_5. The replication endpoint paths egress through access ports 25 and 26 and Flexx ports 73 and 75. Switch Plexxi_5 The replication ingress is through East1.3, The replication endpoint paths egress through Flexx ports Plexxi Release Notes 17

18 Viewing Replication Paths To view replication paths, select Configuration > Replication Paths. All configured replication paths are shown. For example: Removing a Replication Path To Remove a Replication Path: 1. In Plexxi Control, click Replication Paths. 2. Click Edit. 3. Select the path to delete, then click REMOVE. 4. Respond to the confirmation message. The path will be removed. 18 Plexxi Release Notes

19 Removing a Switch from a Replication Path To Remove a switch from a Replication Path: 1. In Plexxi Control, click Replication Paths. 2. Click Edit. 3. Select the path. 4. Select the switch to remove from the path. Wait for the data to load. 5. Click Remove. The path is removed; you will not be prompted to confirm the change. 6. Click Apply to apply the change. Plexxi Release Notes 19

20 Plexxi Control Read-Only User For Plexxi Control user administration, the release adds a Read-Only role so that the following user roles are now available: Administrator, Operator, and Read-Only. To open a window to create and manage users, in the header, select the Operations icon > Configure > Users: The following windows illustrate the new read-only user: Read-Only users can view items in Plexxi Control, however, they are unable to create, delete, manage or edit any operation in Plexxi Control. Also, Read-Only users are allowed to edit their own profile information (password, , icon, description), however, they can NOT change their own roles or delete any user, including themselves. If a user logs into Plexxi Control as Read-Only, a pop-up window indicates the Read-Only status. 20 Plexxi Release Notes

21 Also, in Plexxi Control, the user icon for a read-only user changes to a padlock: An Administrator or Operator has a user icon such as this default icon: Plexxi Release Notes 21

22 Launching Terminals from Plexxi Control In release 2.2.1, you can launch an SSH session, a Python shell or a Jython shell directly from Plexxi Control in a browser to any switch in the Plexxi network. In Plexxi Control, you can now launch shells from: The selection panel on the Networks tab, The Switch Details window for the selected switch, The Plexxi Control header, The Terminal Launch window which appears when you exit or quit any shell. Launching Terminals from the Networks tab You can launch an SSH session from the left-hand selection panel on the Networks tab in Plexxi Control as follows: 1. In Plexxi Control, select the Networks tab. 2. On the Networks tab, select the switch to connect to. In the left-hand panel, Launch SSH will activate. 3. Click Launch SSH to open the SSH session on the selected switch. 4. Log into the SSH session. 22 Plexxi Release Notes

23 Launching Terminals from the Switch Details Window From Plexxi Control, an SSH session or shell can be launched from the Plexxi switch details window for any Plexxi switch in the Plexxi network. To open an SSH session for a specific switch: 1. In Plexxi Control, on the Dashboard tab, in Health & Inventory, click the switch count (i.e. 16) to show the switches. 2. In the Show Switches window, click a switch s Status field to open the details for the switch: Plexxi Release Notes 23

24 3. In the Plexxi Switch details window, click Launch SSH to open an SSH session on that switch. 4. Log into the SSH session. Launching Terminals from the Plexxi Control Header You can launch an SSH session, a Python shell or a Jython shell from the Plexxi Control header. Note: Note: To log into a specific switch, you must have the hostname, IP address or SSH URL for the switch. The Python shell and Jython shell are for advanced users only. 1. In Plexxi Control, select the Tools icon > Plexxi Terminal > Launch SSH. 2. Enter the hostname, IP address or SSH URL for the switch. For example: ssh:// :22 3. Log into the switch. 24 Plexxi Release Notes

25 Launching Terminals from the Terminal Launch window When you exit a terminal session, a terminal launch window is created. You can then re-launch the SSH session, a Jython shell or a Python shell from the Terminal Launch window. Note: The Python shell and Jython shell are for advanced users only. Plexxi Release Notes 25

26 User-Defined Transceiver Names and Descriptions This feature enables the network administrator to assign transceiver names and descriptions to switch front panel access port and fabric port transceivers using Plexxi Control. Transceiver port names and descriptions are helpful when troubleshooting network connectivity issues. Assigning Transceiver Names and Descriptions To assign names and descriptions to front-panel transceiver ports: 1. Open Plexxi Control. 2. On the Dashboard, in the Health & Inventory panel, click the active switches # to open the Switch Status window. 3. Open the Details window for the appropriate switch. 4. Click Ports to Open the front panel view for the switch. 5. Click on the port # for the transceiver to be named. If you hover over the number for a port that has not been named, it will appear as follows: If you hover over the number for a port that has been named, it will appear as follows: 6. In the pop-up window, enter the transceiver name and description and then click OK. 7. Repeat these steps as needed to name and describe other transceivers. 26 Plexxi Release Notes

27 Viewing Transceiver Names and Descriptions Assigned transceiver names and descriptions appear: when hovering over a port number in PlexxiControl, with listed switch port information in PlexxiControl, in some Plexxi CLI show commands, and in some SNMP tables As described in the following sections. PlexxiControl: Hovering over a port number If you hover over the number for a port that has been named, the port name and description will appear as follows: PlexxiControl: With Listed Switch Port Information if a switch port is attached to a named transceiver/physical port, any time the switch port information is displayed, the associated transceiver name is also listed. For example for port 5: PlexxiCLI: Returned by some show commands Transceiver names and descriptions are returned for the following show commands in the Plexxi CLI: show interface show interface <IFACE> show interface statistics show interface <IFACE> statistics show transceivers show transceivers <NAME> show lag show fsat show psat show vlan SNMP Transceiver names and descriptions are provided for SNMP when transceivers are mapped to switch fabric ports. Plexxi Release Notes 27

28 Extended SNMP MIB Support Release extends SNMP MIB support. New MIB Table support The following additional MIB tables are supported in 2.2.1: ipforwarding (RFC4292) dot3statsduplexstatus (RFC3635) dot1qvlancurrenttable (RFC4363) dot1dtpfdbtable (RFC4188) dot1dbaseporttable (RFC4188) lldpcachetable (also known as lldpremtable) lldpaddrecachetable (also known as lldpremmanaddrtable) 28 Plexxi Release Notes

29 Plexxi Control Help Viewing Plexxi Control Help in Google Chrome might not render some pages While viewing Plexxi Control Help in a Google Chrome browser, if a page does not render when you select it from the Contents, try any of the following workarounds to render the page: Resize the browser window. Click the arrow to hide the table of contents listing, Click the icon in the upper right to convert to frames view. Plexxi Release Notes 29

30 Issues Fixed in this Release Issue ID Description PXAP-7340 Fixed an issue where upgrading switches from sp1 to could result in lost communication between the switches and PlexxiControl. PXCTL-1132 Fixed an issue where, following upgrade from to 2.2.0, LAG groups cannot be configured. After adding a LAG group name, selecting a switch, and clicking Add, the tool freezes and sits at the spinner. PXCTL-1151 Fixed an issue where the Network view in Plexxi Control may not display all configured connections between switches. PXCTL-1193 Fixed an issue where an erroneous alarm for "All uplinks out of service" could be generated. PXPF-824 Fixed an issue where transceiver temperature alarms were erroneously generated in a Switch 2/2s/2sp/2p with reverse fan airflow. The transceiver temperature alarm threshold was too low;; the reverse airflow caused the temperature to rise above the threshold even though the transceiver temperatures were within an acceptable range. PXSW-101 Fixed an issue that prevented the CPU Temperature from displaying for some switches in the switch Stats (statistics) window in Plexxi Control. PXSW-106 Fixed an issue where traffic could be dropped after removing a port from an MLAG. PXSW-172 Fixed an issue that, after a ring reboot, ARP broadcasts were not delivered to all switches in a ring. PXSW-174 Fixed an issue where the source port number and ingress port number did not match in sflow reports, potentially causing compatibility issues with collectors. PXSW-177 Fixed an issue where some switches repeatedly report VLAN errors in /var/log/messages. PXSW-179 Fixed an issue where a MAC address learned on an MLAG attachment is not updated in all cases where the endpoint moves. PXSW-217 Fixed an issue where Active FSAT entries are not successfully added to the hardware forwarding tables. PXSW-249 Fixed an issue where the P2 table is inconsistent when two rings are combined into one ring. 30 Plexxi Release Notes

31 Issue ID Description PXSW-308 Fixed an issue where, on a VLAN with COS 1, multicast packets with IGMP snooping learned the destination MAC egress with COS 4 on remote switches. Packets egress the remote switch with COS 4 and the local switch with COS 1. PXSW-478 Fixed an issue in an MLAG to MLAG scenario where FSAT entries were MAC invalidated. FSAT S are now validated on all switches that are members of an MLAG. PXSW-636 Fixed an issue where removing one port from the confluent ring LAG incorrectly removed both peers. PXSW-650 Fixed an issue where parity error messages are returned through the switch debug shell. These errors affected VLAN statistics. PXSW-772 Fixed an issue where interface counters on peering ports between switch 2SP and switch 2E contain invalid counts. PXSW-773 Fixed an issue where the shell command show mac sw-table verbose fails and returns an error. PXSW-793 Fixed an issue where the shell command traceattachment info MAC VLAN did not work correctly. PXSW-800 Fixed an issue where processing invalid ping commands led to lost resources and an eventual switch crash. PXSW-801 PXSW-826 Fixed issues where mis-cabling switches (east to east instead of east to west) resulted in inconsistent MAC address between switches in the ring. PXSW-842 Fixed an issue where the loss of peering on one port in a LAG results in the entire LAG being blocked. PXUI-1939 Fixed an issue where, following an upgrade of Plexxi Control from to 2.2.0, individually assigned and correctly provisioned VLANs do not display in the Configuration > VLANs > Assignments window in Plexxi Control. PXUI-2104 Fixed an issue where an attempt to display a large range of VLANs on the VLAN assignment configuration page resulted in an error. PXUI-2116 Fixed an issue where, in Plexxi Control, Applying a VLAN range from the Configuration > VLANs > Assignments > Edit window causes Plexxi Control to have a long delay or become unresponsive. Plexxi Release Notes 31

32 Known Issues in this Release Issue ID Description PXCTL-1277 Link traffic indicators on the Plexxi Control UI Visualizer tab are updated in 5 minute intervals. PXSW-601 If a user disables the link state port on the ingress switch of an L1 Replication path, no link state down alarm is generated. PXUI-1812 Display issues occur in some browsers when opening more than 15 simultaneous Plexxi Terminal sessions. PXUI-1917 When a SSH session to a switch has been closed using the Close button on the right hand panel, the user will be brought back to the Plexxi Terminal page. If the user reopens a SSH session from this Plexxi Terminal page, the application will attempt to reestablish a SSH session with the original switch. PXUI-2116 When using large ranges of VLANs in the VLAN assignment screen, the UI may become sluggish or non-responsive. Plexxi recommends that you use VLAN group definitions to assign large numbers of VLANs to ports. 32 Plexxi Release Notes

33 Contact Plexxi Care Copyright Plexxi Care technical support services are available to answer your questions and to make sure your software and hardware are operating properly at all times. Contact Plexxi Care using one of the following methods: (US/Canada toll-free) (US/International) The information contained herein is subject to change without notice. Plexxi and the Plexxi logo are trademarks of Plexxi, Inc. in the United States and other countries. Other product or service name may be trademarks or service marks of others. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from Plexxi, Inc. Plexxi, Inc. provides this documentation AS IS, without warranty, term, or condition of any kind, either implied or expressed, including, but not limited to, the implied warranties, terms, or conditions of merchantability, satisfactory quality, non-infringement and fitness for a particular purpose. Plexxi, Inc. reserves the right to make changes to equipment design or program components described in this documentation, as progress in engineering, manufacturing methods, or other circumstances may warrant. No responsibility is assumed for the use of Plexxi, Inc. software or hardware, all rights, obligations and remedies related to which are as set forth in the applicable sales and license agreements. Plexxi, Inc. 100 Innovative Way - Suite 3322 Nashua, NH Tel: PLEX (7539) Published Date, March Printed in United States of America. Copyright 2016 Plexxi, Inc. All rights reserved. Plexxi Release Notes 33