Professional Documents
Culture Documents
Cisco Small Business 300 Series Managed Switch Administration Guide Release 1.3
Contents
1
1
2
3 4
5 6 7
7 9
12
12 13 15 16 17 18
18 20 21 22 24 24
28
28 30 31
32 32
Contents
34
34 37
38
41 41
42 43
47 48 49
50 50 51 51 53
56
56 58
58 60
Console Settings (Autobaud Rate Support) Rebooting the Device Routing Resources Monitoring Fan Status Defining Idle Session Timeout Pinging a Host Traceroute
61 62 64 65 67 67 69
72
2
Contents
73
73 74
74 75
75 77 80 80 81
82 83
84
84 86
86
Configuring Port and VLAN Mirroring Viewing CPU Utilization and Secure Core Technology
87 89
92
92
92 93
94 95
96 97 98 100 102 103 104
Contents
Configuring CDP
Setting CDP Properties Editing CDP Interface Settings Displaying CDP Local Information Displaying CDP Neighbors Information Viewing CDP Statistics
115
115 118 119 121 123
124
124 125 128
129
129
Default Settings and Configuration Static and Dynamic LAG Workflow Defining LAG Management Configuring LAG Settings Configuring LACP
LACP Priority and Rules LACP With No Link Partner Setting LACP Parameter Settings
136
136
137 138
Setting Global Green Ethernet Properties Setting Green Ethernet Properties for Ports
140 141
144
145
Contents
146 146
148
Smartport Macros
Applying a Smartport Type to an Interface
149
150
Macro Failure and the Reset Operation How the Smartport Feature Works Auto Smartport
Enabling Auto Smartport Identifying Smartport Type
Using CDP/LLDP Information to Identify Smartport Types
154 155
Error Handling Default Configuration Relationships with Other Features and Backwards Compatibility Common Smartport Tasks Configuring Smartport Using The Web-based Interface
Smartport Properties Smartport Type Settings Smartport Interface Settings
164
176
176
176 177
177
179 180
180
Contents
184
184 187 189 190 191
192 193
GVRP Settings
Defining GVRP Settings
194
195
VLAN Groups
MAC-based Groups
Assigning MAC-based VLAN Groups Mapping VLAN Group to VLAN Per Interface
195
196
196 197
Voice VLAN
Voice VLAN Overview
Dynamic Voice VLAN Modes Voice End-Points Auto Voice VLAN, Auto Smartports, CDP, and LLDP Voice VLAN QoS Voice VLAN Constraints Voice VLAN Workflows
198
198
199 200 200 202 203 203
204
205 206
208
208 210
211
212 212 213 213
214
Contents
214
215 216
218
218 219 221 223 226 226 227 228 229
232
232
233 234
234 234
235
236
236
237 239
Defining Multicast Properties Adding MAC Group Address Adding IP Multicast Group Addresses Configuring IGMP Snooping
Contents
MLD Snooping Querying IGMP/MLD IP Multicast Group Defining Multicast Router Ports Defining Forward All Multicast Defining Unregistered Multicast Settings
254
254
255 256
256
256
257 258
IPv4 Routes ARP ARP Proxy UDP Relay/IP Helper DHCPv4 Snooping/Relay
DHCPv4 Snooping DHCPv4 Relay Transparent DHCP Relay Option 82
Interactions Between DHCPv4 Snooping, DHCPv4 Relay and Option 82 265 DHCP Snooping Binding Database
DHCP Trusted Ports How the DHCP Snooping Binding Database is Built DHCP Snooping Along With DHCP Relay DHCP Default Configuration Configuring DHCP Work Flow
269
270 270 272 272 272
DHCP Snooping/Relay
Properties Interface Settings DHCP Snooping Trusted Interfaces DHCP Snooping Binding Database
273
273 274 274 275
Contents
DHCP Server
DHCP Options Dependencies Between Features Default Settings and Configurations
DHCPv4 Server Network Pool Excluded Addresses Static Hosts Address Binding
276
276 278 278
279 279 281 281 283
284
285 285 288
289
Defining IPv6 Addresses IPv6 Default Router List Defining IPv6 Neighbors Information Viewing IPv6 Route Tables DHCPv6 Relay
Dependencies with Other Features Global Destinations Interface Settings
Domain Name
DNS Settings Search List Host Mapping
297
298 299 300
302
303
303 305
Configuring TACACS+
Accounting Using a TACACS+ Server Defaults
306
307 308
Contents
Configuring RADIUS
Accounting Using a RADIUS Server Defaults Interactions With Other Features Radius Workflow
311
311 311 312 312
315 316
317 319
SSL Server
SSL Overview Default Settings and Configuration SSL Server Authentication Settings
321
321 322 322
Configuring TCP/UDP Services Defining Storm Control Configuring Port Security Configuring 802.1X
802.1X Parameters Workflow Defining 802.1X Properties Defining 802.1X Port Authentication Defining Host and Session Authentication Viewing Authenticated Hosts
339 340
340 340 341 342
10
Contents
342 342
342 344 345 346 347 348 348
IP Source Guard
Interactions with Other Features Filtering Configuring IP Source Guard Work Flow Enabling IP Source Guard Configuring IP Source Guard on Interfaces Binding Database
349
349 350 350 351 351 352
353
354 355
355
ARP Inspection Work Flow Defining ARP Inspection Properties Defining Dynamic ARP Inspection Interfaces Settings Defining ARP Inspection Access Control Defining ARP Inspection Access Control Rules Defining ARP Inspection VLAN Settings
360
360
361
SSD Rules
Elements of an SSD Rule SSD Rules and User Authentication Default SSD Rules
361
362 365 365
11
Contents
366
SSD Properties
Passphrase Default and User-defined Passphrases Local Passphrase Configuration File Passphrase Control Configuration File Integrity Control Read Mode
366
367 367 367 368 368 369
Configuration Files
File SSD Indicator SSD Control Block Startup Configuration File Running Configuration File Backup and Mirror Configuration File Sensitive Data Zero-Touch Auto Configuration
369
369 370 370 371 372 373
SSD Management Channels Menu CLI and Password Recovery Configuring SSD
SSD Properties SSD Rules
380
380 381
381 382 382
383 384
384
385 385
12
Contents
387
387 388 388
390
390 391 392
392 393
396
396 398
399
IPv4-based ACLs
Defining an IPv4-based ACL Adding Rules (ACEs) to an IPv4-Based ACL
401
401 402
IPv6-Based ACLs
Adding Rules (ACEs) for an IPv6-Based ACL
405
406
409
412
413
413 414
415
416 417 418 420
13
Contents
Configuring Bandwidth Configuring Egress Shaping per Queue Configuring VLAN Ingress Rate Limit TCP Congestion Avoidance
427
427 428 429
429
431 431 432 434 435 436 437 438 440
440
441
441 442
442
446
446
447 447 447 449
449 450
14
Contents
Configuring SNMP Views Creating SNMP Groups Managing SNMP Users Defining SNMP Communities Defining Trap Settings Notification Recipients
Defining SNMPv1,2 Notification Recipients Defining SNMPv3 Notification Recipients
463
15
Contents
16
1
Getting Started
This section provides an introduction to the web-based configuration utility, and covers the following topics: Starting the Web-based Configuration Utility Quick Start Device Configuration Interface Naming Conventions Window Navigation
Browser Restrictions
If you are using older versions of Internet Explorer, you cannot directly use an IPv6 address to access the device. You can, however, use the DNS (Domain Name System) server to create a domain name that contains the IPv6 address, and then use that domain name in the address bar in place of the IPv6 address. If you have multiple IPv6 interfaces on your management station, use the IPv6 global address instead of the IPv6 link local address to access the device from your browser.
Getting Started
Starting the Web-based Configuration Utility
LED flashes continuously. When the device is using a DHCP assigned IP address or an administrator-configured static IP address, the power LED is on solid.
Logging In
The default username is cisco and the default password is cisco. The first time that you log in with the default username and password, you are required to enter a new password.
NOTE If you have not previously selected a language for the GUI, the language of the Login
page is determined by the language(s) requested by your browser and the languages configured on your device. If your browser requests Chinese, for example, and Chinese has been loaded into your device, the Login page is automatically displayed in Chinese. If Chinese has not been loaded into your device, the Login page appears in English. The languages loaded into the device have a language and country code (en-US, en-GB and so on). For the Login page to be automatically displayed in a particular language, based on the browser request, both the language and country code of the browser request must match those of the language loaded on the device. If the browser request contains only the language code without a country code (for example: fr). The first embedded language with a matching language code is taken (without matching the country code, for example: fr_CA). To log in to the device configuration utility:
STEP 1 Enter the username/password. The password can contain up to 64 ASCII
characters. Password-complexity rules are described in the Setting Password Complexity Rules section of the Configuring Security chapter.
STEP 2 If you are not using English, select the desired language from the Language drop-
down menu. To add a new language to the device or update a current one, refer to the Upgrade/Backup Firmware/Language section.
Getting Started
Starting the Web-based Configuration Utility
STEP 3 If this is the first time that you logged on with the default user ID (cisco) and the
default password (cisco) or your password has expired, the Change Password Page appears. See Password Expiration for additional information.
STEP 4 Choose whether to select Disable Password Complexity Enforcement or not.
For more information on password complexity, see the Setting Password Complexity Rules section.
STEP 5 Enter the new password and click Apply.
When the login attempt is successful, the Getting Started page appears. If you entered an incorrect username or password, an error message appears and the Login page remains displayed on the window. If you are having problems logging in, please see the Launching the Configuration Utility section in the Administration Guide for additional information. Select Dont show this page on startup to prevent the Getting Started page from being displayed each time that you log on to the system. If you select this option, the System Summary page is opened instead of the Getting Started page.
HTTP/HTTPS
You can either open an HTTP session (not secured) by clicking Log In, or you can open an HTTPS (secured) session, by clicking Secure Browsing (HTTPS). You are asked to approve the logon with a default RSA key, and an HTTPS session is opened.
NOTE There is no need to input the username/password prior to clicking the Secure
Browsing (HTTPS) button. For information on how to configure HTTPS, see SSL Server.
Password Expiration
The New Password page appears: The first time you access the device with the default username cisco and password cisco. This page forces you to replace the factory default password. When the password expires, this page forces you to select a new password.
Getting Started
Starting the Web-based Configuration Utility
Logging Out
By default, the application logs out after ten minutes of inactivity. You can change this default value as described in the Defining Idle Session Timeout section.
!
CAUTION Unless the Running Configuration is copied to the Startup Configuration, rebooting
the device will remove all changes made since the last time the file was saved. Save the Running Configuration to the Startup Configuration before logging off to preserve any changes you made during this session. A flashing red X icon to the left of the Save application link indicates that Running Configuration changes have not yet been saved to the Startup Configuration file. The flashing can be disabled by clicking on the Disable Save Icon Blinking button on the Copy/Save Configuration page When the device auto-discovers a device, such as an IP phone (see What is a Smartport), and it configures the port appropriately for the device. These configuration commands are written to the Running Configuration file. This causes the Save icon to begin blinking when the you log on even though you did not make any configuration changes. When you click Save, the Copy/Save Configuration page appears. Save the Running Configuration file by copying it to the Startup Configuration file. After this save, the red X icon and the Save application link are no longer displayed. To logout, click Logout in the top right corner of any page. The system logs out of the device. When a timeout occurs or you intentionally log out of the system, a message appears and the Login page appears, with a message indicating the logged-out state. After you log in, the application returns to the initial page. The initial page displayed depends on the Do not show this page on startup option in the Getting Started page. If you did not select this option, the initial page is the Getting Started page. If you did select this option, the initial page is the System Summary page.
1
Quick Start Device Configuration
Getting Started
Quick Start Device Configuration
To simplify device configuration through quick navigation, the Getting Started page provides links to the most commonly used pages.
Links on the Getting Started page Category Link Name (on the Page) Change Management Applications and Services Change Device IP Address Create VLAN Configure Port Settings Device Status System Summary Port Statistics RMON Statistics View Log Quick Access Change Device Password Upgrade Device Software Backup Device Configuration Create MAC Based ACL Create IP Based ACL Configure QoS Configure Port Mirroring Linked Page TCP/UDP Services page IPv4 Interface page Create VLAN page Port Setting page System Summary page Interface page Statistics page RAM Memory page User Accounts page Upgrade/Backup Firmware/ Language page Download/Backup Configuration/Log page MAC Based ACL page IPv4 Based ACL page QoS Properties page Port and VLAN Mirroring page
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 Small Business Support Community page.
Getting Started
Interface Naming Conventions
1
Window Navigation
Getting Started
Window Navigation
This section describes the features of the web-based switch configuration utility.
Application Header
The Application Header appears on every page. It provides the following application links:
Application Links Application Link Name Description A flashing red X icon displayed to the left of the Save application link indicates that Running Configuration changes have been made that have not yet been saved to the Startup Configuration file. The flashing of the red X can be disabled on the Copy/Save Configuration page. Click Save to display the Copy/Save Configuration page. Save the Running Configuration file by copying it to the Startup Configuration file type on the device. After this save, the red X icon and the Save application link are no longer displayed. When the device is rebooted, it copies the Startup Configuration file type to the Running Configuration and sets the device parameters according to the data in the Running Configuration. Username Displays the name of the user logged on to the device. The default username is cisco. (The default password is cisco).
Getting Started
Window Navigation
1
Application Links (Continued) Application Link Name Language Menu Description This menu provides the following options: Select a language: Select one of the languages that appear in the menu. This language will be the webbased configuration utility language. Download Language: Add a new language to the device. Delete Language: Deletes the second language on the device. The first language (English) cannot be deleted. Debug: Used for translation purposes. If you select this option, all web-based configuration utility labels disappear and in their place are the IDs of the strings that correspond to the IDs in the language file.
NOTE To upgrade a language file, use the Upgrade/
Backup Firmware/Language page. Logout About Help Click to log out of the web-based switch configuration utility. Click to display the device name and device version number. Click to display the online help. The SYSLOG Alert Status icon appears when a SYSLOG message, above the critical severity level, is logged. Click the icon to open the RAM Memory page. After you access this page, the SYSLOG Alert Status icon is no longer displayed. To display the page when there is not an active SYSLOG message, Click Status and Statistics > View Log > RAM Memory.
1
Management Buttons
Getting Started
Window Navigation
The following table describes the commonly-used buttons that appear on various pages in the system.
Management Buttons Button Name Description Use the pull-down menu to configure the number of entries per page. Indicates a mandatory field.
Add
Click to display the related Add page and add an entry to a table. Enter the information and click Apply to save it to the Running Configuration. Click Close to return to the main page. Click Save to display the Copy/Save Configuration page and save the Running Configuration to the Startup Configuration file type on the device. Click to apply changes to the Running Configuration on the device. If the device is rebooted, the Running Configuration is lost, unless it is saved to the Startup Configuration file type or another file type. Click Save to display the Copy/Save Configuration page and save the Running Configuration to the Startup Configuration file type on the device. Click to reset changes made on the page. Click to clear the statistic counters for all interfaces.
Apply
Cancel Clear All Interfaces Counters Clear Interface Counters Clear Logs Clear Table Close
Click to clear the statistic counters for the selected interface. Clears log files. Clears table entries. Returns to main page. If any changes were not applied to the Running Configuration, a message appears.
Getting Started
Window Navigation
1
Management Buttons (Continued) Button Name Copy Settings Description A table typically contains one or more entries containing configuration settings. Instead of modifying each entry individually, it is possible to modify one entry and then copy the selected entry to multiple entries, as described below: 1. Select the entry to be copied. Click Copy Settings to display the popup. 2. Enter the destination entry numbers in the to field. 3. Click Apply to save the changes and click Close to return to the main page. Delete Details Edit After selecting an entry in the table, click Delete to remove. Click to display the details associated with the entry selected. Select the entry and click Edit . The Edit page appears, and the entry can be modified. 1. Click Apply to save the changes to the Running Configuration. 2. Click Close to return to the main page. Go Test Enter the query filtering criteria and click Go. The results are displayed on the page. Click Test to perform the related tests.
10
Getting Started
Window Navigation
11
2
Status and Statistics
This section describes how to view device statistics. It covers the following topics: Viewing Ethernet Interfaces Viewing Etherlike Statistics Viewing GVRP Statistics Viewing 802.1X EAP Statistics Viewing TCAM Utilization[ Managing RMON
InterfaceSelect the type of interface and specific interface for which Ethernet statistics are to be displayed. Refresh RateSelect the time period that passes before the interface Ethernet statistics are refreshed. The available options are: No RefreshStatistics are not refreshed.
12
2
-
15 SecStatistics are refreshed every 15 seconds. 30 SecStatistics are refreshed every 30 seconds. 60 SecStatistics are refreshed every 60 seconds.
The Receive Statistics area displays information about incoming packets. Total Bytes (Octets)Octets received, including bad packets and FCS octets, but excluding framing bits. Unicast PacketsGood Unicast packets received. Multicast PacketsGood Multicast packets received. Broadcast PacketsGood Broadcast packets received. Packets with ErrorsPackets with errors received.
The Transmit Statistics area displays information about outgoing packets. Total Bytes (Octets)Octets transmitted, including bad packets and FCS octets, but excluding framing bits. Unicast PacketsGood Unicast packets transmitted. Multicast PacketsGood Multicast packets transmitted. Broadcast PacketsGood Broadcast packets transmitted.
To clear statistics counters: Click Clear Interface Counters to clear counters for the interface displayed. Click View All Interfaces Statistics to see all ports on a single page.
13
STEP 1 Click Status and Statistics > Etherlike. STEP 2 Enter the parameters.
InterfaceSelect the type of interface and specific interface for which Ethernet statistics are to be displayed. Refresh RateSelect the amount of time that passes before the Etherlike statistics are refreshed.
The fields are displayed for the selected interface. Frame Check Sequence (FCS) ErrorsReceived frames that failed the CRC (cyclic redundancy checks). Single Collision FramesFrames that were involved in a single collision, but were successfully transmitted. Late CollisionsCollisions that have been detected after the first 512 bits of data. Excessive CollisionsNumber of transmissions rejected due to excessive collisions. Oversize PacketsPackets greater than 2000 octets received. Internal MAC Receive ErrorsFrames rejected because of receiver errors. Pause Frames ReceivedReceived flow control pause frames. Pause Frames TransmittedFlow control pause frames transmitted from the selected interface.
To clear statistics counters: Click Clear Interface Counters to clear the selected interfaces counters. Click View All Interfaces Statistics to see all ports on a single page.
14
2
Viewing GVRP Statistics
The GVRP page displays information regarding GARP VLAN Registration Protocol (GVRP) frames that were sent or received from a port. GVRP is a standards-based Layer 2 network protocol, for automatic configuration of VLAN information on switches. It was defined in the 802.1ak amendment to 802.1Q-2005. GVRP statistics for a port are only displayed if GVRP is enabled globally and on the port. See the GVRP page. To view GVRP statistics and/or set the refresh rate:
STEP 1 Click Status and Statistics > GVRP . STEP 2 Enter the parameters.
InterfaceSelect the specific interface for which GVRP statistics are to be displayed. Refresh RateSelect the time period that passes before the GVRP statistics page is refreshed.
The Attribute Counter block displays the counters for various types of packets per interface. Join EmptyNumber of GVRP Join Empty packets received/transmitted. EmptyNumber of GVRP empty packets received/transmitted. Leave EmptyNumber of GVRP Leave Empty packets received/ transmitted. Join InNumber of GVRP Join In packets received/transmitted. Leave InNumber of GVRP Leave In packets received/transmitted. Leave AllNumber of GVRP Leave All packets received/transmitted.
The GVRP Error Statistics section displays the GVRP error counters. Invalid Protocol IDInvalid protocol ID errors. Invalid Attribute TypeInvalid attribute ID errors. Invalid Attribute ValueInvalid attribute value errors. Invalid Attribute LengthInvalid attribute length errors. Invalid EventInvalid events.
15
2
Click Clear Interface Counters to clear the selected counters. Click View All Interfaces Statistics to see all ports on a single page.
refreshed. The values are displayed for the selected interface. EAPOL Frames ReceivedValid EAPOL frames received on the port. EAPOL Frames TransmittedValid EAPOL frames transmitted by the port. EAPOL Start Frames ReceivedEAPOL Start frames received on the port. EAPOL Logoff Frames ReceivedEAPOL Logoff frames received on the port. EAP Response/ID Frames ReceivedEAP Resp/ID frames received on the port. EAP Response Frames ReceivedEAP Response frames received by the port (other than Resp/ID frames). EAP Request/ID Frames TransmittedEAP Req/ID frames transmitted by the port. EAP Request Frames TransmittedEAP Request frames transmitted by the port.
16
Invalid EAPOL Frames ReceivedUnrecognized EAPOL frames received on this port. EAP Length Error Frames ReceivedEAPOL frames with an invalid Packet Body Length received on this port. Last EAPOL Frame VersionProtocol version number attached to the most recently received EAPOL frame. Last EAPOL Frame SourceSource MAC address attached to the most recently received EAPOL frame.
To clear statistics counters: Click Clear Interface Counters to clear the selected interfaces counters. Click Clear All Interface Counters to clear the counters of all interfaces.
17
2
Non-IP Rules In UseNumber of TCAM entries used for non-IP rules. MaximumNumber of available TCAM entries that can be used for nonIP rules.
Managing RMON
RMON (Remote Networking Monitoring) is an SNMP specification that 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 the correct thresholds set relative to your networks base line. RMON decreases the traffic between the manager and the device because the SNMP manager does not have to poll the device frequently for information, and enables the manager to get timely status reports, because the device reports events as they occur. With this feature, you can perform the following actions: View the current statistics (since the counter values were 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).
18
2
Late collision event has not been detected. Received (Rx) error event has not been detected. Packet has a valid CRC.
statistics are refreshed. The statistics are displayed for the selected interface. Bytes ReceivedNumber of octets received, including bad packets and FCS octets, but excluding framing bits. Drop EventsNumber of packets dropped. Packets ReceivedNumber of good packets received, including Multicast and Broadcast packets. Broadcast Packets ReceivedNumber of good Broadcast packets received. This number does not include Multicast packets. Multicast Packets ReceivedNumber of good Multicast packets received. CRC & Align ErrorsNumber of CRC and Align errors that have occurred. Undersize PacketsNumber of undersized packets (less than 64 octets) received. Oversize PacketsNumber of oversized packets (over 2000 octets) received. FragmentsNumber of fragments (packets with less than 64 octets, excluding framing bits, but including FCS octets) received. JabbersTotal number received packets that were 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: Packet data length is greater than MRU.
19
2
Packet has an invalid CRC. Received (Rx) Error Event has not been detected. CollisionsNumber of collisions received. If Jumbo Frames are enabled, the threshold of Jabber Frames is raised to the maximum size of Jumbo Frames. Frames of 64 BytesNumber of frames, containing 64 bytes that were received. Frames of 65 to 127 BytesNumber of frames, containing 65-127 bytes that were received. Frames of 128 to 255 BytesNumber of frames, containing 128-255 bytes that were received. Frames of 256 to 511 BytesNumber of frames, containing 256-511 bytes that were received. Frames of 512 to 1023 BytesNumber of frames, containing 512-1023 bytes that were received. Frames greater than 1024 BytesNumber of frames, containing 10242000 bytes, and Jumbo Frames, that were received.
To clear statistics counters: Click Clear Interface Counters to clear the selected interfaces counters. Click View All Interfaces Statistics to see all ports on a single page.
20
2
To enter RMON control information:
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 SamplesRMON is allowed by standard to not grant all requested samples, but rather to limit the number of samples per request. Therefore, this field represents the sample number actually granted to the request that is equal or less than the requested value.
New History EntryDisplays the number of the new History table entry. Source InterfaceSelect the type of interface from which the history samples are to be taken. Max No. of Samples to KeepEnter the number of samples to store. Sampling IntervalEnter the time in seconds that samples are collected from the ports. The field range is 1-3600. OwnerEnter 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
21
2
The fields are displayed for the selected sample. OwnerHistory table entry owner. Sample No.Statistics were taken from this sample. Drop EventsDropped packets due to lack of network resources during the sampling interval. This may not represent the exact number of dropped packets, but rather the number of times dropped packets were detected. Bytes ReceivedOctets received including bad packets and FCS octets, but excluding framing bits. Packets ReceivedPackets received, including bad packets, Multicast, and Broadcast packets. Broadcast PacketsGood Broadcast packets excluding Multicast packets. Multicast PacketsGood Multicast packets received. CRC Align ErrorsCRC and Align errors that have occurred. Undersize PacketsUndersized packets (less than 64 octets) received. Oversize PacketsOversized packets (over 2000 octets) received. FragmentsFragments (packets with less than 64 octets) received, excluding framing bits, but including FCS octets. JabbersTotal number of received packets that were longer than 2000 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. CollisionsCollisions received. UtilizationPercentage of current interface traffic compared to maximum traffic that the interface can handle.
22
2
To define RMON events:
STEP 1 Click Status and Statistics > RMON > Events.
Event EntryDisplays the event entry index number for the new entry. CommunityEnter the SNMP community string to be included when traps are sent (optional). DescriptionEnter a name for the event. This name is used in the Add RMON Alarm page to attach an alarm to an event. Notification TypeSelect the type of action that results from this event. Values are: NoneNo action occurs when the alarm goes off. Log (Event Log Table)Add a log entry to the Event Log table when the alarm is triggered. Trap (SNMP Manager and SYSLOG Server)Send a trap to the remote log server when the alarm goes off. Log and TrapAdd a log entry to the Event Log table and send a trap to the remote log server when the alarm goes off.
TimeThe time of the event. (This is a read-only table in the parent window and cannot be defined). OwnerEnter 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 Event Log Table to display the log of alarms that have occurred and that have
23
2
Viewing the RMON Events Logs
The Event Log Table 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 (see the Alarms page) and the conditions of the alarm have occurred.
STEP 1 Click Status and Statistics > RMON > Events. STEP 2 Click Event Log Table.
This page displays the following fields: Event Entry No.Events log entry number. Log No.Log number (within the event). Log TimeTime that the log entry was entered. DescriptionDescription of event that triggered the alarm.
24
2
To enter RMON alarms:
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. In addition to those fields, the following field appears: Counter ValueDisplays the value of the statistic during the last sampling period.
Alarm EntryDisplays the alarm entry number. InterfaceSelect the type of interface for which RMON statistics are displayed. Counter NameSelect the MIB variable that indicates the type of occurrence measured. Sample TypeSelect the sampling method to generate an alarm. The options are: AbsoluteIf the threshold is crossed, an alarm is generated. DeltaSubtracts 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.
Rising ThresholdEnter the value that triggers the rising threshold alarm. Rising EventSelect an event to be performed when a rising event is triggered. Events are created in the Events page. Falling ThresholdEnter the value that triggers the falling threshold alarm. Falling EventSelect an event to be performed when a falling event is triggered. Startup AlarmSelect 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 AlarmA rising value triggers the rising threshold alarm. Falling AlarmA falling value triggers the falling threshold alarm. Rising and FallingBoth rising and falling values trigger the alarm.
25
2
IntervalEnter the alarm interval time in seconds. OwnerEnter the name of the user or network management system that receives the alarm.
STEP 4 Click Apply. The RMON alarm is saved to the Running Configuration file.
26
27
3
Administration: System Log
This section describes the System Log feature, which enables the device to generate several 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. This section covers the following sections: Setting System Log Settings Setting Remote Logging Settings Viewing Memory Logs
28
3
EmergencySystem is not usable. AlertAction is needed. CriticalSystem is in a critical condition. ErrorSystem is in error condition. WarningSystem warning has occurred.
The event severity levels are listed from the highest severity to the lowest severity, as follows:
NoticeSystem is functioning properly, but a system notice has occurred. InformationalDevice information. DebugDetailed information about an event.
You can select different severity levels for RAM and Flash logs. These logs are displayed in the RAM Memory page and Flash Memory page, respectively. 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:
STEP 1 Click Administration > System Log > Log Settings. STEP 2 Enter the parameters.
LoggingSelect to enable message logging. Syslog AggregatorSelect to enable 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. Max Aggregation TimeEnter the interval of time that SYSLOG messages are aggregated.
29
3
Originator IdentifierEnables adding an origin identifier to SYSLOG messages. The options are: NoneDo not include the origin identifier in SYSLOG messages. HostnameInclude the system hostname in SYSLOG messages. IPv4 AddressInclude the IPv4 address of the sending interface in SYSLOG messages. IPv6 AddressInclude the IPv6 address of the sending interface in SYSLOG messages. User DefinedEnter a description to be included in SYSLOG messages.
RAM Memory LoggingSelect the severity levels of the messages to be logged to the RAM. Flash Memory LoggingSelect the severity levels of the messages to be logged to the Flash memory.
Server DefinitionSelect whether to identify the remote log server by IP address or name. IP VersionSelect the supported IP format. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are:
30
3
-
Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceSelect the link local interface (if IPv6 Address Type Link Local is selected) from the list. Log Server IP Address/NameEnter the IP address or domain name of the log server. UDP PortEnter the UDP port to which the log messages are sent. FacilitySelect 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. DescriptionEnter a server description. Minimum SeveritySelect the minimum level of system log messages to be sent to the server.
STEP 4 Click Apply. The Add Remote Log Server page closes, the SYSLOG server is
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.
31
RAM Memory
The RAM Memory page displays all messages that were saved in the RAM (cache) in chronological order. Entries are stored in the RAM log according to the configuration in the Log Settings page. To view log entries, click Status and Statistics > View Log > RAM Memory. The top of the page has a button that allows you to Disable Alert Icon Blinking. Click to toggle between disable and enable. This page contains the following fields: Log IndexLog entry number. Log TimeTime when message was generated. SeverityEvent severity. DescriptionMessage text describing the event.
To clear the log messages, click Clear Logs. The messages are cleared.
Flash Memory
The Flash Memory page displays the messages that were stored in the Flash memory, in chronological order. The minimum severity for logging is configured in the Log Settings page. 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. This page contains the following fields: Log IndexLog entry number. Log TimeTime when message was generated. SeverityEvent severity. DescriptionMessage text describing the event.
To clear the messages, click Clear Logs. The messages are cleared.
32
33
4
Administration: File Management
This section describes how system files are managed. The following topics are covered: System Files Upgrade/Backup Firmware/Language Active Image Download/Backup Configuration/Log Configuration Files Properties Copy/Save Configuration DHCP Auto Configuration
System Files
System files are files that contain configuration information, firmware images or boot code. Various actions can be performed with these files, such as: selecting the firmware file from which the device boots, copying various types of configuration files internally on the device, or copying files to or from an external device, such as an external server. The possible methods of file transfer are: Internal copy. HTTP/HTTPS that uses the facilities that the browser provides. TFTF/SCP client, requiring a TFTP/SCP server.
34
Configuration files on the device are defined by their type, and contain the settings and parameter values for the device. When a configuration is referenced on the device, it is referenced by its configuration file type (such as Startup Configuration or Running Configuration), as opposed to a file name that can be modified by the user. Content can be copied from one configuration file type to another, but the names of the file types cannot be changed by the user. Other files on the device include firmware, boot code, and log files, and are referred to as operational files. The configuration files are text files and can be edited in a text editor, such as Notepad after they are copied to an external device, such as a PC.
35
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. The option of automatically copying the Running Configuration to the mirror configuration can be disabled in the Configuration Files Properties page. Backup ConfigurationA manual copy of a configuration file used for protection against system shutdown or for the maintenance of a specific operating state. You can copy the Mirror Configuration, Startup Configuration, or Running Configuration to a Backup Configuration file. The Backup Configuration exists in Flash and is preserved if the device is rebooted. FirmwareThe program that controls the operations and functionality of the device. More commonly referred to as the image. Boot CodeControls the basic system startup and launches the firmware image. Language FileThe dictionary that enables the web-based configuration utility windows to be displayed in the selected language. Flash LogSYSLOG messages stored in Flash memory.
File Actions
The following actions can be performed to manage firmware and configuration files: Upgrade the firmware or boot code, or replace a second language, as described in Upgrade/Backup Firmware/Language section. View the firmware image currently in use or select the image to be used in the next reboot as described in the Active Image section. Save configuration files on the device to a location on another device as described in the Download/Backup Configuration/Log section. Clear the Startup Configuration or Backup Configuration file types as described in the Configuration Files Properties section. Copy one configuration file type to another configuration file type as described in the Copy/Save Configuration section. Enable automatically uploading a configuration file from a DHCP server to the device, as described in the DHCP Auto Configuration section.
36
4
This section covers the following topics: Upgrade/Backup Firmware/Language Active Image Download/Backup Configuration/Log Configuration Files Properties Copy/Save Configuration DHCP Auto Configuration
Upgrade/Backup Firmware/Language
The Upgrade/Backup Firmware/Language process can be used to: Upgrade or backup the firmware image. Upgrade or backup the boot code. Import or upgrade a second language file.
The following methods for transferring files are supported: HTTP/HTTPS that uses the facilities provided by the browser TFTP that requires a TFTP server Secure Copy Protocol (SCP) that requires an SCP server
If a new language file was loaded onto the device, the new language can be selected from the drop-down menu. (It is not necessary to reboot the device). There are two firmware images stored on the device. One of the images is identified as the active image and other image is identified as the inactive image. When you upgrade the firmware, the new image always replaces the image identified as the inactive image. Even after uploading new firmware on the device, the device continues to boot by using the active image (the old version) until you change the status of the new image to be the active image by using the procedure in the Active Image section. Then boot the device.
37
Language.
STEP 2 Click the Transfer Method. Proceed as follows:
If you selected TFTP, go to STEP 3. If you selected via HTTP/HTTPS, go to STEP 4. If you selected via SCP, go to STEP 5.
STEP 3 If you selected via TFTP, enter the parameters as described in this step.
Otherwise, skip to STEP 4. Select one of the following Save Actions: UpgradeSpecifies that the file type on the device is to be replaced with a new version of that file type located on a TFTP server. BackupSpecifies that a copy of the file type is to be saved to a file on another device.
Enter the following fields: File TypeSelect the destination file type. Only valid file types are shown. (The file types are described in the Files and File Types section). TFTP Server DefinitionSelect whether to specify the TFTP server by IP address or domain name. IP VersionSelect whether an IPv4 or an IPv6 address is used. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
38
Link Local InterfaceSelect the link local interface (if IPv6 is used) from the list. TFTP Server IP Address/NameEnter the IP address or the domain name of the TFTP server. (For Upgrade) Source File NameEnter the name of the source file. (For Backup) Destination File NameEnter the name of the backup file.
STEP 4 If you selected via HTTP/HTTPS, you can only Upgrade. Enter the parameters as
described in this step. File TypeSelect one of the following file types: Firmware ImageSelect this to upgrade the firmware image. LanguageSelect this to upgrade the language file.
File NameClick Browse to select a file or enter the path and source file name to be used in the transfer.
STEP 5 If you selected via SCP (Over SSH), see SSH Client Authentication for
instructions. Then, enter the following fields: (only unique fields are described, for non-unique fields, see the descriptions above) Remote SSH Server AuthenticationTo enable SSH server authentication (which is disabled by default), click Edit. This takes you to the SSH Server Authentication page to configure the SSH server, and return to this page. Use the SSH Server Authentication page to select an SSH user authentication method (password or public/private key), set a username and password on the device (if the password method is selected), and generate an RSA or DSA key if required.
SSH Client AuthenticationClient authentication can be done in one of the following ways: Use SSH Client System CredentialsSets permanent SSH user credentials. Click System Credentials to go to the SSH User Authentication page where the user/password can be set once for all future use. Use SSH Client One-Time CredentialsEnter the following: UsernameEnter a username for this copy action. PasswordEnter a password for this copy.
NOTE The username and password for one-time credential will not saved in configuration file.
39
Select one of the following Save Actions: UpgradeSpecifies that the file type on the device is to be replaced with a new version of that file type located on a TFTP server. BackupSpecifies that a copy of the file type is to be saved to a file on another device.
Enter the following fields: File TypeSelect the destination file type. Only valid file types are shown. (The file types are described in the Files and File Types section). SCP Server DefinitionSelect whether to specify the SCP server by IP address or by domain name. IP VersionSelect whether an IPv4 or an IPv6 address is used. IPv6 Address TypeSelect the IPv6 address type (if used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPv6 type that is visible and reachable from other networks.
Link-Local InterfaceSelect the link local interface from the list. SCP Server IP Address/NameEnter the IP address or domain name of the SCP server. (For Upgrade) Source File NameEnter the name of the source file. (For Backup) Destination File NameEnter the name of the backup file.
STEP 6 Click Apply. If the files, passwords and server addresses are correct, one of the
following may happen: If SSH server authentication is enabled (in the SSH Server Authentication page), and the SCP server is trusted, the operation succeeds. If the SCP server is not trusted, the operation fails and an error is displayed.
40
If SSH server authentication is not enabled, the operation succeeds for any SCP server.
Active Image
There are two firmware images stored on the device. One of the images is identified as the active image and other image is identified as the inactive image. The device boots from the image you set as the active image. You can change the image identified as the inactive image to the active image. (You can reboot the device by using the process described in the Rebooting the Device section). To select the active image:
STEP 1 Click Administration > File Management > Active Image.
The page displays the following: Active ImageDisplays the image file that is currently active on the device. Active Image Version NumberDisplays the firmware version of the active image. Active Image After RebootDisplays the image that is active after reboot. Active Image Version Number After RebootDisplays the firmware version of the active image as it be after reboot.
STEP 2 Select the image from the Active Image After Reboot menu to identify the
firmware image that is used as the active image after the device is rebooted. The Active Image Version Number After Reboot displays the firmware version of the active image that is used after the device is rebooted.
STEP 3 Click Apply. The active image selection is updated.
Download/Backup Configuration/Log
The Download/Backup Configuration/Log page enables:
41
When restoring a configuration file to the Running Configuration, the imported file adds any configuration commands that did not exist in the old file and overwrites any parameter values in the existing configuration commands. When restoring a configuration file to the Startup Configuration or a backup configuration file, the new file replaces the previous file. When restoring to Startup Configuration, the device must be rebooted for the restored Startup Configuration to be used as the Running Configuration. You can reboot the device by using the process described in the Rebooting the Device section.
See Configuration After Reboot for a description of what happens when the stacking modes are changed.
42
Log.
STEP 2 Select the Transfer Method. STEP 3 If you selected via TFTP, enter the parameters. Otherwise, skip to STEP 4.
Select either Download or Backup as the Save Action. Download Save ActionSpecifies that the file on another device replaces a file type on the device. Enter the following fields: a. Server DefinitionSelect whether to specify the TFTP server by IP address or by domain name. b. IP VersionSelect whether an IPv4 or an IPv6 address is used.
NOTE If the server is selected by name in the Server Definition, there is no
need to select the IP Version related options. c. IPv6 Address TypeSelect the IPv6 address type (if used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
d. Link-Local InterfaceSelect the link local interface from the list. e. TFTP ServerEnter the IP address of the TFTP server. f. Source File NameEnter the source file name. File names cannot contain slashes (\ or /), cannot start with a period (.), and must include between 1 and 160 characters. (Valid characters: A-Z, a-z, 0-9, ., -, _).
g. Destination File TypeEnter the destination configuration file type. Only valid file types are displayed. (The file types are described in the Files and File Types section).
43
Backup Save ActionSpecifies that a file type is to be copied to a file on another device. Enter the following fields: a. Server DefinitionSelect whether to specify the TFTP server by IP address or by domain name. b. IP VersionSelect whether an IPv4 or an IPv6 address is used. c. IPv6 Address TypeSelect the IPv6 address type (if used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
d. Link-Local InterfaceSelect the link local interface from the list. e. TFTP Server IP Address/NameEnter the IP address or domain name of the TFTP server. f. Source File TypeEnter the source configuration file type. Only valid file types are displayed. (The file types are described in the Files and File Types section).
g. Sensitive DataSelect how sensitive data should be included in the backup file. The following options are available: ExcludeDo not include sensitive data in the backup. EncryptedInclude sensitive data in the backup in its encrypted form. PlaintextInclude sensitive data in the backup in its plaintext form.
NOTE The available sensitive data options are determined by the current user SSD rules. For details, refer to Secure Sensitive Data Management > SSD Rules page.
h. Destination File NameEnter the destination file name. File names cannot contain slashes (\ or /), the leading letter of the file name must not be a period (.), and the file name must be between 1 and 160 characters. (Valid characters: A-Z, a-z, 0-9, ., -, _). i. Click Apply. The file is upgraded or backed up.
44
4
Select the Save Action.
STEP 4 If you selected via HTTP/HTTPS, enter the parameters as described in this step.
If Save Action is Download (replacing the file on the device with a new version from another device), do the following. Otherwise, go to the next procedure in this step. a. Source File NameClick Browse to select a file or enter the path and source file name to be used in the transfer. b. Destination File TypeSelect the configuration file type. Only valid file types are displayed. (The file types are described in the Files and File Types section). c. Click Apply. The file is transferred from the other device to the device. If Save Action is Backup (copying a file to another device), do the following: a. Source File TypeSelect the configuration file type. Only valid file types are displayed. (The file types are described in the Files and File Types section). b. Sensitive DataSelect how sensitive data should be included in the backup file. The following options are available: ExcludeDo not include sensitive data in the backup. EncryptedInclude sensitive data in the backup in its encrypted form. PlaintextInclude sensitive data in the backup in its plaintext form.
NOTE The available sensitive data options are determined by the current user SSD rules. For details, refer to Secure Sensitive Data Management > SSD Rules page.
GUI for instructions. Then enter the following fields: Remote SSH Server AuthenticationTo enable SSH server authentication (it is disabled by default), click Edit, which takes you to the SSH Server Authentication page to configure this, and return to this page. Use the SSH Server Authentication page to select an SSH user authentication method (password or public/private key), set a username and password on the device, if the password method is selected, and generate an RSA or DSA key if required.
45
SSH Client AuthenticationClient authentication can be done in one of the following ways: Use SSH ClientSets permanent SSH user credentials. Click System Credentials to go to the SSH User Authentication page where the user/ password can be set once for all future use. Use SSH Client One-Time CredentialsEnter the following: UsernameEnter a username for this copy action. PasswordEnter a password for this copy.
SCP Server DefinitionSelect whether to specify the TFTP server by IP address or by domain name. IP VersionSelect whether an IPv4 or an IPv6 address is used. IPv6 Address TypeSelect the IPv6 address type (if used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link-Local InterfaceSelect the link local interface from the list. SCP Server IP Address/NameEnter the IP address or domain name of the TFTP server.
If Save Action is Download (replacing the file on the device with a new version from another device), enter the following fields. Source File NameEnter the name of the source file. Destination File TypeSelect the configuration file type. Only valid file types are displayed. (The file types are described in the Files and File Types section).
46
If Save Action is Backup (copying a file to another device), enter the following fields (in addition to those fields listed above): Source File TypeSelect the configuration file type. Only valid file types are displayed. (The file types are described in the Files and File Types section). Sensitive DataSelect how sensitive data should be included in the backup file. The following options are available: ExcludeDo not include sensitive data in the backup. EncryptedInclude sensitive data in the backup in its encrypted form. PlaintextInclude sensitive data in the backup in its plaintext form.
NOTE The available sensitive data options are determined by the current user SSD rules. For details, refer to Secure Sensitive Data Management > SSD Rules page.
creation of mirror configuration files. When disabling this feature, the mirror configuration file, if it exists, is deleted. See System Files for a description of mirror files and why you might not want to automatically create mirror configuration files.
47
STEP 3 If required, select either the Startup Configuration, Backup Configuration or both
and click Clear Files to delete these files. This page provides the following fields: Configuration File NameDisplays the type of file. Creation TimeDisplays the date and time that file was modified.
Copy/Save Configuration
When you click Apply on any window, changes that you made to the device configuration settings are stored only in the Running Configuration. To preserve the parameters in the Running Configuration, the Running Configuration must be copied to another configuration type or saved on another device.
!
CAUTION Unless the Running Configuration is copied to the Startup Configuration or another
configuration file, all changes made since the last time the file was copied are lost when the device is rebooted. The following combinations of copying internal file types are allowed: From the Running Configuration to the Startup Configuration or Backup Configuration. From the Startup Configuration to the Running Configuration, Startup Configuration or Backup Configuration. From the Backup Configuration to the Running Configuration, Startup Configuration or Backup Configuration. From the Mirror Configuration to the Running Configuration, Startup Configuration or Backup Configuration.
48
STEP 3 Select the Destination File Name to be overwritten by the source file.
If you are backing up a configuration file, select one of the following formats for the backup file. ExcludeSensitive data is not included in the backup file. EncryptedSensitive data is included in the backup file in encrypted form. PlaintextSensitive data is included in the backup file in plain text.
NOTE The available sensitive data options are determined by the current
user SSD rules. For details, refer to Secure Sensitive Data Management > SSD Rules page.
STEP 4 The Save Icon Blinking field indicates whether an icon blinks when there is
unsaved data. To disable/enable this feature, click Disable/Enable Save Icon Blinking.
STEP 5 Click Apply. The file is copied.
49
After reboot when an IP address is allocated or renewed dynamically (using DHCPv4). Upon an explicit DHCPv4 renewal request and if the device and the server are configured to do so. Upon automatic renewal of the DHCPv4 lease.
DHCPv6 Auto Configuration is triggered when the following conditions are fulfilled: When a DHCPv6 server sends information to the device. This occurs in the following cases: When an interface, which is IPv6 enabled, is defined as a DHCPv6 stateless configuration client. When DHCPv6 messages are received from the server (for example, when you press the Restart button on IPv6 Interfaces page, When DHCPv6 information is refreshed by the device. After rebooting the device when stateless DHCPv6 client is enabled.
When the DHCPv6 server packets contain the configuration filename option.
50
extension are downloaded using SCP, and files with the other extensions are downloaded using TFTP. TFTP OnlyThe download is done through TFTP regardless of the file extension of the configuration file name. SCP OnlyThe download is done through SCP (over SSH) regardless of the file extension of the configuration file name.
NOTE The SSH Client authentication parameters can also be used when downloading a
file for manual download (a download that is not performed through the DHCP Auto Configuration feature).
51
4
For DHCPv4: SCPThe Auto Configuration process is halted. TFTPThe device sends TFTP Request messages to a limited Broadcast address (for IPv4) or ALL NODES address (for IPv6) on its IP interfaces and continues the process of Auto Configuration with the first answering TFTP server.
If the DHCP server did not send these options and the backup TFTP/SCP server address parameter is empty then: -
If the configuration filename was supplied by the DHCP server (DHCPv4: option 67, DHCPv6: option 60), then the copy protocol (SCP/TFTP) is selected as described in Auto Configuration Download Protocol (TFTP or SCP). When downloading using SCP, the device accepts any specified SCP/SSH server (without authentication) if either of the following is true: The SSH server authentication process is disabled. Note that by default the SSH server authentication is disabled in order to allow downloading configuration file for devices with factory default configuration (for example out-of-box devices). The SSH Server is configured in the SSH Trusted Servers list.
If the SSH server authentication process is enabled, and the SSH server is not found in the SSH Trusted Servers list, the Auto Configuration process is halted. If the information is available, the TFTP/SCP server is accessed to download the file from it. The download process is done only if the new configuration filename is different from the current configuration filename (even if the current configuration file is empty). A SYSLOG message is generated acknowledging that the Auto Configuration process is completed.
52
4
Workflow
To configure DHCP Auto Configuration.
1. Configure the DHCPv4 and/or DHCPv6 servers to send the required options. this process is not described in this guide. 2. Configure Auto Configuration parameters. 3. Define the device as a DHCPv4 client in the Defining an IPv4 Interface in Layer 2 System Mode or Defining IPv4 Interface in Layer 3 System Mode pages, and/or define the device as a DHCPv6 client in the IPv6 Interface page.
Web Configuration
The DHCP Auto Configuration page is used to perform the following actions when the information is not provided in a DHCP message: Enable the DHCP auto configuration feature. Specify the download protocol. Configure the device to receive configuration information from a specific file on a specific server.
Note the following regarding the DHCP auto configuration process: A configuration file that is placed on the TFTP/SCP server must match the form and format requirements of the supported configuration file. The form and format of the file are checked, but the validity of the configuration parameters is not checked prior to loading it to the Startup Configuration. In IPv4, to ensure that the device configuration functions as intended, due to allocation of different IP addresses with each DHCP renew cycle, it is recommended that IP addresses be bound to MAC addresses in the DHCP server table. This ensures that each device has its own reserved IP address and other relevant information.
Auto Configuration Via DHCPSelect this field to enable DHCP Auto Configuration. This feature is enabled by default, but can be disabled here.
53
4
Auto By File ExtensionSelect to indicate that auto configuration uses
the TFTP or SCP protocol depending on the extension of the configuration file. If this option is selected, the extension of the configuration file does not necessarily have to be given. If it is not given, the default extension is used (as indicated below).
File Extension for SCPIf Auto By File Extension is selected, you can indicate a file extension here. Any file with this extension is downloaded using SCP. If no extension is entered, the default file extension.scp is used. TFTP OnlySelect to indicate that only the TFTP protocol is to be used
for auto configuration.
SCP OnlySelect to indicate that only the SCP protocol is to be used for
auto configuration.
SSH Settings for SCPWhen using SCP for downloading the configuration files, select one of the following options: -
Remote SSH Server AuthenticationClick on the Enable/Disable link to navigate to the SSH Server Authentication page. There you can enable authentication of the SSH server to be used for the download and enter the trusted SSH server if required. SSH Client AuthenticationClick on the System Credentials link to enter
user credentials in the SSH User Authentication page.
STEP 3 Enter the following optional information to be used if no configuration file name
was received from the DHCP server. Backup Server DefinitionSelect By IP address or By name to configure the server. IP VersionSelect whether an IPv4 or an IPv6 address is used. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration.
54
GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceSelect the link local interface (if IPv6 is used) from the list. Backup Server IP Address/NameEnter the IP address or the name of the server to be used if no server IP address was specified in the DHCP message. Backup Configuration File NameEnter the path and file name of the file to be used if no configuration file name was specified in the DHCP message.
STEP 4 Click Apply. The parameters are copied to the Running Configuration file.
55
5
Administration: General Information
This section describes how to view system information and configure various options on the device. It covers the following topics: Device Models System Information Console Settings (Autobaud Rate Support)Rebooting the Device Routing Resources Monitoring Fan Status Defining Idle Session Timeout Pinging a Host Traceroute
Device Models
All models can be fully managed through the web-based switch configuration utility. In Layer 2 system mode, the device forwards packets as a VLAN-aware bridge. In Layer 3 system mode, the device performs both IPv4 routing and VLAN-aware bridging. When the device operates in Layer 3 system mode, the VLAN Rate Limit, and QoS policers are not operational. Other QoS Advanced mode features are operational.
NOTE The following port conventions are used:
56
The following table describes the various models, the number and type of ports on them and their PoE information. Managed Switch Models Model Name Product ID (PID) Description of Ports on Device Power Dedicated to PoE No. of Ports that Support PoE
SG300-10 SG30010MP SG30010P SG300-20 SG300-28 SG30028P SG300-52 SF300-08 SF302-08 SF30208MP SF30208P SF300-24 SF30024P
SRW2008-K9 SRW2008MP -K9 SRW2008PK9 SRW2016-K9 SRW2024-K9 SRW2024PK9 SRW2048-K9 SRW208-K9 SRW208GK9 SRW208MPK9 SRW208P-K9 SRW224G4K9 SRW224G4P -K9
8 GE ports, and 2 special-purpose combo ports (GE/SFP) 8 GE ports, and 2 special-purpose combo ports (GE/SFP) 8 GE ports, and 2 special-purpose combo ports (GE/SFP) 16 GE ports, and 4 special purpose ports - 2 uplinks and 2 combo ports 24 GE ports, and 4 special-purpose ports - 2 uplinks and 2 combo-ports 24 GE ports, and 4 special-purpose ports - 2 uplinks and 2 combo-ports. 48 GE ports, and 4 special-purpose ports - 2 uplinks and 2 combo-ports 8 FE ports. 8 FE ports plus 2 GE ports 8 FE ports plus 2 GE ports 8 FE ports plus 2 GE ports 24 FE ports plus 4 GE special-purpose ports - 2 uplinks and 2 combo-ports. 24 FE ports plus 4 GE special-purpose ports - 2 uplinks and 2 combo-ports. 124W 62W N/A N/A 180W N/A N/A N/A 124W 62W N/A 180W 8 8 N/A N/A 24 N/A N/A N/A 8 8 N/A 24
57
5
Power Dedicated to PoE N/A 375W 740W N/A N/A N/A No. of Ports that Support PoE N/A 48 48 N/A N/A N/A
Managed Switch Models (Continued) Model Name Product ID (PID) Description of Ports on Device
48 FE ports plus 4 GE special-purpose ports - 2 uplinks and 2 combo-ports 48 FE ports plus 4 GE special-purpose ports - 2 uplinks and 2 combo-ports 52-Port Gigabit PoE Managed Switch 10-Port Gigabit Managed SFP Switch 52-Port Gigabit Managed Switch 52-Port Gigabit Managed Switch
24-Port 10/100 PoE Managed Switch 28-Port Gigabit PoE Managed Switch
375W 375W
24 24
System Information
The System Summary page provides a graphic view of the device, and displays device status, hardware information, firmware version information, general PoE status, and other items.
58
5
System Information:
System DescriptionA description of the system. System LocationPhysical location of the device. Click Edit to go the System Settings page to enter this value. System ContactName of a contact person. Click Edit to go the System Settings page to enter this value. Host NameName of the device. Click Edit to go the System Settings page to enter this value. By default, the device hostname is composed of the word device concatenated with the three least significant bytes of the device MAC address (the six furthest right hexadecimal digits). System UptimeTime that has elapsed since the last reboot. Current TimeCurrent system time. Base MAC AddressDevice MAC address. Jumbo FramesJumbo frame support status. This support can be enabled or disabled by using the Port Settings page of the Port Management menu.
NOTE Jumbo frames support takes effect only after it is enabled, and after
the device is rebooted. TCP/UDP Services Status: HTTP ServiceDisplays whether HTTP is enabled/disabled. HTTPS ServiceDisplays whether HTTPS is enabled/disabled. SNMP ServiceDisplays whether SNMP is enabled/disabled. Telnet ServiceDisplays whether Telnet is enabled/disabled. SSH ServiceDisplays whether SSH is enabled/disabled.
Other Summary Information: Model DescriptionDevice model description. Serial NumberSerial number. PID VIDPart number and version ID.
59
Firmware Version (Active Image)Firmware version number of the active image. Firmware MD5 Checksum (Active Image)MD5 checksum of the active image. Firmware Version (Non-active Image)Firmware version number of the non-active image. Firmware MD5 Checksum (Non-active Image)MD5 checksum of the non-active image. Boot VersionBoot version number. Boot MD5 ChecksumMD5 checksum of the boot version. LocaleLocale of the first language. (This is always English). Language VersionLanguage package version of the first or English language. Language MD5 ChecksumMD5 checksum of the language file.
PoE Power Information: Maximum Available PoE Power (W)Maximum available power that can be delivered by the PoE. Total PoE Power Consumption (W)Total PoE power delivered to connected PoE devices. PoE Power ModePort Limit or Class Limit.
System DescriptionDisplays a description of the device. System LocationEnter the location where the device is physically located. System ContactEnter the name of a contact person.
60
5
-
Host NameSelect the host name of this device. This is used in the prompt of CLI commands: Use DefaultThe 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 DefinedEnter the hostname. Use only letters, digits, and hyphens. Host names cannot begin or end with a hyphen. No other symbols, punctuation characters, or blank spaces are permitted (as specified in RFC1033, 1034, 1035).
require a reboot, and the startup configuration file will be gone after the boot. L2Select to place the device in Layer 2 system mode. L3Select to place the device in Layer 3 system mode.
Custom Login Screen SettingsTo display text on the Login page, enter the text in the Login Banner text box. Click Preview to view the results.
NOTE 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).
STEP 3 Click Apply to save the values in the Running Configuration file.
61
After Auto Detection is enabled in the Console Settings page, it can be activated by connecting the console to the device and press the Enter key twice. The device detects the baud rate automatically. To enable Auto Detection or to manually set the baud rate of the console:
STEP 1 Click Administration > Console Settings. STEP 2 Select one of the following:
Auto DetectionThe console baud rate is detected automatically. StaticSelect one of the available speeds.
62
5
To reboot the device:
STEP 1 Click Administration > Reboot .
RebootReboots the device. Since any unsaved information in the Running Configuration is discarded when the device is rebooted, you must click Save in the upper-right corner of any window to preserve current configuration across the boot process. If the Save option is not displayed, the Running Configuration matches the Startup Configuration and no action is necessary. The following options are available: ImmediateReboot immediately. DateEnter the date (month/day) and time (hour and minutes) of the schedule reboot. This schedules a reload of the software to take place at the specified time (using a 24-hour clock). If you specify the month and day, the reload is scheduled to take place at the specified time and date. If you do not specify the month and day, the reload takes place at the specified time on the current day (if the specified time is later than the current time) or on the next day (if the specified time is earlier than the current time). Specifying 00:00 schedules the reload for midnight. The reload must take place within 24 days.
NOTE This option can only be used if the system time has either been set manually or by SNTP.
InReboot within the specified number of hours and minutes. The maximum amount of time that can pass is 24 days.
Reboot to Factory DefaultsReboots the device by using the factory default configuration. This process erases the Startup Configuration file and the backup configuration file. The mirror configuration file is not deleted when restoring to factory defaults.
Clear Startup Configuration FileCheck to clear the startup configuration on the device for the next time it boots up.
NOTE Clearing the Startup Configuration File and Rebooting is not the same
63
Routing Resources
Use the Router Resources page to display TCAM allocation and modify total TCAM size. TCAM entries are divided into the following groups: IP EntriesTCAM entries reserved for IP static routes, IP addresses on the device, and IP hosts. Each type generates the following number of TCAM entries: IPv4 static routesOne entry per route IP AddressesTwo entries per IP address IP HostsOne entry per host
Non-IP EntriesTCAM entries reserved for other applications, such as ACL rules, CoS policers, and VLAN rate limits.
The following fields are displayed: NeighborsCount is the number of neighbors recorded on the device and TCAM Entries is the total number of TCAM entries being used for neighbors. InterfacesCount is the number of IP addresses on interfaces on the device and TCAM Entries is the total number of TCAM entries being used for the IP addresses. RoutesCount is the number of routes recorded on the device and TCAM Entries is the total number of TCAM entries being used for the routes. TotalDisplays the number of TCAM entries which are currently being used. Maximum EntriesSelect one of the following options: Use DefaultThe number of TCAM entries available for IP entries is 25% of the TCAM size (128). User DefinedEnter a value up to 512 entries.
64
You must save your current configuration before changing the TCAM Allocation Settings.
NOTE A summary of the TCAM entries actually in use and available is
displayed at the bottom of this page. For an explanation of the fields, see Viewing TCAM Utilization[.
STEP 2 Save the new settings by clicking Apply. This checks the feasibility of the TCAM
allocation. If it is incorrect, an error message is displayed. If it is correct, the allocation is saved to the Running Configuration file and a reboot is performed.
65
5
Action The following are generated: SYSLOG message SNMP trap
The following actions are performed: System LED is set to solid amber (if hardware supports this). Disable Ports When the Critical temperature has been exceeded for two minutes, all ports will be shut down. (On devices that support PoE) Disable the PoE circuitry so that less power is consumed and less heat is emitted.
Cool down period after the Critical threshold was exceeded (all sensors are lower than the Warning threshold - 2 C).
After all the sensors cool down to Warning Threshold minus 2 degree C, the PHY will be reenabled, and all ports brought back up. If FAN status is OK, the ports are enabled. (On devices that support PoE) the PoE circuitry is enabled.
To view the device health parameters, click Status and Statistics > Health. The Health page displays the following fields: Fan StatusFan status. The following values are possible: OKFan is operating normally. FailFan is not operating correctly. N/AFan ID is not applicable for the specific model.
Fan Direction(On relevant devices) The direction that the fans are working in (for example: Front to Back).
66
5
Defining Idle Session Timeout
The Idle Session Timeout configures the time intervals that the management sessions can remain idle before they timeout and you must log in again to reestablish one of the following sessions: HTTP Session Timeout HTTPS Session Timeout Console Session Timeout Telnet Session Timeout SSH Session Timeout
Pinging a Host
Ping is a utility used to test if a remote host can be reached and to measure the round-trip time for packets sent from the device to a destination device. 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:
STEP 1 Click Administration > Ping. STEP 2 Configure ping by entering the fields:
67
IP VersionIf the host is identified by its IP address, select either IPv4 or IPv6 to indicate that it will be entered in the selected format. IPv6 Address TypeSelect Link Local or Global as the type of IPv6 address to enter. Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceIf the IPv6 address type is Link Local, select from where it is received. Host IP Address/NameAddress or host name of the device to be pinged. Whether this is an IP address or host name depends on the Host Definition. Ping IntervalLength of time the system waits between ping packets. Ping is repeated the number of times configured in the "Number of Pings" field, whether the ping succeeds or not. Choose to use the default interval or specify your own value. Number of PingsThe number of times the ping operation is performed. Choose to use the default or specify your own value. StatusDisplays whether the ping succeeded or failed.
STEP 3 Click Activate Ping to ping the host. The ping status appears and another
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.
68
5
Traceroute
Traceroute discovers the IP routes along which packets were 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 into the following fields:
Host DefinitionSelect whether hosts are identified by their IP address or name. IP VersionIf the host is identified by its IP address, select either IPv4 or IPv6 to indicate that it will be entered in the selected format. IPv6 Address TypeSelect Link Local or Global as the type of IPv6 address to enter. Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceIf the IPv6 address type is Link Local, select from where it is received. Host IP Address/NameEnter the host address or name. TTLEnter 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 . TimeoutEnter the length of time that the system waits for a frame to return before declaring it lost, or select Use Default .
69
A page appears showing the Round Trip Time (RTT) and status for each trip in the fields: IndexDisplays the number of the hop. HostDisplays a stop along the route to the destination. Round Trip Time (1-3)Displays the round trip time in (ms) for the first through third frame and the status of the first through third operation.
70
71
6
Administration: 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 Simple Network Time Protocol (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. This section describes the options for configuring the system time, time zone, and Daylight Savings Time (DST). It covers the following topics: System Time Options SNTP Modes Configuring System Time
72
6
System Time Options
System time can be set manually by the user, dynamically from an SNTP server, or synchronized from the PC running the GUI. If an SNTP server is chosen, the manual time settings are overwritten when communications with the server are established. As part of the boot process, the device always configures the time, time zone, and DST. These parameters are obtained from the PC running the GUI, SNTP, values set manually, or if all else fails, from the factory defaults.
Time
The following methods are available for setting the system time on the device: ManualYou must manually sets the time. From PCTime can be received from the PC by using browser information. The configuration of time from the computer is saved to the Running Configuration file. You must copy the Running Configuration to the Startup Configuration in order to enable the device to use the time from the computer after reboot. The time after reboot is set during the first WEB login to the device. When you configure this feature for the first time, if the time was not already set, the device sets the time from the PC. This method of setting time works with both HTTP and HTTPS connections. SNTPTime can be received from SNTP time servers. SNTP ensures accurate network time synchronization of the device up to the millisecond by using an SNTP server for the clock source. When specifying an SNTP server, if choosing to identify it by hostname, three suggestions are given in the GUI: time-a.timefreq.bldrdoc.gov time-b.timefreq.bldrdoc.gov time-c.timefreq.bldrdoc.gov
After the time has been set by any of the above sources, it is not set again by the browser.
NOTE SNTP is the recommended method for time setting.
73
6
Dynamic configuration of the device through a DHCP server, where: Dynamic DST, when enabled and available, always takes precedence over the manual configuration of DST. If the server supplying the source parameters fails, or dynamic configuration is disabled by the user, the manual settings are used. Dynamic configuration of the time zone and DST continues after the IP address lease time has expired.
Manual configuration of the time zone and DST becomes the Operational time zone and DST, only if the dynamic configuration is disabled or fails.
NOTE The DHCP server must supply DHCP option 100 in order for dynamic
SNTP Modes
The device can receive the system time from an SNTP server in one of the following ways: Client Broadcast Reception (passive mode) SNTP servers broadcast the time, and the device listens to these broadcasts. When the device is in this mode, there is no need to define a Unicast SNTP server. Client Broadcast Transmission (active mode)The device, as an SNTP client, periodically requests SNTP time updates. This mode works in either of the following ways: SNTP Anycast Client ModeThe device broadcasts time request packets to all SNTP servers in the subnet, and waits for a response. Unicast SNTP Server ModeThe device sends Unicast queries to a list of manually-configured SNTP servers, and waits for a response.
The device supports having all of the above modes active at the same time and selects the best system time received from an SNTP server, according to an algorithm based on the closest stratum (distance from the reference clock).
74
6
Configuring System Time
Selecting Source of 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 If the system time is set manually and the device is rebooted, the manual time
The following fields are displayed: Actual Time (Static)System time on the device. This shows the DHCP time zone or the acronym for the user-defined time zone if these were defined. Last Synchronized ServerAddress, stratum and type of the SNTP server from which time was last taken.
Clock Source SettingsSelect the source used to set the system clock. Main Clock Source (SNTP Servers)If you enable this, the system time is obtained from an SNTP server. To use this feature, you must also configure a connection to an SNTP server in the SNTP Interface Settings page. Optionally, enforce authentication of the SNTP sessions by using the SNTP Authentication page. Alternate Clock Source (PC via active HTTP/HTTPS sessions)Select to set the date and time from the configuring computer using the HTTP protocol.
NOTE The Clock Source Setting needs to be set to either of the above in order for RIP MD5 authentication to work. This also helps features that associate with time, for example: Time Based ACL, Port, 802.1 port authentication that are supported on some devices.
75
6
DateEnter the system date. Local TimeEnter the system time.
Manual SettingsSet the date and time manually. The local time is used when there is no alternate source of time, such as an SNTP server:
Time Zone SettingsThe local time is used via the DHCP server or Time Zone offset. Get Time Zone from DHCPSelect to enable dynamic configuration of the time zone and the DST from the DHCP server. Whether one or both of these parameters can be configured depends on the information found in the DHCP packet. If this option is enabled, you must also enable DHCP client on the device.
NOTE The DHCP Client supports Option 100 providing dynamic time zone
setting. Time Zone from DHCPDisplays the acronym of the time zone configured from the DHCP server. This acronym appears in the Actual Time field Time Zone OffsetSelect the difference in hours between Greenwich Mean Time (GMT) and the local time. For example, the Time Zone Offset for Paris is GMT +1, while the Time Zone Offset for New York is GMT 5. Time Zone AcronymEnter a user-defined name that represents the time zone you have configured. This acronym appears in the Actual Time field.
Daylight Savings SettingsSelect how DST is defined: Daylight SavingsSelect to enable Daylight Saving Time. Time Set OffsetEnter the number of minutes offset from GMT ranging from 11440. The default is 60. Daylight Savings TypeClick one of the following: -
USADST is set according to the dates used in the USA. EuropeanDST is set according to the dates used by the European Union and other countries that use this standard. By DatesDST is set manually, typically for a country other than the USA
or a European country. Enter the following parameters:
76
6
FromDay and time that DST starts. ToDay and time that DST ends.
Selecting Recurring allows different customization of the start and stop of DST: FromDate when DST begins each year.
DayDay of the week on which DST begins every year. WeekWeek within the month from which DST begins every year. MonthMonth of the year in which DST begins every year. TimeThe time at which DST begins every year.
ToDate when DST ends each year. For example, DST ends locally every fourth Friday in October at 5:00 am. The parameters are: -
DayDay of the week on which DST ends every year. WeekWeek within the month from which DST ends every year. MonthMonth of the year in which DST ends every year. TimeThe time at which DST ends every year.
STEP 3 Click Apply. The system time values are written to the Running Configuration file.
on the device (see DNS Settings). In order to add a Unicast SNTP server, check the box to enable SNTP Client Unicast . To add a Unicast SNTP server:
STEP 1 Click Administration > Time Settings > SNTP Unicast .
This page contains the following information for each Unicast SNTP server: SNTP ServerSNTP server IP address. The preferred server, or hostname, is chosen according to its stratum level.
77
6
Poll IntervalDisplays whether polling is enabled or disabled. Authentication Key IDKey Identification used to communicate between the SNTP server and device. Stratum LevelDistance from the reference clock expressed as a numerical value. An SNTP server cannot be the primary server (stratum level 1) unless polling interval is enabled. StatusSNTP server status. The possible values are: UpSNTP server is currently operating normally. DownSNTP server is currently not available. UnknownSNTP server is currently being searched for by the device.
In ProcessOccurs when the SNTP server has not fully trusted its own
time server (i.e. when first booting up the SNTP server).
Last ResponseDate and time of the last time a response was received from this SNTP server. OffsetThe estimated offset of the server's clock relative to the local clock, in milliseconds. The host determines the value of this offset using the algorithm described in RFC 2030. DelayThe estimated round-trip delay of the server's clock relative to the local clock over the network path between them, in milliseconds. The host determines the value of this delay using the algorithm described in RFC 2030. SourceHow SNTP server was defined, for example: manually or from DHCPv6 server. InterfaceInterface on which packets are received.
STEP 2 To add a Unicast SNTP server, enable SNTP Client Unicast . STEP 3 Click Add. STEP 4 Enter the following parameters:
Server DefinitionSelect if the SNTP server is going to be identified by its IP address or if you are going to select a well-known SNTP server by name from the list.
NOTE To specify a well-known SNTP server, the device must be connected
to the Internet and configured with a DNS server or configured so that a DNS server is identified by using DHCP. (See DNS Settings)
Cisco Small Business 300 Series Managed Switch Administration Guide 78
IP VersionSelect the version of the IP address: Version 6 or Version 4. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceSelect the link local interface (if IPv6 Address Type Link Local is selected) from the list. SNTP Server IP AddressEnter the SNTP server IP address. The format depends on which address type was selected. SNTP ServerSelect the name of the SNTP server from a list of well-known NTP servers. If other is chosen, enter name of SNTP server in the adjacent field. Poll IntervalSelect to enable polling of the SNTP server for system time information. All NTP servers that are registered for polling are polled, and the clock is selected from the server with the lowest stratum level (distance from the reference clock) that is reachable. The server with the lowest stratum is considered to be the primary server. The server with the next lowest stratum is a secondary server, and so forth. If the primary server is down, the device polls all servers with the polling setting enabled, and selects a new primary server with the lowest stratum. AuthenticationSelect the check box to enable authentication. Authentication Key IDIf authentication is enabled, select the value of the key ID. (Create the authentication keys using the SNTP Authentication page.)
STEP 5 Click Apply. The STNP server is added, and you are returned to the main page.
79
SNTP IPv4 Multicast Client Mode (Client Broadcast Reception)Select to receive system time IPv4 Multicast transmissions from any SNTP server on the subnet. SNTP IPv6 Multicast Client Mode (Client Broadcast Reception)Select to receive system time IPv6 Multicast transmissions from any SNTP server on the subnet. SNTP IPv4 Anycast Client Mode (Client Broadcast Transmission)Select to transmit SNTP IPv4 synchronization packets requesting system time information. The packets are transmitted to all SNTP servers on the subnet. SNTP IPv6 Anycast Client Mode (Client Broadcast Transmission)Select to transmit SNTP IPv6 synchronization packets requesting system time information. The packets are transmitted to all SNTP servers on the subnet.
STEP 3 If the system is in Layer 3 system mode, click Add to enter the interface for SNTP
80
The authentication key is created on the SNTP server in a separate process that depends on the type of SNTP server you are using. Consult with the SNTP server system administrator for more information.
Workflow
STEP 1 Enable authentication in the SNTP Authentication page. STEP 2 Create a key in the SNTP Authentication page. STEP 3 Associate this key with an SNTP server in the SNTP Unicast page.
Authentication Key IDEnter the number used to identify this SNTP authentication key internally. Authentication KeyEnter the key used for authentication (up to eight characters). The SNTP server must send this key for the device to synchronize to it. Trusted KeySelect to enable the device to receive synchronization information only from a SNTP server by using this authentication key.
STEP 6 Click Apply. The SNTP Authentication parameters are written to the Running
Configuration file.
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:
81
ACLs
Cisco Small Business 300 Series Managed Switch Administration Guide
6
8021X Port Authentication 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 recurring element can be added to it. Recurring This type of time range contains a time range element that is added to an absolute range, and begins and ends on a recurring basis. It is defined in the Recurring Range pages.
If a time range includes both absolute and recurring ranges, the process associated with it is activated only if both absolute start time and the recurring time range have been reached. The process is deactivated when either of the time ranges is reached. The device supports a maximum of 10 absolute time ranges. All time specifications are interpreted as local time (Daylight Saving Time does not affect this). 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 Chapter 9, Configuring Ports and Chapter 9, Configuring LAG Settings) Limit PoE operation to a specified period.
82
Time Range NameEnter a new time range name. Absolute Starting TimeTo define the start time, enter the following: ImmediateSelect for the time range to start immediately. Date, TimeEnter the date and time that the Time Range begins.
Absolute Ending TimeTo define the start time, enter the following: InfiniteSelect for the time range to never end. Date, TimeEnter the date and time that the Time Range ends.
The existing recurring time ranges are displayed (filtered per a specific, absolute time range.)
STEP 2 Select the absolute time range to which to add the recurring range. STEP 3 To add a new recurring time range, click Add. STEP 4 Enter the following fields:
Recurring Starting TimeEnter the date and time that the Time Range begins on a recurring basis. Recurring Ending TimeEnter the date and time that the Time Range ends on a recurring basis.
83
7
Administration: Diagnostics
This section contains information for configuring port mirroring, running cable tests, and viewing device operational information. It covers the following topics: Testing Copper Ports Displaying Optical Module Status Configuring Port and VLAN Mirroring Viewing CPU Utilization and Secure Core Technology
84
Administration: Diagnostics
Testing Copper Ports
(Optional) Disable EEE (see the Port Management > Green Ethernet > Properties page)
Use a CAT5 data cable when testing cables using (VCT). Accuracy of the test results can have an error range of +/- 10 for Advanced Testing and +/- 2 for basic testing.
!
CAUTION 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:
STEP 1 Click Administration > Diagnostics > Copper Test . STEP 2 Select the 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: Last UpdateTime of the last test conducted on the port. Test ResultsCable test results. Possible values are: OKCable passed the test. No CableCable is not connected to the port. Open CableCable is connected on only one side. Short CableShort circuit has occurred in the cable. Unknown Test ResultError has occurred.
Distance to FaultDistance from the port to the location on the cable where the fault was discovered. Operational Port StatusDisplays whether port is up or down.
85
Administration: Diagnostics
Displaying Optical Module Status
7
Cable Length: Provides an estimate for the length. PairCable wire pair being tested. StatusWire pair status. Red indicates fault and Green indicates status OK. ChannelCable channel indicating whether the wires are straight or crossover. PolarityIndicates if automatic polarity detection and correction has been activated for the wire pair. Pair SkewDifference in delay between wire pairs.
If the port being tested is a Giga port, the Advanced Information block contains the following information, which is refreshed each time you enter the page:
NOTE TDR tests cannot be performed when the port speed is 10Mbit/Sec.
MSA-compatible SFPs
The following FE SFP (100Mbps) transceivers are supported: MFEBX1: 100BASE-BX-20U SFP transceiver for single-mode fiber, 1310 nm wavelength, supports up to 20 km. MFEFX1: 100BASE-FX SFP transceiver, for multimode fiber, 1310 nm wavelength, supports up to 2 km. MFELX1: 100BASE-LX SFP transceiver, for single-mode fiber, 1310 nm wavelength, supports up to 10 km.
The following GE SFP (1000Mbps) transceivers are supported: MGBBX1: 1000BASE-BX-20U SFP transceiver, for single-mode fiber, 1310 nm wavelength, supports up to 40 km.
86
Administration: Diagnostics
Configuring Port and VLAN Mirroring
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.
To view the results of optical tests, click Administration > Diagnostics > Optical Module Status. This page contains the following fields: PortPort number on which the SFP is connected. TemperatureTemperature (Celsius) at which the SFP is operating. VoltageSFPs operating voltage. CurrentSFPs current consumption. Output PowerTransmitted optical power. Input PowerReceived optical power. Transmitter FaultRemote SFP reports signal loss. Values are True, False, and No Signal (N/S). Loss of SignalLocal SFP reports signal loss. Values are True and False. Data ReadySFP is operational. Values are True and False
87
Administration: Diagnostics
Configuring Port and VLAN Mirroring
A packet that is received on a network port 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. 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. VLAN mirroring is not active on a VLAN that was not manually created. For example, if VLAN 23 was created by GVRP, and you manually created VLAN 34, and you create port mirroring that includes VLAN 23, VLAN 34, or both, and later on delete VLAN 34, the status in port mirroring is set to Not Ready, because the VLAN34 is no longer in the database and VLAN23 was not created manually. Only one instance of mirroring is supported system-wide. The analyzer port (or target port for VLAN mirroring or port mirroring) is the same for all the mirrored VLANs or ports. To enable mirroring:
STEP 1 Click Administration > Diagnostics > Port and VLAN Mirroring.
This page contains the following fields: Destination PortPort to which traffic is to be copied; the analyzer port. Source InterfaceInterface, port, or VLAN from which traffic is sent to the analyzer port. TypeType of monitoring: incoming to the port (Rx), outgoing from the port (Tx), or both. Status Displays one of the following values: ActiveBoth source and destination interfaces are up and forwarding traffic. Not ReadyEither source or destination (or both) are down or not forwarding traffic for some reason.
STEP 2 Click Add to add a port or VLAN to be mirrored. STEP 3 Enter the parameters:
88
Administration: Diagnostics
Viewing CPU Utilization and Secure Core Technology
Destination PortSelect the analyzer port to where packets are copied. A network analyzer, such as a PC running Wireshark, is connected to this port. If a port is identified as an analyzer destination port, it remains the analyzer destination port until all entries are removed. Source InterfaceSelect the source port or source VLAN from where traffic is to be mirrored. TypeSelect whether incoming, outgoing, or both types of traffic are mirrored to the analyzer port. If Port is selected, the options are: Rx OnlyPort mirroring on incoming packets. Tx OnlyPort mirroring on outgoing packets. Tx and RxPort mirroring on both incoming and outgoing packets.
Excessive traffic burdens the CPU, and might prevent normal device operation. The device uses the Secure Core Technology (SCT) feature to ensure that the device receives and processes management and protocol traffic, no matter how much total traffic is received. SCT is enabled by default on the device and cannot be disabled. There are no interactions with other features. To display CPU utilization:
89
Administration: Diagnostics
Viewing CPU Utilization and Secure Core Technology
The CPU Utilization page appears. The CPU Input Rate field displays the rate of input frames to the CPU per second. The window contains a graph of the CPU utilization. The Y axis is percentage of usage, and the X axis is the sample number.
STEP 2 Select the Refresh Rate (time period in seconds) that passes before the statistics
90
Administration: Diagnostics
Viewing CPU Utilization and Secure Core Technology
91
8
Administration: Discovery
This section provides information for configuring Discovery. It covers the following topics: Configuring Bonjour Discovery LLDP and CDP Configuring LLDP Configuring CDP
92
Administration: Discovery
Configuring Bonjour Discovery
When Bonjour Discovery is disabled, the device stops any service type advertisements and does not respond to requests for service from network management applications. To globally enable Bonjour when the system is in Layer 2 system mode:
STEP 1 Click Administration > Discovery - Bonjour. STEP 2 Select Enable to enable Bonjour Discovery globally on the device. STEP 3 Click Apply. Bonjour is enabled or disabled on the device according to the
selection.
93
Administration: Discovery
LLDP and CDP
STEP 3 Click Apply to update the Running Configuration file. STEP 4 To enable Bonjour on an interface, click Add. STEP 5 Select the interface, and click Apply. NOTE Click Delete to disable Bonjour on an interface (this performs the delete operation
94
Administration: Discovery
Configuring LLDP
CDP and LLDP end devices, such as IP phones, learn the voice VLAN configuration from CDP and LLDP advertisements. By default, the device is enabled to send out CDP and LLDP advertisement based on the voice VLAN configured at the device. Refer to the Voice VLAN and Auto Voice VLAN sections for details.
NOTE CDP/LLDP does not distinguish if a port is in a LAG. If there are multiple ports in a
LAG, CDP/LLDP transmit packets on each port without taking into account the fact that the ports are in a LAG. The operation of CDP/LLDP is independent of the STP status of an interface. If 802.1x port access control is enabled at an interface, the device transmits and receives CDP/LLDP packets to and from the interface only if the interface is authenticated and authorized. If a port is the target of mirroring, then according to CDP/LLDP it is considered down.
NOTE CDP and LLDP are link layer protocols for directly-connected CDP/LLDP capable
devices to advertise themselves and their capabilities. In deployments where the CDP/LLDP-capable devices are not directly connected and are separated with CDP/LLDP-incapable devices, the CDP/LLDP-capable devices may be able to receive the advertisement from other device(s) only if the CDP/LLDP-incapable devices flood the CDP/LLDP packets they receives. If the CDP/LLDP-incapable devices perform VLAN-aware flooding, then CDP/LLDP-capable devices can hear each other only if they are in the same VLAN. A CDP/LLDP-capable device may receive advertisement from more than one device if the CDP/LLDP-incapable devices flood the CDP/LLDP packets.
Configuring LLDP
This section describes how to configure LLDP. It covers the following topics: LLDP Overview Setting LLDP Properties Editing LLDP Port Settings LLDP MED Network Policy Configuring LLDP MED Port Settings Displaying LLDP Port Status
95
Administration: Discovery
Configuring LLDP
8
Displaying LLDP Local Information Displaying LLDP Neighbors Information Accessing LLDP Statistics LLDP Overloading
LLDP Overview
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). The network management system models the topology of the network by querying these MIB databases. LLDP is a link layer protocol. By default, the device terminates and processes all incoming LLDP packets as required by the protocol. The LLDP protocol has an extension called LLDP Media Endpoint Discovery (LLDP-MED), which provides and accepts information from media endpoint devices such as VoIP phones and video phones. For further information about LLDP-MED, see LLDP MED Network Policy.
96
Administration: Discovery
Configuring LLDP
4. Associate LLDP MED network policies and the optional LLDP-MED TLVs to the desired interfaces by using the LLDP MED Port Settings page. 5. If Auto Smartport is to detect the capabilities of LLDP devices, enable LLDP in the Smartport Properties page. 6. Display overloading information by using the LLDP Overloading page.
LLDP StatusSelect to enable LLDP on the device (enabled by default). LLDP Frames HandlingIf LLDP is not enabled, select the action to be taken if a packet that matches the selected criteria is received: -
TLV Advertise IntervalEnter the rate in seconds at which LLDP advertisement updates are sent, or use the default. Topology Change SNMP Notification IntervalEnter the minimum time interval between SNMP notifications. Hold MultiplierEnter 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 DelayEnter the time interval in seconds that passes between disabling and reinitializing LLDP, following an LLDP enable/disable cycle. Transmit DelayEnter the amount of time in seconds that passes between successive LLDP frame transmissions due to changes in the LLDP local systems MIB.
97
Administration: Discovery
Configuring LLDP
STEP 3 In the 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.
This page provides the following fields: InterfaceSelect the port to edit. Administrative StatusSelect the LLDP publishing option for the port. The values are: Tx OnlyPublishes but does not discover. Rx OnlyDiscovers but does not publish. Tx & RxPublishes and discovers. DisableIndicates that LLDP is disabled on the port.
SNMP NotificationSelect Enable to send notifications to SNMP notification recipients; for example, an SNMP managing system, when there is a topology change.
98
Administration: Discovery
Configuring LLDP
The time interval between notifications is entered in the Topology Change SNMP Notification Interval field in the LLDP Properties page. Define SNMP Notification Recipients by using the SNMP > Notification Recipient v1,2 and/or SNMP > Notification Recipient v3 page. Available Optional TLVsSelect the information to be published by the device by moving the TLV to the Selected Optional TLVs list. The available TLVs contain the following information: Port DescriptionInformation about the port, including manufacturer, product name and hardware/software version. System NameSystem's assigned name (in alpha-numeric format). The value equals the sysName object. System DescriptionDescription of the network entity (in alphanumeric format). This includes the system's name and versions of the hardware, operating system, and networking software supported by the device. The value equals the sysDescr object. System CapabilitiesPrimary functions of the device, and whether or not these functions are enabled in 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. 802.3 MAC-PHYDuplex and bit rate capability and the current duplex and bit rate settings of the sending device. It also indicates whether the current settings are due to auto-negotiation or manual configuration. 802.3 Link AggregationWhether the link (associated with the port on which the LLDP PDU is transmitted) can be aggregated. It also indicates whether the link is currently aggregated, and if so, provides the aggregated port identifier. 802.3 Maximum FrameMaximum frame size capability of the MAC/ PHY implementation.
The following fields relate to the Management Address: Advertisement ModeSelect one of the following ways to advertise the IP management address of the device: Auto AdvertiseSpecifies that the software would automatically choose a management address to advertise from all the IP addresses of the product. In case of multiple IP addresses the software chooses the
99
Administration: Discovery
Configuring LLDP
8
lowest IP address among the dynamic IP addresses. If there are no dynamic addresses, the software chooses the lowest IP address among the static IP addresses. NoneDo not advertise the management IP address. Manual AdvertiseSelect this option and the management IP address to be advertised. We recommend you select this option when the device is in Layer 3 system mode and the device is configured with multiple IP addresses (this is always true on SG500X/ESW2-550X devices).
IP AddressIf Manual Advertise was selected, select the Management IP address from the addresses provided.
STEP 3 Enter the relevant information, and click Apply. The port settings are written to the
100
8
Setting LLDP MED Network Policy
Administration: Discovery
Configuring LLDP
An 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 page. 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. In addition, an administrator can instruct the device to automatically generate and advertise a network policy for voice application based on the voice VLAN maintained by the device. Refer the Auto Voice VLAN section for details on how the device maintains its voice VLAN. To define an LLDP MED network policy:
STEP 1 Click Administration > Discovery - LLDP > LLDP MED Network Policy.
automatically generate and advertise a network policy for voice application based on the voice VLAN maintained by the device.
NOTE When this box is checked, you may not manually configure a voice
network policy.
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:
101
Network Policy NumberSelect the number of the policy to be created. ApplicationSelect the type of application (type of traffic) for which the network policy is being defined. VLAN IDEnter the VLAN ID to which the traffic must be sent.
Cisco Small Business 300 Series Managed Switch Administration Guide
Administration: Discovery
Configuring LLDP
8
VLAN TagSelect whether the traffic is Tagged or Untagged. User PrioritySelect the traffic priority applied to traffic defined by this network policy. This is the CoS value. DSCP ValueSelect the DSCP value to associate with application data sent by neighbors. This 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.
Page) is Auto and Auto Voice VLAN is in operation, then the device automatically generates an LLDP-MED Network Policy for Voice Application for all the ports that are LLDP-MED enabled and are members of the voice VLAN. To configure LLDP MED on each port:
STEP 1 Click Administration > Discovery - LLDP > LLDP MED Port Settings.
This page contains LLDP MED settings, including enabled TLVs, for all ports.
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 (see LLDP Overview). Click on the link to change the mode.
STEP 3 To associate additional LLDP MED TLV and/or one or more user-defined LLDP
InterfaceSelect the interface to configure. LLDP MED StatusEnable/disable LLDP MED on this port.
102
Administration: Discovery
Configuring LLDP
SNMP NotificationSelect whether SNMP notification is sent on a per-port basis when an end station that supports MED is discovered; for example a SNMP managing system, when there is a topology change. Available Optional TLVsSelect the TLVs that can be published by the device by moving them to the Selected Optional TLVs list. Available Network PoliciesSelect the LLDP MED policies to be published by LLDP by moving them to the Selected Network Policies list. These were created in the LLDP MED Network Policy page. To include one or more userdefined network polices 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-TIA1057_final_for_publication.pdf): Location CoordinateEnter the coordinate location to be published by LLDP. Location Civic AddressEnter the civic address to be published by LLDP. Location (ECS) ELINEnter 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.
Port Status.
STEP 2 Click LLDP Local Information Detail to see the details of the LLDP and LLDP-MED
MED TLVs received from the neighbor. LLDP Port Status Global Information
103
Administration: Discovery
Configuring LLDP
8
Chassis ID SubtypeType of chassis ID (for example, MAC address). Chassis IDIdentifier of chassis. Where the chassis ID subtype is a MAC address, the MAC address of the device appears. System NameName of device. System DescriptionDescription of the device (in alpha-numeric format). Supported System CapabilitiesPrimary functions of the device, such as Bridge, WLAN AP, or Router. Enabled System CapabilitiesPrimary enabled function(s) of the device. Port ID SubtypeType of the port identifier that is shown.
LLDP Port Status Table InterfacePort identifier. LLDP StatusLLDP publishing option. LLDP MED StatusEnabled or disabled. Local PoELocal PoE information advertised. Remote PoEPoE information advertised by the neighbor. # of neighborsNumber of neighbors discovered. Neighbor Capability of 1st DeviceDisplays the primary functions of the neighbor; for example: Bridge or Router.
Click LLDP Local Information Details to see the details of the LLDP and LLDP MED TLVs sent to the neighbor. Click LLDP Neighbor Information Details to see the details of the LLDP and LLDPMED TLVs received from the neighbor.
STEP 3 Select the desired port from the Port list.
104
8
This page provides the following fields:
Administration: Discovery
Configuring LLDP
Global
Chassis ID SubtypeType of chassis ID. (For example, the MAC address.) Chassis IDIdentifier of chassis. Where the chassis ID subtype is a MAC address, the MAC address of the device appears. System NameName of device. System DescriptionDescription of the device (in alpha-numeric format). Supported System CapabilitiesPrimary functions of the device, such as Bridge, WLAN AP, or Router. Enabled System CapabilitiesPrimary enabled function(s) of the device. Port ID SubtypeType of the port identifier that is shown. Port IDIdentifier of port. Port DescriptionInformation about the port, including manufacturer, product name and hardware/software version.
Management Address
Displays the table of addresses of the local LLDP agent. Other remote managers can use this address to obtain information related to the local device. The address consists of the following elements: Address SubtypeType of management IP address that is listed in the Management Address field; for example, IPv4. AddressReturned address most appropriate for management use,typically a Layer 3 address. Interface SubtypeNumbering method used for defining the interface number. Interface NumberSpecific interface associated with this management address.
MAC/PHY Details
Auto-Negotiation SupportedPort speed auto-negotiation support status. Auto-Negotiation EnabledPort speed auto-negotiation active status.
105
Administration: Discovery
Configuring LLDP
8
Auto-Negotiation Advertised CapabilitiesPort speed auto-negotiation capabilities; for example, 1000BASE-T half duplex mode, 100BASE-TX full duplex mode. Operational MAU TypeMedium 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.
802.3 Details
802.3 Maximum Frame SizeThe maximum supported IEEE 802.3 frame size.
MED Details
Capabilities SupportedMED capabilities supported on the port. Current CapabilitiesMED capabilities enabled on the port. Device ClassLLDP-MED endpoint device class. The possible device classes are:
106
8
LLDP services.
Administration: Discovery
Configuring LLDP
Endpoint Class 1Indicates a generic endpoint class, offering basic Endpoint Class 2Indicates a media endpoint class, offering media streaming capabilities, as well as all Class 1 features. Endpoint Class 3Indicates a communications device class, offering all Class 1 and Class 2 features plus location, 911, Layer 2 device support, and device information management capabilities.
PoE Device TypePort PoE type; for example, powered. PoE Power SourcePort power source. PoE Power PriorityPort power priority. PoE Power ValuePort power value. Hardware RevisionHardware version. Firmware RevisionFirmware version. Software RevisionSoftware version. Serial NumberDevice serial number. Manufacturer NameDevice manufacturer name. Model NameDevice model name. Asset IDAsset ID.
Location Information
CivicStreet address. CoordinatesMap coordinates: latitude, longitude, and altitude. ECS ELINEmergency Call Service (ECS) Emergency Location Identification Number (ELIN).
Administration: Discovery
Configuring LLDP
This page contains the following fields: Local PortNumber of the local port to which the neighbor is connected. Chassis ID SubtypeType of chassis ID (for example, MAC address). Chassis IDIdentifier of the 802 LAN neighboring device's chassis. Port ID SubtypeType of the port identifier that is shown. Port IDIdentifier of port. System NamePublished name of the device. Time to LiveTime interval (in seconds) after which the information for this neighbor is deleted.
Port Details
Local PortPort number. MSAP EntryDevice Media Service Access Point (MSAP) entry number.
108
8
Basic Details
Administration: Discovery
Configuring LLDP
Chassis ID SubtypeType of chassis ID (for example, MAC address). Chassis IDIdentifier of the 802 LAN neighboring device chassis. Port ID SubtypeType of the port identifier that is shown. Port IDIdentifier of port. Port DescriptionInformation about the port, including manufacturer, product name and hardware/software version. System NameName of system that is published. System DescriptionDescription 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 CapabilitiesPrimary 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 CapabilitiesPrimary enabled function(s) of the device.
MAC/PHY Details
Auto-Negotiation SupportedPort speed auto-negotiation support status. The possible values are True and False. Auto-Negotiation EnabledPort speed auto-negotiation active status. The possible values are True and False. Auto-Negotiation Advertised CapabilitiesPort speed auto-negotiation capabilities, for example, 1000BASE-T half duplex mode, 100BASE-TX full duplex mode.
109
Administration: Discovery
Configuring LLDP
8
Operational MAU TypeMedium 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.
802.3 Details
802.3 Maximum Frame SizeAdvertised maximum frame size that is supported on the port.
110
8
MED Details
Administration: Discovery
Configuring LLDP
Capabilities SupportedMED capabilities enabled on the port. Current CapabilitiesMED TLVs advertised by the port. Device ClassLLDP-MED endpoint device class. The possible device classes are: Endpoint Class 1Indicates a generic endpoint class, offering basic LLDP services. Endpoint Class 2Indicates a media endpoint class, offering media streaming capabilities as well as all Class 1 features. Endpoint Class 3Indicates 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 TypePort PoE type, for example, powered. PoE Power SourcePorts power source. PoE Power PriorityPorts power priority. PoE Power ValuePorts power value. Hardware Revision Hardware version. Firmware RevisionFirmware version. Software RevisionSoftware version. Serial NumberDevice serial number. Manufacturer NameDevice manufacturer name. Model NameDevice model name. Asset IDAsset ID.
PPVID Table
VIDProtocol VLAN ID. SupportedSupported Port and Protocol VLAN IDs.
111
Administration: Discovery
Configuring LLDP
8
EnabledEnabled Port and Protocol VLAN IDs.
VLAN IDs
VIDPort and Protocol VLAN ID. VLAN NamesAdvertised VLAN names.
Protocol IDs
Protocol ID TableAdvertised protocol IDs.
Location Information
Enter the following data structures in hexadecimal as described in section 10.2.4 of the ANSI-TIA-1057 standard: CivicCivic or street address. CoordinatesLocation map coordinateslatitude, longitude, and altitude. ECS ELINDevices Emergency Call Service (ECS) Emergency Location Identification Number (ELIN). UnknownUnknown location information.
Network Policies
Application TypeNetwork policy application type, for example, Voice. VLAN IDVLAN ID for which the network policy is defined. VLAN TypeVLAN type, Tagged or Untagged, for which the network policy is defined. User PriorityNetwork policy user priority. DSCPNetwork policy DSCP.
112
8
For each port, the fields are displayed: InterfaceIdentifier of interface.
Administration: Discovery
Configuring LLDP
TotalNumber of received frames. DiscardedTotal number of received frames that were discarded. ErrorsTotal number of received frames with errors.
Rx TLVs -
DiscardedTotal number of received TLVs that were discarded. UnrecognizedTotal number of received TLVs that were unrecognized.
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 a LLDP packet exceed 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 for additional LLDP information, and the overloading status of every interface. To view LLDP overloading information:
STEP 1 Click Administration > Discovery - LLDP > LLDP Overloading.
This page contains the following fields for each port: InterfacePort identifier. Total (Bytes)Total number of bytes of LLDP information in each packet
113
Administration: Discovery
Configuring LLDP
8
Left to Send (Bytes)Total number of available bytes left for additional LLDP information in each packet. StatusWhether 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. StatusIf 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. StatusIf the LLDP MED capabilities packets were sent, or if they were overloaded.
Size (Bytes)Total LLDP MED location packets byte size. StatusIf the LLDP MED locations packets were sent, or if they were overloaded.
Size (Bytes)Total LLDP MED network policies packets byte size. StatusIf the LLDP MED network policies packets were sent, or if they were overloaded.
Size (Bytes)Total LLDP MED extended power via MDI packets byte
size.
StatusIf the LLDP MED extended power via MDI packets were sent, or if they were overloaded.
802.3 TLVs -
Size (Bytes)Total LLDP MED 802.3 TLVs packets byte size. StatusIf the LLDP MED 802.3 TLVs packets were sent, or if they were overloaded.
114
8
LLDP Optional TLVs
Administration: Discovery
Configuring CDP
Size (Bytes)Total LLDP MED optional TLVs packets byte size. StatusIf the LLDP MED optional TLVs packets were sent, or if they were overloaded.
Size (Bytes)Total LLDP MED inventory TLVs packets byte size. StatusIf the LLDP MED inventory packets were sent, or if they were overloaded.
Total (Bytes)Total number of bytes of LLDP information in each packet Left to Send (Bytes)Total number of available bytes left for additional LLDP information in each packet.
Configuring CDP
This section describes how to configure CDP. It covers the following topics: Setting CDP Properties Editing CDP Interface Settings Displaying CDP Local Information Displaying CDP Neighbors Information Viewing CDP Statistics
115
Administration: Discovery
Configuring CDP
Smartport Properties page. See Identifying Smartport Type for a description of how CDP is used to identify devices for the Smartport feature. To enter CDP general parameters:
STEP 1 Click Administration > Discovery - CDP > Properties. STEP 2 Enter the parameters.
CDP StatusSelect to enable CDP on the device. CDP Frames HandlingIf CDP is not enabled, select the action to be taken if a packet that matches the selected criteria is received: -
BridgingForward the packet based on the VLAN. FilteringDelete the packet. FloodingVLAN unaware flooding that forwards incoming CDP packets
to all the ports excluding the ingress ports.
CDP Voice VLAN AdvertisementSelect 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. The voice VLAN is configured in the Voice VLAN Properties page. CDP Mandatory TLVs ValidationIf selected, incoming CDP packets not containing the mandatory TLVs are discarded and the invalid error counter is incremented. CDP VersionSelect the version of CDP to use.
116
Administration: Discovery
Configuring CDP
CDP Hold TimeAmount 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 LLDP packets are discarded after 120 seconds. The following options are possible: Use DefaultUse the default time (180 seconds) User DefinedEnter the time in seconds.
CDP Transmission RateThe rate in seconds at which CDP advertisement updates are sent. The following options are possible: Use DefaultUse the default rate (60 seconds) User DefinedEnter the rate in seconds.
Device ID FormatSelect the format of the device ID (MAC address or serial number). Source InterfaceIP address to be used in the TLV of the frames. The following options are possible: Use DefaultUse the IP address of the outgoing interface. User DefinedUse the IP address of the interface (in the Interface field) in the address TLV.
InterfaceIF User Defined was selected for Source Interface, select the interface. Syslog Voice VLAN MismatchCheck 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. Syslog Native VLAN MismatchCheck 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. Syslog Duplex MismatchCheck 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.
117
Administration: Discovery
Configuring CDP
This page contains the following CDP information for each interface. CDP StatusCDP publishing option for the port. Reporting Conflicts with CDP NeighborsDisplays the status of the reporting options that are enabled/disabled in the Edit page (Voice VLAN/ Native VLAN/Duplex). No. of NeighborsNumber of neighbors detected.
The bottom of the page has four buttons: Copy SettingsSelect to copy a configuration from one port to another. EditFields explained in Step 2 below. CDP Local Information DetailsTakes you to the Administration > Discovery - CDP > CDP Local Information page. CDP Neighbor Information DetailsTakes you to the Administration > Discovery - CDP > CDP Neighbor Information page.
This page provides the following fields: InterfaceSelect the interface to be defined. CDP StatusSelect to enable/disable the CDP publishing option for the port.
NOTE The next three fields are operational when the device has been set up
118
Administration: Discovery
Configuring CDP
Syslog Voice VLAN MismatchSelect to enable the option of sending 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. Syslog Native VLAN MismatchSelect to enable the option of sending 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. Syslog Duplex MismatchSelect to enable the option of sending a SYSLOG message when duplex information mismatch is detected. This means that the duplex information in the incoming frame does not 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.
InterfaceNumber of the local port. CDP StateDisplays whether CDP is enabled or not. Device ID TLV Device ID TypeType of the device ID advertised in the device ID TLV. Device IDDevice ID advertised in the device ID TLV.
Port TLV
119
Administration: Discovery
Configuring CDP
8
Port IDIdentifier of port advertised in the port TLV. Capabilities TLV CapabilitiesCapabilities advertised in the port TLV)
Version TLV VersionInformation about the software release on which the device is running.
Native VLAN TLV Native VLANThe native VLAN identifier advertised in the native VLAN TLV.
Full/Half Duplex TLV DuplexWhether port is half or full duplex advertised in the full/half duplex TLV.
Appliance TLV Appliance IDType of device attached to port advertised in the appliance TLV. Appliance VLAN IDVLAN on the device used by the appliance, for instance if the appliance is an IP phone, this is the voice VLAN.
Extended Trust TLV Extended TrustEnabled indicates that the port is trusted, meaning that the host/server from which the packet is received is trusted to mark the packets itself. In this case, packets received on such a port are not remarked. Disabled indicates that the port is not trusted in which case, the following field is relevant.
CoS for Untrusted Ports TLV CoS for Untrusted PortsIf Extended Trust is disabled on the port, this fields 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.
Power TLV
120
8
-
Administration: Discovery
Configuring CDP
Request IDLast power request ID received echoes the Request-ID field last received in a Power Requested TLV. It is 0 if no Power Requested TLV was received since the interface last transitioned to Up. Power Management IDValue incremented by 1 (or 2, to avoid 0) each time any one of the following events occur: Available-Power or Management Power Level fields change value A Power Requested TLV is received with a Request-ID field which is different from the last-received set (or when the first value is received) The interface transitions to Down
Available PowerAmount of power consumed by port. Management Power LevelDisplays the supplier's request to the powered device for its Power Consumption TLV. The device always displays No Preference in this field.
This page contains the following fields for the link partner (neighbor): Device IDNeighbors device ID. System nameNeighbors system name. Local InterfaceNumber of the local port to which the neighbor is connected. Advertisement VersionCDP protocol version. Time to Live (sec)Time interval (in seconds) after which the information for this neighbor is deleted.
121
Administration: Discovery
Configuring CDP
8
CapabilitiesCapabilities advertised by neighbor. PlatformInformation from Platform TLV of neighbor. Neighbor InterfaceOutgoing interface of the neighbor.
This page contains the following fields about the neighbor: Device IDIdentifier of the neighboring device ID. Local InterfaceInterface number of port through which frame arrived. Advertisement VersionVersion of CDP. Time to LiveTime interval (in seconds) after which the information for this neighbor is deleted. CapabilitiesPrimary 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. PlatformIdentifier of the neighbors platform. Neighbor InterfaceInterface number of the neighbor through which frame arrived. Native VLANNeighbors native VLAN. DuplexWhether neighbors interface is half or full duplex. AddressesNeighbors addresses. Power DrawnAmount of power consumed by neighbor on the interface. VersionNeighbors software version.
NOTE Clicking on the Clear Table button disconnect all connected devices if from CDP,
122
8
Viewing CDP Statistics
Administration: Discovery
Configuring CDP
The CDP Statistics page displays information regarding Cisco Discovery Protocol (CDP) frames that were sent or received from a port. CDP packets are received from devices attached to the switches interfaces, and are used for the Smartport feature. See Configuring CDP for more information. CDP statistics for a port are only displayed if CDP is enabled globally and on the port. This is done in the CDP Properties page and the CDP Interface Settings page. To view CDP statistics:
STEP 1 Click Administration > Discovery - CDP > CDP Statistics.
The following fields are displayed for every interface:. Packets Received/Transmitted: Version 1Number of CDP version 1 packets received/transmitted. Version 2Number of CDP version 2 packets received/transmitted. TotalTotal number of CDP packets received/transmitted.
The CDP Error Statistics section displays the CDP error counters. Illegal ChecksumNumber of packets received with illegal checksum value. Other ErrorsNumber of packets received with errors other than illegal checksums. Neighbors Over MaximumNumber of times that packet information could not be stored in cache because of lack of room.
To clear all counters on all interfaces, click Clear All Interface Counters. To clear all counters on an interface, select it and click Clear All Interface Counters.
123
9
Port Management
This section describes port configuration, link aggregation, and the Green Ethernet feature. It covers the following topics: Configuring Ports Setting Port Configuration Configuring Link Aggregation Configuring Green Ethernet
Configuring Ports
To configure ports, perform the following actions: 1. Configure port by using the Port Settings page. 2. Enable/disable the Link Aggregation Control (LAG) protocol, and configure the potential member ports to the desired LAGs by using the LAG Management page. By default, all LAGs are empty. 3. Configure the Ethernet parameters, such as speed and auto-negotiation for the LAGs by using the LAG Settings page. 4. Configure the LACP parameters for the ports that are members or candidates of a dynamic LAG by using the LACP page. 5. Configure Green Ethernet and 802.3 Energy Efficient Ethernet by using the Properties page. 6. Configure Green Ethernet energy mode and 802.3 Energy Efficient Ethernet per port by using the Port Settings page. 7. If PoE is supported and enabled for the device, configure the device as described in Port Management: PoE.
124
9
Setting Port Configuration
Port Management
Setting Port Configuration
The Port Settings page displays the global and per port setting of all the ports. This page enables you to select and configure the desired ports from the Edit Port Settings page. To configure port settings:
STEP 1 Click Port Management > Port Settings. STEP 2 Select Jumbo Frames to support packets of up to 10 Kb in size. If Jumbo Frames
is not enabled (default), the system supports packet size up to 2,000 bytes. For jumbo frames to take effect, the device must be rebooted after the feature is enabled.
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 Copy/ Save Configuration page, 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:
InterfaceSelect the port number. Port TypeDisplays the port type and speed. The possible options are: Copper PortsRegular, not Combo, support the following values: 10M, 100M, and 1000M (type: Copper). Combo Ports CopperCombo port connected with copper CAT5 cable, supports the following values: 10M, 100M, and 1000M (type: ComboC). Combo FiberSFP Fiber Gigabit Interface Converter Port with the following values: 100M and 1000M (type: ComboF). 10G-Fiber OpticsPorts with speed of either 1G or 10G.
NOTE SFP Fiber takes precedence in Combo ports when both ports are
being used. Port DescriptionEnter the port user-defined name or comment. Administrative StatusSelect whether the port must be Up or Down when the device is rebooted.
125
Port Management
Setting Port Configuration
9
Operational StatusDisplays whether the port is currently Up or Down. If the port is down because of an error, the description of the error is displayed. Time RangeSelect 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. If a time range is not yet defined, click Edit to go to the Time Range page. Time Range NameSelect the profile that specifies the time range. Operational Time-Range StateDisplays whether the time range is currently active or inactive. Reactivate Suspended PortSelect to reactivate a port that has been suspended. There are numerous ways that a port can be suspended, such as through the locked port security option, dot1x single host violation, loopback detection, STP loopback guard or Access Control List (ACL) configurations. The reactivate operation brings the port up without regard to why the port was suspended. Auto-NegotiationSelect to enable auto-negotiation on the port. Autonegotiation enables a port to advertise its transmission speed, duplex mode, and Flow Control abilities to the port link partner. Operational Auto-NegotiationDisplays the current auto-negotiation status on the port. Administrative Port SpeedConfigure the speed of the port. The port type determines which the available speeds. You can designate Administrative Speed only when port auto-negotiation is disabled. Operational Port SpeedDisplays the current port speed that is the result of negotiation. Administrative Duplex ModeSelect 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, the mode is always full duplex. The possible options are: FullThe interface supports transmission between the device and the client in both directions simultaneously. HalfThe interface supports transmission between the device and the client in only one direction at a time.
126
Port Management
Setting Port Configuration
Auto AdvertisementSelect the capabilities advertised by autonegotiation when it is enabled. The options are: Max CapabilityAll port speeds and duplex mode settings can be accepted. 10 Half10 Mbps speed and Half Duplex mode. 10 Full10 Mbps speed and Full Duplex mode. 100 Half100 Mbps speed and Half Duplex mode. 100 Full100 Mbps speed and Full Duplex mode. 1000 Full1000 Mbps speed and Full Duplex mode.
Operational AdvertisementDisplays the capabilities currently published to the ports neighbor. The possible options are those specified in the Administrative Advertisement field. Neighbor AdvertisementDisplays the capabilities advertised by the neighboring device (link partner). Back PressureSelect the Back Pressure mode on the port (used with Half Duplex mode) to slow down the packet reception speed when the device is congested. It disables the remote port, preventing it from sending packets by jamming the signal. Flow ControlEnable or disable 802.3x Flow Control, or enable the autonegotiation of Flow Control on the port (only when in Full Duplex mode). MDI/MDIXthe Media Dependent Interface (MDI)/Media Dependent Interface with Crossover (MDIX) status on the port. The options are: MDIXSelect to swap the port's transmit and receives pairs. MDISelect to connect this device to a station by using a straight through cable. AutoSelect to configure this device to automatically detect the correct pinouts for the connection to another device.
Operational MDI/MDIXDisplays the current MDI/MDIX setting. Protected PortSelect 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:
127
Port Management
Configuring Link Aggregation
9
Protected Ports provide Layer 2 isolation between interfaces (Ethernet ports and LAGs) that share the same 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. Protected LAGs are described in the Configuring LAG Settings section.
Member in LAGIf the port is a member of a LAG, the LAG number appears; otherwise this field is left blank.
STEP 6 Click Apply. The Port Settings are written to the Running Configuration file.
128
9
Link Aggregation Overview
Port Management
Configuring Link Aggregation
Link Aggregation Control Protocol (LACP) is part of the IEEE specification (802.3az) that enables you to bundle several physical ports together to form a single logical channel (LAG). LAGs multiply the bandwidth, increase port flexibility, and provide link redundancy between two devices. Two types of LAGs are supported: StaticA LAG is static if the LACP is disabled on it. The group of ports assigned to a static LAG are always active members. After a LAG is manually created, the LACP option cannot be added or removed, until the LAG is edited and a member is removed (which can be added prior to applying), then the LACP button become available for editing. DynamicA 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 non-active candidate ports are standby ports ready to replace any failing active member ports.
Load Balancing
Traffic forwarded to a LAG is load-balanced across the active member ports, thus achieving an effective bandwidth close to the aggregate bandwidth of all the active member ports of the LAG. Traffic load balancing over the active member ports of a LAG is managed by a hash-based distribution function that distributes Unicast and Multicast traffic based on Layer 2 or Layer 3 packet header information. The device supports two modes of load balancing: By MAC AddressesBased on the destination and source MAC addresses of all packets. By IP and MAC AddressesBased on the destination and source IP addresses for IP packets, and destination and source MAC addresses for non-IP packets.
LAG Management
In general, a LAG is treated by the system as a single logical port. In particular, the LAG has port attributes similar to a regular port, such as state and speed. The device supports 32 LAGs with up to 8 ports in a LAG group.
129
Port Management
Configuring Link Aggregation
9
All ports in a LAG must be of the same media type. To add a port to the LAG, it cannot belong to any VLAN except the default VLAN. Ports in a LAG must not be assigned to another LAG. No more than eight ports are assigned to a static LAG and no more than 16 ports can be candidates for a dynamic LAG. All the ports in a LAG must have auto-negotiation disabled, although the LAG can have auto-negotiation enabled. When a port is added to a LAG, the configuration of the LAG is applied to the port. When the port is removed from the LAG, its original configuration is reapplied. Protocols, such as Spanning Tree, consider all the ports in the LAG to be one port.
130
Port Management
Configuring Link Aggregation
To configure a dynamic LAG, perform the following actions: 1. Enable LACP on the LAG. Assign up to 16 candidates ports to the dynamic LAG by selecting and moving the ports from the Port List to the LAG Members List by using the LAG Management page. 2. Configure various aspects of the LAG, such as speed and flow control by using the LAG Settings page. 3. Set the LACP priority and timeout of the ports in the LAG by using the LACP page.
MAC AddressPerform load balancing by source and destination MAC addresses on all packets. IP/MAC AddressPerform load balancing by the source and destination IP addresses on IP packets, and by the source and destination MAC addresses on non-IP packets
STEP 3 Click Apply. The Load Balance Algorithm is saved to the Running Configuration file.
LAGSelect the LAG number. LAG NameEnter the LAG name or a comment. LACPSelect 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.
131
Port Management
Configuring Link Aggregation
9
Port ListMove those ports that are to be assigned to the LAG from the Port List to the LAG Members list. Up to eight ports per static LAG can be assigned, and 16 ports can be assigned to a dynamic LAG.
STEP 3 Click Apply. LAG membership is saved to the Running Configuration file.
LAGSelect the LAG ID number. DescriptionEnter the LAG name or a comment. LAG TypeDisplays the port type that comprises the LAG. Administrative StatusSet the selected LAG to be Up or Down. Operational StatusDisplays whether the LAG is currently operating. Time RangeSelect 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. If a time range is not yet defined, click Edit to go to the Time Range page. Time Range NameSelect the profile that specifies the time range. Operational Time-Range StateDisplays whether the time range is currently active or inactive. Reactivate Suspended LAGSelect to reactivate a port if the LAG has been disabled through the locked port security option or through ACL configurations.
132
Port Management
Configuring Link Aggregation
Administrative Auto NegotiationEnables 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. Operational Auto NegotiationDisplays the auto-negotiation setting. Administrative SpeedSelect the LAG speed. Operational LAG SpeedDisplays the current speed at which the LAG is operating. Administrative AdvertisementSelect the capabilities to be advertised by the LAG. The options are: Max CapabilityAll LAG speeds and both duplex modes are available. 10 FullThe LAG advertises a 10 Mbps speed and the mode is full duplex. 100 FullThe LAG advertises a 100 Mbps speed and the mode is full duplex. 1000 FullThe LAG advertises a 1000 Mbps speed and the mode is full duplex.
Operational AdvertisementDisplays 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. Administrative Flow ControlSet Flow Control to either Enable or Disable or enable the Auto-Negotiation of Flow Control on the LAG. Operational Flow ControlDisplays the current Flow Control setting. Protected LAGSelect to make the LAG a protected port for Layer 2 isolation. See the Port Configuration description in Setting Basic Port Configuration for details regarding protected ports and LAGs.
133
Port Management
Configuring Link Aggregation
Configuring LACP
A dynamic LAG is LACP-enabled, and LACP is run on every candidate port defined in the LAG.
134
Port Management
Configuring Link Aggregation
However, there are cases when one link partner is temporarily not configured for LACP. One example for such case is when the link partner is on a device, which is in the process of receiving its configuration using the auto-config protocol. This device's ports are not yet configured to LACP. If the LAG link cannot come up, the device cannot ever become configured. A similar case occurs with dual-NIC network-boot computers (e.g. PXE), which receive their LAG configuration only after they bootup. When several LACP-configured ports are configured, and the link comes up in one or more ports but there are no LACP responses from the link partner for those ports, the first port that had link up is added to the LACP LAG and becomes active (the other ports become non-candidates). In this way, the neighbor device can, for example, get its IP Address using DHCP and get its configuration using autoconfiguration.
PortSelect the port number to which timeout and priority values are assigned. LACP Port PriorityEnter the LACP priority value for the port. See Setting LACP Parameter Settings. LACP TimeoutTime 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.
135
Port Management
Configuring Green Ethernet
136
Port Management
Configuring Green Ethernet
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. See 802.3az Energy Efficient Ethernet Feature for more information (available on GE models only). EEE is enabled globally by default. On a given port, if EEE is enabled, short reach mode be disabled. If Short Reach Mode is enabled, EEE be grayed out. These modes are configured per port, without taking into account the LAG membership of the ports. The device LEDs are power consumers. Since most of the time the devices are in an unoccupied room, having these LEDs lit is a waste of energy. The Green Ethernet feature enables you to disable the port LEDs (for link, speed, and PoE) when they are not required, and to enable the LEDs if they are needed (debugging, connecting additional devices etc.). On the System Summary page, the LEDs that are displayed on the device board pictures are not affected by disabling the LEDs. 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.
137
Port Management
Configuring Green Ethernet
9
802.3az Energy Efficient Ethernet Feature
This section describes the 802.3az Energy Efficient Ethernet (EEE) feature. It covers the following topics: 802.3az EEE Overview Advertise Capabilities Negotiation Link Level Discovery for 802.3az EEE Availability of 802.3az EEE Default Configuration Interactions Between Features 802.3az EEE Configuration Workflow
138
9
Advertise Capabilities Negotiation
Port Management
Configuring Green Ethernet
802.3az EEE support is advertised during the Auto-Negotiation stage. AutoNegotiation provides a linked device with the capability to detect the abilities (modes of operation) supported by the device at the other end of the link, determine common abilities, and configure itself for joint operation. AutoNegotiation is performed at the time of link-up, on command from management, or upon detection of a link error. During the link establishment process, both link partners to exchange their 802.3az EEE capabilities. Auto-Negotiation functions automatically without user interaction when it is enabled on the device.
NOTE If Auto-Negotiation is not enabled on a port, the EEE is disabled. The
only exception is if the link speed is 1GB, then EEE still e enabled even though Auto-Negotiation is disabled.
Default Configuration
By default, 802.3az EEE and EEE LLDP are enabled globally and per port.
139
Port Management
Configuring Green Ethernet
9
802.3az EEE Configuration Workflow
This section describes how to configure the 802.3az EEE feature and view its counters.
STEP 1 Ensure that auto-negotiation is enabled on the port by opening the Port
Management > Port Settings page. a. Select a port and open the Edit Port Setting page. b. Select Auto Negotiation field to ensure that it is Enabled.
STEP 2 Ensure that 802.3 Energy Efficient Ethernet (EEE) is globally enabled in the Port
Management > Green Ethernet > Properties page (it is enabled by default). This page also displays how much energy has been saved.
STEP 3 Ensure that 802.3az EEE is enabled on a port by opening the Green Ethernet > Port
Settings page. a. Select a port, open the Edit Port Setting page. b. Check the 802.3 Energy Efficient Ethernet (EEE) mode on the port (it is enabled by default). c. Select whether to enable or disable advertisement of 802.3az EEE capabilities through LLDP in 802.3 Energy Efficient Ethernet (EEE) LLDP (it is enabled by default).
STEP 4 To see 802.3 EEE-related information on the local device, open the
Administration > Discovery LLDP >LLDP Local Information page, and view the information in the 802.3 Energy Efficient Ethernet (EEE) block.
STEP 5 To display 802.3az EEE information on the remote device, open the Administration
> Discovery LLDP > LLDP Neighbor Information pages, and view the information in the 802.3 Energy Efficient Ethernet (EEE) block.
140
Port Management
Configuring Green Ethernet
Energy Detect ModeDisabled by default. Click the checkbox to enable. Short ReachGlobally enable or disable Short Reach mode if there are GE ports on the device.
NOTE If Short Reach is enabled, EEE must be disabled.
Power SavingsDisplays the percentage of power saved by running Green Ethernet and Short Reach. The power savings displayed is only relevant to the power saved by Short Reach and Energy Detect modes. The EEE power savings is dynamic by nature since it is based on port utilization and is therefore not taken into consideration. The power saving calculation is performed by comparing the maximum power consumption without power savings to the current consumption. Cumulative Energy SavedDisplays the amount of energy saved from the last device reboot. This value is updated each time there is an event that affects power saving. 802.3 Energy Efficient Ethernet (EEE) Globally enable or disable EEE mode. Port LEDsSelect to enable the port LEDs. When these are disabled, they do not display link status, activity, etc.
STEP 3 Click Apply. The Green Ethernet Properties are written to the Running
Configuration file.
141
Port Management
Configuring Green Ethernet
9
To define per port Green Ethernet settings:
STEP 1 Click Port Management > Green Ethernet > Port Settings.
The Port Settings page displays the following: Global Parameter StatusDescribes the enabled features.
For each port the following fields are described: PortThe port number. Energy DetectState of the port regarding Energy Detect mode: AdministrativeDisplays whether Energy Detect mode was enabled. OperationalDisplays whether Energy Detect mode is currently operating. ReasonIf Energy Detect mode is not operational, displays the reason.
Short ReachState of the port regarding Short Reach mode: AdministrativeDisplays whether Short Reach mode was enabled. OperationalDisplays whether Short Reach mode is currently operating. ReasonIf Short-Reach mode is not operational, displays the reason. Cable LengthDisplays VCT-returned cable length in meters.
apply to Combo ports. 802.3 Energy Efficient Ethernet (EEE)State of the port regarding the EEE feature: AdministrativeDisplays whether EEE was enabled. OperationalDisplays whether EEE is currently operating on the local port. This is a function of whether it has been enabled (Administrative Status), whether it has been enabled on the local port and whether it is operational on the local port. LLDP AdministrativeDisplays whether advertising EEE counters through LLDP was enabled. LLDP OperationalDisplays whether advertising EEE counters through LLDP is currently operating.
142
9
-
Port Management
Configuring Green Ethernet
EEE Support on RemoteDisplays whether EEE is supported on the link partner. EEE must be supported on both the local and remote link partners.
NOTE The window displays the Short Reach, Energy Detect and EEE
settings for each port; however, they are not enabled on any port unless they are also enabled globally by using the Properties page. To enable Short Reach and EEE globally, see Setting Global Green Ethernet Properties.
STEP 2 Select a Port and click Edit. STEP 3 Select to enable or disable Energy Detect mode on the port. STEP 4 Select to enable or disable Short Reach mode on the port if there are GE ports on
the device.
STEP 5 Select to enable or disable 802.3 Energy Efficient Ethernet (EEE) mode on the port
the port (advertisement of EEE capabilities through LLDP) if there are GE ports on the device.
STEP 7 Click Apply. The Green Ethernet port settings are written to the Running
Configuration file.
143
10
Smartport
This document describes the Smartports feature. It contains the following topics: Overview What is a Smartport Smartport Types Smartport Macros Macro Failure and the Reset Operation How the Smartport Feature Works Auto Smartport Error Handling Default Configuration Relationships with Other Features and Backwards Compatibility Common Smartport Tasks Configuring Smartport Using The Web-based Interface Built-in Smartport Macros
144
10
Overview
Smartport
Overview
The Smartport feature provides a convenient way to save and share common configurations. By applying the same Smartport macro to multiple interfaces, the interfaces share a common set of configurations. A Smartport macro is a script of CLI (Command Line Interface) commands A Smartport macro can be applied to an interface by the macro name, or by the Smartport type associated with the macro. Applying a Smartport macro by macro name can be done only through CLI. Refer to the CLI guide for details. There are two ways to apply a Smartport macro by Smartport type to an interface: Static SmartportYou manually assign a Smartport type to an interface. The result is the corresponding Smartport macro is applied to the interface. Auto SmartportAuto Smartport waits for a device to be attached to the interface before applying a configuration. When a device is detected from an interface, the Smartport macro (if assigned) that corresponds to the Smartport type of the attaching device is automatically applied.
The Smartport feature consists of various components and works in conjunction with other features on the device. These components and features are described in the following sections: Smartport, Smartport types and Smartport macros, described in this section. Voice VLAN and Smartport, described in the Voice VLAN section. LLDP/CDP for Smartport, described in the Configuring LLDP and Configuring CDP sections, respectively.
Additionally, typical work flows are described in the Common Smartport Tasks section.
145
Smartport
What is a Smartport
10
A Smartport is an interface to which a built-in (or user-defined) macro may be applied. These macros are designed to provide a means of quickly configuring the device to support the communication requirements and utilize the features of various types of network devices. The network access and QoS requirements vary if the interface is connected to an IP phone, a printer, or a router and/or Access Point (AP).
What is a Smartport
Smartport Types
Smartport types refers to the types of devices attached, or to be attached to Smartports. The device supports the following Smartport types: Printer Desktop Guest Server Host IP Camera IP phone IP Phone+Desktop Switch Router Wireless Access Point
Smartport types are named so that they describe the type of device connected to an interface. Each Smartport type is associated with two Smartport macros. One macro, called "the macro" serves to apply the desired configuration. The other, called "the anti-macro," serves to undo all configuration performed by "the macro" when that interface happens to become a different Smartport type. You can apply a Smartport macro by the following methods: The associated Smartport type.
146
10
Smartport
Smartport Types
A Smartport macro can be applied by its Smartport type statically from CLI and GUI, and dynamically by Auto Smartport. Auto Smartport derives the Smartport types of the attached devices based on CDP capabilities, LLDP system capabilities, and/or LLDP-MED capabilities. The following describes the relationship of Smartport types and Auto Smartport Smartport and Auto Smartport Types Smartport Type Unknown Default Printer Desktop Guest Server Host IP camera IP phone IP phone desktop Switch Router Wireless Access Point Supported by Auto Smartport No No No No No No Yes No Yes Yes Yes Yes Yes Supported by Auto Smartport by default No No No No No No No No Yes Yes Yes No Yes
147
Smartport
Smartport Types
10
Special Smartport Types
There are two special Smartport types; default and unknown. These two types are not associated with macros, but they exist to signify the state of the interface regarding Smartport. The following describe these special Smartport types: Default An interface that does not (yet) have a Smartport type assigned to it has the Default Smartport status. If Auto Smartport assigns a Smartport type to an interface and the interface is not configured to be Auto Smartport Persistent, then its Smartport type is re-initialized to Default in the following cases: A link down/up operation is performed on the interface. The device is restarted. All devices attached to the interface have aged out, which is defined as the absence of CDP and/or LLDP advertisement from the device for a specified time period.
Unknown If a Smartport macro is applied to an interface and an error occurs, the interface is assigned the Unknown status. In this case, the Smartport and Auto Smartport features do not function on the interface until you correct the error and applies the Reset action (performed in the Interface Settings pages) that resets the Smartport status. See the workflow area in Common Smartport Tasks section for troubleshooting tips.
NOTE Throughout this section, the term aged out is used to describe the LLDP and CDP
messages via their TTL. If Auto Smartport is enabled, and persistent status is disabled, and no more CDP or LLDP messages are received on the interface before both TTLs of the most recent CDP and LLDP packets decrease to 0, then the antimacro is run, and the Smartport type returns to default.
148
10
Smartport Macros
Smartport
Smartport Macros
A Smartport macro is a script of CLI commands that configure an interface appropriately for a particular network device. Smartport macros should not be confused with global macros. Global macros configure the device globally, however, the scope of a Smartport macro is limited to the interface on which it is applied. The macro source may be found by running the show parser macro name [macro_name] command in privileged exec mode of the CLI or by clicking the View Macro Source button on the Smartport Type Settings page. A macro and the corresponding anti-macro are paired together in association with each Smartport type. The macro applies the configuration and the anti-macro removes it. There are two types of Smartport macros: Built-InThese are macros provided by the system. One macro applies the configuration profile and the other removes it. The macro names of the builtin Smartport macros and the Smartport type they are associated with as follows macro-name (for example: printer) no_macro-name (for example: no_printer)
User-DefinedThese are macros written by the users. See the CLI Reference Guide for more information about these. To associate a user defined macro to a Smartport type, its anti macro must be defined as well. smartport-type-name (for example: my_printer) no_smartport-type-name (for example: no_my_printer)
Smartport macros are bound to Smartport types in the Edit Smartport Type Setting page. See Built-in Smartport Macros for a listing of the built-in Smartport macros for each device type.
149
Smartport
Macro Failure and the Reset Operation
10
When a Smartport macro fails on an interface, the status of the interface is set to Unknown. The reason for the failure can be displayed in the Interface Settings page, Show Diagnostics popup.
150
10
Smartport
How the Smartport Feature Works
After the source of the problem is determined and the existing configuration or Smartport macro is corrected, you must perform a reset operation to reset the interface before it can be reapplied with a Smartport type (in the Interface Settings pages). See the workflow area in Common Smartport Tasks section for troubleshooting tips.
151
Smartport
Auto Smartport
10
In order for Auto Smartport to automatically assign Smartport types to interfaces, the Auto Smartport feature must be enabled globally and on the relevant interfaces which Auto Smartport should be allowed to configure. By default, Auto Smartport is enabled and allowed to configure all interfaces. The Smartport type assigned to each interface is determined by the CDP and LLDP packets received on the each interface respectively. If multiple devices are attached to an interface, a configuration profile that is appropriate for all of the devices is applied to the interface if possible. If a device is aged out (no longer receiving advertisements from other devices), the interface configuration is changed according to its Persistent Status. If the Persistent Status is enabled, the interface configuration is retained. If not, the Smartport Type reverts to Default.
Auto Smartport
NOTE In addition to enabling Auto Smartport globally, you must enable Auto Smartport at
the desired interface as well. By default, Auto Smartport is enabled at all the interfaces. See Voice VLAN for more information on enabling Auto Voice VLAN
152
10
Smartport
Auto Smartport
If, for example, an IP phone is attached to a port, it transmits CDP or LLDP packets that advertise its capabilities. After reception of these CDP and/or LLDP packets, the device derives the appropriate Smartport type for phone and applies the corresponding Smartport macro to the interface where the IP phone attaches. Unless Persistent Auto Smartport is enabled on an interface, the Smartport type and resulting configuration applied by Auto Smartport is removed if the attaching device(s) ages out, links down, reboots, or conflicting capabilities are received. Aging out times are determined by the absence of CDP and/or LLDP advertisements from the device for a specified time period.
153
Smartport
Auto Smartport
10
LLDP Capabilities Mapping to Smartport Type Capability Name Other Repeater IETF RFC 2108 MAC Bridge IEEE Std. 802.1D WLAN Access Point IEEE Std. 802.11 MIB Router IETF RFC 1812 Telephone IETF RFC 4293 DOCSIS cable device IETF RFC 4639 and IETF RFC 4546 Station Only IETF RFC 4293 C-VLAN Component of a VLAN Bridge IEEE Std. 802.1Q S-VLAN Component of a VLAN Bridge IEEE Std. 802.1Q Two-port MAC Relay (TPMR) IEEE Std. 802.1Q Reserved LLDP Bit 1 2 3 4 5 6 7 8 9 10 11 12-16 Smartport Type Ignore Ignore Switch Wireless Access Point Router ip_phone Ignore Host Switch Switch Ignore Ignore
NOTE If only the IP Phone and Host bits are set, then the Smartport type is
ip_phone_desktop.
154
10
Smartport
Error Handling
If all devices on an interface advertise the same capability (there is no conflict) the matching Smartport type is applied to the interface. If one of the devices is a switch, the Switch Smartport type is used. If one of the devices is an AP, the Wireless Access Point Smartport type is used. If one of the devices is an IP phone and another device is a host, the ip_phone_desktop Smartport type is used. If one of the devices is an IP phone desktop and the other is an IP phone or host, the ip_phone_desktop Smartport type is used. In all other cases the default Smartport type is used.
For more information about LLDP/CDP refer to the Configuring LLDP and Configuring CDP sections, respectively.
between reboots only if the running configuration with the Smartport type applied at the interfaces is saved to the startup configuration file.
Error Handling
When a smart port macro fails to apply to an interface, you can examine the point of the failure in the Interface Settings page and reset the port and reapply the macro after the error is corrected from the Interface Settings and Interface Settings Edit pages.
155
Smartport
Default Configuration
10
Smartport is always available. By default, Auto Smartport is enabled by Auto Voice VLAN, relies on both CDP and LLDP to detect attaching device's Smartport type, and detects Smartport type IP phone, IP phone + Desktop, Switch, and Wireless Access Point. See Voice VLAN for a description of the voice factory defaults.
Default Configuration
a firmware level that supports Auto Smartport, the Auto Voice VLAN is disabled after the upgrade. If Telephony OUI was enabled before the upgrade, then Auto Smartport is disabled after the upgrade, and Telephony OUI remains enabled.
Workflow1: To globally enable Auto Smartport on the device, and to configure a port with Auto Smartport, perform the following steps:
STEP 1 To enable the Auto Smartport feature on the device, open the Smartport >
Properties page. Set Administrative Auto Smartport to Enable or Enable by Voice VLAN.
STEP 2 Select whether the device is to process CDP and/or LLDP advertisements from
connected devices.
STEP 3 Select which type of devices are to be detected in the Auto Smartport Device
Detection field.
156
10
STEP 4 Click Apply
Smartport
Common Smartport Tasks
STEP 5 To enable the Auto Smartport feature on one or more interfaces, open the
Settings page.
STEP 2 Select the interface, and click Edit. STEP 3 Select the Smartport type that is to be assigned to the interface in the Smartport
Application field.
STEP 4 Set the macro parameters as required. STEP 5 Click Apply.
Workflow3: To adjust Smartport macro parameter defaults and/or bind a user-defined macro pair to a Smartport type, perform the following steps:
Through this procedure you can accomplish the following: View the macro source. Change parameter defaults. Restore the parameter defaults to the factory settings. Bind a user-defined macro pair (a macro and its corresponding anti-macro) to a Smartport type.
1. Open the Smartport > Smartport Type Settings page. 2. Select the Smartport Type.
157
Smartport
Common Smartport Tasks
10
3. Click View Macro Source to view the current Smartport macro that is associated with the selected Smartport Type. 4. Click Edit to open a new window in which you can bind user-defined macros to the selected Smartport type and/or modify the default values of the parameters in the macros bound to that Smartport type. These parameter default values are used when Auto Smartport applies the selected Smartport type (if applicable) to an interface. 5. In the Edit page, modify the fields. 6. Click Apply to rerun the macro if the parameters were changed, or Restore Defaults to restore default parameter values to built-in macros if required.
Workflow4: To rerun a Smartport macro after it has failed, perform the following steps:
STEP 1 In the Interface Settings page, select an interface with Smartport type Unknown. STEP 2 Click Show Diagnostics to see the problem. STEP 3 Troubleshoot, then correct the problem. Consider the troubleshooting tip below. STEP 4 Click Edit. A new window appears in which you can click Reset to reset the
interface.
STEP 5 Return to the main page and reapply the macro using either Reapply (for devices
that are not switches, routers or APs) or Reapply Smartport Macro (for switches, routers or APs) to run the Smartport Macro on the interface. A second method of resetting single or multiple unknown interfaces is:
STEP 1 In the Interface Settings page, select the Port Type equals to checkbox. STEP 2 Select Unknown and click Go. STEP 3 Click Reset All Unknown Smartports. Then reapply the macro as described above.
TIP
The reason that the macro failed might be a conflict with a configuration on the interface made prior to applying the macro (most often encountered with security and storm-control settings), a wrong port type, a typo or an incorrect command within the user-defined macro, or an invalid parameter setting. Parameters are checked for neither type nor boundary prior to the attempt to apply the macro, therefore, an incorrect or invalid input to a parameter value will almost assuredly cause failure when applying the macro.
158
10
Smartport
Configuring Smartport Using The Web-based Interface
Smartport Properties
To configure the Smartport feature globally:
STEP 1 Click Smartport > Properties. STEP 2 Enter the parameters.
Administrative Auto SmartportSelect to globally enable or disable Auto Smartport. The following options are available: DisableSelect to disable Auto Smartport on the device. EnableSelect to enable Auto Smartport on the device. Enable by Auto Voice VLANThis enables Auto Smartport, but puts it in operation only when Auto Voice VLAN is also enabled and in operation. Enable by Auto Voice VLAN is the default.
Auto Smartport Device Detection MethodSelect whether incoming CDP, LLDP, or both types of packets are used to detect the Smartport type of the attaching device(s). At least one must be checked in order for Auto Smartport to identify devices. Operational CDP StatusDisplays the operational status of CDP. Enable CDP if Auto Smartport is to detect the Smartport type based on CDP advertisement. Operational LLDP StatusDisplays the operational status of LLDP. Enable LLDP if Auto Smartport is to detect the Smartport type based on LLDP/ LLDP-MED advertisement. Auto Smartport Device DetectionSelect each type of device for which Auto Smartport can assign Smartport types to interfaces. If unchecked, Auto Smartport does not assign that Smartport type to any interface.
159
Smartport
Configuring Smartport Using The Web-based Interface
10
STEP 3 Click Apply. This sets the global Smartport parameters on the device.
interfaces which have already been assigned that type by Auto Smartport. In this case, binding an invalid macro or setting an invalid default parameter value causes all ports of this Smartport type to become unknown.
STEP 1 Click Smartport > Smartport Type Settings. STEP 2 To view the Smartport macro associated with a Smartport type, select a
Port TypeSelect a Smartport type. Macro NameDisplays the name of the Smartport macro currently associated with the Smartport type. Macro TypeSelect whether the pair of macro and anti-macro associated with this Smartport type is built-in or user-defined.
160
10
Smartport
Configuring Smartport Using The Web-based Interface
User Defined MacroIf desired, select the user-defined macro that is to be associated with the selected Smartport type. The macro must have already been paired with an anti-macro. Pairing of the two macros is done by name and is described in the Smartport Macro section.
Macro ParametersDisplays the following fields for three parameters in the macro: Parameter NameName of parameter in macro. Parameter ValueCurrent value of parameter in macro. This can be changed here. Parameter DescriptionDescription of parameter.
You can restore the default parameter values by clicking Restore Defaults.
STEP 5 Click Apply to save the changes to the running configuration. If the Smartport
macro and/or its parameter values associated with the Smartport type are modified, Auto Smartport automatically reapplies the macro to the interfaces currently assigned with the Smartport type by Auto Smartport. Auto Smartport does not apply the changes to interfaces that were statically assigned a Smartport type.
NOTE There is no method to validate macro parameters because they do not have a type
association. Therefore, any entry is valid at this point. However, invalid parameter values may cause errors to occur when the Smartport type is assigned to an interface, applying the associated macro.
161
Smartport
Configuring Smartport Using The Web-based Interface
10
corrections have been made prior to clicking Reapply. See the workflow area in Common Smartport Tasks section for troubleshooting tips. Reapply a Smartport macro to an interface. In some circumstances, you may want to reapply a Smartport macro so that the configuration at an interface is up to date. For instance, reapplying a switch Smartport macro at a device interface makes the interface a member of the VLANs created since the last macro application. You have to be familiar with the current configurations on the device and the definition of the macro to determine if a reapplication has any impact on the interface. Reset unknown interfaces. This sets the mode of Unknown interfaces to Default.
Reapply the associated Smartport macro in the following ways: Select a group of Smartport types (switches, routers or APs) and click Reapply Smartport Macro. The macros are applied to all selected interface types. Select an interface that is UP and click Reapply to reapply the last macro that was applied to the interface. The Reapply action also adds the interface to all newly-created VLANs.
STEP 2 Smartport Diagnostic.
If a Smartport macro fails, the Smartport Type of the interface is Unknown. Select an interface which is of unknown type and click Show Diagnostic. This displays the command at which application of the macro failed. See the workflow area in Common Smartport Tasks section for troubleshooting tips. Proceed to reapply the macro after correcting the problem.
STEP 3 Resetting all Unknown interfaces to Default type.
Select the Port Type equals to checkbox. Select Unknown and click Go. Click Reset All Unknown Smartports. Then reapply the macro as described above. This performs a reset on all interfaces with type Unknown, meaning that all interfaces are returned to the Default type. After correcting the error in the macro or on the current interface configuration or both, a new macro may be applied.
162
10
Smartport
Configuring Smartport Using The Web-based Interface
NOTE Resetting the interface of unknown type does not reset the configuration
performed by the macro that failed. This clean up must be done manually. To assign a Smartport type to an interface or activate Auto Smartport on the interface:
STEP 1 Select an interface and click Edit . STEP 2 Enter the fields.
InterfaceSelect the port or LAG. Smartport TypeDisplays the Smartport type currently assigned to the port/LAG. Smartport ApplicationSelect the Smartport type from the Smartport Application pull-down. Smartport Application Method If Auto Smartport is selected, Auto Smartport automatically assigns the Smartport type based on the CDP and/ or LLDP advertisement received from the connecting devices as well as applying the corresponding Smartport macro. To statically assign a Smartport type and apply the corresponding Smartport macro to the interface, select the desired Smartport type. Persistent StatusSelect to enable the Persistent status. If enabled, the association of a Smartport type to an interface remains even if the interface goes down, or the device is rebooted. Persistent is applicable only if the Smartport Application of the interface is Auto Smartport. Enabling Persistent at an interface eliminates the device detection delay that otherwise occurs. Macro ParametersDisplays the following fields for up to three parameters in the macro: Parameter NameName of parameter in macro. Parameter ValueCurrent value of parameter in macro. This can be changed here. Parameter DescriptionDescription of parameter.
STEP 3 Click Reset to set an interface to Default if it is in Unknown status (as a result of an
unsuccessful macro application). The macro can be reapplied on the main page.
STEP 4 Click Apply to update the changes and assign the Smartport type to the interface.
163
Smartport
Built-in Smartport Macros
10
The following describes the pair of built-in macros for each Smartport type. For each Smartport type there is a macro to configure the interface and an anti macro to remove the configuration. Macro code for the following Smartport types are provided: desktop printer guest server host ip_camera ip_phone ip_phone_desktop switch router ap
desktop
[desktop] #interface configuration, for increased network security and reliability when connecting a desktop device, such as a PC, to a switch port. #macro description Desktop #macro keywords $native_vlan $max_hosts # #macro key description: $native_vlan: The untag VLAN which will be configured on the port # $max_hosts: The maximum number of allowed devices on the port #Default Values are #$native_vlan = Default VLAN #$max_hosts = 10 # #the port type cannot be detected automatically # #the default mode is trunk smartport switchport trunk native vlan $native_vlan # port security max $max_hosts
164
10
port security mode max-addresses port security discard trap 60 # smartport storm-control broadcast level 10 smartport storm-control include-multicast smartport storm-control broadcast enable # spanning-tree portfast # @
Smartport
Built-in Smartport Macros
no_desktop
[no_desktop] #macro description No Desktop # no smartport switchport trunk native vlan smartport switchport trunk allowed vlan remove all # no port security no port security mode no port security max # no smartport storm-control broadcast enable no smartport storm-control broadcast level no smartport storm-control include-multicast # spanning-tree portfast auto # @
printer
[printer] #macro description printer #macro keywords $native_vlan # #macro key description: $native_vlan: The untag VLAN which will be configured on the port #Default Values are #$native_vlan = Default VLAN # #the port type cannot be detected automatically # switchport mode access switchport access vlan $native_vlan # #single host port security max 1 port security mode max-addresses port security discard trap 60
165
Smartport
Built-in Smartport Macros
10
# smartport storm-control broadcast level 10 smartport storm-control include-multicast smartport storm-control broadcast enable # spanning-tree portfast # @
no_printer
[no_printer] #macro description No printer # no switchport access vlan no switchport mode # no port security no port security mode # no smartport storm-control broadcast enable no smartport storm-control broadcast level no smartport storm-control include-multicast # spanning-tree portfast auto # @
guest
[guest] #macro description guest #macro keywords $native_vlan # #macro key description: $native_vlan: The untag VLAN which will be configured on the port #Default Values are #$native_vlan = Default VLAN # #the port type cannot be detected automatically # switchport mode access switchport access vlan $native_vlan # #single host port security max 1 port security mode max-addresses port security discard trap 60 # smartport storm-control broadcast level 10 smartport storm-control include-multicast
166
10
smartport storm-control broadcast enable # spanning-tree portfast # @
Smartport
Built-in Smartport Macros
no_guest]]
[no_guest] #macro description No guest # no switchport access vlan no switchport mode # no port security no port security mode # no smartport storm-control broadcast enable no smartport storm-control broadcast level no smartport storm-control include-multicast # spanning-tree portfast auto # @
server
[server] #macro description server #macro keywords $native_vlan $max_hosts # #macro key description: $native_vlan: The untag VLAN which will be configured on the port # $max_hosts: The maximum number of allowed devices on the port #Default Values are #$native_vlan = Default VLAN #$max_hosts = 10 # #the port type cannot be detected automatically # #the default mode is trunk smartport switchport trunk native vlan $native_vlan # port security max $max_hosts port security mode max-addresses port security discard trap 60 # smartport storm-control broadcast level 10 smartport storm-control broadcast enable #
167
Smartport
Built-in Smartport Macros
10
spanning-tree portfast # @
no_server
[no_server] #macro description No server # no smartport switchport trunk native vlan smartport switchport trunk allowed vlan remove all # no port security no port security mode no port security max # no smartport storm-control broadcast enable no smartport storm-control broadcast level # spanning-tree portfast auto # @
host
[host] #macro description host #macro keywords $native_vlan $max_hosts # #macro key description: $native_vlan: The untag VLAN which will be configured on the port # $max_hosts: The maximum number of allowed devices on the port #Default Values are #$native_vlan = Default VLAN #$max_hosts = 10 # #the port type cannot be detected automatically # #the default mode is trunk smartport switchport trunk native vlan $native_vlan # port security max $max_hosts port security mode max-addresses port security discard trap 60 # smartport storm-control broadcast level 10 smartport storm-control include-multicast smartport storm-control broadcast enable # spanning-tree portfast
168
10
# @
Smartport
Built-in Smartport Macros
no_host
[no_host] #macro description No host # no smartport switchport trunk native vlan smartport switchport trunk allowed vlan remove all # no port security no port security mode no port security max # no smartport storm-control broadcast enable no smartport storm-control broadcast level no smartport storm-control include-multicast # spanning-tree portfast auto # @
ip_camera
[ip_camera] #macro description ip_camera #macro keywords $native_vlan # #macro key description: $native_vlan: The untag VLAN which will be configured on the port #Default Values are #$native_vlan = Default VLAN # switchport mode access switchport access vlan $native_vlan # #single host port security max 1 port security mode max-addresses port security discard trap 60 # smartport storm-control broadcast level 10 smartport storm-control include-multicast smartport storm-control broadcast enable # spanning-tree portfast # @
169
Smartport
Built-in Smartport Macros
10
no_ip_camera
[no_ip_camera] #macro description No ip_camera # no switchport access vlan no switchport mode # no port security no port security mode # no smartport storm-control broadcast enable no smartport storm-control broadcast level no smartport storm-control include-multicast # spanning-tree portfast auto # @
ip_phone
[ip_phone] #macro description ip_phone #macro keywords $native_vlan $voice_vlan $max_hosts # #macro key description: $native_vlan: The untag VLAN which will be configured on the port # $voice_vlan: The voice VLAN ID # $max_hosts: The maximum number of allowed devices on the port #Default Values are #$native_vlan = Default VLAN #$voice_vlan = 1 #$max_hosts = 10 # #the default mode is trunk smartport switchport trunk allowed vlan add $voice_vlan smartport switchport trunk native vlan $native_vlan # port security max $max_hosts port security mode max-addresses port security discard trap 60 # smartport storm-control broadcast level 10 smartport storm-control include-multicast smartport storm-control broadcast enable # spanning-tree portfast # @
170
10
no_ip_phone
Smartport
Built-in Smartport Macros
[no_ip_phone] #macro description no ip_phone #macro keywords $voice_vlan # #macro key description: $voice_vlan: The voice VLAN ID # #Default Values are #$voice_vlan = 1 # smartport switchport trunk allowed vlan remove $voice_vlan no smartport switchport trunk native vlan smartport switchport trunk allowed vlan remove all # no port security no port security mode no port security max # no smartport storm-control broadcast enable no smartport storm-control broadcast level no smartport storm-control include-multicast # spanning-tree portfast auto # @
ip_phone_desktop
[ip_phone_desktop] #macro description ip_phone_desktop #macro keywords $native_vlan $voice_vlan $max_hosts # #macro key description: $native_vlan: The untag VLAN which will be configured on the port # $voice_vlan: The voice VLAN ID # $max_hosts: The maximum number of allowed devices on the port #Default Values are #$native_vlan = Default VLAN #$voice_vlan = 1 #$max_hosts = 10 # #the default mode is trunk smartport switchport trunk allowed vlan add $voice_vlan smartport switchport trunk native vlan $native_vlan # port security max $max_hosts port security mode max-addresses port security discard trap 60 # smartport storm-control broadcast level 10 smartport storm-control include-multicast
171
Smartport
Built-in Smartport Macros
10
smartport storm-control broadcast enable # spanning-tree portfast # @
no_ip_phone_desktop
[no_ip_phone_desktop] #macro description no ip_phone_desktop #macro keywords $voice_vlan # #macro key description: $voice_vlan: The voice VLAN ID # #Default Values are #$voice_vlan = 1 # smartport switchport trunk allowed vlan remove $voice_vlan no smartport switchport trunk native vlan smartport switchport trunk allowed vlan remove all # no port security no port security mode no port security max # no smartport storm-control broadcast enable no smartport storm-control broadcast level no smartport storm-control include-multicast # spanning-tree portfast auto # @
switch
[switch] #macro description switch #macro keywords $native_vlan $voice_vlan # #macro key description: $native_vlan: The untag VLAN which will be configured on the port # $voice_vlan: The voice VLAN ID #Default Values are #$native_vlan = Default VLAN #$voice_vlan = 1 # #the default mode is trunk smartport switchport trunk allowed vlan add all smartport switchport trunk native vlan $native_vlan # spanning-tree link-type point-to-point
172
10
# @
Smartport
Built-in Smartport Macros
no_switch
[no_switch] #macro description No switch #macro keywords $voice_vlan # #macro key description: $voice_vlan: The voice VLAN ID # no smartport switchport trunk native vlan smartport switchport trunk allowed vlan remove all # no spanning-tree link-type # @
router
[router] #macro description router #macro keywords $native_vlan $voice_vlan # #macro key description: $native_vlan: The untag VLAN which will be configured on the port # $voice_vlan: The voice VLAN ID # #Default Values are #$native_vlan = Default VLAN #$voice_vlan = 1 # #the default mode is trunk smartport switchport trunk allowed vlan add all smartport switchport trunk native vlan $native_vlan # smartport storm-control broadcast level 10 smartport storm-control broadcast enable # spanning-tree link-type point-to-point # @
no_router
[no_router] #macro description No router
173
Smartport
Built-in Smartport Macros
10
#macro keywords $voice_vlan # #macro key description: $voice_vlan: The voice VLAN ID # no smartport switchport trunk native vlan smartport switchport trunk allowed vlan remove all # no smartport storm-control broadcast enable no smartport storm-control broadcast level # no spanning-tree link-type # @
ap
[ap] #macro description ap #macro keywords $native_vlan $voice_vlan # #macro key description: $native_vlan: The untag VLAN which will be configured on the port
174
10
Smartport
Built-in Smartport Macros
175
11
Port Management: PoE
The Power over Ethernet (PoE) feature is only available on PoE-based devices. For a list of PoE-based devices, refer to the Device Models section. This section describes how to use the PoE feature. It covers the following topics: PoE on the Device Configuring PoE Properties Configuring PoE Settings
PoE Features
PoE provides the following features: Eliminates the need to run 110/220 V AC power to all devices on a wired LAN. Removes the necessity for placing all network devices next to power sources. Eliminates the need to deploy double cabling systems in an enterprise significantly decreasing installation costs.
176
11
IP phones Wireless access points IP gateways Audio and video remote monitoring devices
Power over Ethernet can be used in any enterprise network that deploys relatively low-powered devices connected to the Ethernet LAN, such as:
PoE Operation
PoE implements in the following stages: DetectionSends special pulses on the copper cable. When a PoE device is located at the other end, that device responds to these pulses. ClassificationNegotiation between the Power Sourcing Equipment (PSE) and the Powered Device (PD) commences after the Detection stage. During negotiation, the PD specifies its class, which is the amount of maximum power that the PD consumes. Power ConsumptionAfter 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 LimitThe maximum power the device agrees to supply is limited to the value the system administrator configures, regardless of the Classification result. Class Power LimitThe 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.
177
11
You can decide the following: Maximum power a PSE is allowed to supply to a PD During device operation, to change the mode from Class Power Limit to Port Limit and vice versa. The power values per port that were configured for the Port Limit mode are retained.
NOTE Changing the mode from Class Limit to Port limit and vice versa when the device is operational forces the Powered Device to reboot.
Maximum port limit allowed as a per-port numerical limit in mW (Port Limit mode). To generate a trap when a PD tries to consume too much and at what percent of the maximum power this trap is generated.
The PoE-specific hardware automatically detects the PD class and its power limit according to the class of the device connected to each specific port (Class Limit mode). If at any time during the connectivity an attached PD requires more power from the device than the configured allocation allows (no matter if the device is in Class Limit or Port Limit mode), the device does the following: Maintains the up/down status of the PoE port link Turns off power delivery to the PoE port Logs the reason for turning off power Generates an SNMP trap
!
CAUTION Consider the following when connecting switches capable of supplying PoE:
The PoE models of the Sx200, Sx300, and Sx500 series switches are PSE (Power Sourcing Equipment) that are capable of supplying DC power to attaching PD (Powered Devices). These devices include VoIP phones, IP cameras, and wireless access points. The PoE switches can detect and supply power to pre-standard legacy PoE Powered Devices. Due to the support of legacy PoE, it is possible that a PoE device acting as a PSE may mistakenly detect and supply power to an attaching PSE, including other PoE switches, as a legacy PD. Even though Sx200/300/500 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 device may not operate properly and
178
11
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 device. 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.
Port LimitThe maximum power limit per each port is configured by the
user.
NOTE When you change from Port Limit to Class Limit or vice versa, you
must disable PoE ports, and enable them after changing the power configuration. TrapsEnable or disable traps. If traps are enabled, you must also enable SNMP and configure at least one SNMP Notification Recipient. Power Trap ThresholdEnter the usage threshold that is a percentage of the power limit. An alarm is initiated if the power exceeds this value.
179
11
The following counters are displayed for each device: Nominal PowerThe total amount of power the device can supply to all the connected PDs. Consumed PowerAmount of power currently being consumed by the PoE ports. Available PowerNominal power minus the amount of consumed power.
to define, per port, the days in the week and the hours that PoE is enabled. When the time range is not active, PoE is disabled. To use this feature, a time range must first be defined in the Time Range page. Click Port Management > PoE > Settings. This page limits the power per port in two ways depending on the Power Mode: Port Limit: Power is limited to a specified wattage. For these settings to be active, the system must be in PoE Port Limit mode. That mode is configured in the PoE Properties page. When the power consumed on the port exceeds the port limit, the port power is turned off. Class Limit: Power is limited based on the class of the connected PD. For these settings to be active, the system must be in PoE Class Limit mode. That mode is configured in the PoE Properties page. When the power consumed on the port exceeds the class limit, the port power is turned off.
180
11
The administrator configures all ports to allocate up to 30 watts. This results in 48 times 30 ports equaling 1440 watts, which is too much. The device cannot provide enough power to each port, so it provides power according to the priority. The administrator sets the priority for each port, allocating how much power it can be given. These priorities are entered in the PoE Settings page. See Device Models for a description of the device models that support PoE and the maximum power that can be allocated to PoE ports. To configure PoE port settings:
STEP 1 Click Port Management > PoE > Settings.The list of fields below is for Port Limit
Power Mode. The fields are slightly different if the Power Mode is Class Limit.
STEP 2 Select a port and click Edit. The list of fields below is for Port Limit Power Mode.
The fields are slightly different if the Power Mode is Class Limit.
STEP 3 Enter the value for the following field:
InterfaceSelect the port to configure. PoE Administrative StatusEnable or disable PoE on the port. Time RangeSelect to enabled PoE on the port. Time Range NameIf Time Range has been enabled, select the time range to be used. Time ranges are defined in the Time Range page. Power Priority LevelSelect 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 AllocationThis field appears only if the Power Mode set in the PoE Properties page is Port Limit. If the Power mode is Power Limit, enter the power in milliwatts allocated to the port. Max Power AllocationDisplays the maximum amount of power permitted on this port.
181
11
ClassThis field appears only if the Power Mode set in the PoE Properties page is Class Limit. The class determines the power level: Class 0 1 2 3 4 Maximum Power Delivered by Device Port 15.4 watt 4.0 watt 7.0 watt 15.4 watt 30.0 watt
Power ConsumptionDisplays the amount of power in milliwatts assigned to the powered device connected to the selected interface. Overload CounterDisplays the total number of power overload occurrences. Short CounterDisplays the total number of power shortage occurrences. Denied CounterDisplays number of times the powered device was denied power. Absent CounterDisplays the number of times that power was stopped to the powered device, because the powered device was no longer detected. Invalid Signature CounterDisplays the times 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.
182
11
183
12
VLAN Management
This section covers the following topics: VLANs Configuring Default VLAN Settings Creating VLANs Configuring VLAN Interface Settings Defining VLAN Membership GVRP Settings VLAN Groups Voice VLAN Access Port Multicast TV VLAN Customer Port Multicast TV VLAN
VLANs
A VLAN is a logical group of ports that enables devices associated with it to communicate with each other over the Ethernet MAC layer, regardless of the physical LAN segment of the bridged network to which they are connected.
184
12
VLAN Description
VLAN Management
VLANs
Each VLAN is configured with a unique VID (VLAN ID) with a value from 1 to 4094. A port on a device in a bridged network is a member of a VLAN if it can send data to and receive data from the VLAN. A port is an untagged member of a VLAN if all packets destined for that port into the VLAN have no VLAN tag. A port is a tagged member of a VLAN if all packets destined for that port into the VLAN have a VLAN tag. A port can be a member of one untagged VLAN and can be a member of several tagged VLANs. A port in VLAN Access mode can be part of only one VLAN. If it is in General or Trunk mode, the port can be part of one or more VLANs. VLANs address security and scalability issues. Traffic from a VLAN stays within the VLAN, and terminates at devices in the VLAN. It also eases network configuration by logically connecting devices without physically relocating those devices. If a frame is VLAN-tagged, a four-byte VLAN tag is added to each Ethernet frame. The tag contains a VLAN ID between 1 and 4094, and a VLAN Priority Tag (VPT) between 0 and 7. See Quality of Service for details about VPT. When a frame enters a VLAN-aware device, it is classified as belonging to a VLAN, based on the four-byte VLAN tag in the frame. If there is no VLAN tag in the frame or the frame is priority-tagged only, the frame is classified to the VLAN based on the PVID (Port VLAN Identifier) configured at the ingress port where the frame is received. The frame is discarded at the ingress port if Ingress Filtering is enabled and the ingress port is not a member of the VLAN to which the packet belongs. A frame is regarded as priority-tagged only if the VID in its VLAN tag is 0. Frames belonging to a VLAN remain within the VLAN. This is achieved by sending or forwarding a frame only to egress ports that are members of the target VLAN. An egress port may be a tagged or untagged member of a VLAN. The egress port: Adds a VLAN tag to the frame if the egress port is a tagged member of the target VLAN, and the original frame does not have a VLAN tag. Removes the VLAN tag from the frame if the egress port is an untagged member of the target VLAN, and the original frame has a VLAN tag.
185
VLAN Management
VLANs
12
VLAN Roles
VLANs function at Layer 2. All VLAN traffic (Unicast/Broadcast/Multicast) remains within its VLAN. Devices attached to different VLANs do not have direct connectivity to each other over the Ethernet MAC layer. Devices from different VLANs can communicate with each other only through Layer 3 routers. An IP router, for example, is required to route IP traffic between VLANs if each VLAN represents an IP subnet. The IP router might be a traditional router, where each of its interfaces connects to only one VLAN. Traffic to and from a traditional IP router must be VLAN untagged. The IP router can be a VLAN-aware router, where each of its interfaces can connect to one or more VLANs. Traffic to and from a VLAN-aware IP router can be VLAN tagged or untagged. Adjacent VLAN-aware devices exchange VLAN information with each other by using Generic VLAN Registration Protocol (GVRP). As a result, VLAN information is propagated through a bridged network. VLANs on a device can be created statically or dynamically, based on the GVRP information exchanged by devices. A VLAN can be static or dynamic (from GVRP), but not both. For more information about GVRP, refer to the GVRP Settings section. Some VLANs can have additional roles, including: Voice VLAN: For more information refer to the Voice VLAN section. Guest VLAN: Set in the Edit VLAN Authentication page. Default VLAN: For more information refer to the Configuring Default VLAN Settings section. Management VLAN (in Layer 2-system-mode systems): For more information refer to the Layer 2 IP Addressing section.
QinQ
QinQ provides isolation between service provider networks and customers' networks. The device is a provider bridge that supports port-based c-tagged service interface. With QinQ, the device adds an ID tag known as Service Tag (S-tag) to forward traffic over the network. The S-tag is used to segregate traffic between various customers, while preserving the customer VLAN tags.
186
12
VLAN Management
Configuring Default VLAN Settings
Customer traffic is encapsulated with an S-tag with TPID 0x8100, regardless of whether it was originally c-tagged or untagged. The S-tag allows this traffic to be treated as an aggregate within a provider bridge network, where the bridging is based on the S-tag VID (S-VID) only. The S-Tag is preserved while traffic is forwarded through the network service provider's infrastructure, and is later removed by an egress device. An additional benefit of QinQ is that there is no need to configure customers' edge devices. QinQ is enabled in the VLAN Management > Interface Settings page.
187
VLAN Management
Configuring Default VLAN Settings
12
It 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 device 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. RADIUS servers cannot assign the default VLAN to 802.1x supplicants by using Dynamic VLAN Assignment.
When the VID of the default VLAN is changed, the device performs the following on all the ports in the VLAN, after saving the configuration and rebooting the device: Removes VLAN membership of the ports from the original default VLAN (possible only after reboot). Changes the PVID (Port VLAN Identifier) of the ports to the VID of the new default VLAN. The original default VLAN ID is removed from the device. To be used, it must be recreated. Adds the ports as untagged VLAN members of the new default VLAN.
Current Default VLAN IDDisplays the current default VLAN ID. Default VLAN ID After RebootEnter a new VLAN ID to replace the default VLAN ID after reboot.
STEP 3 Click Apply. STEP 4 Click Save (in the upper-right corner of the window) and save the Running
Configuration to the Startup Configuration. The Default VLAN ID After Reset becomes the Current Default VLAN ID after you reboot the device.
188
12
Creating VLANs
VLAN Management
Creating VLANs
You can create a VLAN, but this has no effect until the VLAN is attached to at least one port, either manually or dynamically. Ports must always belong to one or more VLANs. The 300 Series device supports up to 4K VLANs, including the default VLAN. Each VLAN must be configured with a unique VID (VLAN ID) with a value from 1 to 4094. The device reserves VID 4095 as the Discard VLAN. All packets classified to the Discard VLAN are discarded at ingress, and are not forwarded to a port. To create a VLAN:
STEP 1 Click VLAN Management > Create VLAN.
The Create VLAN page contains the following fields for all VLANs: VLAN IDUser-defined VLAN ID. VLAN NameUser-defined VLAN name. TypeVLAN type: DynamicVLAN was dynamically created through Generic VLAN Registration Protocol (GVRP). StaticVLAN is user-defined. DefaultVLAN is the default VLAN.
STEP 2 Click Add to add a new VLAN or select an existing VLAN and click Edit to modify
the VLAN parameters. 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 (VID),
and optionally the VLAN Name. To create a range of VLANs, select the Range radio button, and specify the range of VLANs to be created by entering the Starting VID and Ending VID, inclusive. When using the Range function, the maximum number of VLANs you can create at one time is 100.
STEP 4 Click Apply to create the VLAN(s).
189
VLAN Management
Configuring VLAN Interface Settings
12
InterfaceSelect a Port/LAG. Interface VLAN ModeSelect the interface mode for the VLAN. The options are: GeneralThe 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. AccessThe interface is an untagged member of a single VLAN. A port configured in this mode is known as an access port. TrunkThe 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. CustomerSelecting 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 customer ports. See QinQ.
Administrative PVIDEnter the Port VLAN ID (PVID) of the VLAN to which incoming untagged and priority tagged frames are classified. The possible values are 1 to 4094. Frame TypeSelect the type of frame that the interface can receive. Frames that are not of the configured frame type are discarded at ingress. These frame types are only available in General mode. Possible values are: Admit AllThe interface accepts all types of frames: untagged frames, tagged frames, and priority tagged frames.
190
12
VLAN Management
Defining VLAN Membership
Admit Tagged OnlyThe interface accepts only tagged frames. Admit Untagged OnlyThe interface accepts only untagged and priority frames.
Ingress Filtering(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 is not a member. Ingress filtering can be disabled or enabled on general ports. It is always enabled on access ports and trunk ports.
STEP 5 Click Apply. The parameters are written to the Running Configuration file.
191
VLAN Management
Defining VLAN Membership
12
Configuring 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:
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. The port mode for each port or LAG appears with its current port mode (Access, Trunk or General) configured from the Interface Settings page. Each port or LAG appears with its current registration to the VLAN.
STEP 3 Change the registration of an interface to the VLAN by selecting the desired
option from the following list: ForbiddenThe interface is not allowed to join the VLAN even from GVRP registration. When a port is not a member of any other VLAN, enabling this option on the port makes the port part of internal VLAN 4095 (a reserved VID). ExcludedThe interface is currently not a member of the VLAN. This is the default for all the ports and LAGs. The port can join the VLAN through GVRP registration. TaggedThe interface is a tagged member of the VLAN. UntaggedThe interface is an untagged member of the VLAN. Frames of the VLAN are sent untagged to the interface VLAN. Multicast TV VLANThe interface used for Digital TV using Multicast IP. PVIDSelect 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. You can continue to display and/or configure port membership of another VLAN by selecting another VLAN ID.
192
12
Configuring VLAN Membership
VLAN Management
Defining VLAN Membership
The Port VLAN Membership page displays all ports on the device along with a list of VLANs to which each port belongs. If the port-based authentication method for an interface is 802.1x and the Administrative Port Control is Auto, then: Until the port is authenticated, it is excluded from all VLANs, except guest and unauthenticated ones. In the VLAN to Port page, the port is marked with an upper case P. When the port is authenticated, it receives membership in the VLAN in which it was configured.
displayed for all interfaces of the selected type: InterfacePort/LAG ID. ModeInterface VLAN mode that was selected in the Interface Settings page. Administrative VLANsDrop-down list that displays all VLANs of which the interface might be a member. Operational VLANsDrop-down list that displays all VLANs of which the interface is currently a member. LAGIf interface selected is Port, displays the LAG in which it is a member.
STEP 3 Select a port, and click the Join VLAN button. STEP 4 Enter the values for the following fields:
InterfaceSelect a Port or LAG. ModeDisplays the port VLAN mode that was selected in the Interface Settings page. Select VLANTo associate a port with a VLAN(s), move the VLAN ID(s) from the left list to the right list by using the arrow buttons. The default VLAN might appear in the right list if it is tagged, but it cannot be selected. TaggingSelect one of the following tagging/PVID options:
193
VLAN Management
GVRP Settings
12
ForbiddenThe interface is not allowed to join the VLAN even from GVRP registration. When a port is not a member of any other VLAN, enabling this option on the port makes the port part of internal VLAN 4095 (a reserved VID). ExcludedThe interface is currently not a member of the VLAN. This is the default for all the ports and LAGs. The port can join the VLAN through GVRP registration TaggedSelect whether the port is tagged. This is not relevant for Access ports. UntaggedSelect whether port is untagged. This is not relevant for Access ports. PVIDPort PVID is set to this VLAN. If the interface is in access mode or trunk mode, the device automatically makes the interface an untagged member of the VLAN. If the interface is in general mode, you must manually configure VLAN membership.
STEP 5 Click Apply. The settings are modified and written to the Running Configuration
file.
STEP 6 To see the administrative and operational VLANs on an interface, click Details.
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. Since GVRP requires support for tagging, the port must be configured in Trunk or General mode. When a port joins a VLAN by using GVRP, it is added to the VLAN as a dynamic member, unless this was expressly forbidden in the Port VLAN Membership page. If the VLAN does not exist, it is dynamically created when Dynamic VLAN creation is enabled for this port (in the GVRP Settings page).
194
12
VLAN Management
VLAN Groups
GVRP must be activated globally as well as on each port. When it is activated, it transmits and receives GARP Packet Data Units (GPDUs). VLANs that are defined but not active are not propagated. To propagate the VLAN, it must be up on at least one port. By default, GVRP is disabled globally and on ports.
type.
STEP 5 To define GVRP settings for a port, select it, and click Edit. STEP 6 Enter the values for the following fields:
InterfaceSelect the interface (Port or LAG) to be edited. GVRP StateSelect to enable GVRP on this interface. Dynamic VLAN CreationSelect to enable Dynamic VLAN Creation on this interface. GVRP RegistrationSelect 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 Groups
VLAN groups are used for load balancing of traffic on a Layer 2 network. Packets are assigned a VLAN according to various classifications that have been configured (such as VLAN groups).
195
VLAN Management
VLAN Groups
12
If several classifications schemes are defined, packets are assigned to a VLAN in the following order: TAG: If the packet is tagged, the VLAN is taken from the tag. MAC-Based VLAN: If a MAC-based VLAN has been defined, the VLAN is taken from the source MAC-to-VLAN mapping of the ingress interface. PVID: VLAN is taken from the port default VLAN ID.
MAC-based Groups
MAC-based VLAN classification enable packets to be classified according to their source MAC address. You can then define MAC-to-VLAN mapping per interface. You can define several MAC-based VLAN groups, which each group containing different MAC addresses. These MAC-based groups can be assigned to specific ports/LAGs. MAC-based VLAN groups cannot contain overlapping ranges of MAC addresses on the same port.
Workflow
To define a MAC-based VLAN group: 1. Assign a MAC address to a VLAN group ID (using the MAC-Based Groups page). 2. For each required interface: a. Assign the VLAN group to a VLAN (using Mac-Based Groups to VLAN page). The interfaces must be in General mode. b. If the interface does not belong to the VLAN, manually assign it to the VLAN using the Port to VLAN page.
12
Prefix MaskEnter one of the following: HostSource host of the MAC address LengthPrefix of the MAC address
VLAN Management
VLAN Groups
NOTE This MAC address cannot be assigned to any other VLAN group.
Group TypeDisplays that the group is MAC-Based. InterfaceEnter a general interface (port/LAG) through which traffic is received. Group IDSelect a VLAN group, defined in the MAC-Based Groups page. VLAN IDSelect the VLAN to which traffic from the VLAN group is forwarded.
STEP 4 Click Apply to set the mapping of the VLAN group to the VLAN. This mapping
does not bind the interface dynamically to the VLAN; the interface must be manually added to the VLAN.)
197
VLAN Management
Voice VLAN
12
In a LAN, voice devices, such as IP phones, VoIP endpoints, and voice systems are placed into the same VLAN. This VLAN is referred as the voice VLAN. If the voice devices are in different voice VLANs, IP (Layer 3) routers are needed to provide communication. This section covers the following topics: Voice VLAN Overview Configuring Voice VLAN
Voice VLAN
The following are typical voice deployment scenarios with appropriate configurations: UC3xx/UC5xx hosted: All Cisco phones and VoIP endpoints support this deployment model. For this model, the UC3xx/UC5xx, Cisco phones and VoIP endpoints reside in the same voice VLAN. The voice VLAN of UC3xx/ UC5xx defaults to VLAN 100. Third-party IP PBX-hosted: Cisco SBTG CP-79xx, SPA5xx phones and SPA8800 endpoints support this deployment model. In this model, the VLAN used by the phones is determined by the network configuration. There may or may not be separate voice and data VLANs. The phones and VoIP endpoints register with an on-premise IP PBX. IP Centrex/ITSP hosted: Cisco CP-79xx, SPA5xx phones and SPA8800 endpoints support this deployment model. For this model, the VLAN used by the phones is determined by the network configuration. There may or may not be separate voice and data VLANs. The phones and VoIP endpoints register with an off-premise SIP proxy in the cloud.
198
12
VLAN Management
Voice VLAN
From a VLAN perspective, the above models operate in both VLAN-aware and VLAN-unaware environments. In the VLAN-aware environment, the voice VLAN is one of the many VLANs configured in an installation. The VLAN-unaware scenario is equivalent to a VLAN-aware environment with only one VLAN. The device always operates as a VLAN-aware switch. The device supports a single voice VLAN. By default, the voice VLAN is VLAN 1. The voice VLAN is defaulted to VLAN 1. A different voice VLAN can be manually configured. It can also be dynamically learned when Auto Voice VLAN is enabled. Ports can be manually added to the voice VLAN by using basic VLAN configuration described in the Configuring VLAN Interface Setting section, or by manually applying voice-related Smartport macro to the ports. Alternatively, they can be added dynamically if the device is in Telephony OUI mode, or has Auto Smartports enabled.
199
VLAN Management
Voice VLAN
12
Unlike Telephony OUI mode that detects voice devices based on telephony OUI, Auto Voice VLAN mode depends on Auto Smartport to dynamically add the ports to the voice VLAN. Auto Smartport, if enabled, adds a port to the voice VLAN if it detects an attaching device to the port that advertises itself as a phone or media end points through CDP and/or LLDP-MED.
Voice End-Points
To have a voice VLAN work properly, the voice devices, such as Cisco phones and VoIP endpoints, must be assigned to the voice VLAN where it sends and receives its voice traffic. Some of the possible scenarios are as follows: A phone/endpoint may be statically configured with the voice VLAN. A phone/endpoint may obtain the voice VLAN in the boot file it downloads from a TFTP server. A DHCP server may specify the boot file and the TFTP server when it assigns an IP address to the phone. A phone/endpoint may obtain the voice VLAN information from CDP and LLDP-MED advertisements it receives from their neighbor voice systems and switches.
The device expects the attaching voice devices to send voice VLAN, tagged packets. On ports where the voice VLAN is also the native VLAN, voice VLAN untagged packets are possible.
200
12
VLAN Management
Voice VLAN
When Auto Smartport is enabled, depending on Auto Voice VLAN mode, Auto Smartport is enabled when Auto Voice VLAN becomes operational. If desired, you can make Auto Smartport independent of Auto Voice VLAN.
NOTE The default configuration list here applies to switches whose firmware version
supports Auto Voice VLAN out of the box. It also applies to unconfigured switches that have been upgraded to the firmware version that supports Auto Voice VLAN.
NOTE The defaults and the voice VLAN triggers are designed to have no effect on any
installations without a voice VLAN and on switches that have already been configured. You may manually disable and enable Auto Voice VLAN and/or Auto Smartport to fit your deployment if needed.
configure the port on the UC device using the switchport voice vlan command to ensure the UC device advertises its voice VLAN in CDP at the port. It synchronizes the voice VLAN-related parameters with other Auto Voice VLAN-enabled switches, using Voice Service Discovery Protocol (VSDP). The device always configures itself with the voice VLAN from the highest priority source it is aware of. The priority is based on the source type and MAC address of the source providing the voice VLAN information. Source type priority from high to low are static VLAN configuration, CDP advertisement, and default configuration based on changed default VLAN, and default voice VLAN. A numeric low MAC address is of higher priority than a numeric high MAC address. It maintains the voice VLAN until a new voice VLAN from a higher priority source is discovered or until the Auto Voice VLAN is restarted by the user. When restarted, the device resets the voice VLAN to the default voice VLAN and restarts the Auto Voice VLAN discovery.
201
VLAN Management
Voice VLAN
12
When a new voice VLAN is configured/discovered, the device automatically creates it, and replaces all the port memberships of the existing voice VLAN to the new voice VLAN. This may interrupt or terminate existing voice sessions, which is expected when network topology is altered.
NOTE If the device is in Layer 2 system mode, it can synchronize with only
VSDP capable switches in the same management VLAN. If the device is in Layer 3 system mode, it can synchronize with VSDP capable switches that are in the directly-connected IP subnets configured at the device. Auto Smartport works with CDP/LLDP to maintain the port memberships of the voice VLAN when voice end-points are detected from the ports: When CDP and LLDP are enabled, the device sends out CDP and LLDP packets periodically to advertise the voice VLAN to the voice endpoints to use. When a device attaching to a port advertises itself as a voice endpoint through CDP and/or LLDP, the Auto Smartport automatically adds the port to the voice VLAN by applying the corresponding Smartport macro to the port (if there is no other devices from the port advertising a conflicting or superior capability). If a device advertises itself as a phone, the default Smartport macro is phone. If a device advertises itself as a phone and host or phone and bridge, the default Smartport macro is phone+desktop.
202
12
Voice VLAN Constraints
The following constraints exist: Only one Voice VLAN is supported.
VLAN Management
Voice VLAN
In addition the following constraints are applicable for Telephony OUI: The Voice VLAN cannot be VLAN1 (the default VLAN). The Voice VLAN cannot be Smartport enabled. The Voice VLAN cannot support DVA (Dynamic VLAN assignment). The Voice VLAN cannot be the Guest VLAN if the voice VLAN mode is OUI. If the voice VLAN mode is Auto, then the Voice VLAN can be the Guest VLAN. The Voice VLAN QoS decision has priority over any other QoS decision, except for the Policy/ACL QoS decision. A new VLAN ID can be configured for the Voice VLAN only if the current Voice VLAN does not have candidate ports. The interface VLAN of a candidate port must be in General or Trunk mode. The Voice VLAN QoS is applied to candidate ports that have joined the Voice VLAN, and to static ports. The voice flow is accepted if the MAC address can be learned by the Forwarding Database (FDB). (If there is no free space in FDB, no action occurs).
203
VLAN Management
Voice VLAN
12
NOTE If the device is currently in Telephony OUI mode, you must disable it
Settings page.
NOTE Step 7 and Step 8 are optional as they are enabled by default.
Interface page.
204
12
Configuring 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.
VLAN Management
Voice VLAN
Configure the voice VLAN mode (Telephony OUI or Auto Voice VLAN). Configure how Auto Voice VLAN is triggered.
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.
CoS/802.1p Select a CoS/802.1p value that to be used by LLDP-MED as a voice network policy. Refer to Administration > Discovery > LLDP > LLDP MED Network Policy for additional details. DSCPSelection of DSCP values that to be used by the LLDP-MED as a voice network policy. Refer to Administration > Discovery > LLDP > LLDP MED Network Policy for additional details. Dynamic Voice VLANSelect this field to disable or enable voice VLAN feature in one of the following ways: -
205
VLAN Management
Voice VLAN
12
Auto Voice VLAN ActivationIf Auto Voice VLAN was enabled, select one of the following options to activate Auto Voice VLAN: -
ImmediateAuto Voice VLAN on the device is to be activated and put into operation immediately if enabled. By External Voice VLAN TriggerAuto Voice VLAN on the device is activated and put into operation only if the device detects a device advertising the voice VLAN.
NOTE Manually re-configuring 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 that was learned from external sources.
STEP 3 Click Apply. The VLAN properties are written to the Running Configuration file.
Inactive state.
To view Auto Voice VLAN parameters:
STEP 1 Click VLAN Management > Voice VLAN > Auto Voice VLAN.
The Operation Status block on this page shows the information about the current voice VLAN and its source: Auto Voice VLAN StatusDisplays whether Auto Voice VLAN is enabled. Voice VLAN IDThe identifier of the current voice VLAN
206
12
VLAN Management
Voice VLAN
Source TypeDisplays the type of source where the voice VLAN is discovered by the root device. CoS/802.1pDisplays CoS/802.1p values to be used by the LLDP-MED as a voice network policy. DSCPDisplays DSCP values to be used by the LLDP-MED as a voice network policy. Root Switch MAC AddressThe MAC address of the Auto Voice VLAN root device that discovers or is configured with the voice VLAN from which the voice VLAN is learned. Switch MAC AddressBase MAC address of the device. If the device's Switch MAC address is the Root Switch MAC Address, the device is the Auto Voice VLAN root device. Voice VLAN ID Change TimeLast time that voice VLAN was updated.
STEP 2 Click Restart Auto Voice VLAN to reset the voice VLAN to the default voice VLAN
and restart Auto Voice VLAN discovery on all the Auto-Voice-VLAN-enabled switches in the LAN. The Voice VLAN Local Table displays voice VLAN configured on the device, as well as any voice VLAN configuration advertised by directly-connected neighbor devices. It contains the following fields: InterfaceDisplays the interface on which voice VLAN configuration was received or configured. If N/A appears, the configuration was done on the device itself. If an interface appears, a voice configuration was received from a neighbor. Source MAC Address MAC address of a UC from which the voice configuration was received. Source Type Type of UC from which voice configuration was received. The following options are available: DefaultDefault voice VLAN configuration on the device StaticUser-defined voice VLAN configuration defined on the device. CDPUC that advertised voice VLAN configuration is running CDP. LLDPUC that advertised voice VLAN configuration is running LLDP. Voice VLAN IDThe identifier of the advertised or configured voice VLAN
207
VLAN Management
Voice VLAN
12
Voice VLAN IDThe identifier of the current voice VLAN. CoS/802.1pThe advertised or configured CoS/802.1p values that are used by the LLDP-MED as a voice network policy. DSCPThe advertised or configured DSCP values that are used by the LLDP-MED as a voice network policy. Best Local SourceDisplays whether this voice VLAN was used by the device. The following options are available: YesThe device uses this voice VLAN to synchronize with other Auto Voice VLAN-enabled switches. This voice VLAN is the voice VLAN for the network unless a voice VLAN from a higher priority source is discovered. Only one local source is the best local source. NoThis is not the best local source.
208
12
STEP 1 Click VLAN Management > Voice VLAN > Telephony OUI.
VLAN Management
Voice VLAN
The Telephony OUI page contains the following fields: Telephony OUI Operational StatusDisplays whether OUIs are used to identify voice traffic. CoS/802.1pSelect the CoS queue to be assigned to voice traffic. Remark CoS/802.1pSelect whether to remark egress traffic. Auto Membership Aging TimeEnter 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 2 Click Apply to update the Running Configuration of the device with these values.
The Telephony OUI table appears: Telephony OUIFirst six digits of the MAC address that are reserved for OUIs. DescriptionUser-assigned OUI description.
STEP 3 Click Restore OUI Defaults to delete all of the user-created OUIs, and leave only
the default OUIs in the table. 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, the system recovers the known OUIs.
STEP 4 To add a new OUI, click Add. STEP 5 Enter the values for the following fields:
STEP 6 Click Apply. The OUI is added to the Telephony OUI Table.
209
VLAN Management
Voice VLAN
12
Adding Interfaces to Voice VLAN on Basis of OUIs
The QoS attributes can be assigned per port to the voice packets in one of the following modes: AllQuality 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. 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
InterfaceSelect an interface. Telephony OUI VLAN MembershipIf 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 ModeSelect one of the following options: AllQoS attributes are applied on all packets that are classified to the Voice VLAN. Telephony Source MAC AddressQoS attributes are applied only on packets from IP phones.
210
12
Access Port Multicast TV VLAN
VLAN Management
Access Port Multicast TV VLAN
Multicast TV VLANs enable Multicast transmissions to subscribers who are not on the same data VLAN (Layer 2-isolated), without replicating the Multicast transmission frames for each subscriber VLAN. Subscribers, who are not on the same data VLAN (Layer 2-isolated) and are connected to the device with different VLAN ID membership. can share the same Multicast stream by joining the ports to the same Multicast VLAN ID. The network port, connected to the Multicast server, is statically configured as a member in the Multicast VLAN ID. The network ports, which through subscribers communicate with the Multicast server (by sending IGMP messages), receive the Multicast streams from the Multicast server, while including the Multicast TV VLAN in the Multicast packet header. For this reasons, the network ports must be statically configured as the following: Trunk or general port type (see Configuring VLAN Interface Settings) Member on the Multicast TV VLAN
The subscriber receiver ports can be associated with the Multicast TV VLAN only if it is defined in one of the two following types: Access port Customer port (see Customer Port Multicast TV VLAN)
One or more IP Multicast address groups can be associated with the same Multicast TV VLAN. Any VLAN can be configured as a Multicast-TV VLAN. A port assigned to a Multicast-TV VLAN: Joins the Multicast-TV VLAN. Packets passing through egress ports in the Multicast TV VLAN are untagged. The ports Frame Type parameter is set to Admit All, allowing untagged packets (see Configuring VLAN Interface Settings).
The Multicast TV VLAN configuration is defined per port. Customer ports are configured to be member of Multicast TV VLANs using the Multicast TV VLAN Page.
211
VLAN Management
Access Port Multicast TV VLAN
12
IGMP Snooping
Multicast TV VLAN relies on IGMP snooping, which means that: Subscribers use IGMP messages to join or leave a Multicast group. Device performs IGMP snooping and configures the access port according to its Multicast membership on Multicast TV VLAN.
The device decides for each IGMP packet that is received on an access port whether to associate it with the access VLAN or with the Multicast TV VLAN according to the following rules: If an IGMP message is received on an access port, with destination Multicast IP address that is associated with the ports Multicast TV VLAN, then the software associates the IGMP packet with the Multicast TV VLAN. Otherwise the IGMP message is associated to the access VLAN and the IGMP message is only forwarded within that VLAN. The IGMP message is discarded if: The STP/RSTP state on the access port is discard. The MSTP state for the access VLAN is discard. The MSTP state for the Multicast TV VLAN is discard, and the IGMP message is associated with this Multicast TV VLAN.
Group registration
212
12
Regular VLAN Receiver ports VLAN can be used to both send and receive traffic (both Multicast and Unicast). Receivers of same multicast stream are on the same data VLAN and can communicate with each other
VLAN Management
Access Port Multicast TV VLAN
Multicast TV VLAN Multicast VLAN can only be used to receive traffic by the stations on the port (only Multicast). Receivers of same multicast stream are in different Access VLANs and isolated from each other
Configuration
Workflow
Configure TV VLAN with the following steps: 1. Define a TV VLAN by associating a Multicast group to a VLAN (using the Multicast Group to VLAN page). 2. Specify the access ports in each Multicast VLAN (using the Port Multicast VLAN Membership page.
VLAN. The following fields are displayed: Multicast GroupIP address of the Multicast group. Multicast TV VLANVLAN to which the Multicast packets are assigned.
STEP 2 Click Add to associate a Multicast group to a VLAN. Any VLAN can be selected.
Configuration file.
213
VLAN Management
Customer Port Multicast TV VLAN
12
Membership.
STEP 2 Select a VLAN from the Multicast TV VLAN field. STEP 3 The Candidate Access Ports list contains all access ports configured on the
device. Move the required ports from the Candidate Access Ports field to the Member Access Ports field.
STEP 4 Click Apply. Multicast TV VLAN settings are modified, and written to the Running
Configuration file.
The triple play service is provisioned for service provider subscribers, while keeping Layer 2-isolation between them. Each subscriber has a CPE MUX box. The MUX has multiple access ports that are connected to the subscriber's devices (PC, telephone and so on), and one network port that is connected to the access device. The box forwards the packets from the network port to the subscriber's devices based on the VLAN tag of the packet. Each VLAN is mapped to one of the MUX access ports. Packets from subscribers to the service provider network are forwarded as VLAN tagged frames, in order to distinguish between the service types, which mean that for each service type there is a unique VLAN ID in the CPE box.
214
12
VLAN Management
Customer Port Multicast TV VLAN
All packets from the subscriber to the service provider network are encapsulated by the access device with the subscribers VLAN configured as customer VLAN (Outer tag or S-VID), except for IGMP snooping messages from the TV receivers, which are associated with the Multicast TV VLAN. VOD information that is also sent from the TV receivers are sent like any other type of traffic. Packets from the service provider network that received on the network port to the subscriber are sent on the service provider network as double tag packets, while the outer tag (Service Tag or S-Tag) represent one of the two type of VLAN as following: Subscribers VLAN (Includes Internet and IP Phones) Multicast TV VLAN
The inner VLAN (C-Tag) is the tag that determines the destination in the subscribers network (by the CPE MUX).
Workflow
1. Configure an access port as a customer port (using the VLAN Management > Interface Settings page). See QinQ for more information. 2. Configure the network port as a trunk or general port with subscriber and Multicast TV VLAN as tagged VLANS. (using the VLAN Management > Interface Settings page. 3. Create a Multicast TV VLAN with up to 4094 different VLAN(s). (The VLAN creation is done via the regular VLAN management configuration) 4. Associate the customer port to a Multicast TV VLAN, using the Port Multicast VLAN Membership page. 5. Map the CPE VLAN (C-TAG) to the Multicast TV VLAN (S-Tag), using the CPE VLAN to VLAN page.
215
VLAN Management
Customer Port Multicast TV VLAN
12
VLAN.
STEP 2 Click Add. STEP 3 Enter the following fields:
CPE VLANEnter the VLAN defined on the CPE box. Multicast TV VLANSelect the Multicast TV VLAN which is mapped to the CPE VLAN.
STEP 4 Click Apply. CPE VLAN Mapping is modified, and written to the Running
Configuration file.
216
12
VLAN Management
Customer Port Multicast TV VLAN
217
13
Spanning Tree
This section describes the Spanning Tree Protocol (STP) (IEEE802.1D and IEEE802.1Q) and covers the following topics: STP Flavors Configuring STP Status and Global Settings Defining Spanning Tree Interface Settings Configuring Rapid Spanning Tree Settings Multiple Spanning Tree Defining MSTP Properties Mapping VLANs to a MSTP Instance Defining MSTP Instance Settings Defining MSTP Interface Settings
STP Flavors
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. Loops occur when alternate routes exist between hosts. Loops in an extended network can cause switches to forward traffic indefinitely, resulting in increased traffic load and reduced network efficiency. 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.
218
13
Spanning Tree
Configuring STP Status and Global Settings
The device supports the following Spanning Tree Protocol versions: Classic STP Provides a single path between any two end stations, avoiding and eliminating loops. Rapid STP (RSTP) Detects network topologies to provide faster convergence of the spanning tree. This is most effective when the network topology is naturally tree-structured, and therefore faster convergence might be possible. RSTP is enabled by default. Multiple STP (MSTP) MSTP is based on RSTP. It detects Layer 2 loops, and attempts to mitigate them by preventing the involved port from transmitting traffic. Since loops exist on a per-Layer 2-domain basis, a situation can occur where there is a loop in VLAN A and no loop in VLAN B. If both VLANs are on Port X, and STP wants to mitigate the loop, it stops traffic on the entire port, including VLAN B traffic. MSTP solves this problem by enabling several STP instances, so that it is possible to detect and mitigate loops separately in each instance. By associating instances to VLANs, each instance is associated with the Layer 2 domain on which it performs loop detection and mitigation. This enables a port to be stopped in one instance, such as traffic from VLAN A that is causing a loop, while traffic can remain active in another domain where no loop was seen, such as on VLAN B.
Global Settings: Spanning Tree StateEnable or disable STP on the device. STP Operation ModeSelect an STP mode.
219
Spanning Tree
Configuring STP Status and Global Settings
13
BPDU HandlingSelect how Bridge Protocol Data Unit (BPDU) packets are managed when STP is disabled on the port or the device. BPDUs are used to transmit spanning tree information. FilteringFilters BPDU packets when Spanning Tree is disabled on an interface. FloodingFloods BPDU packets when Spanning Tree is disabled on an interface.
Path Cost Default ValuesSelects 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. ShortSpecifies the range 1 through 65,535 for port path costs. LongSpecifies the range 1 through 200,000,000 for port path costs.
Bridge Settings: PrioritySets 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. Hello TimeSet the interval (in seconds) that a Root Bridge waits between configuration messages. Max AgeSet the interval (in seconds) that the device can wait without receiving a configuration message, before attempting to redefine its own configuration. Forward DelaySet the interval (in seconds) that a bridge remains in a learning state before forwarding packets. For more information, refer to Defining Spanning Tree Interface Settings.
Designated Root: Bridge IDThe bridge priority concatenated with the MAC address of the device. Root Bridge IDThe Root Bridge priority concatenated with the MAC address of the Root Bridge. Root PortThe port that offers the lowest cost path from this bridge to the Root Bridge. (This is significant when the bridge is not the root.) Root Path CostThe cost of the path from this bridge to the root.
220
13
Spanning Tree
Defining Spanning Tree Interface Settings
Topology Changes CountsThe total number of STP topology changes that have occurred. Last Topology ChangeThe time interval that elapsed since the last topology change occurred. The time appears in a days/hours/minutes/ seconds format.
STEP 3 Click Apply. The STP Global settings are written to the Running Configuration file.
InterfaceSelect the Port or LAG on which Spanning Tree is configured. STPEnables or disables STP on the port. Edge PortEnables 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: EnableEnables Fast Link immediately. AutoEnables Fast Link a few seconds after the interface becomes active. This allows STP to resolve loops before enabling Fast Link. DisableDisables Fast Link.
NOTE It is recommended to set the value to Auto so that the device sets
the port to fast link mode if a host is connected to it, or sets it as a regular STP port if connected to another device. This helps avoid loops.
221
Spanning Tree
Defining Spanning Tree Interface Settings
13
Root GuardEnables or disables Root Guard on the device. The Root Guard option provides a way to enforce the root bridge placement in the network. Root Guard ensures that the port on which this feature is enabled is the designated port. Normally, all root bridge ports are designated ports, unless two or more ports of the root bridge are connected. If the bridge receives superior BPDUs on a Root Guard-enabled port, Root Guard moves this port to a root-inconsistent STP state. This root-inconsistent state is effectively equal to a listening state. No traffic is forwarded across this port. In this way, Root Guard enforces the position of the root bridge.
BPDU GuardEnables or disables the Bridge Protocol Data Unit (BPDU) Guard feature on the port. The BPDU Guard enables you to enforce the STP domain borders and keep the active topology predictable. The devices behind the ports that have BPDU Guard enabled cannot influence the STP topology. At the reception of BPDUs, the BPDU guard operation disables the port that has BPDU configured. In this case, a BPDU message is received, and an appropriate SNMP trap is generated.
BPDU HandlingSelect how BPDU packets are managed when STP is disabled on the port or the device. BPDUs are used to transmit spanning tree information. Use Global SettingsSelect to use the settings defined in the STP Status and Global Settings page. FilteringFilters BPDU packets when Spanning Tree is disabled on an interface. FloodingFloods BPDU packets when Spanning Tree is disabled on an interface.
Path CostSet the port contribution to the root path cost or use the default cost generated by the system. PrioritySet 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 from 0 to 240, set in increments of 16. Port StateDisplays the current STP state of a port. DisabledSTP is currently disabled on the port. The port forwards traffic while learning MAC addresses.
222
13
Spanning Tree
Configuring Rapid Spanning Tree Settings
BlockingThe port is currently blocked, and cannot forward traffic (with the exception of BPDU data) or learn MAC addresses. ListeningThe port is in Listening mode. The port cannot forward traffic, and cannot learn MAC addresses. LearningThe port is in Learning mode. The port cannot forward traffic, but it can learn new MAC addresses. ForwardingThe port is in Forwarding mode. The port can forward traffic and learn new MAC addresses.
Designated Bridge IDDisplays the bridge priority and the MAC address of the designated bridge. Designated Port IDDisplays the priority and interface of the selected port. Designated CostDisplays 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. Forward TransitionsDisplays the number of times the port has changed from the Blocking state to Forwarding state. SpeedDisplays the speed of the port. LAGDisplays the LAG to which the port belongs. If a port is a member of a LAG, the LAG settings override the port settings.
STEP 4 Click Apply. The interface settings are written to the Running Configuration file.
223
Spanning Tree
Configuring Rapid Spanning Tree Settings
13
page appears:
STEP 3 Select a port. NOTE Activate Protocol Migration is only available after selecting the port
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 5 Select an interface, and click Edit. STEP 6 Enter the parameters
InterfaceSet the interface, and specify the port or LAG where RSTP is to be configured. Point to Point Administrative StatusDefine the point-to-point link status. Ports defined as Full Duplex are considered Point-to-Point port links. -
EnableThis port is an RSTP edge port when this feature is enabled, and
is brought to Forwarding mode quickly (usually within 2 seconds).
Point to Point Operational StatusDisplays the Point-to-Point operational status if the Point to Point Administrative Status is set to Auto. RoleDisplays the role of the port that was assigned by STP to provide STP paths. The possible roles are: -
224
13
-
Spanning Tree
Configuring Rapid Spanning Tree Settings
ModeDisplays the current Spanning Tree mode: Classic STP or RSTP. Fast Link Operational StatusDisplays whether the Fast Link (Edge Port) is enabled, disabled, or automatic for the interface. The values are: -
EnabledFast Link is enabled. DisabledFast Link is disabled. AutoFast Link mode is enabled a few seconds after the interface
becomes active.
DisabledSTP is currently disabled on the port. BlockingThe port is currently blocked, and it cannot forward traffic or
learn MAC addresses.
ForwardingThe port is in Forwarding mode. The port can forward traffic and learn new MAC addresses.
225
Spanning Tree
Multiple Spanning Tree
13
Multiple Spanning Tree Protocol (MSTP) is used to separate the STP port state between various domains (on different VLANs). For example, while port A is blocked in one STP instance due to a loop on VLAN A, the same port can be placed in the Forwarding State in another STP instance. The MSTP Properties page enables you to define the global MSTP settings. To configure MSTP: 1. Set the STP Operation Mode to MSTP as described in the Configuring STP Status and Global Settings page. 2. Define MSTP instances. Each MSTP instance calculates and builds a loop free topology to bridge packets from the VLANs that map to the instance. Refer to the Mapping VLANs to a MSTP Instance section. 3. Decide which MSTP instance be active in what VLAN, and associate these MSTP instances to VLAN(s) accordingly. 4. Configure the MSTP attributes by: Defining MSTP Properties Defining MSTP Instance Settings Mapping VLANs to a MSTP Instance
13
Spanning Tree
Mapping VLANs to a MSTP Instance
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 VLAN to MST Instance page. Use this page if the system operates in MSTP mode. To define MSTP:
STEP 1 Click Spanning Tree > STP Status and Global Settings. Enable MSTP. STEP 2 Click Spanning Tree > MSTP Properties. STEP 3 Enter the parameters.
Region NameDefine an MSTP region name. RevisionDefine an unsigned 16-bit number that identifies the revision of the current MST configuration. The field range is from 0 to 65535. Max HopsSet 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 from 1 to 40. IST MasterDisplays the regions master.
STEP 4 Click Apply. The MSTP properties are defined, and the Running Configuration file
is updated.
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 seven MST instances (predefined from 1-7) can be defined on 300 Series switches, in addition to instance zero.
227
Spanning Tree
Defining MSTP Instance Settings
13
For those VLANs that are not 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:
STEP 1 Click Spanning Tree > VLAN to MSTP Instance.
The VLAN to MSTP Instance page contains the following fields: MST Instance IDAll MST instances are displayed. VLANsAll 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.
MST Instance IDSelect the MST instance. VLANsDefine the VLANs being mapped to this MST instance. ActionDefine 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
228
13
Spanning Tree
Defining MSTP Interface Settings
Included VLANDisplays 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 PrioritySet the priority of this bridge for the selected MST instance. Designated Root Bridge IDDisplays the priority and MAC address of the Root Bridge for the MST instance. Root PortDisplays the root port of the selected instance. Root Path CostDisplays the root path cost of the selected instance. Bridge IDDisplays the bridge priority and the MAC address of this device for the selected instance. Remaining HopsDisplays the number of hops remaining to the next destination.
STEP 3 Click Apply. The MST Instance configuration is defined, and the Running
Instance equals ToSelect the MSTP instance to be configured. Interface Type equals toSelect whether to display the list of ports or LAGs.
STEP 3 Click Go. The MSTP parameters for the interfaces on the instance are displayed. STEP 4 Select an interface, and click Edit .
229
Spanning Tree
Defining MSTP Interface Settings
13
Instance IDSelect the MST instance to be configured. InterfaceSelect the interface for which the MSTI settings are to be defined. Interface PrioritySet the port priority for the specified interface and MST instance. Path CostSet the port contribution to the root path cost or use the default value. Port StateDisplays the MSTP status of the specific port on a specific MST instance. The parameters are defined as: DisabledSTP is currently disabled. BlockingThe port on this instance is currently blocked, and cannot forward traffic (with the exception of BPDU data) or learn MAC addresses. ListeningThe port on this instance is in Listening mode. The port cannot forward traffic, and cannot learn MAC addresses. LearningThe port on this instance is in Learning mode. The port cannot forward traffic, but it can learn new MAC addresses. ForwardingThe port on this instance is in Forwarding mode. The port can forward traffic and learn new MAC addresses.
Port RoleDisplays the port or LAG role, per port or LAG per instance, assigned by the MSTP algorithm to provide STP paths: RootForwarding packets through this interface provides the lowest cost path for forwarding packets to the root device. DesignatedThe 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. AlternateThe interface provides an alternate path to the root device from the root interface.
230
13
-
Spanning Tree
Defining MSTP Interface Settings
BackupThe 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. DisabledThe interface does not participate in the Spanning Tree.
ModeDisplays the current Spanning Tree mode. Classic STPClassic STP is enabled on the port. Rapid STPRapid STP is enabled on the port. MSTPMSTP is enabled on the port.
TypeDisplays the MST type of the port. BoundaryA Boundary port attaches MST bridges to a LAN in a remote region. If the port is a boundary port, it also indicates whether the device on the other side of the link is working in RSTP or STP mode. InternalThe port is an internal port.
Designated Bridge IDDisplays the ID number of the bridge that connects the link or shared LAN to the root. Designated Port IDDisplays the Port ID number on the designated bridge that connects the link or the shared LAN to the root. Designated CostDisplays 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. Remaining HopsDisplays the hops remaining to the next destination. Forward TransitionsDisplays the number of times the port has changed from the Forwarding state to the Blocking state.
231
14
Managing MAC Address Tables
This section describe how to add MAC addresses to the system. It covers the following topics: Configuring Static MAC Addresses Managing Dynamic MAC Addresses Defining Reserved MAC Addresses
232
14
Configuring Static MAC Addresses
Static MAC addresses are assigned to a specific physical interface and VLAN on the device. If that address is detected on another interface, it is ignored, and is not written to the address table. To define a static address:
STEP 1 Click MAC Address Tables > Static Addresses.
The Static Addresses page contains the currently defined static addresses.
STEP 2 Click Add. STEP 3 Enter the parameters.
VLAN IDSelect the VLAN ID for the port. MAC AddressEnter the interface MAC address. InterfaceSelect an interface (port, or LAG) for the entry. StatusSelect how the entry is treated. The options are: PermanentThe system never removes this MAC address. If the static MAC address is saved in the Startup Configuration, it is retained after rebooting. Delete on resetThe static MAC address is deleted when the device is reset. Delete on timeoutThe MAC address is deleted when aging occurs. SecureThe MAC address is secure when the interface is in classic locked mode (see Configuring Port Security).
233
14
and twice that value minus 1. For example, if you entered 300 seconds, the aging time is between 300 and 599 seconds.
STEP 3 Click Apply. The aging time is updated.
VLAN IDEnter the VLAN ID for which the table is queried. MAC AddressEnter the MAC address for which the table is queried. InterfaceSelect the interface for which the table is queried. The query can search for specific unit/slot, ports, or LAGs.
STEP 3 Enter the Dynamic Address Table Sort Key field by which the table is sorted. The
displayed. To delete all of the dynamic MAC addresses. click Clear Table.
234
14
Defining Reserved MAC Addresses
When the device receives a frame with a Destination MAC address that belongs to a reserved range (per the IEEE standard), the frame can be discarded or bridged. The entry in the Reserved MAC Address Table can either specify the reserved MAC address or the reserved MAC address and a frame type: To add an entry for a reserved MAC address:
STEP 1 Click MAC Address Tables > Reserved MAC Addresses. The Reserved MAC
MAC AddressSelect the MAC address to be reserved. Frame TypeSelect a frame type based on the following criteria: -
ActionSelect one of the following actions to be taken upon receiving a packet that matches the selected criteria: -
235
15
Multicast
This section describes the Multicast Forwarding feature, and covers the following topics: Multicast Forwarding Defining Multicast Properties Adding MAC Group Address Adding IP Multicast Group Addresses Configuring IGMP Snooping MLD Snooping Querying IGMP/MLD IP Multicast Group Defining Multicast Router Ports Defining Forward All Multicast Defining Unregistered Multicast Settings
Multicast Forwarding
Multicast forwarding enables one-to-many information dissemination. Multicast applications are useful for dissemination of information to multiple clients, where clients do not require reception of the entire content. A typical application is a cable-TV-like service, where clients can join a channel in the middle of a transmission, and leave before it ends. The data is sent only to relevant ports. Forwarding the data only to the relevant ports conserves bandwidth and host resources on links.
236
15
Send and receive Multicast packets.
Multicast
Multicast Forwarding
For Multicast forwarding to work across IP subnets, nodes, and routers must be Multicast-capable. A Multicast-capable node must be able to:
Register the Multicast addresses being listened to by the node with local routers, so that local and remote routers can route the Multicast packet to the nodes.
this section is mostly for IGMP, it also describes coverage of MLD where implied. These queries reach the device, which in turn floods the queries to the VLAN, and also learns the port where there is a Multicast router (Mrouter). When a host receives the IGMP query message, it responds with an IGMP Join message saying that the host wants to receive a specific Multicast stream and optionally from a specific source. The device with the IGMP snooping analyzes the Join messages, and learns that the Multicast stream the host has requested must be forwarded to this specific port. It then forwards the IGMP Join to the Mrouter only. Similarly, when the Mrouter receives an IGMP Join message, it learns the interface from which it received the Join messages that wants to receive a specific Multicast stream. The Mrouter forwards the requested Multicast stream to the interface. In a Layer 2 Multicast service, a Layer 2 switch receives a single frame addressed to a specific Multicast address. It creates copies of the frame to be transmitted on each relevant port. When the device is IGMP/MLD-snooping-enabled and receives a frame for a Multicast stream, it forwards the Multicast frame to all the ports that have registered to receive the Multicast stream using IGMP Join messages.
237
Multicast
Multicast Forwarding
15
The device can forward Multicast streams based on one of the following options: Multicast MAC Group Address IP Multicast Group Address (G) A combination of the source IP address (S) and the destination IP Multicast Group Address (G) of the Multicast packet.
One of these options can be configured per VLAN. The system maintains lists of Multicast groups for each VLAN, and this manages the Multicast information that each port should receive. The Multicast groups and their receiving ports can be configured statically or learned dynamically using IGMP or Multicast Listener Discovery (MLD) protocols snooping. Multicast registration is the process of listening and responding to Multicast registration protocols. The available protocols are IGMP for IPv4 and MLD for IPv6. When IGMP/MLD snooping is enabled in a device on a VLAN, it analyzes the IGMP/ MLD packets it receives from the VLAN connected to the device and Multicast routers in the network. When a device learns that a host is using IGMP/MLD messages to register to receive a Multicast stream, optionally from a specific source, the device adds the registration to its Multicast Forwarding Data Base (MFDB). IGMP/MLD snooping can effectively reduce Multicast traffic from streaming bandwidth-intensive IP applications. A device using IGMP/MLD snooping only forwards Multicast traffic to the hosts interested in that traffic. This reduction of Multicast traffic reduces the packet processing at the device, and also reduces the workload of the end hosts, since they do not have to receive and filter all of the Multicast traffic generated in the network. The following versions are supported: IGMP v1/v2/ v3 MLD v1/v2 A simple IGMP Snooping Querier
An IGMP Querier is required to facilitate the IGMP protocol on a given subnet. In general, a Multicast router is also an IGMP Querier. When there are multiple IGMP Queriers in a subnet, the queriers elect a single querier as the primary querier. The device can be configured to be an IGMP Querier as a backup querier, or in situation where a regular IGMP Querier does not exist. The device is not a full capability IGMP Querier.
238
15
Multicast
Defining Multicast Properties
If the device is enabled as an IGMP Querier, it starts after 60 seconds have passed with no IGMP traffic (queries) detected from a Multicast router. In the presence of other IGMP Queriers, the device might (or might not) stop sending queries, based on the results of the standard querier selection process.
239
Multicast
Defining Multicast Properties
15
A common way of representing Multicast membership is the (S,G) notation where S is the (single) source sending a Multicast stream of data, and G is the IPv4 or IPv6 group address. If a Multicast client can receive Multicast traffic from any source of a specific Multicast group, this is saved as (*,G). The following are ways of forwarding Multicast frames: MAC Group AddressBased on the destination MAC address in the Ethernet frame.
NOTE As mentioned before, one or more IP Multicast group addresses
can be mapped to a MAC group address. Forwarding, based on the MAC group address, can result in an IP Multicast stream being forwarded to ports that have no receiver for the stream. IP Group AddressBased on the destination IP address of the IP packet (*,G). Source Specific IP Group AddressBased on both the destination IP address and the source IP address of the IP packet (S,G).
By selecting the forwarding mode, you can define the method used by hardware to identify Multicast flow by one of the following options: MAC Group Address, IP Group Address, or Source Specific IP Group Address. (S,G) is supported by IGMPv3 and MLDv2, while IGMPv1/2 and MLDv1 support only (*.G), which is just the group ID. The device supports a maximum of 256 static and dynamic Multicast group addresses. To enable Multicast filtering, and select the forwarding method:
STEP 1 Click Multicast > Properties. STEP 2 Enter the parameters.
Bridge Multicast Filtering StatusSelect to enable filtering. VLAN IDSelect the VLAN ID to set its forwarding method. Forwarding Method for IPv6Set one of the following forwarding methods for IPv6 addresses: MAC Group Address, IP Group Address, or Source Specific IP Group Address. Forwarding Method for IPv4Set one of the following forwarding methods for IPv4 addresses: MAC Group Address, IP Group Address, or Source Specific IP Group Address.
240
15
STEP 3 Click Apply. The Running Configuration file is updated.
Multicast
Adding MAC Group Address
For viewing the forwarding information when the mode is IP Address Group or IP and Source Group, use the IP Multicast Group Address page. To define and view MAC Multicast groups:
STEP 1 Click Multicast > MAC Group Address. STEP 2 Enter the parameters.
VLAN ID Equals ToSet the VLAN ID of the group to be displayed. MAC Group Address Equals ToSet the MAC address of the Multicast group to be displayed. If no MAC Group Address is specified, the page contains all the MAC Group Addresses from the selected VLAN.
STEP 3 Click Go, and the MAC Multicast group addresses are displayed in the lower
block.
241
Multicast
Adding MAC Group Address
15
Entries that were created both in this page and in the IP Multicast Group Address page are displayed. For those created in the IP Multicast Group Address page, the IP addresses are converted to MAC addresses.
STEP 4 Click Add to add a static MAC Group Address. STEP 5 Enter the parameters.
VLAN IDDefines the VLAN ID of the new Multicast group. MAC Group AddressDefines the MAC address of the new Multicast group.
STEP 6 Click Apply, the MAC Multicast group is saved to the Running Configuration file.
To configure and display the registration for the interfaces within the group, select an address, and click Details. The page contains: VLAN IDThe VLAN ID of the Multicast group. MAC Group AddressThe MAC address of the group.
STEP 7 Select the port or LAG to be displayed from the Filter: Interface Type menu. STEP 8 Click Go to display the port or LAG membership. STEP 9 Select the way that each interface is associated with the Multicast group:
StaticAttaches the interface to the Multicast group as a static member. DynamicIndicates that the interface was added to the Multicast group as a result of IGMP/MLD snooping. ForbiddenSpecifies that this port is not allowed to join this group on this VLAN. NoneSpecifies that the port is not currently a member of this Multicast group on this VLAN.
STEP 10 Click Apply, and the Running Configuration file is updated. NOTE Entries that were created in the IP Multicast Group Address page
242
15
Adding IP Multicast Group Addresses
Multicast
Adding IP Multicast Group Addresses
The IP Multicast Group Address page is similar to the MAC Group Address page except that Multicast groups are identified by IP addresses. The IP Multicast Group Address page enables querying and adding IP Multicast groups. To define and view IP Multicast groups:
STEP 1 Click Multicast > IP Multicast Group Address .
The page contains all of the IP Multicast group addresses learned by snooping.
STEP 2 Enter the parameters required for filtering.
VLAN ID equals toDefine the VLAN ID of the group to be displayed. IP Version equals toSelect IPv6 or IPv4. IP Multicast Group Address equals toDefine the IP address of the Multicast group to be displayed. This is only relevant when the Forwarding mode is (S,G). Source IP Address equals toDefine the source IP address of the sending device. If mode is (S,G), enter the sender S. This together with the IP Group Address is the Multicast group ID (S,G) to be displayed. If mode is (*.G), enter an * to indicate that the Multicast group is only defined by destination.
STEP 3 Click Go. The results are displayed in the lower block. When Bonjour and IGMP are
enabled on the device in Layer 2 system mode, the IP Multicast address of Bonjour appears. Click Go. The results are displayed in the lower block.
STEP 4 Click Add to add a static IP Multicast Group Address. STEP 5 Enter the parameters.
VLAN IDDefines the VLAN ID of the group to be added. IP VersionSelect the IP address type. IP Multicast Group AddressDefine the IP address of the new Multicast group. Source SpecificIndicates that the entry contains a specific source, and adds the address in the IP Source Address field. If not, the entry is added as a (*,G) entry, an IP group address from any IP source.
243
Multicast
Configuring IGMP Snooping
15
IP Source AddressDefines the source address to be included.
STEP 6 Click Apply. The IP Multicast group is added, and the device is updated. STEP 7 To configure and display the registration of an IP group address, select an address
and click Details. The VLAN ID, IP Version, IP Multicast Group Address, and Source IP Address selected are displayed as read-only in the top of the window. You can select the filter type: Interface Type equals toSelect whether to display ports or LAGs.
STEP 8 For each interface, select its association type. The options are as follows:
StaticAttaches the interface to the Multicast group as a static member. ForbiddenSpecifies that this port is forbidden from joining this group on this VLAN. NoneIndicates that the port is not currently a member of this Multicast group on this VLAN. This is selected by default until Static or Forbidden is selected.
244
15
Multicast
Configuring IGMP Snooping
When IGMP Snooping is enabled globally or on a VLAN, all IGMP packets are forwarded to the CPU. The CPU analyzes the incoming packets, and determines the following: Which ports are asking to join which Multicast groups on what VLAN. Which ports are connected to Multicast routers (Mrouters) that are generating IGMP queries. Which ports are receiving PIM, DVMRP, or IGMP query protocols.
These are displayed on the IGMP Snooping page. Ports, asking to join a specific Multicast group, issue an IGMP report that specifies which group(s) the host wants to join. This results in the creation of a forwarding entry in the Multicast Forwarding Data Base. The IGMP Snooping Querier is used to support a Layer 2 Multicast domain of snooping switches in the absence of a Multicast router. For example, where Multicast content is provided by a local server, but the router (if one exists) on that network does not support Multicast. The speed of IGMP Querier activity must be aligned with the IGMP-snoopingenabled switches. Queries must be sent at a rate that is aligned to the snooping table aging time. If queries are sent at a rate lower than the aging time, the subscriber cannot receive the Multicast packets. This is performed in the IGMP Snooping Edit page. To enable IGMP Snooping and identify the device as an IGMP Snooping Querier on a VLAN:
STEP 1 Click Multicast > IGMP Snooping. STEP 2 Enable or disable the IGMP Snooping status.
When IGMP Snooping is enabled globally, the device monitoring network traffic can determine which hosts have requested to receive Multicast traffic. The device only performs IGMP Snooping if both IGMP snooping and Bridge Multicast filtering are enabled.
STEP 3 Select a VLAN, and click Edit .
245
Multicast
Configuring IGMP Snooping
15
There can be only one IGMP Querier in a network. The device supports standards-based IGMP Querier election. Some of the values of the operational parameters of this table are sent by the elected querier. The other values are derived from the device.
VLAN IDSelect the VLAN ID on which IGMP snooping is defined. IGMP Snooping StatusEnable or disable the monitoring of network traffic for the selected VLAN. Operational IGMP Snooping StatusDisplays the current status of the IGMP Snooping for the selected VLAN. MRouter Ports Auto LearnEnable or disable auto learning of the ports to which the Mrouter is connected. Query RobustnessEnter the Robustness Variable value to be used if this device is the elected querier. Operational Query RobustnessDisplays the robustness variable sent by the elected querier. Query IntervalEnter the interval between the General Queries to be used if this device is the elected querier. Operational Query IntervalThe time interval in seconds between General Queries sent by the elected querier. Query Max Response IntervalEnter the delay used to calculate the Maximum Response Code inserted into the periodic General Queries. Operational Query Max Response IntervalDisplays the Query Max Response Interval included in the General Queries sent by the elected querier. Last Member Query CounterEnter the number of IGMP Group-Specific Queries sent before the device assumes there are no more members for the group, if the device is the elected querier. Operational Last Member Query CounterDisplays the operational value of the Last Member Query Counter. Last Member Query IntervalEnter the Maximum Response Delay to be used if the device cannot read Max Response Time value from groupspecific queries sent by the elected querier.
246
15
Multicast
MLD Snooping
Operational Last Member Query IntervalDisplays the Last Member Query Interval sent by the elected querier. Immediate LeaveEnable Immediate Leave to decrease the time it takes to block a Multicast stream sent to a member port when an IGMP Group Leave message is received on that port. IGMP Querier StatusEnable or disable the IGMP Querier. Administrative Querier Source IP AddressSelect the source IP address of the IGMP Querier. This can be the IP address of the VLAN or it can be the management IP address. Operational Querier Source IP AddressDisplays the source IP address of the elected querier. IGMP Querier VersionSelect the IGMP version used if the device becomes the elected querier. Select IGMPv3 if there are switches and/or Multicast routers in the VLAN that perform source-specific IP Multicast forwarding.
MLD Snooping
Hosts use the MLD protocol to report their participation in Multicast sessions, and the device uses MLD snooping to build Multicast membership lists. It uses these lists to forward Multicast packets only to device ports where there are host nodes that are members of the Multicast groups. The device does not support MLD Querier. Hosts use the MLD protocol to report their participation in Multicast sessions. The device supports two versions of MLD snooping: MLDv1 snooping detects MLDv1 control packets, and sets up traffic bridging, based on IPv6 destination Multicast addresses. MLDv2 snooping uses MLDv2 control packets to forward traffic based on the source IPv6 address, and the destination IPv6 Multicast address.
The actual MLD version is selected by the Multicast router in the network.
247
Multicast
MLD Snooping
15
In an approach similar to IGMP snooping, MLD frames are snooped as they are forwarded by the device from stations to an upstream Multicast router and vice versa. This facility enables a device to conclude the following: On which ports stations interested in joining a specific Multicast group are located On which ports Multicast routers sending Multicast frames are located
This knowledge is used to exclude irrelevant ports (ports on which no stations have registered to receive a specific Multicast group) from the forwarding set of an incoming Multicast frame. If you enable MLD snooping in addition to the manually-configured Multicast groups, the result is a union of the Multicast groups and port memberships derived from the manual setup and the dynamic discovery by MLD snooping. Only static definitions are preserved when the system is rebooted. To enable MLD Snooping:
STEP 1 Click Multicast > MLD Snooping. STEP 2 Enable or disable MLD Snooping Status. When MLD Snooping is globally
enabled, the device monitoring network traffic can determine which hosts have requested to receive Multicast traffic. The device performs MLD Snooping only if both MLD snooping and Bridge Multicast filtering are enabled.
STEP 3 Select a VLAN, and click Edit . STEP 4 Enter the parameters.
VLAN IDSelect the VLAN ID. MLD Snooping StatusEnable or disable MLD snooping on the VLAN. The device monitors network traffic to determine which hosts have asked to be sent Multicast traffic. The device performs MLD snooping only when MLD snooping and Bridge Multicast filtering are both enabled Operational MLD Snooping StatusDisplays the current status of MLD Snooping for the selected VLAN. MRouter Ports Auto-LearnEnable or disable Auto Learn for the Multicast router. Query RobustnessEnter the Robustness Variable value to be used if the device cannot read this value from messages sent by the elected querier.
248
15
Multicast
Querying IGMP/MLD IP Multicast Group
Operational Query RobustnessDisplays the robustness variable sent by the elected querier. Query IntervalEnter the Query Interval value to be used by the device if the device cannot derive the value from the messages sent by the elected querier. Operational Query IntervalThe time interval in seconds between General Queries received from the elected querier. Query Max Response IntervalEnter Query Max Response delay to be used if the device cannot read the Max Response Time value from General Queries sent by the elected querier. Operational Query Max Response IntervalDisplays the delay used to calculate the Maximum Response Code inserted into the General Queries. Last Member Query CounterEnter the Last Member Query Count to be used if the device cannot derive the value from the messages sent by the elected querier. Operational Last Member Query CounterDisplays the operational value of the Last Member Query Counter. Last Member Query IntervalEnter the Maximum Response Delay to be used if the device cannot read Max Response Time value from GroupSpecific queries sent by the elected querier. Operational Last Member Query IntervalThe Last Member Query Interval sent by the elected querier. Immediate LeaveWhen enabled, reduces the time it takes to block unnecessary MLD traffic sent to a device port.
249
Multicast
Defining Multicast Router Ports
15
There might be a difference between information on this page and, for example, information displayed in the MAC Group Address page. Assuming that the system is in MAC-based groups and a port that requested to join the following Multicast groups 224.1.1.1 and 225.1.1.1, both are mapped to the same MAC Multicast address 01:00:5e:01:01:01. In this case, there is a single entry in the MAC Multicast page, but two entries on this page. To query for a IP Multicast group:
STEP 1 Click Multicast > IGMP/MLD IP Multicast Group. STEP 2 Set the type of snooping group for which to search: IGMP or MLD. STEP 3 Enter some or all of following query filter criteria:
Group Address equals toDefines the Multicast group MAC address or IP address to query. Source Address equals toDefines the sender address to query. VLAN ID equals toDefines the VLAN ID to query.
STEP 4 Click Go. The following fields are displayed for each Multicast group:
VLANThe VLAN ID. Group AddressThe Multicast group MAC address or IP address. Source AddressThe sender address for all of the specified group ports. Included PortsThe list of destination ports for the Multicast stream. Excluded PortsThe list of ports not included in the group. Compatibility ModeThe oldest IGMP/MLD version of registration from the hosts the device receives on the IP group address.
250
15
STEP 1 Click Multicast > Multicast Router Port . STEP 2 Enter some or all of following query filter criteria:
Multicast
Defining Forward All Multicast
VLAN ID equals toSelect the VLAN ID for the router ports that are described. IP Version equals toSelect the IP version that the Multicast router supports. Interface Type equals toSelect whether to display ports or LAGs.
STEP 3 Click Go. The interfaces matching the query criteria are displayed. STEP 4 For each port or LAG, select its association type. The options are as follows:
StaticThe port is statically configured as a Multicast router port. Dynamic(Display only) The port is dynamically configured as a Multicast router port by a MLD/IGMP query. To enable the dynamic learning of Multicast router ports, go to the Multicast > IGMP Snooping page, and the Multicast > MLD Snooping page ForbiddenThis port is not to be configured as a Multicast router port, even if IGMP or MLD queries are received on this port. If Forbidden is enabled on a port, Mrouter is not learned on this port (i.e. MRouter Ports Auto-Learn is not enabled on this port). NoneThe port is not currently a Multicast router port.
251
Multicast
Defining Unregistered Multicast Settings
15
IGMP or MLD messages are not forwarded to ports defined as Forward All.
NOTE The configuration affects only the ports that are members of the selected VLAN.
VLAN ID equals toThe VLAN ID the ports/LAGs are to be displayed. Interface Type equals toDefine whether to display ports or LAGs.
STEP 3 Click Go. The status of all ports/LAGs are displayed. STEP 4 Select the port/LAG that is to be defined as Forward All by using the following
methods: StaticThe port receives all Multicast streams. ForbiddenPorts cannot receive any Multicast streams, even if IGMP/MLD snooping designated the port to join a Multicast group. NoneThe port is not currently a Forward All port.
252
15
Multicast
Defining Unregistered Multicast Settings
You can select a port to receive or filter unregistered Multicast streams. The configuration is valid for any VLAN of which it is a member (or will be a member). This feature ensures that the customer receives only the Multicast groups requested and not others that may be transmitted in the network. To define unregistered Multicast settings:
STEP 1 Click Multicast > Unregistered Multicast . STEP 2 Define the following:
Interface Type equals toThe view as all ports or all LAGs. Port/LAGDisplays the port or LAG ID. Unregistered MulticastDisplays the forwarding status of the selected interface. The possible values are: ForwardingEnables forwarding of unregistered Multicast frames to the selected interface. FilteringEnables filtering (rejecting) of unregistered Multicast frames to the selected interface.
STEP 3 Click Apply. The settings are saved, and the Running Configuration file is updated.
253
16
IP Configuration
IP interface addresses can be configured manually by the user, or automatically configured by a DHCP server. This section provides information for defining the device IP addresses, either manually or by making the device a DHCP client. This section covers the following topics: Overview IPv4 Management and Interfaces IPv6 Management and Interfaces Domain Name
Overview
Some features are only available in Layer 2 or Layer 3 system mode, as described below: In Layer 2 system mode, the device operates as a Layer 2 VLAN-aware device, and has no routing capabilities. In Layer 3 system mode, the device has IP routing capabilities as well as Layer 2 system mode capabilities. In this system mode, a Layer 3 port still retains much of the Layer 2 functionality, such as Spanning Tree Protocol and VLAN membership. In Layer 3 system mode, the device does not support MAC-based VLAN, Dynamic VLAN Assignment, VLAN Rate Limit, SYN Rate DoS Protection, and Advanced QoS Policers. Configuring the device to work in either mode is performed in the Administration > System Settings page.
NOTE Switching from one system mode (layer) to another (on Sx500 devices) requires a
mandatory reboot, and the startup configuration of the device is then deleted.
254
16
Layer 2 IP Addressing
IP Configuration
Overview
In Layer 2 system mode, the device has up to one IPv4 address and up to two IPv6 interfaces (either native interface or Tunnel) in the management VLAN. This IP address and the default gateway can be configured manually, or by DHCP. The static IP address and default gateway for Layer 2 system mode are configured on the IPv4 Interface and IPv6 Interfaces pages. In Layer 2 system mode, the device uses the default gateway, if configured, to communicate with devices that are not in the same IP subnet with the device. By default, VLAN 1 is the management VLAN, but this can be modified. When operating in Layer 2 system mode, the device can only be reached at the configured IP address through its management VLAN. The factory default setting of the IPv4 address configuration is DHCPv4. This means that the device acts as a DHCPv4 client, and sends out a DHCPv4 request during boot up. If the device receives a DHCPv4 response from the DHCPv4 server with an IPv4 address, it sends Address Resolution Protocol (ARP) packets to confirm that the IP address is unique. If the ARP response shows that the IPv4 address is in use, the device sends a DHCPDECLINE message to the offering DHCP server, and sends another DHCPDISCOVER packet that restarts the process. If the device does not receive a DHCPv4 response in 60 seconds, it continues to send DHCPDISCOVER queries, and adopts the default IPv4 address: 192.168.1.254/24. IP address collisions occur when the same IP address is used in the same IP subnet by more than one device. Address collisions require administrative actions on the DHCP server and/or the devices that collide with the device. When a VLAN is configured to use dynamic IPv4 addresses, the device issues DHCPv4 requests until it is assigned an IPv4 address from a DHCPv4 server. In Layer 2 system mode, only the management VLAN can be configured with a static or dynamic IP address. In Layer 3 system mode, all the interface types (ports, LAGs, and/or VLANs) on the device can be configured with a static or dynamic IP address. The IP address assignment rules for the device are as follows: When in Layer 2 system mode, unless the device is configured with a static IP address, it issues DHCPv4 requests until a response is received from the DHCP server. If the IP address on the device is changed, the device issues gratuitous ARP packets to the corresponding VLAN to check IP address collisions. This rule also applies when the device reverts to the default IP address.
Cisco Small Business 300 Series Managed Switch Administration Guide
255
IP Configuration
IPv4 Management and Interfaces
16
The system status LED changes to solid green when a new unique IP address is received from the DHCP server. If a static IP address has been set, the system status LED also changes to solid green. The LED flashes when the device is acquiring an IP address and is currently using the factory default IP address 192.168.1.254. The same rules apply when a client must renew the lease, prior to its expiration date through a DHCPREQUEST message. With factory default settings, when no statically-defined or DHCP-acquired IP address is available, the default IP address is used. When the other IP addresses become available, the addresses are automatically used. The default IP address is always on the management VLAN.
Layer 3 IP Addressing
In Layer 3 system mode, the device can have multiple IP addresses. Each IP address can be assigned to specified ports, LAGs, or VLANs. These IP addresses are configured in the IPv4 Interface and IPv6 Interfaces pages in Layer 3 system mode. This provides more network flexibility than the Layer 2 system mode, in which only a single IP address can be configured. Operating in Layer 3 system mode, the device can be reached at all its IP addresses from the corresponding interfaces. A predefined, default route is not provided in Layer 3 system mode. To remotely manage the device, a default route must be defined. All DHCP-assigned default gateways are stored as default routes. In addition, you can manually define default routes. This is defined in the IPv4 Static Routes and IPv6 Routes pages. All the IP addresses configured or assigned to the device are referred to as Management IP addresses in this guide. If the pages for Layer 2 and Layer 3 are different, both versions are displayed.
256
16
IP Configuration
IPv4 Management and Interfaces
Management VLANSelect the Management VLAN used to access the device through telnet or the Web GUI. VLAN1 is the default Management VLAN. IP Address TypeSelect one of the following options: -
NOTE DHCP Option 12 (Host Name option) is supported when the device is
an DHCP client. If DHCP Option 12 is received from a DHCP server, it is saved as the servers host name. DHCP option 12 will not be requested by the device. The DHCP server must be configured to send option 12 regardless of what is requested in order to make use of this feature. If a static IP address is used, configure the following fields. IP AddressEnter the IP address, and configure one of the following Mask fields: Network MaskSelect and enter the IP address mask. Prefix LengthSelect and enter the length of the IPv4 address prefix.
Administrative Default GatewaySelect User Defined and enter the default gateway IP address, or select None to remove the selected default gateway IP address from the interface. Operational Default GatewayDisplays the current default gateway status.
NOTE If the device is not configured with a default gateway, it cannot
communicate with other devices that are not in the same IP subnet.
257
IP Configuration
IPv4 Management and Interfaces
16
Renew IP Address NowThe device dynamic IP address can be renewed any time after it is assigned by a DHCP server. Note that depending on your DHCP server configuration, the device might receive a new IP address after the renewal that requires setting the web-based configuration utility to the new IP address. Auto Configuration via DHCPDisplays status of Auto Configuration feature. You can configure this from Administration > File Management > DHCP Auto Configuration.
If a dynamic IP address is retrieved from the DHCP server, select those of the following fields that are enabled:
STEP 3 Click Apply. The IPv4 interface settings are written to the Running Configuration
file.
address configured on a port or LAG. The device takes the first VID that is not used starting from 4094. To configure the IPv4 addresses:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > IPv4 Interface.
This page displays the following fields in the IPv4 Interface Table: InterfaceInterface for which the IP address is defined. IP Address TypeIP address defined as static or DHCP. StaticEntered manually. DHCPReceived from DHCP server.
258
16
MaskConfigured IP address mask.
IP Configuration
IPv4 Management and Interfaces
StatusResults of the IP address duplication check. TentativeThere is no final result for the IP address duplication check. ValidThe IP address collision check was completed, and no IP address collision was detected. Valid-DuplicatedThe IP address duplication check was completed, and a duplicate IP address was detected. DuplicatedA duplicated IP address was detected for the default IP address. DelayedThe assignment of the IP address is delayed for 60 second if DHCP Client is enabled on startup in order to give time to discover DHCP address. Not ReceivedRelevant for DHCP Address. When a DCHP Client starts a discovery process, it assigns a dummy IP address 0.0.0.0 before the real address is obtained. This dummy address has the status of Not Received.
InterfaceSelect Port, LAG, or VLAN as the interface associated with this IP configuration, and select an interface from the list. IP Address TypeSelect one of the following options: -
Dynamic IP AddressReceive the IP address from a DHCP server. Static IP AddressEnter the IP address.
STEP 4 If Static Address was selected, enter the IP Address for this interface. STEP 5 If Static Address was selected, enter one of the following:
file.
Network MaskIP mask for this address. Prefix LengthLength of the IPv4 prefix.
STEP 6 Click Apply. The IPv4 address settings are written to the Running Configuration
259
IP Configuration
IPv4 Management and Interfaces
16
IPv4 Routes
When the device is in Layer 3 system mode, this page enables configuring and viewing IPv4 static routes on the device. When routing traffic, the next hop is decided on according to the longest prefix match (LPM algorithm). A destination IPv4 address may match multiple routes in the IPv4 Static Route Table. The device uses the matched route with the highest subnet mask, that is, the longest prefix match. To define an IP static route:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > IPv4 Routes. STEP 2 Click Add. STEP 3 Enter values for the following fields:
Destination IP PrefixEnter the destination IP address prefix. MaskSelect and enter information for one of the following: Network MaskThe IP route prefix for the destination IP. Prefix LengthThe IP route prefix for the destination IP.
Next Hop Router IP AddressEnter the next hop IP address or IP alias on the route.
NOTE You cannot configure a static route through a directly-connected IP
subnet where the device gets its IP address from a DHCP server. MetricEnter the administrative distance to the next hop. The range is 1 255.
STEP 4 Click Apply. The IP Static route is saved to the Running Configuration file.
260
16
ARP
IP Configuration
IPv4 Management and Interfaces
The device maintains an ARP (Address Resolution Protocol) table for all known devices that reside in the IP subnets directly connected to it. A directly-connected IP subnet is the subnet to which an IPv4 interface of the device is connected. When the device is required to send/route a packet to a local device, it searches the ARP table to obtain the MAC address of the device. The ARP table contains both static and dynamic addresses. Static addresses are manually configured and do not age out. The device creates dynamic addresses from the ARP packets it receives. Dynamic addresses age out after a configured time.
NOTE In Layer 2 mode, the IP, MAC address mapping in ARP Table is used by the device
to forward traffic originated by the device. In Layer 3 mode, the mapping information is used for Layer 3 routing as well as to forward generated traffic. To define the ARP tables:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > ARP. STEP 2 Enter the parameters.
ARP Entry Age OutEnter the number of seconds that dynamic addresses can remain in the ARP table. A dynamic address ages out after the time it is in the table exceeds the ARP Entry Age Out time. When a dynamic address ages out, it is deleted from the table, and only returns when it is relearned. Clear ARP Table EntriesSelect the type of ARP entries to be cleared from the system. -
AllDeletes all of the static and dynamic addresses immediately. DynamicDeletes all of the dynamic addresses immediately. StaticDeletes all of the static addresses immediately. Normal Age OutDeletes dynamic addresses based on the configured
ARP Entry Age Out time.
STEP 3 Click Apply. The ARP global settings are written to the Running Configuration file.
The ARP table displays the following fields: InterfaceThe IPv4 Interface of the directly-connected IP subnet where the IP device resides. IP AddressThe IP address of the IP device. MAC AddressThe MAC address of the IP device.
261
IP Configuration
IPv4 Management and Interfaces
16
StatusWhether the entry was manually entered or dynamically learned.
IP VersionThe IP address format supported by the host. Only IPv4 is supported. VLANIn Layer 2, displays the management VLAN ID. For devices in Layer 2 mode, there is only one directly-connected IP subnet, which is always in the management VLAN. All the static and dynamic addresses in the ARP Table reside in the management VLAN. InterfaceFor devices in Layer 3 system mode, an IPv4 interface can be configured on a port, LAG or VLAN. Select the desired interface from the list of configured IPv4 interfaces on the device.
IP AddressEnter the IP address of the local device. MAC AddressEnter the MAC address of the local device.
STEP 6 Click Apply. The ARP entry is saved to the Running Configuration file.
ARP Proxy
The Proxy ARP technique is used by the device on a given IP subnet to answer ARP queries for a network address that is not on that network.
NOTE The ARP proxy feature is only available when the device is in L3 mode.
The ARP Proxy is aware of the destination of traffic, and offers another MAC address in reply. Serving as an ARP Proxy for another host effectively directs LAN traffic destination to the host. The captured traffic is then typically routed by the Proxy to the intended destination by using another interface, or by using a tunnel. The process in which an ARP-query-request for a different IP address, for proxy purposes, results in the node responding with its own MAC address is sometimes referred to as publishing. To enable ARP Proxy on all IP interfaces:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > ARP Proxy. STEP 2 Select ARP Proxy to enable the device to respond to ARP requests for remotely-
262
16
updated.
IP Configuration
IPv4 Management and Interfaces
STEP 3 Click Apply. The ARP proxy is enabled, and the Running Configuration file is
Helper.
STEP 2 Click Add. STEP 3 Select the Source IP Interface to where the device is to relay UDP Broadcast
packets based on a configured UDP destination port. The interface must be one of the IPv4 interfaces configured on the device.
STEP 4 Enter the UDP Destination Port number for the packets that the device is to relay.
Select a well-known port from the drop-down list, or click the port radio button to enter the number manually.
STEP 5 Enter the Destination IP Address that receives the UDP packet relays. If this field
is 0.0.0.0, UDP packets are discarded. If this field is 255.255.255.255, UDP packets are flooded to all IP interfaces.
STEP 6 Click Apply. The UDP relay settings are written to the Running Configuration file.
DHCPv4 Snooping/Relay
DHCPv4 Snooping
DHCP snooping provides a security mechanism to prevent receiving false DHCP response packets and to log DHCP addresses. It does this by treating ports on the device as either trusted or untrusted.
263
IP Configuration
IPv4 Management and Interfaces
16
A trusted port is a port that is connected to a DHCP server and is allowed to assign DHCP addresses. DHCP messages received on trusted ports are allowed to pass through the device. An untrusted port is a port that is not allowed to assign DHCP addresses. By default, all ports are considered untrusted until you declare them trusted (in the DHCP Snooping Interface Settings page).
DHCPv4 Relay
DHCP Relay relays DHCP packets to the DHCP server.
For regular DHCP Relay: Enable DHCP Relay. No need to enable Option 82 insertion.
Option 82
Option 82 (DHCP Relay Agent Information Option) passes port and agent information to a central DHCP server, indicating where an assigned IP address physically connects to the network. The main goal of option 82 is to help to the DHCP server select the best IP subnet (network pool) from which to obtain an IP address.
Cisco Small Business 300 Series Managed Switch Administration Guide 264
16
IP Configuration
IPv4 Management and Interfaces
The following Option 82 options are available on the device: DHCP Insertion - Add Option 82 information to packets that do not have foreign Option 82 information. DHCP Passthrough - Forward or reject DHCP packets that contain Option 82 information from untrusted ports. On trusted ports, DHCP packets containing Option 82 information are always forwarded.
The following table shows the packet flow through the DHCP Relay, DHCP Snooping, and Option 82 modules: The following cases are possible: DHCP client and DHCP server are connected to the same VLAN. In this case, a regular bridging passes the DHCP messages between DHCP client and DHCP server. DHCP client and DHCP server are connected to different VLANs. In the case, only DHCP Relay can and does broadcast DHCP messages between DHCP client and DHCP server. Unicast DHCP messages are passed by regular routers and therefore if DHCP Relay is enabled on a VLAN without an IP address or if the device is not a router (Layer 2 device) then an external router is needed.
DHCP Relay and only DHCP Relay relays DHCP messages to a DHCP server
265
IP Configuration
IPv4 Management and Interfaces
16
DHCP Relay VLAN with IP Address DHCP Relay VLAN without IP Address Relay inserts Option 82 Bridge no Option 82 is inserted Relay discards the packet Bridge Packet is sent with the original Option 82 Relay discards the packet Bridge Packet is sent with the original Option 82
The following describes how DHCP request packets are handled when both DHCP Snooping and DHCP Relay are enabled: DHCP Relay VLAN with IP Address Packet arrives without Option 82 Option 82 Insertion Disabled Packet is sent without Option 82 Packet arrives with Option 82 Packet is sent with the original Option 82 DHCP Relay VLAN without IP Address Packet arrives without Option 82 Relay inserts Option 82 Bridge no Option 82 is inserted Packet arrives with Option 82 Relay discards the packet Bridge Packet is sent with the original Option 82
266
16
DHCP Relay VLAN with IP Address Option 82 Insertion Enabled Relay is sent with Option 82 Bridge Option 82 is added (if port is trusted, behaves as if DHCP Snooping is not enabled) Packet is sent with the original Option 82
IP Configuration
IPv4 Management and Interfaces
DHCP Relay VLAN without IP Address Relay is sent with Option 82 Bridge Option 82 is inserted (if port is trusted, behaves as if DHCP Snooping is not enabled) Relay discards the packet Bridge Packet is sent with the original Option 82
The following describes how DHCP Reply packets are handled when DHCP Snooping is disabled: DHCP Relay VLAN with IP Address Packet arrives without Option 82 Packet arrives with Option 82 DHCP Relay VLAN without IP Address Packet arrives without Option 82 Packet arrives with Option 82
267
IP Configuration
IPv4 Management and Interfaces
16
DHCP Relay VLAN with IP Address DHCP Relay VLAN without IP Address Relay discards Option 82 Bridge Packet is sent without Option 82 Relay 1. If reply originates in device, packet is sent without Option 82 2. If reply does not originate in device, packet is discarded Bridge Packet is sent with the original Option 82
Relay Packet is sent without Option 82 Bridge Packet is sent with the Option 82
Relay Packet is sent without Option 82 Bridge Packet is sent with the Option 82
268
16
DHCP Relay VLAN with IP Address Packet arrives without Option 82 Option 82 Insertion Disabled Packet is sent without Option 82 Packet arrives with Option 82 Packet is sent with the original Option 82
IP Configuration
IPv4 Management and Interfaces
The following describes how DHCP reply packets are handled when both DHCP Snooping and DHCP Relay are enabled DHCP Relay VLAN without IP Address Packet arrives without Option 82 Relay discards Option 82 Bridge Packet is sent without Option 82 Packet arrives with Option 82
Relay 1. If reply originates on the device, packet is sent without Option 82 2. If reply does not originate on the device, discards the packet Bridge Packet is sent with the original Option 82
269
IP Configuration
IPv4 Management and Interfaces
16
The DHCP Snooping Binding database is also used by IP Source Guard and Dynamic ARP Inspection features to determine legitimate packet sources.
Binding database.
STEP 3 Device forwards DHCPDISCOVER or DHCPREQUEST packets. STEP 4 DHCP server sends DHCPOFFER packet to offer an IP address, DHCPACK to
matches the packet, the device replaces it with IP-MAC binding on receipt of DHCPACK.
270
16
IP Configuration
IPv4 Management and Interfaces
The following summarizes how DHCP packets are handled from both trusted and untrusted ports. The DHCP Snooping Binding database is stored in non-volatile memory. DHCP Snooping Packet Handling Packet Type Arriving from Untrusted Ingress Interface Forward to trusted interfaces only. Filter. Arriving from Trusted Ingress Interface Forwarded to trusted interfaces only. Forward the packet according to DHCP information. If the destination address is unknown the packet is filtered. Forward to trusted interfaces only. Same as DHCPOFFER and an entry is added to the DHCP Snooping Binding database. Same as DHCPOFFER. Remove entry if exists. Forward to trusted interfaces only
DHCPDISCOVER DHCPOFFER
DHCPREQUEST DHCPACK
DHCPNAK DHCPDECLINE
Filter. Check if there is information in the database. If the information exists and does not match the interface on which the message was received, the packet is filtered. Otherwise the packet is forwarded to trusted interfaces only, and the entry is removed from database.
271
IP Configuration
IPv4 Management and Interfaces
16
Arriving from Untrusted Ingress Interface Same as DHCPDECLINE. Forward to trusted interfaces only. Filtered. Arriving from Trusted Ingress Interface Same as DHCPDECLINE. Forward to trusted interfaces only. Forward.
Packet Type
272
16
IP Configuration
IPv4 Management and Interfaces
STEP 1 Enable DHCP Snooping and/or DHCP Relay in the IP Configuration > DHCP >
Properties page or in the Security > DHCP Snooping > Properties page.
STEP 2 Define the interfaces on which DHCP Snooping is enabled in the IP Configuration
DHCP Snooping/Relay
This section describes how the DHCP Relay and Snooping features are implemented via the Web-based interface.
Properties
To configure DHCP Relay, DHCP Snooping and Option 82:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces >
DHCP Snooping/Relay > Properties or Security > DHCP Snooping. Enter the following fields: Option 82Select Option 82 to insert Option 82 information into packets. DHCP RelaySelect to enable DHCP Relay. DHCP Snooping StatusSelect to enable DHCP Snooping. If DHCP Snooping is enabled, the following options can be enabled: -
Verify MAC AddressSelect to verify that the source MAC address of the Layer 2 header matches the client hardware address as appears in the DHCP Header (part of the payload) on DHCP untrusted ports. Backup DatabaseSelect to back up the DHCP Snooping Binding
database on the devices flash memory.
273
IP Configuration
IPv4 Management and Interfaces
16
STEP 2 Click Apply. The settings are written to the Running Configuration file. STEP 3 To define a DHCP server, click Add. STEP 4 Enter the IP address of the DHCP server and click Apply. The settings are written
Interface Settings
In Layer 2, DHCP Relay and Snooping can only be enabled on VLANs with IP addresses. In Layer 3, DHCP Relay and Snooping can be enabled on any interface with an IP address and on VLANs with or without an IP address. To enable DHCP Snooping/Relay on specific interfaces:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > DHCP Snooping/
Snooping.
STEP 4 Click Apply. The settings are written to the Running Configuration file.
274
16
DHCP Snooping Binding Database
IP Configuration
IPv4 Management and Interfaces
See How the DHCP Snooping Binding Database is Built for a description of how dynamic entries are added to the DHCP Snooping Binding database. Note the following points about maintenance of the DHCP Snooping Binding database: The device does not update the DHCP Snooping Binding database when a station moves to another interface. If a port is down, the entries for that port are not deleted. When DHCP Snooping is disabled for a VLAN, the binding entries that were collected for that VLAN are removed. If the database is full, DHCP Snooping continue to forward packets but new entries are not created. Note that if the IP source guard and/or ARP inspection features are active, the clients that are not written in the DHCP Snooping Binding database are not be able to connect to the network.
Relay > DHCP Snooping Binding Database. To see a subset of entries in the DHCP Snooping Binding database, enter the relevant search criteria and click Go.
STEP 2 To add an entry, click Add. STEP 3 Enter the fields:
VLAN IDVLAN on which packet is expected. MAC AddressMAC address of packet. IP AddressIP address of packet. InterfaceUnit/Slot/Interface on which packet is expected. TypeThe possible field values are: -
Lease TimeIf the entry is dynamic, enter the amount of time that the entry is to be active in the DHCP Database. If there is no Lease Time, check Infinite.)
275
IP Configuration
DHCP Server
16
STEP 4 Click Apply. The settings are defined, and the device is updated.
DHCP Server
The DHCPv4 Server feature enables you to configure the device as a DHCPv4 server. A DHCPv4 server is used to assign IPv4 address and other information to another device (DHCP client) The DHCPv4 server allocates IPv4 addresses from a user-defined pool of IPv4 addresses. These can be in the following modes: Static AllocationThe hardware address of a host is manually mapped to an IP address. Dynamic AllocationA client obtains a leased IP address for a specified period of time (that can be infinite). If the DHCP client does not renew the allocated IP Address, the IP address is revoked at the end of this period, and the client must request another IP address.
DHCP Options
The following tables defines DHCP options supported by the DHCP server for which there are dedicated configuration commands, so that they can be referenced by name. Option # 1 3 4 6 12 15 Type of Option Basic Basic Basic Basic Basic Basic Option Name Subnet Mask Router Option Time Server Option Domain Name Server Option Host Name Option Domain Name
276
16
51 44 46 Extension NetBIOS NetBIOS IP Address Lease Time
IP Configuration
DHCP Server
NetBIOS over TCP/IP Name Server Option netbios-name-server NetBIOS over TCP/IP Node Type Option netbios-node-type
The following options can be set with the generic DHCP option CLI command: Integer type: 2, 13, 22, 26, 24, 25, 35, 38 ASCII type: 14, 17, 18, 40, 43, 47, 64 IP Address type: 16, 28, 32 IP List type: 5, 7-11, 21, 33, 41, 42, 45, 48, 49, 65, 69-76
The following table defines DHCP options which are supported by the DHCPv4 server, but cannot be set in the GUI or CLI: Option # 50 53 Option Name Requested IP Address DHCP Message Type Description The option is created by the DHCP client during renew The option specifies the DHCP message type (value - message type): 54 Server Identifier 1 - DHCPDISCOVER 2 - DHCPOFFER 3 - DHCPREQUEST 4 - DHCPDECLINE 5 - DHCPACK 6 - DHCPNAK 7 - DHCPRELEASE 8 - DHCPINFORM
This option, created by the DHCP client, is the IP address of the selected server.
277
IP Configuration
DHCP Server
16
Option # 55 56 58 59 61 Option Name Parameter Request List Message Renewal (T1) Time Value Rebinding (T2) Time Value Client-identifier Description Created by the DHCP client. Contains error text. Hard-coded. Hard-coded. Created by the DHCP client using sysName.
Hosts page.
278
16
can be deleted in this page.
IP Configuration
DHCP Server
STEP 5 View the allocated IP addresses using the Address Binding page. IP addresses
DHCPv4 Server
To configure the device as a DHCPv4 server:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > DHCP Server >
Network Pool
When the device is serving as a DHCP server, one or more pools of IP addresses must be defined, from which the device will allocate IP addresses to clients. Each network pool contains a range of addresses that belong to a specific subnetwork. These addresses are allocated to various clients within that subnet. When a client requests an IP address, the device as DHCP server allocates an IP address according to the following: Directly-attached ClientThe device allocates an address from the network pool whose subnet matches the subnet configured on the devices IP interface from which the DHCP request was received. Remote ClientThe devices takes an IP address from the network pool whose first relay subnet, which is connected directly to the client, matches the subnet configured on one of switches IP interfaces.
Up to eight network pools can be defined. To create a pool of IP addresses, and define their lease durations:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > DHCP Server >
Network Pool to display the Network Pool page. The previously-defined network pools are displayed.
STEP 2 Click Add to define a new network pool. Note that you either enter the Subnet IP
Address and the Mask, or enter the Mask, the Address Pool Start and Address Pool End.
STEP 3 Enter the fields:
279
IP Configuration
DHCP Server
16
Pool NameEnter the pool name. Subnet IP AddressEnter the subnet in which the network pool resides. MaskEnter one of following: Network MaskCheck and enter the pools network mask. Prefix LengthCheck and enter the number of bits that comprise the address prefix.
Address Pool StartEnter the first IP address in the range of the network pool. Address Pool EndEnter the last IP address in the range of the network pool. Lease DurationEnter the amount of time a DHCP client can use an IP address from this pool. You can configure a lease duration of up to 49,710 days or an infinite duration. InfiniteThe duration of the lease is unlimited. DaysThe duration of the lease in number of days. The range is 0 to 49710 days. HoursThe number of hours in the lease. A days value must be supplied before an hours value can be added. MinutesThe number of minutes in the lease. A days value and an hours value must be added before a minutes value can be added.
Default Router IP Address (Option 3) Enter the default router for the DHCP client. Domain Name Server IP Address (Option 6)Select one of the devices DNS servers (if already configured) or select Other and enter the IP address of the DNS server available to the DHCP client. Domain Name (Option 15)Enter the domain name for a DHCP client. NetBIOS WINS Server (Option 44) Enter the NetBIOS WINS name server available to a DHCP client. NetBIOS Node Type (Option 46)Select how to resolve the NetBIOS name. Valid node types are: HybridA hybrid combination of b-node and p-node is used. When configured to use h-node, a computer always tries p-node first and uses b-node only if p-node fails. This is the default.
280
16
-
IP Configuration
DHCP Server
MixedA combination of b-node and p-node communications is used to register and resolve NetBIOS names. M-node first uses b-node; then, if necessary, p-node. M-node is typically not the best choice for larger networks because its preference for b-node Broadcasts increases network traffic. Peer-to-PeerPoint-to-point communications with a NetBIOS name server are used to register and resolve computer names to IP addresses. BroadcastIP Broadcast messages are used to register and resolve NetBIOS names to IP addresses.
SNTP Server IP Address (Option 4) Select one of the devices SNTP servers (if already configured) or select Other and enter the IP address of the time server for the DHCP client. File Server IP Address (siaddr)Enter the IP address of the TFTP/SCP server from which the configuration file is downloaded. File Server Host Name (sname)Enter the name of the TFTP/SCP server. Configuration File Name (file)Enter the name of the file that is used as a configuration file.
Excluded Addresses
By default, the DHCP server assumes that all pool addresses in a pool may be assigned to clients. A single IP address or a range of IP addresses can be excluded. The excluded addresses are excluded from all DHCP pools. To define an excluded address range:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > DHCP Server >
Excluded Addresses to display the Excluded Addresses page. The previously-defined excluded IP addresses are displayed.
STEP 2 To add a range of IP addresses to be excluded, click Add, and enter the fields:
Start IP AddressFirst IP address in the range of excluded IP addresses. End IP AddressLast IP address in the range of excluded IP addresses.
Static Hosts
You might want to assign some DHCP clients a permanent IP address that never changes. This client is then known as a static host.
281
IP Configuration
DHCP Server
16
To manually allocate a permanent IP address to a specific client: Hosts to display the Static Hosts page. The static hosts are displayed.
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > DHCP Server > Static
STEP 2 To add a static host, click Add, and enter the fields:
IP AddressEnter the IP address that was statically assigned to the host. Pool NameEnter the host name, which can be a string of symbols and an integer. MaskEnter the static hosts network mask. Network MaskCheck and enter the static hosts network mask. Prefix LengthCheck and enter the number of bits that comprise the address prefix.
Identifier TypeSet how to identify the specific static host. Client IdentifierEnter a unique identification of the client specified in dotted hexadecimal notation, such as: 01b6.0819.6811.72.
Client NameEnter the name of the static host, using a standard set of ASCII characters. The client name must not include the domain name. Default Router IP Address (Option 3) Enter the default router for the static host. Domain Name Server IP Address (Option 6)Select one of the devices DNS servers (if already configured) or select Other and enter the IP address of the DNS server available to the DHCP client. Domain Name (Option 15)Enter the domain name for the static host. NetBIOS WINS Server (Option 44) Enter the NetBIOS WINS name server available to the static host. NetBIOS Node Type (Option 46)Select how to resolve the NetBIOS name. Valid node types are:
282
16
-
IP Configuration
DHCP Server
HybridA hybrid combination of b-node and p-node is used. When configured to use h-node, a computer always tries p-node first and uses b-node only if p-node fails. This is the default. MixedA combination of b-node and p-node communications is used to register and resolve NetBIOS names. M-node first uses b-node; then, if necessary, p-node. M-node is typically not the best choice for larger networks because its preference for b-node Broadcasts increases network traffic. Peer-to-PeerPoint-to-point communications with a NetBIOS name server are used to register and resolve computer names to IP addresses. BroadcastIP Broadcast messages are used to register and resolve NetBIOS names to IP addresses.
SNTP Server IP Address (Option 4) Select one of the devices SNTP servers (if already configured) or select Other and enter the IP address of the time server for the DHCP client. File Server IP Address (siaddr)Enter the IP address of the TFTP/SCP server from which the configuration file is downloaded. File Server Host Name (sname)Enter the name of the TFTP/SCP server. Configuration File Name (file)Enter the name of the file that is used as a configuration file.
Address Binding
Use the Address Binding page to view and remove the IP addresses allocated by the device and their corresponding MAC addresses. To view and/or remove address bindings:
STEP 1 Click IP Configuration > IPv4 Management and Interfaces > DHCP Server >
Address Binding to display the Address Binding page. The following fields for the address bindings are displayed: IP AddressThe IP addresses of the DHCP clients. Address Type Whether the address of the DHCP client appears as a MAC address or using a client identifier. MAC Address/Client IdentifierA unique identification of the client specified as a MAC Address or in dotted hexadecimal notation, e.g., 01b6.0819.6811.72.
283
IP Configuration
IPv6 Management and Interfaces
16
Lease ExpirationThe lease expiration date and time of the hosts IP address or Infinite is such was the lease duration defined. TypeThe manner in which the IP address was assigned to the client. The possible options are: StaticThe hardware address of the host was mapped to an IP address. DynamicThe IP address, obtained dynamically from the device, is owned by the client for a specified period of time. The IP address is revoked at the end of this period, at which time the client must request another IP address.
StateThe possible options are: AllocatedIP address has been allocated. DeclinedIP address was allocated but not accepted. ExpiredThe lease of the IP address has expired. Pre-AllocatedThe IP address was assigned to a static host.
16
IPv6 Global Configuration
IP Configuration
IPv6 Management and Interfaces
Global Configuration. In Layer 3 system mode, click IP Configuration > IPv6 Management and Interfaces > IPv6 Global Configuration.
STEP 2 Enter values for the following fields:
ICMPv6 Rate Limit IntervalEnter how often the ICMP error messages are generated. ICMPv6 Rate Limit Bucket SizeEnter the maximum number of ICMP error messages that can be sent by the device per interval.
DHCPv6 Client Settings Unique Identifier (DUID) FormatThis is the identifier of the DHCP client that is used by the DHCP server to locate the client. It can be in one of the following formats: Link-Layer(Default). If you select this option, the MAC address of the device is used. Enterprise NumberIf you select this option, enter the following fields.
Enterprise NumberThe vendors registered Private Enterprise number as maintained by IANA. IdentifierThe vendor-defined hex string (up to 64 hex characters). If the number of the character is not even, a zero is added at the right. Each 2 hex characters can be separated by a period or colon. DHCPv6 Unique Identifier (DUID)Displays the identifier selected.
IPv6 Interface
An IPv6 interface can be configured on a port, LAG, VLAN, or tunnel. A tunnel interface is configured with an IPv6 address based on the settings defined in the IPv6 Tunnel page.
285
IP Configuration
IPv6 Management and Interfaces
16
Interfaces. In Layer 3 system mode, click IP Configuration > IPv6 Management and Interfaces > IPv6 Interfaces.
STEP 2 Click Add to add a new interface on which interface IPv6 is enabled. STEP 3 Enter the fields:
IPv6 InterfaceSelect a specific port, LAG, VLAN, or ISATAP tunnel for the IPv6 address.
STEP 4 To configure the interface as a DHCPv6 client, meaning to enable the interface to
receive information from the DHCPv6 server, such as: SNTP configuration and DNS information, enter the DHCPv6 Client fields: StatelessSelect to enable the interface as a stateless DHCPv6 client. Minimum Information Refresh TimeThis value is used to put a floor on the refresh time value. If the server sends a refresh time option that is less than this value, this value is used instead. Select either Infinite (no refresh unless the server sends this option) or User Defined to set a value. Information Refresh TimeThis value indicates how often the device will refresh information received from the DHCPv6 server. If this option is not received from the server, the value entered here is used. Select either Infinite (no refresh unless the server sends this option) or User Defined to set a value.
IPv6 Address Auto ConfigurationSelect to enable automatic address configuration from router advertisements sent by neighbors.
NOTE The device does not support stateful address auto configuration from
a DHCPv6 server. Number of DAD AttemptsEnter the number of consecutive neighbor solicitation messages that are sent while Duplicate Address Detection (DAD) is performed on the interfaces Unicast IPv6 addresses. DAD verifies the uniqueness of a new Unicast IPv6 address before it is assigned. New addresses remain in a tentative state during DAD verification. Entering 0 in this field disables duplicate address detection processing on the specified interface. Entering 1 in this field indicates a single transmission without follow-up transmissions.
286
16
IP Configuration
IPv6 Management and Interfaces
STEP 6 Click Apply to enable IPv6 processing on the selected interface. Regular IPv6
interfaces have the following addresses automatically configured: Link local address using EUI-64 format interface ID based on a devices MAC address All node link local Multicast addresses (FF02::1) Solicited-Node Multicast address (format FF02::1:FFXX:XXXX)
STEP 7 Click IPv6 Address Table to manually assign IPv6 addresses to the interface, if
Stateless ServiceIs the client defined as stateless (receives configuration information from a DHCP server) or not. DHCPv6 Server AddressAddress of DHCPv6 server. DHCPv6 Server DUIDUnique identifier of the DHCPv6 server. DHCPv6 Server PreferencePriority of this DHCPv6 server. Information Minimum Refresh Time See above. Information Refresh TimeSee above.
287
IP Configuration
IPv6 Management and Interfaces
16
Received Information Refresh TimeRefresh time received from DHCPv6 server. Remaining Information Refresh TimeRemaining time until next refresh. DNS ServersList of DNS servers received from the DHCPv6 server. DNS Domain Search ListList of domains received from the DHCPv6 server. SNTP ServersList of SNTP servers received from the DHCPv6 server. POSIX Timezone StringTimezone received from the DHCPv6 server. Configuration ServerServer containing configuration file received from the DHCPv6 server. Configuration Path NamePath to configuration file on the configuration server received from the DHCPv6 server.
IPv6 Tunnel
Tunnels enable transmission of IPv6 packets over IPv4 networks. Each tunnel has a source IPv4 address and a destination IPv4 address. The IPv6 packet is encapsulated between these addresses.
ISATAP Tunnels
The type of tunnel that can be configured on the device is called an Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunnel, which is a point-to-multipoint tunnel. The source address is the IPv4 address (or one of the IPv4 addresses) of the device. When configuring an ISATAP tunnel, the destination IPv4 address is provided by the router. Note the following: An IPv6 link local address is assigned to the ISATAP interface. The initial IP address is assigned to the interface, which is then activated. If an ISATAP interface is active, the ISATAP router IPv4 address is resolved via DNS by using ISATAP-to-IPv4 mapping. If the ISATAP DNS record is not resolved, the ISATAP host name-to-address mapping is searched for in the host mapping table. When the ISATAP router IPv4 address is not resolved via the DNS process, the ISATAP IP interface remains active. The system does not have a default router for ISATAP traffic until the DNS process is resolved.
288
16
Configuring Tunnels
Interfaces page. To configure an IPv6 tunnel:
IP Configuration
IPv6 Management and Interfaces
NOTE To configure a tunnel, first configure an IPv6 interface as a tunnel in the IPv6
STEP 1 In Layer 2 system mode, click Administration > Management Interface > IPv6
Tunnel. In Layer 3 system mode, click IP Configuration > IPv6 Management and Interfaces > IPv6 Tunnel.
Tunnel NumberDisplays the automatic tunnel router domain number. Tunnel TypeAlways ISATAP. Source IPv4 AddressThe IPv4 address of the selected interface on the current device used to form part of the IPv6 address. -
NoneDisable the tunnel. ManualEnter the IPv4 source address to be used. The IPv4 address
configured must be one of the IPv4 addresses of the devices IPv4 interfaces.
ISATAP Router NameA global string that represents a specific automatic tunnel router domain name. The name can either be the default name (ISATAP) or a user defined name. ISATAP Solicitation IntervalThe number of seconds between ISATAP router solicitations messages, when there is no active ISATAP router. The interval can be the default value or a user defined interval.
289
IP Configuration
IPv6 Management and Interfaces
16
ISATAP RobustnessUsed to calculate the interval for the DNS or router solicitation queries. The larger the number, the more frequent the queries.
NOTE The ISATAP tunnel is not operational if the underlying IPv4 interface is
not in operation.
STEP 3 Click Apply. The tunnel is saved to the Running Configuration file.
Addresses. In Layer 3 system mode, click IP Configuration > IPv6 Management and Interfaces > IPv6 Addresses.
STEP 2 To filter the table, select an interface name, and click Go. The interface appears in
IPv6 InterfaceDisplays the interface on which the IPv6 address is to be defined. If an * is displayed, this means that the IPv6 interface is not enabled but has been configured. IPv6 Address TypeSelect the type of the IPv6 address to add. Link LocalAn IPv6 address that uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalAn IPv6 address that is a global Unicast IPV6 type that is visible and reachable from other networks.
IPv6 AddressIn Layer 2, the device supports one IPv6 interface. In addition to the default link local and Multicast addresses, the device also automatically adds global addresses to the interface based on the router advertisements it receives. The device supports a maximum of 128 addresses at the interface. Each address must be a valid IPv6 address that
290
16
IP Configuration
IPv6 Management and Interfaces
is specified in hexadecimal format by using 16-bit values separated by colons.You cannot configure an IPv6 addresses directly on an ISATAP tunnel interface. Prefix LengthThe length of the Global IPv6 prefix is a value from 0-128 indicating the number of the high-order contiguous bits of the address comprise the prefix (the network portion of the address). EUI-64Select to use the EUI-64 parameter to identify the interface ID portion of the Global IPv6 address by using the EUI-64 format based on a device MAC address.
291
IP Configuration
IPv6 Management and Interfaces
16
In Layer 3 system mode, click IP Configuration > IPv6 Management and Interfaces > IPv6 Default Router List . This page displays the following fields for each default router: Default Router IPv6 AddressLink local IP address of the default router. InterfaceOutgoing IPv6 interface where the default router resides. TypeThe default router configuration that includes the following options: StaticThe default router was manually added to this table through the Add button. DynamicThe default router was dynamically configured.
StateThe default router status options are: IncompleteAddress resolution is in process. Default router has not yet responded. ReachablePositive confirmation was received within the Reachable
Time.
UnreachablePositive confirmation was not received within the
Reachable Time.
StalePreviously-known neighboring network is unreachable, and no action is taken to verify its reachability until it is necessary to send traffic. DelayPreviously-known neighboring network is unreachable. The device is in Delay state for a predefined Delay Time. If no confirmation is received, the state changes to Probe. ProbeNeighboring network is unavailable, and Unicast Neighbor Solicitation probes are being sent to verify the status.
STEP 2 Click Add to add a static default router. STEP 3 Enter the following fields:
Link Local InterfaceDisplays the outgoing Link Local interface. Default Router IPv6 AddressThe IP address of the default router
STEP 4 Click Apply. The default router is saved to the Running Configuration file.
292
16
Defining IPv6 Neighbors Information
IP Configuration
IPv6 Management and Interfaces
The IPv6 Neighbors page enables configuring and viewing the list of IPv6 neighbors on the IPv6 interface. The IPv6 Neighbor Table (also known as IPv6 Neighbor Discovery Cache) displays the MAC addresses of the IPv6 neighbors that are in the same IPv6 subnet as the device. This is the IPv6 equivalent of the IPv4 ARP Table. When the device needs to communicate with its neighbors, the device uses the IPv6 Neighbor Table to determine the MAC addresses based on their IPv6 addresses. This page displays the neighbors that were automatically detected or manually configured entries. Each entry displays to which interface the neighbor is connected, the neighbors IPv6 and MAC addresses, the entry type (static or dynamic), and the state of the neighbor. To define IPv6 neighbors:
STEP 1 n Layer 2 system mode, click Administration > Management Interface > IPv6
Neighbors. In Layer 3 system mode, click IP Configuration > IPv6 Management and Interfaces > IPv6 Neighbors.
STEP 2 You can select a Clear Table option to clear some or all of IPv6 addresses in the
IPv6 Neighbors Table. Static OnlyDeletes the static IPv6 address entries. Dynamic OnlyDeletes the dynamic IPv6 address entries. All Dynamic & StaticDeletes the static and dynamic address entries IPv6 address entries.
The following fields are displayed for the neighboring interfaces: InterfaceNeighboring IPv6 interface type. IPv6 AddressIPv6 address of a neighbor. MAC AddressMAC address mapped to the specified IPv6 address. TypeNeighbor discovery cache information entry type (static or dynamic). StateSpecifies the IPv6 neighbor status. The values are: -
IncompleteAddress resolution is working. The neighbor has not yet responded. ReachableNeighbor is known to be reachable.
293
IP Configuration
IPv6 Management and Interfaces
16
-
STEP 3 To add a neighbor to the table, click Add. STEP 4 Enter values for the following fields:
InterfaceThe neighboring IPv6 interface to be added. IPv6 AddressEnter the IPv6 network address assigned to the interface. The address must be a valid IPv6 address. MAC AddressEnter the MAC address mapped to the specified IPv6 address.
STEP 5 Click Apply. The Running Configuration file is updated. STEP 6 To change the type of an IP address from Dynamic to Static, select the address,
294
16
-or
IP Configuration
IPv6 Management and Interfaces
To view IPv6 routing entries in Layer 3 system mode: Click IP Configuration > IPv6 Management and Interfaces > IPv6 Routes. This page displays the following fields: IPv6 AddressThe IPv6 subnet address. Prefix LengthIP route prefix length for the destination IPv6 subnet address. It is preceded by a forward slash. InterfaceInterface used to forward the packet. Next HopAddress where the packet is forwarded. Typically, this is the address of a neighboring router. It can be one of the following types. Link LocalAn IPv6 interface and IPv6 address that uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalAn IPv6 address that is a global Unicast IPV6 type that is visible and reachable from other networks. Point-to-PointA Point-to-point tunnel.
MetricValue used for comparing this route to other routes with the same destination in the IPv6 router table. All default routes have the same value. LifetimeTime period during which the packet can be sent, and resent, before being deleted. Route TypeHow the destination is attached, and the method used to obtain the entry. The following values are: -
295
IP Configuration
IPv6 Management and Interfaces
16
-
DHCPv6 Relay
DHCPv6 Relay is used for relaying DHCPv6 messages to DHCPv6 servers. It is defined in RFC 3315. When the DHCPv6 client is not directly connected to the DHCPv6 server, a DHCPv6 relay agent (the device) to which this DHCPv6 client is directlyconnected encapsulates the received messages from the directly-connected DHCPv6 client, and forwards them to the DHCPv6 server. In the opposite direction, the relay agent decapsulates packets received from the DHCPv6 server and forwards them, towards the DHCPv6 client. The user must configure the list DHCP servers to which packets are forwarded. Two sets of DHCPv6 servers can be configured: Global DestinationsPackets are always relayed to these DHCPv6 servers. Interface ListThis is a per-interface list of DHCPv6 servers. When a DHCPv6 packet is received on an interface, the packet is relayed both to the servers on the interface list (if it exists) and to the servers on the global destination list.
Global Destinations
To configure a list of DHCPv6 servers to which all DHCPv6 packets are relayed:
STEP 1 Click IP Configuration > IPv6 Management and Interfaces > DHCPv6 Relay >
Global Destinations.
STEP 2 To add a default DHCPv6 server, click Add. STEP 3 Enter the fields:
IPv6 Address TypeEnter the type of the destination address to which client messages are forwarded. The address type can be Link Local, Global or Multicast (All_DHCP_Relay_Agents_and_Servers).
296
16
IP Configuration
Domain Name
DHCPv6 Server IP AddressEnter the address of the DHCPv6 server to which packets are forwarded. IPv6 InterfaceEnter the interface on which packets are transmitted when the address type of the DHCPv6 server is Link Local or Multicast .
Interface Settings
To enable the DHCPv6 Relay feature on an interface and to configure a list of DHCPv6 servers to which DHCPv6 packets are relayed when they are received on this interface.
STEP 1 Click IP Configuration > IPv6 Management and Interfaces > DHCPv6 Relay >
Interface Settings.
STEP 2 To enable DHCPv6 on an interface and optionally add a DHCPv6 server for an
interface, click Add. Enter the fields: Source InterfaceSelect the interface (port, LAG, VLAN or tunnel) for which DHCPv6 Relay is enabled. Use Global Destinations OnlySelect to forward packets to the DHCPv6 global destination servers only. IPv6 Address TypeEnter the type of the destination address to which client messages are forwarded. The address type can be Link Local, Global or Multicast (All_DHCP_Relay_Agents_and_Servers). DHCPv6 Server IP AddressEnter the address of the DHCPv6 server to which packets are forwarded. IPv6 InterfaceEnter the interface on which packets are transmitted when the address type of the DHCPv6 server is Link Local or Multicast .
Domain Name
The Domain Name System (DNS) translates domain names into IP addresses for the purpose of locating and addressing hosts.
297
IP Configuration
Domain Name
16
As a DNS client, the device resolves domain names to IP addresses through the use of one or more configured DNS servers.
DNS Settings
Use the DNS Settings page to enable the DNS feature, configure the DNS servers and set the default domain used by the device.
STEP 1 Click IP Configuration > Domain Name > DNS Settings. STEP 2 Enter the parameters.
DNSSelect to designate the device as a DNS client, which can resolve DNS names into IP addresses through one or more configured DNS servers. Polling RetriesEnter the number of times to send a DNS query to a DNS server until the device decides that the DNS server does not exist. Polling TimeoutEnter the number of seconds that the device will wait for a response to a DNS query. Polling IntervalEnter how often (in seconds) the device sends DNS query packets after the number of retries has been exhausted. Use DefaultSelect to use the default value. This value = 2*(Polling Retries + 1)* Polling Timeout User DefinedSelect to enter a user-defined value.
Default ParametersEnter the following default parameters: Default Domain NameEnter the DNS domain name used to complete unqualified host names. The device appends this to all non-fully qualified domain names (NFQDNs) turning them into FQDNs.
NOTE Do not include the initial period that separates an unqualified name
from the domain name (like cisco.com). DHCP Domain Search ListClick Details to view the list of DNS servers configured on the device.
DNS Server Table: The following fields are displayed for each DNS server configured: DNS ServerThe IP address of the DNS server.
298
16
IP Configuration
Domain Name
PreferenceEach server has a preference value, a lower value means a higher chance of being used. SourceSource of the servers IP address (static or DHCPv4 or DHCPv6) InterfaceInterface of the servers IP address.
STEP 4 Up to eight DNS servers can be defined. To add a DNS server, click Add.
Enter the parameters. IP VersionSelect Version 6 for IPv6 or Version 4 for IPv4. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceIf the IPv6 address type is Link Local, select the interface through which it is received. DNS Server IP AddressEnter the DNS server IP address. DNS Server StateSelect to activate the new DNS server.
STEP 5 Click Apply. The DNS server is saved to the Running Configuration file.
Search List
The search list can contain one static entry defined by the user the DNS Settings page and dynamic entries received from DHCPv4 and DHCPv6 servers. To view the domain names that have been configured on the device:
STEP 1 Click IP Configuration > Domain Name > Search List .
The following fields are displayed for each DNS server configured on the device. Domain NameName of domain that can be used on the device.
299
IP Configuration
Domain Name
16
SourceSource of the servers IP address (static or DHCPv4 or DHCPv6) for this domain. InterfaceInterface of the servers IP address for this domain. PreferenceThis is the order in which the domains are used (from low to high). This effectively determines the order in which unqualified names are completed during DNS queries.
Host Mapping
Host name/IP address mappings are stored in the Host Mapping Table (DNS cache). This cache can contain the following type of entries: Static EntriesThese are mapping pairs that were manually added to the cache. There can be up to 64 static entries. Dynamic EntriesThese are mapping pairs that were either added by the system as a result of being used by the user, or and an entry for each IP address configured on the device by DHCP. There can be 256 dynamic entries.
Name resolution always begins by checking static entries, continues by checking the dynamic entries, and ends by sending requests to the external DNS server. Eight IP addresses are supported per DNS server per host name. To add a host name and its IP address:
STEP 1 Click IP Configuration > Domain Name System > Host Mapping. STEP 2 You can select a Clear Table option to clear some or all of the entries in the Host
Mapping Table. Static OnlyDeletes the static hosts. Dynamic OnlyDeletes the dynamic hosts. All Dynamic & StaticDeletes the static and dynamic hosts.
The Host Mapping Table displays the following fields: Host NameUser-defined host name or fully-qualified name. IP AddressThe host IP address.
300
16
TypeIs this a Dynamic or Static entry to the cache.
IP Configuration
Domain Name
OKAttempt succeeded. Negative CacheAttempt failed, do not try again. No ResponseThere was no response, but system can try again in
future.
TTL If this is a dynamic entry, how long will it remain in the cache. Remaining TTL If this is a dynamic entry, how much longer will it remain in the cache.
STEP 3 To add a host mapping, click Add. STEP 4 Enter the parameters.
IP VersionSelect Version 6 for IPv6 or Version 4 for IPv4. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceIf the IPv6 address type is Link Local, select the interface through which it is received. Host NameEnter a user-defined host name or fully-qualified name. Host names are restricted to the ASCII letters A through Z (case-insensitive), the digits 0 through 9, the underscore and the hyphen. A period (.) is used to separate labels. IP Address(es)Enter a single address or up to eight associated IP addresses (IPv4 or IPv6).
301
17
Security
This section describes device security and access control. The system handles various types of security. The following list of topics describes the various types of security features described in this section. Some features are used for more than a single type of security or control, and so they appear twice in the list of topics below. Permission to administer the device is described in the following sections: Defining Users Configuring TACACS+ Configuring RADIUS Configuring Management Access Authentication Defining Management Access Method SSL Server SSL Server
Protection from attacks directed at the device CPU is described in the following sections: Configuring TCP/UDP Services Defining Storm Control Access Control
Access control of end-users to the network through the device is described in the following sections: Configuring Management Access Authentication Defining Management Access Method Configuring TACACS+
302
17
Configuring RADIUS Configuring Port Security Configuring 802.1X Defining Time Ranges
Security
Defining Users
Protection from other network users is described in the following sections. These are attacks that pass through, but are not directed at, the device. Denial of Service Prevention SSL Server Defining Storm Control Configuring Port Security IP Source Guard Dynamic ARP Inspection Access Control
Defining Users
The default username/password is cisco/cisco. The first time that you log in with the default username and password, you are required to enter a new password. Password complexity is enabled by default. If the password that you choose is not complex enough (Password Complexity Settings are enabled in the Password Strength page), you are prompted to create another password.
303
Security
Defining Users
17
STEP 1 Click Administration > User Accounts.
This page displays the users defined in the system and their user privilege level.
STEP 2 Select Password Recovery Service to enable this feature. When this is enabled, an
end user, with physical access to the console port of the device, can enter the boot menu and trigger the password recovery process. When the boot system process ends, you are allowed to login to the device without password authentication. Entering the device is allowed only via the console and only when the console is connected to the device with physical access. When password recovery mechanism is disabled, accessing the boot menu is still allowed and you can trigger the password recovery process. The difference is that in this case, all configuration and user files are removed during the system boot process, and a suitable log message is generated to the terminal.
STEP 3 Click Add to add a new user or click Edit to modify a user. STEP 4 Enter the parameters.
User NameEnter a new username between 0 and 20 characters. UTF-8 characters are not permitted. PasswordEnter a password (UTF-8 characters are not permitted). If the password strength and complexity is defined, the user password must comply with the policy configured in the Setting Password Complexity Rules section. Confirm PasswordEnter the password again. Password Strength MeterDisplays the strength of password. The policy for password strength and complexity are configured in the Password Strength page. User LevelSelect the privilege level of the user being added/edited. Read-Only CLI Access (1)User cannot access the GUI, and can only access CLI commands that do not change the device configuration. Read/Limited Write CLI Access (7)User cannot access the GUI, and can only access some CLI commands that change the device configuration. See the CLI Reference Guide for more information. Read/Write Management Access (15)User can access the GUI, and can configure the device.
304
17
Setting Password Complexity Rules
Security
Defining Users
STEP 5 Click Apply. The user is added to the Running Configuration file of the device.
Passwords are used to authenticate users accessing the device. Simple passwords are potential security hazards. Therefore, password complexity requirements are enforced by default and may be configured as necessary. Password complexity requirements are configured on the Password Strength page reached through the Security drop-down menu. Additionally, password aging time may be configured on this page. To define password complexity rules:
STEP 1 Click Security > Password Strength. STEP 2 Enter the following aging parameters for passwords:
Password AgingIf selected, the user is prompted to change the password when the Password Aging Time expires. Password Aging TimeEnter the number of days that can elapse before the user is prompted to change the password.
NOTE Password aging also applies to zero-length passwords (no
password).
STEP 3 Select Password Complexity Settings to enable complexity rules for passwords.
If password complexity is enabled, new passwords must conform to the following default settings: Have a minimum length of eight characters. Contain characters from at least three character classes (uppercase letters, lowercase letters, numbers, and special characters available on a standard keyboard). Are different from the current password. Contain no character that is repeated more than three times consecutively. Do not repeat or reverse the users name or any variant reached by changing the case of the characters. Do not repeat or reverse the manufacturers name or any variant reached by changing the case of the characters.
305
Security
Configuring TACACS+
17
be configured: Minimal Password LengthEnter the minimal number of characters required for passwords.
NOTE A zero-length password (no password) is allowed, and can still have
STEP 4 If the Password Complexity Settings are enabled, the following parameters may
password aging assigned to it. Allowed Character RepetitionEnter the number of times that a character can be repeated. Minimal Number of Character ClassesEnter the number of character classes which must be present in a password. Character classes are lower case (1), upper case (2), digits (3), and symbols or special characters (4). The New Password Must Be Different than the Current OneIf selected, the new password cannot be the same as the current password upon a password change.
STEP 5 Click Apply. The password settings are written to the Running Configuration file.
equivalence may be done through the CLI. See the CLI Reference Guide for further instruction.
Configuring TACACS+
An organization can establish a Terminal Access Controller Access Control System (TACACS+) server to provide centralized security for all of its devices. In this way, authentication and authorization can be handled on a single server for all devices in the organization. The device can act as a TACACS+ client that uses the TACACS+ server for the following services: AuthenticationProvides authentication of users logging onto the device by using usernames and user-defined passwords. AuthorizationPerformed at login. After the authentication session is completed, an authorization session starts using the authenticated username. The TACACS+ server then checks user privileges.
306
17
Security
Configuring TACACS+
AccountingEnable accounting of login sessions using the TACACS+ server. This enables a system administrator to generate accounting reports from the TACACS+ server.
In addition to providing authentication and authorization services, the TACACS+ protocol helps to ensure TACACS message protection through encrypted TACACS body messages. TACACS+ is supported only with IPv4. Some TACACS+ servers support a single connection that enables the device to receive all information in a single connection. If the TACACS+ server does not support this, the device reverts to multiple connections.
307
Security
Configuring TACACS+
17
Defaults
The following defaults are relevant to this feature: No default TACACS+ server is defined by default. If you configure a TACACS+ server, the accounting feature is disabled by default.
Workflow
To use a TACACS+ server, do the following:
STEP 1 Open an account for a user on the TACACS+ server. STEP 2 Configure that server along with the other parameters in the TACACS+ and Add
user logs onto the device, authentication is performed on the TACACS+ server instead of in the local database.
NOTE If more than one TACACS+ server has been configured, the device uses the
configured priorities of the available TACACS+ servers to select the TACACS+ server to be used by the device.
308
17
STEP 1 Click Security > TACACS+.
Security
Configuring TACACS+
Key StringEnter the default Key String used for communicating with all TACACS+ servers in Encrypted or Plaintext mode. The device can be configured to use this key or to use a key entered for an specific server (entered in the Add TACACS+ Server page). If you do not enter a key string in this field, the server key entered in the Add TACACS+ Server page must match the encryption key used by the TACACS+ server. If you enter both a key string here and a key string for an individual TACACS+ server, the key string configured for the individual TACACS+ server takes precedence.
Timeout for ReplyEnter the amount of time that passes before the connection between the device and the TACACS+ server times out. If a value is not entered in the Add TACACS+ Server page for a specific server, the value is taken from this field. Source IPv4 AddressEnter the device IPv4 source addresses to be used by the TACACS+ server. Source IPv6 AddressEnter the device IPv6 source addresses to be used by the TACACS+ server.
STEP 4 Click Apply. The TACACS+ default settings are added to the Running
Configuration file. These are used if the equivalent parameters are not defined in the Add page.
STEP 5 To add a TACACS+ server, click Add. STEP 6 Enter the parameters.
Server DefinitionSelect one of the following ways to identify the TACACS+ server: By IP AddressIf this is selected, enter the IP address of the server in the Server IP Address/Name field. By NameIf this is selected enter the name of the server in the Server IP Address/Name field.
309
Security
Configuring TACACS+
17
Server IP Address/NameEnter the IP address or name of the TACACS+ server. PriorityEnter the order in which this TACACS+ server is used. Zero is the highest priority TACACS+ server and is the first server used. If it cannot establish a session with the high priority server, the device tries the next highest priority server. Source IP Address(For SG500X devices and other devices in Layer 3 system mode). Select to use either the default device source address or one of the available device IP addresses for communication with the TACACS+ server. Key StringEnter the default key string used for authenticating and encrypting between the device and the TACACS+ server. This key must match the key configured on the TACACS+ server. A key string is used to encrypt communications by using MD5. You can select the default key on the device, or the key can be entered in Encrypted or Plaintext form. If you do not have an encrypted key string (from another device), enter the key string in plaintext mode and click Apply. The encrypted key string is generated and displayed. If you enter a key, this overrides the default key string if one has been defined for the device on the main page. Timeout for ReplyEnter the amount of time that passes before the connection between the device and the TACACS+ server times out. Select Use Default to use the default value displayed on the page. IP PortEnter the port number through which the TACACS+ session occurs. Single ConnectionSelect to enable receiving all information in a single connection. If the TACACS+ server does not support this, the device reverts to multiple connections.
STEP 7 To display sensitive data in plaintext form in the configuration file, click Display
device.
310
17
Configuring RADIUS
Security
Configuring RADIUS
Remote Authorization Dial-In User Service (RADIUS) servers provide a centralized 802.1X or MAC-based network access control. The device is a RADIUS client that can use a RADIUS server to provide centralized security. An organization can establish a Remote Authorization Dial-In User Service (RADIUS) server to provide centralized 802.1X or MAC-based network access control for all of its devices. In this way, authentication and authorization can be handled on a single server for all devices in the organization. The device can act as a RADIUS client that uses the RADIUS server for the following services: AuthenticationProvides authentication of regular and 802.1X users logging onto the device by using usernames and user-defined passwords. AuthorizationPerformed at login. After the authentication session is completed, an authorization session starts using the authenticated username. The TACACS+ server then checks user privileges. AccountingEnable accounting of login sessions using the RADIUS server. This enables a system administrator to generate accounting reports from the RADIUS server.
Defaults
The following defaults are relevant to this feature: No default RADIUS server is defined by default. If you configure a RADIUS server, the accounting feature is disabled by default.
311
Security
Configuring RADIUS
17
Interactions With Other Features
You cannot enable accounting on both a RADIUS and TACACS+ server.
Radius Workflow
To user a RADIUS server, do the following:
STEP 1 Open an account for the device on the RADIUS server. STEP 2 Configure that server along with the other parameters in the RADIUS and ADD
configured priorities of the available RADIUS servers to select the RADIUS server to be used by the device. To set the RADIUS server parameters:
STEP 1 Click Security > RADIUS. STEP 2 Enter the RADIUS Accounting option. The following options are available:
Port Based Access Control (802.1X, MAC Based)Specifies that the RADIUS server is used for 802.1x port accounting. Management AccessSpecifies that the RADIUS server is used for user login accounting. Both Port Based Access Control and Management AccessSpecifies that the RADIUS server is used for both user login accounting and 802.1x port accounting. NoneSpecifies that the RADIUS server is not used for accounting.
STEP 3 Enter the default RADIUS parameters if required. Values entered in the Default
Parameters are applied to all servers. If a value is not entered for a specific server (in the Add RADIUS Server page) the device uses the values in these fields. RetriesEnter the number of transmitted requests that are sent to the RADIUS server before a failure is considered to have occurred. Timeout for ReplyEnter the number of seconds that the device waits for an answer from the RADIUS server before retrying the query, or switching to the next server.
312
17
Security
Configuring RADIUS
Dead TimeEnter the number of minutes that elapse before a nonresponsive RADIUS server is bypassed for service requests. If the value is 0, the server is not bypassed. Key StringEnter the default key string used for authenticating and encrypting between the device and the RADIUS server. This key must match the key configured on the RADIUS server. A key string is used to encrypt communications by using MD5. The key can be entered in Encrypted or Plaintext form. If you do not have an encrypted key string (from another device), enter the key string in plaintext mode and click Apply. The encrypted key string is generated and displayed.
This overrides the default key string if one has been defined. Source IPv4 Address(For devices in Layer 3 system mode) Enter the source IPv4 address to be used. Source IPv6 AddressEnter the source IPv6 address to be used.
STEP 4 Click Apply. The RADIUS default settings for the device are updated in the
entered in the RADIUS page, select Use Default . Server DefinitionSelect whether to specify the RADIUS server by IP address or name. IPv6 Address TypeDisplays that IPv6 address type is Global. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceSelect the link local interface (if IPv6 Address Type Link Local is selected) from the list.
313
Security
Configuring RADIUS
17
Server IP Address/NameEnter the RADIUS server by IP address or name. PriorityEnter the priority of the server. The priority determines the order the device attempts to contact the servers to authenticate a user. The device starts with the highest priority RADIUS server first. Zero is the highest priority. Source IP Address(For devices in Layer 3 system mode) Select to use either the default source address or select one of the available IP addresses. Key StringEnter the key string used for authenticating and encrypting communication between the device and the RADIUS server. This key must match the key configured on the RADIUS server. It can be entered in Encrypted or Plaintext format. If Use Default is selected, the device attempts to authenticate to the RADIUS server by using the default Key String. Timeout for ReplyEnter the number of seconds the device waits for an answer from the RADIUS server before retrying the query, or switching to the next server if the maximum number of retries were made. If Use Default is selected, the device uses the default timeout value. Authentication PortEnter the UDP port number of the RADIUS server port for authentication requests. Accounting PortEnter the UDP port number of the RADIUS server port for accounting requests. RetriesEnter the number of requests that are sent to the RADIUS server before a failure is considered to have occurred. If Use Default is selected, the device uses the default value for the number of retries. Dead TimeEnter the number of minutes that must pass before a nonresponsive RADIUS server is bypassed for service requests. If Use Default is selected, the device uses the default value for the dead time. If you enter 0 minutes, there is no dead time. Usage TypeEnter the RADIUS server authentication type. The options are: LoginRADIUS server is used for authenticating users that ask to administer the device. 802.1XRADIUS server is used for 802.1x authentication. AllRADIUS server is used for authenticating user that ask to administer the device and for 802.1X authentication.
314
17
Sensitive Data As Plaintext .
Security
Configuring Management Access Authentication
STEP 6 To display sensitive data in plaintext form in the configuration file, click Display
STEP 7 Click Apply. The RADIUS server definition is added to the Running Configuration
column and the Selected Methods column. The first method selected is the first method that is used. RADIUSUser is authenticated on a RADIUS server. You must have configured one or more RADIUS servers. TACACS+User authenticated on the TACACS+ server. You must have configured one or more TACACS+ servers. NoneUser is allowed to access the device without authentication.
315
Security
Defining Management Access Method
17
LocalUsername and password are checked against the data stored on the local device. These username and password pairs are defined in the User Accounts page.
NOTE The Local or None authentication method must always be
selected last. All authentication methods selected after Local or None are ignored.
STEP 4 Click Apply. The selected authentication methods are associated with the access
method.
ActionPermit or deny access to an interface or source address. InterfaceWhich ports, LAGs, or VLANs are permitted to access or are denied access to the web-based configuration utility.
316
17
Security
Defining Management Access Method
Source IP AddressIP addresses or subnets. Access to management methods might differ among user groups. For example, one user group might be able to access the device module only by using an HTTPS session, while another user group might be able to access the device module by using both HTTPS and Telnet sessions.
This page displays all of the access profiles, active and inactive.
STEP 2 To change the active access profile, select a profile from the Active Access
Profile drop down menu and click Apply. This makes the chosen profile the active access profile.
NOTE A caution message appears if you selected Console Only. If you
continue, you are immediately disconnected from the web-based configuration utility and can access the device only through the console port. This only applies to device types that offer a console port.
317
Security
Defining Management Access Method
17
A caution message displays if you selected any other access profile, warning you that, depending on the selected access profile, you might be disconnected from the web-based configuration utility.
STEP 3 Click OK to select the active access profile or click Cancel to discontinue the
action.
STEP 4 Click Add to open the Add Access Profile page. The page allows you to configure
Rule PriorityEnter the rule priority. When the packet is matched to a rule, user groups are either granted or denied access to the device. The rule priority is essential to matching packets to rules, as packets are matched on a first-match basis. One is the highest priority. Management MethodSelect the management method for which the rule is defined. The options are: AllAssigns all management methods to the rule. TelnetUsers requesting access to the device that meets the Telnet access profile criteria are permitted or denied access. Secure Telnet (SSH)Users requesting access to the device that meets the SSH access profile criteria, are permitted or denied access. HTTP Users requesting access to the device that meets the HTTP access profile criteria, are permitted or denied. Secure HTTP (HTTPS)Users requesting access to the device that meets the HTTPS access profile criteria, are permitted or denied. SNMPUsers requesting access to the device that meets the SNMP access profile criteria are permitted or denied.
ActionSelect the action attached to the rule. The options are: PermitPermits access to the device if the user matches the settings in the profile. DenyDenies access to the device if the user matches the settings in the profile.
Applies to InterfaceSelect the interface attached to the rule. The options are:
318
17
Security
Defining Management Access Method
AllApplies to all ports, VLANs, and LAGs. User DefinedApplies to selected interface.
InterfaceEnter the interface number if User Defined was selected. Applies to Source IP AddressSelect the type of source IP address to which the access profile applies. The Source IP Address field is valid for a subnetwork. Select one of the following values: AllApplies to all types of IP addresses. User DefinedApplies to only those types of IP addresses defined in the fields.
IP AddressEnter the source IP address. MaskSelect the format for the subnet mask for the source IP address, and enter a value in one of the fields: -
Prefix LengthSelect the Prefix Length and enter the number of bits that
comprise the source IP address prefix.
STEP 7 Click Apply. The access profile is written to the Running Configuration file. You can
319
Security
Defining Management Access Method
17
STEP 1 Click Security > Mgmt Access Method > Profile Rules. STEP 2 Select the Filter field, and an access profile. Click Go.
Access Profile NameSelect an access profile. Rule PriorityEnter the rule priority. When the packet is matched to a rule, user groups are either granted or denied access to the device. The rule priority is essential to matching packets to rules, as packets are matched on a first-fit basis. Management MethodSelect the management method for which the rule is defined. The options are: AllAssigns all management methods to the rule. TelnetUsers requesting access to the device that meets the Telnet access profile criteria are permitted or denied access. Secure Telnet (SSH)Users requesting access to the device that meets the Telnet access profile criteria, are permitted or denied access. HTTPAssigns HTTP access to the rule. Users requesting access to the device that meets the HTTP access profile criteria, are permitted or denied. Secure HTTP (HTTPS)Users requesting access to the device that meets the HTTPS access profile criteria, are permitted or denied. SNMPUsers requesting access to the device that meets the SNMP access profile criteria are permitted or denied.
ActionSelect Permit to permit the users that attempt to access the device by using the configured access method from the interface and IP source defined in this rule. Or select Deny to deny access. Applies to InterfaceSelect the interface attached to the rule. The options are: AllApplies to all ports, VLANs, and LAGs. User DefinedApplies only to the port, VLAN, or LAG selected.
320
17
InterfaceEnter the interface number.
Security
SSL Server
Applies to Source IP AddressSelect the type of source IP address to which the access profile applies. The Source IP Address field is valid for a subnetwork. Select one of the following values: AllApplies to all types of IP addresses. User DefinedApplies to only those types of IP addresses defined in the fields.
IP VersionSelect the supported IP version of the source address: IPv6 or IPv4. IP AddressEnter the source IP address. MaskSelect the format for the subnet mask for the source IP address, and enter a value in one of the field: Network MaskSelect the subnet to which the source IP address belongs and enter the subnet mask in dotted decimal format. Prefix LengthSelect the Prefix Length and enter the number of bits that comprise the source IP address prefix.
STEP 5 Click Apply, and the rule is added to the access profile.
SSL Server
This section describes the Secure Socket Layer (SSL) feature.
SSL Overview
The Secure Socket Layer (SSL) feature is used to open an HTTPS session to the device. An HTTPS session may be opened with the default certificate that exists on the device. Some browsers generate warnings when using a default certificate, since this certificate is not signed by a Certification Authority (CA). It is best practice to have a certificate signed by a trusted CA.
321
Security
SSL Server
17
To open an HTTPS session with a user-created certificate, perform the following actions: 1. Generate a certificate. 2. Request that the certificate be certified by a CA. 3. Import the signed certificate into the device.
Information appears for certificate 1 and 2 in the SSL Server Key Table. These fields are defined in the Edit page except for the following fields: Valid FromSpecifies the date from which the certificate is valid. Valid ToSpecifies the date up to which the certificate is valid. Certificate SourceSpecifies whether the certificate was generated by the system (Auto Generated) or the user (User Defined).
STEP 2 Select an active certificate. STEP 3 You can perform one of the following actions by clicking the relevant button:
EditSelect one of the certificates and enter the following fields for it: Regenerate RSA KeySelect to regenerate the RSA key. Key LengthEnter the length of the RSA key to be generated. Common NameSpecifies the fully-qualified device URL or IP address. If unspecified, defaults to the lowest IP address of the device (when the certificate is generated).
322
17
Organization NameSpecifies the organization name. LocationSpecifies the location or city name. StateSpecifies the state or province name. CountrySpecifies the country name.
Security
SSL Server
Generate Certificate RequestGenerate a certificate request to be signed by a CA. Enter the fields for the certificate (same as fields in Edit page).
STEP 4 Click Generate Certificate Request . This creates a key that must be entered on
the CA. Import CertificateWhen the approval is received from the CA, enter the following: Certificate IDSelect the active certificate. CertificateCopy in the received certificate. Import RSA KEY-PairSelect to enable copying in the new RSA keypair. Public KeyCopy in the RSA public key. Private Key (Encrypted)Select and copy in the RSA private key in encrypted form. Private Key (Plaintext)Select and copy in the RSA private key in plain text form. Display Sensitive Data as EncryptedClick this button to display this key as encrypted. When this button is clicked, the private keys are written to the configuration file in encrypted form (when Apply is clicked).
DetailsDisplays the certificate and RSA key pair. This is used to copy the certificate and RSA key-pair to another device (using copy/paste). When you click Display Sensitive Data as Encrypted., the private keys are displayed in encrypted form.
323
Security
Configuring TCP/UDP Services
17
The active TCP connections are also displayed in this window. To configure TCP/UDP services:
STEP 1 Click Security > TCP/UDP Services. STEP 2 Enable or disable the following TCP/UDP services on the displayed services.
HTTP ServiceIndicates whether the HTTP service is enabled or disabled. HTTPS ServiceIndicates whether the HTTPS service is enabled or disabled. SNMP ServiceIndicates whether the SNMP service is enabled or disabled. Telnet ServiceIndicates whether the Telnet service is enabled or disabled. SSH ServiceIndicates whether the SSH server service is enabled or disabled.
The TCP Service Table displays the following fields for each service: Service NameAccess method through which the device is offering the TCP service. TypeIP protocol the service uses. Local IP AddressLocal IP address through which the device is offering the service. Local PortLocal TCP port through which the device is offering the service.
324
17
Security
Defining Storm Control
Remote IP AddressIP address of the remote device that is requesting the service. Remote PortTCP port of the remote device that is requesting the service. StateStatus of the service.
The UDP Services table displays the following information: Service NameAccess method through which the device is offering the UDP service. TypeIP protocol the service uses. Local IP AddressLocal IP address through which the device is offering the service. Local PortLocal UDP port through which the device is offering the service. Application InstanceThe service instance of the UDP service. (For example, when two senders send data to the same destination.)
STEP 3 Click Apply. The services are written to the Running Configuration file.
325
Security
Configuring Port Security
17
All the fields on this page are described in the Edit Storm Control page except for the Storm Control Rate Threshold (%). It displays the percent of the total available bandwidth for unknown Unicast, Multicast, and Broadcast packets before storm control is applied at the port. The default value is 10% of the maximum rate of the port and is set in the Edit Storm Control page.
STEP 2 Select a port and click Edit. STEP 3 Enter the parameters.
InterfaceSelect the port for which storm control is enabled. Storm ControlSelect to enable Storm Control. Storm Control Rate ThresholdEnter the maximum rate at which unknown packets can be forwarded. The default for this threshold is 10,000 for FE devices and 100,000 for GE devices. Storm Control ModeSelect one of the modes: Unknown Unicast, Multicast & BroadcastCounts unknown Unicast, Broadcast, and Multicast traffic towards the bandwidth threshold. Multicast & BroadcastCounts Broadcast and Multicast traffic towards the bandwidth threshold. Broadcast OnlyCounts only Broadcast traffic towards the bandwidth threshold.
STEP 4 Click Apply. Storm control is modified, and the Running Configuration file is
updated.
326
17
Security
Configuring Port Security
Classic LockAll learned MAC addresses on the port are locked, and the port does not learn any new MAC addresses. The learned addresses are not subject to aging or re-learning. Limited Dynamic LockThe device learns MAC addresses up to the configured limit of allowed addresses. After the limit is reached, the device does not learn additional addresses. In this mode, the addresses are subject to aging and re-learning. Secure PermanentKeeps the current dynamic MAC addresses associated with the port and learns up to the maximum number of addresses allowed on the port (set by Max No. of Addresses Allowed). Relearning and aging are disabled. Secure Delete on ResetDeletes the current dynamic MAC addresses associated with the port after reset. New MAC addresses can be learned as Delete-On-Reset ones up to the maximum addresses allowed on the port. Relearning and aging are disabled.
When a frame from a new MAC address is detected on a port where it is not authorized (the port is classically locked, and there is a new MAC address, or the port is dynamically locked, and the maximum number of allowed addresses has been exceeded), the protection mechanism is invoked, and one of the following actions can take place: Frame is discarded Frame is forwarded Port is shut down
When the secure MAC address is seen on another port, the frame is forwarded, but the MAC address is not learned on that port. In addition to one of these actions, you can also generate traps, and limit their frequency and number to avoid overloading the devices.
NOTE To use 802.1X on a port, it must be in multiple host or multi session modes. Port
security on a port cannot be set if the port is in single mode (see the 802.1x, Host and Session Authentication page). To configure port security:
STEP 1 Click Security > Port Security. STEP 2 Select an interface to be modified, and click Edit. STEP 3 Enter the parameters.
327
Security
Configuring Port Security
17
InterfaceSelect the interface name. Interface StatusSelect to lock the port. Learning ModeSelect the type of port locking. To configure this field, the Interface Status must be unlocked. The Learning Mode field is enabled only if the Interface Status field is locked. To change the Learning Mode, the Lock Interface must be cleared. After the mode is changed, the Lock Interface can be reinstated. The options are: Classic LockLocks the port immediately, regardless of the number of addresses that have already been learned. Limited Dynamic LockLocks the port by deleting the current dynamic MAC addresses associated with the port. The port learns up to the maximum addresses allowed on the port. Both re-learning and aging of MAC addresses are enabled. Secure PermanentKeeps the current dynamic MAC addresses associated with the port and learns up to the maximum number of addresses allowed on the port (set by Max No. of Addresses Allowed). Relearning and aging are enabled. Secure Delete on ResetDeletes the current dynamic MAC addresses associated with the port after reset. New MAC addresses can be learned as Delete-On-Reset ones up to the maximum addresses allowed on the port. Relearning and aging are disabled.
Max No. of Addresses AllowedEnter the maximum number of MAC addresses that can be learned on the port if Limited Dynamic Lock learning mode is selected. The number 0 indicates that only static addresses are supported on the interface. Action on ViolationSelect an action to be applied to packets arriving on a locked port. The options are: DiscardDiscards packets from any unlearned source. ForwardForwards packets from an unknown source without learning the MAC address. ShutdownDiscards packets from any unlearned source, and shuts down the port. The port remains shut down until reactivated, or until the device is rebooted.
328
17
Security
Configuring 802.1X
TrapSelect to enable traps when a packet is received on a locked port. This is relevant for lock violations. For Classic Lock, this is any new address received. For Limited Dynamic Lock, this is any new address that exceeds the number of allowed addresses. Trap FrequencyEnter minimum time (in seconds) that elapses between traps.
STEP 4 Click Apply. Port security is modified, and the Running Configuration file is
updated.
Configuring 802.1X
Port-based access control has the effect of creating two types of access on the device ports. One type of access enables uncontrolled communication, regardless of the authorization state (uncontrolled port). The other type of access authorizes communication between a host and the device. The 802.1x is an IEEE standard for port-based network access control. The 802.1x framework enables a device (the supplicant) to request port access from a remote device (authenticator) to which it is connected. Only when the supplicant requesting port access is authenticated and authorized is it permitted to send data to the port. Otherwise, the authenticator discards the supplicant data unless the data is sent to a Guest VLAN and/or non-authenticated VLANs. Authentication of the supplicant is performed by an external RADIUS server through the authenticator. The authenticator monitors the result of the authentication. In the 802.1x standard, a device can be a supplicant and an authenticator at a port simultaneously, requesting port access and granting port access. However, this device is only the authenticator, and does not take on the role of a supplicant. The following varieties of 802.1X exist: Single session 802.1X: Single-session/single hostIn this mode, the device, as an authenticator, supports a single 802.1x session and grants permission to use the port to the authorized supplicant. All access by other devices received from the same port are denied until the authorized supplicant is no longer using the port or the access is to the unauthenticated VLAN or guest VLAN.
Cisco Small Business 300 Series Managed Switch Administration Guide
329
Security
Configuring 802.1X
17
Single session/multiple hostsThis follows the 802.1x standard. In this mode, the device as an authenticator allows any device to use a port as long as it has been granted permission.
Multi-Session 802.1XEvery device (supplicant) connecting to a port must be authenticated and authorized by the device (authenticator) separately in a different 802.1x session.
NOTE This is the only mode that supports Dynamic VLAN Assignment (DVA).
For a device to be authenticated and authorized at a port which is DVA-enabled: The RADIUS server must authenticate the device and dynamically assign a VLAN to the device. The user can configure an alternative VLAN ahead of time to be used if the RADIUS server does not assign a VLAN. The assigned VLAN must not be the default VLAN and must have been created on the device. The device must not be configured to use both a DVA and a MAC-based VLAN group together. A RADIUS server must support DVA with RADIUS attributes tunnel-type (64) = VLAN (13), tunnel-media-type (65) = 802 (6), and tunnel-privategroup-id = a VLAN ID.
The authentication methods can be: 802.1xThe device supports the authentication mechanism, as described in the standard, to authenticate and authorize 802.1x supplicants. MAC-basedThe device can be configured to use this mode to authenticate and authorized devices that do not support 802.1x. The device emulates the supplicant role on behalf of the non 802.1x capable devices, and uses the MAC address of the devices as the username and password when communicating with the RADIUS servers. MAC addresses for username and password must be entered in lower case and with no
330
17
A Guest VLAN must be defined The port must be Guest VLAN enabled.
Security
Configuring 802.1X
The packets from the first supplicant at the port before it is authorized must be untagged packets.
You can configure a port to use 802.1x, MAC-based, or 802.1x and MAC-based authentication. If a port is configured to use both 802.1x and MAC-based authentication, 802.1x has precedence over non-802.1x device.
The Guest VLAN, if configured, is a static VLAN with the following characteristics. Must be manually defined from an existing static VLAN. Is automatically available only to unauthorized devices or ports of devices that are connected and Guest-VLAN-enabled. If a port is Guest-VLAN-enabled, the device automatically adds the port as untagged member of the Guest VLAN when the port is not authorized, and removes the port from the Guest VLAN when the first supplicant of the port is authorized. The Guest VLAN cannot be used as the Voice VLAN and an unauthenticated VLAN.
331
Security
Configuring 802.1X
17
The device also uses the Guest VLAN for the authentication process at ports configured with Multiple Session mode and MAC-based authentication. Therefore, you must configure a Guest VLAN before you can use the MAC authentication mode.
Note the following: On this page, DVA can be activated on a port by selecting the RADIUS VLAN Assignment field. You can select the Guest VLAN field to have untagged incoming frames go to the guest VLAN. Define host authentication parameters for each port using the Port Authentication page. View 802.1X authentication history using the Authenticated Hosts page.
332
17
Security
Configuring 802.1X
Port-Based AuthenticationEnable or disable port-based, 802.1X authentication. Authentication MethodSelect the user authentication methods. The options are: RADIUS, NonePerform port authentication first by using the RADIUS server. If no response is received from RADIUS (for example, if the server is down), then no authentication is performed, and the session is permitted. If the server is available but the user credentials are incorrect, access is denied and the session terminated. RADIUSAuthenticate the user on the RADIUS server. If no authentication is performed, the session is not permitted. NoneDo not authenticate the user. Permit the session.
Guest VLANSelect to enable the use of a Guest VLAN for unauthorized ports. If a Guest VLAN is enabled, all unauthorized ports automatically join the VLAN selected in the Guest VLAN ID field. If a port is later authorized, it is removed from the Guest VLAN. Guest VLAN IDSelect the guest VLAN from the list of VLANs. Guest VLAN TimeoutDefine a time period: After linkup, if the software does not detect the 802.1X supplicant, or the authentication has failed, the port is added to the Guest VLAN, only after the Guest VLAN timeout period has expired. If the port state changes from Authorized to Not Authorized, the port is added to the Guest VLAN only after the Guest VLAN timeout has expired.
The VLAN Authentication Table displays all VLANs, and indicates whether authentication has been enabled on them.
STEP 3 Click Apply. The 802.1X properties are written to the Running Configuration file.
333
Security
Configuring 802.1X
17
Configuring Unauthenticated VLANs
When a port is 802.1x-enabled, unauthorized ports or devices are not allowed to access a VLAN unless the VLAN is a Guest VLAN or an unauthenticated VLAN. You can make a static VLAN an authenticated VLAN by using the procedure in the Defining 802.1X Properties section, allowing both 802.1x authorized and unauthorized devices or ports to send or receive packets to or from unauthenticated VLANs. You must manually add ports to VLANs by using the Port to VLAN page.
STEP 1 Click Security > 802.1X > Properties. STEP 2 Select a VLAN, and click Edit . STEP 3 Select a VLAN. STEP 4 Optionally, uncheck Authentication to make the VLAN an unauthenticated VLAN. STEP 5 Click Apply, and the Running Configuration file is updated.
334
17
Security
Configuring 802.1X
Current Port ControlDisplays the current port authorization state. If the state is Authorized, the port is either authenticated or the Administrative Port Control is Force Authorized. Conversely, if the state is Unauthorized, then the port is either not authenticated or the Administrative Port Control is Force Unauthorized. Administrative Port ControlSelect the Administrative Port Authorization state. The options are: Force UnauthorizedDenies the interface access by moving the interface into the unauthorized state. The device does not provide authentication services to the client through the interface. AutoEnables port-based authentication and authorization on the device. The interface moves between an authorized or unauthorized state based on the authentication exchange between the device and the client. Force AuthorizedAuthorizes the interface without authentication.
RADIUS VLAN AssignmentSelect to enable Dynamic VLAN assignment on the selected port. Dynamic VLAN assignment is possible only when the 802.1X mode is set to Multiple Session. (After authentication, the port joins the supplicant VLAN as an untagged port in that VLAN.) Alternate VLAN AssignmentIf RADIUS VLAN Assignment is enabled, you can select one of the following options: EnabledSelect an alternative VLAN that is used if the RADUS server does not assign a VLAN. DisabledIf the RADIUS server does not assign a VLAN, the authentication fails.
Guest VLANSelect to indicate that the usage of a previously-defined Guest VLAN is enabled for the device. The options are: SelectedEnables using a Guest VLAN for unauthorized ports. If a Guest VLAN is enabled, the unauthorized port automatically joins the VLAN selected in the Guest VLAN ID field in the 802.1X Port Authentication page. After an authentication failure, and if Guest VLAN is activated globally on a given port, the guest VLAN is automatically assigned to the unauthorized ports as an Untagged VLAN. ClearedDisables Guest VLAN on the port.
335
Security
Configuring 802.1X
17
Authentication MethodSelect the authentication method for the port. The options are: 802.1X Only802.1X authentication is the only authentication method performed on the port. MAC OnlyPort is authenticated based on the supplicant MAC address. Only 8 MAC-based authentications can be used on the port. 802.1X and MACBoth 802.1X and MAC-based authentication are performed on the device. The 802.1X authentication takes precedence.
NOTE For MAC authentication to succeed, the RADIUS server supplicant
username and password must be the supplicant MAC address. The MAC address must be in lower case letters and entered without the : or - separators; for example: 0020aa00bbcc. Periodic ReauthenticationSelect to enable port re-authentication attempts after the specified Reauthentication Period. Reauthentication PeriodEnter the number of seconds after which the selected port is reauthenticated. Reauthenticate NowSelect to enable immediate port re-authentication. Authenticator StateDisplays the defined port authorization state. The options are: InitializeIn process of coming up. Force-AuthorizedControlled port state is set to Force-Authorized (forward traffic). Force-UnauthorizedControlled port state is set to Force-Unauthorized (discard traffic).
NOTE If the port is not in Force-Authorized or Force-Unauthorized, it is in
Auto Mode and the authenticator displays the state of the authentication in progress. After the port is authenticated, the state is shown as Authenticated. Time RangeEnable a limit on the time that the specific port is authorized for use if 802.1x has been enabled (Port -Based authentication is checked). Time Range NameSelect the profile that specifies the time range. Quiet PeriodEnter the number of seconds that the device remains in the quiet state following a failed authentication exchange.
336
17
Security
Configuring 802.1X
Resending EAPEnter the number of seconds that the device waits for a response to an Extensible Authentication Protocol (EAP) request/identity frame from the supplicant (client) before resending the request. Max EAP RequestsEnter the maximum number of EAP requests that can be sent. If a response is not received after the defined period (supplicant timeout), the authentication process is restarted. Supplicant TimeoutEnter the number of seconds that lapses before EAP requests are resent to the supplicant. Server TimeoutEnter the number of seconds that lapses before the device resends a request to the authentication server. Termination CauseDisplays the reason for which port authentication was terminated, if applicable.
STEP 4 Click Apply. The port settings are written to the Running Configuration file.
337
Security
Configuring 802.1X
17
To define 802.1X advanced settings for ports:
STEP 1 Click Security > 802.1X > Host and Session Authentication.
802.1X authentication parameters are described for all ports. All fields except the following are described in the Edit Host and Session Authentication page. StatusDisplays the host status. An asterisk indicates that the port is either not linked or is down. The options are: UnauthorizedEither the port control is Force Unauthorized and the port link is down, or the port control is Auto but a client has not been authenticated via the port. Force-AuthorizedClients have full port access. Single-host LockPort control is Auto and only a single client has been authenticated by using the port. No Single HostPort control is Auto and Multiple Hosts mode is enabled. At least one client has been authenticated. Not in Auto ModeAuto port control is not enabled.
Number of ViolationsDisplays the number of packets that arrive on the interface in single-host mode, from a host whose MAC address is not the supplicant MAC address.
STEP 2 Select a port, and click Edit. STEP 3 Enter the parameters.
InterfaceEnter a port number for which host authentication is enabled. Host AuthenticationSelect one of the modes. These modes are described above in Defining Host and Session Authentication. The following fields are only relevant if you select Single in the Host Authentication field.
Single Host Violation Settings: Action on ViolationSelect the action to be applied to packets arriving in Single Session/Single Host mode, from a host whose MAC address is not the supplicant MAC address. The options are: Protect (Discard)Discards the packets. Restrict (Forward)Forwards the packets.
338
17
Traps (on single host violation)Select to enable traps.
Security
Defining Time Ranges
ShutdownDiscards the packets and shuts down the port. The ports remains shut down until reactivated, or until the device is rebooted.
Trap Frequency (on Single Host Violation)Defines how often traps are sent to the host. This field can be defined only if multiple hosts are disabled.
STEP 4 Click Apply. The settings are written to the Running Configuration file.
This page displays the following fields: User NameSupplicant names that were authenticated on each port. PortNumber of the port. Session Time (DD:HH:MM:SS)Amount of time that the supplicant was logged on the port. Authentication MethodMethod by which the last session was authenticated. The options are: NoneNo authentication is applied; it is automatically authorized. RADIUSSupplicant was authenticated by a RADIUS server.
339
Security
Denial of Service Prevention
17
340
17
Security
Denial of Service Prevention
Martian AddressesMartian addresses are illegal from the point of view of the IP protocol. See Martian Addresses for more details. ICMP AttackSending malformed ICMP packets or overwhelming number of ICMP packets to the victim that might lead to a system crash. IP FragmentationMangled IP fragments with overlapping, over-sized payloads are sent to the device. This can crash various operating systems due to a bug in their TCP/IP fragmentation re-assembly code. Windows 3.1x, Windows 95 and Windows NT operating systems, as well as versions of Linux prior to versions 2.0.32 and 2.1.63 are vulnerable to this attack. Stacheldraht DistributionThe attacker uses a client program to connect to handlers, which are compromised systems that issue commands to zombie agents, which in turn facilitate the DoS attack. Agents are compromised via the handlers by the attacker. Using automated routines to exploit vulnerabilities in programs that accept remote connections running on the targeted remote hosts. Each handler can control up to a thousand agents.
Invasor TrojanA trojan enables the attacker to download a zombie agent (or the trojan may contain one). Attackers can also break into systems using automated tools that exploit flaws in programs that listen for connections from remote hosts. This scenario primarily concerns the device when it serves as a server on the web. Back OrifaceTrojanThis is a variation of a trojan that uses Back Oriface software to implant the trojan.
341
Security
Denial of Service Prevention
17
Prevent TCP connections from a specific interface (SYN Filtering page) and rate limit the packets (SYN Rate Protection page) Configure the blocking of certain ICMP packets (ICMP Filtering page) Discard fragmented IP packets from a specific interface (IP Fragments Filtering page) Deny attacks from Stacheldraht Distribution, Invasor Trojan, and Back Orifice Trojan (Security Suite Settings page).
Default Configuration
The DoS Prevention feature has the following defaults: The DoS Prevention feature is disabled by default. SYN-FIN protection is enabled by default (even if DoS Prevention is disabled). If SYN protection is enabled, the default protection mode is Block and Report . The default threshold is 30 SYN packets per second. All other DoS Prevention features are disabled by default.
or advanced QoS policies that are bound to a port. ACL and advanced QoS policies are not active when a port has DoS Protection enabled on it. To configure DoS Prevention global settings and monitor SCT:
342
17
Security Suite Settings displays.
Security
Denial of Service Prevention
STEP 1 Click Security > Denial of Service Prevention > Security Suite Settings. The
DisableDisable the feature. System-Level PreventionEnable that part of the feature that prevents attacks from Stacheldraht Distribution, Invasor Trojan, and Back Orifice Trojan.
selected, enable one or more of the following DoS Prevention options: Stacheldraht DistributionDiscards TCP packets with source TCP port equal to 16660. Invasor TrojanDiscards TCP packets with destination TCP port equal to 2140 and source TCP port equal to 1024. Back Orifice TrojanDiscards UDP packets with destination UDP port equal to 31337 and source UDP port equal to 1024.
STEP 6 Click Apply. The Denial of Service prevention Security Suite settings are written to
the Running Configuration file. If Interface-Level Prevention is selected, click the appropriate Edit button to configure the desired prevention.
343
Security
Denial of Service Prevention
17
SYN Protection
The network ports might be used by hackers to attack the device in a SYN attack, which consumes TCP resources (buffers) and CPU power. Since the CPU is protected using SCT, TCP traffic to the CPU is limited. However, if one or more ports are attacked with a high rate of SYN packets, the CPU receives only the attacker packets, thus creating Denial-of-Service. When using the SYN protection feature, the CPU counts the SYN packets ingressing from each network port to the CPU per second. If the number is higher than the specific, user-defined threshold, a deny SYN with MAC-to-me rule is applied on the port. This rule is unbound from the port every user-defined interval (SYN Protection Period). To configure SYN protection:
STEP 1 Click Security > Denial of Service Prevention > SYN Protection. STEP 2 Enter the parameters.
Block SYN-FIN PacketsSelect to enable the feature. All TCP packets with both SYN and FIN flags are dropped on all ports. SYN Protection ModeSelect between three modes: DisableThe feature is disabled on a specific interface. ReportGenerates a SYSLOG message.The status of the port is changed to Attacked when the threshold is passed. Block and ReportWhen a TCP SYN attack is identified, TCP SYN packets destined for the system are dropped and the status of the port is changed to Blocked.
SYN Protection ThresholdNumber of SYN packets per second before SYN packets will be blocked (deny SYN with MAC-to-me rule will be applied on the port). SYN Protection PeriodTime in seconds before unblocking the SYN packets (the deny SYN with MAC-to-me rule is unbound from the port).
STEP 3 Click Apply. SYN protection is defined, and the Running Configuration file is
updated. The SYN Protection Interface Table displays the following fields for every port or LAG (as requested by the user)
344
17
Security
Denial of Service Prevention
Current StatusInterface status. The possible values are: NormalNo attack was identified on this interface. BlockedTraffic is not forwarded on this interface. AttackedAttack was identified on this interface.
Last AttackDate of last SYN-FIN attack identified by the system and the system action (Reported or Blocked and Reported).
Martian Addresses
The Martian Addresses page enables entering IP addresses that indicate an attack if they are seen on the network. Packets from these addresses are discarded. The device supports a set of reserved Martian addresses that are illegal from the point of view of the IP protocol. The supported reserved Martian addresses are: Addresses defined to be illegal in the Martian Addresses page. Addresses that are illegal from the point of view of the protocol, such as loopback addresses, including addresses within the following ranges: 0.0.0.0/8 (Except 0.0.0.0/32 as a Source Address)Addresses in this block refer to source hosts on this network. 127.0.0.0/8Used as the Internet host loopback address. 192.0.2.0/24Used as the TEST-NET in documentation and example codes. 224.0.0.0/4 (As a Source IP Address)Used in IPv4 Multicast address assignments, and was formerly known as Class D Address Space. 240.0.0.0/4 (Except 255.255.255.255/32 as a Destination Address)Reserved address range, and was formerly known as Class E Address Space.
You can also add new Martian Addresses for DoS prevention. Packets that have a Martian addresses are discarded. To define Martian addresses:
STEP 1 Click Security > Denial of Service Prevention > Martian Addresses. STEP 2 Select Reserved Martian Addresses and click Apply to include the reserved
345
Security
Denial of Service Prevention
17
IP VersionIndicates the supported IP version. Currently, support is only offered for IPv4. IP AddressEnter an IP addresses to reject. The possible values are:
STEP 3 To add a Martian address click Add. STEP 4 Enter the parameters.
MaskEnter the mask of the IP address to define a range of IP addresses to reject. The values are: -
Network MaskNetwork mask in dotted decimal format. Prefix LengthEnter the prefix of the IP address to define the range of IP addresses for which Denial of Service prevention is enabled.
STEP 5 Click Apply. The Martian addresses are written to the Running Configuration file.
SYN Filtering
The SYN Filtering page enables filtering TCP packets that contain a SYN flag, and are destined for one or more ports. To define a SYN filter:
STEP 1 Click Security > Denial of Service Prevention > SYN Filtering. STEP 2 Click Add. STEP 3 Enter the parameters.
InterfaceSelect the interface on which the filter is defined. IPv4 AddressEnter the IP address for which the filter is defined, or select All Addresses. Network MaskEnter the network mask for which the filter is enabled in IP address format. TCP PortSelect the destination TCP port being filtered: Known PortsSelect a port from the list.
346
17
updated. User DefinedEnter a port number.
Security
Denial of Service Prevention
STEP 4 Click Apply. The SYN filter is defined, and the Running Configuration file is
This page appears the SYN rate protection currently defined per interface.
STEP 2 Click Add. STEP 3 Enter the parameters.
InterfaceSelect the interface on which the rate protection is being defined. IP AddressEnter the IP address for which the SYN rate protection is defined or select All Addresses. If you enter the IP address, enter either the mask or prefix length. Network MaskSelect the format for the subnet mask for the source IP address, and enter a value in one of the field: MaskSelect the subnet to which the source IP address belongs and enter the subnet mask in dotted decimal format. Prefix LengthSelect the Prefix Length and enter the number of bits that comprise the source IP address prefix.
347
Security
Denial of Service Prevention
17
STEP 4 Click Apply. The SYN rate protection is defined, and the Running Configuration is
updated.
ICMP Filtering
The ICMP Filtering page enables the blocking of ICMP packets from certain sources. This can reduce the load on the network in case of an ICMP attack. To define ICMP filtering:
STEP 1 Click Security > Denial of Service Prevention > ICMP Filtering. STEP 2 Click Add. STEP 3 Enter the parameters.
InterfaceSelect the interface on which the ICMP filtering is being defined. IP AddressEnter the IPv4 address for which the ICMP packet filtering is activated or select All Addresses to block ICMP packets from all source addresses. If you enter the IP address, enter either the mask or prefix length. Network MaskSelect the format for the subnet mask for the source IP address, and enter a value in one of the field: MaskSelect the subnet to which the source IP address belongs and enter the subnet mask in dotted decimal format. Prefix LengthSelect the Prefix Length and enter the number of bits that comprise the source IP address prefix.
STEP 4 Click Apply. The ICMP filtering is defined, and the Running Configuration is
updated.
IP Fragmented Filtering
The IP Fragmented page enables blocking fragmented IP packets. To configure fragmented IP blocking:
STEP 1 Click Security > Denial of Service Prevention > IP Fragments Filtering. STEP 2 Click Add. STEP 3 Enter the parameters.
348
17
Security
IP Source Guard
InterfaceSelect the interface on which the IP fragmentation is being defined. IP AddressEnter an IP network from which the fragmented IP packets is filtered or select All Addresses to block IP fragmented packets from all addresses. If you enter the IP address, enter either the mask or prefix length. Network MaskSelect the format for the subnet mask for the source IP address, and enter a value in one of the field: MaskSelect the subnet to which the source IP address belongs and enter the subnet mask in dotted decimal format. Prefix LengthSelect the Prefix Length and enter the number of bits that comprise the source IP address prefix.
STEP 4 Click Apply. The IP fragmentation is defined, and the Running Configuration file is
updated.
IP Source Guard
IP Source Guard is a security feature that can be used to prevent traffic attacks caused when a host tries to use the IP address of its neighbor. When IP Source Guard is enabled, the device only transmits client IP traffic to IP addresses contained in the DHCP Snooping Binding database. This includes both addresses added by DHCP Snooping and manually-added entries. If the packet matches an entry in the database, the device forwards it. If not, it is dropped.
349
Security
IP Source Guard
17
The interface is DHCP untrusted. All packets on trusted ports are forwarded. If a port is DHCP trusted, filtering of static IP addresses can be configured, even though IP Source Guard is not active in that condition by enabling IP Source Guard on the port. When the ports status changes from DHCP untrusted to DHCP trusted, the static IP address filtering entries remain in the Binding database, but they become inactive. Port security cannot be enabled if source IP and MAC address filtering is configured on a port. IP Source Guard uses TCAM resources and requires a single TCAM rule per IP Source Guard address entry. If the number of IP Source Guard entries exceeds the number of available TCAM rules, the extra addresses are inactive.
Filtering
If IP Source Guard is enabled on a port then: DHCP packets allowed by DHCP Snooping are permitted. If source IP address filtering is enabled: IPv4 traffic: Only traffic with a source IP address that is associated with the port is permitted. Non IPv4 traffic: Permitted (Including ARP packets).
350
17
Source Guard > Interface Settings page.
Security
IP Source Guard
STEP 5 Enable IP Source Guard on the untrusted interfaces as required in the Security > IP
STEP 6 View entries to the Binding database in the Security > IP Source Guard > Binding
Database page.
See Interactions with Other Features for more information about enabling IP Source Guard on interfaces. To configure IP Source Guard on interfaces:
STEP 1 Click Security > IP Source Guard > Interface Settings. STEP 2 Select port/LAG from the Filter field and click Go. The ports/LAGs on this unit are
displayed along with the following: IP Source Guard Indicates whether IP Source Guard is enabled on the port. DHCP Snooping Trusted InterfaceIndicates whether this is a DHCP trusted interface.
STEP 3 Select the port/LAG and click Edit . Select Enable in the IP Source Guard field to
351
Security
IP Source Guard
17
Binding Database
IP Source Guard uses the DHCP Snooping Binding database to check packets from untrusted ports. If the device attempts to write too many entries to the DHCP Snooping Binding database, the excessive entries are maintained in an inactive status. Entries are deleted when their lease time expires and so inactive entries may be made active. See DHCPv4 Snooping/Relay.
NOTE The Binding Database page only displays the entries in the DHCP Snooping
Binding database defined on IP-Source-Guard-enabled ports. To view the DHCP Snooping Binding database and see TCAM usage, set Insert Inactive:
STEP 1 Click Security > IP Source Guard > Binding Database. STEP 2 The DHCP Snooping Binding database uses TCAM resources for managing the
database. Complete the Insert Inactive field to select how frequently the device should attempt to activate inactive entries. It has the following options: Retry FrequencyThe frequency with which the TCAM resources are checked. Never-Never try to reactivate inactive addresses.
STEP 3 Click Apply to save the above changes to the Running Configuration and/or Retry
Now to check TCAM resources. The entries in the Binding database are displayed: VLAN IDVLAN on which packet is expected. MAC AddressMAC address to be matched. IP AddressIP address to be matched. InterfaceInterface on which packet is expected. StatusDisplays whether interface is active. TypeDisplays whether entry is dynamic or static. ReasonIf the interface is not active, displays the reason. The following reasons are possible: No ProblemInterface is active.
352
17
Trusted PortPort has become trusted.
Security
Dynamic ARP Inspection
To see a subset of these entries, enter the relevant search criteria and click Go.
353
Security
Dynamic ARP Inspection
17
Hosts A, B, and C are connected to the switch on interfaces A, B and C, all of which are on the same subnet. Their IP, MAC addresses are shown in parentheses; for example, Host A uses IP address IA and MAC address MA. When Host A needs to communicate with Host B at the IP layer, it broadcasts an ARP request for the MAC address associated with IP address IB. Host B responds with an ARP reply. The switch and Host A update their ARP cache with the MAC and IP of Host B. Host C can poison the ARP caches of the switch, Host A, and Host B by broadcasting forged ARP responses with bindings for a host with an IP address of IA (or IB) and a MAC address of MC. Hosts with poisoned ARP caches use the MAC address MC as the destination MAC address for traffic intended for IA or IB, which enables Host C intercepts that traffic. Because Host C knows the true MAC addresses associated with IA and IB, it can forward the intercepted traffic to those hosts by using the correct MAC address as the destination. Host C has inserted itself into the traffic stream from Host A to Host B, the classic man-in-the-middle attack.
ARP inspection is performed only on untrusted interfaces. ARP packets that are received on the trusted interface are simply forwarded. Upon packet arrival on untrusted interfaces the following logic is implemented: Search the ARP access control rules for the packet's IP/MAC addresses. If the IP address is found and the MAC address in the list matches the packet's MAC address, then the packet is valid; otherwise it is not. If the packet's IP address was not found, and DHCP Snooping is enabled for the packets VLAN, search the DHCP Snooping Binding database for the packet's <VLAN - IP address> pair. If the <VLAN - IP address> pair was found, and the MAC address and the interface in the database match the packet's MAC address and ingress interface, the packet is valid. If the packet's IP address was not found in the ARP access control rules or in the DHCP Snooping Binding database the packet is invalid and is dropped. A SYSLOG message is generated.
354
17
Security
Dynamic ARP Inspection
If the ARP Packet Validation option is selected (Properties page), the following additional validation checks are performed: Source MAC Compares the packets source MAC address in the Ethernet header against the senders MAC address in the ARP request. This check is performed on both ARP requests and responses. Destination MAC Compares the packets destination MAC address in the Ethernet header against the destination interfaces MAC address. This check is performed for ARP responses. IP Addresses Compares the ARP body for invalid and unexpected IP addresses. Addresses include 0.0.0.0, 255.255.255.255, and all IP Multicast addresses.
Packets with invalid ARP Inspection bindings are logged and dropped. Up to 1024 entries can be defined in the ARP Access Control table.
ARP Defaults
ARP Defaults Table Option Dynamic ARP Inspection ARP Packet Validation ARP Inspection Enabled on VLAN Log Buffer Interval Default State Not enabled. Not enabled Not enabled SYSLOG message generation for dropped packets is enabled at 5 seconds interval
355
Security
Dynamic ARP Inspection
17
ARP Inspection Work Flow
To configure ARP Inspection:
STEP 1 Enable ARP Inspection and configure various options in the Security > ARP
Rules for each VLAN in the Security > ARP Inspection > VLAN Settings page.
Enter the following fields: ARP Inspection StatusSelect to enable ARP Inspection. ARP Packet ValidationSelect to enable the following validation checks: Source MAC Compares the packets source MAC address in the Ethernet header against the senders MAC address in the ARP request. This check is performed on both ARP requests and responses. Destination MAC Compares the packets destination MAC address in the Ethernet header against the destination interfaces MAC address. This check is performed for ARP responses. IP Addresses Compares the ARP body for invalid and unexpected IP addresses. Addresses include 0.0.0.0, 255.255.255.255, and all IP Multicast addresses.
Log Buffer IntervalSelect one of the following options: Retry FrequencyEnable sending SYSLOG messages for dropped packets. Entered the frequency with which the messages are sent.
356
17
updated.
Security
Dynamic ARP Inspection
STEP 2 Click Apply. The settings are defined, and the Running Configuration file is
Configuration file.
ARP Access Control NameEnter a user-created name. MAC AddressMAC address of packet. IP AddressIP address of packet.
357
Security
Dynamic ARP Inspection
17
updated.
STEP 4 Click Apply. The settings are defined, and the Running Configuration file is
STEP 4 Click Apply. The settings are defined, and the Running Configuration file is
updated.
updated.
358
17
Security
Dynamic ARP Inspection
359
18
Security: Secure Sensitive Data Management
Secure Sensitive Data (SSD) is an architecture that facilitates the protection of sensitive data on a device, such as passwords and keys. The facility makes use of passphrases, encryption, access control, and user authentication to provide a secure solution to managing sensitive data. The facility is extended to protect the integrity of configuration files, to secure the configuration process, and to support SSD zero-touch auto configuration. Introduction SSD Rules SSD Properties Configuration Files SSD Management Channels Menu CLI and Password Recovery Configuring SSD
Introduction
SSD protects sensitive data on a device, such as passwords and keys, permits and denies access to sensitive data encrypted and in plain text based on user credentials and SSD rules, and protects configuration files containing sensitive data from being tampered with. In addition, SSD enables the secure backup and sharing of configuration files containing sensitive data. SSD provides users with the flexibility to configure the desired level of protection on their sensitive data; from no protection with sensitive data in plaintext, minimum
protection with encryption based on the default passphrase, and better protection with encryption based on user-defined passphrase.
360
18
SSD grants read permission to sensitive data only to authenticated and authorized users, and according to SSD rules. A device authenticates and authorizes management access to users through the user authentication process.
Whether or not SSD is used, it is recommended that an administrator should secure the authentication process by using the local authentication database, and/ or secure the communication to external authentication server (RADIUS and TACACS) used in the user authentication process.
In summary, SSD protects sensitive data on a device with SSD rules, SSD properties, and user authentication. And SSD rules, SSD properties, and user authentication configurations of the device are themselves sensitive data protected by SSD.
SSD Management
SSD management includes a collection of configuration parameters that define the handling and security of sensitive data. The SSD configuration parameters themselves are sensitive data and are protected under SSD. All configuration of SSD is performed through the SSD pages that are only available to users with the correct permissions (see SSD Rules).
SSD Rules
SSD rules define the read permissions and default read mode given to a user session on a management channel. An SSD rule is uniquely identified by its user and SSD management channel. Different SSD rules might exist for the same user but for different channels, and conversely, different rules might exist for the same channel but for different users. Read permissions determine how sensitive data can be viewed: in only encrypted form, in only plaintext form, in both encrypted or plaintext, or no permission to view sensitive data. The SSD rules themselves are protected as sensitive data. A device can support a total of 32 SSD rules. A device grants a user the SSD read permission of the SSD rule that best matches the user identity/credential and the type of management channel from which the user is/will access the sensitive data. A device comes with a set of default SSD rules. An administrator can add, delete, and change SSD rules as desired.
361
18
NOTE A device may not support all the channels defined by SSD.
User NameIf user type is Specific, a user name is required. Channel. Type of SSD management channel to which the rule is applied. The channel types supported are: SecureSpecifies the rule applies only to secure channels. Depending on the device, it may support some or all of the following secure channels: Console port interface, SCP, SSH, and HTTPS. InsecureSpecifies that this rule applies only to insecure channels. Depending on the device, it may support some or all of the following insecure channels: Telnet, TFTP, and HTTP. Secure XML SNMPSpecifies that this rule applies only to XML over HTTPS or SNMPv3 with privacy. A device may or may not support all of the secure XML and SNMP channels. Insecure XML SNMPSpecifies that this rule applies only to XML over HTTP or SNMPv1/v2 and SNMPv3 without privacy. A device may or may not support all of the secure XML and SNMP channels.
Read PermissionThe read permissions associate with the rules. These can be the following: (Lowest) ExcludeUsers are not permitted to access sensitive data in any form. (Middle) Encrypted OnlyUsers are permitted to access sensitive data as encrypted only.
362
18
-
(Higher) Plaintext OnlyUsers are permitted to access sensitive data in plaintext only. Users will also have read and write permission to SSD parameters as well. (Highest) BothUsers have both encrypted and plaintext permissions and are permitted to access sensitive data as encrypted and in plaintext. Users will also have read and write permission to SSD parameters as well.
Each management channel allows specific read permissions. The following summarizes these. Table 1 Read Permissions Allowed per Management Channel Management Channel Secure Insecure Secure XML SNMP Insecure XML SNMP Read Permission Options Allowed Both, Encrypted Only Both, Encrypted Only Exclude, Plaintext Only Exclude, Plaintext Only
Default Read ModeAll default read modes are subjected to the read permission of the rule. The following options exist, but some might be rejected, depending on the read permission. If the user-defined read permission for a user is Exclude (for example), and the default read mode is Encrypted, the user-defined read permission prevails. ExcludeDo not allow reading sensitive data. EncryptedSensitive data is presented in encrypted form. PlaintextSensitive data is presented in plaintext form.
Each management channel allows specific read presumptions. The following summarizes these. Table 2 Default Read Modes for Read Permissions Read Permission Exclude Encrypted Only Plaintext Only Default Read Mode Allowed Exclude *Encrypted *Plaintext
363
18
Default Read Mode Allowed *Plaintext, Encrypted
Table 2
* The Read mode of a session can be temporarily changed in the SSD Properties page if the new read mode does not violate the read permission.
NOTE Note the following:
The default Read mode for the Secure XML SNMP and Insecure XML SNMP management channels must be identical to their read permission. Read permission Exclude is allowed only for Secure XML SNMP and Insecure XML SNMP management channels; Exclude is not allowed for regular secure and insecure channels. Exclude sensitive data in secure and Insecure XML-SNMP management channels means that the sensitive data is presented as a 0 (meaning null string or numeric 0). If the user wants to view sensitive data, the rule must be changed to plaintext. By default, an SNMPv3 user with privacy and XML-over-secure channels permissions is considered to be a level-15 user. SNMP users on Insecure XML and SNMP (SNMPv1,v2, and v3 with no privacy) channel are considered as All users. SNMP community names are not used as user names to match SSD rules. Access by a specific SNMPv3 user can be controlled by configuring an SSD rule with a user name matching the SNMPv3 user name. There must always be at least one rule with read permission: Plaintext Only or Both, because only users with those permissions are able to access the SSD pages. Changes in the default read mode and read permissions of a rule will become effective, and will be applied to the affected user(s) and channel of all active management sessions immediately, excluding the session making the changes even if the rule is applicable. When a rule is changed (add, delete, edit), a system will update all the affected CLI/GUI sessions.
NOTE When the SSD rule applied upon the session login is changed from
within that session, the user must log out and back in to see the change.
364
18
NOTE When doing a file transfer initiated by an XML or SNMP command, the
underlying protocol used is TFTP. Therefore, the SSD rule for insecure channel will apply.
non SSD related mechanism If a user from a channel issues an action that uses an alternate channel, the device applies the read permission and default read mode from the SSD rule that match the user credential and the alternate channel. For example, if a user logs in via a secure channel and starts a TFTP upload session, the SSD read permission of the user on the insecure channel (TFTP) is applied
Rule Key
365
18
Rule Action Read Permission Encrypted Only Encrypted Only Default Read Mode Encrypted Encrypted
Rule Key
The default rules can be modified, but they cannot be deleted. If the SSD default rules have been changed, they can be restored.
SSD Properties
SSD properties are a set of parameters that, in conjunction with the SSD rules, define and control the SSD environment of a device. The SSD environment consists of these properties: Controlling how the sensitive data is encrypted. Controlling the strength of security on configuration files. Controlling how the sensitive data is viewed within the current session.
366
18
Passphrase
A passphrase is the basis of the security mechanism in the SSD feature, and is used to generate the key for the encryption and decryption of sensitive data. Sx200, Sx300, Sx500, and SG500X/ESW2-550X series switches that have the same passphrase are able to decrypt each other's sensitive data encrypted with the key generated from the passphrase. A passphrase must comply with the following rules: LengthBetween 8-16 characters. Character ClassesThe passphrase must have at least one upper case character, one lower case character, one numeric character, and one special character e.g. #,$.
Local Passphrase
A device maintains a local passphrase which is the passphrase of its Running Configuration. SSD normally performs encryption and decryption of sensitive data with the key generated from the local passphrase. The local passphrase can be configured to be either the default passphrase or a user-defined passphrase. By default, the local passphrase and default passphrase are identical. It can be changed by administrative actions from either the Command Line Interface (if available) or the web-based interface. It is
367
18
automatically changed to the passphrase in the startup configuration file, when the startup configuration becomes the running configuration of the device. When a device is reset to factory default, the local passphrase is reset to the default passphrase.
After a device is reset to the factory default, its local passphrase is reset to the default passphrase. As a result, the device will be not able to decrypt any sensitive data encrypted based on a user-defined passphrase entered from a management session (GUI/CLI), or in any configuration file with restricted mode, including the files created by the device itself before it is reset to factory default. This remains until the device is manually reconfigured with the user-defined passphrase, or learns the user-defined passphrase from a configuration file.
!
CAUTION Any modification made to a configuration file that is integrity protected is
considered tampering.
368
18
A device determines whether the integrity of a configuration file is protected by examining the File Integrity Control command in the file's SSD Control block. If a file is integrity protected but a device finds the integrity of the file is not intact, the device rejects the file. Otherwise, the file is accepted for further processing. A device checks for the integrity of a text-based configuration file when the file is downloaded or copied to the Startup Configuration file.
Read Mode
Each session has a Read mode. This determines how sensitive data appears. The Read mode can be either Plaintext, in which case sensitive data appears as regular text, or Encrypted, in which sensitive data appears in its encrypted form.
Configuration Files
A configuration file contains the configuration of a device. A device has a Running Configuration file, a Startup Configuration file, a Mirror Configuration file (optionally), and a Backup Configuration file. A user can manually upload and download a configuration file to and from a remote file-server. A device can automatically download its Startup Configuration from a remote file server during the auto configuration stage using DHCP. Configuration files stored on remote file servers are referred to as remote configuration files. A Running Configuration file contains the configuration currently being used by a device. The configuration in a Startup Configuration file becomes the Running Configuration after reboot. Running and Startup Configuration files are formatted in internal format. Mirror, Backup, and the remote configuration files are text-based files usually kept for archive, records, or recovery. During copying, uploading, and downloading a source configuration file, a device automatically transforms the source content to the format of the destination file if the two files are of different formats.
369
18
A text-based configuration that does not include an SSD indicator is considered not to contain sensitive data. The SSD indicator is used to enforce SSD read permissions on text-based configuration files, but is ignored when copying the configuration files to the Running or Startup Configuration file.
The SSD indicator in a file is set according to the users instruction, during copy, to include encrypted, plaintext or exclude sensitive data from a file.
370
18
If there is a passphrase in the SSD control block of the source configuration file, the device will reject the source file, and the copy fails if there is encrypted sensitive data in the file not encrypted by the key generated from the passphrase in the SSD control block. If there is an SSD control block in the source configuration file and the file fails the SSD integrity check, and/or file integrity check, the device rejects the source file and fails the copy. If there is no passphrase in the SSD control block of the source configuration file, all the encrypted sensitive data in the file must be encrypted by either the key generated from the local passphrase, or the key generated from the default passphrase, but not both. Otherwise, the source file is rejected and the copy fails. The device configures the passphrase, passphrase control, and file integrity, if any, from the SSD Control Block in the source configuration file to the Startup Configuration file. It configures the Startup Configuration file with the passphrase that is used to generate the key to decrypt the sensitive data in the source configuration file. Any SSD configurations that are not found are reset to the default. If there is an SSD control block in the source configuration file and the file contains plaintext, sensitive data excluding the SSD configurations in the SSD control block, the file is accepted.
371
18
When copied from a source file, the copy will fail if the passphrase in the source file is in plaintext. If the passphrase is encrypted, it is ignored. When directly configuring the passphrase, (non file copy), in the Running Configuration, the passphrase in the command must be entered in plaintext. Otherwise, the command is rejected. Configuration commands with encrypted sensitive data, that are encrypted with the key generated from the local passphrase, are configured into the Running Configuration. Otherwise, the configuration command is in error, and is not incorporated into the Running Configuration file.
372
18
A user with Exclude permission cannot access mirror and backup configuration files with their file SSD indicator showing either encrypted or plaintext sensitive data.
The user should not manually change the file SSD indicator that conflicts with the sensitive data, if any, in the file. Otherwise, plaintext sensitive data may be unexpectedly exposed.
fields, as well as DHCP option 150 and statically configured on the device. The user can safely auto configure target devices with encrypted sensitive data, by first creating the configuration file that is to be used in the auto configuration from a device that contains the configurations. The device must be configured and instructed to: Encrypt the sensitive data in the file Enforce the integrity of the file content Include the secure, authentication configuration commands and SSD rules that properly control and secure the access to devices and the sensitive data
If the configuration file was generated with a user passphrase and SSD file passphrase control is Restricted, the resulting configuration file can be autoconfigured to the desired target devices. However, for auto configuration to succeed with a user-defined passphrase, the target devices must be manually pre-configured with the same passphrase as the device that generates the files, which is not zero touch.
373
18
If the device creating the configuration file is in Unrestricted passphrase control mode, the device includes the passphrase in the file. As a result, the user can auto configure the target devices, including devices that are out-of-the-box or in factory default, with the configuration file without manually pre-configuring the target devices with the passphrase. This is zero touch because the target devices learn the passphrase directly from the configuration file.
NOTE Devices that are out-of-the-box or in factory default states use the default
374
18
SNMPv3 with privacy TFTP SCP (Secure Copy) HTTP based file transfer HTTPS based file transfer
Secure-XML-SNMP (level-15 users) Insecure Secure Insecure Secure HTTPS-based file transfer SCP
Configuring SSD
The SSD feature is configured in the following pages: SSD properties are set in the Properties page. SSD rules are defined in the SSD Rules page.
SSD Properties
Only users with SSD read permission of Plaintext-only or Both are allowed to set SSD properties. To configure global SSD properties:
375
18
STEP 1 Click Security > Secure Sensitive Data Management > Properties. The
following field appears: Current Local Passphrase TypeDisplays whether the default passphrase or a user-defined passphrase is currently being used.
Configuration File Passphrase ControlSelect an option as described in Configuration File Passphrase Control. Configuration File Integrity ControlSelect to enable this feature. See Configuration File Integrity Control.
STEP 3 Select a Read mode for the current session (see Elements of an SSD Rule).
DefaultUse the devices default passphrase. User Defined (Plaintext)Enter and confirm a new passphrase.
SSD Rules
Only users with SSD read permission of Plaintext-only or Both are allowed to set SSD rules. To configure SSD rules:
STEP 1 Click Security > Secure Sensitive Data Management > SSD Rules.
UserThis defines the user(s) to which the rule applies: Select one of the following options: Specific UserSelect and enter the specific user name to which this rule applies (this user does not necessarily have to be defined). Default User (cisco)Indicates that this rule applies to the default user.
376
18
Level 15Indicates that this rule applies to all users with privilege level 15. AllIndicates that this rule applies to all users.
ChannelThis defines the security level of the input channel to which the rule applies: Select one of the following options: SecureIndicates that this rule applies only to secure channels (console, SCP, SSH and HTTPS), not including the SNMP and XML channels. InsecureIndicates that this rule applies only to insecure channels (Telnet, TFTP and HTTP), not including the SNMP and XML channels. Secure XML SNMPIndicates that this rule applies only to XML over HTTPS and SNMPv3 with privacy. Insecure XML SNMPIndicates that this rule applies only to XML over HTTP or and SNMPv1/v2and SNMPv3 without privacy.
Read PermissionThe read permissions associated with the rule. These can be the following: ExcludeLowest read permission. Users are not permitted to get sensitive data in any form. Plaintext OnlyHigher read permission than above ones. Users are permitted to get sensitive data in plaintext only. Encrypted OnlyMiddle read permission. Users are permitted to get sensitive data as encrypted only. Both (Plaintext and Encrypted)Highest read permission. Users have both encrypted and plaintext permissions and are permitted to get sensitive data as encrypted and in plaintext
Default Read ModeAll default read modes are subjected to the read permission of the rule. The following options exist, but some might be rejected, depending on the rules read permission. ExcludeDo not allow reading the sensitive data. EncryptedSensitive data is presented encrypted. PlaintextSensitive data is presented as plaintext.
377
18
Restore All Rules to DefaultRestore all user-modified default rules to the default rule and remove all user-defined rules.
378
18
379
19
Security: SSH Client
This section describes the device when it functions as an SSH client. It covers the following topics: Secure Copy (SCP) and SSH Protection Methods SSH Server Authentication SSH Client Authentication Before You Begin Common Tasks SSH Client Configuration Through the GUI
380
19
When files are downloaded via TFTP or HTTP, the data transfer is unsecured. When files are downloaded via SCP, the information is downloaded from the SCP server to the device via a secure channel. The creation of this secure channel is preceded by authentication, which ensures that the user is permitted to perform the operation. Authentication information must be entered by the user, both on the device and on the SSH server, although this guide does not describe server operations. The following illustrates a typical network configuration in which the SCP feature might be used. Typical Network Configuration
Protection Methods
When data is transferred from an SSH server to a device (client), the SSH server uses various methods for client authentication. These are described below.
Passwords
To use the password method, first ensure that a username/password has been established on the SSH server. This is not done through the devices management system, although, after a username has been established on the server, the server password can be changed through the devices management system.
381
19
The username/password must then be created on the device. When data is transferred from the server to the device, the username/password supplied by the device must match the username/password on the server. Data can be encrypted using a one-time symmetric key negotiated during the session. Each device being managed must have its own username/password, although the same username/password can be used for multiple switches. The password method is the default method on the device.
Public/Private Keys
To use the public/private key method, create a username and public key on the SSH server. The public key is generated on the device, as described below, and then copied to the server. The actions of creating a username on the server and copying the public key to the server are not described in this guide. RSA and DSA default key pairs are generated for the device when it is booted. One of these keys is used to encrypt the data being downloaded from the SSH server. The RSA key is used by default. If the user deletes one or both of these keys, they are regenerated. The public/private keys are encrypted and stored in the device memory. The keys are part of the device configuration file, and the private key can be displayed to the user, in encrypted or plaintext form. Since the private key cannot be copied directly to the private key of another device, an import method exists that enables copying private keys from device to device (described in Import Keys).
Import Keys
In the key method, individual public/private keys must be created for each individual device, and these private keys cannot be copied directly from one device to another because of security considerations. If there are multiple switches in the network, the process of creating public/private keys for all the switches might be time-consuming, because each public/private key must be created and then loaded onto the SSH server. To facilitate this process, an additional feature enables secure transfer of the encrypted private key to all switches in the system.
382
19
When a private key is created on a device, it is also possible to create an associated passphrase. This passphrase is used to encrypt the private key and to import it into the remaining switches. In this way, all the switches can use the same public/private key.
When SSH server authentication is enabled, the SSH client running on the device authenticates the SSH server using the following authentication process: The device calculates the fingerprint of the received SSH servers public key. The device searches the SSH Trusted Servers table for the SSH servers IP address/host name. One of the following can occur: If a match is found, both for the servers IP address/host name and its fingerprint, the server is authenticated. If a matching IP address/host name is found, but there is no matching fingerprint, the search continues. If no matching fingerprint is found, the search is completed and authentication fails. If no matching IP address/host name is found, the search is completed and authentication fails.
If the entry for the SSH server is not found in the list of trusted servers, the process fails.
383
19
SSH client authentication by password is enabled by default, with the username/ password being anonymous. The user must configure the following information for authentication: The authentication method to be used. The username/password or public/private key pair.
In order to support auto configuration of an out-of-box device (device with factory default configuration), SSH server authentication is disabled by default.
Supported Algorithms
When the connection between a device (as an SSH client) and an SSH server is established, the client and SSH server exchange data in order to determine the algorithms to use in the SSH transport layer. The following algorithms are supported on the client side: Key Exchange Algorithm-diffie-hellman Encryption Algorithms aes128-cbc 3des-cbc arcfour aes192-cbc aes256-cbc
384
19
Before You Begin
The following actions must be performed before using the SCP feature: When using the password authentication method, a username/password must be set up on the SSH server. When using public/private keys authentication method, the public key must be stored on the SSH server.
Common Tasks
This section describes some common tasks performed using the SSH client. All pages referenced are pages found under the SSH Client branch of the menu tree.
Workflow1: To configure SSH client and transfer data to/from an SSH server, perform the following steps:
STEP 1 Decide which method is to be used: password or public/private key. Use the SSH
a. Create a global password in the SSH User Authentication page, or create a temporary one in the Upgrade/Backup Firmware/Language or Backup Configuration/Log pages, when you actually activate the secure data transfer. b. Upgrade the firmware, boot image or language file, using SCP, by selecting the via SCP (over SSH) option in the Upgrade/Backup Firmware/Language page. The password can be entered in this page directly, or the password entered in the SSH User Authentication page can be used. c. Download/backup the configuration file, using SCP, by selecting the via SCP (over SSH) option in the Download/Backup Configuration/Log page. The password can be entered in this page directly, or the password entered in the SSH User Authentication page can be used.
STEP 3 Set up a username/password on the SSH server or modify the password on the
SSH server. This activity depends on the server and is not described here.
385
19
a. Select whether to use an RSA or DSA key, create a username and then generate the public/private keys. b. View the generated key by clicking the Details button, and transfer the username and public key to the SSH server. This action depends on the server and is not described in this guide. c. Upgrade/backup the firmware or language file, using SCP, by selecting the via SCP (over SSH) option in the Upgrade/Backup Firmware/Language page. d. Download/backup the configuration file, using SCP, by selecting the via SCP (over SSH) option in the Download/Backup Configuration/Log page.
STEP 4 If the public/private key method is being used, perform the following steps:
Begin and End footers) from the Details page to an external device. Copy the public and private keys separately.
STEP 4 Log on to another device and open the SSH User Authentication page. Select the
type of key required and click Edit. Paste in the public/private keys.
STEP 5 Click Apply to copy the public/private keys onto the second device.
386
19
the secure copy (SCP). Select one of the options: By PasswordThis is the default setting. If this is selected, enter a password or retain the default one. By RSA Public KeyIf this is selected, create an RSA public and Private key in the SSH User Key Table block. By DSA Public KeyIf this is selected, create a DSA public/private key in the SSH User Key Table block.
STEP 3 Enter the Username (no matter what method was selected) or user the default
username. This must match the username defined on the SSH server.
STEP 4 If the By Password method was selected, enter a password (Encrypted or
ApplyThe selected authentication methods are associated with the access method. Restore Default CredentialsThe default username and password (anonymous) are restored. Display Sensitive Data As PlaintextSensitive data for the current page appears as plaintext.
The SSH User Key Table contains the following fields for each key: Key TypeRSA or DSA.
387
19
Key SourceAuto Generated or User Defined. FingerprintFingerprint generated from the key.
STEP 6 To handle an RSA or DSA key, select either RSA or DSA and perform one of the
following actions: GenerateGenerate a new key. EditDisplay the keys for copying/pasting to another device. DeleteDelete the key. DetailsDisplay the keys.
Server DefinitionSelect one of the following ways to identify the SSH server: By IP AddressIf this is selected enter the IP address of the server in the fields below. By NameIf this is selected enter the name of the server in the Server IP Address/Name field.
FingerprintEnter the fingerprint of the SSH server (copied from that server).
STEP 4 Click Apply. The trusted server definition is stored in the Running Configuration
file.
388
19
STEP 2 Enter the following fields:
STEP 1 Click Security > SSH Client > Change User Password on SSH Server.
Server DefinitionDefine the SSH server by selecting either By IP Address or By Name. Enter the server name or IP address of the server in the Server IP Address/Name field. IP VersionIf you selected to specify the SSH server by IP address, select whether that IP address is an IPv4 or IPv6 address. IP Address TypeIf the SSH server IP address is an IPv6 address, select the IPv6 address type. The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceSelect the link local interface from the list of interfaces. Server IP Address/NameEnter either the IP address of the SSH server or its name, depending on what was selected in Server Definition. UsernameThis must match the username on the server. Old PasswordThis must match the password on the server. New PasswordEnter the new password and confirm it in the Confirm Password field.
389
20
Security: SSH Server
This section describes how to establish an SSH session on the device. It covers the following topics: Overview Common Tasks SSH Server Configuration Pages
Overview
The SSH Server feature enables users to create an SSH session to the device. This is similar to establishing a telnet session, except that the session is secured. Public and private keys are automatically generated on the device. These can be modified by the user. The SSH session is opened using a special SSH client application, such as PuTTY. SSH Server can operate in the following modes: By Internally-generated RSA/DSA Keys (Default Setting)An RSA and a DSA key are generated. Users log on the SSH Server application and are automatically authenticated to open a session on the device when they supply the IP address of the device. Public Key ModeUsers are defined on the device. Their RSA/DSA keys are generated in an external SSH server application, such as PuTTY. The public keys are entered in the device. The users can then open an SSH session on the device through the external SSH server application.
390
20
Common Tasks
This section describes some common tasks performed using the SSH Server feature.
Workflow1: To logon to the device over SSH using the devices automatically-created (default) key, perform the following:
STEP 1 Enable SSH server in the TCP/UDP Services page and verify that SSH user
the device (it is not necessary to use a username or key that is known to the device).
Workflow2: To create an SSH user and logon to the device over SSH using this user, perform the following steps:
STEP 1 Generate an RSA or DSA key on an external SSH client application, such as
PuTTY.
STEP 2 Enable SSH user authentication by public key or password in the SSH User
Authentication page.
STEP 3 Enable Automatic Login if required (see Automatic Login below). STEP 4 Add a user in the SSH User Authentication page and copy in the public key
generated externally.
STEP 5 Log onto an external SSH client application, such as PuTTY, using the IP address of
Workflow3: To import an RSA or DSA key from device A to device B, perform the following steps:
STEP 1 On device A, select an RSA or DSA key in the SSH Server Authentication page. STEP 2 Click Details and copy the public key of the select key type to Notepad or other
the RSA or DSA key, click Edit and paste in the key from device A.
391
20
Automatic Login
If you use the SSH User Authentication page to create an SSH username for a user who is already configured in the local user database. You can prevent additional authentication by configuring the Automatic Login feature, which works as follows: EnabledIf a user is defined in the local database, and this user passed SSH Authentication using a public-key, the authentication by the local database username and password is skipped.
NOTE The configured authentication method for this specific management
method (console, Telnet, SSH and so on) must be Local (i.e. not RADIUS or TACACS+). See Configuring Management Access Authentication for more details). Not EnabledAfter successful authentication by SSH public key, even if the username is configured in the local user database, the user is authenticated again, as per the configured authentication methods, configured on the Management Access Authentication page.
This page is optional. You do not have to work with user authentication in SSH. To enable authentication and add a user.
STEP 1 Click Security > SSH Server > SSH User Authentication. STEP 2 Select the following fields:
392
20
SSH User Authentication by PasswordSelect to perform authentication of the SSH client user using the username/password configured in the local database (see Defining Users). SSH User Authentication by Public KeySelect to perform authentication of the SSH client user using the public key. Automatic LoginThis field can be enabled if the SSH User Authentication by Public Key feature was selected. See Automatic Login.
The following fields are displayed for the configured users: SSH User NameUser name of user. Key TypeWhether this is an RSA or DSA key. FingerprintFingerprint generated from the public keys.
STEP 3 Click Add to add a new user and enter the fields:
SSH User NameEnter a user name. Key TypeSelect either RSA or DSA. Public KeyCopy the public key generated by an external SSH client application (like PuTTY) into this text box.
The following fields are displayed for each key: Key TypeRSA or DSA. Key SourceAuto Generated or User Defined. FingerprintFingerprint generated from the key.
393
20
GenerateGenerates a key of the selected type. EditEnables you to copy in a key from another device. DeleteEnables you to delete a key. DetailsEnables you to view the generated key. The Details window also enables you to click Display Sensitive Data as Plaintext. If this is clicked, the keys are displayed as plaintext and not in encrypted form. If the key is already being displayed as plaintext, you can click Display Sensitive Data as Encrypted. to display the text in encrypted form.
STEP 4 If new keys were copied in from another, click Apply. The key(s) are stored in the
394
20
395
21
Access Control
The Access Control List (ACL) feature is part of the security mechanism. ACL definitions serve as one of the mechanisms to define traffic flows that are given a specific Quality of Service (QoS). For more information see Quality of Service. ACLs enable network managers to define patterns (filter and actions) for ingress traffic. Packets, entering the device on a port or LAG with an active ACL, are either admitted or denied entry. This section contains the following topics: Access Control Lists Defining MAC-based ACLs IPv4-based ACLs IPv6-Based ACLs Defining ACL Binding
396
21
Access Control
Access Control Lists
When a packet matches an ACE filter, the ACE action is taken and that ACL processing is stopped. If the packet does not match the ACE filter, the next ACE is processed. If all ACEs of an ACL have been processed without finding a match, and if another ACL exists, it is processed in a similar manner.
NOTE If no match is found to any ACE in all relevant ACLs, the packet is dropped (as a
default action). Because of this default drop action you must explicitly add ACEs into the ACL to permit the desired traffic, including management traffic, such as Telnet, HTTP or SNMP that is directed to the device itself. For example, if you do not want to discard all the packets that do not match the conditions in an ACL, you must explicitly add a lowest priority ACE into the ACL that permits all the traffic. If IGMP/MLD snooping is enabled on a port bound with an ACL, add ACE filters in the ACL to forward IGMP/MLD packets to the device. Otherwise, IGMP/MLD snooping fails at the port. The order of the ACEs within the ACL is significant, since they are applied in a firstfit manner. The ACEs are processed sequentially, starting with the first ACE. ACLs can be used for security, for example by permitting or denying certain traffic flows, and also for traffic classification and prioritization in the QoS Advanced mode.
NOTE A port can be either secured with ACLs or configured with advanced QoS policy,
but not both. There can only be one ACL per port, with the exception that it is possible to associate both an IP-based ACL and an IPv6-based ACL with a single port. To associate more than one ACL with a port, a policy with one or more class maps must be used. The following types of ACLs can be defined (depending on which part of the frame header is examined): MAC ACLExamines Layer 2 fields only, as described in Defining MACbased ACLs IP ACLExamines the Layer 3 layer of IP frames, as described in IPv4based ACLs IPv6 ACLExamines the Layer 3 layer of IPv4 frames as described in
397
Access Control
Defining MAC-based ACLs
21
Creating ACLs Workflow
To create ACLs and associate them with an interface, perform the following: 1. Create one or more of the following types of ACLs: a. MAC-based ACL by using the MAC Based ACL page and the MAC Based ACE page b. IP-based ACL by using the IPv4 Based ACL page and the IPv4 Based ACE page c. IPv6-based ACL by using the IPv6 Based ACL page and the IPv6 Based ACE page 2. Associate the ACL with interfaces by using the ACL Binding page.
398
21
To define a MAC-based ACL:
STEP 1 Click Access Control > MAC-Based ACL.
Access Control
Defining MAC-based ACLs
MAC-based ACLs are defined in the MAC Based ACL page. The rules are defined in the MAC Based ACE page.
case-sensitive.
STEP 4 Click Apply. The MAC-based ACL is saved to the Running Configuration file.
ACL NameDisplays the name of the ACL to which an ACE is being added. PriorityEnter the priority of the ACE. ACEs with higher priority are processed first. One is the highest priority. ActionSelect the action taken upon a match. The options are: -
PermitForward packets that meet the ACE criteria. DenyDrop packets that meet the ACE criteria. ShutdownDrop packets that meet the ACE criteria, and disable the port
from where the packets were received. Such ports can be reactivated from the Port Settings page.
Time RangeSelect to enable limiting the use of the ACL to a specific time range.
399
Access Control
Defining MAC-based ACLs
21
Time Range NameIf Time Range is selected, select the time range to be used. Time ranges are defined in the Time Range section. Destination MAC AddressSelect Any if all destination addresses are acceptable or User defined to enter a destination address or a range of destination addresses. Destination MAC Address ValueEnter the MAC address to which the destination MAC address is to be matched and its mask (if relevant). Destination MAC Wildcard MaskEnter the mask to define a range of MAC addresses. Note that this mask is different than in other uses, such as subnet mask. Here, setting a bit as 1 indicates don't care and 0 indicates to mask that value.
NOTE Given a mask of 0000 0000 0000 0000 0000 0000 1111 1111 (which means that you match on the bits where there is 0 and don't match on the bits where there are 1's). You need to translate the 1's to a decimal integer and you write 0 for each four zeros. In this example since 1111 1111 = 255, the mask would be written: as 0.0.0.255.
Source MAC AddressSelect Any if all source address are acceptable or User defined to enter a source address or range of source addresses. Source MAC Address ValueEnter the MAC address to which the source MAC address is to be matched and its mask (if relevant). Source MAC Wildcard MaskEnter the mask to define a range of MAC addresses. VLAN IDEnter the VLAN ID section of the VLAN tag to match. 802.1pSelect Include to use 802.1p. 802.1p ValueEnter the 802.1p value to be added to the VPT tag. 802.1p MaskEnter the wildcard mask to be applied to the VPT tag. EthertypeEnter the frame Ethertype to be matched.
STEP 5 Click Apply. The MAC-based ACE is saved to the Running Configuration file.
400
21
IPv4-based ACLs
Access Control
IPv4-based ACLs
IPv4-based ACLs are used to check IPv4 packets, while other types of frames, such as ARPs, are not checked. The following fields can be matched: IP protocol (by name for well-known protocols, or directly by value) Source/destination ports for TCP/UDP traffic Flag values for TCP frames ICMP and IGMP type and code Source/destination IP addresses (including wildcards) DSCP/IP-precedence value
NOTE ACLs are also used as the building elements of flow definitions for per-flow QoS
handling (see QoS Advanced Mode). The IPv4 Based ACL page enables adding ACLs to the system. The rules are defined in the IPv4 Based ACE page. IPv6 ACLs are defined in the IPv6 Based ACL page.
case-sensitive.
STEP 4 Click Apply. The IPv4-based ACL is saved to the Running Configuration file.
401
Access Control
IPv4-based ACLs
21
Adding Rules (ACEs) to an IPv4-Based ACL
To add rules (ACEs) to an IPv4-based ACL:
STEP 1 Click Access Control > IPv4-Based ACE. STEP 2 Select an ACL, and click Go. All currently-defined IP ACEs for the selected ACL are
displayed.
STEP 3 Click Add. STEP 4 Enter the parameters.
ACL NameDisplays the name of the ACL. PriorityEnter the priority. ACEs with higher priority are processed first. ActionSelect the action assigned to the packet matching the ACE. The options are as follows: -
PermitForward packets that meet the ACE criteria. DenyDrop packets that meet the ACE criteria. ShutdownDrop packet that meets the ACE criteria and disable the port
to which the packet was addressed. Ports are reactivated from the Port Management page.
Time RangeSelect to enable limiting the use of the ACL to a specific time range. Time Range NameIf Time Range is selected, select the time range to be used. Time ranges are defined in the Time Range section. ProtocolSelect to create an ACE based on a specific protocol or protocol ID. Select Any (IPv4) to accept all IP protocols. Otherwise select one of the following protocols from the drop-down list: -
ICMPInternet Control Message Protocol IGMPInternet Group Management Protocol IP in IPIP in IP encapsulation TCPTransmission Control Protocol EGPExterior Gateway Protocol IGPInterior Gateway Protocol
402
21
Access Control
IPv4-based ACLs
UDPUser Datagram Protocol HMPHost Mapping Protocol RDPReliable Datagram Protocol. IDPRInter-Domain Policy Routing Protocol IPV6IPv6 over IPv4 tunneling IPV6:ROUTMatches packets belonging to the IPv6 over IPv4 route
through a gateway
IDRPInter-Domain Routing Protocol RSVPReSerVation Protocol AHAuthentication Header IPV6:ICMPInternet Control Message Protocol EIGRPEnhanced Interior Gateway Routing Protocol OSPFOpen Shortest Path First IPIPIP in IP PIMProtocol Independent Multicast L2TPLayer 2 Tunneling Protocol ISISIGP-specific protocol
Protocol ID to MatchInstead of selecting the name, enter the protocol ID. Source IP AddressSelect Any if all source address are acceptable or User defined to enter a source address or range of source addresses. Source IP Address ValueEnter the IP address to which the source IP address is to be matched. Source IP Wildcard MaskEnter the mask to define a range of IP addresses. Note that this mask is different than in other uses, such as subnet mask. Here, setting a bit as 1 indicates don't care and 0 indicates to mask that value.
403
Access Control
IPv4-based ACLs
21
NOTE Given a mask of 0000 0000 0000 0000 0000 0000 1111 1111 (which
means that you match on the bits where there is 0 and don't match on the bits where there are 1's). You need to translate the 1's to a decimal integer and you write 0 for each four zeros. In this example since 1111 1111 = 255, the mask would be written: as 0.0.0.255. Destination IP AddressSelect Any if all destination address are acceptable or User defined to enter a destination address or range of destination addresses. Destination IP Address ValueEnter the IP address to which the destination IP address is to be matched. Destination IP Wildcard MaskEnter the mask to define a range of IP addresses. Source PortSelect one of the following: AnyMatch to all source ports. SingleEnter a single TCP/UDP source port to which packets are matched. This field is active only if 800/6-TCP or 800/17-UDP is selected in the Select from List drop-down menu. RangeSelect a range of TCP/UDP source ports to which the packet is matched. There are eight different port ranges that can be configured (shared between source and destination ports). TCP and UDP protocols each have eight port ranges.
Destination PortSelect one of the available values that are the same as the Source Port field described above.
NOTE You must specify the IP protocol for the ACE before you can enter the
source and/or destination port. TCP FlagsSelect one or more TCP flags with which to filter packets. Filtered packets are either forwarded or dropped. Filtering packets by TCP flags increases packet control, which increases network security. Type of ServiceThe service type of the IP packet. -
AnyAny service type DSCP to MatchDifferentiated Serves Code Point (DSCP) to match
404
21
-
Access Control
IPv6-Based ACLs
ICMPIf the IP protocol of the ACL is ICMP, select the ICMP message type used for filtering purposes. Either select the message type by name or enter the message type number: AnyAll message types are accepted. Select from listSelect message type by name. ICMP Type to MatchNumber of message type to be used for filtering purposes.
ICMP CodeThe ICMP messages can have a code field that indicates how to handle the message. Select one of the following options to configure whether to filter on this code: AnyAccept all codes. User definedEnter an ICMP code for filtering purposes.
IGMPIf the ACL is based on IGMP, select the IGMP message type to be used for filtering purposes. Either select the message type by name or enter the message type number: AnyAll message types are accepted. Select from listSelect message type by name. IGMP Type to matchNumber of message type that is to be used for filtering purposes.
STEP 5 Click Apply. The IPv4-based ACE is saved to the Running Configuration file.
IPv6-Based ACLs
The IPv6-Based ACL page displays and enables the creation of IPv6 ACLs, which check pure IPv6-based traffic. IPv6 ACLs do not check IPv6-over-IPv4 or ARP packets.
405
Access Control
IPv6-Based ACLs
21
NOTE ACLs are also used as the building elements of flow definitions for per-flow QoS
This window contains the list of defined ACLs and their contents
STEP 2 Click Add. STEP 3 Enter the name of a new ACL in the ACL Name field. The names are
case-sensitive.
STEP 4 Click Apply. The IPv6-based ACL is saved to the Running Configuration file.
This window contains the ACE (rules) for a specified ACL (group of rules).
STEP 2 Select an ACL, and click Go. All currently-defined IP ACEs for the selected ACL are
displayed.
STEP 3 Click Add. STEP 4 Enter the parameters.
ACL NameDisplays the name of the ACL to which an ACE is being added. PriorityEnter the priority. ACEs with higher priority are processed first. ActionSelect the action assigned to the packet matching the ACE. The options are as follows: PermitForward packets that meet the ACE criteria. DenyDrop packets that meet the ACE criteria. ShutdownDrop packets that meet the ACE criteria, and disable the port to which the packets were addressed. Ports are reactivated from the Port Management page.
406
21
Access Control
IPv6-Based ACLs
Time RangeSelect to enable limiting the use of the ACL to a specific time range. Time Range NameIf Time Range is selected, select the time range to be used. Time ranges are described in the Time Range section. ProtocolSelect to create an ACE based on a specific protocol. Select Any (IPv6) to accept all IP protocols. Otherwise select one of the following protocols: TCPTransmission Control Protocol. Enables two hosts to communicate and exchange data streams. TCP guarantees packet delivery, and guarantees that packets are transmitted and received in the order they were sent. UDPUser Datagram Protocol. Transmits packets but does not guarantee their delivery. ICMPMatches packets to the Internet Control Message Protocol (ICMP).
Protocol ID to MatchEnter the ID of the protocol to be matched. Source IP AddressSelect Any if all source address are acceptable or User defined to enter a source address or range of source addresses. Source IP Address ValueEnter the IP address to which the source IP address is to be matched and its mask (if relevant). Source IP Prefix LengthEnter the prefix length of the source IP address. Destination IP AddressSelect Any if all destination address are acceptable or User defined to enter a destination address or a range of destination addresses. Destination IP Address ValueEnter the IP address to which the destination MAC address is matched and its mask (if relevant). Destination IP Prefix LengthEnter the prefix length of the IP address. Source PortSelect one of the following: AnyMatch to all source ports. SingleEnter a single TCP/UDP source port to which packets are matched. This field is active only if 800/6-TCP or 800/17-UDP is selected in the IP Protocol drop-down menu.
407
Access Control
IPv6-Based ACLs
21
RangeSelect a range of TCP/UDP source ports to which the packet is matched. Destination PortSelect one of the available values. (They are the same as for the Source Port field described above).
NOTE You must specify the IPv6 protocol for the ACL before you can configure the source and/or destination port.
TCP FlagsSelect one or more TCP flags with which to filter packets. Filtered packets are either forwarded or dropped. Filtering packets by TCP flags increases packet control, which increases network security. SetMatch if the flag is SET. UnsetMatch if the flag is Not SET. Dont careIgnore the TCP flag.
Type of ServiceThe service type of the IP packet. ICMPIf the ACL is based on ICMP, select the ICMP message type that is used for filtering purposes. Either select the message type by name or enter the message type number. If all message types are accepted, select Any. AnyAll message types are accepted. Select from listSelect message type by name from the drop-down list. ICMP Type to MatchNumber of message type that is to be used for filtering purposes.
ICMP CodeThe ICMP messages may have a code field that indicates how to handle the message. Select one of the following options, to configure whether to filter on this code: AnyAccept all codes. User definedEnter an ICMP code for filtering purposes.
408
21
Defining ACL Binding
Access Control
Defining ACL Binding
When an ACL is bound to an interface, its ACE rules are applied to packets arriving at that interface. Packets that do not match any of the ACEs in the ACL are matched to a default rule, whose action is to drop unmatched packets. Although each interface can be bound to only one ACL, multiple interfaces can be bound to the same ACL by grouping them into a policy-map, and binding that policy-map to the interface. After an ACL is bound to an interface, it cannot be edited, modified, or deleted until it is removed from all the ports to which it is bound or in use.
NOTE It is possible to either bind a port to a policy or to an ACL but both cannot be bound.
displayed with a list of their current ACLs: InterfaceIdentifier of interface. MAC ACLACLs of type MAC that are bound to the interface (if any). IPv4 ACLACLs of type IPv4 that are bound to the interface (if any). IPv6 ACLACLs of type IPv6 that are bound to the interface (if any).
NOTE To unbind all ACLs from an interface, select the interface, and click
Clear.
STEP 4 Select an interface, and click Edit . STEP 5 Select the Interface to which the ACLs are to be bound. STEP 6 Select one of the following:
Select MAC Based ACLSelect a MAC-based ACL to be bound to the interface. Select IPv4 Based ACLSelect an IPv4-based ACL to be bound to the interface. Select IPv6 Based ACLSelect an IPv6-based ACL to be bound to the interface.
Cisco Small Business 300 Series Managed Switch Administration Guide
409
Access Control
Defining ACL Binding
21
Permit AnySelect one of the following options: .Disable (Deny Any)If packet does not match an ACL, it is denied (dropped). EnableIf packet does not match an ACL, it is permitted (forwarded).
NOTE Permit Any can be defined only if IP Source Guard is not activated on
the interface.
STEP 7 Click Apply. The ACL binding is modified, and the Running Configuration file is
updated.
NOTE If no ACL is selected, the ACL(s) that is previously bound to the
interface is unbound.
410
21
Access Control
Defining ACL Binding
411
22
Quality of Service
The Quality of Service feature is applied throughout the network to ensure that network traffic is prioritized according to required criteria and the desired traffic receives preferential treatment. This section covers the following topics: QoS Features and Components Configuring QoS - General QoS Basic Mode QoS Advanced Mode Managing QoS Statistics
412
22
QoS Features and Components
Quality of Service
QoS Features and Components
The QoS feature is used to optimize network performance. QoS provides the following: Classification of incoming traffic to traffic classes, based on attributes, including: Device Configuration Ingress interface Packet content Combination of these attributes
QoS includes the following: Traffic ClassificationClassifies each incoming packet as belonging to a specific traffic flow, based on the packet contents and/or the port. The classification is done by ACL (Access Control List), and only traffic that meets the ACL criteria is subject to CoS or QoS classification. Assignment to Hardware QueuesAssigns incoming packets to forwarding queues. Packets are sent to a particular queue for handling as a function of the traffic class to which they belong. See Configuring QoS Queues. Other Traffic Class-Handling AttributeApplies QoS mechanisms to various classes, including bandwidth management.
QoS Modes
The QoS mode that is selected applies to all interfaces in the system. Basic ModeClass of Service (CoS). All traffic of the same class receives the same treatment, which is the single QoS action of determining the egress queue on the egress port, based on the indicated QoS value in the incoming frame. This can be the VLAN Priority Tag (VPT) 802.1p value in Layer 2 and the Differentiated Service Code Point (DSCP) value for IPv4 or Traffic Class (TC) value for IPv6 in Layer 3. When operating in Basic Mode, the device trusts this external assigned QoS value. The external assigned QoS value of a packet determines its traffic class and QoS.
413
Quality of Service
QoS Features and Components
22
The header field to be trusted is entered in the Global Settings page. For every value of that field, an egress queue is assigned where the frame is sent in the CoS/802.1p to Queue page or the DSCP to Queue page (depending on whether the trust mode is CoS/802.1p or DSCP, respectively). Advanced ModePer-flow Quality of Service (QoS). In advanced mode, a per flow QoS consists of a class map and/or a policer: A class map defines the kind of traffic in a flow, and contains one or more ACLs. Packets that match the ACLs belong to the flow. A policer applies the configured QoS to a flow. The QoS configuration of a flow may consist of egress queue, the DSCP or CoS/802.1p value, and actions on out of profile (excess) traffic.
Disable ModeIn this mode all traffic is mapped to a single best effort queue, so that no type of traffic is prioritized over another.
Only a single mode can be active at a time. When the system is configured to work in QoS Advanced mode, settings for QoS Basic mode are not active and vice versa. When the mode is changed, the following occurs: When changing from QoS Advanced mode to any other mode, policy profile definitions and class maps are deleted. ACLs bonded directly to interfaces remain bonded. When changing from QoS Basic mode to Advanced mode, the QoS Trust mode configuration in Basic mode is not retained. When disabling QoS, the shaper and queue setting (WRR/SP bandwidth setting) are reset to default values.
QoS Workflow
To configure general QoS parameters, perform the following:
STEP 1 Choose the QoS mode (Basic, Advanced, or Disabled, as described in the QoS
Modes section) for the system by using the QoS Properties page. The following steps in the workflow, assume that you have chosen to enable QoS.
STEP 2 Assign each interface a default CoS priority by using the QoS Properties page.
414
22
WRR to the egress queues by using the Queue page.
Quality of Service
Configuring QoS - General
STEP 3 Assign the schedule method (Strict Priority or WRR) and bandwidth allocation for
STEP 4 Designate an egress queue to each IP DSCP/TC value with the DSCP to Queue
page. If the device is in DSCP trusted mode, incoming packets are put into the egress queues based on the their DSCP/TC value.
STEP 5 Designate an egress queue to each CoS/802.1p priority. If the device is in CoS/
802.1 trusted mode, all incoming packets are put into the designated egress queues according to the CoS/802.1p priority in the packets. This is done by using the CoS/802.1p to Queue page.
STEP 6 If required for Layer 3 traffic only, assign a queue to each DSCP/TC value, by using
a. Set egress shaping per queue by using the Egress Shaping Per Queue page. b. Set ingress rate limit and egress shaping rate per port by using the Bandwidth page. c. Set VLAN ingress rate limit by using the VLAN Ingress Rate Limit page.
STEP 8 Configure the selected mode by performing one of the following:
a. Configure Basic mode, as described in Workflow to Configure Basic QoS Mode b. Configure Advanced mode, as described in Workflow to Configure Advanced QoS Mode.
415
Quality of Service
Configuring QoS - General
22
Setting QoS Properties
To select the QoS mode:
STEP 1 Click Quality of Service > General > QoS Properties. STEP 2 Set the QoS mode. The following options are available:
DisableQoS is disabled on the device. BasicQoS is enabled on the device in Basic mode. AdvancedQoS is enabled on the device in Advanced mode.
STEP 3 Select Port/LAG and click GO to display/modify all ports/LAGs on the device and
their CoS information. The following fields are displayed for all ports/LAGs: InterfaceType of interface. Default CoSDefault VPT value for incoming packets that do not have a VLAN Tag. The default CoS is 0. The default is only relevant for untagged frames and only if the system is in Basic mode and Trust CoS is selected in the Global Settings page.
Select Restore Defaults to restore the factory CoS default setting for this interface.
STEP 4 Click Apply. The Running Configuration file is updated.
InterfaceSelect the port or LAG. Default CoSSelect the default CoS (Class-of-Service) value to be assigned for incoming packets (that do not have a VLAN tag).
STEP 2 Click Apply. The interface default CoS value is saved to Running Configuration file.
416
22
Configuring QoS Queues
Quality of Service
Configuring QoS - General
The device supports either 4 or 8 queues for each interface (selected in the System Mode and Stack Management page). Queue number four or eight is the highest priority queue. Queue number one is the lowest priority queue. There are two ways of determining how traffic in queues is handled, Strict Priority and Weighted Round Robin (WRR). Strict PriorityEgress traffic from the highest-priority queue is transmitted first. Traffic from the lower queues is processed only after the highest queue has been transmitted, thus providing the highest level of priority of traffic to the highest numbered queue. Weighted Round Robin (WRR)In WRR mode the number of packets sent from the queue is proportional to the weight of the queue (the higher the weight the more frames are sent). For example, if there are a maximum of four queues possible and all four queues are WRR and the default weights are used, queue1 receives 1/15 of the bandwidth (assuming all queues are saturated and there is congestion), queue 2 receives 2/15, queue 3 receives 4/15 and queue 4 receives 8 /15 of the bandwidth. The type of WRR algorithm used in the device is not the standard Deficit WRR (DWRR), but rather Shaped Deficit WRR (SDWRR).
The queuing modes can be selected in the Queue page. When the queuing mode is by strict priority, the priority sets the order in which queues are serviced, starting with Queue 4 or Queue 8 (the highest priority queue) and going to the next lower queue when each queue is completed. When the queuing mode is Weighted Round Robin, queues are serviced until their quota has been used up and then another queue is serviced. It is also possible to assign some of the lower queues to WRR, while keeping some of the higher queues in strict priority. In this case traffic for the strict priority queues is always sent before traffic from the WRR queues. Only after the strict priority queues have been emptied is traffic from the WRR queues forwarded. (The relative portion from each WRR queue depends on its weight). To select the priority method and enter WRR data.
STEP 1 Click Quality of Service > General > Queue. STEP 2 Enter the parameters.
QueueDisplays the queue number. Scheduling Method: Select one of the following options:
417
Quality of Service
Configuring QoS - General
22
-
Strict PriorityTraffic scheduling for the selected queue and all higher
queues is based strictly on the queue priority.
WRRTraffic scheduling for the selected queue is based on WRR. The period time is divided between the WRR queues that are not empty, meaning they have descriptors to egress. This happens only if strict priority queues are empty. WRR WeightIf WRR is selected, enter the WRR weight assigned to the
queue.
STEP 3 Click Apply. The queues are configured, and the Running Configuration file is
updated.
Background Best Effort Excellent Effort Critical Application - LVS phone SIP Video
418
22
802.1p Values (0-7, 7 being the highest) 5 6 7 Queue (4 queues 14, 4 being the highest priority) 4 4 4
Quality of Service
Configuring QoS - General
Notes
Voice - Cisco IP phone default Interwork Control - LVS phone RTP Network Control
Default Mapping for 8 Queues 802.1p Values (0-7, 7 being the highest) Queue (8 queues 18, 8 is the highest priority) Standalone 1 2 3 6 5 8 8 7 7 Queues (8 is the highest priority used for stack control traffic) (stack) 1 1 2 5 4 7 7 6 Background Best Effort Excellent Effort Critical Application - LVS phone SIP Video Voice - Cisco IP phone default Interwork Control LVS phone RTP Network Control Notes
0 1 2 3 4 5 6 7
By changing the CoS/802.1p to Queue mapping (CoS/802.1p to Queue) and the Queue schedule method and bandwidth allocation (Queue page), it is possible to achieve the desired quality of service in a network. The CoS/802.1p to Queue mapping is applicable only if one of the following exists:
419
Quality of Service
Configuring QoS - General
22
The device is in QoS Basic mode and CoS/802.1p trusted mode The device is in QoS Advanced mode and the packets belong to flows that are CoS/802.1p trusted
Queue 1 has the lowest priority, queue 4 or 8 has the highest priority. To map CoS values to egress queues:
STEP 1 Click Quality of Service > General > CoS/802.1p to Queue. STEP 2 Enter the parameters.
802.1pDisplays the 802.1p priority tag values to be assigned to an egress queue, where 0 is the lowest and 7 is the highest priority. Output QueueSelect the egress queue to which the 802.1p priority is mapped. Either four or eight egress queues are supported, where Queue 4 or Queue 8 is the highest priority egress queue and Queue1 is the lowest priority.
STEP 3 For each 802.1p priority, select the Output Queue to which it is mapped. STEP 4 Click Apply. 801.1p priority values to queues are mapped, and the Running
420
22
Table 4 DSCP Queue DSCP Queue DSCP Queue DSCP Queue DSCP Queue DSCP Queue DSCP Queue DSCP Queue
Quality of Service
Configuring QoS - General
The following tables describe the default DSCP to queue mapping for a 4 and 8 queue systems: DSCP to Queue Default Mapping 4 Queues System 63 3 62 3 61 3 60 3 59 3 58 3 57 3 56 3 55 3 54 3 53 3 52 3 51 3 50 3 49 3 48 3 47 4 46 4 45 4 44 4 43 4 42 4 41 4 40 4 39 3 38 3 37 3 36 3 35 3 34 3 33 3 32 3 31 3 30 3 29 3 28 3 27 3 26 3 25 3 24 3 23 2 22 2 21 2 20 2 19 2 18 2 17 2 16 2 15 1 14 1 13 1 12 1 11 1 10 1 9 1 8 1 7 1 6 1 5 1 4 1 3 1 2 1 1 1 0 1
Table 5 DSCP to Queue Default Mapping 8 Queues System (7 is highest and 8 is used for stack control purposes) DSCP Queue DSCP 63 6 62 55 6 54 47 7 46 39 5 38 31 4 30 23 3 22 15 2 14 7 1 6
421
Quality of Service
Configuring QoS - General
22
Table 5 DSCP to Queue Default Mapping 8 Queues System (7 is highest and 8 is used for stack control purposes) Queue DSCP Queue DSCP Queue DSCP Queue DSCP Queue DSCP Queue DSCP Queue 6 61 6 60 6 59 6 58 6 57 6 56 6 6 53 6 52 6 51 6 50 6 49 6 48 6 7 45 7 44 7 43 7 42 7 41 7 40 6 5 37 5 36 5 35 5 34 5 33 5 32 7 4 29 4 28 4 27 4 26 4 25 4 24 6 3 21 3 20 3 19 3 18 3 17 3 16 6 2 13 2 12 2 11 2 10 2 9 2 8 1 1 5 1 4 1 3 1 2 1 1 1 0 1
422
22
Table 6 DSCP Queue DSCP Queue DSCP Queue DSCP Queue 59 7 58 7 57 7 56 7 51 7 50 7 49 7 48 7 43 8 42 8 41 8 40 7 35 6 34 6 33 6 32 8 27 5 26 5 25 5 24 7 19 4 18 4 17 4 16 7
Quality of Service
Configuring QoS - General
The DSCP to Queue page contains Ingress DSCP. It displays the DSCP value in the incoming packet and its associated class.
STEP 2 Select the Output Queue (traffic forwarding queue) to which the DSCP value is
mapped.
STEP 3 Click Apply. The Running Configuration file is updated.
Configuring Bandwidth
The Bandwidth page enables users to define two values, Ingress Rate Limit and Egress Shaping Rate, which determine how much traffic the system can receive and send. The ingress rate limit is the number of bits per second that can be received from the ingress interface. Excess bandwidth above this limit is discarded. The following values are entered for egress shaping: Committed Information Rate (CIR) sets the average maximum amount of data allowed to be sent on the egress interface, measured in bits per second
423
Quality of Service
Configuring QoS - General
22
Committed Burst Size (CBS) is the burst of data that is allowed to be sent, even though it is above the CIR. This is defined in number of bytes of data. To enter bandwidth limitation:
The Bandwidth page displays bandwidth information for each interface. The % column is the ingress rate limit for the port divided by the total port bandwidth.
STEP 2 Select an interface, and click Edit . STEP 3 Select the Port or LAG interface. STEP 4 Enter the fields for the selected interface:
Ingress Rate LimitSelect to enable the ingress rate limit, which is defined in the field below. Ingress Rate LimitEnter the maximum amount of bandwidth allowed on the interface.
NOTE The two Ingress Rate Limit fields do not appear when the interface type is LAG.
Ingress Committed Burst Size (CBS)Enter the maximum burst size of data for the ingress interface in bytes of data. This amount can be sent even if it temporarily increases the bandwidth beyond the allowed limit. This field is only available if the interface is a port. Egress Shaping RateSelect to enable egress shaping on the interface. Committed Information Rate (CIR)Enter the maximum bandwidth for the egress interface. Egress Committed Burst Size (CBS)Enter the maximum burst size of data for the egress interface in bytes of data. This amount can be sent even if it temporarily increases the bandwidth beyond the allowed limit.
STEP 5 Click Apply. The bandwidth settings are written to the Running Configuration file.
424
22
Configuring Egress Shaping per Queue
Quality of Service
Configuring QoS - General
In addition to limiting transmission rate per port, which is done in the Bandwidth page, the device can limit the transmission rate of selected egressing frames on a per-queue per-port basis. Egress rate limiting is performed by shaping the output load. The device limits all frames except for management frames. Any frames that are not limited are ignored in the rate calculations, meaning that their size is not included in the limit total. Per-queue Egress rate shaping can be disabled. To define egress shaping per queue:
STEP 1 Click Quality of Service > General > Egress Shaping per Queue.
The Egress Shaping Per Queue page displays the rate limit and burst size for each queue.
STEP 2 Select an interface type (Port or LAG), and click Go. STEP 3 Select a Port/LAG, and click Edit .
This page enables shaping the egress for up to eight queues on each interface.
STEP 4 Select the Interface. STEP 5 For each queue that is required, enter the following fields:
Enable ShapingSelect to enable egress shaping on this queue. Committed Information Rate (CIR)Enter the maximum rate (CIR) in Kbits per second (Kbps). CIR is the average maximum amount of data that can be sent. Committed Burst Size (CBS)Enter the maximum burst size (CBS) in bytes. CBS is the maximum burst of data allowed to be sent even if a burst exceeds CIR.
STEP 6 Click Apply. The bandwidth settings are written to the Running Configuration file.
425
Quality of Service
Configuring QoS - General
22
Rate limiting per VLAN, performed in the VLAN Ingress Rate Limit page, enables traffic limiting on VLANs. When VLAN ingress rate limiting is configured, it limits aggregate traffic from all the ports on the device. The following constraints apply to rate limiting per VLAN: It has lower precedence than any other traffic policing defined in the system. For example, if a packet is subject to QoS rate limits but is also subject to VLAN rate limiting, and the rate limits conflict, the QoS rate limits take precedence. It is applied at the device level and within the device at the packet processor level. If there is more than one packet processor on the device, the configured VLAN rate limit value is applied to each of the packet processors, independently. Devices with up to 24 ports have a single packet processor, while devices of 48 ports or more have two packet processors.
VLAN IDSelect a VLAN. Committed Information Rate (CIR)Enter the average maximum amount of data that can be accepted into the VLAN in Kilobytes per second. Committed Burst Size (CBS)Enter the maximum burst size of data for the egress interface in bytes of data. This amount can be sent even if it temporarily increases the bandwidth beyond the allowed limit. Cannot be entered for LAGs.
STEP 4 Click Apply. The VLAN rate limit is added, and the Running Configuration file is
updated.
426
22
TCP Congestion Avoidance
Quality of Service
QoS Basic Mode
The TCP Congestion Avoidance page enables activating a TCP congestion avoidance algorithm. The algorithm breaks up or avoids TCP global synchronization in a congested node, where the congestion is due to various sources sending packets with the same byte count. To configure TCP congestion avoidance:
STEP 1 Click Quality of Service > General > TCP Congestion Avoidance. STEP 2 Click Enable to enable TCP congestion avoidance, and click Apply.
427
Quality of Service
QoS Basic Mode
22
Configuring Global Settings
The Global Settings page contains information for enabling Trust on the device (see the Trust Mode field below). This configuration is active when the QoS mode is Basic mode. Packets entering a QoS domain are classified at the edge of the QoS domain. To define the Trust configuration:
STEP 1 Click Quality of Service > QoS Basic Mode > Global Settings. STEP 2 Select the Trust Mode while the device is in Basic mode. If a packet CoS level and
DSCP tag are mapped to separate queues, the Trust mode determines the queue to which the packet is assigned: CoS/802.1pTraffic is mapped to queues based on the VPT field in the VLAN tag, or based on the per-port default CoS/802.1p value (if there is no VLAN tag on the incoming packet), the actual mapping of the VPT to queue can be configured in the mapping CoS/802.1p to Queue page. DSCPAll IP traffic is mapped to queues based on the DSCP field in the IP header. The actual mapping of the DSCP to queue can be configured in the DSCP to Queue page. If traffic is not IP traffic, it is mapped to the best effort queue. CoS/802.1p-DSCPEither CoS/802.1p or DSCP whichever has been set.
STEP 3 Select Override Ingress DSCP to override the original DSCP values in the
incoming packets with the new values according to the DSCP Override Table. When Override Ingress DSCP is enabled, the device uses the new DSCP values for egress queueing. It also replaces the original DSCP values in the packets with the new DSCP values.
NOTE The frame is mapped to an egress queue using the new, rewritten
reconfigure DSCP. DSCP In displays the DSCP value of the incoming packet that needs to be remarked to an alternative value.
STEP 5 Select the DSCP Out value to indicate the outgoing value is mapped. STEP 6 Click Apply. The Running Configuration file is updated with the new DSCP values.
428
22
Interface QoS Settings
Quality of Service
QoS Advanced Mode
The Interface Settings page enables configuring QoS on each port of the device, as follows: QoS State Disabled on an InterfaceAll inbound traffic on the port is mapped to the best effort queue and no classification/prioritization takes place. QoS State of the Port is EnabledPort prioritize traffic on ingress is based on the system wide configured trusted mode, which is either CoS/ 802.1p trusted mode or DSCP trusted mode. To enter QoS settings per interface:
STEP 1 Click Quality of Service > QoS Basic Mode > Interface Settings. STEP 2 Select Port or LAG to display the list of ports or LAGs.
429
Quality of Service
QoS Advanced Mode
22
quality of services. Thus, a policy contains one or more flows, each with a user defined QoS. The QoS of a class map (flow) is enforced by the associating policer. There are two type of policers, single policer and aggregate policer. Each policer is configured with a QoS specification. A single policer applies the QoS to a single class map, and thus to a single flow, based on the policer QoS specification. An aggregate policer applies the QoS to one or more class maps, and thus one or more flows. An aggregate policer can support class maps from different policies. Per flow QoS are applied to flows by binding the policies to the desired ports. A policy and its class maps can be bound to one or more ports, but each port is bound with at most one policy.
Notes:
Single policer and aggregation policer are available when the device is in Layer 2 mode. An ACL can be configured to one or more class maps regardless of policies. A class map can belong to only one policy. When a class map using single policer is bound to multiple ports, each port has its own instance of single policer; each applying the QoS on the class map (flow) at a port independent of each other. An aggregate policer applies the QoS to all its flow(s) in aggregation regardless of policies and ports.
Advanced QoS settings consist of three parts: Definitions of the rules to match. All frames matching a single group of rules are considered to be a flow. Definition of the actions to be applied to frames in each flow that match the rules. Binding the combinations of rules and action to one or more interfaces.
430
22
Workflow to Configure Advanced QoS Mode
To configure Advanced QoS mode, perform the following:
Quality of Service
QoS Advanced Mode
1. Select Advanced mode for the system by using the QoS Properties page. Select the Trust Mode using the Global Settings page. If a packet CoS level and DSCP tag are mapped to separate queues, the Trust mode determines the queue to which the packet is assigned: If internal DSCP values are different from those used on incoming packets, map the external values to internal values by using the Out-of-Profile DSCP Mapping page. This in turn opens the DSCP Remarking page.
2. Create ACLs, as described in Create ACL Workflow. 3. If ACLs were defined, create class maps and associate the ACLs with them by using the Class Mapping page. 4. Create a policy using the Policy Table page, and associate the policy with one or more class maps using the Policy Class Map page. You can also specify the QoS, if needed, by assigning a policer to a class map when you associate the class map to the policy. Single PolicerCreate a policy that associates a class map with a single policer by using the Policy Table page and the Class Mapping page. Within the policy, define the single policer. Aggregate PolicerCreate a QoS action for each flow that sends all matching frames to the same policer (aggregate policer) by using the Aggregate Policer page. Create a policy that associates a class map with the aggregate policer by using the Policy Table page.
level and DSCP tag are mapped to separate queues, the Trust mode determines the queue to which the packet is assigned:
431
Quality of Service
QoS Advanced Mode
22
CoS/802.1pTraffic is mapped to queues based on the VPT field in the VLAN tag, or based on the per-port default CoS/802.1p value (if there is no VLAN tag on the incoming packet), the actual mapping of the VPT to queue can be configured in the mapping CoS/802.1p to Queue page. DSCPAll IP traffic is mapped to queues based on the DSCP field in the IP header. The actual mapping of the DSCP to queue can be configured in the DSCP to Queue page. If traffic is not IP traffic, it is mapped to the best effort queue. CoS/802.1p-DSCPSelect to use Trust CoS mode for non-IP traffic and Trust DSCP for IP traffic.
STEP 3 Select the default Advanced mode QoS trust mode (either trusted or untrusted) for
interfaces in the Default Mode Status field. This provides basic QoS functionality on Advanced QoS, so that you can trust CoS/DSCP on Advanced QoS by default (without having to create a policy). In QoS Advanced Mode, when the Default Mode Status is set to Not Trusted, the Default CoS values configured on the interface are used for prioritizing the traffic arriving on the interface. See the Quality of Service > QoS Advanced Mode > Global Settings page for details. If you have a policy on an interface then the Default Mode is irrelevant, the action is according to the policy configuration and unmatched traffic is dropped.
STEP 4 Select Override Ingress DSCP to override the original DSCP values in the
incoming packets with the new values according to the DSCP Override Table. When Override Ingress DSCP is enabled, the device uses the new DSCP values for egress queueing. It also replaces the original DSCP values in the packets with the new DSCP values.
NOTE The frame is mapped to an egress queue using the new, rewritten
reconfigure DSCP. See the DSCP Override Table page for details.
432
22
Quality of Service
QoS Advanced Mode
If the exceed action is Out of Profile DSCP, the device remaps the original DSCP value of the out-of-profile IP packets with a new value based on the Out of Profile DSCP Mapping Table. The device uses the new values to assign resources and the egress queues to these packets. The device also physically replaces the original DSCP value in the out of profile packets with the new DSCP value. To use the out-of-profile DSCP exceed action, remap the DSCP value in the Out Of Profile DSCP Mapping Table. Otherwise the action is null, because the DSCP value in the table remaps the packets to itself by factory default. This feature changes the DSCP tags for incoming traffic switched between trusted QoS domains. Changing the DSCP values used in one domain, sets the priority of that type of traffic to the DSCP value used in the other domain to identify the same type of traffic. These settings are active when the system is in the QoS basic mode, and once activated they are active globally. For example: Assume that there are three levels of service: Silver, Gold, and Platinum and the DSCP incoming values used to mark these levels are 10, 20, and 30 respectively. If this traffic is forwarded to another service provider that has the same three levels of service, but uses DSCP values 16, 24, and 48, Out of Profile DSCP Mapping changes the incoming values as they are mapped to the outgoing values. To map DSCP values:
STEP 1 Click Quality of Service > QoS Advanced Mode > Out of Profile DSCP Mapping.
This page enables setting the change-the-DSCP-value of traffic entering or leaving the device. DSCP In displays the DSCP value of the incoming packet that needs to be remarked to an alternative value.
STEP 2 Select the DSCP Out value to where the incoming value is mapped. STEP 3 Click Apply. The Running Configuration file is updated with the new DSCP
Mapping table.
433
Quality of Service
QoS Advanced Mode
22
Defining Class Mapping
A Class Map defines a traffic flow with ACLs (Access Control Lists). A MAC ACL, IP ACL, and IPv6 ACL can be combined into a class map. Class maps are configured to match packet criteria on a match-all or match-any basis. They are matched to packets on a first-fit basis, meaning that the action associated with the first-matched class map is the action performed by the system. Packets that matches the same class map are considered to belong to the same flow.
NOTE Defining class maps does not have any effect on QoS; it is an interim step, enabling
the class maps to be used later. If more complex sets of rules are needed, several class maps can be grouped into a super-group called a policy (see Configuring a Policy). The Class Mapping page shows the list of defined class maps and the ACLs comprising each, and enables you to add/delete class maps. To define a Class Map:
STEP 1 Click Quality of Service > QoS Advanced Mode > Class Mapping.
A new class map is added by selecting one or two ACLs and giving the class map a name. If a class map has two ACLs, you can specify that a frame must match both ACLs, or that it must match either one or both of the ACLs selected.
STEP 3 Enter the parameters.
Class Map NameEnter the name of a new class map. Match ACL TypeThe criteria that a packet must match in order to be considered to belong to the flow defined in the class map. The options are: -
IPA packet must match either of the IP based ACLs in the class map. MACA packet must match the MAC based ACL in the class map. IP and MACA packet must match the IP based ACL and the MAC based
ACL in the class map.
IP or MACA packet must match either the IP based ACL or the MAC based ACL in the class map.
IPSelect the IPv4 based ACL or the IPv6 based ACL for the class map.
434
22
MACSelect the MAC based ACL for the class map.
Quality of Service
QoS Advanced Mode
Preferred ACLSelect whether packets are first matched to an IP-based ACL or a MAC-based ACL.
QoS Policers
NOTE QoS policers are not supported on Sx500 devices in Layer 3 system mode. They
are always supported on SG500X devices. You can measure the rate of traffic that matches a pre-defined set of rules, and to enforce limits, such as limiting the rate of file-transfer traffic that is allowed on a port. This can be done by using the ACLs in the class map(s) to match the desired traffic, and by using a policer to apply the QoS on the matching traffic. A policer is configured with a QoS specification. There are two kinds of policers: Single (Regular) PolicerA single policer applies the QoS to a single class map, and to a single flow based on the policer's QoS specification. When a class map using single policer is bound to multiple ports, each port has its own instance of single policer; each applying the QoS on the class map (flow) at ports that are otherwise independent of each other. A single policer is created in the Policy Table page. Aggregate PolicerAn aggregate policer applies the QoS to one or more class maps, and one or more flows. An aggregation policer can support class maps from different policies. An aggregate policer applies QoS to all its flow(s) in aggregation regardless of policies and ports. An aggregate policer is created in the Aggregate Policer page. An aggregate policer is defined if the policer is to be shared with more than one class. Policers on a port cannot be shared with other policers in another device.
435
Quality of Service
QoS Advanced Mode
22
Each policer is defined with its own QoS specification with a combination of the following parameters: A maximum allowed rate, called a Committed Information Rate (CIR), measured in Kbps. An amount of traffic, measured in bytes, called a Committed Burst Size (CBS). This is traffic that is allowed to pass as a temporary burst even if it is above the defined maximum rate. An action to be applied to frames that are over the limits (called out-ofprofile traffic), where such frames can be passed as is, dropped, or passed, but remapped to a new DSCP value that marks them as lower-priority frames for all subsequent handling within the device.
Assigning a policer to a class map is done when a class map is added to a policy. If the policer is an aggregate policer, you must create it using the Aggregate Policer page.
Aggregate Policer NameEnter the name of the Aggregate Policer. Ingress Committed Information Rate (CIR)Enter the maximum bandwidth allowed in bits per second. See the description of this in the Bandwidth page.
436
22
Quality of Service
QoS Advanced Mode
Ingress Committed Burst Size (CBS)Enter the maximum burst size (even if it goes beyond the CIR) in bytes. See the description of this in the Bandwidth page. Exceed ActionSelect the action to be performed on incoming packets that exceed the CIR. Possible values are: ForwardPackets exceeding the defined CIR value are forwarded. DropPackets exceeding the defined CIR value are dropped. Out of Profile DSCPThe DSCP values of packets exceeding the defined CIR value are remapped to a value based on the Out Of Profile DSCP Mapping Table.
Configuring a Policy
The Policy Table Map page displays the list of advanced QoS polices defined in the system. The page also allows you to create and delete polices. Only those policies that are bound to an interface are active (see Policy Binding page). Each policy consists of: One or more class maps of ACLs which define the traffic flows in the policy. One or more aggregates that applies the QoS to the traffic flows in the policy.
After a policy has been added, class maps can be added by using the Policy Table page. To add a QoS policy:
STEP 1 Click Quality of Service > QoS Advanced Mode > Policy Table.
437
Quality of Service
QoS Advanced Mode
22
updated.
STEP 4 Click Apply. The QoS policy profile is added, and the Running Configuration file is
Layer 3 mode. The device supports policers only in Layer 2 mode. To add a class map to a policy:
STEP 1 Click Quality of Service > QoS Advanced Mode > Policy Class Maps. STEP 2 Select a policy in the Filter, and click Go. All class maps in that policy are
displayed.
STEP 3 To add a new class map, click Add. STEP 4 Enter the parameters.
Policy NameDisplays the policy to which the class map is being added. Class Map NameSelect an existing class map to be associated with the policy. Class maps are created in the Class Mapping page. Action TypeSelect the action regarding the ingress CoS/802.1p and/or DSCP value of all the matching packets. -
Use default trust modeIgnore the ingress CoS/802.1p and/or DSCP value. The matching packets are sent as best effort. Always TrustIf this option is selected, the device trusts the CoS/802.1p
and DSCP of the matching packet. If a packet is an IP packet, the device puts the packet in the egress queue based on its DSCP value and the DSCP to Queue Table. Otherwise, the egress queue of the packet is based on the packet's CoS/802.1p value and the CoS/802.1p to Queue Table.
SetIf this option is selected, use the value entered in the New Value box
to determine the egress queue of the matching packets as follows:
438
22
Quality of Service
QoS Advanced Mode
If the new value (0..7) is a CoS/802.1p priority, use the priority value and the CoS/802.1p to Queue Table to determine the egress queue of all the matching packets. If the new value (0..63) is a DSCP, use the new DSCP and the DSCP to Queue Table to determine the egress queue of the matching IP packets. Otherwise, use the new value (1..8) as the egress queue number for all the matching packets. Police TypeAvailable in Layer 2 system mode only. Select the policer type for the policy. The options are: NoneNo policy is used. SingleThe policer for the policy is a single policer. AggregateThe policer for the policy is an aggregate policer.
Aggregate PolicerAvailable in Layer 2 system mode only. If Police Type is Aggregate, select a previously-defined (in the Aggregate Policer page) aggregate policer.
If Police Type is Single, enter the following QoS parameters: Ingress Committed Information Rate (CIR)Enter the CIR in Kbps. See a description of this in the Bandwidth page. Ingress Committed Burst Size (CBS)Enter the CBS in bytes. See a description of this in the Bandwidth page. Exceed ActionSelect the action assigned to incoming packets exceeding the CIR. The options are: NoneNo action. DropPackets exceeding the defined CIR value are dropped. Out of Profile DSCPIP packets exceeding the defined CIR are forwarding with a new DSCP derived from the Out Of Profile DSCP Mapping Table.
439
Quality of Service
Managing QoS Statistics
22
Policy Binding
The Policy Binding page shows which policy profile is bound and to which port. When a policy profile is bound to a specific port, it is active on that port. Only one policy profile can be configured on a single port, but a single policy can be bound to more than one port. When a policy is bound to a port, it filters and applies QoS to ingress traffic that belongs to the flows defined in the policy. The policy does not apply to traffic egress to the same port. To edit a policy, it must first be removed (unbound) from all those ports to which it is bound.
NOTE It is possible to either bind a port to a policy or to an ACL but both cannot be bound.
BindingSelect to bind the policy to the interface. Permit AnySelect to forward packets on the interface if they do not match any policy.
NOTE Permit Any can be defined only if IP Source Guard is not activated on
the interface.
STEP 5 Click Apply. The QoS policy binding is defined, and the Running Configuration file
is updated.
440
22
Policer Statistics
Quality of Service
Managing QoS Statistics
A Single Policer is bound to a class map from a single policy. An Aggregate Policer is bound to one or more class maps from one or more policies.
This page displays the following fields: InterfaceStatistics are displayed for this interface. PolicyStatistics are displayed for this policy. Class MapStatistics are displayed for this class map. In-Profile BytesNumber of in-profile bytes received. Out-of-Profile BytesNumber of out-profile bytes received.
InterfaceSelect the interface for which statistics are accumulated. Policy NameSelect the policy name. Class Map NameSelect the class name.
STEP 4 Click Apply. An additional request for statistics is created and the Running
441
Quality of Service
Managing QoS Statistics
22
Viewing Aggregated Policer Statistics
To view aggregated policer statistics:
STEP 1 Click Quality of Service > QoS Statistics > Aggregate Policer Statistics.
This page displays the following fields: Aggregate Policer NamePolicer on which statistics are based. In-profile bytesNumber of in-profile packets that were received. Out-of-profile bytesNumber of out-of-profile packets that were received.
STEP 2 Click Add. STEP 3 Select an Aggregate Policer Name, one of the previously-created Aggregate
This page displays the following fields: Refresh RateSelect the time period that passes before the interface Ethernet statistics are refreshed. The available options are: No RefreshStatistics are not refreshed. 15 SecStatistics are refreshed every 15 seconds. 30 SecStatistics are refreshed every 30 seconds.
442
22
Counter SetThe options are:
Quality of Service
Managing QoS Statistics
Set 1Displays the statistics for Set 1 that contains all interfaces and queues with a high DP (Drop Precedence). Set 2Displays the statistics for Set 2 that contains all interfaces and queues with a low DP.
InterfaceQueue statistics are displayed for this interface. QueuePackets were forwarded or tail dropped from this queue. Drop PrecedenceLowest drop precedence has the lowest probability of being dropped. Total PacketsNumber of packets forwarded or tail dropped. Tail Drop PacketsPercentage of packets that were tail dropped.
Counter SetSelect the counter set: Set 1Displays the statistics for Set 1 that contains all interfaces and queues with a high DP (Drop Precedence). Set 2Displays the statistics for Set 2 that contains all interfaces and queues with a low DP.
InterfaceQueue statistics are displayed for this interface. QueuePackets were forwarded or tail dropped from this queue. Drop PrecedenceLowest drop precedence has the lowest probability of being dropped. Total PacketsNumber of packets forwarded or tail dropped. Tail Drop PacketsPercentage of packets that were tail dropped.
443
Quality of Service
Managing QoS Statistics
22
Set 1Displays the statistics for Set 1 that contains all interfaces and queues with a high DP (Drop Precedence). Set 2Displays the statistics for Set 2 that contains all interfaces and queues with a low DP.
InterfaceSelect the ports for which statistics are displayed. The options are: PortSelects the port on the selected unit number for which statistics are displayed. All PortsSpecifies that statistics are displayed for all ports.
QueueSelect the queue for which statistics are displayed. Drop PrecedenceEnter drop precedence that indicates the probability of being dropped.
STEP 6 Click Apply. The Queue Statistics counter is added, and the Running Configuration
file is updated.
444
22
Quality of Service
Managing QoS Statistics
445
23
SNMP
This section describes the Simple Network Management Protocol (SNMP) feature that provides a method for managing network devices. It covers the following topics: SNMP Versions and Workflow Model OIDs SNMP Engine ID Configuring SNMP Views Creating SNMP Groups Managing SNMP Users Defining SNMP Communities Defining Trap Settings Notification Recipients SNMP Notification Filters
446
23
SNMPv1 and v2
SNMP
SNMP Versions and Workflow
To control access to the system, a list of community entries is defined. Each community entry consists of a community string and its access privilege. The system responds only to SNMP messages specifying the community which has the correct permissions and correct operation. SNMP agents maintain a list of variables that are used to manage the device. These variables are defined in the Management Information Base (MIB).
NOTE Due to the security vulnerabilities of other versions, it is recommended to use
SNMPv3.
SNMPv3
In addition to the functionality provided by SNMPv1 and v2, SNMPv3 applies access control and new trap mechanisms to SNMPv1 and SNMPv2 PDUs. SNMPv3 also defines a User Security Model (USM) that includes: AuthenticationProvides data integrity and data origin authentication. PrivacyProtects against disclosure message content. Cipher BlockChaining (CBC-DES) is used for encryption. Either authentication alone can be enabled on an SNMP message, or both authentication and privacy can be enabled on an SNMP message. However, privacy cannot be enabled without authentication. TimelinessProtects against message delay or playback attacks. The SNMP agent compares the incoming message time stamp to the message arrival time. Key ManagementDefines key generation, key updates, and key use. The device supports SNMP notification filters based on Object IDs (OID). OIDs are used by the system to manage device features.
SNMP Workflow
NOTE For security reasons, SNMP is disabled by default. Before you can
manage the device via SNMP, you must turn on SNMP on the Security >TCP/ UDP Services page. The following is the recommended series of actions for configuring SNMP:
447
SNMP
SNMP Versions and Workflow
23
associated with access rights and a view in Basic mode or with a group in Advanced mode. There are two ways to define access rights of a community: Basic modeThe access rights of a community can configure with Read Only, Read Write, or SNMP Admin. In addition, you can restrict the access to the community to only certain MIB objects by selecting a view (defined in the Views page). Advanced ModeThe access rights of a community are defined by a group (defined in the Groups page). You can configure the group with a specific security model. The access rights of a group are Read, Write, and Notify.
STEP 2 Choose whether to restrict the SNMP management station to one address or allow
SNMP management from all addresses. If you choose to restrict SNMP management to one address, then input the address of your SNMP Management PC in the IP Address field.
STEP 3 Input the unique community string in the Community String field. STEP 4 Optionally, enable traps by using the Trap Settings page. STEP 5 Optionally, define a notification filter(s) by using the Notification Filter page. STEP 6 Configure the notification recipients on the Notification Recipients SNMPv1,2
page.
Engine ID or use the default Engine ID. Applying an Engine ID configuration clears the SNMP database.
STEP 2 Optionally, define SNMP view(s) by using the Views page. This limits the range of
group. If the SNMP Engine ID is not set, then users may not be created.
STEP 5 Optionally, enable or disable traps by using the Trap Settings page. STEP 6 Optionally, define a notification filter(s) by using the Notification Filter page.
448
23
page.
SNMP
Model OIDs
Supported MIBs
For a list of supported MIBs, visit the following URL and navigate to the download area listed as Cisco MIBS: www.cisco.com/cisco/software/navigator.html
Model OIDs
The following are the device model Object IDs (OIDs): Model Name SG300-10 SG300-10MP SG300-10P SG300-20 SG300-28 SG300-28P SG300-52 SF300-08 SF302-08 SF302-08MP SF302-08P Description 8 GE ports, and 2 special-purpose combo ports (GE/SFP) 8 GE ports, and 2 special-purpose combo ports (GE/SFP) 8 GE ports, and 2 special-purpose combo ports (GE/SFP) 16 GE ports, and 4 special purpose ports - 2 uplinks and 2 combo ports 24 GE ports, and 4 special-purpose ports - 2 uplinks and 2 combo-ports 24 GE ports, and 4 special-purpose ports - 2 uplinks and 2 combo-ports. 48 GE ports, and 4 special-purpose ports - 2 uplinks and 2 combo-ports 8 FE ports. 8 FE ports plus 2 GE ports 8 FE ports plus 2 GE ports 8 FE ports plus 2 GE ports Object ID 9.6.1.83.10.1 9.6.1.83.10.3 9.6.1.83.10.2 9.6.1.83.20.1 9.6.1.83.28.1 9.6.1.83.28.2 9.6.1.83.52.1 9.6.1.82.08.4 9.6.1.82.08.1 9.6.1.82.08.3 9.6.1.82.08.2
449
SNMP
SNMP Engine ID
23
Model Name SF300-24 SF300-24P SF300-48 SF300-48P SG300-52P SG300-52MP SG300-10SFP ESW2-350G52 ESW2-350G52DC SF300-24MP SG300-28MP Description 24 FE ports plus 4 GE special-purpose ports - 2 uplinks and 2 combo-ports. 24 FE ports plus 4 GE special-purpose ports - 2 uplinks and 2 combo-ports. 48 FE ports plus 4 GE special-purpose ports - 2 uplinks and 2 combo-ports 48 FE ports plus 4 GE special-purpose ports - 2 uplinks and 2 combo-ports 52-Port Gigabit PoE Managed Switch 52-Port Gigabit PoE Managed Switch 10-Port Gigabit Managed SFP Switch 52-Port Gigabit Managed Switch 52-Port Gigabit Managed Switch 24-Port 10/100 PoE Managed Switch 28-Port Gigabit PoE Managed Switch Object ID 9.6.1.82.24.1 9.6.1.82.24.2 9.6.1.82.48.1 9.6.1.82.48.2 9.6.1.83.52.2 9.6.1.83.52.3 9.6.1.83.10.5 9.6.1.86.52.1 9.6.1.86.52.6 9.6.1.82.24.3 9.6.1.83.28.3
SNMP Engine ID
The Engine ID is used by SNMPv3 entities to uniquely identify them. An SNMP agent is considered an authoritative SNMP engine. This means that the agent responds to incoming messages (Get, GetNext, GetBulk, Set) and sends trap messages to a manager. The agent's local information is encapsulated in fields in the message. Each SNMP agent maintains local information that is used in SNMPv3 message exchanges. The default SNMP Engine ID is comprised of the enterprise number and the default MAC address. This engine ID must be unique for the administrative domain, so that no two devices in a network have the same engine ID.
450
23
!
SNMP
SNMP Engine ID
Local information is stored in four MIB variables that are read-only (snmpEngineId, snmpEngineBoots, snmpEngineTime, and snmpEngineMaxMessageSize).
CAUTION When the engine ID is changed, all configured users and groups are erased.
Use DefaultSelect to use the device-generated engine ID. The default engine ID is based on the device MAC address, and is defined per standard as: First 4 octetsFirst bit = 1, the rest is the IANA enterprise number. Fifth octetSet to 3 to indicate the MAC address that follows. Last 6 octetsMAC address of the device.
NoneNo engine ID is used. User DefinedEnter the local device engine ID. The field value is a hexadecimal string (range: 10 - 64). Each byte in the hexadecimal character strings is represented by two hexadecimal digits.
All remote engine IDs and their IP addresses are displayed in the Remote Engine ID table.
STEP 3 Click Apply. The Running Configuration file is updated.
The Remote Engine ID table shows the mapping between IP addresses of the engine and Engine ID. To add the IP address of an engine ID:
STEP 4 Click Add. Enter the following fields:
Server DefinitionSelect whether to specify the Engine ID server by IP address or name. IP VersionSelect the supported IP format. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are:
451
SNMP
Configuring SNMP Views
23
Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceSelect the link local interface (if IPv6 Address Type Link Local is selected) from the list. Server IP Address/NameEnter the IP address or domain name of the log server. Engine IDEnter the Engine ID.
452
23
SNMP
Creating SNMP Groups
Object ID SubtreeSelect the node in the MIB tree that is included or excluded in the selected SNMP view. The options to select the object are as follows: Select from listEnables you to navigate the MIB tree. Press the Up arrow to go to the level of the selected node's parent and siblings; press the Down arrow to descend to the level of the selected node's children. Click nodes in the view to pass from one node to its sibling. Use the scrollbar to bring siblings in view. User DefinedEnter an OID not offered in the Select from list option.
STEP 4 Select or deselect Include in view. If this is selected, the selected MIBs are
Filter: View Name list. The following views exist by default: DefaultDefault SNMP view for read and read/write views. DefaultSuperDefault SNMP view for administrator views.
Other views can be added. Object ID SubtreeDisplays the subtree to be included or excluded in the SNMP view. Object ID Subtree View TypeDisplays whether the defined subtree is included or excluded in the selected SNMP view.
453
SNMP
Creating SNMP Groups
23
PrivacySNMP frames can carry encrypted data. Thus, in SNMPv3, there are three levels of security: No security (No authentication and no privacy) Authentication (Authentication and no privacy) Authentication and privacy
SNMPv3 provides a means of controlling the content each user can read or write and the notifications they receive. A group defines read/write privileges and a level of security. It becomes operational when it is associated with an SNMP user or community.
NOTE To associate a non-default view with a group, first create the view in the Views
page.
This page contains the existing SNMP groups and their security levels.
STEP 2 Click Add. STEP 3 Enter the parameters.
Group NameEnter a new group name. Security ModelSelect the SNMP version attached to the group, SNMPv1, v2, or v3.
Three types of views with various security levels can be defined. For each security level, select the views for Read, Write and Notify by entering the following fields: EnableSelect this field to enable the Security Level. Security LevelDefine the security level attached to the group. SNMPv1 and SNMPv2 support neither authentication nor privacy. If SNMPv3 is selected, choose one of the following: No Authentication and No PrivacyNeither the Authentication nor the Privacy security levels are assigned to the group. Authentication and No PrivacyAuthenticates SNMP messages, and ensures the SNMP message origin is authenticated but does not encrypt them.
454
23
SNMP
Managing SNMP Users
ViewAssociating a view with the read, write, and notify access privileges of the group limits the scope of the MIB tree to which the group has read, write, and notify access. ViewSelect a previously-defined view for Read, Write and Notify. ReadManagement access is read-only for the selected view. Otherwise, a user or a community associated with this group is able to read all MIBs except those that control SNMP itself. WriteManagement access is write for the selected view. Otherwise, a user or a community associated with this group is able to write all MIBs except those that control SNMP itself. NotifyLimits the available content of the traps to those included in the selected view. Otherwise, there is no restriction on the contents of the traps. This can only be selected for SNMPv3.
STEP 4 Click Apply. The SNMP group is saved to the Running Configuration file.
455
SNMP
Managing SNMP Users
23
To display SNMP users and define new ones:
This page provides information for assigning SNMP access control privileges to SNMP users.
STEP 3 Enter the parameters.
User NameEnter a name for the user. Engine IDSelect either the local or remote SNMP entity to which the user is connected. Changing or removing the local SNMP Engine ID deletes the SNMPv3 User Database. To receive inform messages and request information, you must define both a local and remote user. LocalUser is connected to the local device. Remote IP AddressUser is connected to a different SNMP entity besides the local device. If the remote Engine ID is defined, remote devices receive inform messages, but cannot make requests for information. Enter the remote engine ID.
Group NameSelect the SNMP group to which the SNMP user belongs. SNMP groups are defined in the Add Group page.
NOTE Users, who belong to groups which have been deleted, remain, but
they are inactive. Authentication MethodSelect the Authentication method that varies according to the Group Name assigned. If the group does not require authentication, then the user cannot configure any authentication. The options are: NoneNo user authentication is used. MD5 PasswordA password that is used for generating a key by the MD5 authentication method. SHA PasswordA password that is used for generating a key by the SHA (Secure Hash Algorithm) authentication method.
456
23
SNMP
Defining SNMP Communities
Authentication PasswordIf authentication is accomplished by either a MD5 or a SHA password, enter the local user password in either Encrypted or Plaintext. Local user passwords are compared to the local database. and can contain up to 32 ASCII characters. Privacy MethodSelect one of the following options: NonePrivacy password is not encrypted. DESPrivacy password is encrypted according to the Data Encryption Standard (DES).
Privacy Password16 bytes are required (DES encryption key) if the DES privacy method was selected. This field must be exactly 32 hexadecimal characters. The Encrypted or Plaintext mode can be selected.
457
SNMP
Defining SNMP Communities
23
This page contains a table of configured SNMP communities and their properties.
STEP 2 Click Add.
This page enables network managers to define and configure new SNMP communities.
STEP 3 SNMP Management StationClick User Defined to enter the management
station IP address that can access the SNMP community. Click All to indicate that any IP device can access the SNMP community. IP VersionSelect either IPv4 or IPv6. IPv6 Address TypeSelect the supported IPv6 address type if IPv6 is used. The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceIf the IPv6 address type is Link Local, select whether it is received through a VLAN or ISATAP. IP AddressEnter the SNMP management station IP address. Community StringEnter the community name used to authenticate the management station to the device. BasicSelect this mode for a selected community. In this mode, there is no connection to any group. You can only choose the community access level (Read Only, Read Write, or SNMP Admin) and, optionally, further qualify it for a specific view. By default, it applies to the entire MIB. If this is selected, enter the following fields: Access ModeSelect the access rights of the community. The options are: Read OnlyManagement access is restricted to read-only. Changes cannot be made to the community.
458
23
SNMP
Defining Trap Settings
Read WriteManagement access is read-write. Changes can be made to the device configuration, but not to the community. SNMP AdminUser has access to all device configuration options, as well as permissions to modify the community. SNMP Admin is equivalent to Read Write for all MIBs except for the SNMP MIBs. SNMP Admin is required for access to the SNMP MIBs. View NameSelect an SNMP view (a collection of MIB subtrees to which access is granted).
AdvancedSelect this mode for a selected community. Group NameSelect an SNMP group that determines the access rights.
STEP 4 Click Apply. The SNMP Community is defined, and the Running Configuration is
updated.
notifications.
STEP 3 Select Enable for Authentication Notifications to enable SNMP authentication
failure notification.
STEP 4 Click Apply. The SNMP Trap settings are written to the Running Configuration file.
459
SNMP
Notification Recipients
23
Trap messages are generated to report system events, as defined in RFC 1215. The system can generate traps defined in the MIB that it supports. Trap receivers (aka Notification Recipients) are network nodes where the trap messages are sent by the device. A list of notification recipients are defined as the targets of trap messages. A trap receiver entry contains the IP address of the node and the SNMP credentials corresponding to the version that is included in the trap message. When an event arises that requires a trap message to be sent, it is sent to every node listed in the Notification Recipient Table. The Notification Recipients SNMPv1,2 page and the Notification Recipients SNMPv3 page enable configuring the destination to which SNMP notifications are sent, and the types of SNMP notifications that are sent to each destination (traps or informs). The Add/Edit pop-ups enable configuring the attributes of the notifications. An SNMP notification is a message sent from the device to the SNMP management station indicating that a certain event has occurred, such as a link up/ down. It is also possible to filter certain notifications. This can be done by creating a filter in the Notification Filter page and attaching it to an SNMP notification recipient. The notification filter enables filtering the type of SNMP notifications that are sent to the management station based on the OID of the notification that is about to be sent.
Notification Recipients
Server DefinitionSelect whether to specify the remote log server by IP address or name.
460
23
IP VersionSelect either IPv4 or IPv6. -
SNMP
Notification Recipients
IPv6 Address TypeSelect either Link Local or Global. Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceIf the IPv6 address type is Link Local, select whether it is received through a VLAN or ISATAP. Recipient IP Address/NameEnter the IP address or server name of where the traps are sent. UDP PortEnter the UDP port used for notifications on the recipient device. Notification TypeSelect whether to send Traps or Informs. If both are required, two recipients must be created. TimeoutEnter the number of seconds the device waits before re-sending informs. RetriesEnter the number of times that the device resends an inform request. Community StringSelect from the pull-down the community string of the trap manager. Community String names are generated from those listed in the Community page. Notification VersionSelect the trap SNMP version. Either SNMPv1 or SNMPv2 may be used as the version of traps, with only a single version enabled at a time. Notification FilterSelect to enable filtering the type of SNMP notifications sent to the management station. The filters are created in the Notification Filter page. Filter NameSelect the SNMP filter that defines the information contained in traps (defined in the Notification Filter page).
STEP 4 Click Apply. The SNMP Notification Recipient settings are written to the Running
Configuration file.
461
SNMP
Notification Recipients
23
Defining SNMPv3 Notification Recipients
To define a recipient in SNMPv3:
Server DefinitionSelect whether to specify the remote log server by IP address or name. IP VersionSelect either IPv4 or IPv6. IPv6 Address TypeSelect the IPv6 address type (if IPv6 is used). The options are: Link LocalThe IPv6 address uniquely identifies hosts on a single network link. A link local address has a prefix of FE80, is not routable, and can be used for communication only on the local network. Only one link local address is supported. If a link local address exists on the interface, this entry replaces the address in the configuration. GlobalThe IPv6 address is a global Unicast IPV6 type that is visible and reachable from other networks.
Link Local InterfaceSelect the link local interface (if IPv6 Address Type Link Local is selected) from the pull-down list. Recipient IP Address/NameEnter the IP address or server name of where the traps are sent. UDP PortEnter the UDP port used to for notifications on the recipient device. Notification TypeSelect whether to send traps or informs. If both are required, two recipients must be created. TimeoutEnter the amount of time (seconds) the device waits before resending informs/traps. Timeout: Range 1-300, default 15 RetriesEnter the number of times that the device resends an inform request. Retries: Range 1-255, default 3
462
23
SNMP
SNMP Notification Filters
User NameSelect from the drop-down list the user to whom SNMP notifications are sent. In order to receive notifications, this user must be defined on the SNMP User page, and its engine ID must be remote. Security LevelSelect how much authentication is applied to the packet.
NOTE The Security Level here depends on which User Name was selected. If this User Name was configured as No Authentication, the Security Level is No Authentication only. However, if this User Name has assigned Authentication and Privacy on the User page, the security level on this screen can be either No Authentication, or Authentication Only, or Authentication and Privacy.
AuthenticationIndicates the packet is authenticated but not encrypted. PrivacyIndicates the packet is both authenticated and encrypted.
Notification FilterSelect to enable filtering the type of SNMP notifications sent to the management station. The filters are created in the Notification Filter page. Filter NameSelect the SNMP filter that defines the information contained in traps (defined in the Notification Filter page).
STEP 4 Click Apply. The SNMP Notification Recipient settings are written to the Running
Configuration file.
463
SNMP
SNMP Notification Filters
23
To define a notification filter:
The Notification Filter page contains notification information for each filter. The table is able to filter notification entries by Filter Name.
STEP 2 Click Add. STEP 3 Enter the parameters.
Filter NameEnter a name between 0-30 characters. Object ID SubtreeSelect the node in the MIB tree that is included or excluded in the selected SNMP filter. The options to select the object are as follows: Select from listEnables you to navigate the MIB tree. Press the Up arrow to go to the level of the selected node's parent and siblings; press the Down arrow to descend to the level of the selected node's children. Click nodes in the view to pass from one node to its sibling. Use the scrollbar to bring siblings in view. If Object ID is used, the entered object identifier is included in the view if the Include in filter option is selected.
STEP 4 Select or deselect Include in filter. If this is selected, the selected MIBs are
updated.
464
23
SNMP
SNMP Notification Filters
465
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
78-19308-01