Cisco CBS220-24T-4X Manual [EN]

Download

Cisco Business 220 Series Switches Administration Guide

First Published: 2020-12-08

Last Modified: 2021-07-20

Americas Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

Get to Know Your Switch

This chapter contains the following sections:

Introduction

Thank you for purchasing the Cisco CBS 220 Series Switch. The Cisco CBS 220 Series Switches are the next generation of affordable smart switches that combine powerful network performance and reliability with a complete suite of network features that you need for a solid business network. These expandable Gigabit Ethernet switches, with Gigabit or 10-Gigabit uplinks, provide multiple management options, and rich security capabilities. With an easy-to-use web user interface and Power over Ethernet Plus capability, you can deploy and configure a complete business network in minutes.

CHAPTER 1

• Introduction, on page 1

• Rack Mounting Switch, on page 2

• Wall Mounting a Switch, on page 3

• PoE Consideration, on page 5

• Front Panel, on page 6

• Configuring Switches, on page 8

Before You Begin

Before you begin installing your device, ensure that the following items are available:

• RJ-45 Ethernet cables for connecting network devices. A category 6a and higher cable is required for 10G ports; a category 5e and higher cable is required for all other ports.

• Tools for installing the hardware.

• The rack-mount kit packed with the switch contains four rubber feet for desktop placement, and two brackets and twelve screws for rack mounting.

• If the supplied screws are lost, use replacement screws in the following size:

• Diameter of the screw head: 6.9 mm

• Length of face of screw head to base of screw: 5.9 mm

• Shaft diameter: 3.94 mm

Cisco Business 220 Series Switches Administration Guide

Rack Mounting Switch

Get to Know Your Switch

Warning

• A computer to manage the device either via the console port or via the web-based interface. for web based interface the computer needs to support one of the following browsers:

• Microsoft Edge

• Firefox (version 82 or 81 or higher)

• Chrome (version 86 or 85 or higher)

• Safari over MAC (version 14.0 and higher)

Suitable for installation in information Technology Rooms in accordance with Article 645 of the national Electric Code and NFPA 75.

To prevent airflow restriction, allow clearance around the ventilation openings to be at least 3 inches (7.6 cm).

Rack Mounting Switch

You can mount the switches on any standard size, 19-inch (about 48 cm) wide rack. The switch requires 1 rack unit (RU) of space, which is 1.75 inches (44.45 mm) high.

Caution

Step 1 Place one of the supplied brackets on the side of the switch so that the four holes of the brackets align to the screw holes,

and then use the four supplied screws to secure it.

Step 2 Repeat the previous step to attach the other bracket to the opposite side of the switch.

Step 3 After the brackets are securely attached, the switch is now ready to be installed into a standard 19-inch rack.

For stability, load the rack from the bottom to the top, with the heaviest devices on the bottom. A top-heavy rack is likely to be unstable and might tip over.

To install the switch into a 19-inch standard chassis:

Cisco Business 220 Series Switches Administration Guide

Get to Know Your Switch

Wall Mounting a Switch

You can mount the switches on a wall, using wall studs or to a firmly attached plywood mounting backboard.

Wall Mounting a Switch

Caution

Step 1 Attach a 19-inch bracket to one side of the switch.

Step 2 Repeat the previous step to attach the other bracket to the opposite side of the switch.

Step 3 After the brackets are securely attached, mount the switch with the front panel facing down. Make sure that the switch

is attached securely to wall studs or to a firmly attached plywood-mounting backboard. Wall-mounting a 24-port switch.

Wall-mounting a 24-port

Read these instructions carefully before beginning installation. Failure to use the correct hardware or to follow the correct procedures could result in a hazardous situation to people and damage to the system.

Do not wall-mount the switch with its front panel facing up. Following safety regulations, wallmount the switch with its front panel facing down or to the side to prevent airflow restriction and to provide easier access to the cables.

To wall-mount a 24-port switch using brackets:

Cisco Business 220 Series Switches Administration Guide

Wall Mount an 8 Port Switch

Get to Know Your Switch

Wall Mount an 8 Port Switch

To wall-mount a 8-port switch using mounting screws, follow these steps:

Step 1 Locate the screw template. The template is used to align the mounting screw holes.

Step 2 Position the screw template so that the edge that is marked as CABLE SIDE ENTRY faces toward the floor. Make sure

that the switch is attached securely to wall studs or to a firmly attached plywoodmounting backboard.

Step 3 Peel the adhesive strip off the bottom of the screw template.

Step 4 Attach the screw template to the wall.

Step 5 Use a 0.144-inch (3.7 mm) or a #27 drill bit to drill a 1/2-inch (12.7 mm) hole in the two screw template slots.

Step 6 Insert two screws in the slots on the screw template, and tighten them until they touch the top of the screw template.

Installing the mounting screws on the wall

Figure 3 Installing the mounting screws on the wall

Cisco Business 220 Series Switches Administration Guide

Get to Know Your Switch

PoE Consideration

Step 7 Remove the screw template from the wall.

Step 8 Place the switch onto the mounting screws, and slide it down until it locks in place.Wall-mounting an 8-port switch

Figure 4 Wall-mounting an 8-port switch

PoE Consideration

Some switches support PoE while others do not. The switch models that support PoE have a P in their model number, such as: CBSxxx-xxP-xx. If your switch is one of the Power over Ethernet (PoE) models, consider the following power requirement.

Danger

The switch is to be connected only to PoE networks without routing to the outside plant.

Cisco Business 220 Series Switches Administration Guide

Front Panel

Get to Know Your Switch

Table 1: Switches with Power Over Ethernet

PoE PSE SupportPoE PD Chipset TypeDescriptionSKU Name

CBS220-8P-E-2G

CBS220-8FP-E-2G

CBS220-16P-2G

CBS220-24P-4G

CBS220-24FP-4G

CBS220-48P-4G

CBS220-48P-4X

CBS220-48FP-4X

AF/AT1*69208M10-Port Gigabit PoE

Smart Switch

AF/AT1*69208M10-Port Gigabit PoE

Smart Switch

AF/AT2*69208M18-Port Gigabit PoE

Smart Switch

AF/AT3*69208M24-Port Gigabit PoE

Smart Switch

AF/AT3*69208M24-Port Gigabit PoE

Smart Switch

AF/AT6*69208M48-Port Gigabit PoE

Smart Switch

AF/AT6*69208M48-Port Gigabit PoE

Smart Switch

AF/AT6*69208M48-Port Gigabit PoE

Smart Switch

Note

Front Panel

Consider the following when connecting a PoE switch. The PoE switches are PSE (Power Sourcing Equipment) that are capable of supplying DC power to attaching powered devices (PD). These devices include VoIP phones, IP cameras, and wireless access points. The PoE switches can detect and supply power to pre-standard legacy PoE PD. Due to the PoE legacy support, it is possible that a PoE switch acting as a PSE may mistakenly detect and supply power to an attaching PSE, including other PoE switches, as a legacy PD. Even though PoE switches are PSE, and as such should be powered by AC, they could be powered up as a legacy PD by another PSE due to false detection. When this happens, the PoE switch may not operate properly and may not be able to properly supply power to its attaching PDs.

To prevent false detection, you should disable PoE on the ports on the PoE switches that are used to connect to PSEs. You should also first power up a PSE device before connecting it to a PoE switch. When a device is being falsely detected as a PD, you should disconnect the device from the PoE port and power recycle the device with AC power before reconnecting its PoE ports.

The ports, LEDs, and Reset button are located on the front panel of the switch, as well as the following components:

Cisco Business 220 Series Model

Cisco Business 220 Series Switches Administration Guide

Get to Know Your Switch

Note

Front Panel LEDs

Models may differ within the CBS 220 series and this is just a representation of a model within the series.

• Console port with RJ-45. The console connects a serial cable to a computer serial port so that it can be configured using a terminal emulation program.

Note

Only certain models support this feature.

• RJ-45 Ethernet Ports—The RJ-45 Ethernet ports connect network devices, such as computers, printers, and access points, to the switch.

• SFP+ Port (if present)—The small form-factor pluggable plus (SFP+) are connection points for modules so that the switch can link to other switches. These ports are also commonly referred to as mini 10 GigaBit Interface Converter ports. The term SFP+ is used in this guide.

• The SFP+ ports are compatible with the following Cisco SFP 1G optical modules MGBSX1, MGBLX1, MGBLH1, MGBT1, as well as other brands.

• Reset button is used to reset or reboot the switch. To reboot the switch, press the Reset button for less

Front Panel LEDs

The following are the global LEDs found on the devices:

• System—(Green) The LED lights steady when the switch is powered on, and flashes when booting,

The following are per port LEDs:

• LINK/ACT—(Green) Located on the left of each port. The LED lights steady when a link between the

• XG—(Green) (if present) Located on the right of a 10G port. The LED lights steady when another device

• The Cisco SFP+ Copper Cable modules that are supported in the Cisco switches are: SFP-H10GB-CU1M, SFP-H10GB-CU3M, and SFP-H10GB-CU5M.

• Small form-factor pluggable (SFP) ports are connection points for modules, so the switch can link to other switches.

than 10 seconds.

performing self-tests, or acquiring an IP address. If the LED flashes Amber, the switch has detected a hardware or firmware failure, and/or a configuration file error.

corresponding port and another device is detected, and flashes when the port is passing traffic.

is connected to the port, is powered on, and a 10 Gbps link is established between the devices. When the LED is off, the connection speed is under 10 Gbps or nothing is cabled to the port.

• Gigabit—(Green) (if present) Located on the right of the 1G port. The LED lights steady when another device is connected to the port, is powered on, and a 1000 Mbps link is established between the devices. When the LED is off, the connection speed is under 1000 Mbps or nothing is cabled to the port.

• PoE (if present)—(Amber) Located on the right of the port. The LED lights steady when power is being supplied to a device attached to the corresponding port.

Cisco Business 220 Series Switches Administration Guide

Configuring Switches

The switch can be accessed and managed by two different methods; over your IP network using the web-based interface, or by using the switch’s command-line interface through the console port. Using the console port requires advanced user skills.

The following table shows the default settings used when configuring your switch for the first time.

Default ValueParameter

ciscoUsername

ciscoPassword

192.168.1.254LAN IP

Configuring Your Switch Using the Web-based Interface

Get to Know Your Switch

To access the switch with a web-based interface, you must know the IP address that the switch is using. The switch uses the factory default IP address of 192.168.1.254, with a subnet of /24. When the switch is using the factory default IP address, the System LED flashes continuously. When the switch is using a DHCP server-assigned IP address or an administrator has configured a static IP address, the System LED is a steady green (DHCP is enabled by default).

If you are managing the switch through a network connection and the switch IP address is changed, either by a DHCP server or manually, your access to the switch will be lost. You must enter the new IP address that the switch is using into your browser to use the web-based interface. If you are managing the switch through a console port connection, the link is retained.

To configure the switch using the web-based interface:

Step 1 Power on the computer and your switch.

Step 2 Connect the computer to any network port.

Step 3 Set up the IP configuration on your computer.

a) If the switch is using the default static IP address of 192.168.1.254/24, you must choose an IP address for the computer

in the range of 192.168.1.2 to 192.168.1.253 that is not already in use.

b) If the IP addresses will be assigned by DHCP, make sure that your DHCP server is running and can be reached from

the switch and the computer. You may need to disconnect and reconnect the devices for them to discover their new IP addresses from the DHCP server.

Note

Details on how to change the IP address on your computer depend upon the type of architecture and operating system that you are using. Use your computers local Help and Support functionality and search for “IP Addressing.”

Step 4 Open a web browser window. Step 5 Enter the switch IP address in the address bar and press Enter. For example, http://192.168.1.254.

Step 6 When the login page appears, choose the language that you prefer to use in the web-based interface and enter the username

and password.

Cisco Business 220 Series Switches Administration Guide

Get to Know Your Switch

The default username is cisco. The default password is cisco. Usernames and passwords are both case sensitive.

Step 7 Click Log In.

If this is the first time that you have logged on with the default username and password, the Change username and Password page opens. The rules for constructing a new password are displayed on the page.

Step 8 Enter a new username and password and confirm.

Configuring Your Switch Using the Console Port

Note

Password complexity is enabled by default. The password must comply with the default complexity rules.

Step 9 Click Apply.

Caution

Make sure that any configuration changes made are saved before exiting from the web-based interface by clicking on the Save icon. Exiting before you save your configuration results in all changes being lost.

The Getting Started page opens. You are now ready to configure the switch. Refer to the Administration Guide or see the help pages for further information.

Configuring Your Switch Using the Console Port

To configure the switch using the console port, proceed with the following steps:

Step 1 Connect a computer to the switch console port using a Cisco console cable (purchased separately) or a cable with mini

USB connector.

Step 2 Start a console port utility such as HyperTerminal on the computer.

Step 3 Configure the utility with the following parameters:

• 115200 bits per second

• 8 data bits

• no parity

• 1 stop bit

• no flow control

Step 4 Enter a username and password. The default username is cisco, and the default password is cisco. Usernames and passwords

are both case sensitive.

If this is the first time that you have logged on with the default username and password, the following message appears:

Please change your username AND password from the default settings. Change of credentials

is required for better protection of your network.

Please note that new password must follow password complexity rules

Step 5 Set a new administrator username and password.

Caution

Make sure that any configuration changes made are saved before exiting.

You are now ready to configure the switch. See the CLI Guide for your switch.

Cisco Business 220 Series Switches Administration Guide

Configuring Your Switch Using the Console Port

Get to Know Your Switch

Note

If you are not using DHCP on your network, set the IP address type on the switch to Static and change the static IP address and subnet mask to match your network topology. Failure to do so may result in multiple switches using the same factory default IP address of 192.168.1.254.

Console access also provides additional interfaces for debug access which are not available via the web interface. These debug access interfaces are intended to be used by a Cisco Support Team personnel, in cases where it is required to debug device’s behavior. These interfaces are password protected. The passwords are held by the Cisco support team. The device supports the following debug access interfaces:

• U-BOOT access during boot sequence

• Linux Kernel access during boot sequence

• Run time debug modes - allows Cisco support team to view device settings and apply protocol and layer 1 debug commands and settings. The run time debug mode is accessible over telnet and SSH terminals in addition to console.

Cisco Business 220 Series Switches Administration Guide

Getting Started

This chapter contains the following section:

• Getting Started, on page 11

Getting Started

This section will guide you on how to install and manage your device.

Click on Getting Started to access the page where you can use the various links and follow the on-screen

instructions to quickly configure your switch.

Initial Setup

and Services

CHAPTER 2

TCP/UDP Services, on page 129Change Management Applications

IPv4 Interface, on page 116Change Device IP Address

Device Status

Quick Access

VLAN Settings, on page 82Create VLAN

Port Settings, on page 47Configure Port Settings

System Summary, on page 13System Summary

Interface, on page 13Port Statistics

RMON Statistics, on page 18RMON Statistics

RAM Memory, on page 22View Log

User Accounts, on page 26Change Device Password

Firmware Operations, on page 34Upgrade Device Software

Cisco Business 220 Series Switches Administration Guide

Getting Started

File Operations, on page 35Backup Device Configuration

MAC-Based ACL, on page 153Create MAC-Based ACL

IPv4-based ACL, on page 155Create IP-Based ACL

QoS Properties, on page 163Configure QoS

SPAN and RSPAN, on page 16Configure SPAN

There are two hot links on the Getting Started page that take you to Cisco web pages for more information. Clicking on the Support link takes you to the device product support page, and clicking on the Forums link takes you to the Support Community page.

Cisco Business 220 Series Switches Administration Guide

Status and Statistics

This chapter contains the following sections:

• System Summary, on page 13

• Interface, on page 13

• Etherlike, on page 14

• Hardware Resource Utilization, on page 15

• Health, on page 16

• SPAN and RSPAN, on page 16

• RMON, on page 18

• View Log, on page 22

System Summary

The System Summary provides a preview of the device status, hardware, firmware version, general PoE status, and other system information.

To view the system information, click Status and Statistics > System Summary.

CHAPTER 3

Interface

The Interface page displays traffic statistics per port. This page is useful for analyzing the amount of traffic that is both sent and received, and its dispersion (Unicast, Multicast, and Broadcast).

To display Ethernet statistics and/or set the refresh rate, follow these steps:

Step 1 Click Status and Statistics > Interface.

Step 2 To view statistics counters in table view or graphic view:

• Click Clear Interface Counters, to clear all counters.

• Click Refreshto refresh the counters.

• Click View All Interfaces Statistics to see all ports in table view.

• Select the refresh rate from the Refresh Rate drop-down menu.

Cisco Business 220 Series Switches Administration Guide

Etherlike

• Select an interface and click Clear Interface Counters to clear the statistics counters for the selected interface.

• Click Clear All Interface Counters to clear the statistics counters for all interfaces.

• Select an interface and click View Interface Statisticsto see the statistics counters for the selected interface

on a single page.

• Click Refreshto manually refresh the statistics counters for all interfaces.

Step 3 Enter the parameters.

• Interface—Select the interface for which Ethernet statistics are to be displayed.

• Refresh Rate—Select the time period that passes before the interface Ethernet statistics are refreshed.

Step 4 In the Receive Statistics section, the following stats are displayed:

• Total Bytes (Octets)—Octets received, including bad packets and FCS octets, but excluding framing bits.

• Unicast Packets—Good Unicast packets received.

Status and Statistics

• Multicast Packets—Good Multicast packets received.

• Broadcast Packets—Good Broadcast packets received.

• Packets with Errors—Packets with errors received.

Step 5 In the Transmit Statistics section, the following stats are displayed:

• Total Bytes (Octets)—Octets transmitted, including bad packets and FCS octets, but excluding framing bits.

• Unicast Packets—Good Unicast packets transmitted.

• Multicast Packets—Good Multicast packets transmitted.

• Broadcast Packets—Good Broadcast packets transmitted.

Etherlike

The Etherlike page displays statistics per port according to the Etherlike MIB standard definition. The refresh rate of the information can be selected. This page provides more detailed information regarding errors in the physical layer (Layer 1) that might disrupt traffic.

To view Etherlike Statistics and/or set the refresh rate follow these steps:

Step 1 Click Status and Statistics > Etherlike. Step 2 To view statistics counters in table view, click View All Interfaces Statistics to see all ports in table view.

• Select the refresh rate from the Refresh Rate drop-down menu.

• Select an interface and click Clear Interface Counters to clear the statistics counters for the selected interface.

Cisco Business 220 Series Switches Administration Guide

Status and Statistics

• Click Clear All Interface Counters to clear the statistics counters for all interfaces.

• Select an interface and click View Interface Statisticsto see the statistics counters for the selected interface on a

single page.

• Click Refreshto manually refresh the statistics counters for all interfaces.

Step 3 Enter the parameters.

• Interface-Select the specific interface for which Ethernet statistics are to be displayed.

• Refresh Rate-Select the amount of time that passes before the Etherlike statistics are refreshed.

The fields are displayed for the selected interface.

• Frame Check Sequence (FCS) Errors - Received frames that failed the CRC (cyclic redundancy checks).

• Single Collision Frames- Frames that involved in a single collision, but successfully transmitted.

• Late Collisions - Collisions that have been detected after the first 512 bits of data.

• Excessive Collisions - Transmissions rejected due to excessive collisions.

Hardware Resource Utilization

• Oversize Packets - Packets greater than 2000 octets received.

• Internal MAC Receive Errors - Frames rejected because of receiver errors.

• Pause Frames Received - Received flow control pause frames.

• Pause Frames Transmitted - Number of flow control pause frames transmitted from the selected interface.

Step 4 You can also click Refresh to refresh the stats or click Clear Interface Counters to clear the counters.

Hardware Resource Utilization

This page displays the resources used by the device, such as Access Control Lists (ACL) and Quality of Service (QoS). Some applications allocate rules upon their initiation.

The count of each item may differ from different Models due to system design. Also, because of ASIC characteristics, it’s possible to show a "Lack of HW resources" when binding an Advance QoS service policy or User-defined ACL but this page shows enough TCAM resources.

To view the hardware resource utilization, click Status and Statistics > Hardware Resource Utilization.

The following fields are displayed:

• Total Entries

• Maximum—Number of available TCAM entries that can be used for whole system.

• In Use—Number of TCAM entries used for whole system

• System Rules

• Allocated—Number of allocated TCAM entries that can be used for system rules.

Cisco Business 220 Series Switches Administration Guide

Health

Status and Statistics

• In Use—Number of TCAM entries used for system rules.

• ACL and QoS Rules

• Allocated—Number of allocated TCAM entries that can be used for ACL and QoS rules.

• In Use—Number of TCAM entries used for ACL and QoS rules.

The Health page monitors the temperature, and fan status on all relevant devices. The fans on the device vary based on the model.

Fan Status

• Fan—Displays fan ID.

• Status—Displays whether the fan is operating normally (OK) or not (Fault).

• Speed (RPM)—Displays fan speed.

Temperature Status

• Sensor—Displays sensor id.

• Status—Displays one of the following options:

• OK—The temperature is below the warning threshold.

• Warning—The temperature is between the warning threshold to the critical threshold.

• Critical—Temperature is above the critical threshold.

• TEMP (°C) —Displays temperature of sensor.

SPAN and RSPAN

The SPAN feature, which is sometimes called port mirroring or port monitoring, selects network traffic for analysis by a network analyzer. The network analyzer can be a Cisco Switch Probe device or other Remote Monitoring (RMON) probes.

Port mirroring is used on a network device to send a copy of network packets, seen on a single device port, multipledevice ports, or an entire VLAN, to a network monitoring connection on another port on the device. This is commonly used when monitoring of network traffic, such as for an intrusion-detection system, is required. A network analyzer, connected to the monitoring port, processes the data packets. A packet, which is received on a network port and assigned to a VLAN that is subject to mirroring, is mirrored to the analyzer port even if the packet was eventually trapped or discarded. Packets sent by the device are mirrored when Transmit (Tx) mirroring is activated.

RSPAN supports source ports, source VLANs, and destination ports on different switches, enabling remote monitoring of multiple switches across your network. The traffic for each RSPAN session is carried over a user-specified RSPAN VLAN that is dedicated for that RSPAN session in all participating switches. The

Cisco Business 220 Series Switches Administration Guide

Status and Statistics

RSPAN traffic from the source ports or VLANs is copied into the RSPAN VLAN and forwarded carrying the RSPAN VLAN to a destination session monitoring the RSPAN VLAN.

Mirroring does not guarantee that all traffic from the source port(s) is received on the analyzer (destination) port. If more data is sent to the analyzer port than it can support, some data might be lost.

RSPAN VLAN

An RSPAN VLAN carries SPAN traffic between RSPAN source and destination sessions.

To configure a VLAN as an RSPAN VLAN, follow these steps:

Step 1 Click Status and Statistics > SPAN > RSPAN VLAN. to view the previously defined RSPAN VLAN.

Step 2 Select the RSPAN VLAN. Step 3 Click Apply.

RSPAN VLAN

Session Destinations

A monitoring session consists of one or more source ports and a single destination ports. A destination port must be configured on the start and final devices. On the start device, this is the reflector port. On the final device, it is the analyzer port.

To add a destination port, follow these steps:

Step 1 Click Status and Statistics >SPAN & RSPAN> Session Destinations. Step 2 Click Add.

Step 3 Enter the following fields:

• Session ID—Select a session ID. This must match the session IDs of the source ports.

• Destination Type – Select a local interface or remote VLAN as destination.

• Port—Select a port from the drop-down list.

• Network Traffic—Select to enable that traffic other than monitored traffic is possible on the port.

Step 4 Click Apply.

Session Sources

In a single local SPAN or RSPAN session source, you can monitor the port traffic, such as received (Rx), transmitted (Tx), or bidirectional (both). The switch supports any number of source ports (up to the maximum number of available ports on the switch) and any number of source VLANs.

To configure the source ports to be mirrored, follow these steps:

Cisco Business 220 Series Switches Administration Guide

Status and Statistics

RMON

Step 1 Click Status and Statistics > SPAN and RSPAN > Session Sources. Step 2 Click Add.

Step 3 Select the session number from Session ID. This must be the same for all source ports and the destination port. Step 4 In the Monitor Type field, select whether incoming, outgoing, or both types of traffic are mirrored.

• Rx and Tx—Port mirroring on both incoming and outgoing packets

• Rx—Port mirroring on incoming packets

• Tx—Port mirroring on outgoing packets

Step 5 Click Apply. The source interface for the mirroring is configured.

RMON

Remote Networking Monitoring (RMON) enables an SNMP agent in the device to proactively monitor traffic statistics over a given period and send traps to an SNMP manager. The local SNMP agent compares actual, real-time counters against predefined thresholds and generates alarms, without the need for polling by a central SNMP management platform. This is an effective mechanism for proactive management, provided that you have set the correct thresholds relative to your network’s base line.

RMON decreases the traffic between the manager and the device since the SNMP manager does not have to poll the device frequently for information, and enables the manager to get timely status reports, since the device reports events as they occur.

With this feature, you can perform the following actions:

RMON Statistics

The Statistics page displays detailed information regarding packet sizes and information regarding physical layer errors. The information is displayed according to the RMON standard. An oversized packet is defined as an Ethernet frame with the following criteria:

• View the current statistics (from the time that the counter values cleared). You can also collect the values of these counters over a period of time, and then view the table of collected data, where each collected set is a single line of the History tab.

• Define interesting changes in counter values, such as “reached a certain number of late collisions” (defines the alarm), and then specify what action to perform when this event occurs (log, trap, or log and trap).

• Packet length is greater than MRU byte size.

• Collision event has not been detected.

• Late collision event has not been detected.

• Received (Rx) error event has not been detected.

• Packet has a valid CRC.

Cisco Business 220 Series Switches Administration Guide

Status and Statistics

RMON Statistics

To view RMON statistics and/or set the refresh rate, complete the following:

Step 1 Click Status and Statistics > RMON > Statistics.

Step 2 Select the Interface for which Ethernet statistics are to be displayed.

Step 3 Select the Refresh Rate, which is the time period that passes before the interface statistics are refreshed.

The following statistics are displayed for the selected interface.

RMON Bytes Received (Octets)

RMON Broadcast Packets Received

RMON Fragments

RMON Jabbers

Octets received, including bad packets and FCS octets, but excluding framing bits.

Packets dropped.RMON Drop Events

Good packets received including Multicast and Broadcast packets.RMON Packets Received

Good Broadcast packets received. This number does not include Multicast packets.

Good Multicast packets received.RMON Multicast Packets Received

CRC and Align errors that have occurred.RMON CRC & Align Errors

Undersized packets (less than 64 octets) received.RMON Undersize Packets

Oversized packets (over 2000 octets) received.RMON Oversize Packets

Fragments (packets with less than 64 octets, excluding framing bits, but including FCS octets) received.

Received packets that are longer than 1632 octets. This number excludes frame bits, but includes FCS octets that had either a bad FCS (Frame Check Sequence) with an integral number of octets (FCS Error) or a bad FCS with a non-integral octet (Alignment Error) number. A Jabber packet is defined as an Ethernet frame that satisfies the following criteria:

RMON Collisions

Frames of 1024 Bytes or More

Step 4 To view counters in table view:

Collisions received. If Jumbo frames are enabled, the threshold of Jabber frames is raised to the maximum size of Jumbo frames.

Frames, containing 64 bytes that were sent or received.Frames of 64 Bytes

Frames, containing 65-127 bytes that were sent or received.Frames of 65 to 127 Bytes

Frames, containing 128-255 bytes that were sent or received.Frames of 128 to 255 Bytes

Frames, containing 256-511 bytes that were sent or received.Frames of 256 to 511 Bytes

Frames, containing 512-1023 bytes that were sent or received.Frames of 512 to 1023 Bytes

Frames, containing 1024-2000 bytes, and Jumbo Frames, that were sent or received.

Cisco Business 220 Series Switches Administration Guide

Status and Statistics

RMON History

• Click View All Interfaces Statistics to see all ports in table view.

RMON History

The RMON feature enables monitoring statistics per interface.

The History page defines the sampling frequency, amount of samples to store and the port from which to gather the data. After the data is sampled and stored, it appears in the History Table page that can be viewed by clicking History Table.

To enter RMON control information, complete the following:

Step 1 Click Status and Statistics> RMON > History. The fields displayed on this page are defined in the Add RMON History

page, below. The only field is that is on this page and not defined in the Add page is:

• Current Number of Samples-RMON is allowed by the standard not to grant all requested samples, but rather to limit the number of samples per request. Therefore, this field represents the sample number granted to the request that is equal or less than the requested value.

Step 2 Click Add.

Step 3 Enter the parameters.

• New History Entry-Displays the number of the new History table entry.

• Source Interface-Select the type of interface from which the history samples are to be taken.

• Max No. of Samples to Keep-Enter the number of samples to store.

• Sampling Interval-Enter the time in seconds that samples are collected from the ports. The field range is 1-3600.

• Owner-Enter the RMON station or user that requested the RMON information.

Step 4 Click Apply. The entry is added to the History Control Table page, and the Running Configuration file is updated. Step 5 Click History Table to view the actual statistics.

RMON Events

The Events page displays the log of events (actions) that occurred. Two types of events can be logged: Log or Log and Trap. The action in the event is performed when the event is bound to an alarm and the conditions of the alarm have occurred.

Step 1 Click Status and Statistics > RMON > Events. Step 2 Click Add.

Step 3 Enter the parameters:

• Event Entry—Displays the event entry index number for the new entry.

Cisco Business 220 Series Switches Administration Guide

Status and Statistics

Alarms

• Community—Enter the SNMP community string to be included when traps are sent (optional).

• Description—Entera name for the event. This name is used in the Add RMON Alarm page to attach an alarm to an event.

• Notification Type—Select the type of action that results from this event. Values are:

• None—No action occurs when the alarm goesoff.

• Log (Event Log Table)—Add a log entry to the Event Log table when the alarm istriggered.

• Trap (SNMP Manager and Syslog Server—Send a trap to the remote log server when the alarm goes off.

• Log and Trap—Add a log entry to the Event Log table and send a trap to the remote log server when the alarm goes off.

• Owner—Enter the device or user that defined the event.

Step 4 Click Apply.The RMON event is saved to the Running Configuration file. Step 5 Click EventLog Tableto display the log of alarms that have occurred and that have been logged (see description below).

Alarms

RMON alarms provide a mechanism for setting thresholds and sampling intervals to generate exception events on counters or any other SNMP object counter maintained by the agent. Both the rising and falling thresholds must be configured in the alarm. After a rising threshold is crossed, no rising events are generated until the companion falling threshold is crossed. After a falling alarm is issued, the next alarm is issued when a rising threshold is crossed.

One or more alarms are bound to an event, which indicates the action to be taken when the alarm occurs.

Alarm counters can be monitored by either absolute values or changes (delta) in the counter values.

To enter RMON alarms, complete the following steps:

Step 1 Click Status and Statistics > RMON > Alarms.

All previously defined alarms are displayed. The fields are described in the Add RMON Alarm page below.

Step 2 Click Add.

Step 3 Enter the parameters.

Displays the alarm entry number.Alarm Entry

Select the type of interface for which RMON statistics are displayed.Interface

Select the MIB variable that indicates the type of occurrence measured.Counter Name

Cisco Business 220 Series Switches Administration Guide

View Log

Status and Statistics

Sample Type

Startup Alarm

Select the sampling method to generate an alarm. The options are:

• Absolute—If the threshold is crossed, an alarm is generated.

• Delta—Subtracts the last sampled value from the current value The difference in the values is compared to the threshold. If the threshold was crossed, an alarm is generated.

Enter the value that triggers the rising threshold alarm.Rising Threshold

Select an event to be performed when a rising event is triggered.Rising Event

Enter the value that triggers the falling threshold alarm.Falling Threshold

Select an event to be performed when a falling event is triggered.Falling Event

Select the first event from which to start generation of alarms. Rising is defined by crossing the threshold from a low-value threshold to a higher-value threshold.

• Rising Alarm—A rising value triggers the rising threshold alarm.

• Falling Alarm—A falling value triggers the falling threshold alarm.

• Rising and Falling—Both rising and falling values trigger the alarm.

Enter the alarm interval time in seconds.Interval

Enter the name of the user or network management system that receives the alarm.Owner

Step 4 Click Apply. The RMON alarm is saved to the Running Configuration file.

View Log

The device can write to the following logs:

• Log in RAM (cleared during reboot).

• Log in Flash memory (cleared only upon user command).

You can configure the messages that are written to each log by severity, and a message can go to more than one log, including logs that reside on external SYSLOG servers.

RAM Memory

The RAM Memory page displays all messages that are saved in the RAM (cache) in chronological order. All entries are stored in the RAM log.

To view log entries, click Status and Statistics > View Log > RAM Memory.

The following are displayed at the top of the page:

• Alert Icon Blinking—Toggles between disable and enable.

Cisco Business 220 Series Switches Administration Guide

Status and Statistics

Flash Memory

• Current Logging Threshold—Specifies the levels of logging that are generated. This can be changed by clicking Edit by the field’s name.

This page contains the following fields for every log file:

• Log Index—Log entry number

• Log Time—Time when message was generated.

• Severity—Event severity

• Description—Message text describing the event

To clear the log messages, click Clear Logs.

The Flash Memory page displays the messages that stored in the Flash memory, in chronological order. The minimum severity for logging is configured in the Log Settings, on page 32. Flash logs remain when the device is rebooted. You can clear the logs manually.

To view the Flash logs, click Status and Statistics > View Log > Flash Memory.

The Current Logging Threshold specifies the levels of logging that are generated. This can be changed by clicking Edit by the field’s name.

This page contains the following fields for each log file:

• Log Index—Log entry number

• Log Time—Time when message was generated.

• Severity—Event severity

• Description—Message text describing the event

To clear the messages, click Clear Logs. The messages are cleared.

Cisco Business 220 Series Switches Administration Guide

Flash Memory

Status and Statistics

Cisco Business 220 Series Switches Administration Guide

Administration

This chapter contains the following sections:

• System Settings, on page 25

• Console Settings , on page 26

• User Accounts, on page 26

• Idle Session Timeout, on page 27

• Time Settings, on page 28

• System Log, on page 31

• File Management, on page 33

• Cisco Business Dashboard Settings, on page 37

• Plug-n-Play (PNP), on page 38

• Reboot, on page 43

• Diagnostics, on page 43

• Discovery Bonjour, on page 46

• Discovery LLDP, on page 46

• Discovery - CDP, on page 58

• Locate Device, on page 64

• Ping, on page 64

• Traceroute, on page 65

CHAPTER 4

System Settings

The system setting page allows you customize the settings on your switch. You can configure the following:

Step 1 Click Administration > System Settings.

Step 2 View or modify the system settings.

• System Description—Displays a description of the device.

• System Location—Enter the physical location of the device.

• System Contact—Enter the name of a contact person.

• Host Name—Select the host name of this device. This is used in the prompt of CLI commands:

Cisco Business 220 Series Switches Administration Guide

Console Settings

• Custom Banner Settings—The following banners can be set:

Administration

• Use Default—The default hostname (System Name) of these switches is: switch123456, where 123456 represents the last three bytes of the device MAC address in hex format.

• User Defined—Enter the hostname. Use only letters, digits, and hyphens. Host names can’t begin or end with a hyphen. No other symbols, punctuation characters, or blank spaces are permitted (as specified in RFC1033, 1034, 1035).

• Login Banner—Enter text to display on the Login page before login. Click Previewto view the results.

• Welcome Banner—Enter text to display on the Login page after login. Click Preview to view the results.

Note

Step 3 Click Apply to save the values in the Running Configuration file.

When you define a login banner from the web-based configuration utility, it also activates the banner for the CLI interfaces (Console, Telnet, and SSH).

The banner can contain up to 2000 characters.

Console Settings

The console port speed can be set to one of the following speeds: 2400, 4800, 9600, 19200, 38400, 57600, and 115200.

To configure the console settings, follow these steps:

Step 1 Click Administration > Console Settings.

Step 2 Select a value from the Console Port Baud Rate drop-down menu. The available values are 2400, 4800, 9600, 19200,

38400, 57600, and 115200 Bit/sec.

Step 3 Click Apply. The console port Baud rate is defined, and the Running Configuration is updated.

User Accounts

The User Accounts page enables entering additional users that are permitted to access to the device (read-only or read-write) or changing the passwords of existing users. A user accessing the device for the first time uses the cisco/cisco username and password. After providing the default credentials, you’re prompted to replace the default level 15 username and password, and you must provide a new username and password. The new password must comply with the password complexity rules.

To add a new user, follow these steps:

Step 1 Click Administration > User Accounts. Step 2 Click Add to add a new user or click Edit to modify a user.

Cisco Business 220 Series Switches Administration Guide

Administration

Step 3 Enter the parameters.

• User Name—Enter a new username from 0 through 31 characters. UTF-8 characters aren’t permitted.

• Password—Enter a password (UTF-8 characters aren’t permitted).

• Confirm Password—Enter the password again.

• Password Strength Meter—Displays the strength of password. The password must comply with the minimum strength and complexity requirements shown on this page.

• User Level—Select the privilege level of the user.

• Read-Only CLI Access (1)—User can’t access the GUI, and can only access CLI commands that don’t change the device configuration.

• Read/Write Management Access (15)—User can access the GUI, and can configure the device.

Step 4 Click Apply. The user is added to the Running Configuration file of the device.

Idle Session Timeout

Note

The password is stored in the configuration files as a non-recoverable hash using Password Based Key Derivation Function 2 (PBKDF2) with Secure Hash Algorithm, and SHA-256 as the hashing algorithm.

Idle Session Timeout

The Idle Session Timeout configures the time intervals that the management sessions can remain idle before they timeout.

To set the idle session timeout for various types of sessions, complete these steps:

Step 1 Click Administration > Idle Session Timeout.

Step 2 Select the timeout for the each type of session from the list.

• HTTP Session Timeout

• HTTPS Session Timeout

• Console Session Timeout

• Telnet Session Timeout

• SSH Session Timeout

The default timeout value is 10 minutes. You must log in again to reestablish one of the chosen sessions.

Step 3 Click Apply to set the configuration settings on the device.

Cisco Business 220 Series Switches Administration Guide

Time Settings

Synchronized system clocks provide a frame of reference between all devices on the network. Network time synchronization is critical because every aspect of managing, securing, planning, and debugging a network involves determining when events occur. Without synchronized clocks, accurately correlating log files between devices when tracking security breaches or network usage is impossible. Synchronized time also reduces confusion in shared file systems, as it is important for the modification times to be consistent, regardless of the machine on which the file systems reside. For these reasons, it is important that the time configured on all of the devices on the network is accurate.

Note

The device supports SNTP, and when enabled, the device dynamically synchronizes the device time with time from an SNTP server. The device operates only as an SNTP client, and cannot provide time services to other devices.

Administration

System Time

Use the System Time page to select the system time source. If the source is manual, you can enter the time here.

Caution

Step 1 Click Administration > Time Settings > System Time.

The following fields are displayed:

• Actual Time— Actual system time on the device.

Step 2 Enter the following parameters:

• Clock Source Settings—Select the source used to set the system clock.

• Manual Settings—Set the date and time manually. The local time is used when there’s no alternate source of time,

If the system time is set manually and the device is rebooted, the manual time settings must be reentered.

To define system time, complete these steps:

• Main Clock Source (SNTP Servers)—If this is enabled, the system time is obtained from an SNTP server.

such as an SNTP server:

• Date—Enter the system date.

• Local Time—Enter the system time.

• Time Zone Settings

• Time Zone Offset—Select the difference in hours between Greenwich Mean Time (GMT) and the local time.

Cisco Business 220 Series Switches Administration Guide

For example, the Time Zone Offset for Paris is GMT +1, while the Time Zone Offset for New York is GMT – 5.

Administration

SNTP Settings

• Time Zone Acronym—Enter a name that represents this time zone. This acronym appears in the Actual Time field.

• Daylight Savings Settings—Select how DST is defined:

• Daylight Savings—Select to enable Daylight Saving Time.

• Time Set Offset—Enter the number of minutes offset from GMT ranging 1—1440. The default is 60.

• Daylight Savings Type—Click one of the following:

USA—DST is set according to the dates used in the USA.

European—DST is set according to the dates used by the European Union and other countries that use this standard.

By dates—DST is set manually, typically for a country other than the USA or a European country. Enter the parameters described below.

Recurring—DST occurs on the same date every year.

Selecting By Dates allows customization of the start and stop of DST:

• From—Day and time that DST starts.

• To—Day and time that DST ends.

Step 3 Selecting Recurring allows different customization of the start and stop of DST:

• From—Date when DST begins each year.

• Day—Day of the week on which DST begins every year.

• Week—Week within the month from which DST begins every year.

• Month—Month of the year in which DST begins every year.

• Time—The time at which DST begins every year.

• To—Date when DST ends each year. For example, DST ends locally every fourth Friday in October at 5:00 a.m.. The parameters are:

• Day—Day of the week on which DST ends every year.

• Week—Week within the month from which DST ends every year.

• Month—Month of the year in which DST ends every year.

• Time—The time at which DST ends every year.

Step 4 Click Apply. The system time values are written to the Running Configuration file.

SNTP Settings

The switch can be configured to synchronize its system clock with an SNTP server specified on the SNTP Settings page.

Cisco Business 220 Series Switches Administration Guide

Time Range

To specify an SNTP server by name, you must first configure the DNS servers on the switch and enable the Main Clock Source (SNTP Servers) on the System Time page.

To add a SNTP server, complete the following steps:

Step 1 Click Administration > Time Settings> SNTP Settings .

Step 2 Enter the following information:

• Host Definition—Select whether to specify the SNTP server by IPv4 address or by host name.

• SNTP Server IP Address/Name—Enter the IPv4 address or hostname of the SNTP server.

Step 3 Click Apply. The SNTP server is added, and the Running Configuration is updated

Time Range

Time ranges can be defined and associated with the following types of commands, so that they are applied only during that time range:

Administration

• Port Stat

• Time-Based PoE

There are two types of time ranges:

• Absolute—This type of time range begins on a specific date or immediately and ends on a specific date or extends infinitely. It is created in the Time Range pages. A periodic element can be added to it.

• Periodic—This type of time range contains a time range element that is added to an absolute range, and begins and ends on a periodic basis. It is defined in the Periodic Range pages.

If a time range includes both absolute and periodic ranges, the process associated with it is activated only if both absolute start time and the periodic time range have been reached. The process is deactivated when either of the time ranges are reached. The device supports a maximum of 20 absolute time ranges.

To ensure that the time range entries take effect at the desired times, the system time must be set.The time-range feature can be used for the following:

• Limit access of computers to the network during business hours (for example), after which the network ports are locked, and access to the rest of the network is blocked (see Configuring Ports and Configuring LAG Settings)

• Limit PoE operation to a specified period.

Add these descriptions for time range

Step 1 Click Administration > Time Settings > Time Range. Step 2 In the Time Range Table, click Add to add a new time range or Edit or Delete to edit or delete an existing one. Step 3 To add a new time range, click Add and configure the following:

• Time Range Name—Enter a name for your time range

Cisco Business 220 Series Switches Administration Guide

Administration

• Absolute Starting Time—Select Immediate or enter a date and time.

• Absolute Ending Time—Select Infinite or enter a date and time

Step 4 Click Apply to apply the new time range settings.

Periodic Time Range

A periodic time element can be added to an absolute time range. This limits the operation to certain time periods within the absolute range.

To add a periodic time range element to an absolute time range:

Step 1 Click Administration > Time Settings > Periodic Range.

The existing periodic time ranges are displayed (filtered per a specific, absolute time range.)

Periodic Time Range

Step 2 Select the absolute time range to which to add the periodic range. Step 3 To add a new periodic time range, click Add.

Step 4 Enter the following fields:

• Periodic Starting Time—Enter the day of the week, and time that the Time Range begins.

• Periodic Ending Time—Enter the day of the week, and time that the Time Range ends.

Step 5 Click Apply. Step 6 Click Time Range to access the Time Range, on page 30.

System Log

This section describes the system logging, which enables the device to generate multiple independent logs. Each log is a set of messages describing system events.

The device generates the following local logs:

• Log sent to the console interface.

• Log written into a cyclical list of logged events in the RAM and erased when the device reboots.

• Log written to a cyclical log-file saved to the Flash memory and persists across reboots.

In addition, you can send messages to remote SYSLOG servers in the form of SNMP traps and SYSLOG messages.

Cisco Business 220 Series Switches Administration Guide

Log Settings

Administration

You can select the events to be logged by severity level. Each log message has a severity level concatenated with a dash (-) on each side. For example, the log message "SYSTEM-5-STARTUP: … " has a severity level of 5, meaning Notice.

The event severity levels are listed from the highest severity to the lowest severity, as follows:

• Emergency—System is not usable.

• Alert—Action is needed.

• Critical—System is in a critical condition.

• Error—System is in error condition.

• Warning—System warning has occurred.

• Notice—System is functioning properly, but a system notice has occurred.

• Informational—Device information.

• Debug—Detailed information about an event.

Selecting a severity level to be stored in a log causes all of the higher severity events to be automatically stored in the log. Lower severity events are not stored in the log. For example, if Warning is selected, all severity levels that are Warning and higher are stored in the log (Emergency, Alert, Critical, Error, and Warning). No events with severity level below Warning are stored (Notice, Informational, and Debug).

To set global log parameters, complete the following steps:

Step 1 Click Administration > System Log > Log Settings.

Step 2 Enter the parameters.

Select to enable message logging.Logging

Syslog Aggregator

Step 3 Click Apply. The Running Configuration file is updated.

Select the aggregation of SYSLOG messages and traps. If enabled, identical and contiguous SYSLOG messages and traps are aggregated over the specified Max. Aggregation Time and sent in a single message. The aggregated messages are sent in the order of their arrival. Each message states the number of times it was aggregated.

Enter the interval of time that SYSLOG messages are aggregated.Max. Aggregation Time

Select the severity levels of the messages to be logged to the RAM.RAM Memory Logging

Select the severity levels of the messages to be logged to the Flash memory.Flash Memory Logging

Remote Log Servers

The Remote Log Servers page enables defining remote SYSLOG servers to which log messages are sent. For each server, you can configure the severity of the messages that it receives.

Cisco Business 220 Series Switches Administration Guide

Administration

To define SYSLOG servers, follow these steps:

Step 1 Click Administration > System Log > Remote Log Servers. Step 2 Click Add.

Step 3 Enter the parameters.

Select whether to identify the remote log server by IP address or name.Server Definition

Select the supported IP format.IP Version

Enter the IP address or domain name of the log server.Log Server IP Address/Name

Enter the UDP port to which the log messages are sent.UDP Port

File Management

Facility

Step 4 Click Apply. The Add Remote Log Server page closes, the SYSLOG server is added, and the Running Configuration

file is updated.

Select a facility value from which system logs are sent to the remote server. Only one facility value can be assigned to a server. If a second facility code is assigned, the first facility value is overridden.

Select the minimum level of system log messages to be sent to the server.Minimum Severity

File Management

A File Management System is an application that is used to store, arrange and access the files that are on your device. The system files are files that contain information, such as: configuration information or firmware images. Various actions can be performed with these files, such as: selecting the firmware file from which the device boots, or copying files to or from an external device, such as an external server.

The following are some of the types of files are found on the device:

• Running Configuration—Contains the parameters currently being used by the device to operate. This file is modified when you change parameter values on the device. If the device is rebooted, the Running Configuration is lost. To preserve any changes you made to the device, you must save the Running Configuration to the Startup Configuration, or another file type.

• Startup Configuration—The parameter values that saved by copying another configuration (usually the Running Configuration) to the Startup Configuration. The Startup Configuration is retained in Flash and is preserved when the device is rebooted. At this time, the Startup Configuration is copied to RAM and identified as the Running Configuration.

• Mirror Configuration—A copy of the Startup Configuration, created by the device when the following conditions exist:

• The device has been operating continuously for 24 hours.

• No configuration changes have been made to the Running Configuration in the previous 24 hours.

• The Startup Configuration is identical to the Running Configuration.

Cisco Business 220 Series Switches Administration Guide

Firmware Operations

Only the system can copy the Startup Configuration to the Mirror Configuration. However, you can copy from the Mirror Configuration to other file types or to another device.

• Backup Files—Manual copies of a files used for protection against system shutdown or for the maintenance of a specific operating state. For instance, you can copy the Mirror Configuration, Startup Configuration, or Running Configuration to a Backup file. The Backup exists in Flash or on a PC or USB drive and is preserved if the device is rebooted.

• Firmware—The program that controls the operations and functionality of the device. More commonly referred to as the image.

• Language File—The dictionary that enables the web-based configuration utility windows to be displayed in the selected language.

• Logging File—SYSLOG messages stored in Flash memory.

Firmware Operations

The Firmware Operations page can be used to:

Administration

• Update or backup the firmware image

• Swap the active image.

The software images of the units in a stack must be identical to ensure proper stack operations. Stack units can be upgraded in any one of the following ways.

Step 1 Click Administration > File Management > Firmware Operations.

The following fields are displayed:

• Active Image—Displays the current, active firmware file.

• Active Image Version Number—Displays the version of the current, active firmware file.

Step 2 Select the Operation Type from the following options:

• Update Firmware

• Backup Firmware

• Swap Image

Step 3 Select the Transfer Method from the following options:

HTTP/HTTPS

For HTTP/HTTPS, enter the file name in the File Name field, or browse to locate and select the file.

For TFTP, proceed with the TFTP Instructions below.TFTP

TFTP Instructions

Configure the following if you selected the TFTP as your copy method for the firmware operations.

Cisco Business 220 Series Switches Administration Guide

Administration

File Operations

TFTP Server IP Address/Name

Select from the following options:

• By IP Address

• By Name

IP Version

Select from the following options:

• IP Version 6

• IP Version 4

Enter the server IP address/name.TFTP Server IP

Address/Name

Enter the name of the source (0 - 128 characters used)Source File Name

Step 4 Click Apply to save your settings.

File Operations

Step 1 Click Administration > File Management > File Operations.

Step 2 Select the Operation Type from the following options:

• Update File

• Backup File

• Duplicate

Step 3 Select the Destination File Type from the following options:

• Running Configuration

• Startup Configuration

• Backup Configuration

• Mirror Configuration

• Logging File

• Language File

Step 4 Select the Copy Method from the following options:

HTTP/HTTPS

For HTTP/HTTPS, enter the file name in the File Name field, or browse to locate and select the file.

For TFTP, proceed with the TFTP Instructions below.TFTP

TFTP Instructions

Cisco Business 220 Series Switches Administration Guide

Configuration File Properties

Configure the following if you selected the TFTP as your update or backup method for the file operations.

Administration

TFTP Server Definition

IP Version

Address/Name

Step 5 In the File name section, click the Browse button to locate and select the file. Step 6 Click Apply.

Select from the following options:

• By IP Address

• By Name

Select from the following options:

• IP Version 6

• IP Version 4

Enter the server IP address/name.TFTP Server IP

Enter the name of the source (0 - 160 characters used)Source File Name

Configuration File Properties

The Configuration File Properties page displays the system files existing in the system.

Step 1 Click Administration > File Management > Configuration File Properties.

Step 2 If required, select either the Startup Configuration, Backup Configuration, or both and click delete icon to delete these

files.

DHCP Auto Configuration

The Auto Configuration/Image Update feature provides a convenient method to automatically configure switches in a network. This process enables the administrator to remotely ensure that the configuration of these devices in the network are up to date.

Step 1 Click Administration > File Management > DHCP Auto Configuration.

Step 2 Configure the following:

Auto Configuration Via DHCP

Step 3 Select the TFTP server settings.

Check to enable the auto configuration via DHCP. The Auto Configuration feature provides a convenient method to automatically configure switches in a network.

Cisco Business 220 Series Switches Administration Guide

Administration

Cisco Business Dashboard Settings

Backup Server Definition

IP Version

IP Address

Note

Step 4 Click Apply to save your settings.

DHCP Auto Configuration / Image is operational only when the IP Address configuration is dynamic.

Select from the following options:

• By IP Address

• By Name

Select from the following options:

• IP Version 6

• IP Version 4

Enter the name of the backup configuration file.Backup TFTP Server IP Address/Name

Enter the name of the backup configuration file (0 - 160 characters used)Backup Configuration File

The address of the last auto configuration address is displayed.Last Auto Configuration TFTP Server

The name of the last auto configuration file is displayed.Last Auto Configuration File Name

Cisco Business Dashboard Settings

Cisco Business Dashboard helps you monitor and manage your Cisco 100 to 500 Series network with the use of the Cisco Business Dashboard Manager. The Cisco Business Dashboard Manager is an add-on that automatically discovers your network, and allows you to configure and monitor all supported Cisco 100 to 500 Series devices such as Cisco switches, routers, and wireless access points.

Note

For detailed instructions on how to setup the Cisco Business Dashboard Manager and Agent, please consult the Cisco Business Dashboard Quick Start Guide.

https://cisco.com/go/cbd-docs

Complete the following steps on the switch graphical user interface (GUI) to enable an Agent connection to a Dashboard, configure the Organization and Network name, and other information required to allow connection to the Dashboard:

Step 1 Click Administration > Cisco Business Dashboard Settings.

Step 2 Configure the following:

Displays the status of the Cisco Business Dashboard connection.Connection Status

Displays the version of the Cisco Business Dashboard call home agent.Agent Version

Cisco Business 220 Series Switches Administration Guide

Plug-n-Play (PNP)

Enabled

Administration

Check to enable call home agent for connecting to Cisco Business Dashboard.Callhome Agent Enabled

Select the logging severity of call home agent.Callhome Agent Log Level

Check to enable connectivity.Dashboard Connection

Enter the organization name of the Cisco Business Dashboard Agent running on the device.Organization Name

Enter the site name of the Cisco Business Dashboard Agent.Network Name

Dashboard Definition

Dashboard Port

Access

Key ID

Access Key

Secret

Step 3 Click Apply to save the setting to the running configuration.

Note

The fields Organization Name, Network Name, Dashboard Address, Key ID cannot be modified if Dashboard Connection setting is enabled. To modify any of these settings clear the Dashboard Connection check box,

click Apply, and redo steps 2-4 above.

Define the address of the Cisco Business Dashboard. Select one of the following:

• By IP address - this option requires you to enter a valid IP address to the IP Address/Name field.

• By Name- this option requires you to enter a hostname to the IP Address/Name field.

Enter the name of IP address of the Cisco Business Dashboard.IP Address/Name

Specify one of the following TCP ports to connect to the Dashboard.

• Use Default (443).

• User Defined (Range: 1-65535). This option is available only if a valid address is entered in the Dashboard Address field.

Specify the key ID to be used for the initial authentication between the Cisco Business Dashboard Agent running on the device and the Cisco Business Dashboard.

Specify the secret to use for authentication. It can be Encrypted or in Plaintext format. The Plaintext format is specified as an alphanumeric string without white-spaces (up to 160 chars). The Key ID and Secret settings must be set together.

Plug-n-Play (PNP)

Installation of new networking devices or replacement of devices can be expensive, time-consuming and error-prone when performed manually. Typically, new devices are first sent to a central staging facility where the devices are unboxed, connected to a staging network, updated with the right licenses, configurations and images; then packaged and shipped to the actual installation location. After these processes are completed, experts must travel to the installation locations to perform the installation. Even in scenarios where the devices are installed in the NOC/Data Center itself, there may not be enough experts for the sheer number of devices. All these issues contribute to delays in deployment and add to the operational costs.

Cisco Business 220 Series Switches Administration Guide

Administration

Plug-n-Play (PNP)

Connecting to PNP Server

To allow the switch to connect to the PnP server, a discovery process takes place, in which the switch discovers the PNP server address/url. There are multiple discovery methods, and they are executed by the switch according to the sequence detailed below. If a PnP server is discovered by a certain method, the discovery process is completed and the rest of the methods are not executed:

1. User configured address - the PnP server url or IP address are specified by the user.

2. Address received from DHCP response option 43 - the PnP server url or IP address are received as part

of option 43 in the DHCP response

3. DNS resolution of hostname "pnpserver" - the PnP server IP addressed is obtained via DNS server

resolution of hostname “pnpserver”.

4. Cisco Plug and Play Connect - a redirection service that allows full “out of the box” PNP server discovery

which runs over HTTPs.

The switch contacts the redirection service using the FQDN “devicehelper.cisco.com”.

Cisco PnP Connect Prerequisites

To allow Cisco Plug and Play Connect operation, the user needs to create devices and controller profiles in Plug and Play Connect (navigate to https://software.cisco.com and click the PnP Connect link). Note that a Cisco Smart Account is required to use PnP Connect. To create or update a Smart Account, see the Administration section of https://software.cisco.com.

In addition, the following prerequisites are required to be met on the switch itself:

• The PNP server was not discovered by the other discovery methods

• The device is able to successfully resolve the name devicehelper.cisco.com (either static configuration or using DNS server)

• System time was set using one of the following methods

• Time was updated by an SNTP server

• Clock was set manually by user

• Time was preserved across resets by Real Time Clock (RTC).

CA-Signed Certificate based Authentication

Cisco distributes certificates signed by a signing authorities in .tar file format and signs the bundle with Cisco Certificate Authority (CA) signature. This certificate bundle is provided by Cisco infoSec for public downloads on cisco.com.

Note

If the PNP server discovery is based on Cisco PnP Connect, the trustpool is downloaded from following:

http://www.cisco.com/security/pki/trs/ios_core.p7b.

If the PNP server discovery is based on DHCP option 43, use the “T<Trust pool CA bundle URL>;” parameter in DHCP option 43 to provide the URL for downloading the trust pool. The certificates from this bundle can

Cisco Business 220 Series Switches Administration Guide

Plug-n-Play (PNP)

Note

Administration

be installed on the Cisco device for server-side validation during SSL handshake. It is assumed that the server uses a certificate, which is signed by one of the CA that is available in the bundle.

The PnP agent uses the built-in PKI capability to validate the certificate bundle. As the bundle is signed by Cisco CA, the agent is capable of identifying a bundle that is tampered before installing the certificates on the device. After the integrity of the bundle is ensured by the agent, the agent installs the certificates on the device. After the certificates are installed on the device, the PnP agent initiates an HTTPs connection to the server without any additional steps from the server.

The device also supports a built in certificate bundle which is installed as part of the bootup process. this bundle can be used to validate PNP server. If a Bundle is downloaded based on Cisco PnP Connect information then the certificates from the downloaded bundle are installed and the certificates based on the built in bundle are uninstalled.

In addition to validating PNP certificate based on installed CA certificate the PNP Agent also validates that the certificate's Common Name/Subject Alternate Name (CN/SAN) matches the hostname/IP address of the PNP server. If they don't match validation of certificate is rejected.

Cisco PnP DHCP Option 43 Usage Guidelines

DHCP option 43 is a vendor specific identifier which is one of the methods that can be used by the PnP agent to locate and connect to the PnP server (see Cisco Plug-n-Play for more information).

The following provides Information on configuration of Option 43 to allow proper configuration on DHCP server.

Option 43 includes the following fields/parameters:

<DHCP-typecode><feature-opcode><version><debug-option>;<arglist>

The <arglist> parameter should use the following syntax:

B<IPaddress type>;I<IPaddress>;J<Port>;K<Transportprotocol>;T<Trust poolCA bundleURL>;Z<SNTP server IP address>

The following table details the description and usage of option 43 fields

DescriptionParameter

DHCP sub-option type. The DHCP sub-option type for PnP is 5.DHCP-typecode

Feature-opcode

Feature operation code – can be either Active (A) or Passive (P). The feature operation code for PnP is Active (A) which implies that PnP agent initiates a connection to the PnP server. If the PnP server cannot be reached, PnP agent retries until it makes a connection.

Version of template to be used by PnP agent. Must be 1.Version

Debug-option

Turns ON or OFF the debug messages during the processing of the DHCP Option 43:

D – debug option is ON ; N – debug option is OFF.

Cisco Business 220 Series Switches Administration Guide

Administration

Plug-n-Play (PNP)

DescriptionParameter

Transport protocol to be used between PnP agent and PnP server:

4 - HTTP or 5 – HTTPS.

IP address type of PnP server IP address specified with the letter code

‘I’:

1 - host , 2- IPv4 , 3 - IPv6

IP address or hostname of PnP server. If hostname is specified, DNS related options must be present in the DHCP server to allow for successful use of hostname.

URL of trust pool CA bundle. You can get the CA bundle from a Cisco Business Dashboard, or from a TFTP server.

• When using Cisco Business Dashboard, use the following URL format:

http://CBD IP address or domain

name/ca/trustpool/CA_bundle_name

• When using TFTP Server, use the following URL format:

tftp://tftp server IP/CA_bundle_name

SNTP server IP address. You must sync the clock before configuring a trust pool.

Note

The switch clock is considered synchronized if it was updated by any SNTP server supported by the switch (by default, user configured or in Z parameter) or set manually by the user. This parameter is required when using trust pool security if the switch can not reach any other SNTP server. For example, for an out-of-the box switch with factory default configuration but no Internet connectivity to reach the default SNTP servers.

Port number http=80 https=443J

Examples for Option 43 usage:

• The following format is used for PnP connection setup using HTTP:

option 43 ascii 5A1N;K4;B2;I10.10.10.3;J80

• The following format is used for PnP connection setup on top of HTTPS, directly using a trust pool. HTTPS can be used when the trust pool CA bundle is downloaded from a Cisco Business Dashboard and the Cisco Business Dashboard server certificate was issued by a 3rd party (not self signed). In the example below “10.10.10.3” is the Cisco Business Dashboard IP address. Optionally, you can specify a domain name:

option 43 ascii

5A1N;K5;B2;I10.10.10.3;J443;Thttp://10.10.10.3/ca/trustpool/ios.p7b;Z10.75.166.1

Cisco Business 220 Series Switches Administration Guide

PNP Settings

To configure PNP settings, follow these steps:

Step 1 Click Administration > PNP > PNP Settings.

Step 2 Configure PNP by entering information in the following fields:

Check to enable.PNP State

Administration

PNP Transport / Settings Definition

IP Version

Select one of the following options for locating configuration information, regarding the transport protocol to use, the PNP server address and the TCP port to use:

• Auto—If this option is selected, the PNP settings are then taken from DHCP option

43. If settings aren’t received from DHCP option 43, the following default values are used: default transport protocol HTTP, DNS name "pnpserver" for PNP server and the port related to HTTP. If the “pnpserver” name is not resolved by DNS, then Cisco Plug and Play Connect service is used, using DNS name “devicehelper.cisco.com”. When selecting the Default Settings option, all fields in PNP Transport section are grayed out. If both PNP agent and DHCP Auto Configuration/Image Update are enabled on device - in case he DHCP reply includes, in addition to option 43, options related to config or image file name, then device ignores received option 43.

• Static—Manually set the TCP port and server settings to use for PNP transport.

Select the transport protocol, HTTP or HTTPS.Transport Protocol

Number of the TCP port. This is entered automatically by the system: 80 for HTTP.TCP Port

Select whether to specify the PNP server By IP address or By name.Server Definition

Select the supported IP format.

• Version 6—IPv6

• Version 4—IPv4

Enter the IP address or domain name of the PNP server.Server IP Address/Name

Step 3 Click Apply. The parameters are copied to the Running Configuration file.

PNP Session

The PNP Session screen displays the value of the PNP parameters currently in effect. The source of the parameter is displayed in parenthesis where relevant.

To display information about PNP parameters, follow these steps:

Click Administration > PNP > PNP Session.

Cisco Business 220 Series Switches Administration Guide

Administration

The following fields are displayed:

Reboot

• Administrative Status—Whether PNP is enabled or not.

• Operational Status—Is PNP operational.

• PNP Agent State—Indicates whether there’s an active PNP session. The possible values are Discovery Wait; Discovery; Not Ready; Disabled; Session; Session Wait.

• Transport Protocol– Displays the PNP agent session information.

• TCP Port—TCP port of the PNP session

• Server Address—IP address of PNP server

Some configuration changes, such as enabling jumbo frame support, require the system to be rebooted before they take effect. However, rebooting the device deletes the Running Configuration, so it’s critical to save the Running Configuration as the Startup Configuration before rebooting. Clicking Apply doesn’t save the configuration to the Startup Configuration. section.

To reboot the device, follow these steps:

Step 1 Click Administration > Reboot. Step 2 Click Reboot to reboot the device.

• Reboot—Reboots the device. Since any unsaved information in the Running Configuration is discarded at reboot,

you must click Saveto preserve the current configuration across the boot process. If the Save option isn’t displayed,

the Running Configuration matches the Startup Configuration and no action is necessary.

• Restore to Factory Defaults—Reboots the device by using the factory default configuration. This process erases all except the Active Image, Inactive Image, Mirror configuration and Localization files.

• Clear Startup Configuration File—Check to clear the startup configuration on the device for the next time it boots up.

Diagnostics

You can use diagnostics to test and verify the functionality of the hardware components of your system (chassis, supervisor engines, modules, and ASICs) while your device is connected to a live network. Diagnostics consists of packet-switching tests that test hardware components and verify the data path and control signals.

Cisco Business 220 Series Switches Administration Guide

Copper Test

Administration

Caution

Step 1 Click Administration > Diagnostics > Copper Test.

Step 2 Select a port on which to run the test. Step 3 Click Copper Test. Step 4 When the message appears, click OK to confirm that the link can go down or Cancel to abort the test. The following

fields are displayed in the Test Results block:

• Test Results—Cable test results. Possible values are:

• Cable Length—Estimated cable length. The cable length is Unknown when the green features are enabled.

• Operational Port Status—Displays whether port is up or down.

When a port is tested, it is set to the down state and communications are interrupted. After the test, the port returns to the Up state. It is not recommended that you run the copper port test on a port you are using to run the web-based switch configuration utility, because communications with that device are disrupted.

To test copper cables attached to ports:, follow these steps

Optical Module Status

The Optical Module Status page displays the operating conditions reported by the SFP (Small Form-factor Pluggable) transceiver.

The following GE SFP (1000Mbps) transceivers are supported:

• MGBLH1: 1000BASE-LH SFP transceiver, for single-mode fiber, 1310 nm wavelength, supports up to 40 km.

• MGBLX1: 1000BASE-LX SFP transceiver, for single-mode fiber, 1310 nm wavelength, supports up to 10 km.

• MGBSX1:1000BASE-SX SFP transceiver, for multimode fiber, 850 nm wavelength, supports up to 550 m.

• MGBT1: 1000BASE-T SFP transceiver for category 5 copper wire, supports up to 100 m.

• GLC-SX-MMD - 1000BASE-SX short wavelength; with DOM

• GLC-LH-SMD - 1000BASE-LX/LH long-wavelength; with DOM

• GLC-BX-D - 1000BASE-BX10-D downstream bidirectional single fiber; with DOM

• GLC-BX-U - 1000BASE-BX10-U upstream bidirectional single fiber; with DOM

• GLC-TE - 1000BASE-T standard

The following XG SFP+ (10,000Mbps) transceivers are supported:

Cisco Business 220 Series Switches Administration Guide

Administration

CPU Utilization

• Cisco SFP-10G-SR

• Cisco SFP-10G-LR

• Cisco SFP-10G-SR-S

• Cisco SFP-10G-LR-S

The following XG passive cables (Twinax/DAC) are supported:

• Cisco SFP-H10G-CU1M

To view the results of optical tests, click Administration > Diagnostics > Optical Module Status.

This page displays the following fields:

• Port—Port number on which the SFP is connected

• Temperature—Temperature (Celsius) at which the SFP is operating

• Voltage—SFPs operating voltage

• Current—SFPs current consumption

• Output Power—Transmitted optical power

• Input Power—Received optical power

• Loss of Signal—Local SFP reports signal loss. Values are True and False

CPU Utilization

To view the current CPU utilization and/or set the refresh rate:

Step 1 Click Administration >Diagnostic > CPU Utilization.

The CPU Input Rate field displays the rate of input frames to the CPU per second. The window contains a graph displaying CPU utilization on the device. The Y axis is percentage of usage, and the X axis is the sample number.

Step 2 Check Enable to enable the CPU Utilization.

Step 3 Select the Refresh Rate (time period in seconds) that passes before the statistics are refreshed. A new sample is created

for each time period.

The window containing a graph displaying CPU utilization on the device is displayed.

Tech-Support Information

This page provides a detailed log of the device status. This is valuable when the technical support are trying to help a user with a problem, since it gives the output of many show commands (including debug command) in a single command.

To view technical support information useful for debugging purposes:

Cisco Business 220 Series Switches Administration Guide

Discovery Bonjour

Step 1 Click Administration> Diagnostics > Tech-Support Information. Step 2 Click Generate.

Administration

Note

Generation of output from this command may take some time. When the information is generated, the tech-support information file will be download to default download directory of browser automatically.

Discovery Bonjour

As a Bonjour client, the device broadcasts Bonjour Discovery protocol packets to directly connected IP subnets. The device can be discovered by a network management system or other third-party applications. By default, Bonjour is enabled on the Management VLAN.

To configure Bonjour, follow these steps:

Step 1 Click Administration > Discovery - Bonjour. Step 2 Check Enable to enable Bonjour Discovery globally. Step 3 Click Apply to update the Running Configuration file.

Note

When Bonjour is enabled, it sends Bonjour Discovery packets to interfaces with IP addresses associated with Bonjour on the Bonjour Discovery Interface Control table.

Discovery LLDP

LLDP is a protocol that enables network managers to troubleshoot and enhance network management in multi-vendor environments. LLDP standardizes methods for network devices to advertise themselves to other systems, and to store discovered information. LLDP enables a device to advertise its identification, configuration, and capabilities to neighboring devices that then store the data in a Management Information Base (MIB).

LDP is a link layer protocol. By default, the device terminates and processes all incoming LLDP packets as required by the protocol. This section describes how to configure LLDP and covers the following topics:

Properties

The Properties page enables entering LLDP general parameters, such as enabling/disabling the feature globally. To enter LLDP properties, proceed as follows:

Step 1 Click Administration > Discovery LLDP > Properties.

Step 2 Enter the parameters.

Cisco Business 220 Series Switches Administration Guide

Administration

Port Settings

Select to enable LLDP on the device (enabled by default).LLDP Status

LLDP Frames Handling

If LLDP isn’t enabled, select one of the following options:

• Filtering—Delete the packet.

• Bridging— (VLAN-aware flooding) Forwards the packet to all VLAN members.

• Flooding—Forward the packet to all VLAN members

Enter the rate in seconds at which LLDP advertisement updates are sent, or use the default.TLV Advertise Interval

Hold Multiplier

Enter the amount of time that LLDP packets are held before the packets are discarded, measured in multiples of the TLV Advertise Interval. For example, if the TLV Advertise Interval is 30 seconds, and the Hold Multiplier is 4, then the LLDP packets are discarded after 120 seconds.

Reinitializing Delay

Enter the time interval in seconds that passes between disabling and reinitializing LLDP, following an LLDP enable/disable cycle.

Transmit Delay

Enter the amount of time in seconds that passes between successive LLDP frame transmissions, due to changes in the LLDP local systems MIB.

Step 3 In the LED-MED Properties Fast Start Repeat Count field, enter the number of times LLDP packets are sent when the

LLDP-MED Fast Start mechanism is initialized. This occurs when a new endpoint device links to the device. For a description of LLDP MED, refer to the LLDP MED Network Policy section.

Step 4 Click Apply. The LLDP properties are added to the Running Configuration file.

Port Settings

The LLDP Port Settings page enables LLDP and SNMP notification per port. The LLDP-MED TLVs can be configured in the LLDP MED Port Settings, on page 49.

To define the LLDP port settings, follow these steps:

Step 1 Click Administration > Discovery LLDP > Port Settings.

This page contains the port LLDP information.

Step 2 Select a port and click Edit.

Step 3 Configure the following fields:

Select the port to edit.Interface

Cisco Business 220 Series Switches Administration Guide

LLDP MED Network Policy

Administration

Administrative Status

Available/Selected Optional TLVs

Select the LLDP publishing option for the port.

• Tx Only—Publishes but doesn’t discover.

• Rx Only—Discovers but doesn’t publish.

• Tx & Rx—Publishes and discovers.

• Disable—Indicates that LLDP is disabled on the port.

Select the options to be published by the device:

• Port Description—Information about the port.

• System Name—System's assigned name.

• System Description—Description of the network entity.

• System Capabilities—Primary functions of the device, and whether these functions are enabled on the device.

• 802.3 MAC-PHY—Duplex and bit rate capability and the current duplex and bit rate settings of the sending device.

• 802.3 Link Aggregation—Whether the link (associated with the port on which the LLDP PDU is transmitted) can be aggregated.

• 802.3 Maximum Frame Size—Maximum frame size capability of the MAC/PHY implementation

• Management IP Address

Step 4 Enter the relevant information, and click Apply. The port settings are written to the Running Configuration file.

LLDP MED Network Policy

The LLDP-MED network policy is a related set of configuration settings for a specific real-time application such as voice, or video. A network policy, if configured, can be included in the outgoing LLDP packets to the attached LLDP media endpoint device. The media endpoint device must send its traffic as specified in the network policy it receives. For example, a policy can be created for VoIP traffic that instructs VoIP phone to:

• Send voice traffic on VLAN 10 as tagged packet and with 802.1p priority 5.

• Send voice traffic with DSCP 46.

Network policies are associated with ports by using the LLDP MED Port Settings, on page 49. An administrator can manually configure one or more network policies and the interfaces where the policies are to be sent. It is the administrator's responsibility to manually create the VLANs and their port memberships according to the network policies and their associated interfaces.

To define an LLDP MED network policy, follow these steps:

Step 1 Click Administration > Discovery LLDP > LLDP MED Network Policy.

Cisco Business 220 Series Switches Administration Guide

Administration

LLDP MED Port Settings

This page contains previously-created network policies.

Step 2 Check Enable next to the LLDP MED Network Policy for Voice Application option to automatically generate and

advertise a network policy for voice application based on the voice VLAN maintained by the device.

Step 3 Click Apply to add this setting to the Running Configuration file. Step 4 To define a new policy, click Add.

Step 5 Enter the values:

• Network Policy Number—Select the number of the policy to be created.

• Application—Select the type of application (type of traffic) for which the network policy is being defined.

• VLAN ID—Enter the VLAN ID to which the traffic must be sent.

• VLAN Tag—Select whether the traffic is Tagged or Untagged.

• User Priority—Select the traffic priority applied to traffic defined by this network policy. This is the CoS value.

• DSCP Value—Select the DSCP value to associate with application data sent by neighbors. This value informs them how they must mark the application traffic they send to the device.

Step 6 Click Apply. The network policy is defined.

Note

You must manually configure the interfaces to include the desired manually-defined network policies for the outgoing LLDP packets using the LLDP MED Port Settings.

LLDP MED Port Settings

The LLDP MED Port Settings page enables configuration of the LLDP-MED TLVs. Network policies are configured using the LLDP MED Network Policy page.

Note

If LLDP-MED Network Policy for Voice Application is enabled and Auto Voice VLAN is in operation, then the device automatically generates an LLDP-MED Network Policy for Voice Application for all the LLDP ports. LLDP-MED enabled and are members of the voice VLAN.

To configure LLDP MED on each port, proceed as follows:

Step 1 Click Administration > Discovery LLDP > LLDP MED Port Settings.

This page displays the following LLDP MED settings for all ports :

• User-Defined Network Policy—Policies are defined for types of traffic in LLDP MED Network Policy, on page

48. The following information is displayed for the policy on the port:

• Active—Is the type of traffic active on the port.

• Application—Type of traffic for which the policy is defined.

• Location—Whether Location TLV is transmitted.

Cisco Business 220 Series Switches Administration Guide

Administration

LLDP Port Status

• PoE—Whether PoE-PSE TLV is transmitted.

• Inventory—Whether Inventory TLV is transmitted.

Step 2 The message at the top of the page indicates whether the generation of the LLDP MED Network Policy for the voice

application is automatic or not. Click on the link to change the mode.

Step 3 To associate additional LLDP MED TLV and/or one or more user-defined LLDP MED Network Policies to a port, select

it, and click Edit.

Step 4 Enter the parameters:

• Interface—Select the interface to configure.

• LLDP MED Status—Enable/disable LLDP MED on this port.

• Selected Optional TLVs—Select the TLVs that can be published by the device by moving them from the Available Optional TLVs list to the Selected Optional TLVs list.

• Selected Network Policies—Select the LLDP MED policies to be published by LLDP by moving them from the Available Network Policies list to the Selected Network Policies list. To include one or more user-defined network

policies in the advertisement, you must also select Network Policy from the Available Optional TLVs.

Note

The following fields must be entered in hexadecimal characters in the exact data format that is defined in the LLDP-MED standard (ANSI-TIA-1057_final_for_publication.pdf):

• Location Coordinate—Enter the coordinate location to be published by LLDP.

• Location Civic Address—Enter the civic address to be published by LLDP.

• Location ECS ELIN—Enter the Emergency Call Service (ECS) ELIN location to be published by LLDP.

Step 5 Click Apply. The LLDP MED port settings are written to the Running Configuration file.

LLDP Port Status

The LLDP Port Status page contains the LLDP global information for every port.

Step 1 To view the LLDP port status, click Administration > Discovery LLDP > LLDP Port Status.

Information for all ports is displayed.

Step 2 Select a specific port and click LLDP Local Information Detail to see the details of the LLDP and LLDP-MED TLVs

sent out to the port.

Step 3 Select a specific port and click LLDP Neighbor Information Detail to see the details of the LLDP and LLDP-MED

TLVs received from the port.

LLDP Port Status Global Information

• Chassis ID Subtype—Type of chassis ID (for example, MAC address).

• Chassis ID—Identifier of chassis. Where the chassis ID subtype is a MAC address, the MAC address of the device appears.

Cisco Business 220 Series Switches Administration Guide

Administration

LLDP Port Status Table

LLDP Local Information

• System Name—Name of device.

• System Description—Description of the device (in alpha-numeric format).

• Supported System Capabilities—Primary functions of the device, such as Bridge, WLAN AP, or Router.

• Enabled System Capabilities—Primary enabled function(s) of the device.

• Port ID Subtype—Type of the port identifier that is shown.

• Interface—Port identifier.

• LLDP Status—LLDP publishing option.

• LLDP MED Status—Enabled or disabled.

• Local PoE ((Power Type, Power Source, Power Priority, Power Value)—Local PoE information advertised.

• Remote PoE (Power Type, Power Source, Power Priority, Power Value)—PoE information advertised by the neighbor.

• # of neighbors—Number of neighbors discovered.

• Neighbor capability of 1st device—Displays the primary functions of the neighbor; for example: Bridge or Router.

LLDP Local Information

To view the LLDP local port status advertised on a port, follow these steps:

Step 1 Click Administration > Discovery LLDP > LLDP Local Information. Step 2 Select the interface and port for which the LLDP local information is to be displayed.

The LLDP Local Information page contains the following fields:

Global

• Chassis ID Subtype—Type of chassis ID. (For example, the MAC address.)

• Chassis ID—Identifier of chassis. Where the chassis ID subtype is a MAC address, the MAC address of the device appears.

• System Name—Name of device.

• System Description—Description of the device (in alpha-numeric format).

• Supported System Capabilities—Primary functions of the device, such as Bridge, WLAN AP, or Router.

• Enabled System Capabilities—Primary enabled function(s) of the device.

• Port ID Subtype—Type of the port identifier that is shown.

• Port ID—Identifier of port.

• Port Description—Information about the port, including manufacturer, product name and hardware/software version.

Cisco Business 220 Series Switches Administration Guide

LLDP Local Information

Management Address

• Address Subtype—Type of management IP address that is listed in the Management Address field, for example, IPv4.

• Address—Returned address most appropriate for management use, typically a Layer 3 address.

• Interface Subtype—Numbering method used for defining the interface number.

• Interface Number—Specific interface associated with this management address.

MAC/PHY Details

• Auto-Negotiation Supported—Port speed auto-negotiation support status. The possible values are True and False.

• Auto-Negotiation Enabled—Port speed auto-negotiation active status. The possible values are True and False.

• Auto-Negotiation Advertised Capabilities—Port speed auto-negotiation capabilities, for example, 1000BASE-T half duplex mode, 100BASE-TX full duplex mode.

• Operational MAU Type—Medium Attachment Unit (MAU) type. The MAU performs physical layer functions, including digital data conversion from the Ethernet interfaces’ collision detection and bit injection into the network; for example, 100BASE-TX full duplex mode.

Administration

802.3 Details

• 802.3 Maximum Frame Size - The maximum supported IEEE 802.3 frame size.

802.3 Link Aggregation

• Aggregation Capability—Indicates whether the interface can be aggregated.

• Aggregation Status—Indicates whether the interface is aggregated.

• Aggregation Port ID—Advertised aggregated interface ID.

MED Details

• Capabilities Supported—MED capabilities enabled on the port.

• Current Capabilities—MED TLVs advertised by the port.

• Device Class—LLDP-MED endpoint device class. The possible device classes are:

• Endpoint Class 1—Indicates a generic endpoint class, offering basic LLDP services.

• Endpoint Class 2—Indicates a media endpoint class, offering media streaming capabilities as well as all Class 1 features.

• Endpoint Class 3—Indicates a communications device class, offering all Class 1 and Class 2 features plus location, 911, Layer 2 switch support and device information management capabilities.

• PoE Device Type—Port PoE type, for example, PD/PSE.

• PoE Power Source—Port’s power source.

• PoE Power Priority—Port’s power priority.

• PoE Power Value—Port’s power value.

Cisco Business 220 Series Switches Administration Guide

Administration

Location Information

Enter the following data structures in hexadecimal as described in section 10.2.4 of the ANSI-TIA-1057 standard:

LLDP Neighbor

• Hardware Revision –Hardware version.

• Firmware Revision—Firmware version.

• Software Revision—Software version.

• Serial Number—Device serial number.

• Manufacturer Name—Device manufacturer name.

• Model Name—Device model name.

• Asset ID—Asset ID.

• Civic—Civic or street address.

• Coordinates—Location map coordinates—latitude, longitude, and altitude.

• ECS ELIN—Device’s Emergency Call Service (ECS) Emergency Location Identification Number (ELIN).

Network Policy Table

• Application Type—Network policy application type, for example, Voice.

• VLAN ID—VLAN ID for which the network policy is defined.

• VLAN Type—VLAN type, Tagged or Untagged, for which the network policy is defined.

• User Priority—Network policy user priority.

• DSCP—Network policy DSCP.

LLDP Neighbor

The LLDP Neighbor Information page contains information that was received from neighboring devices. After timeout (based on the value received from the neighbor Time To Live TLV during which no LLDP PDU was received from a neighbor), the information is deleted.

To view the LLDP neighbors information, follow these steps:

Step 1 Click Administration > Discovery LLDP > LLDP Neighbor . Step 2 Select a local port, and click Go.

The following fields are displayed:

• Local Port—Number of the local port to which the neighbor is connected.

• Chassis ID Subtype—Type of chassis ID (for example, MAC address).

• Chassis ID—Identifier of the 802 LAN neighboring device's chassis.

• Port ID Subtype—Type of the port identifier that is shown.

Cisco Business 220 Series Switches Administration Guide

LLDP Neighbor

• Port ID—Identifier of port.

• System Name—Published name of the device.

• Time to Live—Time interval (in seconds) after which the information for this neighbor is deleted.

Step 3 Select a local port, and click Details.

The LLDP Neighbor Information page contains the following fields:

Port Details

• Local Port—Port number.

Basic Details

• Chassis ID Subtype—Type of chassis ID (for example, MAC address).

• Chassis ID—Identifier of the 802 LAN neighboring device chassis.

• Port ID Subtype—Type of the port identifier that is shown.

• Port ID—Identifier of port.

Administration

• System Name—Name of system that is published.

• System Description—Description of the network entity (in alpha-numeric format). This includes the system name and versions of the hardware, operating system, and networking software supported by the device. The value equals the sysDescr object.

• Supported System Capabilities—Primary functions of the device. The capabilities are indicated by two octets. Bits 0 through 7 indicate Other, Repeater, Bridge, WLAN AP, Router, Telephone, DOCSIS cable device, and station, respectively. Bits 8 through 15 are reserved.

• Enabled System Capabilities—Primary enabled function(s) of the device.

Management Address Table

• Address Subtype—Managed address subtype; for example, MAC or IPv4.

• Address—Managed address.

• Interface Subtype—Port subtype.

• Interface Number—Port number.

MAC/PHY Details

• Auto-Negotiation Supported—Port speed auto-negotiation support status. The possible values are True and False.

• Auto-Negotiation Enabled—Port speed auto-negotiation active status. The possible values are True and False.

• Auto-Negotiation Advertised Capabilities—Port speed auto-negotiation capabilities, for example, 1000BASE-T half duplex mode, 100BASE-TX full duplex mode.

802.3 Details

Cisco Business 220 Series Switches Administration Guide

Administration

802.3 Link Aggregation

MED Details

LLDP Neighbor

• 802.3 Maximum Frame Size—Advertised maximum frame size that is supported on the port.

• Aggregation Capability—Indicates if the port can be aggregated.

• Aggregation Status—Indicates if the port is currently aggregated.

• Aggregation Port ID—Advertised aggregated port ID.

• Capabilities Supported—MED capabilities enabled on the port.

• Current Capabilities—MED TLVs advertised by the port.

• Device Class—LLDP-MED endpoint device class. The possible device classes are:

• Endpoint Class 1—Indicates a generic endpoint class, offering basic LLDP services.

• Endpoint Class 2—Indicates a media endpoint class, offering media streaming capabilities as well as all Class 1 features.

• Endpoint Class 3—Indicates a communications device class, offering all Class 1 and Class 2 features plus location, 911, Layer 2 switch support and device information management capabilities.

• PoE Device Type—Port PoE type, for example, PD/PSE.

• PoE Power Source—Port’s power source.

• PoE Power Priority—Port’s power priority.

• PoE Power Value—Port’s power value.

• Hardware Revision –Hardware version.

• Firmware Revision—Firmware version.

• Software Revision—Software version.

• Serial Number—Device serial number.

• Manufacturer Name—Device manufacturer name.

• Model Name—Device model name.

• Asset ID—Asset ID.

802.1 VLAN and Protocol

• PVID—Advertised port VLAN ID.

VLAN ID Table

• VID—Port and Protocol VLAN ID.

• VLAN Name—Advertised VLAN names.

Location Information

Enter the following data structures in hexadecimal as described in section 10.2.4 of the ANSI-TIA-1057 standard:

Cisco Business 220 Series Switches Administration Guide

LLDP Statistics

• Civic—Civic or street address.

• Coordinates—Location map coordinates—latitude, longitude, and altitude.

• ECS ELIN—Device’s Emergency Call Service (ECS) Emergency Location Identification Number (ELIN).

Network Policy Table

• Application Type—Network policy application type, for example, Voice.

• VLAN ID—VLAN ID for which the network policy is defined.

• VLAN Type—VLAN type, Tagged or Untagged, for which the network policy is defined.

• User Priority—Network policy user priority.

• DSCP—Network policy DSCP.

Step 4 Click Refresh to refresh the data in the LLDP Neighbor table.

Administration

LLDP Statistics

The LLDP Statistics page displays LLDP statistical information per port.

To view the LLDP statistics, follow these steps:

Step 1 Click Administration > Discovery LLDP > LLDP Statistics.

For each port, the fields are displayed:

• Interface—Identifier of interface.

• Tx Frames (Total)—Number of transmitted frames.

• Rx Frames

• Total—Number of received frames

• Discarded—Total number of received frames that discarded

• Errors—Total number of received frames with errors

• Rx TLVs

• Discarded—Total number of received TLVs that discarded

• Unrecognized—Total number of received TLVs that unrecognized.

• Neighbor's Information Deletion Count—Number of neighbor age outs on the interface.

Step 2 Click Refresh to view the latest statistics.

Cisco Business 220 Series Switches Administration Guide

Administration

LLDP Overloading

LLDP adds information as LLDP and LLDP-MED TLVs into the LLDP packets. LLDP overload occurs when the total amount of information to be included in an LLDP packet exceeds the maximum PDU size supported by an interface.

The LLDP Overloading page displays the number of bytes of LLDP/LLDP-MED information, the number of available bytes, and the overloading status of every interface.

To view LLDP overloading information:

Step 1 Click Administration > Discovery LLDP > LLDP Overloading.

In the LLDP Overloading Table, the following information is displayed for each port:

• Interface—Port identifier.

• Total Bytes In-Use—Total number of bytes of LLDP information in each packet

• Available Bytes Left—Total amount of available bytes left for other LLDP information in each packet.

LLDP Overloading

• Status—Whether TLVs are being transmitted or if they are overloaded.

Step 2 To view the overloading details for a port, select it and click Details.

This page contains the following information for each TLV sent on the port:

• LLDP Mandatory TLVs

• Size (Bytes)—Total mandatory TLV byte size

• Status—If the mandatory TLV group is being transmitted, or if the TLV group was overloaded.

• LLDP MED Capabilities

• Size (Bytes)—Total LLDP MED capabilities packets byte size

• Status—If the LLDP MED capabilities packets sent, or if they overloaded.

• LLDP MED Location

• Size (Bytes)—Total LLDP MED location packets byte size

• Status—If the LLDP MED locations packets sent, or if they overloaded.

• LLDP MED Network Policy

• Size (Bytes)—Total LLDP MED network policies packets byte size

• Status—If the LLDP MED network policies packets sent, or if they overloaded.

• LLDP MED Extended Power via MDI

• Size (Bytes)—Total LLDP MED extended power via MDI packets byte size.

• Status—If the LLDP MED extended power via MDI packets sent, or if they overloaded.

• 802.3 TLVs

Cisco Business 220 Series Switches Administration Guide

Discovery - CDP

• LLDP Optional TLVs

• LLDP MED Inventory

• Total

Administration

Size (Bytes)—Total LLDP MED 802.3 TLVs packets byte size.•

• Status—If the LLDP MED 802.3 TLVs packets sent, or if they overloaded.

• Size (Bytes)—Total LLDP MED optional TLVs packets byte size.

• Status—If the LLDP MED optional TLVs packets sent, or if they overloaded.

• Size (Bytes)—Total LLDP MED inventory TLVs packets byte size.

• Status—If the LLDP MED inventory packets sent, or if they overloaded.

• Total (Bytes)—Total number of bytes of LLDP information in each packet.

• Available Bytes Left—Total number of available bytes left to send for additional LLDP information in each packet.

Discovery - CDP

Cisco Discovery Protocol is a Layer 2, media-independent, and network-independent protocol that networking applications use to learn about nearby, directly connected devices. Cisco Discovery Protocol is enabled by default. Each device configured for Cisco Discovery Protocol advertises at least one address at which the device can receive messages and sends periodic advertisements (messages) to the well-known multicast address 01:00:0C:CC:CC:CC. Devices discover each other by listening at that address. They also listen to messages to learn when interfaces on other devices are up or go down.

Advertisements contain time-to-live information, which indicates the length of time a receiving device should hold Cisco Discovery Protocol information before discarding it. Advertisements supported and configured in Cisco software are sent, by default, every 60 seconds on interfaces that support Subnetwork Access Protocol (SNAP) headers. Cisco devices never forward Cisco Discovery Protocol packets. Cisco devices that support Cisco Discovery Protocol store the information received in a table. Information in this table is refreshed every time an advertisement is received, and information about a device is discarded after three advertisements from that device are missed.

This section describes how to configure CDP.

Properties

Similar to LLDP, the Cisco Discovery Protocol (CDP) is a link layer protocol for directly connected neighbors to advertise themselves and their capabilities to each other. Unlike LLDP, CDP is a Cisco proprietary protocol. To configure the CDP properties, complete the following steps:

Step 1 Click Administration > Discovery - CDP > Properties.

Cisco Business 220 Series Switches Administration Guide

Administration

Step 2 Enter the parameters.

Properties

Select to enable CDP on the device.CDP Status

CDP Frames Handling

CDP Voice VLAN Advertisement

CDP Mandatory TLVs Validation

CDP Hold Time

If CDP is not enabled, select the action to be taken if a packet that matches the selected criteria is received:

• Bridging—(VLAN-aware flooding) Forwards the packet based on the VLAN

• Filtering—Deletes the packet

• Flooding—(VLAN-unaware flooding) Forwards incoming CDP packets to all the ports excluding the ingress ports

Select to enable the device to advertise the voice VLAN in CDP on all of the ports that are CDP enabled, and are member of the voice VLAN.

If selected, incoming CDP packets not containing the mandatory TLVs are discarded and the invalid error counter is incremented.

Select the version of CDP to use.CDP Version

Amount of time that CDP packets are held before the packets are discarded, measured in multiples of the TLV Advertise Interval. For example, if the TLV Advertise Interval is 30 seconds, and the Hold Multiplier is 4, then the CDP packets are discarded after 120 seconds. The following options are possible:

• Use Default—Use the default time (180 seconds)

• User Defined—Enter the time in seconds.

CDP Transmission Rate

Source Interface

Syslog Voice VLAN Mismatch

Syslog Native VLAN Mismatch

The rate in seconds at which CDP advertisement updates are sent. The following options are possible:

• Use Default—Use the default rate (60 seconds)

• User Defined—Enter the rate in seconds.

Select the format of the device ID (MAC address or serial number, hostname).Device ID Format

IP address to be used in the TLV of the frames. The following options are possible:

• Use Default—Use the IP address of the outgoing interface.

• User Defined—Use the IP address of the interface (in the Interface field) in the address TLV.

IF User Defined was selected for Source Interface, select the interface.Interface

Check to send a SYSLOG message when a voice VLAN mismatch is detected. This means that the voice VLAN information in the incoming frame does not match what the local device is advertising.

Check to send a SYSLOG message when a native VLAN mismatch is detected. This means that the native VLAN information in the incoming frame does not match what the local device is advertising.

Cisco Business 220 Series Switches Administration Guide

CDP Interface Settings

Administration

Syslog Duplex Mismatch

Check to send a SYSLOG message when duplex information is mismatched. This means that the duplex information in the incoming frame does not match what the local device is advertising.

Step 3 Click Apply. The CDP properties are defined.

CDP Interface Settings

The Interface Settings page enables you to enable/disable CDP per port. By setting these properties, it’s possible to select the types of information to be provided to devices that support the protocol.

To define the CDP interface settings:

Step 1 Click Administration > Discovery - CDP > Interface Settings.

This page displays the following CDP information for each interface.

• Entry No.—Port identifier.

• CDP Status—CDP publishing option for the port.

• Reporting Conflicts with CDP Neighbors—Status of the reporting options that are enabled/disabled in the Edit page (Voice VLAN/Native VLAN/Duplex).

• No. of Neighbors—Number of neighbors detected.

The bottom of the page has four buttons:

• Copy Settings—Select to copy a configuration from one port to another.

• Edit—Fields explained in Step 2 below.

• CDP Local Information Details—Takes you to the CDP Local Information, on page 61 .

• CDP Neighbor Information Details—Takes you to the CDP Neighbors Information, on page 62.

Step 2 Select a port and click Edit.

This page provides the following fields:

• Interface—Select the interface to be defined.

• CDP Status—Select to enable/disable the CDP publishing option for the port.

Note

The next three fields are operational when the device has been set up to send traps to the management station.

• Syslog Voice VLAN Mismatch—Select to enable sending a SYSLOG message when a voice VLAN mismatch is detected. This means that the voice VLAN information in the incoming frame doesn’t match what the local device is advertising.

• Syslog Native VLAN Mismatch—Select to enable sending a SYSLOG message when a native VLAN mismatch is detected. This means that the native VLAN information in the incoming frame doesn’t match what the local device is advertising.

Cisco Business 220 Series Switches Administration Guide

Administration

CDP Local Information

• Syslog Duplex Mismatch—Select to enable sending a SYSLOG message when duplex information mismatch is detected. This means that the duplex information in the incoming frame doesn’t match what the local device is advertising.

Step 3 Enter the relevant information, and click Apply. The port settings are written to the Running Configuration.

CDP Local Information

To view information that is advertised by the CDP protocol about the local device:

Click Administration > Discovery - CDP > CDP Local Information. The following fields are displayed:

Number of the local port.Interface

Displays whether CDP is enabled or not.CDP State

Device ID TLV

Appliance TLV

• Device ID Type—Type of the device ID advertised in the device ID TLV

• Device ID—Device ID advertised in the device ID TLV

System Name—System name of the device.System Name TLV

Address—IP addresses (advertised in the device address TLV).Address TLV

Port ID—Identifier of port advertised in the port TLV.Port TLV

Identifier of port advertised in the port TLV.Port ID

Capabilities—Capabilities advertised in the port TLV).Capabilities TLV

Version—Information about the software release on which the device is running.Version TLV

Platform—Identifier of platform advertised in the platform TLV.Platform TLV

Native VLAN—The native VLAN identifier advertised in the native VLAN TLV.Native VLAN TLV

Duplex—Whether port is half or full-duplex advertised in the full/half duplex TLV.Full/Half Duplex TLV

• Appliance ID—Type of device attached to port advertised in the appliance TLV

• Appliance VLAN ID—VLAN on the device used by the appliance, for instance if the appliance is an IP phone, this is the voice VLAN.

Extended Trust TLV

CoS for Untrusted Ports TLV

Extended Trust—Enabled indicates that the port is trusted, and the packets received are marked. In this case, packets received on such a port aren’t re-marked. Disabled indicates that the port isn’t trusted in which case, the following field is relevant.

CoS for Untrusted Ports—If Extended Trust is disabled on the port, this field displays the Layer 2 CoS value, meaning, an 802.1D/802.1p priority value. This is the COS value with which all packets received on an untrusted port are remarked by the device.

Cisco Business 220 Series Switches Administration Guide

CDP Neighbors Information

Administration

Power Available TLV (Only applicable for PoE models)

CDP Neighbors Information

The CDP Neighbors Information page displays CDP information received from neighboring devices.

Information is deleted, after timeout (based on the value received from Time To Live TLV during which no CDP PDU was received).

• Request ID—Last power request ID received echoes the Request-ID field last received in a Power Requested TLV. It’s 0 if no Power Requested TLV was received since the interface last transitioned to Up.

• Power Management ID—Value incremented by 1 (or 2, to avoid 0) each time any one of the following events occurs:

Available Power or Management Power Level change

A Power Requested TLV is received with a Request-ID that is different from the last-received set.

The interface transitions to Down.

• Available Power—Amount of power consumed by port

• Management Power Level—Displays the supplier's request to the pod device.

To view the CDP neighbors information, proceed as follows:

Step 1 Click Administration > Discovery - CDP > CDP Neighbor Information. Step 2 To select a filter, check the Filter checkbox, select a Local interface, and click Go.

The filter is applied on the list, and Clear Filter is activated to enable stopping the filter.

The CDP Neighbor Information page contains the following fields for the link partner (neighbor):

Neighbors device ID.Device ID

Number of the local port to which the neighbor is connected.Local Interface

CDP protocol version.Advertisement Version

Time interval (in seconds) after which the information for this neighbor is deleted.Time to Live

Capabilities advertised by neighbor.Capabilities

Information from Platform TLV of neighbor.Platform

Outgoing interface of the neighbor.Neighbor Interface

Step 3 Select a device, and click Details.

This page contains the following fields about the neighbor (actual field display depends on what the neighbor is advertising):

Neighbors device ID.Device ID

Cisco Business 220 Series Switches Administration Guide

Administration

CDP Statistics

Number of the local port to which the neighbor is connected.Local Interface

CDP protocol version.Advertisement Version

Time interval (in seconds) after which the information for this neighbor is deleted.Time to Live (sec)

Capabilities advertised by neighbor.Capabilities

Information from Platform TLV of neighbor.Platform

Outgoing interface of the neighbor.Neighbor Interface

Neighbors native VLAN.Native VLAN

Whether neighbors interface is half or full-duplex.Duplex

Neighbors addresses.Addresses

Amount of power consumed by neighbor on the interface.Power Drawn

Neighbors software version.Version

Note

Disconnects on the Clear Table button all connected devices if from CDP.

CDP Statistics

The CDP Statistics page displays information regarding CDP frames that sent or received from a port. CDP packets are received from devices attached to the switches interfaces, and are used for the Smartport feature.

To view CDP statistics, follow these steps:

Step 1 Click Administration > Discovery- CDP > CDP Statistics.

The following fields are displayed for every interface:

Packets Received/Packets Transmitted:

• Version 1—Number of CDP version 1 packets received/transmitted.

• Version 2—Number of CDP version 2 packets received/transmitted.

• Total—Total number of CDP packets received/transmitted.

CDP Error Statistics:

• Illegal Checksum—Number of packets received with illegal checksum value.

• Other Errors—Number of packets received with errors other than illegal checksums.

• Neighbors Over Maximum—Number of times that packet information couldn’t be stored in cache because of lack of room.

Cisco Business 220 Series Switches Administration Guide

Administration

Locate Device

Step 2 To clear all counters on all interfaces, click Clear All Interface Counters. To clear all counters on an interface, select

it and click Clear Interface Counters.

Locate Device

This feature enables flashing all network port LEDs on a specific device in the network to locate the device physically. This feature is useful for locating a device within a room with many interconnected devices. When this feature is activated, all network port LEDs on the device flash for a configured duration (one minute by default).

Step 1 Click Administration > Locate Device.

Step 2 Enter values in the following fields:

• Duration—Enter for how long (in seconds) the port’s LEDs flash.

• Remaining Time—This field is only displayed if the feature is currently activated. It displays the remaining time during which the LED flashes.

Step 3 Click Start to activate the feature.

When the feature is activated the Start button is replaced by the Stop button, which allows you to stop the LED blinking before the defined timer expires.

Ping

The Ping utility tests if a remote host can be reached and measures the round-trip time for packets sent.

Ping operates by sending Internet Control Message Protocol (ICMP) echo request packets to the target host and waiting for an ICMP response, sometimes called a pong. It measures the round-trip time and records any packet loss.

To ping a host, follow these steps:

Step 1 Click Administration > Ping.

Step 2 Configure ping by entering the fields:

DescriptionOption

Host Definition

Select whether to specify the source interface by its IP address or name. This field influences the interfaces that are displayed in the Source IP field, as described below.

IP Version

If the source interface is identified by its IP address, select either IPv4 or IPv6 to indicate that it will be entered in the selected format.

Enter the IP address or hostname of the host to be pinged.Host IP Address/Name

Cisco Business 220 Series Switches Administration Guide

Administration

Traceroute

DescriptionOption

Number of Pings

Step 3 Click Activate Ping to ping the host. The ping status appears and a message is added to the list of messages, indicating

the result of the ping operation.

Step 4 View the results of ping in the Ping Counters and Status section of the page:

• Number of Sent Packets—Number of packets sent by ping

• Number of Received Packets—Number of packets received by ping

• Packet Loss—Percentage of packets lost in ping process

• Minimum Round Trip Time—Shortest time for packet to return

• Maximum Round Trip Time—Longest time for packet to return

• Average Round Trip Time—Average time for packet to return

• Status—Fail, Ping aborted, Ping in progress by another process, or succeed.

The number of times the ping operation is performed. Select to use the default or specify your own value.

Traceroute

Traceroute discovers the IP routes forwarded by sending an IP packet to the target host and back to the device. The Traceroute page shows each hop between the device and a target host, and the round-trip time to each such hop.

Step 1 Click Administration > Traceroute.

Step 2 Configure Traceroute by entering information in the following fields:

• Host Definition—Select whether hosts are identified by their IP address or name.

• Host IP Address/Name—Enter the host address or name.

• TTL—Enter the maximum number of hops that Traceroute permits. This is used to prevent a case where the sent frame gets into an endless loop. The Traceroute command terminates when the destination is reached or when this

value is reached. To use the default value (30), select Use Default.

Step 3 Click Activate Traceroute. The operation is performed.

Note

A pop-up will appear indicating if you would like to stop the traceroute. Click Stop Traceroute to stop the

process.

Cisco Business 220 Series Switches Administration Guide

Traceroute

Administration

Cisco Business 220 Series Switches Administration Guide

Port Management

This chapter contains the following sections:

Port Settings

The Port Settings page displays the global and per port setting of all the ports. Here, you can select and configure the desired ports from the Edit Port Settings page.

To configure port settings, follow these steps:

CHAPTER 5

• Port Settings, on page 67

• Error Recovery Settings, on page 70

• Loopback Detection Settings, on page 71

• Link Aggregation, on page 71

• Power over Ethernet, on page 75

• Green Ethernet, on page 78

Step 1 Click Port Management > PortSettings.

The port settings are displayed for all ports.

Step 2 Enter the following fields:

• Jumbo Frames—Check to support packets of up to 10 KB in size. If Jumbo Frames isn’t enabled (default), the system supports packet size up to 1522 bytes.

Step 3 Click Apply to update the global setting.

Jumbo frames configuration changes take effect only after the Running Configuration is explicitly saved to the Startup Configuration File using the File Operations, on page 35, and the device is rebooted.

Step 4 To update the port settings, select the desired port, and click Edit.

Step 5 Modify the following parameters:

Select the port number.Interface

Cisco Business 220 Series Switches Administration Guide

Port Settings

Port Management

Description

Operational Status

Time Range

State

Auto Negotiation

Negotiation

Administrative Port Speed

Enter the port user-defined name or comment.

Note

The Interface and Port Description are displayed on the main page in the Port column.

Select whether the port must be Up or Down when the device is rebooted.Administrative Status

Displays whether the port is currently Up or Down. If the port is down because of an error, the description of the error is displayed

Select to enable the time range during which the port is in Up state. When the time range isn’t active, the port is in shutdown. If a time range is configured, it is effective only when the port is administratively Up.

Select the profile that specifies the time range.Time Range Name

Range State—Displays whether the time range is currently active or inactive.Operational Time Range

Select to enable auto-negotiation on the port. Auto-negotiation enables a port to advertise its transmission speed, duplex mode, and Flow Control abilities to the port link partner.

Displays the current auto-negotiation status on the port.Operational Auto

Select the speed of the port. The port type determines the available speeds. You can designate Administrative Speed only when port auto-negotiation is disabled.

Administrative Duplex Mode

Displays the current port speed that is the result of negotiation.Operational Port Speed

Select the port duplex mode. This field is configurable only when auto-negotiation is disabled, and the port speed is set to 10M or 100M. At port speed of 1G or 10G, the mode is always full-duplex. The possible options are:

• Half—The interface supports transmission between the device and the client in only one direction at a time.

• Full—The interface supports transmission between the device and the client in both directions simultaneously.

Displays the ports current duplex mode.Operational Duplex Mode

Cisco Business 220 Series Switches Administration Guide

Port Management

Port Settings

Auto Advertisement Speed

Operational Advertisement

Auto Advertisement Duplex

Select the capabilities advertised by auto-negotiation when it is enabled.

Note

Not all options are relevant for all devices.

The options are:

• All Speed—All port speeds and duplex mode settings can be accepted.

• 10M—10 Mbps speed

• 100M—100 Mbps speed

• 1000M—1000 Mbps speed

• 10M/100M—10 and 100 Mbps speeds

• 10G—10 Gbps speed

Displays the capabilities currently published to the ports neighbor. The possible options are those specified in the Administrative Advertisement field.

Select the duplex mode to be advertised by the port. The options are:

• All Duplex—All duplex modes can be accepted.

• Full—The interface supports transmission between the switch and the client in both directions simultaneously.

• Half—The interface supports transmission between the switch and the client in only one direction at a time

Back Pressure

Flow Control

Protected Port

Select the Back Pressure mode on the port (used with Half Duplex mode) to slow down the packet reception speed when the device is congested. Selecting this option disables the remote port, preventing it from sending packets by jamming the signal.

Enable or disable 802.3x Flow Control, or enable the auto-negotiation of Flow Control on the port (only when in Full Duplex mode). Flow control auto-negotiation can’t be enabled on combo ports.

Check Enable to make this a protected port. A protected port is also referred as a Private VLAN Edge (PVE). The features of a protected port are as follows:

• Protected Ports provide Layer 2 isolation between interfaces (Ethernet ports and Link Aggregation Groups (LAGs)) that share the same Broadcast domain (VLAN).

• Packets received from protected ports can be forwarded only to unprotected egress ports. Protected port filtering rules are also applied to packets that are forwarded by software, such as snooping applications.

• Port protection is not subject to VLAN membership. Devices connected to protected ports are not allowed to communicate with each other, even if they are members of the same VLAN.

• Both ports and LAGs can be defined as protected or unprotected.Both ports and LAGs can be defined as protected or unprotected.

Cisco Business 220 Series Switches Administration Guide

Error Recovery Settings

Port Management

Member in LAG

Step 6 Click Apply. The Port Settings are written to the Running Configuration file.

If the port is a member of a LAG, the LAG number appears; otherwise this field is left blank.

Error Recovery Settings

The Error Recovery Settings page enables the user to automatically reactivate a port that has been shut down because of a device error that occurs after the Automatic Recovery Interval has passed.

To configure the error recovery settings, complete these steps:

Step 1 Click Port Management > ErrorRecovery Settings.

Step 2 Enter the following fields:

• Automatic Recovery Interval—Specify the time delay for automatic error recovery, if enabled, after a port is shut down.

• Automatic ErrDisable Recovery

• 802.1x Single Host Violation—Select to enable automatic error recovery when the port is shut down by 802.1x.

• ACL —Select to enable automatic error recovery mechanism by an ACL action.

• BPDU—Enable automatic recovery when the port is shut down by STP Loopback Guard.

• Broadcast Flood—Select to enable automatic error recovery from the Broadcast flood

• DHCP Rate Limit—Check Enable to enable the timer to recover from the DHCP rate limit causes.

• ARP Inspection—Check Enable to the timer to recover from the ARP inspection causes

• PoE— Select Enable to enable the timer to recover from the Power over Ethernet (PoE) causes

• Loopback Detection—Select to enable error recovery mechanism for ports shut down by loopback detection.

• Port Security—Select to enable automatic error recovery when the port is shut down for port security violations.

• Self Loop—Select Enable to enable the timer to recover from the self loop cause

• Unicast Flood— Select Enable to enable the timer to recover from the Unicast flood causes.

• Unknown Multicast Flood— Select Enable to enable the timer to recover from the unknown Multicast flood causes.

Step 3 Click Apply to update the global setting.

To manually reactivate a port:

Step 4 Click Port Management > ErrorRecovery Settings.

The list of inactivated interfaces along with their Suspension Reason is displayed.

Cisco Business 220 Series Switches Administration Guide

Port Management

Loopback Detection Settings

Step 5 To filter the Suspension Reason, select a reason and click Go. Then, only the interfaces that are suspended for that reason

are displayed in the table.

Step 6 Select the interface to be reactivated. Step 7 Click Reactivate.

Loopback Detection Settings

Loopback Detection (LBD) provides protection against loops by transmitting loop protocol packets out of ports on which loop protection has been enabled. When the switch sends out a loop protocol packet, and then receives the same packet, it shuts down the port that received the packet.

Loopback Detection operates independently of STP. After a loop is discovered, the port that received the loops is placed in the Shut Down state. A trap is sent and the event is logged. Network managers can define a Detection Interval that sets the time interval between LBD packets.

To enable and configure LBD, follow these steps:

Step 1 Click Port Management > Loopback Detection Settings. Step 2 Select Enable in the Loopback Detection to enable the feature.

Step 3 Enter the Detection Interval. This is the interval between transmission of LBD packets. Step 4 Click Apply to save the configuration to the Running Configuration file.

The following fields are displayed for each interface, regarding the Loopback Detection State:

• Administrative—Loopback detection is enabled.

• Operational—Loopback detection is enabled but not active on the interface.

Step 5 Select whether to enable LBD on ports or LAGS in the Interface Type equals field in the filter. Step 6 Select the ports or LAGs on which LBD is to be enabled and click Edit. Step 7 Select the settings for the chosen Interface. Next, check Enablein the Loopback Detection State field for the port or LAG

selected.

Step 8 Click Apply to save the configuration to the Running Configuration file.

Link Aggregation

Link aggregation applies to various methods of combining multiple network connections in parallel in order to increase throughput beyond what a single connection could sustain. It provides redundancy in case one of the links should fail.

Two types of LAGs are supported:

• Static—The ports in the LAG are manually configured. A LAG is static if LACP is disabled on it. The group of ports assigned to a static LAG are always active members. After a LAG is manually created,

Cisco Business 220 Series Switches Administration Guide

LAG Management

the LACP option can’t be added or removed, until the LAG is edited and a member is removed (which can be added back prior to applying); the LACP button then become available for editing.

• Dynamic—A LAG is dynamic if LACP is enabled on it. The group of ports assigned to dynamic LAG are candidate ports. LACP determines which candidate ports are active member ports. The nonactive candidate ports are standby ports ready to replace any failing active member ports.

This section describes how to configure LAGs.

LAG Management

Link Aggregation Control Protocol (LACP) is part of the IEEE specification (802.3ad) that enables you to bundle several ports together to form a single logical channel (LAG). LAGs multiply bandwidth, increase port flexibility, and provide link redundancy between two devices.

To select the load-balancing algorithm of the LAG, follow these steps:

Step 1 Click Port Management > Link Aggregation > LAG Management.

Step 2 Select one of the following Load Balance Algorithm:

Port Management

• MAC Address—Perform load balancing by source and destination MAC addresses on all packets.

• IP/MAC Address—Perform load balancing by the IP addresses on the IP packets, and by MAC addresses on non-IP packets

Step 3 Click Apply. The Load Balance Algorithm is saved to the Running Configuration file.

To define the member or candidate ports in a LAG.

Step 4 Select the LAG to be configured, and click Edit.

Step 5 Enter the values for the following fields:

• LAG—Select the LAG number.

• LAG Name—Enter the LAG name or a comment.

• LACP—Select to enable LACP on the selected LAG. This makes it a dynamic LAG. This field can only be enabled after moving a port to the LAG in the next field.

• Port List—Move the ports that are assigned to the Port List LAGs to the LAG Members. Up to eight ports per static LAG can be assigned, and 16 ports can be assigned to a dynamic LAG.

Step 6 Click Apply. LAG membership is saved to the Running Configuration file.

LAG Settings

Cisco Business 220 Series Switches Administration Guide

The LAG Settings page displays a table of current settings for all LAGs. You can configure the settings of selected LAGs, and reactivate suspended LAGs by launching the Edit LAG Settings page.

To configure the LAG settings or reactivate a suspended LAG:

Port Management

Step 1 Click Port Management > Link Aggregation > LAG Settings.

The LAGs in the system are displayed.

Step 2 Select a LAG, and click Edit.

Step 3 Enter the values for the following fields:

DescriptionOption

Select the LAG ID number.LAG

Displays the port type that comprises the LAG.LAG Type

Enter the LAG name or a comment.Description

Set the selected LAG to be Up or Down.Administrative Status

LAG Settings

Time Range

Time Range Name

Range State

Auto Negotiation

Speed

Back Pressure

Speed

Select to enable the time range during which the port is in Up state. When the time range is not active, the port is in shutdown. If a time range is configured, it is effective only when the port is administratively up.

Select the profile that specifies the time range. If a time range is not yet defined, click Edit to

go to Time Range, on page 30

Displays whether the LAG is currently operating.Operational Status

Displays whether the time range is currently active or inactive.Operational Time

Enables or disable auto-negotiation on the LAG. Auto-negotiation is a protocol between two link partners that enables a LAG to advertise its transmission speed and flow control to its partner (the Flow Control default is disabled). It is recommended to keep auto-negotiation enabled on both sides of an aggregate link, or disabled on both sides, while ensuring that link speeds are identical.

Select the speed of the ports in the LAG.Administrative Port

Check the Enable check box in the Back Pressure area to slow down packet reception speed

when the device is congested. This feature is used with half duplex mode, and disables the remote port by preventing it from sending packets and jamming the signal.

Select the capabilities to be advertised by the LAG. The options are:Auto Advertisement

• All Speed—All LAG speeds and both duplex modes are available.

• 10M—The LAG advertises a 10 Mbps speed and the mode is full duplex.

• 100M—The LAG advertises a 100 Mbps speed and the mode is full duplex.

• 1000M—The LAG advertises a 1000 Mbps speed and the mode is full duplex.

• 10/100M—The LAG advertises a 10/100 Mbps speed and the mode is full duplex.

• 10G—The LAG advertises a 10G speed and the mode is full duplex.

Cisco Business 220 Series Switches Administration Guide

Link Aggregation Control Protocol (LACP)

Port Management

DescriptionOption

Flow Control

Set Flow Control to either Enable or Disable or enable the Auto-Negotiation of Flow Control on the LAG.

Displays the auto-negotiation setting.Operational Auto

Negotiation

Displays the current speed at which the LAG is operating.Operational LAG Speed

Operational Advertisement

Displays the Administrative Advertisement status. The LAG advertises its capabilities to its neighbor LAG to start the negotiation process. The possible values are those specified in the Administrative Advertisement field.

Displays the current Flow Control setting.Current Flow Control

Step 4 Click Apply. The Running Configuration file is updated.

Link Aggregation Control Protocol (LACP)

A dynamic LAG is LACP-enabled, and LACP is run on every candidate port defined in the LAG. LACP system priority and LACP port priority are both used to determine which of the candidate ports become active member ports in a dynamic LAG configured with more than eight candidate ports.

Use the LACP page to configure the candidate ports for the LAG and to configure the LACP parameters per port. With all factors equal, when the LAG is configured with more candidate ports than the maximum number of active ports allowed (8), the device selects ports as active from the dynamic LAG on the device that has the highest priority.

Note

The LACP setting is irrelevant on ports that are not members of a dynamic LAG.

To define the LACP settings, complete the following steps:

Step 1 Click Port Management > Link Aggregation > LACP. Step 2 If needed, edit the LACP System Priority and click Apply. Step 3 To edit an existing port, select the port, and click Edit.

Step 4 In the Edit LACP Settings dialog box, enter the values for the following fields:

• Port—Select the port number to which timeout and priority values are assigned.

• LACP Port Priority—Enter the LACP priority value for the port.

• LACP Timeout—Time interval between the sending and receiving of consecutive LACP PDUs. Select the periodic transmissions of LACP PDUs, which occur at either a Long or Short transmission speed, depending upon the expressed LACP timeout preference.

Cisco Business 220 Series Switches Administration Guide

Port Management

Step 5 Click Apply. The Running Configuration file is updated.

Power over Ethernet

This section describes how to use the PoE feature.

A PoE device is Power Sourcing Equipment (PSE) that delivers electrical power to a connected Pod Devices (PD) over existing copper cables without interfering with the network traffic, updating the physical network or modifying the network infrastructure.

PoE provides the following features:

• Eliminates the need to run 110/220 V AC power to all devices on a wired LAN.

• Eliminates the need to deploy double cabling systems in an enterprise significantly decreasing installation costs. Power over Ethernet can be used in any enterprise network that deploys relatively low-pod devices connected to the Ethernet LAN, such as: IP phones, Wireless access points, IP gateways, Audio and video remote monitoring devices.

Power over Ethernet

Warning

Properties

PoE implements in the following stages:

• Detection—Sends special pulses on the copper cable. When a PoE device is located at the other end, that device responds to these pulses.

• Classification—Negotiation between the Power Sourcing Equipment (PSE) and the Pod Device (PD) commences after the Detection stage. During negotiation, the PD specifies its class, which indicates maximum amount of power that the PD consumes.

• Power Consumption—After the classification stage completes, the PSE provides power to the PD. If the PD supports PoE, but without classification, it is assumed to be class 0 (the maximum). If a PD tries to consume more power than permitted by the standard, the PSE stops supplying power to the port. PoE supports two modes:

• Port Limit—The maximum power the device agrees to supply is limited to the value the system administrator configures, regardless of the Classification result.

• Class Power Limit—The maximum power the device agrees to supply is determined by the results of the Classification stage. This means that it is set as per the Client's request.

The PoE unit is to be connected only to PoE networks without routing to the outside plant.

Note

This section is only relevant for devices supporting PoE.

Cisco Business 220 Series Switches Administration Guide

PoE Port Settings

The PoE Properties page enables selecting either the Port Limit or Class Limit PoE mode and specifying the PoE traps to be generated. These settings are entered in advance. When the PD actually connects and is consuming power, it might consume much less than the maximum power allowed. Output power is disabled during power-on reboot, initialization, and system configuration to ensure that PDs aren’t damaged.

To configure PoE on the device and monitor current power usage:

Step 1 Click Port Management > PoE> Properties.

Step 2 Enter the values for the following fields:

• Power Mode—Select one of the following options:

• Class Limit—Maximum power limit per port is determined by the class of the device, which results from the Classification stage.

• Port Limit—Maximum power limit per each port is configured by the user.

Port Management

Note

When you change from Port Limit to Class Limit or conversely, disable the PoE ports, and enable them after changing the power configuration.

• Traps—Enable or disable traps. If traps are enabled, you must also enable SNMP and configure at least one SNMP Notification Recipient.

• Power Trap Threshold—Enter the usage threshold that is a percentage of the power limit. An alarm is initiated if the power exceeds this value.

The following counters are displayed for the device:

• Operational Status—Displays the operational status (Normal or Fault) of the PoE switch.

• Nominal Power—Total amount of power the device can supply to all the connected PDs.

• Consumed Power—Amount of power currently being consumed by the PoE ports.

• Available Power—Nominal power minus the amount of consumed power.

• Software Version—Displays the software version of the PoE chip.

• PSE Chipset & Hardware Revision—PoE chipset and hardware revision number.

Step 3 Click Apply to save the PoE properties.

PoE Port Settings

The PoE Settings displays the system information for enabling PoE on the interfaces. It monitors the power usage and maximum power limit per port when the PoE mode is Port Limit. When the power consumed on the port exceeds the port limit, the port power is turned off.

To configure PoE settings, follow these steps:

Step 1 Click Port Management > PoE> PoEPort Settings.

Cisco Business 220 Series Switches Administration Guide

Port Management

Step 2 Select a port and click Edit.

Step 3 Enter the value for the following field:

• Interface—Select the port to configure.

• PoE Administrative Status—Enable or disable PoE on the port.

• Time Range—Select to enable.

• Time Range Name—If Time Range has been enabled, select the time range to be used. Time ranges are defined in

Time Range, on page 30. Click Edit to go to the Time Range page.

• Power Priority Level—Select the port priority: low, high, or critical, for use when the power supply is low. For example, if the power supply is running at 99% usage and port 1 is prioritized as high, but port 3 is prioritized as low, port 1 receives power and port 3 might be denied power.

• Administrative Power Allocation—If the Power mode is Port Limit, enter the power in milliwatts allocated to the port (Range: 0 - 30000. Default: 30000).

• Max Power Allocation—This field appears only if the Power Mode set in the PoE Properties page is Power Limit. Displays the maximum amount of power permitted on this port.

• Power Consumption—Displays the amount of power in milliwatts assigned to the powered device connected to the selected port.

PoE Port Settings

• Class—Displays the class of the device, which indicates the maximum power level of the device.

Maximum Power Delivered by Device PortClass

15.4 watt0

4.0 watt1

7.0 watt2

15.4 watt3

30.0 watt4

• Overload Counter—Displays the number of overload counters

• Short Counter—Displays the number of short counters

• Denied Counter—Displays the number of denied counters

• Absent Counter—Displays the number of absent counters

• Invalid Signature Counter—Displays the times that an invalid signature was received. Signatures are the means by which the powered device identifies itself to the PSE. Signatures are generated during powered device detection, classification, or maintenance.

Step 4 Click Apply. The PoE settings for the port are written to the Running Configuration file.

Cisco Business 220 Series Switches Administration Guide

Green Ethernet

Green Ethernet is a common name for a set of features that is designed to be environmentally friendly, and to reduce the power consumption of a device. Green Ethernet is different from EEE in that Green Ethernet energy-detect is enabled on all devices whereas only Gigabyte ports are enable with EEE.

The Green Ethernet feature can reduce overall power usage in the following ways:

• Energy-Detect Mode—On an inactive link, the port moves into inactive mode, saving power while keeping the Administrative status of the port Up. Recovery from this mode to full operational mode is fast, transparent, and no frames are lost.

In addition to the above Green Ethernet features, the 802.3az Energy Efficient Ethernet (EEE) is found on devices supporting GE ports. EEE reduces power consumption when there is no traffic on the port. EEE is enabled globally by default.

Power savings, current power consumption and cumulative energy saved can be monitored. The total amount of saved energy can be viewed as a percentage of the power that would have been consumed by the physical interfaces had they not been running in Green Ethernet mode. The saved energy displayed is only related to Green Ethernet. The amount of energy saved by EEE is not displayed.

Port Management

Green Ethernet Properties

The Properties page displays and enables configuration of the Green Ethernet mode for the device. It also displays the current power savings.

To enable Green Ethernet and EEE and view power savings, follow these steps:

Step 1 Click Port Management > GreenEthernet > Properties.

Step 2 Enter the values for the following fields:

• Port LEDs—Select to enable the port LEDs. When these are disabled, they don’t display link status, activity, etc.

• 802.3 Energy Efficient Ethernet (EEE)—Globally enable or disable EEE mode. 802.3az EEE is designed to save power when there is no traffic on the link. In Green Ethernet, power is reduced when the port is down. With 802.3az EEE, power is reduced when the port is up, but there is no traffic on it.

Step 3 Click Apply. The Green Ethernet Properties are written to the Running Configuration file.

Port Settings

The Port Settings displays the current Green Ethernet and EEE modes per port, and enables configuring Green Ethernet on a port using the Edit Port Setting page. For the Green Ethernet modes to operate on a port, the corresponding modes must be activated globally in Green Ethernet Properties, on page 78.

To define per port Green Ethernet settings, follow these steps:

Step 1 Click Port Management > GreenEthernet > Port Settings.

Cisco Business 220 Series Switches Administration Guide

Port Management

The Port Settings page displays the following:

Step 2 Select a Port and click Edit.

Step 3 Select to enable or disable 802.3 Energy Efficient Ethernet (EEE) mode on the port. Step 4 Click Apply. The Green Ethernet port settings are written to the Running Configuration file.

Port Settings

Cisco Business 220 Series Switches Administration Guide

Port Settings

Port Management

Cisco Business 220 Series Switches Administration Guide

VLAN Management

This chapter contains the following sections:

• Default VLAN Settings, on page 81

• VLAN Settings, on page 82

• VLAN Interface Settings, on page 82

• Port to VLAN, on page 83

• Port VLAN Membership, on page 84

• GVRP Settings, on page 85

• Voice VLAN, on page 86

Default VLAN Settings

When using the factory default settings, the switch automatically creates VLAN 1 as the default VLAN, the default interface status of all ports is Trunk, and all port are configured as untagged members of the default VLAN.

The default VLAN has the following characteristics:

CHAPTER 6

• Distinct, non-static, and non-dynamic, and all ports are untagged members by

default.

• Cannot be deleted.

• Cannot be given a label.

• Cannot be used for any special role such as unauthenticated VLAN or voice VLAN. This is only relevant for OUI-enabled voice VLAN.

• If a port is no longer a member of any VLAN, the switch automatically configures the port as an untagged member of the default VLAN. A port is no longer a member of a VLAN if the VLAN is deleted or the port is removed from the VLAN.

When the VID of the default VLAN is changed, the switch performs the following on all ports in the VLAN

• Removes VLAN membership of the ports from the original default VLAN.

• Changes the PVID of the ports to the VID of the new default VLAN.

• Adds the ports as untagged VLAN members of the new default VLAN.

Cisco Business 220 Series Switches Administration Guide

VLAN Settings

To change the default VLAN, complete the following steps:

Step 1 Click VLAN Management > Default VLAN Settings.

Step 2 Enter the following information:

• Current Default VLAN ID—Displays the current default VLAN ID.

• Default VLAN ID—Enter a new VLAN ID to replace the default VLAN ID.

Step 3 Click Apply. The default VLAN is changed, and the Running Configuration is updated.

VLAN Settings

Virtual Local Area Network (VLAN) creation allows you to make separate broadcast domains on a switch. The broadcast domains can associate with one another with the help of a Layer 3 device such as a router. A VLAN is mainly used to form groups among the hosts regardless of where the hosts are physically located. Thus, a VLAN improves security with the help of group formation among the hosts. When a VLAN is created, it has no effect until that VLAN is attached to at least one port either manually or dynamically. One of the most common reasons to set up a VLAN is to set up a separate VLAN for voice, and a separate VLAN for data. This directs the packets for both types of data despite using the same network.

VLAN Management

To create a VLAN, follow these steps:

Step 1 Click VLAN Management > VLAN Settings. Step 2 Click Add to add one or more new VLANs.

The page enables the creation of either a single VLAN or a range of VLANs.

Step 3 To create a single VLAN, select the VLAN radio button, enter the VLAN ID, and optionally the VLAN Name. Step 4 To add a range of VLANs, check Range and enter a VLAN Range (Range 2 - 4094) in the VLAN range field. Step 5 Click Apply to create the VLAN(s).

VLAN Interface Settings

The VLAN Interface Settings page displays and enables configuration of VLAN-related parameters.

To configure the VLAN settings, follow these steps:

Step 1 Click VLAN Management > Interface Settings. Step 2 Select an interface type (Port or LAG), and click Go. Ports or LAGs and their VLAN parameters are displayed. Step 3 To configure a Port or LAG, select it and click Edit.

Step 4 Enter the values for the following fields:

Cisco Business 220 Series Switches Administration Guide

VLAN Management

Port to VLAN

Select a Port/LAG.Interface

Interface VLAN Mode

Frame Type

Select the interface mode for the VLAN. The options are:

• Access—The interface is an untagged member of a single VLAN. A port configured in this mode is known as an access port.

• Trunk—The interface is an untagged member of one VLAN at most, and is a tagged member of zero or more VLANs. A port configured in this mode is known as a trunk port.

• General—The interface can support all functions as defined in the IEEE 802.1q specification. The interface can be a tagged or untagged member of one or more VLANs.

• Dot1q-Tunnel—Selecting this option places the interface in QinQ mode. This enables you to use your own VLAN arrangements (PVID) across the provider network. The device is in Q-in-Q mode when it has one or more dot1-q-tunnel ports.

(Available only in General mode) Select the type of frame that the interface can receive. Frames that aren’t of the configured frame type are discarded at ingress. Possible values are:

• Admit All—The interface accepts all types of frames: untagged frames, tagged frames, and priority tagged frames.

• Admit Tagged Only—The interface accepts only tagged frames.

• Admit Untagged Only—The interface accepts only untagged and priority frames.

Ingress Filtering

TPID

Step 5 Click Apply.

Port to VLAN

Use the Port to VLAN page to display and configure the ports within a specific VLAN.

To map ports or LAGs to a VLAN, follow these steps:

Available only in General mode) Select to enable ingress filtering. When an interface is ingress filtering enabled, the interface discards all incoming frames that are classified as VLANs of which the interface isn’t a member. Ingress filtering can be disabled or enabled on general ports. It’s always enabled on access ports and trunk ports.

PVID for selected VLAN mode.Administrative PVID

(Available only in Trunk mode). Check Enable to set the interface as an uplink port.Uplink

(Available only in Trunk mode) If Uplink is enabled, select the TPID value for the interface.

Cisco Business 220 Series Switches Administration Guide

VLAN Management

Port VLAN Membership

Step 1 Click VLAN Management > Port to VLAN. Step 2 Select a VLAN and the interface type (Port or LAG), and click Go to display or to change the port characteristic with

respect to the VLAN.

Step 3 To change the registration of an interface to the VLAN, select the desired option from the following list:

• Forbidden—The interface isn’t allowed to join the VLAN even from GVRP registration. When a port isn’t a member of any other VLAN, enabling this option on the port makes the port part of internal VLAN 4095 (a reserved VID).

• Excluded—The interface is currently not a member of the VLAN. This is the default for all the ports and LAGs when the VLAN is newly created.

• Tagged—The interface is a tagged member of the VLAN.

• Untagged—The interface is an untagged member of the VLAN. Frames of the VLAN are sent untagged to the interface VLAN.

• PVID—Check to set the PVID of the interface to the VID of the VLAN. PVID is a per-port setting.

Step 4 Click Apply. The interfaces are assigned to the VLAN, and written to the Running Configuration file.

Port VLAN Membership

The Port VLAN Membership page displays all ports on the device along with a list of VLANs to which each port belongs.

Note

VLAN IS mode is supported. This means that port VLAN membership can be configured ahead of time for various VLAN modes. When the port is put into the specific VLAN mode, the configuration becomes active.

To assign a port to one or more VLANs, follow these steps:

Step 1 Click VLAN Management > Port VLAN Membership. Step 2 Select interface type (Port or LAG), and click Go. The following fields are displayed for all interfaces of the selected

type:

• Interface—Port/LAG ID.

• Mode—Interface VLAN mode that was selected in the VLAN Interface Settings, on page 82.

• Administrative VLANs— Displays all VLANs of which the interface might be a member.

• Operational VLANs—Displays all VLANs of which the interface is currently a member.

• LAG—If interface selected is Port, displays the LAG in which it’s a member.

Step 3 Select a port, and click Join VLAN.

Step 4 Enter the values for the following fields:

Cisco Business 220 Series Switches Administration Guide

VLAN Management

• Interface—Select a Port or LAG.

• Current VLAN Mode—Displays the port VLAN mode that was selected in the VLAN Interface Settings, on page

• Access Mode Membership (Active)

• Trunk Mode Membership

• General Mode Membership

GVRP Settings

82.

• Access VLAN ID—Select the VLAN from the drop-down list.

• Native VLAN ID—When the port is in Trunk mode, it’s a member of this VLAN.

• Tagged VLANs—When the port is in Trunk mode, it’s a member of these VLANs. The following options are possible:

All VLANs—When the port is in Trunk mode, it’s a member of all VLANs.

User Defined—When the port is in Trunk mode, it’s a member of the VLANs that are entered here.

• Untagged VLANs—When the port is in General mode, it’s an untagged member of this VLAN.

• Tagged VLANs—When the port is in General mode, it’s a tagged member of these VLANs.

• Forbidden VLANs—When the port is in General mode, the interface isn’t allowed to join the VLAN even from GVRP registration. When a port isn’t a member of any other VLAN, enabling this option on the port makes the port part of internal VLAN 4095 (a reserved VID).

• General PVID—When the port is in General mode, it’s a member of these VLANs.

• Dot1q Tunnel Mode Membership

• Dot1q Tunnel VLAN ID—When the port is in Dot1q Tunnel mode, it’s a member of this VLAN.

Step 5 Select a port and click Details to view the following fields:

• Administrative VLANs—Port is configured for these VLANs.

• Operational VLANs—Port is currently a member of these VLANs.

Click Apply (for Join VLAN). The settings are modified and written to the Running Configuration file.

GVRP Settings

Adjacent VLAN-aware devices can exchange VLAN information with each other by using the Generic VLAN Registration Protocol (GVRP). GVRP is based on the Generic Attribute Registration Protocol (GARP) and propagates VLAN information throughout a bridged network.

GVRP must be activated globally and on each port. When it’s activated, it transmits and receives GARP Packet Data Units (GPDUs). VLANs that are defined but not active aren’t propagated. To propagate the VLAN, it must be up on at least one port. By default, GVRP is disabled globally and on ports.

Cisco Business 220 Series Switches Administration Guide

Voice VLAN

To define GVRP settings for an interface:

Step 1 Click VLAN Management > GVRP Settings. Step 2 Select GVRP Global Status to enable GVRP globally. Step 3 Click Apply to set the global GVRP status. Step 4 Select an interface type (Port or LAG), and click Go to display all interfaces of that type. Step 5 To define GVRP settings for a port, select it, and click Edit.

Step 6 Enter the values for the following fields:

• Interface—Select the interface (Port or LAG) to be edited.

• GVRP State—Select to enable GVRP on this interface.

• Dynamic VLAN Creation—Select to enable Dynamic VLAN Creation on this interface.

• GVRP Registration—Select to enable VLAN Registration using GVRP on this interface.

Step 7 Click Apply. GVRP settings are modified, and written to the Running Configuration file.

VLAN Management

Voice VLAN

The voice VLAN feature enables access ports to carry IP voice traffic from an IP phone. When the switch is connected to an IP Phone, the phone sends voice traffic with Layer 3 IP precedence and Layer 2 class of service (CoS) values, which are both set to 5 by default. Because the sound quality of an IP phone call can deteriorate if the data is unevenly sent, the switch supports quality of service (QoS) based on IEEE 802.1p CoS. QoS uses classification and scheduling to send network traffic from the switch in a predictable manner.

Voice VLAN can propagate the CoS/802.1p and DSCP settings by using LLDP-MED Network policies. The LLDP-MED is set by default to response with the Voice QoS setting if an appliance sends LLDP-MED packets. MED-supported devices must send their voice traffic with the same CoS/802.1p and DSCP values, as received with the LLDP-MED response.You can disable the automatic update between Voice VLAN and LLDP-MED and use your own network polic ies. Working with the OUI mode, the device can additionally configure the mapping and remarking (CoS/802.1p) of the voice traffic based on the OUI.

By default, all interfaces are CoS/802.1p trusted. The device applies the quality of service based on the CoS/802.1p value found in the voice stream. For Telephony OUI voice streams, you can override the quality of service and optionally remark the 802.1p of the voice streams by specifying the desired CoS/802.1p values and using the remarking option under Telephony OUI.

Voice VLAN Properties

Use the Voice VLAN Properties page for the following:

• View how voice VLAN is currently configured.

• Configure the VLAN ID of the Voice VLAN.

• Configure voice VLAN QoS settings.

Cisco Business 220 Series Switches Administration Guide

VLAN Management

• Configure the voice VLAN mode (Telephony OUI or Auto Voice VLAN).

To view and configure Voice VLAN properties:

Step 1 Click VLAN Management > Voice VLAN > Properties.

• The voice VLAN settings configured on the device are displayed in the Voice VLAN Settings (Administrative Status) block.

• The voice VLAN settings that are actually being applied to the voice VLAN deployment are displayed in the Voice VLAN Settings (Operational Status) block.

Step 2 Enter values for the following Administrative Status fields:

• Voice VLAN ID—Enter the VLAN that is to be the Voice VLAN.

Voice VLAN Properties

Note

Changes in the voice VLAN ID, CoS/802.1p, and/or DSCP cause the device to advertise the administrative voice VLAN as a static voice VLAN. If the option Auto Voice VLAN Activation triggered by external Voice VLAN is selected, then the default values need to be maintained.

• CoS/802.1p —Select a CoS/802.1p value for the LLDP-MED as a voice network policy. Refer to Administration > Discovery > LLDP > LLDP MED Network Policy for more details.

• DSCP—Selection of DSCP values for the LLDP-MED as a voice network policy. Refer to Administration > Discovery > LLDP > LLDP MED Network Policy for more details.

The following Operational Status fields are displayed:

• Voice VLAN ID—Voice VLAN.

• CoS/802.1p —Value being used by LLDP-MED as a voice network policy. Refer to Administration > Discovery > LLDP > LLDP MED Network Policy for more details.

• DSCP—Value used by the LLDP-MED as a voice network policy.

The following Dynamic Voice VLAN Settings fields are displayed:

• Dynamic Voice VLAN—Select this field to disable or enable voice VLAN feature in one of the following ways:

• Enable Auto Voice VLAN—Enable Dynamic Voice VLAN in Auto Voice VLAN mode.

• Enable Telephony OUI—Enable Dynamic Voice VLAN in Telephony OUI mode.

• Disable—Disable Auto Voice Vlan or Telephony OUI

Note

Manually reconfiguring the voice VLAN ID, CoS/802.1p, and/or DSCP from their default values results in a static voice VLAN, which has higher priority than auto voice VLAN.

Step 3 Click Apply. The VLAN properties are written to the Running Configuration file.

Cisco Business 220 Series Switches Administration Guide

Telephony OUI

Organizationally Unique Identifiers (OUIs) are assigned by the Institute of Electrical and Electronics Engineers, Incorporated (IEEE) Registration Authority. Since the number of IP phone manufacturers is limited and well-known, the known OUI values cause the relevant frames, and the port on which they are seen, to be automatically assigned to a Voice VLAN. Use the Telephony OUI page to configure Telephony OUI QoS properties. In addition, the Auto Membership Aging time can be configured. If the specified time period passes with no telephony activity, the port is removed from the Voice VLAN.

To configure Telephony OUI and/or add a new Voice VLAN OUI:

Step 1 Click VLAN Management > Voice VLAN > Telephony OUI.

The Telephony OUI page contains the following fields:

• Telephony OUI—First six digits of the MAC address that are reserved for OUIs

• Description—User-assigned OUI description.

Step 2 Specify the following general Telephony OUI parameters

VLAN Management

• Telephony OUI Operational Status—Displays whether OUIs are used to identify voice traffic.

• CoS/802.1p—Select the CoS queue to be assigned to voice traffic.

• Remark CoS/802.1p—Select whether to remark egress traffic.

• Auto Membership Aging Time—Enter the time delay to remove a port from the voice VLAN after all of the MAC addresses of the phones detected on the ports have aged out.

Step 3 Click Apply to update the Running Configuration of the device with these values.

The Telephony OUI table appears:

• Telephony OUI—First six digits of the MAC address that are reserved for OUIs.

• Description—User-assigned OUI description.

Step 4 Click RestoreDefault OUIs to delete all of the user-created OUIs, and leave only the default OUIs in the table. The OUI

information may not be accurate until the restoration is completed. This may take several seconds. After several seconds have passed, refresh the page by exiting it and reentering it.

To delete all the OUIs, select the top checkbox. All the OUIs are selected and can be deleted by clicking Delete. If you then click Restore Default OUIs, the system recovers the known OUIs.

Telephone OUI Interface

The QoS attributes can be assigned per port to the voice packets in one of the following modes:

• All—Quality of Service (QoS) values configured to the Voice VLAN are applied to all of the incoming frames that are received on the interface and are classified to the Voice VLAN.

Cisco Business 220 Series Switches Administration Guide

VLAN Management

Telephone OUI Interface

• Telephony Source MAC Address (SRC)—The QoS values configured for the Voice VLAN are applied to any incoming frame that is classified to the Voice VLAN and contains an OUI in the source MAC address that matches a configured telephony OUI.

Use the Telephony OUI Interface page to add an interface to the voice VLAN on the basis of the OUI identifier and to configure the OUI QoS mode of voice VLAN.

To configure Telephony OUI on an interface:

Step 1 Click VLAN Management > Voice VLAN > Telephony OUI Interface.

The Telephony OUI Interface page contains voice VLAN OUI parameters for all interfaces.

Step 2 To configure an interface to be a candidate port of the telephony OUI-based voice VLAN, click Edit.

Step 3 Enter the values for the following fields:

• Interface—Select an interface.

• Telephony OUI VLAN Membership—If enabled, the interface is a candidate port of the telephony OUI based voice VLAN. When packets that match one of the configured telephony OUI are received, the port is added to the voice VLAN.

• Voice VLAN QoS Mode (Telephone OUI QoS Mode in main page)—Select one of the following options:

• All—QoS attributes are applied on all packets that are classified to the Voice VLAN.

• Telephony Source MAC Address—QoS attributes are applied only on packets from IP phones.

Step 4 Click Apply. The OUI is added.

Cisco Business 220 Series Switches Administration Guide

Telephone OUI Interface

VLAN Management

Cisco Business 220 Series Switches Administration Guide

Spanning Tree

This chapter contains the following sections:

• STP Status and Global Settings, on page 91

• STP Interface Settings, on page 92

• RSTP Interface Settings, on page 94

• MSTP Properties, on page 95

• VLANs to MSTP Instance, on page 96

• MSTP Instance Settings, on page 97

• MSTP Interface Settings, on page 97

STP Status and Global Settings

Spanning Tree Protocol (STP) protects a Layer 2 Broadcast domain from Broadcast storms by selectively setting links to standby mode to prevent loops. In standby mode, these links temporarily stop transferring user data. After the topology changes so that the data transfer is made possible, the links are automatically re-activated.

CHAPTER 7

STP provides a tree topology for any arrangement of switches and interconnecting links, by creating a unique path between end stations on a network, and thereby eliminating loops.

The STP Status and Global Settings page contains parameters for enabling the required STP mode. Use the STP Interface Settings page, RSTP Interface Settings page, and MSTP Properties page to configure each mode, respectively. To set the STP status and global settings, follow these steps:

Step 1 Click Spanning Tree > STP Status &Global Settings.

Step 2 Enter the parameters.

Global Settings:

Select to enable on the device.Spanning Tree State

Select to enable Loopback Guard on the device.STP Loopback Guard

Select an STP mode.STP Operation Mode

Cisco Business 220 Series Switches Administration Guide

STP Interface Settings

Spanning Tree

BPDU Handling

Path Cost Default Values

Bridge Settings:

Priority

Max Age

Select how Bridge Protocol Data Unit (BPDU) packets are managed when STP is disabled. BPDUs are used to transmit spanning tree information.

• Filtering-Filters BPDU packets when Spanning Tree is disabled on an interface.

• Flooding-Floods BPDU packets when Spanning Tree is disabled on an interface.

Selects the method used to assign default path costs to the STP ports. The default path cost assigned to an interface varies according to the selected method.

• Short-Specifies the range 1–65,535 for port path costs

• Long-Specifies the range 1–200,000,000 for port path costs

Bridge Settings:

Sets the bridge priority value. After exchanging BPDUs, the device with the lowest priority becomes the Root Bridge. In the case that all bridges use the same priority, then their MAC addresses are used to determine the Root Bridge. The bridge priority value is provided in increments of 4096. For example, 4096, 8192, 12288, and so on.

Set the interval (in seconds) that a Root Bridge waits between configuration messages.Hello Time

Set the interval (in seconds) that the device can wait without receiving a configuration message, before attempting to redefine its own configuration.

Forward Delay

Last Topology Change

Step 3 Click Apply. The STP Global settings are written to the Running Configuration file.

Set the interval (in seconds) that a bridge remains in a learning state before forwarding packets.

The bridge priority concatenated with the MAC address of the device.Designated Root / Bridge ID

The Root Bridge priority concatenated with the MAC address of the Root Bridge.Root Bridge ID

The port that offers the lowest cost path from this bridge to the Root Bridge.Root Port

The cost of the path from this bridge to the root.Root Path Cost

The total number of STP topology changes that have occurred.Topology Changes Counts

The time interval that elapsed since the last topology change occurred. The time appears in a days/hours/minutes/seconds format.

STP Interface Settings

The STP Interface Settings page enables you to configure STP on a per-port basis, and to view the information learned by the protocol, such as the designated bridge.

The defined configuration entered is valid for all flavors of the STP protocol.

Cisco Business 220 Series Switches Administration Guide

Spanning Tree

To configure STP on an interface, follow these steps:

Step 1 Click Spanning Tree > STP Interface Settings. Step 2 Select an interface and click Edit.

Step 3 Enter the parameters

Select the Port or LAG on which Spanning Tree is configured.Interface

STP Interface Settings

Edge Port

Path Cost

Priority

Port State

Enables or disables Fast Link on the port. If Fast Link mode is enabled on a port, the port is automatically set to Forwarding state when the port link is up. Fast Link optimizes the STP protocol convergence. The options are:

• Enable—Enables Fast Link immediately

• Disable—Disables Fast Link

If enabled, the interface will shut down when a BPDU message is received.BDU Guard

If enabled, the interface will not send and receive BPDU messages.BDU Filter

Set the port contribution to the root path cost or use the default cost generated by the system.

Set the priority value of the port. The priority value influences the port choice when a bridge has two ports connected in a loop. The priority is a value 0–240, and must bea multiple of 16.

Displays the current STP state of a port.

• Disabled—STP is currently disabled on the port. The port forwards traffic while learning MAC addresses.

• Blocking—The port is currently blocked, and can’t forward traffic (except for BPDU data) or learn MAC addresses.

• Learning—The port is in Learning mode. The port can’t forward traffic, but it can learn new MAC addresses.

• Forwarding—The port is in Forwarding mode. The port can forward traffic and learn new MAC addresses.

Displays the bridge priority and the MAC address of the designated bridge.Designated Bridge ID

Displays the priority and interface of the selected port.Designated Port ID

Designated Cost

Displays the cost of the port participating in the STP topology. Ports with a lower cost are less likely to be blocked if STP detects loops.

Step 4 Click Apply. The interface settings are written to the Running Configuration file.

Cisco Business 220 Series Switches Administration Guide

RSTP Interface Settings

Rapid Spanning Tree Protocol (RSTP) enables a faster STP convergence without creating forwarding loops.

The RSTP Interface Settings page enables you to configure RSTP per port. Any configuration that is done on this page is active when the global STP mode is set to RSTP.

To enter RSTP settings, proceed with the following steps:

Step 1 Click Spanning Tree > STP Status andGlobal Settings.

Step 2 Enable RSTP. Step 3 Click Spanning Tree > RSTP Interface Settings. The RSTP Interface Settings page appears.

Step 4 Select a port.

Spanning Tree

Note

Step 5 If a link partner is discovered by using STP, click Activate Protocol Migration to run a Protocol Migration test. This

discovers whether the link partner using STP still exists, and if so whether it has migrated to RSTP or MSTP. If it still exists as an STP link, the device continues to communicate with it by using STP. Otherwise, if it has been migrated to RSTP or MSTP, the device communicates with it using RSTP or MSTP, respectively.

Step 6 Select an interface, and click Edit.

Step 7 Enter the parameters:

Point to Point Administrative Status

Point to Point Operational Status

Activate Protocol Migration is only available after selecting the port that is connected to the bridge partner being tested.

Set the interface, and specify the port or LAG where RSTP is to be configured.Interface

Define the point-to-point link status. Ports defined as Full Duplex are considered Point-to-Point port links.

• Enabled-This port is an RSTP edge port when this feature is enabled, and is brought to Forwarding mode quickly (usually within 2 seconds).

• Disabled-The port isn’t considered point-to-point for RSTP purposes, which means that STP works on it at regular speed, as opposed to high speed.

• Auto-Automatically determines the device status by using RSTP BPDUs.

Displays the Point-to-Point operational status if the Point to Point Administrative Status is set to Auto.

Cisco Business 220 Series Switches Administration Guide

Spanning Tree

MSTP Properties

Role

Fast Link Operational Status

Port Status

Displays the role of the port that was assigned by STP to provide STP paths. The possible roles are:

• Root-Lowest cost path to forward packets to the Root Bridge.

• Designated-The interface through which the bridge is connected to the LAN, which provides the lowest cost path from the LAN to the Root Bridge.

• Alternate-Provides an alternate path to the Root Bridge from the root port.

• Backup-Provides a backup path to the designated port path toward the Spanning Tree leaves. This provides a configuration in which two ports are connected in a loop by a point-to-point link. Backup ports are also used when a LAN has two or more established connections to a shared segment.

• Disabled-The port is not participating in Spanning Tree.

Displays whether the Fast Link (Edge Port) is enabled, disabled, or automatic for the interface. The values are:

• Enabled-Fast Link is enabled.

• Disabled-Fast Link is disabled.

Displays the RSTP status on the specific port.

• Disabled-STP is currently disabled on the port.

• Learning-The port is in Learning mode. The port cannot forward traffic, however it can learn new MAC addresses.

• Blocking-The port is currently blocked, and can't forward traffic (except for BPDU data) or learn MAC addresses.

• Forwarding-The port is in Forwarding mode. The port can forward traffic and learn new MAC addresses.

Step 8 Click Apply. The Running Configuration file is updated.

MSTP Properties

The global MSTP configures a separate Spanning Tree for each VLAN group and blocks all but one of the possible alternate paths within each spanning tree instance. MSTP enables formation of MST regions that can run multiple MST instances (MSTI). Multiple regions and other STP bridges are interconnected using one single common spanning tree (CST).

MSTP is fully compatible with RSTP bridges, in that an MSTP BPDU can be interpreted by an RSTP bridge as an RSTP BPDU. This not only enables compatibility with RSTP bridges without configuration changes, but also causes any RSTP bridges outside of an MSTP region to see the region as a single RSTP bridge, regardless of the number of MSTP bridges inside the region itself. For two or more switches to be in the same MST region, they must have the same VLANs to MST instance mapping, configuration revision number, and

Cisco Business 220 Series Switches Administration Guide

VLANs to MSTP Instance

region name. Switches intended to be in the same MST region are never separated by switches from another MST region. If they are separated, the region becomes two separate regions.

This mapping can be done in the MSTP Instance Settings, on page 97. Use this page if the system operates in MSTP mode.

To define MSTP, follow these steps:

Step 1 Click Spanning Tree > MSTP > MSTP Properties.

Step 2 Enter the parameters.

• Region Name—Define an MSTP region name.

• Revision—Define an unsigned 16-bit number that identifies the revision of the current MST configuration. The field range is 0–65535.

• Max Hops—Set the total number of hops that occur in a specific region before the BPDU is discarded. Once the BPDU is discarded, the port information is aged out. The field range is 1–40.

Step 3 Click Apply. The MSTP properties are defined, and the Running Configuration file is updated.

Spanning Tree

VLANs to MSTP Instance

The VLAN to MSTP Instance page enables you to map each VLAN to a Multiple Spanning Tree Instance (MSTI). For devices to be in the same region, they must have the same mapping of VLANs to MSTIs.

Note

The same MSTI can be mapped to more than one VLAN, but each VLAN can only have one MST instance attached to it. Configuration on this page (and all of the MSTP pages) applies if the system STP mode is MSTP. Up to 16 MST instances can be defined in addition to instance zero. For those VLANs that aren’t explicitly mapped to one of the MST instances, the device automatically maps them to the CIST (Core and Internal Spanning Tree) instance. The CIST instance is MST instance 0.

To map VLANs to MST Instances, follow these steps:

Step 1 Click Spanning Tree > RSTP Interface Settings> MSTP > VLAN to MSTPInstance.

The VLAN to MSTP Instance page displays the following fields:

• MSTP Instance ID-All MST instances are displayed.

• VLANs-All VLANs belonging to the MST instance are displayed.

Step 2 To add a VLAN to an MSTP instance, select the MST instance, and click Edit. Step 3 Enter the parameters:

• MSTP Instance ID-Select the MST instance.

• VLANs-Define the VLANs being mapped to this MST instance.

Cisco Business 220 Series Switches Administration Guide

Spanning Tree

MSTP Instance Settings

• Action-Define whether to Add (map) the VLAN to the MST instance or Remove it.

Step 4 Click Apply. The MSTP VLAN mappings are defined, and the Running Configuration file is updated.

MSTP Instance Settings

The MSTP Instance Settings page enables you to configure and view parameters per MST instance. This is the per-instance equivalent to the Configuring STP Status and Global Settings.

To enter the MSTP instance settings, proceed as follows:

Step 1 Click Spanning Tree > MSTP >MSTP InstanceSettings.

Step 2 Enter the parameters.

• Instance ID-Select an MST instance to be displayed and defined.

• Included VLAN-Displays the VLANs mapped to the selected instance. The default mapping is that all VLANs are mapped to the common and internal spanning tree (CIST) instance 0).

• Bridge Priority-Set the priority of this bridge for the selected MST instance.

• Designated Root Bridge ID-Displays the priority and MAC address of the Root Bridge for the MST instance.

• Root Port-Displays the root port of the selected instance.

• Root Path Cost-Displays the root path cost of the selected instance.

• Bridge ID-Displays the bridge priority and the MAC address of this device for the selected instance.

• Remaining Hops-Displays the number of hops remaining to the next destination.

Step 3 Click Apply. The MST Instance configuration is defined, and the Running Configuration file is updated.

MSTP Interface Settings

The MSTP Interface Settings page enables you to configure the port MSTP settings for every MST instance, and to view information that has currently been learned by the protocol, such as the designated bridge per MST instance.

To configure the ports in an MST instance, follow these steps:

Step 1 Click Spanning Tree > MSTP > MSTP Interface Settings. Step 2 Enter the parameters.

• Instance equals to—Select the MSTP instance to be configured.

• Interface Type equals to—Select whether to display the list of ports or LAGs.

Cisco Business 220 Series Switches Administration Guide

MSTP Interface Settings

Step 3 Click Go. The MSTP parameters for the interfaces on the instance are displayed. Step 4 Select an interface, and click Edit. Step 5 Enter the parameters.

DescriptionOption

Select the MST instance to be configured.Instance ID

Select the interface for which the MSTI settings are to be defined.Interface

Set the port priority for the specified interface and MST instance.Interface Priority

Spanning Tree

Path Cost

Port State

Port Role

Enter the port contribution to the root path cost in the User Defined textbox or select Use Default to use the default value.

Displays the MSTP status of the specific port on a specific MST instance. The parameters are defined as:

• Disabled—STP is currently disabled.

• Learning—The port on this instance is in Learning mode. The port cannot forward traffic, but it can learn new MAC addresses.

• Blocking—The port is currently blocked, and can’t forward traffic (except for BPDU data) or learn MAC addresses.

• Forwarding—The port on this instance is in Forwarding mode. The port can forward traffic and learn new MAC addresses.

Displays the port or LAG role, per port or LAG per instance, assigned by the MSTP algorithm to provide STP paths:

• Master—A Master port provides connectivity from an MSTP region to the outlying CIST root

• Root—Forwarding packets through this interface provides the lowest cost path for forwarding packets to the root device.

• Designated Port—The interface through which the bridge is connected to the LAN, which provides the lowest root path cost from the LAN to the Root Bridge for the MST instance.

• Alternate—The interface provides an alternate path to the Root Bridge from the root port.

• Backup—The interface provides a backup path to the designated port path toward the Spanning Tree leaves. Backup ports occur when two ports are connected in a loop by a point-to-point link. Backup ports also occur when a LAN has two or more established connections to a shared segment.

• Disabled—The interface does not participate in the Spanning Tree.

Displays the current interface Spanning Tree mode.Mode

• If the link partner is using MSTP or RSTP, the displayed port mode is RSTP.

• If the link partner is using STP, the displayed port mode is STP.

Displays the MST type of the port.Type

Cisco Business 220 Series Switches Administration Guide

Cisco CBS220-24T-4X Manual [EN]

Specifications and Main Features

Frequently Asked Questions

User Manual

Cisco Business 220 Series Switches Administration Guide

Get to Know Your Switch

Introduction

Rack Mounting Switch

Wall Mounting a Switch

Wall Mount an 8 Port Switch

PoE Consideration

Front Panel

Front Panel LEDs

Configuring Switches

Configuring Your Switch Using the Web-based Interface

Configuring Your Switch Using the Console Port

Getting Started

Getting Started

Status and Statistics

System Summary

Interface

Etherlike

Hardware Resource Utilization

Health

SPAN and RSPAN

RSPAN VLAN

Session Destinations

Session Sources

RMON

RMON Statistics

RMON History

RMON Events

Alarms

View Log

RAM Memory

Flash Memory

Administration

System Settings

Console Settings

User Accounts

Idle Session Timeout

Time Settings

System Time

SNTP Settings

Time Range

Periodic Time Range

System Log

Log Settings

Remote Log Servers

File Management

Firmware Operations

File Operations

Configuration File Properties

DHCP Auto Configuration

Cisco Business Dashboard Settings

Plug-n-Play (PNP)

PNP Settings

PNP Session

Reboot

Diagnostics

Copper Test

Optical Module Status

CPU Utilization

Tech-Support Information

Discovery Bonjour

Discovery LLDP

Properties

Port Settings

LLDP MED Network Policy

LLDP MED Port Settings

LLDP Port Status

LLDP Local Information

LLDP Neighbor

LLDP Statistics

LLDP Overloading

Discovery - CDP

Properties

CDP Interface Settings

CDP Local Information

CDP Neighbors Information