3. If necessary, configure up to two default gateways. 4. Configuring the default gateways allows the switch to send outbound traffic to the routers.
>> >> >> >> >> >> IP Interface 5# Default gateway Default gateway Default gateway Default gateway Default gateway./gw 1 1# addr 205.21.17.1 1# ena 1#./gw 2 2# addr 205.21.17.2 2# ena (Select primary default gateway) (Assign IP address for primary router) (Enable primary default gateway) (Select secondary default gateway) (Assign address for secondary router) (Enable secondary default gateway)
5. Apply, verify, and save the configuration.
>> Default gateway 2# apply >> Default gateway 2# save >> # /cfg/dump (Apply the configuration) (Save the configuration) (Verify the configuration)
Using the Browser-based Interface
By default, the Browser-based Interface (BBI) protocol is enabled on the switch. The Browser-based Interface (BBI) provides access to the common configuration, management and operation features of the switch through your Web browser. For more information, see the HP 1:10Gb Ethernet BL-c Switch Browser-based Interface Reference. The BBI is organized at a high level as follows:
ConfigurationThese menus provide access to the configuration elements for the entire switch.
SystemConfigure general switch configuration elements. Switch portsConfigure switch ports and related features. Port-based port mirroringConfigure mirrored ports and monitoring ports. Layer 2Configure Layer 2 features, including trunk groups, VLANs, and Spanning Tree Protocol. RMON menuConfigure Remote Monitoring (RMON) functions. Layer 3Configure all of the IP related information, including IGMP Snooping. QoSConfigure Quality of Service features. Access ControlConfigure Access Control Lists and Groups. Uplink Failure DetectionConfigure a Failover Pair of Links to Monitor and Links to Disable.
StatisticsThese menus provide access to the switch statistics and state information. DashboardThese 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.0

To access the SNMP agent on the switch, 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. The read and write community strings on the switch can be changed using the following commands on the CLI.

(Assign user to the notify table)
(Define an IP address to send traps)
(Specify SNMPv2 traps to send)
(Define the community string)
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. Use the following commands to configure the access table: /c/sys/ssnmp/snmpv3/access <x>/level /c/sys/ssnmp/snmpv3/tparam <x> Configure the user in the user table to match the configuration of the access table. It is not necessary to configure the community table for SNMPv3 traps because the community string is not used by SNMPv3.
Accessing the switch The following example shows how to configure a SNMPv3 user v3trap with authentication only:
/c/sys/ssnmp/snmpv3/usm 11 name "v3trap" auth md5 authpw v3trap /c/sys/ssnmp/snmpv3/access 11 name "v3trap" level authNoPriv nview "iso" /c/sys/ssnmp/snmpv3/group 11 uname v3trap gname v3trap /c/sys/ssnmp/snmpv3/notify 11 name v3trap tag v3trap /c/sys/ssnmp/snmpv3/taddr 11 name v3trap addr 47.81.25.66 taglist v3trap pname v3param /c/sys/ssnmp/snmpv3/tparam 11 name v3param uname v3trap level authNoPriv (Configure user named v3trap)
(Define access group to view SNMPv3 traps)
(Specify SNMPv3 traps to send)
(Set the authentication level)
For more information on using SNMP, see the HP 1:10Gb Ethernet BL-c Switch Command Reference. See the HP 1:10Gb Ethernet BL-c Switch 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. Authentication and authorization of remote administrators. See the RADIUS authentication and authorization section or the TACACS+ authentication section, both later in this chapter. Encryption of management information exchanged between the remote administrator and the switch. See the Secure Shell and Secure Copy section later in this chapter.
Setting allowable source IP address ranges
To limit access to the switch without having to configure filters for each switch port, you can set a source IP address (or range) that will be allowed to connect to the switch IP interface through Telnet, SSH, SNMP, or the switch browser-based interface (BBI). When an IP packet reaches the application switch, the source IP address is checked against the range of addresses defined by the management network and management mask. If the source IP address of the host or hosts is within this range, it is allowed to attempt to log in. Any packet addressed to a switch IP interface with a source IP address outside this range is discarded.

Accessing the switch 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. Supports secondary authentication server so that when the primary authentication server is unreachable, the switch can send client authentication requests to the secondary authentication server. Use the /cfg/sys/radius/cur command to show the currently active RADIUS authentication server. Supports user-configurable RADIUS server retry and time-out values:
Time-out value = 1-10 seconds Retries = 1-3
The switch will time out if it does not receive a response from the RADIUS server in one to three retries. The switch will also automatically retry connecting to the RADIUS server before it declares the server down. Supports user-configurable RADIUS application port. The default is 1645/User Datagram Protocol (UDP)-based on RFC 2138. Port 1812 is also supported. Allows network administrator to define privileges for one or more specific users to access the switch at the RADIUS user database. Allows the administrator to configure RADIUS backdoor and secure backdoor for Telnet, SSH, HTTP, and HTTPS access.
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 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. Operators can only effect temporary changes on the switch. These changes are lost when the switch is rebooted/reset. Operators have access to the switch management features used for daily switch operations. Because any changes an operator makes are undone by a reset of the switch, operators cannot severely impact switch operation, but do have access to the Maintenance menu. By default, the operator account is disabled and has no password.

Supplicant or ClientThe Supplicant is a device that requests network access and provides the required credentials (user name and password) to the Authenticator and the Authentication Server. AuthenticatorThe Authenticator enforces authentication and controls access to the network. The Authenticator grants network access based on the information provided by the Supplicant and the response from the Authentication Server. The Authenticator acts as an intermediary between the Supplicant and the Authentication Server: requesting identity information from the client, forwarding that information (encapsulated in RADIUS packets) to the Authentication Server for validation, relaying the servers responses to the client, and authorizing network access based on the results of the authentication exchange. The HP 1:10GbE switch acts as an Authenticator. Authentication ServerThe Authentication Server validates the credentials provided by the Supplicant to determine if the Authenticator should grant access to the network. The Authentication Server may be co-located with the Authenticator. The switch relies on external RADIUS servers for authentication.
Upon a successful authentication of the client by the server, the 802.1x-controlled port transitions from unauthorized to authorized state, and the client is allowed full access to services through the port. When the client sends an EAP-Logoff message to the authenticator, the port will transition from authorized to unauthorized state. 46
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). 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. Client sends an EAPOL-Start frame to the switch authenticator, which responds with an EAPRequest/Identity frame. The client confirms its identity by sending an EAP-Response/Identity frame to the switch authenticator, which forwards the frame encapsulated in a RADIUS packet to the server.

3. Apply and save the changes.
>> # apply >> # save (Apply the configuration) (Save the configuration)
Configuring Rapid 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 RSTP general parameters.
a. Click the Configure context button on the Toolbar. b. Open the MSTP/RSTP folder, and select General.
c. Select RSTP mode, and set the MSTP/RSTP state to ON.
RSTP and MSTP 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 32 spanning-tree instances that correspond to STP Groups 1-32. 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. MSTP allows frames assigned to different VLANs to follow separate paths, each path based on an independent Spanning-Tree instance. This approach provides multiple forwarding paths for data traffic, enabling load balancing, and reducing the number of Spanning-Tree instances required to support a large number of VLANs.

MSTP region

A group of interconnected bridges that share the same attributes is called an MST region. Each bridge within the region must share the following attributes:
Alphanumeric name Revision level VLAN-to-STG mapping scheme
MSTP provides rapid reconfiguration, scalability, and control due to the support of regions, and multiple Spanning-Tree instances support within each region.
Common Internal Spanning Tree
The Common Internal Spanning Tree (CIST) provides a common form of Spanning Tree Protocol, with one Spanning Tree instance that can be used throughout the MSTP region. CIST allows the switch to interoperate with legacy equipment, including devices that run IEEE 802.1d (STP). CIST allows the MSTP region to act as a virtual bridge to other bridges outside of the region, and provides a single Spanning-Tree instance to interact with them. CIST is the default spanning tree group. When VLANs are removed from STG 1-128, the VLANs automatically become members of the CIST. CIST port configuration includes Hello time, Edge port status (enable/disable), and Link Type. These parameters do not affect Spanning Tree Groups 1-128. They apply only when the CIST is used.

Quality of Service Overview Using ACL Filters Using DSCP Values to Provide QoS Using 802.1p Priorities to Provide QoS Queuing and Scheduling
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. Traffic for applications that are sensitive to timing out or cannot tolerate delay can be assigned to a high-priority queue. By assigning QoS levels to traffic flows on your network, you can ensure that network resources are allocated where they are needed most. QoS features allow you to prioritize network traffic, thereby providing better service for selected applications. The following figure shows the basic QoS model used by the HP 1:10GbE switch. Figure 11 QoS model

Ingress

Classify Packets

Meter Traffic

Perform Actions

Queue and Schedule

Egress

ACL Filter

ACL Meter

Drop/Pass/ Re-Mark

COS Queue
The switch uses the Differentiated Services (DiffServ) architecture to provide QoS functions. DiffServ is described in IETF RFCs 2474 and 2475. With DiffServ, you can establish policies to direct traffic. A policy is a traffic-controlling mechanism that monitors the characteristics of the traffic, (for example, its source, destination, and protocol) and performs a controlling action on the traffic when certain characteristics are matched. The switch can classify traffic by reading the IEEE 802.1p priority value, or by using filters to match specific criteria. When network traffic attributes match those specified in a traffic pattern, the policy instructs the switch to perform specified actions on each packet that passes through it. The packets are assigned to different Class of Service (COS) queues and scheduled for transmission.
Quality of Service The basic HP 1:10GbE switch QoS model works as follows:

Classify traffic:

Read 802.1p Priority Match ACL filter parameters

Meter traffic:

Define bandwidth and burst parameters Select actions to perform on in-profile and out-of-profile traffic

Perform actions:

Drop packets Pass packets Mark DSCP or 802.1p Priority Set COS queue (with or without re-marking)

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. Generally, you should configure the command on the switch IP interface closest to the client so that the DHCP server knows from which IP subnet the newly allocated IP address should come. The following figure shows a basic DHCP network example: Figure 16 DHCP relay agent configuration
Basic IP routing In HP 1:10GbE switch implementation, there is no need for primary or secondary servers. The client request is forwarded to the BOOTP servers configured on the switch. The use of two servers provides failover redundancy. However, no health checking is supported. Use the following commands to configure the switch as a DHCP relay agent:
>> >> >> >> >> >> # /cfg/l3/bootp Bootstrap Protocol Bootstrap Protocol Bootstrap Protocol Bootstrap Protocol Bootstrap Protocol Relay# Relay# Relay# Relay# Relay# addr addr2 on off cur (Set IP address of BOOTP server) (Set IP address of 2nd BOOTP server) (Globally turn BOOTP relay on) (Globally turn BOOTP relay off) (Display current configuration)
Additionally, DHCP Relay functionality can be assigned on a per interface basis. Use the following command to enable the Relay functionality:
>> # /cfg/l3/if <1-255>/relay ena
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). HP 1:10GbE switch software supports RIP version 1 (RIPv1) and RIP version 2 (RIPv2) for exchanging TCP/IP route information with other routers.

Distance vector protocol

RIP is known as a distance vector protocol. The vector is the network number and next hop, and the distance is the cost associated with the network number. RIP identifies network reachability based on cost, and cost is defined as hop count. One hop is considered to be the distance from one switch to the next which is typically 1. This cost or hop count is known as the metric. When a switch receives a routing update that contains a new or changed destination network entry, the switch adds 1 to the metric value indicated in the update and enters the network in the routing table. The IP address of the sender is used as the next hop.

Stability

RIP includes a number of other stability features that are common to many routing protocols. For example, RIP implements the split horizon and hold-down mechanisms to prevent incorrect routing information from being propagated. RIP prevents routing loops from continuing indefinitely by implementing a limit on the number of hops allowed in a path from the source to a destination. The maximum number of hops in a path is 15. The network destination network is considered unreachable if increasing the metric value by 1 causes the metric to be 16 (infinity). This limits the maximum diameter of a RIP network to less than 16 hops. RIP is often used in stub networks and in small autonomous systems that do not have many redundant paths.

Shortest Path First Tree

The routing devices use a link-state algorithm (Dijkstras algorithm) to calculate the shortest path to all known destinations, based on the cumulative cost required to reach the destination. The cost of an individual interface in OSPF is an indication of the overhead required to send packets across it. The cost is inversely proportional to the bandwidth of the interface. A lower cost indicates a higher bandwidth.
Internal versus external routing
To ensure effective processing of network traffic, every routing device on your network needs to know how to send a packet (directly or indirectly) to any other location/destination in your network. This is referred to as internal routing and can be done with static routes or using active internal routing protocols, such as OSPF, RIP, or RIPv2. It is also useful to tell routers outside your network (upstream providers or peers) about the routes you have access to in your network. Sharing of routing information between autonomous systems is known as external routing. Typically, an AS will have one or more border routers (peer routers that exchange routes with other OSPF networks) as well as an internal routing system enabling every router in that AS to reach every other router and destination within that AS. When a routing device advertises routes to boundary routers on other autonomous systems, it is effectively committing to carry data to the IP space represented in the route being advertised. For example, if the routing device advertises 192.204.4.0/24, it is declaring that if another router sends data destined for any address in the 192.204.4.0/24 range, it will carry that data to its destination.
OSPF implementation in HP 1:10GbE switch software
The HP 1:10GbE switch supports a single instance of OSPF and up to 4 K routes on the network. The following sections describe OSPF implementation in switch software:
Configurable Parameters Defining Areas Interface Cost Electing the Designated Router and Backup Summarizing Routes Default Routes Virtual Links Router ID Authentication

Configurable parameters

In HP 1:10GbE switch software, OSPF parameters can be configured through the Command Line Interface (CLI), Browser-Based Interface (BBI) for HP 1:10GbE switches, or through SNMP. For more information, see Accessing the Switch. The CLI supports the following parameters: interface output cost, interface priority, dead and hello intervals, retransmission interval, and interface transit delay. OSPF trapsTraps produce messages upon certain events or error conditions, such as missing a hello, failing a neighbor, or recalculating the SPF.
OSPF In addition to the above parameters, you can also specify the following:
Link-State Database sizeThe size of the external LSA database can be specified to help manage the memory resources on the switch. Shortest Path First (SPF) intervalTime interval between successive calculations of the shortest path tree using the Dijkstras algorithm. Stub area metricA stub area can be configured to send a numeric metric value such that all routes received via that stub area carry the configured metric to potentially influence routing decisions. Default routesDefault routes with weight metrics can be manually injected into transit areas. This helps establish a preferred route when multiple routing devices exist between two areas. It also helps route traffic to external networks.

Interface cost

The OSPF link-state algorithm (Dijkstras 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. You can manually enter the cost for the output route with the following command:
>> # /cfg/l3/ospf/if <OSPF interface number>/cost <cost value (1-65535)>
Electing the designated router and backup
In any area with more than two routing devices, a Designated Router (DR) is elected as the central contact for database exchanges among neighbors, and a Backup Designated Router (BDR) is elected in case the DR fails. DR and BDR elections are made through the hello process. The election can be influenced by assigning a priority value to the OSPF interfaces on the switch. The command is as follows:
>>#/cfg/l3/ospf/if <OSPF interface number>/prio <priority value (0-255)>
A priority value of 255 is the highest, and 1 is the lowest. A priority value of 0 specifies that the interface cannot be used as a DR or BDR. In case of a tie, the routing device with the lowest router ID wins.

Summarizing routes

Route summarization condenses routing information. Without summarization, each routing device in an OSPF network would retain a route to every subnet in the network. With summarization, routing devices can reduce some sets of routes to a single advertisement, reducing both the load on the routing device and the perceived complexity of the network. The importance of route summarization increases with network size. Summary routes can be defined for up to 16 IP address ranges using the following command:
>> # /cfg/l3/ospf/range <range number>/addr <IP address>/mask <mask>
where <range number> is a number 1 to 16, <IP address> is the base IP address for the range, and <mask> is the IP address mask for the range.

Default routes

When an OSPF routing device encounters traffic for a destination address it does not recognize, it forwards that traffic along the default route. Typically, the default route leads upstream toward the backbone until it reaches the intended area or an external router. Each switch acting as an ABR automatically inserts a default route into each attached area. In simple OSPF stub areas or NSSAs with only one ABR leading upstream (see Area 1 in the figure below), any traffic for IP address destinations outside the area is forwarded to the switchs IP interface, and then into the connected transit area (usually the backbone). Since this is automatic, no further configuration is required for such areas. Figure 19 Injecting default routes

If redundant routes via multiple routing processes (such as OSPF, RIP, BGP, or static routes) exist on your network, the switch defaults to the OSPF-derived route.
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 switch is listed here. Detailed instructions for each of the steps are covered in the following sections:
Configure IP interfaces. One IP interface is required for each desired network (range of IP addresses) being assigned to an OSPF area on the switch.
(Optional) Configure the router ID. The router ID is required only when configuring virtual links on the switch. Enable OSPF on the switch. Define the OSPF areas. Configure OSPF interface parameters. IP interfaces are used for attaching networks to the various areas. (Optional) Configure route summarization between OSPF areas. (Optional) Configure virtual links. (Optional) Configure host routes.
Example 1: Simple OSPF domain (CLI example)
In this example, two OSPF areas are definedone area is the backbone and the other is a stub area. A stub area does not allow advertisements of external routes, thus reducing the size of the database. Instead, a default summary route of IP address 0.0.0.0 is automatically inserted into the stub area. Any traffic for IP address destinations outside the stub area will be forwarded to the stub areas IP interface, and then into the backbone. Figure 21 Simple OSPF domain
OSPF Follow this procedure to configure OSPF support as shown in the figure. 1. Configure IP interfaces on each network that will be attached to OSPF areas. 2. In this example, two IP interfaces are needed: one for the backbone network on 10.10.7.0/24 and one for the stub area network on 10.10.12.0/24.
>> >> >> >> >> >> >> >> # /cfg/l3/if IP Interface IP Interface IP Interface IP Interface IP Interface IP Interface IP Interface # # # # # # # (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 stub area network) mask 255.255.255.0(Set IP mask on stub area network) enable(Enable IP interface 2)

14. Apply and save the configuration changes.
Other Virtual Link Options
You can use redundant paths by configuring multiple virtual links. Only the endpoints of the virtual link are configured. The virtual link path may traverse multiple routers in an area as long as there is a routable path between the endpoints.
Example 3: Summarizing routes
By default, ABRs advertise all the network addresses from one area into another area. Route summarization can be used for consolidating advertised addresses and reducing the perceived complexity of the network. If the network IP addresses in an area are assigned to a contiguous subnet range, you can configure the ABR to advertise a single summary route that includes all the individual IP addresses within the area. The following example shows one summary route from area 1 (stub area) injected into area 0 (the backbone). The summary route consists of all IP addresses from 36.128.192.0 through 36.128.254.255 except for the routes in the range 36.128.200.0 through 36.128.200.255.
OSPF Figure 23 Summarizing routes
NOTE: You can specify a range of addresses to prevent advertising by using the hide option. In this example, routes in the range 36.128.200.0 through 36.128.200.255 are kept private. Follow this procedure to configure OSPF support on Switch A and Switch B, as shown in the figure. 1. Configure IP interfaces for each network which will be attached to OSPF areas.
>> >> >> >> >> >> >> >> # /cfg/l3/if IP Interface IP Interface IP Interface IP Interface IP Interface IP Interface IP Interface 1(Select menu for IP interface 1) 1 # addr 10.10.7.1(Set IP address on backbone network) 1 # mask 255.255.255.0(Set IP mask on backbone network) 1 # ena(Enable IP interface 1) 1 #./if 2(Select menu for IP interface 2) 2 # addr 36.128.192.1(Set IP address on stub area network) 2 # mask 255.255.192.0(Set IP mask on stub area network) 2 # ena(Enable IP interface 2)

2. Enable OSPF.

>> IP Interface 2 # /cfg/l3/ospf/on

3. Define the backbone.

>> >> >> >> Open OSPF OSPF OSPF 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)

Configure RMON History (CLI example)
1. Enable RMON on each port where you wish to collect RMON History.
>> >> >> >> /cfg/port 23/rmon Port 23# ena Port 23 RMON# apply Port 23 RMON# save (Select Port 23 RMON) (Enable RMON) (Make your changes active) (Save for restore after reboot)
2. Configure the RMON History parameters.
>> >> >> >> >> /cfg/rmon/hist 1 (Select RMON History 1) RMON History 1# ifoid 1.3.6.1.2.1.2.2.1.1.23 RMON History 1# rbnum 30 RMON History 1# intrval 120 RMON History 1# owner Owner_History_1
>> RMON History 1# apply >> RMON History 1# save (Make your changes active) (Save for restore after reboot)
This configuration creates an RMON History group to monitor port 23. It takes a data sample every two minutes, and places the data into one of the 30 requested buckets. After 30 samples are gathered, the new samples overwrite the previous samples, beginning with the first bucket. Use SNMP to view the data.
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.
Remote monitoring 2. Configure RMON History Group parameters.
3. Click Submit. 4. Apply, verify, and save the configuration.

RMON group 3alarms

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. The Alarm group can be used to track rising or falling values for a MIB object. The object must be a counter, gauge, integer, or time interval. Use the /cfg/rmon/alarm x/revtidx or /fevtidx to correlate an alarm index to an event index. 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. These MIB Object Identifiers (OIDs) correlate to the ones tracked by the History group. An example of an ICMP stat is as follows: 1.3.6.1.2.1.5.1.0 mgmt.icmp.icmpInMsgs The last digit (x) represents the interface on which to monitor, which corresponds to the interface number, or port number, as follows:
1-256 = IF 1-= port 1 157

258 = port = port 24

This value represents the alarms MIB OID, as a string. Note that for non-tables, you must supply a.0 to specify end node.

Task 1: Configure Switch A
/cfg/l2/vlan 10 >> VLAN 10# ena >> VLAN 10# add 20 >> VLAN 10#. >> Layer 2# vlan 20 >> VLAN 20# ena >> VLAN 20# add 21 (Select VLAN 10) (Enable VLAN 10) (Add port 20 to VLAN 10) (Select VLAN 20) (Enable VLAN 20) (Add port 21 to VLAN 20)
High availability 2. Configure client and server interfaces.
/cfg/l3/if 1 >> IP Interface 1# >> IP Interface 1# >> IP Interface 1# >> IP Interface 1# >> Layer 3# if 2 >> IP Interface 2# >> IP Interface 1# >> IP Interface 2# >> IP Interface 2# >> Layer 3# if 3 >> IP Interface 3# >> IP Interface 3# >> IP Interface 3# >> IP Interface 2# >> Layer 3# if 4 >> IP Interface 4# >> IP Interface 4# >> IP Interface 4# addr 192.168.1.100 vlan 10 ena. addr 192.168.2.101 vlan 20 ena. addr 10.0.1.100 mask 255.255.255.0 ena. addr 10.0.2.101 mask 255.255.255.0 ena (Select (Define (Assign (Enable (Select (Define (Assign (Enable (Select (Define (Define (Enable interface 1) IP address for interface 1) VLAN 10 to interface 1) interface 1) interface 2) IP address for interface 2) VLAN 20 to interface 2) interface 2) interface 3) IP address for interface 3) subnet mask for interface 3) interface 3)
(Select interface 4) (Define IP address for interface 4) (Define subnet mask for interface 4) (Enable interface 4)
3. Configure the default gateways. Each default gateway points to one of the Layer 2 routers.
/cfg/l3/gw 1 >> Default gateway >> Default gateway >> Default gateway >> Layer 3# gw 2 >> Default gateway >> Default gateway (Select default gateway 1) 1# addr 192.168.1.1 (Point gateway to the first L2 router) 1# ena (Enable the default gateway) 1#. (Select default gateway 2) 1# addr 192.168.2.1 (Point gateway to the second router) 1# ena (Enable the default gateway)
4. Turn on VRRP and configure two Virtual Interface Routers.
/cfg/l3/vrrp/on (Turn VRRP on) >> Virtual Router Redundancy Protocol# vr 1 (Select virtual router >> VRRP Virtual Router 1# vrid 1 (Set VRID to 1) >> VRRP Virtual Router 1# if 1 (Set interface 1) >> VRRP Virtual Router 1# addr 192.168.1.200 (Define IP address) >> VRRP Virtual Router 1# ena (Enable virtual router >> VRRP Virtual Router 1#. (Enable virtual router >> Virtual Router Redundancy Protocol# vr 2 (Select virtual router >> VRRP Virtual Router 2# vrid 2 (Set VRID to 2) >> VRRP Virtual Router 2# if 2 (Set interface 2) >> VRRP Virtual Router 2# addr 192.168.2.200 (Define IP address) >> VRRP Virtual Router 2# ena (Enable virtual router 1)