Cisco SG300-10 10-Port Gigabit Managed Switch Release Notes

Release Notes

Release Notes for 200, 300, 500, and ESW2

Series Switches Software Version 1.4.1.03

May 2015

These Release Notes describe the recommended practices and known issues that apply to software version 1.4.1.03 for the products listed in the table below.

Model

SF200-24

SF200-24P

SF200-48

SF200-48P

SG200-18

SG200-26

Description

24-Port 10/100 Smart Switch

24-Port 10/100 PoE Smart Switch

48-Port 10/100 Smart Switch

48-Port 10/100 PoE Smart Switch

18-port Gigabit Smart Switch


Ports

e1-e24, g1-g2 e1-e24, g1-g2 e1-e48, g1-g2 e1-e48, g1-g2 g1-g18 g1-g26

SG200-26P

SG200-50

SG200-50P

SG300-10

26-port Gigabit PoE Smart Switch


50-port Gigabit PoE Smart Switch

10-port Gigabit Managed Switch g1-g26 g1-g50 g1-g50 g1-g10

SG300-10MP 10-port Gigabit PoE Managed Switch g1-g10

SG300-10MPP 10-Port Gigabit PoE+ Managed Switch g1-g10

SG300-10SFP 10-port Gigabit PoE Managed Switch 8 SFP + 2 Combo slots

SG300-10P 10-port Gigabit PoE Managed Switch g1-g10

SG300-10PP 10-Port Gigabit PoE+ Managed Switch g1-g10

Release Notes for 200, 300, 500, and ESW2 Series Switches Firmware Version 1.4.1.03

1

2

Release Notes

Model

SG300-20

SG300-28

SG300-28P

SG300-28PP

Description

20-port Gigabit Managed Switch


Ports

g1-g20 g1-g28

28-port Gigabit PoE Managed Switch g1-g28

28-Port Gigabit PoE+ Managed Switch g1-g28

SG300-28MP 28-port Gigabit Max PoE Managed

Switch g1-g28

SG300-28SFP 28-port Gigabit SFP Managed Switch g1-g24, g25-g28

4 Gigabit Ethernet (2 combo* Gigabit

Ethernet + 2 1GE/5GE SFP)

SG300-52

SG300-52P

SG300-52MP


52-port Gigabit PoE Managed Switch

52-port Gigabit Max PoE Managed

Switch g1-g52 g1-g52 g1-g52

SF300-08

SF302-08

SF302-08MP

SF302-08P

SF302-08PP 8-Port 10/100 PoE+ Managed Switch

SF302-08MPP 8-Port 10/100 PoE+ Managed Switch

SF300-24

SF300-24P

SF300-24MP

24-port 10/100 Managed Switch

24-port 10/100 PoE Managed Switch

24-port 10/100 Max PoE Managed

Switch

SF300-24PP

SF300-48




8-port 10/100 PoE Managed Switch e1-e8 e1-e8, g1-g2 e1-e8, g1-g2 e1-e8, g1-g2 e1-e8, g1-g2 e1-e8, g1-g2 e1-e24, g1-g4 e1-e24, g1-g4 e1-e24, g1-g4

24-Port 10/100 PoE+ Managed Switch e1-e24, g1-g4

48-port 10/100 Managed Switch e1-e48, g1-g4


Release Notes

Model

SF300-48P

SF300-48PP

SF500-24

SF500-24P

SF500-24MP

SF500-48

SF500-48P

SF500-48MP

SG500-28

SG500-28P

Description


Ports

e1-e48, g1-g4

48-Port 10/100 PoE+ Managed Switch e1-e48, g1-g4

24-port 10/100 Stackable Managed

Switch

24-port 10/100 PoE Stackable

Managed Switch

24-port 10/100 PoE+ Stackable

Managed Switch with 4-port GE e1-e24, g1-g4


Ethernet + 2 1GE/5GE SFP) e1-e24, g1-g4


Ethernet + 2 1GE/5GE SFP) e1-e24, g1-g4



48-port 10/100 Stackable Managed

Switch e1-e48, g1-g4



48-port 10/100 PoE Stackable

Managed Switch e1-e48, g1-g4



48-port 10/100 PoE+ Stackable

Managed Switch with 4-port GE e1-e48, g1-g4



28-port 10/100/1000 Stackable

Managed Switch g1-g28



28-port 10/100/1000 PoE Stackable



Ethernet+ 2 1GE/5GE SFP


3

4

Release Notes

Model

SG500-52

SG500-52P

SG500-52MP

SG500X-24

SG500X-24P

SG500X-

24MPP

SG500X-48

SG500X-48P

Description

SG500-28MPP 28-port Gigabit PoE+ Stackable

Managed Switch

Ports

g1-g28


Ethernet+ 2 1GE/5GE SFP


Managed Switch




Ethernet + 2 1GE/5GE SFP) g1-g52


Ethernet+ 2 1GE/5GE SFP)

52-Port Gigabit PoE+ Stackable

Managed Switch


Managed Switch


Managed Switch

24-Port 10/100/1000 POE+ Stackable

Managed Switch with 4-Port 10G


Managed Switch




Ethernet+ 2 1GE/5GE SFP) g1-g24, xg1-xg4

4 10 Gigabit Ethernet SFP+ (1/5/10GE

SFP+ modules) g1-g24, xg1-xg4








SFP+ modules)


Release Notes

Model Description

SG500X-48MP 48-Port 10/100/1000 POE+ Stackable

Managed Switch with 4-Port 10G

SG500XG 16-Port 10-Gigabit Stackable

Managed Switch


Ports

g1-g48, xg1-xg4


SFP+ modules) xg1-xg16

16 10GE ports (8 copper ports and 8 fiber ports) + 1GE port g1-g52

ESW2-350G-

52DC

ESW2-550X-

48DC


Managed Switch g1-g48, xg1-xg4


SFP+ modules)

NOTE

*For the Sx500 Series, each combo mini-GBIC port has one 10/100/1000 copper

Ethernet port and one mini-GBIC/SFP Gigabit Ethernet slot, with one port active at a time.

TIP

As with any firmware release, please read these release notes before upgrading the firmware. Cisco also recommends backing up your configuration before any firmware upgrade.


5

6

Release Notes

Contents

Hardware Versions, page 6

Change in Flash File System, page 7

Issues Addressed in Version 1.4.1.03, page 8

Limitation and Restrictions, page 11

Where to Find Support, page 19

Hardware Versions

This firmware runs on two different versions of hardware for the 200 Series Smart

Switches, and the 300 Series Managed Switches. There is a single version of hardware for the 500 and ESW2 series switches. The number of supported MAC

Addresses, Active VLANs, and Multicast Groups will be different depending on which version of hardware you are using. Refer to the following table for details:

V1 versus V2 Hardware Total Number of MAC

Addresses

Total Number of Active

VLANs

Total Number of Multicast

Groups

Sx200 in Firmware 1.0.x

HW VID=01

8K 128 128

8K 256 256 Sx200 in Firmware 1.1.x and above.

HW VID=01

Sx200 in Firmware 1.1.x and above.

HW VID=02

Sx300 in Firmware 1.0.x

HW VID=01


HW VID=01

8K

8K

8K

256

256

256

256

256

256


Release Notes

V1 versus V2 Hardware Total Number of MAC

Addresses

Total Number of Active

VLANs

Total Number of Multicast

Groups


HW VID=02

16K 4K 1K

Sx500, SG500X and ESW2 switches have a single version of HW, see the admin guide for details.

To determine which version of hardware you are using, click Status > System

Summary. Look at the lower portion of the screen under the graphic representation of the switch for the PID VID. The descriptor will end in the VID number. The version information is also shown on the product label on the back of the switch. The PID VID is located at the bottom of the label.

Change in Flash File System

In versions 1.3.5 and later, the Flash file system has been upgraded. This has implications when upgrading from previous releases to version 1.3.5, and when downgrading from 1.3.5 or later to previous versions as described below.

Upgrading from Versions Earlier than 1.3.5

When upgrading the device from version prior to 1.3.5, you first need to upgrade the device image to image version 1.3.5 or 1.3.7 and the latest boot file (1.4.1.03).

During the first boot of the new version, the flash file system is upgraded and:

• This process takes a few minutes. “…” progress in the Console will be displayed during this process (not relevant to Sx200).

• The syslog file is deleted during this process.

• The original image file is deleted. The two images on the Flash after the upgrade will have the same version (1.3.5/1.3.7).

After the device is upgraded to 1.3.5/1.3.7, you can upgrade the device to version

1.4.1.03.


7

8

Release Notes

Boot Time when Upgrading to 1.4.1.03

This information is relevant to the following SKUs:

• SG300-52P, SG300-52MP

• SF500-24MP, SF500-48MP

• SG500X-24MP, SG500X-48MP

Software version 1.4.1.03 includes upgraded firmware to the PoE controller. The

PoE controller is upgraded automatically when the device is first booted, which makes the boot time longer (~7 minutes). During this time, the device is not responsive; however if a terminal is connected to the console port, the upgrade progress in percentage is displayed. If the upgrade process is interrupted (e.g. device is shutdown during this process), the upgrade will be restarted when the device is booted next.

Downgrading from 1.4.1.03 to Versions Earlier than 1.3.5

The downgrade copy operation process takes a few minutes, as the file system must be converted before the copy operation itself. The user is notified (using “…..” progress on CLI or a message on the WEB GUI) that the conversion process is ongoing. When the conversion process is complete, the image download begins automatically. The device will automatically reboot after the copy is complete.

When a stacking system is downgraded, only the master is downgraded, and after the master comes up again, it loads the image to the other stack members.

Powering off the device during this process might damage the file system. In such cases, booting might require connecting to the device using the console cable (not relevant to Sx200) and loading the image file using XMODEM.

After the downgrade, only downloaded image file will remain on the Flash (the

1.4.1.03 image is deleted during this process). Note that there’s no need to downgrade the boot file, the boot file supports both file systems. The boot file cannot be downgraded while version 1.4.1.03 is active.

Issues Addressed in Version 1.4.1.03

• While connected to a Catalyst 6509, an SG300 will lose the allowed VLAN configuration on the port. (CSCum86013)


Release Notes

• Not providing assigned static DHCP address. (CSCut17045)

• When telephony OUI defined on port, that port will not pass the untagged

VLAN traffic. (CSCup24125)

• Device reboots with fatal error when using URL with specified UN and PW

(multiple 1 in password). (CSCur70402)

• SG500 crashes during multiplexed SSH connection. (CSCus23114)

• When disabling HTTPS, HTTP appears disabled under system summary and TCP/UDP services. (CSCur03265)

• Adjust the threshold for Fan speed to prevent fan speed flapping frequently.

(CQ158082)

• Show inventory can't display 10G stack port or 10G uplink port on SG500x.

The 10G SFP I was using is " SFP-H10GB-CU1M". (CSCup19085)

• If client DHCP packet includes client ID option, will not allocate IP address even there is matched static allocation based on client MAC address.

(CSCup90158)

• DUT send NAK on VLAN which subnet wasn't configured as DHCP pool network. (CSCup71464)

• Upgrade of OpenSSL version from version 0.9.8r to version 1.0.1j. This version removes support for SSLv3, and supports TLS Version 1.1 and TLS version 1.2. (CCut24916, CCut24934)

Limitations and Restrictions

The following caveats are acknowledged in firmware version

1.4.1.03:

Problem:

When downloading (TFTP/HTTP) configuration to device - some commands, which were changed or deprecated before version 1.4.0.88, may not load correctly to the device.

Solution:

Issue happens only if configuration file was copied/loaded from a device running an earlier version. If needed, backup configuration file (TFTP/HTTP) to server after upgrading device to version 1.4.1.3, and user this file as backup.


9

Release Notes

Problem:

Port Settings page is not displayed correctly when using IE version 11 browser, in compatibility mode view.

Solution:

Don't use IE compatibility mode or use other supported browsers,

Firefox or Chrome.

Problem:

SNTP Authentication, Remote Log Servers, and Port and VLAN

Mirroring pages cannot be configured when using IE version 11 browser.

Solution:

Use other supported browsers, Firefox or Chrome.

Problem:

Vlan interface setting web page is not displayed correctly when using

IE version 11 browser.

Solution:

Use other supported browsers, Firefox or Chrome.

Problem:

Using Chrome on MAC OS, for example, version 39.0.2171.71 (64-bit), in WEB GUI change configuration but not save, the WEB page will shakes.

Solution:

Save configuration or use other browser, for example Firefox, IE.

The following caveats are acknowledged in firmware version

1.4.0.x:

Problem:

When Sx500 devices are connected in a ring topology, the IP mroute entry, learned through IGMP proxy, flaps. (CSCun67979)

Solution:

There is no workaround.

Problem:

VLAN1 cannot be configured as the secondary private VLAN.

(CSCup22443)

Solution:


Problem:

MLD snooping does not work for Source Specific Multicast, if IPv6 is enabled on the VLAN interface. (CSCuq13229)

Solution:

There is no workaround

Problem:

DHCP relay stops working if the DHCP relay interface IP address is reassigned. (CSCuq13199)

Solution:

Disable DHCP relay and then enable it again.

10 Release Notes for 200, 300, 500, and ESW2 Series Switches Firmware Version 1.4.1.03

Release Notes

Problem:

On Sx300 devices, the ISATAP tunnel configuration is lost after a firmware upgrade. This issue was noticed when firmware was upgraded to version

1.4.0. (CSCuq01246)

Solution:


Problem:

On Sx500 devices, the ISATAP tunnel type changes to Manual after the firmware upgraded to version 1.4.0, if the tunnel source is IP address or a physical port. (CSCuq01297)

Solution:


Problem:

After restart, the device is unable to send trap notifications to notification recipients, if the notification version is SNMPv2. (CSCuq00828)

Solution:


Problem:

LAG member port flaps if more than 4000 VLANs are added to the LAG at a time. (CSCuq00892)

Solution:

Add fewer VLANs each time.

Problem:

The ISATAP client can send RS packets only after the tunnel interface is restarted. (CSCuq03628)

Solution:


Problem:

Users are unable to set loop back interface IPv4 address as 192.168.1.x

/24.

Solution:


Problem:

When using the 1G SFP module for the 5G or 10G stack port, such as the stack port of the SG500XG-8F8T, SG500X or Sx500 series switch, sometimes the stacking may have issues due to the limited bandwidth (1G), including packet loss and stack failure. (CSCur58273, CSCur58298)

Solution:

Use the 10G SFP+ module for both 5G and 10G stack ports.

Problem:

When using the 1G SFP module for the 5G or 10G stack port, such as the stack port of the SG500XG-8F8T, SG500X or Sx500 series switch, sometimes the stacking may have issues due to the limited bandwidth (1G), including packet loss and stack failure. (CSCur58273, CSCur58298)

Solution:

When you first remove all telephony OUI items, and then save your settings and reboot the switch, the predefined telephony OUI items cannot be deleted and all telephony OUI items will be added automatically after boot up.

(CSCuq92215)


11

Release Notes

12

Solution:

Leave at least one telephony OUI item in the table so that all other telephony OUI items can be deleted successfully.

The following caveats are acknowledged in release 1.3.7.18:

Problem:

During SF500-24MP/48MP reset, the port GS4/S4 link is up for 5 seconds. (CSCum85751)

Solution:

None.

The following caveats are carried forward from release

1.3.5.58:

Problem:

Sometimes on the SG500XG-8F8T, the 10G copper port goes up and down continuously if it is configured to a speed of 1G, and hence the Lion stack performance have Losts of around 3% of frame loss. (CQ147378, CSCuj46317)

Solution:

Configure Nikola switch ports in 1G speed to Auto-negotiation preferred master.

Problem:

When setting a new key chain for RIP using the WEB GUI, if it does not include an accept-lifetime, it does not take effect, and only Key 1 takes effect with accept-lifetime. (CQ148403, CSCuh54765)

Solution:

Use the CLI for entering the key chain, or enter both accept-lifetime and send-lifetime. Only use Key 1 with accept-lifetime.

Problem:

WRR will lose efficacy after it is configured to egress shaping rate.

(CQ146677, CSCuf82588)

Solution:

Configure the WRR again.

Problem:

When user tries to Telnet some other devices from switch, it takes a long time to logout. The user either needs to double click enter button or wait a long time to logout from the device and return to the switch. (CQ146113, CSCuj46177)

Solution:

The only option is to either double click enter key or wait for a long time to logout.

Problem:

On SG500XG-8F8T or SG500X, changing the stack mode from native to advanced-hybrid-xg causes the start-up configuration to be lost. (CQ148932,

CSCui08988)

Solution:

Backup startup-config file before changing the stack mode.


Release Notes

Problem:

When the switch is used as a DHCP server, it always assigns its IP address as default router option (option 3), even if this option is not configured in the DHCP pool. Even if any other IP address is configured, the switch will still continue to provide option 3 as the configured IP to the client. (CQ149277,

CSCui34225)

Solution:


Problem:

When the firmware is downgraded from 1.3.5.39 to 1.3.0.62, only the image for 1.3.0 exists in flash. This happens on all platforms. (CQ148803,

CSCuj46205)

Solution:

Copy the required image to flash again.

Problem:

On stacking, some WEB GUI pages respond slowly. If 8 switches are stacked and 200 devices are connected, some WEB GUI pages take more than 10 seconds to respond. (CQ137261, CSCuj46218)

Some examples of such WEB GUI pages are:

• LLDP Neighbor Information.

• VLAN Management Interface Settings

• 802.1X Port Authentication

• Quality of Service Bandwidth

• Quality of Service Egress Shaping Per Queue

Solution:

Wait until the web GUI pages respond or use CLI commands.

Problem:

On SG500XG-8F8T switches, 1000BASE-T and 100BASE-TX modes only support frame sizes up to 9000 bytes. If the 10G copper port is configured in the 1G or 100M mode, and oversized frames are sent, the port drops the link.

Shutting and then opening this port can bring up this port again. (CQ149642,

CSCuj46378)

Solution:

Limit frame size to 9000 bytes or less in 1000BASE-T mode.

Problem:

For SX500 stacking, when the stack mode is changed from native to basic hybrid using the command: stack basic-hybrid auto unit-id-auto reboot, and the stack is reloaded then restarted with the default configuration, the startup configuration file is removed. (CQ150131, CSCuj37279)

Solution:

Backup startup-config file before changing the stack mode.


13

Release Notes

14

Problem:

When the Chinese localization file is installed on the SX500 stack master from TFTP on the web GUI, and the stack cable between master and backup unit is removed, the localization file is not installed on the backup unit. If CLI is used, or if the file is copied through http, this issue is not observed. (CQ150000,

CSCuj46533)

Solution:

Use HTTP to install localization file.

Problem:

When the firmware is upgraded from 1.3.0 to 1.3.5, both firmware images (active and non active) are saved as 1.3.5 in the flash memory. (CQ148800,

CSCuj46557)

Solution:


Problem:

When multiple different class PDs are connected to SF300-48PP, sometimes two or three ports are not delivered power although there is still power budget. This happens when Consumed Power is about 324 watt (86%) or more.

(CQ147622, CSCuj46584)

Solution:


Problem:

The Stack Port LED on the System Summary page of the web GUI is inconsistent with front panel of SG500XG-8F8T. (CQ150109, CSCuj46594)

Solution:


Problem:

Users are unable to open IPv6 HTTP/HTTPS sessions on Apple Safari.

(CQ147760, CSCuj46288)

Solution:

Use Chrome or Internet Explorer.

Problem:

In switch mode although multiple default gateways can be configured through CLI, only the gateway with lowest value can be active. Hence, switches should not allow the CLI to configure multiple default gateways. (CQ147302)

Solution:

When modifying the default gateway through CLI, delete the old one first.

Problem:

Some of the pages in the web-based interface require the Java

Runtime Environment (JRE) to be installed, otherwise they may display incorrectly.

Solution:

Install the latest JRE.

Problem:

Granularity of traffic shaping on the following Uplink ports starts with

2Mbps and not with 64Kbps. When configuring traffic shaping on these ports to rates lower than 2Mbps, the actual traffic shaping rate will be 2Mbps. (CQ123397,

CQ130715, CQ133170)

• Sx200/Sx300 HW 1.0


Release Notes

• SF500 ports GE1-GE4

• SG500 ports GE-49 - GE52

• SG500X ports XG1 - XG4

Solution:

Use the specified ports when traffic shaping is not required (for example. uplink or stack ports), or when the required traffic shaping rate is at least

2Mbps.

Problem:

When the link on the SG500X ports XG1 - XG4 uplink ports comes up, the link may go up and down a few times then stabilize on the up state. (CQ135073)

Solution:


Problem:

After frequent changes of the stack topology from ring to chain and vice versa, one of the stack links might become non-operational (stuck in a state where even if the stack topology is ring, it will function as a chain). If the remaining operational stack link goes down, the stack might become non-operational.

(CQ135108)

Solution:

Wait for the stack to stabilize before changing its topology.

Problem:

Copper SFP MGBT1 is not supported as stack port due to packet loss and bad CRC. (CQ135473)

Solution:

Use Cisco approved SFPs.

Problem:

When a PoE switch is connected to another PoE switch, one of the switches overcomes the internal power supply of the other PoE switch, so the other

PoE switch cannot provide PoE power to powered devices. If the connection between these switches is removed, the switch that received power from the other switch will momentarily lose its power and reboot. (CQ135360, CQ138875)

Solution:

Disable PoE on the ports connecting the two PoE switches.

Problem:

Given a stack configuration with the stack master as unit #2. On the Port

Vlan Membership page of the web-based interface, changing the value on the

Interface Type drop-down, the drop-down returns to unit #1. The information displayed on the rest of the page belongs to the ports of the unit that was selected using the drop-down. (CQ141909)

Solution:


Problem:

The routing resource “Used number of hosts” is not displayed correctly.

This is just a display issue, there is no user impact. (CQ133802)

Solution:



15

Release Notes

16

Problem:

In Layer 3 mode, SNTP Broadcast can only be operated from the CLI.

Solution:


Problem:

The EEE operational status should become disabled when Auto

Negotiation is disabled. (CQ132106)

Solution:

When the speed on a port is 1 Gigabit, auto negotiation has no effect on the EEE functioning state.

Problem:

The Voice VLAN should be prevented from being set as Guest VLAN, and the user should receive a warning. This is not happening. (CQ132684)

Solution:

Avoid setting the Voice VLAN as guest VLAN and vice-versa.

Problem:

When the Mrouter learning mode is changed between “user defined” to

“auto” and vice-versa, the IGMP Querier election process does not start.

(CQ132805)

Solution:

Disable IGMP Snooping and re-enable again, every time the Mrouter learning mode is changed to start the Querier election process.

Problem:

Some WEB GUI pages require full version compatibility of JRE, Browser and JRE-Browser applets. For XML compatibility reasons, MSXML DLL Version 6 is required for IE browser users.

Solution:

For download and installation information, refer to the following link:

www.microsoft.com/downloads/details.aspx?FamilyID=993C0BCF-3BCF-

4009-BE21-27E85E1857B1&displaylang=en

Problem:

Notification Recipients table entry becomes un-editable with an incorrect or missing parameter. (CQ133316)

Solution:

There will be an asterisk by any values for a table entry which are incorrect. This can be caused by the deletion of users, views, etc. If any of these values are incorrect, then the entry will be un-editable. First add the missing user, view, and so on, in order to edit the entry. The delete button still works regardless of whether the values are correct or not.

Problem:

The result of cable length test for 100 meters is incorrect. It will show between 110 to 140 meters. (CQ132941)

Solution:


Problem:

The maximum number of IPv6 ACEs that can be applied on an interface is 244, not 512 as documented. The user receives the message “Cannot apply because of a lack of hardware resources.” (CQ130161)

Solution:



Release Notes

Problem:

If changing the active image with the menu CLI, the active image after reboot field is not updated. If you change the image number and reboot, then the image does change, but the display in the menu CLI is incorrect. (CQ132211)

Solution:


Problem:

When using the CLI, any time that DNS is used, the user is blocked from interacting with the CLI until the DNS lookup has completed. (CQ133234)

Solution:

The user must wait until the DNS lookup has completed before issuing another command.

Problem:

Egress rate shaping does not work as expected. Configuring egress shape on Gigabit ports or on Combo ports between 64k to 5000k, will always result in 2 Million Bits. This is resolved with the new hardware release 1.1.1.8. It still exists on HW V01. It also does not work on SG300-52/52P & SG200-52/52P switches and all uplink ports of Sx500 and SG500X. (CQ123397 and CQ130715)

Solution:


Problem:

SNTP synchronization error messages are not logged when an incorrect MD5 key leads to the loss of synchronization. (CQ132636)

Solution:

There is no workaround for broadcast messages. For Unicast servers, in the SNTP server table the status message will either say “In process” or “Down” for those servers that have failed authentication.

Problem:

PoE ports on certain Nikola switches might not power the connected powered devices (PD) when used along with Cisco IP Phone 7960 with PID=68-

0808-xx. This issue impacts the following switch models:

Switch SKUs: SG200-26P, SG200-50P, SG300-28P, SG500-28P, SG500-52P,

SG500X-24P and SG500X-48P.

Solution:

Use CAT 5 cables with 2 pair pins 1, 2, 3, and 6.

Problem:

When configuring egress shaping rates on port 1, and enable flow control on port2, the whole vlan port egress rates will be the same. Flow control uses the whole buffer management scheme. When one port is configured to FC

ALL ports are applied by the new scheme. QoS function on other ports will be effected also. (CQ144583)

Solution:

When using QoS, disable the flow control function.

Problem:

When managing a switch through the web-based interface, the loading time on some of the web pages can take a long time, approximately 3-10 seconds depending on the content in the tab. (CQ143850)

Solution:

Use the command line interface instead.


17

Release Notes

18

Problem:

When managing stacking switches through the web-based interface, the loading time on the following web pages is more than 10 seconds: (CQ143851)

• Status and Statistics

• Port Management

• VLAN Management

• Access Control

• Quality of Service

Solution:

Use the command line interface instead.

Problem:

If you modify an IPv6 tunnel configuration, the change will not take effect until you perform a shut then no shut on the tunnel interface. (CQ146071)

Solution:

You must perform a shut then no shut the tunnel interface for it to take effect.

Problem:

When a 10G DAC (Direct Attached Cable) is connected to the copper port of the SG500 using the last two ports (combo ports), the fiber link status display might be up even when the link is not active.

Solution:


Problem:

When enabling IPv6 unicast-routing, the interface cannot get an ipv6 address via auto-config. (CQ146156)

Solution:

Configure the interface using a static IPv6 address.

Japanese language files and firmware version compatibility guideline

Users will see a mismatch in the features between the English language and the

Japanese language when running certain combinations of firmware and language files. Users will see new features added since version 1.1.1.6 in English instead of

Japanese in the GUI when running firmware version 1.1.2.0 and higher subject to the following restriction:

• Japanese language files version 1.1.1.6 and older are forward compatible up to Firmware version 1.1.2.0. For example: loading a version 1.1.1.6 language file onto a device running firmware version 1.2.7.76 and up will fail.

• Japanese language files version 1.1.1.10 and newer are only compatible with firmware version 1.2.7.76 and newer.


Release Notes

Where to Find Support

For current support information, visit the following URLs: www.cisco.com/cisco/web/solutions/small_business/products/ routers_switches/500_series_switches/index.html

www.cisco.com/cisco/web/solutions/small_business/products/ routers_switches/300_series_switches/index.html

www.cisco.com/cisco/web/solutions/small_business/products/ routers_switches/200_series_switches/index.html

www.cisco.com/go/smallbizsupport

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence,

Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar,

Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP,

CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press,

Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without

Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare,

GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo,

LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers,

Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare,

SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet

Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)

Copyright © 2014


19

Cisco SG300-10 10-Port Gigabit Managed Switch Release Notes

Assistant Bot

Release Notes for 200, 300, 500, and ESW2

Series Switches Software Version 1.4.1.03

Contents

Hardware Versions

Change in Flash File System

Issues Addressed in Version 1.4.1.03

Limitations and Restrictions

Where to Find Support

Frequently Answers and Questions

What is the default IP address for the web interface?

How many VLANs can be created?

What is the maximum number of MAC addresses that can be learned?

How many IGMP groups are supported?

What is the maximum number of ACLs that can be configured?

Related manuals

Cisco SG300-10 10-Port Gigabit Managed Switch Release Notes

Assistant Bot

Release Notes for 200, 300, 500, and ESW2

Series Switches Software Version 1.4.1.03

Contents

Hardware Versions

Change in Flash File System

Issues Addressed in Version 1.4.1.03

Limitations and Restrictions

Where to Find Support

Frequently Answers and Questions

What is the default IP address for the web interface?

How many VLANs can be created?

What is the maximum number of MAC addresses that can be learned?

How many IGMP groups are supported?

What is the maximum number of ACLs that can be configured?

Related manuals

Cisco

SG500-52MP 52-port Gigabit Max PoE+ Stackable Managed

Cisco

SF302-08PP 8-port 10 100 PoE+ Managed

Cisco

500 Series Stackable Managed Switches

Cisco

ESW2-550X-48DC Advanced Managed Switch

Cisco

500 SG500-28

Cisco

SG500-52MP

Cisco Systems

SG50028PK9NA

Cisco

500 Series Sx500

Cisco

Small Business 500 Series Stackable Managed Switches

Cisco

Small Business 500 Series Stackable Managed Switches

Cisco Systems

500

SignaMax

I-300 8 Port Industrial Gigabit Managed Switch