HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Guide Part number: 418119-003 Third edition: December 2006
Legal notices © 2004, 2006 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft®, Windows®, and Windows NT® are U.S.
Contents Accessing the switch Introduction ............................................................................................................................................. 8 Additional references ............................................................................................................................... 8 Typographical conventions........................................................................................................................ 9 Management Network......
802.1x port states............................................................................................................................. 41 Supported RADIUS attributes .............................................................................................................. 41 EAPoL configuration guidelines ........................................................................................................... 42 Port-based traffic control ......................................................
Overview.............................................................................................................................................. 70 Using ACL filters .................................................................................................................................... 71 Summary of packet classifiers ............................................................................................................. 71 Summary of ACL actions ......................................
Neighbors and adjacencies ............................................................................................................. 109 Link-State Database ......................................................................................................................... 109 Shortest Path First Tree ..................................................................................................................... 109 Internal versus external routing...............................................
Other network troubleshooting techniques ............................................................................................... 162 Console and Syslog messages .......................................................................................................... 162 Ping .............................................................................................................................................. 162 Trace route.....................................................................
Accessing the switch Introduction This guide will help you plan, implement, and administer the switch software for the HP GbE2c Ethernet Blade Switch and the HP GbE2c Layer 2/3 Ethernet Blade Switch. Where possible, each section provides feature overviews, usage examples, and configuration instructions. • “Accessing the switch” describes how to configure and view information and statistics on the switch over an IP network.
Typographical conventions The following table describes the typographic styles used in this guide: Table 1 Typographic conventions Typeface or symbol Meaning Example AaBbCc123 This type depicts onscreen computer output and prompts. Main# AaBbCc123 This type displays in command examples and shows text that must be typed in exactly as shown. Main# sys This bracketed type displays in command examples as a parameter placeholder.
Connecting through the console port Using a null modem cable, you can directly connect to the switch through the console port. A console connection is required in order to configure Telnet or other remote access applications. For more information on establishing console connectivity to the switch, see the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem User Guide. Connecting through Telnet By default, Telnet is enabled on the switch.
Configuring an IP interface An IP interface address must be set on the switch to provide management access to the switch over an IP network. By default, the management interface is set up to request its IP address from a Bootstrap Protocol (BOOTP) server. If you have a BOOTP server on your network, add the Media Access Control (MAC) address of the switch to the BOOTP configuration file located on the BOOTP server. The MAC address can be found on a small white label on the back panel of the switch.
• Statistics—These menus provide access to the switch statistics and state information. • Dashboard—These menus display settings and operating status of a variety of switch features. Using Simple Network Management Protocol The switch software provides SNMP v1.0 and SNMP v3.0 support for access through any network management software, such as HP-OpenView. SNMP v1.
User configuration Users can be configured to use the authentication/privacy options. The GbE2c supports two authentication algorithms: MD5 and SHA, as specified in the following command: /cfg/sys/ssnmp/snmpv3/usm /auth md5|sha 1. To configure a user with name 'admin,' authentication type MD5, and authentication password of 'admin,' privacy option DES with privacy password of 'admin,' use the following CLI commands: >> >> >> >> >> >> 2.
View based configurations CLI user equivalent To configure an SNMP user equivalent to the CLI 'user,' use the following configuration: /c/sys/ssnmp/snmpv3/usm 4 name "usr" /c/sys/ssnmp/snmpv3/access 3 name "usrgrp" rview "usr" wview "usr" nview "usr" /c/sys/ssnmp/snmpv3/group 4 uname usr gname usrgrp /c/sys/ssnmp/snmpv3/view 6 name "usr" tree " 1.3.6.1.4.1.11.2.3.7.11.33.1.2.1.2" /c/sys/ssnmp/snmpv3/view 7 name "usr" tree " 1.3.6.1.4.1.11.2.3.7.11.33.1.2.1.3" /c/sys/ssnmp/snmpv3/view 8 name "usr" tree " 1.
Configuring SNMP trap hosts SNMPv1 trap host 1. Configure a user with no authentication or password. /c/sys/ssnmp/snmpv3/usm 10 name "v1trap" 2. (Configure user named “v1trap”) Configure an access group and group table entries for the user.
SNMPv2 trap host configuration The SNMPv2 trap host configuration is similar to the SNMPv1 trap host configuration. Wherever you specify the model, specify snmpv2 instead of snmpv1. c/sys/ssnmp/snmpv3/usm 10 name "v2trap" /c/sys/ssnmp/snmpv3/access 10 name "v2trap" model snmpv2 nview "iso" /c/sys/ssnmp/snmpv3/group 10 model snmpv2 uname v2trap gname v2trap /c/sys/ssnmp/snmpv3/notify 10 name v2trap tag v2trap /c/sys/ssnmp/snmpv3/taddr 10 name v2trap addr 47.81.25.
See the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem User Guide for a complete list of supported MIBs. Secure access to the switch Secure switch management is needed for environments that perform significant management functions across the Internet. The following are some of the functions for secured management: • Limiting management users to a specific IP address range. See the “Setting allowable source IP address ranges” section in this chapter.
In this example, the management network is set to 192.192.192.0 and management mask is set to 255.255.255.128. This defines the following range of allowed IP addresses: 192.192.192.1 to 192.192.192.127. The following source IP addresses are granted or not granted access to the switch: • A host with a source IP address of 192.192.192.21 falls within the defined range and would be allowed to access the switch. • A host with a source IP address of 192.192.192.
2. Configure the primary RADIUS secret and secondary RADIUS secret. >> RADIUS Server# secret Enter new RADIUS secret: <1-32 character secret> >> RADIUS Server# secret2 Enter new RADIUS second secret: <1-32 character secret> CAUTION: If you configure the RADIUS secret using any method other than a direct console connection, the secret may be transmitted over the network as clear text. 3. If desired, you may change the default User Datagram Protocol (UDP) port number used to listen to RADIUS.
CAUTION: If you configure the RADIUS secret using any method other than a direct console connection, the secret may be transmitted over the network as clear text. d. Click Submit. 2. Apply, verify, and save the configuration. RADIUS authentication features The switch 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.
User accounts for RADIUS users The user accounts listed in the following table can be defined in the RADIUS server dictionary file. Table 2 User access levels User account Description and tasks performed User User interaction with the switch is completely passive; nothing can be changed on the switch. Users may display information that has no security or privacy implications, such as switch statistics and current operational state information.
• TACACS+ offers full packet encryption whereas RADIUS offers password-only encryption in authentication requests. • TACACS+ separates authentication, authorization, and accounting. How TACACS+ authentication works TACACS+ works much in the same way as RADIUS authentication. 1. Remote administrator connects to the switch and provides user name and password. NOTE: The user name and password can have a maximum length of 128 characters. The password cannot be left blank. 2.
Accounting Accounting is the action of recording a user’s activities on the device for the purposes of billing and/or security. It follows the authentication and authorization actions. If the authentication and authorization is not performed via TACACS+, no TACACS+ accounting messages are sent out. You can use TACACS+ to record and track software logins, configuration changes, and interactive commands.
5. Configure custom privilege-level mapping (optional). >> TACACS+ Server# usermap 2 Current privilege mapping for remote privilege 2: not set Enter new local privilege mapping: user >> TACACS+ Server# usermap 3 user >> TACACS+ Server# usermap 4 user >> TACACS+ Server# usermap 5 oper 6. Apply and save the configuration. Configuring TACACS+ authentication on the switch (BBI example) 1. Configure TACACS+ authentication for the switch. a. Click the Configure context button. b.
e. Configure custom privilege-level mapping (optional). Click Submit to accept each mapping change. 2. Apply, verify, and save the configuration. Secure Shell and Secure Copy Secure Shell (SSH) and Secure Copy (SCP) 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 switch does not provide a secure connection.
Configuring SSH and SCP features (CLI example) Before you can use SSH commands, use the following commands to turn on SSH and SCP. Enabling or disabling SSH To enable the SSH feature, connect to the switch CLI and enter the following commands: >> # /cfg/sys/sshd/on (Turn SSH on) Current status: OFF New status: ON SSHD# apply (Apply the changes to start generating RSA host and server keys) RSA host key generation starts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using SSH and SCP client commands The following shows the format for using some client commands. The examples below use 205.178.15.157 as the IP address of a sample switch. Logging in to the switch Enter the following command to log in to the switch: ssh @ For example: >> # ssh admin@205.178.15.157 Downloading configuration from the switch using SCP Enter the following command to download the switch configuration using SCP.
SSH and SCP encryption of management messages The following encryption and authentication methods are supported for SSH and SCP: • Server Host Authentication—Client RSA authenticates the switch at the beginning of every connection • Key Exchange—RSA • Encryption—AES256-CBC, AES192-CBC, 3DES-CBC, 3DES, ARCFOUR • User Authentication—Local password authentication, RADIUS, TACACS+ Generating RSA host and server keys for SSH access To support the SSH server feature, two sets of RSA keys (host and server
User access control The switch allows an administrator to define end user accounts that permit end users to perform limited actions on the switch. Once end user accounts are configured and enabled, the switch requires username/password authentication. For example, an administrator can assign a user who can log into the switch and perform operational commands (effective only until the next switch reboot). The administrator defines access levels for each switch user, as shown in the following table.
Ports and trunking Introduction The first part of this chapter describes the different types of ports used on the switch. This information is useful in understanding other applications described in this guide, from the context of the embedded switch/server environment. For specific information on how to configure ports for speed, auto-negotiation, and duplex modes, see the port commands in the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Command Reference Guide.
Port trunk groups When using port trunk groups between two switches, you can create an aggregate link operating at up to five Gigabits per second, depending on how many physical ports are combined. The switch supports up to 12 trunk groups per switch, each with up to six ports per trunk group. The trunking software detects broken trunk links (link down or disabled) and redirects traffic to other trunk members within that trunk group.
• You cannot configure a trunk member as a monitor port in a Port Mirroring configuration. • A monitor port cannot monitor trunks; however, trunk members can be monitored. Port trunking example In this example, the Gigabit uplink ports on each switch, and the crosslink ports are configured into a total of five trunk groups: two on each switch, and one trunk group at the crosslink between the two switches. All ports operate at Gigabit Ethernet speed.
Configuring trunk groups (CLI example) 1. 2.
Configuring trunk groups (BBI example) 1. Configure trunk groups. a. Click the Configure context button on the Toolbar. b. Open the Layer 2 folder, and select Trunk Groups. c. Click a Trunk Group number to select it.
d. Enable the Trunk Group. To add ports, select each port in the Ports Available list, and click Add. e. Click Submit. 2. Apply, verify, and save the configuration. 3. Examine the trunking information on each switch. f. Click the Dashboard context button on the Toolbar.
g. Select Trunk Groups. h. Information about each configured trunk group is displayed. Make sure that trunk groups consist of the expected ports and that each port is in the expected state. Configurable Trunk Hash algorithm This feature allows you to configure the particular parameters for the GbE2c Trunk Hash algorithm instead of having to utilize the defaults. You can configure new default behavior for Layer 2 traffic and Layer 3 traffic, using the CLI menu cfg/l2/thash.
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. Refer to the 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).
Configuring LACP Use the following procedure to configure LACP for port 20 and port 21 to participate in link aggregation. 1. Set the LACP mode on port 20. >> # /cfg/l2/lacp/port 20 >> LACP port 20# mode active 2. Define the admin key on port 20. Only ports with the same admin key can form a LACP trunk group. >> LACP port 20# adminkey 100 Current LACP port adminkey: 17 New pending LACP port adminkey: 100 3. (Set port 21 adminkey to 100) Apply and verify the configuration.
Port-based Network Access and traffic control 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 all ports of the GbE2c Ethernet Blade Switch. The following topics are discussed in this section: • Extensible Authentication Protocol over LAN • 802.
The following figure shows a typical message exchange initiated by the client. Figure 2 Using EAPoL to authenticate a port EAPoL Message Exchange During authentication, EAPOL messages are exchanged between the client and the switch authenticator, while RADIUS-EAP messages are exchanged between the switch authenticator and the Radius authentication server. Authentication is initiated by one of the following methods: Switch authenticator sends an EAP-Request/Identity packet to the client.
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 authenticated successfully, the port transitions to the authorized state allowing all traffic to and from the client to flow normally. • Force Unauthorized—You can configure this state that denies all access to the port.
EAPoL 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. For example, the STG state of a port is operationally disabled while the port is in the unauthorized state.
VLANs Introduction This chapter describes network design and topology considerations for using Virtual Local Area Networks (VLANs). VLANs are commonly 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.
Viewing and configuring PVIDs You can view PVIDs from the following CLI commands: Port information >> /info/port Port Tag RMON PVID NAME VLAN(s) ---- --- ---- ---- -------------- ------------------------------1 n d 1 Downlink1 1 2 n e 1 Downlink2 1 3 n d 1 Downlink3 1 4 n d 1 Downlink4 1 5 n d 1 Downlink5 1 6 n d 1 Downlink6 1 7 n d 1 Downlink7 1 : : Port configuration >> /cfg/port 22/pvid 22 Current port VLAN ID: 1 New pending port VLAN ID: 22 >> Port 22# Each port on the switch can belong to one or more
Figure 3 Default VLAN settings NOTE: The port numbers specified in these illustrations may not directly correspond to the physical port configuration of your switch model. When you configure VLANs, you configure the switch ports as tagged or untagged members of specific VLANs. See the following figures. In the following figure, the untagged incoming packet is 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.
Figure 5 802.1Q tagging (after port-based VLAN assignment) In the following figure, the tagged incoming packet is 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 6 802.1Q tag assignment As shown in the following figure, the tagged packet remains unchanged as it leaves the switch through port 5, which is configured as a tagged member of VLAN 2.
VLANs and IP interfaces Carefully consider how you create VLANs within the switch, so that communication with the switch remains possible. In order to access the switch for remote configuration, trap messages, and other management functions, be sure that at least one IP interface on the switch has a VLAN defined. You can also inadvertently cut off access to management functions if you exclude the ports from the VLAN membership.
Figure 8 Multiple VLANs with VLAN tagging The features of this VLAN are described in the following table: Table 10 Multiple VLANs with tagging Component Description Switch 1 Switch 1 is configured for VLANS 1, 2, and 3. Port 1 is tagged to accept traffic from VLANs 1 and 2. Ports 17 and 18 are tagged members of a trunk that accepts traffic from VLANs 1 and 3. Port 20 is tagged to accept traffic from VLANs 1, 2, and 3. Port 23 is an untagged member of VLAN 2.
Table 10 Multiple VLANs with tagging Component Description PC #3 This PC is a member of VLAN 1 and VLAN 2. Via VLAN 1, it can communicate with Server 1 and PC 5. Via VLAN 2, it can communicate with Server 1, PC 1, and PC 5. PC #4 This PC is a member of VLAN 3, and it can communicate with Server 1, Server 2, and PC 1. PC #5 This PC is a member of both VLAN 1 and VLAN 2. Via VLAN 1, it can communicate with Server 1 and PC 3. Via VLAN 2, it can communicate with Server 1, PC 1, and PC 3.
2. Configure the VLANs and their member ports. Since all ports are by default configured for VLAN 1, configure only those ports that belong to VLAN 2. Crosslink ports 17 and 18 must belong to VLANs 1 and 2.
2. Configure the VLANs and their member ports. Since all ports are by default configured for VLAN 1, configure only those ports that belong to other VLANs.
c. Click a port number to select it. d. Enable the port and enable VLAN tagging. e. Click Submit.
2. Configure the VLANs and their member ports. a. Open the Virtual LANs folder, and select Add VLAN. b. Enter the VLAN name, VLAN ID number, and enable the VLAN. To add ports, select each port in the Ports Available list and click Add. Since all ports are configured for VLAN 1 by default, configure only those ports that belong to VLAN 2. The crosslink ports 17 and 18 must belong to VLANs 1 and 2. c. Click Submit.
The external Layer 2 switches should also be configured for VLANs and tagging. 3. Apply, verify, and save the configuration. FDB static entries Static entries in the Forwarding Database (FDB) allow the switch to forward packets without flooding ports to perform a lookup. A FDB static entry is a MAC address associated with a specific port and VLAN. The switch supports 128 static entries.
Spanning Tree Protocol Introduction When multiple paths exist on a network, Spanning Tree Protocol (STP) configures the network so that a switch uses only the most efficient path. The following topics are discussed in this chapter: • Overview • Bridge Protocol Data Units (BPDUs) • Spanning Tree Group (STG) configuration guidelines • Multiple Spanning Trees Overview Spanning Tree Protocol (STP) detects and eliminates logical loops in a bridged or switched network.
Port path cost The port path cost assigns lower values to high-bandwidth ports, such as Gigabit Ethernet, to encourage their use. The objective is to use the fastest links so that the route with the lowest cost is chosen. A value of 0 indicates that port cost is computed dynamically based on link speed. This works when forcing link speed, so it does not just apply to “auto negotiated link speed”. By default, all switch ports have the path cost set to 4, independent of the link speed.
Adding and removing ports from STGs Information on adding and removing ports from STGs is as follows: • By default, all ports belong to VLAN 1 and STG 1. • Each port is always a member of at least one VLAN. Each VLAN is always a member of at least one STG. Port membership within VLANs can be changed, and VLAN membership within STGs can be changed. To move a port from one STG to another, move the VLAN to which the port belongs, or move the port to a VLAN that belongs to the STG.
Figure 9 Two VLANs on one instance of Spanning Tree Protocol In the following figure, VLAN 1 and VLAN 2 belong to different Spanning Tree Groups. The two instances of spanning tree separate the topology without forming a loop, so that both VLANs can forward packets between the switches without losing connectivity.
Configuring Switch 1 (CLI example) 1. Configure port and VLAN membership on Switch 1 as described in the “Configuring ports and VLANs on Switch 1 (CLI example)” section, in the “VLANs” chapter of this guide. 2. Add VLAN 2 to Spanning Tree Group 2. >> /cfg/l2/stp 2 >> Spanning Tree Group 2# add 2 (Select Spanning Tree Group 2) (Add VLAN 2) VLAN 2 is automatically removed from spanning tree group 1. 3. Apply and save.
c. Enter the Spanning Tree Group number and set the Switch Spanning Tree State to on. To add a VLAN to the Spanning Tree Group, select the VLAN in the VLANs Available list, and click Add. VLAN 2 is automatically removed from Spanning Tree Group 1. d. Scroll down, and click Submit. 3. Apply, verify, and save the configuration.
Configuring Port Fast Forwarding Use the following CLI commands to enable Port Fast Forwarding on an external port.
RSTP and MSTP Introduction Rapid Spanning Tree Protocol (IEEE 802.1w) enhances the Spanning Tree Protocol (IEEE 802.1d) to provide rapid convergence on Spanning Tree Group 1. Multiple Spanning Tree Protocol (IEEE 802.1s) extends the Rapid Spanning Tree Protocol to provide both rapid convergence and load balancing in a VLAN environment.
Link type The link type determines how the port behaves in regard to Rapid Spanning Tree. The link type corresponds to the duplex mode of the port. A full-duplex link is point-to-point (p2p), while a half-duplex link should be configured as shared. If you select auto as the link type, the port dynamically configures the link type.
c. Select RSTP mode, and set the MSTP/RSTP state to ON. d. Click Submit. 3. Apply, verify, and save the configuration.
Multiple Spanning Tree Protocol IEEE 802.1s Multiple Spanning Tree extends the IEEE 802.1w Rapid Spanning Tree Protocol through multiple Spanning Tree Groups. MSTP maintains up to 128 spanning-tree instances that correspond to STP Groups 1-128. In Multiple Spanning Tree Protocol (MSTP), several VLANs can be mapped to each Spanning-Tree instance. Each Spanning-Tree instance is independent of other instances.
3. Assign VLANs to Spanning Tree Groups. >> /cfg/l2/stp 2 (Select Spanning Tree Group 2) >> Spanning Tree Group 2# add 2 (Add VLAN 2) >> Spanning Tree Group 2# apply (Apply the configurations) Configuring Multiple Spanning Tree Protocol (BBI example) 1. Configure port and VLAN membership on the switch, as described in the “Configuring ports and VLANs (BBI example)” section in the “VLANs” chapter of this guide. 2. Configure MSTP general parameters. a.
3. Configure Common Internal Spanning Trees (CIST) bridge parameters. a. Open the MSTP/RSTP folder, and select CIST-Bridge. b. Enter the Bridge Priority, Maximum Age, and Forward Delay values. c. Click Submit.
4. Configure Common Internal Spanning Tree (CIST) port parameters. a. Open the MSTP/RSTP folder, and select CIST-Ports. b. Click a port number to select it.
c. Enter the Port Priority, Path Cost, and select the Link Type. Set the CIST Port State to ON. d. Click Submit. 5. Apply, verify, and save the configuration.
Quality of Service Introduction 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.
• Queue and schedule traffic: • Place packets in one of two COS queues • Schedule transmission based on the COS queue weight Using ACL filters Access Control Lists are filters that allow you to classify and segment traffic, so you can provide different levels of service to different traffic types. 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.
Table 15 Well-known application ports Number TCP/UDP Application Number TCP/UDP Application Number 69 tftp 161 snmp 1985 70 gopher 162 snmptrap TCP/UDP Application Table 16 Well-krown TCP flag values Flag Value URG 0x0020 ACK 0x0010 PSH 0x0008 RST 0x0004 SYN 0x0002 FIN 0x0001 • • Packet Format • Ethernet format (eth2, SNAP, LLC) • Ethernet tagging format Egress port packets Note that the egress port ACL will not match a broadcast, multicast, unknown unicast, or Layer 3 pac
Table 17 ACI Precedence Groups Precedence Group ACLs Packet Classifiers Precedence Group 2 ACL 128 – ACL 254 Source MAC address Precedence Level Destination MAC address Ethernet type VLAN ID 802.1p Packet format Precedence Group 3 ACL 255 – ACL 381 Source IP Address Destination IP Address IP protocol TCP source port TCP destination port TCP flags IP Type of Service Egress port Precedence Group 4 ACL 382 – ACL 508 Source MAC address Source IP address Ethernet type VLAN ID 802.
Using ACL Groups Access Control Lists (ACLs) allow you to classify 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. You can define a traffic profile by compiling a number of ACLs into an ACL Group, and assigning the ACL Group to a port. ACL Groups are assigned and enabled on a per-port basis.
Using meters, you set a Committed Rate in Kb/s (1024 bits per second in each Kb/s). All traffic within this Committed Rate is In-Profile. Additionally, you set a Maximum Burst Size that specifies an allowed data burst larger than the Committed Rate for a brief period. These parameters define the In-Profile traffic. Meters keep the sorted packets within certain parameters. You can configure a meter on an ACL, and perform actions on metered traffic, such as packet re-marking.
In this example, all traffic that ingresses on port 20 with source IP from the class 100.10.1.0/24 and destination IP 200.20.1.116 is denied. Example 3: Use this configuration to block traffic from a source that is destined for a specific egress port. >> >> >> >> >> >> >> >> >> >> >> >> >> >> Main# /cfg/acl/acl 1 (Define ACL 1) ACL 1# ethernet/smac 002100000000 ffffffffffff Filtering Ethernet# ..
c. Configure the ACL parameters. Set the Filter Action to Deny, the Ethernet Type to IPv4, and the Destination IP Address to 100.10.1.116. d. Click Submit.
2. Apply, verify, and save the configuration. 3. Add ACL 1 to port 1. a. Click the Configure context button on the Toolbar. b. Select Switch Ports (click the underlined text, not the folder). c. Select a port.
d. Add the ACL to the port. e. Click Submit. 4. Apply, verify, and save the configuration.
Using DSCP values to provide QoS 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. Differentiated Services concepts To differentiate between traffic flows, packets can be classified by their DSCP value.
Table 19 Class selector priority classes Priority Lowest Class Selector DSCP CS2 16 CS1 8 CS0 0 QoS levels The following table shows the default service levels provided by the GbE2c, listed from highest to lowest importance: Table 20 Default QoS service levels Service Level Default PHB 802.
Use the /cfg/qos/8021p/cur command to display the mapping between 802.1p values, Class of Service queues (COSq), and COSq scheduling weights. >> 802.1p# cur Current priority to COS queue configuration: Number of COSq: 2 Priority COSq Weight -------- ---- -----0 0 1 1 0 1 2 0 1 3 0 1 4 1 2 5 1 2 6 1 2 7 1 2 802.1p configuration (CLI example) 1. Configure a port’s default 802.1 priority. >> Main# cfg/port 20 (Select port) >> Port 20# 8021ppri (Set port’s default 802.1p priority) Current 802.
802.1p configuration (BBI example) 1. Configure a port’s default 802.1p priority. a. Click the Configure context button on the Toolbar. b. Select Switch Ports (click the underlined text, not the folder). c. Select a port.
d. Set the 802.1p priority value. e. Click Submit. 2. Map the 802.1p priority value to a COS queue. a. Click the Configure context button on the Toolbar. b. Open the 802.1p folder, and select Priority - CoS.
c. Select an 802.1p priority value. d. Select a Class of Service queue (CoSQ) to correlate with the 802.1p priority value. e. Click Submit. 3. Set the COS queue scheduling weight. a. Click the Configure context button on the Toolbar. b. Open the 802.1p folder, and select CoS - Weight.
c. Select a Class of Service queue (CoS). d. Enter a value for the weight of the Class of Service queue. e. Click Submit. f. Apply, verify, and save the configuration. Queuing and scheduling The GbE2c has two output Class of Service queues (COSq) per port (0-1), into which each packet is placed. Each packet’s 802.1p priority determines its COSq, except when an ACL action sets the COSq of the packet. You can configure the following attributes for COS queues: • Map 802.1p priority value to a COS queue.
Basic IP routing This chapter provides configuration background and examples for using the GbE2c Layer 2/3 Ethernet Blade Switch to perform IP routing functions. The following topics are addressed in this chapter: • IP Routing Benefits • Routing Between IP Subnets • Example of Subnet Routing • Defining IP Address Ranges for the Local Route Cache • Dynamic Host Configuration Protocol NOTE: IP Routing features are available only on the GbE2c Layer 2/3 Ethernet Blade Switch.
Figure 14 Router legacy network In this example, a corporate campus has migrated from a router-centric topology to a faster, more powerful, switchbased topology. As is often the case, the legacy of network growth and redesign has left the system with a mix of illogically distributed subnets. This is a situation that switching alone cannot cure. Instead, the router is flooded with cross-subnet communication. This compromises efficiency in two ways: • Routers can be slower than switches.
Take a closer look at the GbE2c in the following configuration example: Figure 15 Switch-based routing topology The GbE2c connects the Gigabit Ethernet and Fast Ethernet trunks from various switched subnets throughout one building. Common servers are placed on another subnet attached to the switch. Primary and backup routers are attached to the switch on yet another subnet.
2. Assign an IP interface for each subnet attached to the switch. Since there are four IP subnets connected to the switch, four IP interfaces are needed Table 022 Subnet routing example: IP interface assignments Interface Devices IP Interface Address IF 1 Primary and Secondary Default Routers 205.21.17.3 IF 2 First Floor Client Workstations 100.20.10.1 IF 3 Second Floor Client Workstations 131.15.15.1 IF 4 Common Servers 206.30.15.
Using VLANs to segregate broadcast domains In the previous example, devices that share a common IP network are all in the same broadcast domain. If you want to limit the broadcasts on your network, you could use VLANs to create distinct broadcast domains. For example, as shown in the following procedure, you could create one VLAN for the client trunks, one for the routers, and one for the servers. In this example, you are adding to the previous configuration. 1.
3. Add each IP interface to the appropriate VLAN. Now that the ports are separated into three VLANs, the IP interface for each subnet must be placed in the appropriate VLAN. The settings are made as follows: 4. >> VLAN 3# /cfg/l3/if 1 (Select IP interface 1 for def. routers) >> IP Interface 1# vlan 2 (Set to VLAN 2) >> IP Interface 1# ../if 2 (Select IP interface 2 for first floor) >> IP Interface 2# vlan 1 (Set to VLAN 1) >> IP Interface 2# ..
switch. The servers respond as a UDP Unicast message back to the switch, with the default gateway and IP address for the client. The destination IP address in the server response represents the interface address on the switch that received the client request. This interface address tells the switch on which VLAN to send the server response to the client. DHCP relay agent configuration To enable the switch to be the BOOTP forwarder, you need to configure the DHCP/BOOTP server IP addresses on the switch.
Routing Information Protocol In a routed environment, routers communicate with one another to keep track of available routes. Routers can learn about available routes dynamically, using the Routing Information Protocol (RIP). GbE2c software supports RIP version 1 (RIPv1) and RIP version 2 (RIPv2) for exchanging TCP/IP route information with other routers. NOTE: RIP is available only on the GbE2c Layer 2/3 Ethernet Blade Switch. Distance vector protocol RIP is known as a distance vector protocol.
RIPv2 in RIPv1 compatibility mode GbE2c software allows you to configure RIPv2 in RIPv1compatibility mode, for using both RIPv2 and RIPv1 routers within a network. In this mode, the regular routing updates use broadcast UDP data packet to allow RIPv1 routers to receive those packets. With RIPv1 routers as recipients, the routing updates have to carry natural or host mask. Hence, it is not a recommended configuration for most network topologies.
RIP configuration example NOTE: An interface RIP disabled uses all the default values of the RIP, no matter how the RIP parameters are configured for that interface. RIP sends out RIP regular updates to include an Up interface, but not a Down interface. 1. Add VLANs for routing interfaces. >> Main# cfg/l2/vlan 2/ena >> VLAN 2# add 20 (Enable VLAN 2) (Add port 20 to VLAN 2) Port 20 is an UNTAGGED port and its current PVID is 1.
IGMP Snooping Introduction 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 data ports. The switch learns which server hosts are interested in receiving multicast traffic, and forwards it only to ports connected to those servers.
IGMP Filtering With IGMP Filtering, you can allow or deny a port to send and receive multicast traffic to certain multicast groups. Unauthorized users are restricted from streaming multicast traffic across the network. If access to a multicast group is denied, IGMP Membership Reports from the port for that group are dropped, and the port is not allowed to receive IP multicast traffic from that group.
3. View dynamic IGMP information. >> /info/l3/igmp (Select IGMP Information menu) >> IGMP Multicast# dump (Show IGMP Group information) >> Switch-A - IGMP Multicast# dump Group ----------- VLAN Version ------ --------- ------------- V2 V2 20 21 238.1.0.0 238.1.0.
3. Assign the IGMP Filter to a port. >> //cfg/l3/igmp/igmpflt (Select IGMP Filtering menu) >>IGMP Filter# port 24 (Select port 24) >>IGMP Port 24# filt ena (Enable IGMP Filtering on the port) Current port 24 filtering: disabled New port 24 filtering: enabled >>IGMP Port 24# add 1 (Add IGMP Filter 1 to the port) >>IGMP Port 24# apply (Make your changes active Configuring a Static Mrouter (CLI example) 1. Configure a port to which the static Mrouter is connected, and enter the appropriate VLAN.
c. Enable IGMP Snooping. d. Click Submit. 3. Apply, verify, and save the configuration.
Configuring IGMP Filtering (BBI example) 1. Configure IGMP Snooping. 2. Enable IGMP Filtering. a. Click the Configure context button. b. Open the IGMP folder, and select IGMP Filters (click the underlined text, not the folder). c. Enable IGMP Filtering globally. d. Click Submit.
3. Define the IGMP Filter. a. Select Layer 3 > IGMP > IGMP Filters > Add Filter. b. Enable the IGMP Filter. Assign the range of IP multicast addresses and the filter action (allow or deny). c. Click Submit.
4. Assign the filter to a port and enable IGMP Filtering on the port. a. Select Layer 3 > IGMP > IGMP Filters > Switch Ports. b. Select a port from the list.
c. Enable IGMP Filtering on the port. Select a filter in the IGMP Filters Available list, and click Add. d. Click Submit. 5. Apply, verify, and save the configuration. Configuring a Static Multicast Router (BBI example) 1. Configure Static Mrouter. a. Click the Configure context button. b. Open the Switch folder and select IP Menu > IGMP > IGMP Static Mrouter. c. Enter a port number, VLAN ID number, and IGMP version number. d. Click Submit.
2. Apply, verify, and save the configuration.
OSPF GbE2c software supports the Open Shortest Path First (OSPF) routing protocol. The GbE2c implementation conforms to the OSPF version 2 specifications detailed in Internet RFC 1583. The following sections discuss OSPF support for the GbE2c Ethernet Blade Switch: • OSPF Overview: This section provides information on OSPF concepts, such as types of OSPF areas, types of routing devices, neighbors, adjacencies, link state database, authentication, and internal versus external routing.
Figure 17 OSPF area types Types of OSPF routing devices As shown in the figure, OSPF uses the following types of routing devices: • Internal Router (IR)—a router that has all of its interfaces within the same area. IRs maintain LSDBs identical to those of other routing devices within the local area. • Area Border Router (ABR)—a router that has interfaces in multiple areas. ABRs maintain one LSDB for each connected area and disseminate routing information between areas.
Neighbors and adjacencies In areas with two or more routing devices, neighbors and adjacencies are formed. Neighbors are routing devices that maintain information about each others’ health. To establish neighbor relationships, routing devices periodically send hello packets on each of their interfaces.
OSPF implementation in GbE2c software The GbE2c Ethernet Blade Switch supports a single instance of OSPF and up to 4 K routes on the network.
Assigning the area index The aindex option is actually just an arbitrary index (0-2) used only by the switch. This index does not necessarily represent the OSPF area number, though for configuration simplicity, it should where possible. For example, both of the following sets of commands define OSPF area 0 (the backbone) and area 1 because that information is held in the area ID portion of the command.
Interface cost The OSPF link-state algorithm (Dijkstra’s algorithm) places each routing device at the root of a tree and determines the cumulative cost required to reach each destination. Usually, the cost is inversely proportional to the bandwidth of the interface. Low cost indicates high bandwidth.
Figure 19 Injecting default routes In more complex OSPF areas with multiple ABRs or ASBRs (such as area 0 and area 2 in the figure), there are multiple routes leading from the area. In such areas, traffic for unrecognized destinations cannot tell which route leads upstream without further configuration. To resolve the situation and select one default route among multiple choices in an area, you can manually configure a metric value on each ABR.
Router ID Routing devices in OSPF areas are identified by a router ID. The router ID is expressed in IP address format. The IP address of the router ID is not required to be included in any IP interface range or in any OSPF area. The router ID can be configured in one of the following two ways: • Dynamically—OSPF protocol configures the lowest IP interface IP address as the router ID. This is the default.
3. Enable OSPF authentication for Area 2 on switch 4. >> # /cfg/l3/ospf/aindex 2/auth password 4. Configure a simple text password up to eight characters for the virtual link between Area 2 and Area 0 on switches 2 and 4. >> # /cfg/l3/ospf/virt 1/key packard Use the following commands to configure MD5 authentication on the switches shown in the figure: 2. Enable OSPF MD5 authentication for Area 0 on switches 1, 2, and 3 >> # /cfg/l3/ospf/aindex 0/auth md5 5.
OSPF features not supported in this release The following OSPF features are not supported in this release: • Summarizing external routes • Filtering OSPF routes • Using OSPF to forward multicast routes • Configuring OSPF on non-broadcast multi-access networks (such as frame relay, X.25, and ATM) OSPF configuration examples A summary of the basic steps for configuring OSPF on the GbE2c is listed here.
3. Define the backbone. The backbone is always configured as a transit area using areaid 0.0.0.0 >> >> >> >> 4. Shortest Path First # aindex 0(Select menu for area index 0) Area (index) 0 # areaid 0.0.0.0(Set the ID for backbone area 0) Area (index) 0 # type transit(Define backbone as transit type) Area (index) 0 # enable(Enable the area) Define the stub area. >> >> >> >> 5. Open OSPF OSPF OSPF OSPF OSPF OSPF OSPF Area Area Area Area (index) (index) (index) (index) 0 1 1 1 # # # # ..
c. Configure an IP interface. Enter the IP address, subnet mask, and enable the interface. d. Click Submit. 2. Apply, verify, and save the configuration.
3. Enable OSPF. a. Open the OSPF Routing Protocol folder, and select General. b. Enable OSPF. c. Click Submit.
4. Configure OSPF Areas. a. Open the OSPF Areas folder, and select Add OSPF Area. b. Configure the OSPF backbone area 0. c. Click Submit.
d. Select Add OSPF Area. e. Configure the OSPF area 1. f. Click Submit.
5. Configure OSPF Interfaces. a. Open the OSPF Interfaces folder, and select Add OSPF Interface.
b. Configure the OSPF Interface 1, and attach it to the backbone area 0. c. Click Submit. d. Select Add OSPF Interface.
e. Configure the OSPF Interface 2, and attach it to the stub area 1. f. 6. Click Submit. Apply, verify, and save the configuration. Example 2: Virtual links In the example shown in the following figure, area 2 is not physically connected to the backbone as is usually required. Instead, area 2 will be connected to the backbone via a virtual link through area 1. The virtual link must be configured at each endpoint. Figure 22 Configuring a virtual link Configuring OSPF for a virtual link on Switch A 1.
In this example, two IP interfaces are needed on Switch A: one for the backbone network on 10.10.7.0/24 and one for the transit area network on 10.10.12.0/24. >> >> >> >> >> >> (Select menu for IP interface 1) addr 10.10.7.1 (Set IP address on backbone network) mask 255.255.255.0 (Set IP mask on backbone network) enable (Enable IP interface 1) ../if 2 (Select menu for IP interface 2) addr 10.10.12.1 (Set IP address on transit area network) >> IP Interface 2 # mask 255.255.255.
Configuring OSPF for a virtual link on Switch B 1. Configure IP interfaces on each network that will be attached to OSPF areas. Two IP interfaces are needed on Switch B: one for the transit area network on 10.10.12.0/24 and one for the stub area network on 10.10.24.0/24. >> # /cfg/l3/if 1 >> IP Interface 1 # addr 10.10.12.2 >> IP Interface 1 # >> >> >> >> >> 2.
9. Configure the virtual link. The nbr router ID configured in this step must be the same as the router ID that was configured for Switch A in step 2. >> OSPF Interface 2 # ../virt 1 >> OSPF Virtual Link 1 # aindex 1 (Specify a virtual link number) (Specify the transit area for the virtual link) >> OSPF Virtual Link 1 # nbr 10.10.10.1(Specify the router ID of the recipient) >> OSPF Virtual Link 1 # enable (Enable the virtual link) 10. Apply and save the configuration changes.
3. Define the >> >> >> >> backbone. Open Shortest Path First # aindex 0 (Select menu for area index 0) OSPF Area (index) 0 # areaid 0.0.0.0(Set the ID for backbone area 0) OSPF Area (index) 0 # type transit (Define backbone as transit type) OSPF Area (index) 0 # enable (Enable the area) 4. Define the stub area. >> OSPF Area (index) 0 # ../aindex 1 (Select menu for area index 1) >> OSPF Area (index) 1 # areaid 0.0.0.
Remote monitoring Introduction Remote Monitoring (RMON) allows network devices to exchange network monitoring data. RMON performs the following major functions: • Gathers cumulative statistics for Ethernet interfaces • Tracks a history of statistics for Ethernet interfaces • Creates and triggers alarms for user-defined events 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.
2. View RMON statistics for the port.
2. Select a port. 3. Enable RMON on the port. 4. Click Submit.
5. Apply, verify, and save the configuration. 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. 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.
Configure RMON History (BBI example) 1. Configure an RMON History group. a. Click the Configure context button. b. Open the Switch folder, and select RMON > History > Add History Group. 2. Configure RMON History Group parameters. 3. Click Submit. 4. Apply, verify, and save the configuration.
RMON group 3—alarms The RMON Alarm group allows you to define a set of thresholds used to determine network performance. When a configured threshold is crossed, an alarm is generated. For example, you can configure the switch to issue an alarm if more than 1,000 CRC errors occur during a 10-minute time interval. Each Alarm index consists of a variable to monitor, a sampling time interval, and parameters for rising and falling thresholds.
Configure RMON Alarms (CLI example 2) 1. Configure the RMON Alarm parameters to track ICMP messages. >> /cfg/rmon/alarm 5 (Select RMON Alarm 5) >> RMON Alarm 5# oid 1.3.6.1.2.1.5.8.0 >> RMON Alarm 5# intrval 60 >> RMON Alarm 5# almtype rising >> RMON Alarm 5# rlimit 200 >> RMON Alarm 5# revtidx 5 >> RMON Alarm 5# sample delta >> RMON Alarm 5# owner “Alarm_for_icmpInEchos” 2. Apply and save the configuration.
c. Configure RMON Alarm Group parameters to check ifInOctets on port 20 once every hour. Enter a rising limit of two billion, and a rising event index of 6. This configuration creates an RMON alarm that checks ifInOctets on port 20 once every hour. If the statistic exceeds two billion, an alarm is generated that triggers event index 6. 2. Click Submit. 3. Apply, verify, and save the configuration.
Configure RMON Alarms (BBI example 2) 1. Configure an RMON Alarm group. a. Click the Configure context button. b. Open the Switch folder, and select RMON > Alarm > Add Alarm Group. c. 2. Configure RMON Alarm Group parameters to check icmpInEchos, with a polling interval of 60, a rising limit of 200, and a rising event index of 5. This configuration creates an RMON alarm that checks icmpInEchos on the switch once every minute.
3. Apply, verify, and save the configuration. RMON group 9—events The RMON Event group allows you to define events that are triggered by alarms. An event can be a log message, an SNMP trap message, or both. When an alarm is generated, it triggers a corresponding event notification. Use the /cfg/rmon/alarm x/revtidx and /fevtidx commands to correlate an event index to an alarm. RMON events use SNMP and syslogs to send notifications.
Configuring RMON Events (BBI example 1) 1. Configure an RMON Event group. a. Click the Configure context button. b. Open the Switch folder, and select RMON > Event > Add Event Group. c. Configure RMON Event Group parameters. This configuration creates an RMON event that sends a SYSLOG message each time it is triggered by an alarm. 2. Click Submit. 3. Apply, verify, and save the configuration.
High availability Introduction Switches support high availability network topologies. This release provides information about Uplink Failure Detection and Virtual Router Redundancy Protocol (VRRP). VRRP is available only on the GbE2c Layer 2/3 Ethernet Blade Switch. Uplink Failure Detection Uplink Failure Detection (UFD) is designed to support Network Adapter Teaming on HP server blades.
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 uplink port (20-24), or one trunk group that contains only uplink ports. The switch monitors the LtM for link failure. • Link to Disable (LtD) The Link to Disable group consists of one or more downlink ports (1-16) and trunk groups that contain only downlink ports.
Configuring Uplink Failure Detection The preceding figure shows a basic UFD configuration. Port 21 on Blade Switch 1 is connected to a Layer 2/3 routing switch outside of the chassis. Port 20 and port 22 on Blade Switch 2 form a trunk that is connected to a different Layer 2/3 routing switch. The interconnect ports (17-18) are disabled. In this example, NIC 1 is the primary network adapter; NIC 2, NIC 3, and NIC 4 are non-primary adapters.
Configuring Uplink Failure Detection (BBI example) 1. Configure Uplink Failure Detection. a. Click the Configure context button. b. Open the Switch folder, and select Uplink Failure Detection (click the underlined text, not the folder). c. Turn Uplink Failure Detection on, and then select FDP.
d. Enable the FDP. Select ports in the LtM Ports Available list, and click Add to place the ports into the Link to Monitor (LtM). Select ports in the LtD Ports Available list, and click Add to place the ports into the Link to Disable (LtD). e. Click Submit. 2. Apply, verify, and save the configuration.
VRRP overview In a high-availability network topology, no device can create a single point-of-failure for the network or force a single point-of-failure to any other part of the network. This means that your network will remain in service despite the failure of any single device. To achieve this usually requires redundancy for all vital network components.
VRRP operation Only the virtual router master responds to ARP requests. Therefore, the upstream routers only forward packets destined to the master. The master also responds to ICMP ping requests. The backup does not forward any traffic, nor does it respond to ARP requests. If the master is not available, the backup becomes the master and takes over responsibility for packet forwarding and responding to ARP requests.
Active-Active redundancy In an active-active configuration, shown in the following figure, two switches provide redundancy for each other, with both active at the same time. Each switch processes traffic on a different subnet. When a failure occurs, the remaining switch can process traffic on all subnets. The following figure shows an Active-Active configuration example.
Assigning VRRP virtual router ID During the software upgrade process, VRRP virtual router IDs are assigned automatically if failover is enabled on the switch. When configuring virtual routers at any point after upgrade, virtual router ID numbers (/cfg/l3/vrrp/vr #/vrid) must be assigned. The virtual router ID may be configured as any number between 1 and 255. Configuring the switch for tracking Tracking configuration largely depends on user preferences and network environment.
a higher priority. Traffic is forwarded to Switch B, which forwards it to Switch A through the crosslink (ports 17-18). Return traffic uses default gateway 2 (192.168.2.1), and is forwarded through the Layer 2 switch at the bottom of the drawing. To implement the active-active example, perform the following switch configuration. Task 1: Configure Switch A 1. Configure ports. /cfg/l2/vlan 10 >> VLAN 10# ena >> VLAN 10# add 20 >> VLAN 10# .. >> Layer 2# vlan 20 >> VLAN 20# ena >> VLAN 20# add 21 2.
5. Enable tracking on ports. Set the priority of Virtual Router 1 to 101, so that it becomes the Master. /cfg/l3/vrrp/vr 1 >> VRRP Virtual Router 1# track/ports/ena >> VRRP Virtual Router 1 Priority Tracking# .. >> VRRP Virtual Router 1# prio 101 >> VRRP Virtual Router 1# .. >> Virtual Router Redundancy Protocol# vr 2 >> VRRP Virtual Router 1# track/ports/ena 6.
>> VRRP Virtual Router 2# track/ports/ena (Set tracking on ports) >> VRRP Virtual Router 2 Priority Tracking# .. >> VRRP Virtual Router 2# prio 101 (Set the VRRP priority) 6. Turn off Spanning Tree Protocol globally. Apply and save changes. /cfg/l2/stg 1/off >> Spanning Tree Group 1# apply >> Spanning Tree Group 1# save (Turn off STG) Task 1: Configure Switch A (BBI example) 1. Configure ports and VLANs. a. Click the Configure context button. b. Open the Virtual LANs folder, and select Add VLAN.
c. Configure port 20 as a member of VLAN 10 and port 21 as a member of VLAN 20. Enable each VLAN. d. Click Submit. 2. Configure the following client and server interfaces: • IF 1 IP address = 192.168.1.100 Subnet mask = 255.255.255.0 VLAN 10 • IF 2 IP address = 10.10.12.1 Subnet mask = 255.255.255.0 VLAN 20 • IF 3 IP address = 10.10.12.1 Subnet mask = 255.255.255.0 • IF 4 IP address = 10.10.12.1 Subnet mask = 255.255.255.0 a. Open the IP Interfaces folder, and select Add IP Interface.
b. Configure an IP interface. Enter the IP address, subnet mask, and VLAN membership. Enable the interface. c. 3. Click Submit. Configure the default gateways. Each default gateway points to one of the Layer 2 routers. a. Open the Default Gateways folder, and select Add Default Gateway.
b. Configure the IP address for each default gateway. Enable the default gateways. c. 4. Click Submit. Turn on VRRP and configure two Virtual Interface routers. a. Open the Virtual Router Redundancy Protocol folder, and select General.
b. Enable VRRP processing. c. Click Submit. d. Open the Virtual Routers folder, and select Add Virtual Router.
e. Configure the IP address for Virtual Router 1 (VR1). Enable tracking on ports, and set the priority to 101. Enable The Virtual Router. f. Click Submit. g. Select Add Virtual Router.
h. Configure the IP address for Virtual Router 2 (VR2). Enable tracking on ports, but set the priority to 100 (default value). Enable The Virtual Router. i. 5. Click Submit. Turn off Spanning Tree globally. a. Open the Spanning Tree Groups folder, and select Add Spanning Tree Group.
b. Enter Spanning Tree Group ID 1 and set the Switch Spanning Tree State to off. c. 6. Click Submit. Apply, verify, and save the configuration.
Troubleshooting tools Introduction This appendix discusses some tools to help you use the Port Mirroring feature to troubleshoot common network problems on the switch. Port Mirroring The Port Mirroring feature on the switch is very useful for troubleshooting any connection-oriented problem. Any traffic in or out of one or more ports can be mirrored to a single monitoring port to which a network monitor can be attached.
Configuring Port Mirroring (CLI example) To configure Port Mirroring for the example shown in the preceding figure: 1. Specify the monitoring port. >> # /cfg/pmirr/monport 20 2. (Select port 20 for monitoring) Select the ports that you want to mirror.
Configuring Port Mirroring (BBI example) 1. Configure Port Mirroring. a. Click the Configure context button. b. Open the Switch folder, and select Port-Based Port Mirroring (click the underlined text, not the folder). c. Click a port number to select a monitoring port. d. Click Add Mirrored Port.
e. Enter a port number for the mirrored port, and select the Port Mirror Direction. f. Click Submit. 2. Apply, verify, and save the configuration. 3. Verify the Port Mirroring information on the switch. Other network troubleshooting techniques Other network troubleshooting techniques include the following. Console and Syslog messages When a switch experiences a problem, review the console and Syslog messages.
Trace route To identify the route used for station-to-station connectivity across the network, execute the following command: traceroute | [ [ msec delay ]] The IP address is the hostname or IP address of the target station. Max-hops (optional) is the maximum distance to trace (1-16 devices). Msec delay (optional) is the number of milliseconds to wait for the response.
Index 802.
Remote Authentication Dial-in User Service (RADIUS): authentication, 18; SSH/SCP, 28 Remote monitoring (RMON), 129 RIP (Routing Information Protocol): advertisements, 94; distance vector protocol, 94; hop count, 94; metric, 94 RIP configuration, example, 96 RIP features, 95 RMON (remote monitoring), 129 RMON groups: alarms, 134; events, 138; examples of, 129, 130, 132, 133, 134, 135, 137, 138, 139, 142; history, 132; statistics, 129 Router ID: OSPF; router ID, 114 routers, 88, 90; border; peer;autonomous sy
