TM RackSwitch G8000 Application Guide Version 1.0 Part Number: BMD00041, November 2008 2350 Mission College Blvd. Suite 600 Santa Clara, CA 95054 www.bladenetwork.
RackSwitch G8000 Application Guide Copyright © 2009 Blade Network Technologies, Inc., 2350 Mission College Blvd., Suite 600, Santa Clara, California, 95054, USA. All rights reserved. Part Number: BMD00041. This document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this document may be reproduced in any form by any means without prior written authorization of Blade Network Technologies, Inc.
Contents Preface 11 Who Should Use This Guide 11 What You’ll Find in This Guide 12 Typographic Conventions 13 How to Get Help 14 Chapter 1: Accessing the Switch 15 Configuring an IP Interface 16 Using Telnet 17 Using the Browser-Based Interface 18 Configuring BBI access via HTTP 18 Configuring BBI access via HTTPS 18 Using SNMP 20 SNMP v1, v2 20 SNMP v3.
RackSwitch G8000 Application Guide Chapter 3: VLANs 47 Overview 48 VLANs and Port VLAN ID Numbers 49 VLAN numbers 49 PVID numbers 50 VLAN Tagging 51 VLAN Topologies and Design Considerations 55 VLAN configuration rules 55 Multiple VLANs with Tagging Adapters 56 VLAN configuration example 58 Private VLANs 59 Private VLAN ports 59 Configuration guidelines 60 Configuration example 60 Chapter 4: Ports and Trunking 63 Overview 64 Statistical load distribution 64 Built-In fault tolerance 64 Before you configure
RackSwitch G8000 Application Guide Why do we need multiple Spanning Trees? 84 PVRST configuration guidelines 85 Configuring PVRST 85 Multiple Spanning Tree Protocol 86 MSTP Region 86 Common Internal Spanning Tree 86 MSTP configuration guidelines 87 Fast Uplink Convergence 91 Configuration Guidelines 91 Configuring Fast Uplink Convergence 91 Chapter 6: Quality of Service 93 Overview 94 Using ACL Filters 95 IP Standard ACLs 96 IP Extended ACLs 96 Understanding ACL priority 98 Assigning ACLs to a port 98 View
RackSwitch G8000 Application Guide Chapter 8: Basic IP Routing 119 IP Routing Benefits 120 Routing Between IP Subnets 121 Example of Subnet Routing 123 Using VLANs to segregate Broadcast Domains 124 Configuration example 124 Dynamic Host Configuration Protocol 127 Chapter 9: IGMP 129 IGMP Snooping 130 FastLeave 131 IGMPv3 Snooping 131 IGMP Snooping configuration example 132 Static Multicast Router 134 Chapter 10: High Availability 135 Uplink Failure Detection 136 Failure Detection Pair 137 Spanning Tree Pr
Figures Figure 2-1:Authenticating a Port Using EAPoL 41 Figure 3-1:Default VLAN settings 52 Figure 3-2:Port-based VLAN assignment 53 Figure 3-3:802.1Q tagging (after port-based VLAN assignment) 53 Figure 3-4:802.1Q tag assignment 54 Figure 3-5:802.1Q tagging (after 802.
RackSwitch G8000 Application Guide 8 BMD00041, November 2008
Tables Table 1-1: Table 1-2: Table 1-3: Table 1-4: Table 4-1: Table 5-1: Table 6-1: Table 6-2: Table 6-3: Table 8-1: Table 8-2: Table 8-3: BMD00041, November 2008 User Access Levels 29 Blade OS-proprietary Attributes for RADIUS 29 Default TACACS+ Authorization Levels 31 Alternate TACACS+ Authorization Levels 31 Actor vs.
RackSwitch G8000 Application Guide 10 BMD00041, November 2008
Preface The RackSwitch G8000 Application Guide describes how to configure and use the software on the RackSwitch G8000 switch. For documentation about installing the switch physically, see the Installation Guide for your switch. Who Should Use This Guide This Application Guide is intended for network installers and system administrators engaged in configuring and maintaining a network.
RackSwitch G8000 Application Guide What You’ll Find in This Guide This guide will help you plan, implement, and administer RS G8000 software. Where possible, each section provides feature overviews, usage examples, and configuration instructions. 12 Preface Chapter 1, “Accessing the Switch,” describes how to access the switch to perform administration tasks.
RackSwitch G8000 Application Guide Typographic Conventions The following table describes the typographic styles used in this book. Table 1 Typographic Conventions Typeface or Symbol Meaning Example AaBbCc123 This type is used for names of commands, files, and directories used within the text. View the readme.txt file. It also depicts on-screen computer output and Main# prompts. AaBbCc123 This bold type appears in command examples. It shows text that must be typed in exactly as shown.
RackSwitch G8000 Application Guide How to Get Help If you need help, service, or technical assistance, call Blade Network Technologies Technical Support: US toll free calls: 1-800-414-5268 International calls: 1-408-834-7871 You also can visit our website at the following address: http://www.bladenetwork.net Click the Support tab. The warranty card received with your product provides details for contacting a customer support representative.
CHAPTER 1 Accessing the Switch The Blade OS software provides means for accessing, configuring, and viewing information and statistics about the RackSwitch G8000.
RackSwitch G8000 Application Guide Configuring an IP Interface To manage the switch using Telnet, SNMP, or a Web browser, you must configure an IP interface. Configure the following IP parameters: IP address Subnet mask Default gateway address 1. Log on to the switch. 2. Enter IP interface mode. RS G8000> enable RS G8000# configure terminal RS G8000 (config)# interface ip 1 3. Configure an IP interface, subnet mask, and VLAN assignment. Enable the interface. RS RS RS RS RS 4.
RackSwitch G8000 Application Guide Using Telnet A Telnet connection offers the convenience of accessing the switch from any workstation connected to the network. Telnet access provides the same options for user access and administrator access as those available through the console port. To configure the switch for Telnet access, the switch must have an IP address.
RackSwitch G8000 Application Guide Using the Browser-Based Interface The Browser-Based Interface (BBI) is a Web-based management interface for interactive switch access through your Web browser. The BBI provides access to the common configuration, management and operation features of the switch through your Web browser. For more information, refer to the RackSwitch G8000 BBI Quick Guide. Configuring BBI access via HTTP By default, BBI access via HTTP is enabled.
RackSwitch G8000 Application Guide Accessing the BBI via HTTPS requires a SSL certificate to be used during the key exchange. A default certificate is created the first time HTTPS is enabled, but you can import a new certificate that defines the information you want to be used. Use the following command to import the SSL certificate: RS G8000 (config)# access https import-certificate The certificate is saved to Flash memory for use once the switch is rebooted. When a client (e.g.
RackSwitch G8000 Application Guide Using SNMP Blade OS provides SNMP v1.0 and SNMP v3.0 support for access through any network management software, such as IBM Director or HP-OpenView. SNMP v1, v2 To access the SNMP agent on the G8000, the read and write community strings on the SNMP manager should be configured to match those on the switch. The default read community string on the switch is public and the default write community string is private.
RackSwitch G8000 Application Guide To configure an SNMP user name, enter the following command: RS G8000 (config)# snmp-server user <1-16> name <1-32> User configuration: Users can be configured to use the authentication/privacy options. The G8000 supports two authentication algorithms: MD5 and SHA, as specified in the following command: snmp-server user <1-16> authentication-protocol md5|sha 1.
RackSwitch G8000 Application Guide 3. Assign the user to the user group. Use the group table to link the user to a particular access group.
RackSwitch G8000 Application Guide Configuring SNMP Trap Hosts SNMPv1 trap host 1. Configure an entry in the notify table. RS G8000 (config)# snmp-server notify 10 name public RS G8000 (config)# snmp-server notify 10 tag v1trap 2. Specify the IP address and other trap parameters in the targetAddr and targetParam tables.
RackSwitch G8000 Application Guide SNMPv3 trap host configuration To configure a user for SNMPv3 traps, you can choose to send the traps with both privacy and authentication, with authentication only, or without privacy or authentication. This is configured in the access table using the following commands: RS G8000 (config)# snmp-server access <1-32> level RS G8000 (config)# snmp-server target-parameters <1-16> Configure the user in the user table accordingly.
RackSwitch G8000 Application Guide Securing Access to the Switch Secure switch management is needed for environments that perform significant management functions across the Internet.
RackSwitch G8000 Application Guide RADIUS Authentication and Authorization Blade OS supports the RADIUS (Remote Authentication Dial-in User Service) method to authenticate and authorize remote administrators for managing the switch. This method is based on a client/server model. The Remote Access Server (RAS)—the switch—is a client to the back-end database server. A remote user (the remote administrator) interacts only with the RAS, not the back-end server and database.
RackSwitch G8000 Application Guide Configuring RADIUS Use the following procedure to configure RADIUS authentication on your switch. 1. Configure the Primary and Secondary RADIUS servers, and enable RADIUS authentication. RS G8000 (config)# radius-server primary-host 10.10.1.1 RS G8000 (config)# radius-server secondary-host 10.10.1.2 RS G8000 (config)# radius-server enable 2. Configure the RADIUS secret and enable the feature. RS G8000 (config)# radius-server primary-host 10.10.1.
RackSwitch G8000 Application Guide RADIUS authentication features in Blade OS Blade OS supports the following RADIUS authentication features: Supports RADIUS client on the switch, based on the protocol definitions in RFC 2138 and RFC 2866. Allows RADIUS secret password up to 32 bytes and less than 16 octets.
RackSwitch G8000 Application Guide Switch User Accounts The user accounts listed in Table 1-1 can be defined in the RADIUS server dictionary file. Table 1-1 User Access Levels User Account Description and Tasks Performed Password User The User has no direct responsibility for switch management. He/she can view all switch status information and statistics but cannot make any configuration changes to the switch. user Operator The Operator manages all functions of the switch.
RackSwitch G8000 Application Guide TACACS+ Authentication Blade OS supports authentication and authorization with networks using the Cisco Systems TACACS+ protocol. The G8000 functions as the Network Access Server (NAS) by interacting with the remote client and initiating authentication and authorization sessions with the TACACS+ access server. The remote user is defined as someone requiring management access to the G8000 through a data port.
RackSwitch G8000 Application Guide TACACS+ authentication features in Blade OS Authentication is the action of determining the identity of a user, and is generally done when the user first attempts to log in to a device or gain access to its services. Blade OS supports ASCII inbound login to the device. PAP, CHAP and ARAP login methods, TACACS+ change password requests, and one-time password authentication are not supported.
RackSwitch G8000 Application Guide If the remote user is successfully authenticated by the authentication server, the switch verifies the privileges of the remote user and authorizes the appropriate access. The administrator has an option to allow secure backdoor access via Telnet/SSH. Secure backdoor provide switch access when the TACACS+ servers cannot be reached. NOTE – To obtain the TACACS+ backdoor password for your G8000, contact Technical Support.
RackSwitch G8000 Application Guide When TACACS+ Command Logging is enabled, Blade OS configuration commands are logged on the TACACS+ server.
RackSwitch G8000 Application Guide Secure Shell Secure Shell (SSH) use secure tunnels to encrypt and secure messages between a remote administrator and the switch. Telnet does not provide this level of security. The Telnet method of managing a G8000 does not provide a secure connection. SSH is a protocol that enables remote administrators to log securely into the G8000 over a network to execute management commands.
RackSwitch G8000 Application Guide Generating RSA Host and Server Keys for SSH access To support the SSH server feature, two sets of RSA keys (host and server keys) are required. The host key is 1024 bits and is used to identify the G8000. The server key is 768 bits and is used to make it impossible to decipher a captured session by breaking into the G8000 at a later time.
RackSwitch G8000 Application Guide End User Access Control Blade OS allows an administrator to define end user accounts that permit end users to perform operation tasks via the switch CLI commands. Once end user accounts are configured and enabled, the switch requires username/password authentication. For example, an administrator can assign a user, who can then log into the switch and perform operational commands (effective only until the next switch reboot).
RackSwitch G8000 Application Guide Defining a User’s access level The end user is by default assigned to the user access level (also known as class of service, or COS). COS for all user accounts have global access to all resources except for User COS, which has access to view only resources that the user owns. For more information, see Table 1-1 “User Access Levels” on page 29.
RackSwitch G8000 Application Guide 38 Chapter 1: Accessing the Switch BMD00041, November 2008
CHAPTER 2 Port-based Network Access Control Port-Based Network Access control provides a means of authenticating and authorizing devices attached to a LAN port that has point-to-point connection characteristics. It prevents access to ports that fail authentication and authorization. This feature provides security to ports of the G8000 that connect to servers. The following topics are discussed in this section: “Extensible Authentication Protocol over LAN” on page 40 “802.
RackSwitch G8000 Application Guide Extensible Authentication Protocol over LAN The G8000 can provide user-level security for its ports using the IEEE 802.1X protocol, which is a more secure alternative to other methods of port-based network access control. Any device attached to an 802.1X-enabled port that fails authentication is prevented access to the network and denied services offered through that port. The 802.
RackSwitch G8000 Application Guide 802.1X authentication process The clients and authenticators communicate using Extensible Authentication Protocol (EAP), which was originally designed to run over PPP, and for which the IEEE 802.1X Standard has defined an encapsulation method over Ethernet frames, called EAP over LAN (EAPOL). Figure 2-1 shows a typical message exchange initiated by the client. RADIUS Server 802.
RackSwitch G8000 Application Guide EAPoL message exchange During authentication, EAPOL messages are exchanged between the client and the G8000 authenticator, while RADIUS-EAP messages are exchanged between the G8000 authenticator and the RADIUS server. Authentication is initiated by one of the following methods: The G8000 authenticator sends an EAP-Request/Identity packet to the client Client sends an EAPOL-Start frame to the G8000 authenticator, which responds with an EAP-Request/Identity frame.
RackSwitch G8000 Application Guide 802.1X port states The state of the port determines whether the client is granted access to the network, as follows: Unauthorized While in this state the port discards all ingress and egress traffic except EAP packets. Authorized When the client is successfully authenticated, the port transitions to the authorized state allowing all traffic to and from the client to flow normally.
RackSwitch G8000 Application Guide Supported RADIUS attributes The G8000 802.1X Authenticator relies on external RADIUS servers for authentication with EAP. Table 2 lists the RADIUS attributes that are supported as part of RADIUS-EAP authentication based on the guidelines specified in Annex D of the 802.1X standard and RFC 3580.
RackSwitch G8000 Application Guide Configuration guidelines When configuring EAPoL, consider the following guidelines: The 802.1X port-based authentication is currently supported only in point-to-point configurations, that is, with a single supplicant connected to an 802.1X-enabled switch port. When 802.1X is enabled, a port has to be in the authorized state before any other Layer 2 feature can be operationally enabled.
RackSwitch G8000 Application Guide 46 Chapter 2: Port-based Network Access Control BMD00041, November 2008
CHAPTER 3 VLANs This chapter describes network design and topology considerations for using Virtual Local Area Networks (VLANs). VLANs commonly are used to split up groups of network users into manageable broadcast domains, to create logical segmentation of workgroups, and to enforce security policies among logical segments.
RackSwitch G8000 Application Guide Overview Setting up virtual LANs (VLANs) is a way to segment networks to increase network flexibility without changing the physical network topology. With network segmentation, each switch port connects to a segment that is a single broadcast domain. When a switch port is configured to be a member of a VLAN, it is added to a group of ports (workgroup) that belong to one broadcast domain. Ports are grouped into broadcast domains by assigning them to the same VLAN.
RackSwitch G8000 Application Guide VLANs and Port VLAN ID Numbers VLAN numbers The G8000 supports up to 1024 VLANs per switch. Even though the maximum number of VLANs supported at any given time is 1024, each can be identified with any number between 1 and 4094. VLAN 1 is the default VLAN for all ports.
RackSwitch G8000 Application Guide PVID numbers Each port in the switch has a configurable default VLAN number, known as its PVID. By default, the PVID for all ports is set to 1, which correlates to the default VLAN ID. The PVID for each port can be configured to any VLAN number between 1 and 4094.
RackSwitch G8000 Application Guide VLAN Tagging Blade OS software supports IEEE 802.1Q VLAN tagging, providing standards-based VLAN support for Ethernet systems. Tagging places the VLAN identifier in the frame header of a packet, allowing each port to belong to multiple VLANs. When you add a port to multiple VLANs, you also must enable tagging on that port.
RackSwitch G8000 Application Guide NOTE – If a 802.1Q tagged frame is received by a port that has VLAN-tagging disabled and the port VLAN ID (PVID) is different than the VLAN ID of the packet, then the frame is dropped at the ingress port. Figure 3-1 Default VLAN settings 802.1Q Switch VLAN 1 Port 1 Port 2 Port 3 Port 4 Port 5 Port 6 Port 7 ...
RackSwitch G8000 Application Guide Figure 3-2 through Figure 3-5 illustrate generic examples of VLAN tagging. In Figure 3-2, untagged incoming packets are assigned directly to VLAN 2 (PVID = 2). Port 5 is configured as a tagged member of VLAN 2, and port 7 is configured as an untagged member of VLAN 2. NOTE – The port assignments in the following figures are not meant to match the G8000.
RackSwitch G8000 Application Guide In Figure 3-4, tagged incoming packets are assigned directly to VLAN 2 because of the tag assignment in the packet. Port 5 is configured as a tagged member of VLAN 2, and port 7 is configured as an untagged member of VLAN 2. Figure 3-4 802.1Q tag assignment Data Tag SA Port 4 CRC DA Port 2 Port 3 Tagged member of VLAN 2 Port 5 Port 1 PVID = 2 Tagged packet 802.
RackSwitch G8000 Application Guide VLAN Topologies and Design Considerations By default, the G8000 software is configured so that tagging is disabled on all ports. By default, the G8000 software is configured so that all ports are members of VLAN 1. If you configure Spanning Tree, note that Spanning Tree Groups 2-128 may contain only one VLAN. VLAN configuration rules VLANs operate according to specific configuration rules.
RackSwitch G8000 Application Guide Multiple VLANs with Tagging Adapters Enterprise Routing Switch Server 1 VLAN 1 Server 2 VLAN 1 Enterprise Routing Switch Server 3 VLAN 2 Server 4 VLAN 3 Server 5 VLAN 1, 2 Figure 3-6 Example 1: Multiple VLANs with VLAN-Tagged Gigabit Adapters The features of this VLAN are described below: Component Description G8000 switch This switch is configured with three VLANs that represent three different IP subnets. Five ports are connected downstream to servers.
RackSwitch G8000 Application Guide Component Description Server 1 This server is a member of VLAN 1 and has presence in only one IP subnet. The associated switch port is only a member of VLAN 1, so tagging is disabled. Server 2 This server is a member of VLAN 1 and has presence in only one IP subnet. The associated switch port is only a member of VLAN 1, so tagging is disabled. Server 3 This server belongs to VLAN 2, and it is logically in the same IP subnet as Server 5.
RackSwitch G8000 Application Guide VLAN configuration example Use the following procedure to configure the example network shown in Figure 3-6. 1. Enable VLAN tagging on server ports that support multiple VLANs. RS G8000 (config)# interface port 5 RS G8000 (config-if)# tagging RS G8000 (config-if)# exit 2. Enable tagging on uplink ports that support multiple VLANs. RS RS RS RS RS RS 3.
RackSwitch G8000 Application Guide Private VLANs Private VLANs provide Layer 2 isolation between the ports within the same broadcast domain. Private VLANs can control traffic within a VLAN domain, and provide port-based security for host servers. Use Private VLANs to partition a VLAN domain into sub-domains. Each sub-domain is comprised of one primary VLAN and one or more secondary VLANs, as follows: Primary VLAN—carries unidirectional traffic downstream from promiscuous ports.
RackSwitch G8000 Application Guide Community—A community port is a host port that belongs to a community VLAN. Community ports can communicate with other ports in the same community VLAN, and with promiscuous ports. These interfaces are isolated at layer 2 from all other interfaces in other communities and from isolated ports within the Private VLAN. Configuration guidelines The following guidelines apply when configuring Private VLANs: The default VLAN 1 cannot be a Private VLAN.
RackSwitch G8000 Application Guide 2. Configure a secondary VLAN and map it to the primary VLAN. RS RS RS RS RS RS RS RS 3. G8000 G8000 G8000 G8000 G8000 G8000 G8000 G8000 (config)# vlan (config-vlan)# (config-vlan)# (config-vlan)# (config-vlan)# (config-vlan)# (config-vlan)# (config-vlan)# 110 enable member 3 member 4 private-vlan type isolated private-vlan map 100 private-vlan enable exit Verify the configuration.
RackSwitch G8000 Application Guide 62 Chapter 3: VLANs BMD00041, November 2008
CHAPTER 4 Ports and Trunking Trunk groups can provide super-bandwidth, multi-link connections between switches or other trunk-capable devices. A trunk group is a group of ports that act together, combining their bandwidth to create a single, larger virtual link.
RackSwitch G8000 Application Guide Overview When using port trunk groups between two switches, as shown in Figure 4-1, you can create a virtual link between the switches, operating up to 40 Gb per second, depending on how many physical ports are combined. Each G8000 supports up to 52 static trunk groups (portchannels) and up to 52 LACP trunk groups, consisting of 1-8 ports in each group.
RackSwitch G8000 Application Guide Before you configure static trunks When you create and enable a static trunk, the trunk members (switch ports) take on certain settings necessary for correct operation of the trunking feature. Before you configure your trunk, you must consider these settings, along with specific configuration rules, as follows: 1. Read the configuration rules provided in the section, “Static trunk group configuration rules” on page 65. 2.
RackSwitch G8000 Application Guide All trunk members must be in the same Spanning Tree Group (STG) and can belong to only one Spanning Tree Group (STG). However if all ports are tagged, then all trunk ports can belong to multiple STGs. When a trunk is enabled, the trunk’s Spanning Tree participation setting takes precedence over that of any trunk member. You cannot configure a trunk member as a monitor port in a port-mirroring configuration.
RackSwitch G8000 Application Guide Port Trunking Example In the example below, three ports are trunked between two switches. Trunk 3: Ports 2, 23, and 30 2 30 23 Trunk 1: Ports 1, 7, and 32 7 1 32 Figure 4-1 Port Trunk Group Configuration Example Prior to configuring each switch in the above example, you must connect to the appropriate switch’s Command Line Interface (CLI) as the administrator.
RackSwitch G8000 Application Guide 2. Repeat the process on the other switch. RS G8000 (config)# portchannel 1 member 1,7,32 RS G8000 (config)# portchannel 1 enable # show portchannel 3. Connect the switch ports that will be members in the trunk group. Trunk group 3 (on the G8000) is now connected to trunk group 1 (on the other switch). NOTE – In this example, two G8000 switches are used.
RackSwitch G8000 Application Guide Configurable Trunk Hash Algorithm This feature allows you to configure parameters for the trunk hash algorithm, instead of using the default values. Use the IP Trunk Hash commands to configure new default behavior for Layer 2 traffic and Layer 3 traffic. The trunk hash settings affect both static trunks and LACP trunks.
RackSwitch G8000 Application Guide Link Aggregation Control Protocol Link Aggregation Control Protocol (LACP) is an IEEE 802.3ad standard for grouping several physical ports into one logical port (known as a dynamic trunk group or Link Aggregation group) with any device that supports the standard. Please refer to IEEE 802.3ad-2002 for a full description of the standard. The 802.3ad standard allows standard Ethernet links to form a single Layer 2 link using the Link Aggregation Control Protocol (LACP).
RackSwitch G8000 Application Guide LACP automatically determines which member links can be aggregated and then aggregates them. It provides for the controlled addition and removal of physical links for the link aggregation. Each port on the switch can have one of the following LACP modes. off (default) The user can configure this port in to a regular static trunk group. active The port is capable of forming an LACP trunk. This port sends LACPDU packets to partner system ports.
RackSwitch G8000 Application Guide LACP configuration guidelines Consider the following guidelines when you configure LACP trunks: When ports become members of a trunk, configuration parameters (except ACL and QoS) are applied per trunk. When a trunk group is formed, these parameters are configured for the trunk ID, which overrides the port-level parameters. The range of potential LACP trunk IDs is 53-104.
CHAPTER 5 Spanning Tree When multiple paths exist on a network, Spanning Tree Protocol configures the network so that a switch uses only the most efficient path.
RackSwitch G8000 Application Guide Overview Spanning Tree Protocol detects and eliminates logical loops in a bridged or switched network. When multiple paths exist, Spanning Tree configures the network so that a switch uses only the most efficient path. If that path fails, Spanning Tree automatically sets up another active path on the network to sustain network operations. The G8000 supports the following Spanning Tree Protocols: IEEE 802.1D (2004) Rapid Spanning Tree Protocol (RSTP).
RackSwitch G8000 Application Guide Bridge Protocol Data Units (BPDUs) To create a Spanning Tree, the switch generates a configuration Bridge Protocol Data Unit (BPDU), which it then forwards out of its ports. All switches in the Layer 2 network participating in the Spanning Tree gather information about other switches in the network through an exchange of BPDUs. A BPDU is a 64-byte packet that is sent out at a configurable interval, which is typically set for two seconds.
RackSwitch G8000 Application Guide Port Priority The port priority helps determine which bridge port becomes the root/designated port. The case for the root port is when 2 switches are connected using a minimum of two links with the same path-cost. The case for the designated port is in a network topology that has multiple bridge ports with the same path-cost connected to a single segment—the port with the lowest port priority becomes the designated port for the segment.
RackSwitch G8000 Application Guide Assigning a VLAN to a Spanning Tree Group If no VLANs exist beyond the default VLAN 1 see “Creating a VLAN” on page 78 for information on adding ports to VLANs. Assign the VLAN to the STG using the following command: RS G8000 (config-if)# spanning-tree stp 1 vlan <1-4094> If the association between the spanning-tree group and a VLAN is broken, the spanningtree parameters are cleared. Reconfigure all of the parameters for the STG.
RackSwitch G8000 Application Guide Creating a VLAN When you create a VLAN, that VLAN automatically belongs to STG 1, the default STG. You can assign the VLAN to another STG. Move a newly created VLAN to an existing STG by following this order: Create the VLAN. Enable the VLAN. Add the VLAN to an existing STG. VLANs must be contained within a single STG; a VLAN cannot span multiple STGs.
RackSwitch G8000 Application Guide As an example, assume that port 1 belongs to VLAN 2, and VLAN 2 belongs to STG 2. When you remove port 1 from VLAN 2, port 1 is also removed from STG 2. The port moves to the default VLAN 1. However, if port 1 belongs to both VLAN 1 and VLAN 2 and both VLANs belong to STG 1, removing port 1 from VLAN 2 does not remove port 1 from STG 1 because VLAN 1 is still a member of STG 1. An STG cannot be deleted, only disabled.
RackSwitch G8000 Application Guide Rapid Spanning Tree Protocol Rapid Spanning Tree Protocol (RSTP) provides rapid convergence of the spanning tree and provides for fast re-configuration critical for networks carrying delay-sensitive traffic such as voice and video. RSTP significantly reduces the time to reconfigure the active topology of the network when changes occur to the physical topology or its configuration parameters. RSTP reduces the bridged-LAN topology to a single Spanning Tree.
RackSwitch G8000 Application Guide Port Type and Link Type Spanning Tree configuration includes the following parameters to support RSTP and MSTP: edge port and link type. Edge Port A port that does not connect to a bridge is called an edge port. Edge ports can start forwarding as soon as the link is up. Edge ports do not take part in Spanning Tree, and should not receive BPDUs. A port with Edge enabled is intended to be connected directly to a host.
RackSwitch G8000 Application Guide RSTP configuration example This section provides steps to configure Rapid Spanning Tree on the G8000, using the Command-Line Interface (ISCLI). Rapid Spanning Tree Protocol is the default setting on the G8000. Configure Rapid Spanning Tree Rapid Spanning Tree is the default Spanning Tree mode on the G8000. 1. Configure port and VLAN membership on the switch. 2. Set the Spanning Tree mode to Rapid Spanning Tree.
RackSwitch G8000 Application Guide Per VLAN Rapid Spanning Tree Per VLAN Rapid Spanning Tree Plus Protocol (PVRST+) enhances the RSTP protocol by adding the ability to have multiple spanning tree groups. PVRST+ is based on IEEE 802.1w Rapid Spanning Tree Protocol. In PVRST mode, the G8000 supports a maximum of 128 Spanning Tree Groups (STGs). Multiple STGs provide multiple data paths, which can be used for load-balancing and redundancy.
RackSwitch G8000 Application Guide Why do we need multiple Spanning Trees? The following examples describe why we need multiple spanning trees. In Figure 5-1, VLAN 1 and VLAN 2 pass traffic between switch 1 and switch 2. If you have a single Spanning Tree Group, the switches see an apparent physical loop, and one VLAN may become blocked, affecting connectivity, even though no logical loop exists. VLAN 2 traffic is blocked unnecessarily.
RackSwitch G8000 Application Guide PVRST configuration guidelines This section provides important information about configuring Per VLAN Rapid Spanning Tree Groups: By default, STGs 2-128 are empty, and STG 1 contains all configured VLANs until individual VLANs are assigned to other STGs. The G8000 allows only one VLAN per STG, except for STG 1. If the ports are tagged, each port sends out a special BPDU containing the tagged information.
RackSwitch G8000 Application Guide Multiple Spanning Tree Protocol Multiple Spanning Tree extends Rapid Spanning Tree Protocol through multiple Spanning Tree Groups, using multiple VLANs in each STG. MSTP supports up to 32 Spanning-Tree instances, that correspond to STP Groups 1-32. For more information about Spanning Tree Protocol, see Chapter 5, “Spanning Tree.” In Multiple Spanning Tree Protocol (MSTP), several VLANs can be mapped to each Spanning-Tree instance.
RackSwitch G8000 Application Guide MSTP configuration guidelines This section provides important information about configuring Multiple Spanning Tree Groups: When MSTP is turned on, the switch automatically moves all VLANs to the CIST. When MSTP is turned off, the switch moves all VLANs from the CIST to STG 1. When enabling MSTP, Region Name must be configured, and a default version number of 0 (zero) is configured automatically.
RackSwitch G8000 Application Guide Enterprise Routing Switch (MSTP Group 1 root) Enterprise Routing Switch (MSTP Group 2 root) Passing VLAN 1 Blocking VLAN 2 Server 1 VLAN 2 Server 2 VLAN 2 Blocking VLAN 1 Passing VLAN 2 Server 3 VLAN 1 Server 4 VLAN 1 Server 5 VLAN 1 Figure 5-3 Implementing Multiple Spanning Tree Groups 88 Chapter 5: Spanning Tree BMD00041, November 2008
RackSwitch G8000 Application Guide Configuring Multiple Spanning Tree Groups This configuration shows how to configure MSTP Groups on the switch, as shown in Figure 5-3. 1. Configure port membership and define the Spanning Tree groups for VLAN 1. Enable tagging on uplink ports that share VLANs. Port 51 and port 52 connect to the Enterprise Routing switches.
RackSwitch G8000 Application Guide 3. Configure port membership and define the Spanning Tree groups for VLAN 2. Add server ports 3, 4, and 5 to VLAN 2. Add uplink ports 51 and 52 to VLAN 2. Assign VLAN 2 to Spanning Tree Group 2.
RackSwitch G8000 Application Guide Fast Uplink Convergence Fast Uplink Convergence enables the G8000 to recover quickly from the failure of the primary link or trunk group in a Layer 2 network using Spanning Tree Protocol. Normal recovery can take as long as 50 seconds, while the backup link transitions from Blocking to Listening to Learning and then Forwarding states.
RackSwitch G8000 Application Guide 92 Chapter 5: Spanning Tree BMD00041, November 2008
CHAPTER 6 Quality of Service Quality of Service features allow you to allocate network resources to mission-critical applications at the expense of applications that are less sensitive to such factors as time delays or network congestion. You can configure your network to prioritize specific types of traffic, ensuring that each type receives the appropriate Quality of Service (QoS) level.
RackSwitch G8000 Application Guide Overview QoS helps you allocate guaranteed bandwidth to the critical applications, and limit bandwidth for less critical applications. Applications such as video and voice must have a certain amount of bandwidth to work correctly; using QoS, you can provide that bandwidth when necessary. Also, you can put a high priority on applications that are sensitive to timing out or that cannot tolerate delay, by assigning their traffic to a high-priority queue.
RackSwitch G8000 Application Guide Using ACL Filters Access Control Lists are filters that allow you to classify data packets according to a particular content in the packet header, such as the source address, destination address, source port number, destination port number, and others. Packet classifiers identify flows for more processing. Each filter defines the conditions that must match for inclusion in the filter, and also the actions that are performed when a match is made.
RackSwitch G8000 Application Guide IP Standard ACLs The switch supports up to 127 IP ACLs (standard and extended). IP Standard ACLs are numbered from 1-1000. Use IP Standard ACLs to filter traffic using source IP address/network mask and destination IP address/network/mask.
RackSwitch G8000 Application Guide Table 6-1 Well-known protocol types Number Protocol Name 1 4 6 17 89 103 icmp ip tcp udp ospf pim Table 6-2 Well-known application ports Number TCP/UDP Application Number TCP/UDP Application Number TCP/UDP Application 20 21 22 23 25 37 42 43 53 69 70 ftp-data ftp ssh telnet smtp time name whois domain tftp gopher 79 80 109 110 111 119 123 143 144 161 162 finger http pop2 pop3 sunrpc nntp ntp imap news snmp snmptrap 179 194 220 389 443 520 554 1645, 1812 1813
RackSwitch G8000 Application Guide Understanding ACL priority Each ACL has a unique priority, based on its number. The higher the ACL number, the higher the priority, so ACL 1 has the lowest priority. The priority is used to decide which ACL rule to apply when a packet matches one or more ACLs. When an incoming packet matches the highest priority ACL, the ACL’s configured action takes place. The other assigned ACLs are considered in numeric order, from highest to lowest.
RackSwitch G8000 Application Guide NOTE – To ensure your ACLs function properly, do not assign the same ACL to different ports using different filtering directions. It is recommended that you create two ACLs, one for ingress traffic, and one for egress traffic.
RackSwitch G8000 Application Guide ACL configuration examples Example 1 Use this configuration to block traffic to a specific host. All traffic that ingresses port 1 is denied if it is destined for the host at IP address 100.10.1.1 1. Configure an Access Control List. RS G8000 (config)# access-list ip standard 1 RS G8000 (config-std-nacl)# deny any host 100.10.1.1 RS G8000 (config-std-nacl)# exit 2. Assign the ACL to port 1.
RackSwitch G8000 Application Guide Example 2 Use this configuration to block traffic from a network destined for a specific host address. All traffic that ingresses port 10 with source IP from the class 100.10.1.0/24 and destination IP 200.20.2.2 is denied. 1. Configure an Access Control List. RS G8000 (config)# access-list ip standard 2 RS G8000 (config-std-nacl)# deny 100.10.1.0 255.255.255.0 host 200.20.2.2 RS G8000 (config-std-nacl)# exit 2. Assign the ACL to port 10.
RackSwitch G8000 Application Guide Example 3 Use this configuration to block traffic from a network that is destined for a specific egress port. All traffic that egresses port 6 from the network 100.10.1.0/24 is denied. 1. Configure an Access Control List. RS G8000 (config)# ip access-list ip extended 1001 RS G8000 (config-ext-nacl)# deny ip 100.10.1.0 255.255.255.0 any RS G8000 (config-ext-nacl)# exit 2. Add the ACL to port 6.
RackSwitch G8000 Application Guide Example 5 Use this configuration to block all traffic except traffic of certain types. HTTP/HTTPS, DHCP, and ARP packets are permitted on the port. All other traffic is denied. 1. Configure one IP ACL for each type of traffic that you want to permit. RS RS RS RS RS RS RS RS RS RS RS RS 2.
RackSwitch G8000 Application Guide 5. Assign the ACLs to a port.
RackSwitch G8000 Application Guide Using Storm Control Filters The G8000 provides filters that can limit the number of the following packet types transmitted by switch ports: Broadcast packets Multicast packets Unknown unicast packets (destination lookup failure) Broadcast storms Excessive transmission of broadcast or multicast traffic can result in a broadcast storm. A broadcast storm can overwhelm your network with constant broadcast or multicast traffic, and degrade network performance.
RackSwitch G8000 Application Guide Using DSCP Values to Provide QoS The switch uses the Differentiated Services (DiffServ) architecture to provide QoS functions. DiffServ is described in IETF RFCs 2474 and 2475. The six most significant bits in the TOS byte of the IP header are defined as DiffServ Code Points (DSCP). Packets are marked with a certain value depending on the type of treatment the packet must receive in the network device. DSCP is a measure of the Quality of Service (QoS) level of the packet.
RackSwitch G8000 Application Guide The switch can perform the following actions to the DSCP: Read the DSCP value of ingress packets. Map the DSCP value to an 802.1p priority. The switch can use the DSCP value to direct traffic prioritization. With DiffServ, you can establish policies to direct traffic.
RackSwitch G8000 Application Guide Per Hop Behavior The DSCP value determines the Per Hop Behavior (PHB) of each packet. The PHB is the forwarding treatment given to packets at each hop. QoS policies are built by applying a set of rules to packets, based on the DSCP value, as they hop through the network. The default settings are based on the following standard PHBs, as defined in the IEEE standards: Expedited Forwarding (EF)—This PHB has the highest egress priority and lowest drop precedence level.
RackSwitch G8000 Application Guide QoS Levels Table 6-3 shows the default service levels provided by the switch, listed from highest to lowest importance: Table 6-3 Default QoS Service Levels Service Level Default PHB Critical CS7 7 Network Control CS6 6 Premium EF, CS5 5 Platinum AF41, AF42, AF43, CS4 4 Gold AF31, AF32, AF33, CS3 3 Silver AF21, AF22, AF23, CS2 2 Bronze AF11, AF12, AF13, CS1 1 Standard DF, CS0 0 BMD00041, November 2008 802.
RackSwitch G8000 Application Guide DSCP-to-802.1p mapping The switch can use the DSCP value of ingress packets to set the 802.1p priority value. Use the following command to view the default settings. RS G8000 (config)# show qos dscp Current DSCP Remarking Configuration: DSCP New 802.1p Prio -------- --------------0 0 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 1 9 0 10 1 ...
RackSwitch G8000 Application Guide Using 802.1p Priority to Provide QoS The G8000 provides Quality of Service functions based on the priority bits in a packet’s VLAN header. (The priority bits are defined by the 802.1p standard within the IEEE 802.1Q VLAN header.) The 802.1p bits, if present in the packet, specify the priority that should be given to packets during forwarding. Packets with a numerically higher (non-zero) priority are given forwarding preference over packets with lower priority value.
RackSwitch G8000 Application Guide 802.1p configuration example 1. Configure a port’s default 802.1p priority value to 2. RS G8000 (config)# interface port 1 RS G8000 (config-if)# dot1p 2 RS G8000 (config-if)# exit 2. Map the 802.1p priority value to a COS queue and set the COS queue scheduling weight.
CHAPTER 7 Remote Monitoring Remote Monitoring (RMON) allows network devices to exchange network monitoring data. RMON allows the switch to perform the following functions: Track events and trigger alarms when a threshold is reached. Notify administrators by issuing a syslog message or SNMP trap. Overview The RMON MIB provides an interface between the RMON agent on the switch and an RMON management application. The RMON MIB is described in RFC 1757.
RackSwitch G8000 Application Guide RMON group 1—Statistics The switch supports collection of Ethernet statistics as outlined in the RMON statistics MIB, in reference to etherStatsTable. You can configure RMON statistics on a per-port basis. RMON statistics are sampled every second, and new data overwrites any old data on a given port. NOTE – You must configure RMON statistics for the port before you can view RMON statistics. Configuring RMON statistics 1. Enable RMON on a port.
RackSwitch G8000 Application Guide RMON group 2—History The RMON History group allows you to sample and archive Ethernet statistics for a specific interface during a specific time interval. History sampling is done per port. NOTE – RMON port statistics must be enabled for the port before an RMON history group can monitor the port. Data is stored in buckets, which store data gathered during discreet sampling intervals.
RackSwitch G8000 Application Guide Configuring RMON History Perform the following steps to configure RMON History on a port. 1. Enable RMON on a port. RS G8000 (config)# interface port 1 RS G8000 (config)# rmon enable 2. Configure the RMON History parameters for a port.
RackSwitch G8000 Application Guide Use one of the following commands to correlate an Alarm index to an Event index: RS G8000 (config)# rmon alarm rise-event RS G8000 (config)# rmon alarm fall-event When the alarm threshold is reached, the corresponding event is triggered. Alarm MIB objects The most common data types used for alarm monitoring are ifStats: errors, drops, bad CRCs, and so on.
RackSwitch G8000 Application Guide Example 2 1. Configure the RMON Alarm parameters to track ICMP messages. RS G8000 (config)# rmon alarm 1 oid 1.3.6.1.2.1.5.8.0 alarm-type rising rise-event 110 RS G8000 (config)# rmon alarm 1 interval-time 60 RS G8000 (config)# rmon alarm 1 rising-threshold 200 RS G8000 (config)# rmon alarm 1 sample-type delta RS G8000 (config)# rmon alarm 1 owner "Alarm for icmpInEchos" This configuration creates an RMON alarm that checks icmpInEchos on the switch once every minute.
CHAPTER 8 Basic IP Routing This chapter provides configuration background and examples for using the G8000 to perform IP routing functions.
RackSwitch G8000 Application Guide IP Routing Benefits The switch uses a combination of configurable IP switch interfaces and IP routing options. The switch IP routing capabilities provide the following benefits: Connects the server IP subnets to the rest of the backbone network. Provides the ability to route IP traffic between multiple Virtual Local Area Networks (VLANs) configured on the switch.
RackSwitch G8000 Application Guide Routing Between IP Subnets The physical layout of most corporate networks has evolved over time. Classic hub/router topologies have given way to faster switched topologies, particularly now that switches are increasingly intelligent. The G8000 is intelligent and fast enough to perform routing functions on a par with wire speed Layer 2 switching.
RackSwitch G8000 Application Guide This is a situation that switching alone cannot cure. Instead, the router is flooded with crosssubnet communication. This compromises efficiency in two ways: Routers can be slower than switches. The cross-subnet side trip from the switch to the router and back again adds two hops for the data, slowing throughput considerably. Traffic to the router increases, increasing congestion.
RackSwitch G8000 Application Guide Example of Subnet Routing Consider the role of the G8000 in the following configuration example: Default router: 205.21.17.1 10GbE (port 49) IF 1 VLAN 1 IF 2 VLAN 2 IF 4 VLAN 4 IF 3 VLAN 3 Server subnet 3: 206.30.15.2-254 Server subnet 1: 100.20.10.2-254 Server subnet 2: 131.15.15.2-254 Figure 8-2 Switch-Based Routing Topology The switch connects the Gigabit Ethernet and Fast Ethernet trunks from various switched subnets throughout one building.
RackSwitch G8000 Application Guide Using VLANs to segregate Broadcast Domains If you want to control the broadcasts on your network, use VLANs to create distinct broadcast domains. Create one VLAN for each server subnet, and one for the router. Configuration example This section describes the steps used to configure the example topology shown in Figure 8-2 on page 123. 1. Assign an IP address (or document the existing one) for each router and each server.
RackSwitch G8000 Application Guide 3. Determine which switch ports and IP interfaces belong to which VLANs. The following table adds port and VLAN information: Table 8-3 Subnet Routing Example: Optional VLAN Ports Devices IP Interface Switch Ports VLAN # Default router 1 49 1 Web servers 2 1 and 2 2 Database servers 3 3 and 4 3 Terminal Servers 4 5 and 6 4 NOTE – To perform this configuration, you must be connected to the switch Command Line Interface (CLI) as the administrator. 4.
RackSwitch G8000 Application Guide 5. Assign a VLAN to each IP interface. Now that the ports are separated into VLANs, the VLANs are assigned to the appropriate IP interface for each subnet. From Table 8-3 on page 125, the settings are made as follows: RS RS RS RS RS RS RS RS RS RS RS RS RS RS RS RS RS RS RS RS 6.
RackSwitch G8000 Application Guide Dynamic Host Configuration Protocol Dynamic Host Configuration Protocol (DHCP) is a transport protocol that provides a framework for automatically assigning IP addresses and configuration information to other IP hosts or clients in a large TCP/IP network. Without DHCP, the IP address must be entered manually for each network device.
RackSwitch G8000 Application Guide 128 Chapter 8: Basic IP Routing BMD00041, November 2008
CHAPTER 9 IGMP Internet Group Management Protocol (IGMP) is used by IP Multicast routers to learn about the existence of host group members on their directly attached subnet (see RFC 2236). The IP Multicast routers get this information by broadcasting IGMP Membership Queries and listening for IP hosts reporting their host group memberships.
RackSwitch G8000 Application Guide IGMP Snooping IGMP Snooping allows the switch to forward multicast traffic only to those ports that request it. IGMP Snooping prevents multicast traffic from being flooded to all ports. The switch learns which server hosts are interested in receiving multicast traffic, and forwards it only to ports connected to those servers. IGMP Snooping conserves bandwidth.
RackSwitch G8000 Application Guide FastLeave In normal IGMP operation, when the switch receives an IGMPv2 Leave message, it sends a Group-Specific Query to determine if any other devices in the same group (and on the same port) are still interested in the specified multicast group traffic. The switch removes the affiliated port from that particular group, if the following conditions apply: If the switch does not receive an IGMP Membership Report within the query-responseinterval.
RackSwitch G8000 Application Guide The switch supports the following IGMPv3 filter modes: INCLUDE mode: The host requests membership to a multicast group and provides a list of IP addresses from which it wants to receive traffic. EXCLUDE mode: The host requests membership to a multicast group and provides a list of IP addresses from which it does not want to receive traffic. This indicates that the host wants to receive traffic only from sources that are not part of the Exclude list.
RackSwitch G8000 Application Guide 5. View dynamic IGMP information. RS G8000# show ip igmp groups Note: Local groups (224.0.0.x) are not snooped/relayed and will not appear. Source Group VLAN Port Version Mode Expires Fwd -------------- --------------- ------- ------ -------- ----- ------- --10.1.1.1 232.1.1.1 2 4 V3 INC 4:16 Yes 10.1.1.5 232.1.1.1 2 4 V3 INC 4:16 Yes * 232.1.1.1 2 4 V3 INC No 10.10.10.43 235.0.0.1 9 1 V3 INC 2:26 Yes * 236.0.0.
RackSwitch G8000 Application Guide Static Multicast Router A static multicast router (Mrouter) can be configured for a particular port on a particular VLAN. A static Mrouter does not have to be learned through IGMP Snooping. Any data port can accept a static Mrouter. When you configure a static Mrouter on a VLAN, it replaces any dynamic Mrouters learned through IGMP Snooping. Configure a Static Multicast Router 1.
CHAPTER 10 High Availability The RackSwitch G8000 supports high-availability network topologies. The following topics are discussed in this chapter: “Uplink Failure Detection” on page 136.
RackSwitch G8000 Application Guide Uplink Failure Detection Uplink Failure Detection (UFD) is designed to support Network Adapter Teaming. Network Adapter Teaming allows all the NICs on each server to share the same IP address. The NICs are configured into a team. One NIC is the primary link, and the other is a standby link. UFD allows the switch to monitor specific ports (Link to Monitor ports) to detect link failures.
RackSwitch G8000 Application Guide Failure Detection Pair To use UFD, you must configure a Failure Detection Pair and then turn UFD on. A Failure Detection Pair consists of the following groups of ports: Link to Monitor (LtM) The Link to Monitor group consists of one port or one trunk group. The switch monitors the LtM for link failure. Link to Disable (LtD) The Link to Disable group consists of one or more ports and trunk groups.
RackSwitch G8000 Application Guide Configuring UFD Figure 10-1 shows a basic UFD configuration. In this example, NIC 1 is the primary network adapter; NIC 2 is a non-primary adapter. NIC 1 is connected to port 16 and NIC 2 is connected to port 17. Port 2 is connected to a Layer 2/3 routing switch. The following procedure pertains to the example shown in Figure 10-1. 1. Configure Network Adapter Teaming on the servers. 2. Assign the Link to Monitor (LtM) ports. RS G8000 (config)# ufd fdp ltm port 2 3.
APPENDIX A Troubleshooting This section discusses some tools to help you troubleshoot common problems on the RackSwitch G8000: “Monitoring Ports” on page 140 BMD00041, November 2008 139
RackSwitch G8000 Application Guide Monitoring Ports The port mirroring feature in the G8000 allows you to attach a sniffer to a monitoring port that is configured to receive a copy of all packets that are forwarded from the mirrored port. The G8000 enables you to mirror port traffic for all layer 2 and layer 3. Port mirroring can be used as a troubleshooting tool or to enhance the security of your network.
RackSwitch G8000 Application Guide Port Mirroring behavior This section describes the composition of monitored packets in the switch, based on the configuration of the ports. The following port-mirroring cases apply to the G8000: Ingress mirrored packets are not modified. Egress mirrored packets are tagged with the PVID of the egress port. Configuring Port Mirroring To configure port mirroring for the example shown in Figure A-1: 1.
RackSwitch G8000 Application Guide 142 Appendix A: Troubleshooting BMD00041, November 2008
Index Symbols [ ]....................................................................... 13 configuring IP routing ................................................... 124 port trunking................................................. 68 spanning tree groups ................................ 85, 89 Numerics D 802.1p .............................................................. 111 802.1Q VLAN tagging ......................................... 51 default gateway ...........................................
RackSwitch G8000 Application Guide I N IBM Director .......................................................20 ICMP ..................................................................97 IEEE standards 802.1D .........................................................74 802.1p ........................................................111 802.1Q .........................................................51 802.1s ..........................................................74 802.1w ..................................
RackSwitch G8000 Application Guide RSA keys ........................................................... 35 RSTP ................................................................. 80 S security port mirroring ............................................. 140 RADIUS authentication ................................. 26 TACACS+ authentication .............................. 30 VLANs ....................................................... 47 segmentation. See IP subnets. segments. See IP subnets. service ports...
