Since the device is eosl. Version 15 is available for this switch. Just verify here. I hope you know the procedure to upgrade. Hi Ravindra When i checked Release notes for this version, the supported hardware list for my switch is not listed. In response to praveenrk Open a case might help you further. Thanks Ravindra. In response to pieterh. Thanks Pieterh.

One more thing to clarify.. To upgrade from 12 to 15 how much time will it take to complete the upgrade process. Around 45 minutes because of the undocumented micro-code upgrade. Each switch. But if the stack needs to do a micro-code upgrade, then the entire stack will take 45 minutes to upgrade the micro-code and IOS.

Post Reply. Latest Contents. Created by Emmanuel Tychon on AM. Cisco cellular software contains a database of well-known APNs based on the country and Created by Leo Laohoo on PM. The IT Blog Awards is now accepting submissions! Created by caiharve on PM. Any group specific query with a router alert option drops. IPv6 mld traffic causes high CPU utilization on the switch.

A phone connected to a port with EnergyWise activitycheck configured, switches off even though there is an active call. Telnet sessions that are incompletely established may not time out after a period of inactivity, leading to eventual exhaustion of available VTY lines. It needs to be manually cleared via clear tcp only clear line does not work.

The workaround is that it needs to be manually cleared via clear tcp tcb 0xXXXX only clear line does not work. The process Kron CLI Process show tech-support password redirect tftp crashes because of memory corruption. The configuration is as show below:. When rsh command constructs are used within Tclscript, Tcl fails to send the router hostname which causes the rsh command constructs to fail authorization to a remote router. An EEM script that executes on a syslog event causes the Cisco router to fail with the following error message.

Exception to IOS Thread:. It seems that the switch has picked up interface Fa1 macaddress as its engineID. FastEthernet1 is down, line protocol is down. Hardware is RP management port, address is The workaround is to manually configure snmp engineID from cli. When a 1 gig sfp is inserted in a fuller stack with sierra as master, running the sh inventory command does not display the inserted sfp details of the member switch. Topology used is stack with sierra as master and fuller as member both are 48 ports.

The Privilege commands are not appearing in the configuration of a Catalyst switch. When you enter the privilege interface level 3 switchport port-security mac-address sticky command and save the configuration, the command is not visible in neither the startup configuration nor the running configuration.

However, privilege level 3 users can view the command and can use it. If you reload the switch, the command is still is not visible in the configuration and also becomes unavailable to the privilege level 3 users.

The workaround is to use the aaa authorization global configuration command to access the commands available for a particular user from the AAA server.

The workaround is to disable https secure communication and use http for HTTP requests. On the Cisco enhanced EtherSwitch service module SM-ESP , running the logging source-interface command, does not set the source interface for syslog messages sent to a syslog server. In a Catalyst X switch stack, the switches experience a slow performance with the following message.

Sometimes the switch stops responding and is not recovered until power cycling. You may also observe the following messages when the problem occurs. Disabling linecard. Expected during linecard OIR. The issue is observed in switches running It also includes The workaround is to configure a longer logging interval. For example,. If the issue persists after setting a longer logging interval, you must power cycle the switch.

In a switch stack consisting of Catalyst S switches running This issue is observed when the number of member ports is higher than 4. The workaround is to configure the missing MAC addresses manually. A change in the behaviour of DHCP client is observed between The output is as shown:. When trying to remove the macros by running the command " no macro auto global processing ", the CPU comes back to normal but the master switch crashes.

The workaround is to reload the stack. The CPU remains low for a while. Removing the macros at this time does not cause the master switch to crash. After system reload, ip ssh source-interface shows in startup-config but disappears from.

This is seen in both the scenarios as mentioned below. When around Vlans are configured on a switch running IOS The issue is not seen on switches running IOS The workaround is to disable the device sensor as no macro auto monitor.

Designated port on the Root Bridge experiences a block forward for 30 seconds. This issue occurs because the message-time the period of time a packet is alive in the network is almost equal to max-age the period of time a packet is allowed to stay in the network. The CDP neighbor devices are discovered initially on the Gi0 interface of the AP and then after a few seconds, the neighbour devices are discovered on the main interface and the sub-interface Gi0 and Gi0.

The workaround is to disable LLDP on the switch interface. When port-security is configured on all ports and when the end host is moved, the mac address table is out of sync. When a PC with The Switch deletes running It makes authentication process fail on the machines which can only complete it in first run. The show env stack command displays the following output:. Temperature Value: 35 Degree Celsius.

Yellow Threshold : 46 Degree Celsius. Red Threshold : 60 Degree Celsius. Temperature Value: 34 Degree Celsius. This is because switch expects the packet to arrive on voice vlan from EX, but EX is sending packets on data vlan. All DHCP requests get dropped at the switch. Hence EX is not able to get the ip address. The workaround is to disable one of the following:.

Due to a timing issue, the port channel member port on the slave switch of the stack loops during boot up. The issue occurs only on the member port that is configured as the first port in a cross-stack EtherChannel configuration and when Nexus devices are connected to Cisco devices. Due to Link Aggregation Control Protocol LACP graceful convergence, when both the devices are up and in sync S state, Cisco devices start transmitting even before the devices get onto collecting C state.

This causes the port to be pulled down by the Nexus devices. When this happens during boot up, the EtherChannel hardware programming for the port is cleared even when the port is bundled in the port-channel. When a switch stack is configured in VTP client mode with VTP password, the show command for the stack master displays the VTP operating mode as client, whereas the member switches display the VTP operating mode as server.

When the interface is lost in a port channel the flow switch over to the backup link is faster for 10G uplink when compared to a 1G uplink. This is because interface state polling is faster for 10G uplink than 1G uplink.

When you reload the first switch, the auto configuration does not start. The workaround is after you configure the SVI, remove the local proxy ARP configuration by entering the no ip local-proxy-arp command, and reconfigure it by entering the ip local-proxy-arp command. A switch configured with login quiet-mode resets when you enter the login block-for or no login block-for commands. Nevertheless, to avoid a reset, do not enter the login block or no login block-for commands.

When you configure Flex Link on stacks containing interfaces from different switches, the interfaces start flapping continuously. The workaround is to remove the Flex Link configuration from the interfaces. Port-channel interface flaps while adding or removing a VLAN from the trunk on a port-channel interface if one or more port members are not in P or D states. The workaround is to configure enable secret command on an IOS device without Type 4 support, copy the resulting Type 5 password, and paste it into the appropriate command on the upgraded IOS device.

In a stack of Catalyst Switches, port security enabled ports block all the network traffic through them. Using the sh mac address-table command shows that the mac address is learned as static on the master switch, whereas the member switches do not have this mac address on their mac address table.

Configuring logging buffered [size] command with large buffer size causes the switch to experience an out of memory or low memory condition. The workaround is to reduce the logging buffer allocation using the CLI. The workaround is to use the CLI to get the correct values. The host IP address is not displayed when you run the sh auth sess int det command. The switch port goes in to the err-disabled state due to port security violations. The workaround is to run the no switchport command on the interface.

Device under test DUT fails with traceback when you enter the configure replace target-url command. In a switch stack, if a stack member is connected to a Meru access point that requires The stacked switch setup fails when you change or remove an existing password while the relayed console waits for the authentication prompt. The workaround is to reduce the number of changes to the password in the console or VTY when the relayed console waits for the authentication prompt.

The issue occurs after reloading the stack members or after online insertion and removal OIR of the transceivers that are DOM capable. When the source starts sending traffic to the multicast group, an S,G is created and some of the initial packets sent by the source are lost. Once the S,G is programmed for the traffic sent by the source, all the subsequent multicast traffic reaches the receiver. The blocked port on a Catalyst Switch, receives and forwards a malformed TCP packet thereby causing the packet to loop continuously in the network and flooding to all the ports of the VLAN.

This issue takes place only in stack configurations. The workaround is to use vrf definition command instead of ip vrf command to configure per-VRF. After performing a shut or no shut on the ports of a Catalyst Switch, the status of some of the ports are displayed as Not Connected , even if they are connected to a remote device.

The workaround is to perform a shut or no shut on the affected ports. In the switch running earlier to Cisco IOS software release The workaround is to upgrade the switch to Cisco IOS software release The switch reboots if the shutdown and no shutdown commands are repeatedly entered for the alternating ports in an 8-node Resilient Ethernet Protocol REP ring segment.

The following error message is displayed:. The workaround is to downgrade the switch to When you repeatedly run the shut and no shut command in the alternating ports on a 8 node REP ring, the stack member with REP secondary edge port drops the multicast traffic for 20 to 50 seconds. This feature, which previously showed errors, is now functioning properly.

The workaround is to reinsert the module into the switch. The workaround is to enter the shutdown command followed by the no shutdown command, which will recover the failed links. Sometimes the following log message is displayed:. The command power inline port 2x-mode was not supported on the switch. This has now been fixed. The workaround is to either disable multicast fast convergence or configure IGMP version 3 on switch virtual interface.

The workaround is to check if the displayed VLANs are internal and then to hide them. The workaround is to implement SNMP view using the following commands:. As a result, egress traffic to another router on an SSH connection is blocked. The device connected to the switch crashes when a CDP data frame is processed. The workaround is to disable CDP using the no cdp run global configuration command.

This workaround is not applicable if the connected device relies on or supports a phone or voice network. The workaround is to apply protocol filters to the device sensor output by entering the following global configuration commands:. Spurious traps observed periodically on removal of power to RPS.

STP loop occurs on Flexstack connected by parallel links when a link state is changed on Flexlink port. The workaround is to change the switch to root bridge. The traffic continues to take failed PBR path instead of the next available best path. The workaround is to delete the duplex full configuration and configure again.

If a policy map attached to the switch interface is modified then the corresponding QoS policy works incorrectly. The workaround is to delete the policy map, create a new policy map and then attach it to the interface.

This issue occurs when the WCCP cache engine is shut down and the cache is not cleared. When native VLAN is configured on the trunk or when switchport trunk native vlan 99 is configured on the interface, spanning-tree instance is not created for native VLAN. The workaround is to keep VLAN1 as a native on the trunk. To disable dot1x internally, run the no macro auto monitor command.

The stp instance is created for native vlan 99 after running the show and no show command on the interface. When a member of stack is reloaded, the uplink trunk connected to Catalyst switch becomes non-trunk causing STP issues on the switch. When a member of stack with fiber SFP uplinks is reloaded, it results in STP issues on the stack and the internal stack ports on the switch becomes the root port.

CRC errors are reportedwhen traffic is sent from the peer ports of a switch. The workaround is to remove the WCCP redirects command from the interface and then add them back on the interface. The work around is to use the egress span iso of the ingress span and span the malformed TCP packets to span destination port as there are no classification checks in the egress interface for parse fail conditions.

On the Catalyst S switch stack, when the login block command is configured and the running config is saved using the wr command on the master, it brings the master down. When the running config is saved on the new master , the following lines are displayed on entering the show running-config command.

When the secret password is configured, the password is not saved. The default password is used as the secret password. The workaround is to use the default password to login and then change the password.

This symptom is observed in Cisco IOS The known workaround is to enter the no service dhcp command if the switch is not a DHCP server and configure the device sensor as follows:. When a client fails to authenticate in the multi-auth mode, the session continues to be active indefinitely.

The workaround is to enter the clear authentication sessions privileged EXEC command to clear information for all authentication manager sessions. The down-when-looped interface configuration command is not supported with default speed or with BaseT advertisements on the gigabit medium independent interface GMII interface.

This is because the down-when-looped feature and BaseT advertisements both make use of the "next page" function as defined in IEEE Cisco has released free software updates that address this vulnerability. There are no workarounds available to mitigate this vulnerability.

The Cisco IOS Software implementation of the virtual routing and forwarding VRF aware network address translation NAT feature contains a vulnerability when translating IP packets that could allow an unauthenticated, remote attacker to cause a denial of service DoS condition. Workarounds that mitigate this vulnerability are not available. When two traps are generated by two separate processes, the switch fails if one process is suspended while the other process updates variables used by the first process.

If a redundant power supply RSP switchover occurs during a bulk configuration synchronization, some of the line configurations might disappear. The workaround is to reapply the line configurations. This restriction has been removed, and several IP addresses can now be mapped to a single MAC address. The show ip dhcp pool command displays a large number of leased addresses.

The workaround is to turn off ip dhcp remember and reload the switch. The secure copy feature copy: source-filename scp: destination-filename command does not work.

This problem occurs when the Enterprise Policy Manager EPM for a device connected to an interface is authorized in closed mode and no policies are configured or downloaded. If another device is connected to this device, restricted VLAN authentication event interface configuration command is enabled on the port.

When Catalyst switch or Catalyst is configured as a Layer 3 switch with local connected hosts, the switches drop large IPv6 traffic loads intended for local connected hosts. The workaround is to perform the following actions:. A Platform assert failure message is displayed on the switch. Traceback occurs after deleting the static mac-address table.

The workaround is to set the dynamic mac-address table and to ensure that the return value of the API that allocates SD is checked correctly.

When the ip rsvp snooping command is enabled on a Layer 2 environment, the switch stops forwarding the metadata packets. When the master switch Switch A is reloaded or loses power and rejoins the stack as a member switch, any traffic stream that exits Switch A is dropped because the newly joined member is not able to establish an Address Resolution Protocol ARP entry for the next hop router or switch.

The workaround is to add a static ARP. Local web authorization and HTTP services on the switch do not respond because of a web authorization resource limitation in the system.

These are possible workarounds and are not guaranteed to solve the problem:. The macro is applied to devices such as PCs, laptops, and printers. You do not need to configure MAC operationally unique identifier OUI -based triggers and map these triggers to a macro for these devices. The Smart Install client feature in Cisco IOS Software contains a vulnerability that could allow an unauthenticated, remote attacker to cause a denial of service DoS condition on an affected device.

Affected devices that are configured as Smart Install clients are vulnerable. There are no workarounds for devices that have the Smart Install client feature enabled. If an interface is configured with the switchport port-security maximum 1 vlan command, the following error message is displayed:.

The flash memory is corrupted when you format the flash manually. The workaround is to reload the switch. If the Performance Monitor cache is displayed using the show performance monitor cache command and you attempt to stop the command output display by entering the q keyword, there is an unusually long delay before the output is stopped.

The workaround is to enter the term len 0 privileged EXEC command so that all command outputs are displayed without any breaks. MACsec interface commands are not accepted on the switch except when you enter the sap pmk key modelist no-encap command. The device-sensor accounting global configuration command is not available.

When a Catalyst S series switch is booted up, a large number of Yeti2S88gMdioWr: Unknown status for write operation messages may be written to the console. Although the error messages may substantially increase bootup time, the switch is fully functional after Cisco IOS boots. The workaround is to power cycle the switch for a quick recovery.

This is a software issue and the switch does not require replacement. When a switchover occurs in a switch stack, the host session information is lost. The workaround is to reauthenticate all the clients. When the show epm session summary or show epm command is entered from an SSH or telnet session and another command is entered from the console, the switch might unexpectedly reset and generate crash information. The switch might occasionally reload after experiencing a CPU overload, regardless of what process is overloading the CPU.

The switch downloads the running IOS image from the TFTP server and reboots even though the same image is currently loaded and running. An attacker could exploit this vulnerability by sending a crafted request to an affected device that has the DHCP version 6 DHCPv6 server feature enabled, causing a reload.

This advisory is available at the following link:. When an interface is configured with the mls qos command, traffic is not matched by port-based QoS ACLs that use the range option. The workaround is to is to configure the switch using the single port eq keyword. Alternatively, you can configure the trust under class-default setting for the same policy-map that uses the acl-range option.

In a switch stack, you cannot establish a console session with a member switch when an ACL is applied to the VTY lines. The workaround is to use the following procedure when you apply an ACL to line vty 0 4 and line vty 5 Create the vty ACL and permit the network. Append the vrf-also keyword to the configured access-class inbound. In a switch stack, the show interface command shows incorrect values for output drops. The workaround is to use the show platform port-asic stats drops command to see the correct values.

A static route that has the next hop set to null0 is removed when the master switch is changed in a switch stack configuration. This situation occurs when the switch is stacked and the static route is advertised by the network 0. The workaround is to use the ip summary-address eigrp as-number ip-address mask command to set the IP summary aggregate address for the interface through which the next hop can be found. The Catalyst E series switch with Supervisor Engine 7L-E contains a denial of service DoS vulnerability when processing specially crafted packets that can cause a reload of the device.

When ports from each switch in a switch stack are bundled together to form an uplink port channel, Multicast VLAN Registration MVR streams are sent only to the switch with the active member in the port channel. When a device is moved from one port to another in a switch stack, the SNMP data generated for the move event is incorrect.

Users connecting to the network through a device configured for web proxy authentication may experience a web authentication failure.

Using the dot1x default command on a port disables access control on the port and resets the values of the authentication host-mode and authentication timer reauthenticate commands to the default values. The workaround is to avoid using the dot1x default command and set various dot1x parameters individually.

You can also reconfigure the parameters that were changed after you entered the dot1x default command. The workaround is to flap the ingress physical interface, the SVI, or the port channel. In a switch stack setup after you reload a member switch, a multilayer switching MLS class of service CoS configuration command with a specified value such as mls qos cos 7 on the slave switch does not function anymore.

This situation impacts untagged IP and Layer 2 packets. The workaround is to ensure that when you configure a service policy on an interface, an interface default level CoS is also configured. You can use mls trust qos cos command in interface configuration mode. Frame check sequence FCS errors occur when the switch receives jumbo frames greater than bytes on downlink ports. When using the switchport port-security maximum 1 vlan access command, if an IP-phone with a personal computer connected to it is connected to an access port with port security, a security violation will occur on the interface.

This type of message is displayed on the console:. The workaround is to remove the line switchport port-security maximum 1 vlan access. The switch does not correctly detect a loopback when the switch port on an authenticated IP phone is looped to a port configured and authenticated with dot1x security, even when bpduguard is configured on the interface.

This situation can result in percent CPU utilization and degraded switch performance. The workaround is to configure the interface with the authentication open command or to configure authentication mac-move permit on the switch.

The workaround is to save the configuration and reload the switch. Alternatively, configure the switch by entering the no macro auto monitor command followed by the macro auto monitor command after the port is bundled for the first time.

The workaround for v2 stacks is to limit the setup to 5 switches. If more then 5 switches are required in a stack, keep the number of VLANs and enabled features as low as possible. On the downlink interfaces, the switches are capable of sourcing IEEE These documents provide complete information about the Catalyst , , , S and switches and the Cisco EtherSwitch service modules and are available at Cisco.

These documents provide complete information about the Catalyst switches and the Cisco EtherSwitch service modules:. These documents provide complete information about the Catalyst switches:. These documents provide complete information about the Catalyst and S switches and are available on Cisco. For other information about related products, see these documents:. SFP compatibility matrix documents are available from this Cisco. Table 2 Catalyst Switches Supported Switch. Support Cisco FlexStack technology.

Table 4 Other Supported Hardware Switch. We recommend 1 GHz. Security Anomaly Detection by examining flows that do not traverse trust boundaries for inside the perimeter attacks. Impacts of network and application changes. Compliance conformation.

Traffic patterns for capacity planning. Enabling FNF at the access switch ensures you get all flows. The access switch is the most logical place in the network for collecting statistics and monitoring all flows.

With Netflow, you can obtain MAC-address and access port information associated with the flow, to get directly to the source of the flow. Most collectors are able to leverage the location based on MAC-address and interface port number provided by the access switch to the collector. Thus by enabling FNF at the access switch you are able to get the location information of the flow.

The access switch has a variety of identity mechanism for user authentication and adding user awareness is the natural progression that can be developed.

Access switches are an order of magnitude greater than distribution and core which makes them scale well for FNF and ensure there are no performance impacts of oversubscription at aggregation and core. Table 5 shows the cable types and supported lengths of the new Cisco 10G Base-T module. Table 5. Category 7a. Category 7. Category 6. MACsec provides MAC layer encryption over wired networks using out-of-band methods for encryption keying. With the service module you can encrypt switch to switch links such as access to distribution, or encrypt dark fiber links within a building or between buildings.

The switch ships with one power supply by default, and the second power supply can be purchased at the time of ordering the switch or at a later time. If only one power supply is installed, it should always be in the power supply bay 1. See Figure 5. Table 6 shows the different power supplies available in these switches and available PoE power.

Table 6. Power Supply Models. In addition to the above power supplies a W DC power supply is available as a spare should be ordered separately on all switch models. The DC power supply also delivers PoE capabilities for maximum flexibility, please refer to table 7 for available PoE for different configurations and customers can mix and match the AC and DC power supplies in the two available power supply slots. Any of these power supplies can be installed in any of the switches.

Table 7. Available PoE with DC power supply. In addition to PoE PoE removes the need for wall power to each PoE-enabled device and eliminates the cost for additional electrical cabling and circuits that would otherwise be necessary in IP phone and WLAN deployments.

Table 8 shows the power supply combinations required for different PoE needs. This requires the W AC power supply in both the power supply slots. Table 8. PoE UPOE 60W per port. It not only provides the functionalities offered by the RPS but also provides enhanced services with the support for Cisco StackPower technology. When used with the Cisco Catalyst X, it provides RPS functionality, but when used with the Cisco Catalyst X, it provides StackPower functionality to all the stack members, including power supply redundancy.

The XPS supports dual redundant power supplies and fans. Up to nine switches can be connected to the XPS , and it can provide power backup to two of the failed switches concurrently when appropriately sized power supplies are used. The XPS is fully configurable for setting switch priorities in case of multiple failures.

Borderless Networks, a Cisco architecture, deliver the new workspace experience, connecting anyone, anywhere, using any device, to any resource securely, reliably, and transparently. Borderless experience is only possible with intelligent network elements designed and architected to meet the needs of a global workspace.

Cisco Network Access is a primary component of this architecture, enabling various borderless network services such as mobility, security, MediaNet, EnergyWise, and ease of operations for increased productivity and operational efficiency.

When network access is intelligent, it knows the identity of the user, as well as where the user is on the network. It knows what is connecting to the network, to automatically provision the network for QoS and delivery. It becomes services-aware to optimize user experience.

Only with intelligent access network, your enterprise can go borderless securely and transparently. Your business can save energy, simplify operations with better business efficiency, and have an optimized total cost of ownership. Cisco Network Access for Borderless solution focuses on the following primary areas:. Cisco Catalyst switching solutions enable greener practices through measurable power efficiency, integrated services, and continuous innovations such as Cisco EnergyWise, an enterprisewide solution that monitors and conserves energy with customized policies.

Together, Cisco EnergyWise technology and Cisco Catalyst switches reduce greenhouse gas GhG emissions and increase energy cost savings and sustainable business behavior.

Cisco EnergyWise is an innovative architecture, added to fixed configuration switches, promoting companywide sustainability by reducing energy consumption across an entire corporate infrastructure and affecting more than 50 percent of global greenhouse gas emissions created by worldwide building infrastructure, a much greater effect than the 2 percent generated by the IT industry.

Cisco EnergyWise enables companies to measure the power consumption of network infrastructure and network-attached devices and manage power consumption with specific policies, reducing power consumption to realize increased cost savings, potentially affecting any powered device.

EnergyWise encompasses a highly intelligent network-based approach to communicate messages that measure and control energy between network devices and endpoints. The network discovers Cisco EnergyWise manageable devices, monitors their power consumption, and takes action based on business rules to reduce power consumption. EnergyWise uses a unique domain-naming system to query and summarize information from large sets of devices, making it simpler than traditional network management capabilities.

Cisco Catalyst X and X Series Switches, designed and engineered by Cisco, provide optimum power saving, low power operations for industry best-in-class power management, and power consumption capabilities. The Cisco Catalyst X and X ports are capable of reduced power modes so that ports not in use can move into a lower power utilization state. StackPower lets customers to simply add one extra power supply in any switch of the stack and provide either power redundancy for any of the stack members or simply add more power to the shared pool.

During peak work hours, most wired client devices use their network connections with infrequent bursts. The normal EEE operation is well suited to this behavior. During off-peak times the client devices may use sleep or hibernate modes. At this time the network interface can be completely inactive and able to be woken on demand by remote request. Prior to the EEE standard, it was a common practice for client devices such as personal computers and servers to save power during sleep states by renegotiating the Ethernet link to a lower speed.

Cisco Catalyst Smart Operations is a comprehensive set of capabilities that simplify LAN deployment, configuration, and troubleshooting. In addition to adaptive, always on technologies such as StackWise and StackPower, Cisco Catalyst Smart Operations enable zero touch installation and replacement of switches, fast upgrade, as well as ease of troubleshooting with reduced operational cost.

Smart Install utilizes dynamic IP address allocation and the assistance of other switches to facilitate installation providing transparent network plug and play. Using EEM, customers can adapt the behavior of their network devices to align with their business needs. This feature requires IP Base feature set. This feature requires IP Services feature set. Automatic software version checking and updating help ensure that all stack members have the same software version.

A PC-based network management application designed for small and medium-sized business SMB networks with up to users, Cisco Network Assistant offers centralized network management and configuration capabilities. Cisco Network Assistant uses Cisco Smartports technology to simplify both initial deployment and ongoing maintenance.

This application also features an intuitive GUI where users can easily apply common services across Cisco switches, routers, and access points, such as:.

It provides an extensive library of easy-to-use features to automate the initial and day-to-day management of your Cisco network infrastructure. CiscoWorks LMS uniquely uses Cisco hardware and software platform knowledge and operational experience into a powerful set of work-flow driven configuration, monitoring, troubleshooting, reporting, and administrative tools. TrustSec, a primary element of Borderless Security Architecture, helps enterprise customers secure their networks, data and resources with policy-based access control, identity and role-aware networking, pervasive integrity, and confidentiality.

The borderless security is enabled by the following feature sets in the Cisco Catalyst X and X Series Switches:. Cisco Integrated Security Features is an industry-leading solution available on Cisco Catalyst Switches that proactively protects your critical network infrastructure.

Delivering powerful, easy-to-use tools to effectively prevent the most common and potentially damaging Layer 2 security threats, Cisco Integrated Security Features provides robust security throughout the network. This feature is used by other primary security features to prevent a number of other attacks such as ARP poisoning. TrustSec secures access to the network, enforces security policies, and delivers standard based security solutions such as TrustSec capabilities reflect Cisco thought leadership, innovations, and commitment to customer success.

These new capabilities include:. Available on Cisco Catalyst X and X Series Switches, MACsec provides Layer 2, line rate Ethernet data confidentiality and integrity on host facing ports, protecting against man-in-the-middle attacks snooping, tampering, and replay. Borderless network enables enterprise mobility and business-grade video services.

The true borderless experience is enabled by the following feature sets in the Cisco Catalyst X and X Series Switches:. The Cisco Catalyst X Series increases availability for stackable switches. Each switch can operate both as primary controller and as forwarding processor. Each switch in the stack can serve as a primary, creating a 1:N availability scheme for network control. In the unlikely event of a single unit failure, all other units continue to forward traffic and maintain operation.

Other high-availability features include but are not limited to:. Stacked units behave as a single spanning-tree node. The IP Services feature set is required. IP Services feature set is required. The Cisco Catalyst X and X Series offers GbE speed with intelligent services that keep everything flowing smoothly, even at 10 times the normal network speed. Industry-leading mechanisms for marking, classification, and scheduling deliver superior performance for data, voice, and video traffic, all at wire speed.

Four queues are user configurable and four are reserved for system use. A wide variety of devices can appear on the network, both wired switches, routers, IP phones, PCs, access points, controllers, video digital media players, and so on and wireless mobile devices, wireless tags, rogues, and so on. In many industries, locating assets is primarily a manual process and is time consuming and error prone. The inability to locate assets in real time and to help ensure their availability when and where they are needed limits reaction time and efficiency.

Location services answer business-critical questions about both mobile assets and the users of those assets regardless of whether those assets are connecting using wired or wireless, and hence directly improve their organization's profitability. Network Location Services also improve security and accelerate client troubleshooting by locating an asset, user, or device on the network.

With EnergyWise, power policies can be set up to reduce the power or shut down the power from a port based on the location. Table 9. Switching Fabric. Total VLANs. Jumbo Frame. Total Routed Ports per X Stack.