An Intel® product, when used in accordance with its associated documentation, is "Year 2000 Capable" when, upon
installation, it accurately stores, displays, processes, provides, and/or receives date data from, into, and between 1999
and 2000, and the twentieth and twenty-first centuries, including leap year calculations, provided that all other
technology used in combination with said product properly exchanges date data with it. Intel makes no representation
about individual components within the product should they be used independently from the product as a whole.
Intel Corporation assumes no responsibility for errors or omissions in this manual. Nor does Intel make any commitment to update the
information contained herein.
* Other product and corporate names may be trademarks of other companies and are used only for explanation and
to the owners’ benefit, without intent to infringe.
First Edition May 2000 A18558-001
470T-inside pages.p653/30/00, 10:40 AM1
CONTENTS
Intel® NetStructure
Contents
470T and 470F Switches User Guide
1.0 Setting up the Intel® NetStructure™
470T/F Switches1
Limitation de garantie du matériel (Europe) ...................... 117
Garanzia limitata sull’hardware (valida solo in Europa) ... 118
Beschränkte Hardwaregarantie (Nur für Europa) .............. 119
Garantía limitada de hardware (sólo para Europa) ............ 120
Index121
Intel Customer Support Last Page
iv
470-UG TOC.p653/31/00, 12:20 PM4
Setting up the Intel
®
1
NetStructure™
470T
and 470F Switches
Overview
This guide provides information on configuring and managing the Intel
NetStructure 470T and 470F Switches; it is organized into five chapters:
• Chapter 1 - Identifying and connecting the switch hardware.
• Chapter 2 - Using the switch in a LAN and advanced features such as
link aggregation and VLANs
• Chapter 3 - Using Intel Device View
• Chapter 4 - Using Web Device Manager
• Chapter 5 - Using Local Management
Management
Through the switch’s built-in management you can configure the device and
monitor network health. There are several methods for managing this
switch; you can use one method or any combination.
• SNMP management applications like Intel Device View, LANDesk®
Network Manager, or HP OpenView* are tailored for Intel products and
show a graphical representation of the device.
®
470T Ch1.p653/30/00, 5:49 PM1
• Onboard management allows control over the device without using an
SNMP application. The Web Device Manager provides a graphical
interface while Local Management is a menu-driven interface.
• Other SNMP-compliant applications can manage the 470 switches if
you compile the switch’s MIB files into that application.
1
CHAPTER 1
Status
LED
Intel® NetStructure
470T and 470F Switches User Guide
Switch Features
These are the major features of the 470 switches.
8-port 470F Switch (Product Code ES470F)
Link/Activity LEDs
Serial
Port
6+2-port 470T Switch (Product Code ES470T)
Status
LED
Speed LEDs
(top row)
Link/Activity LEDs
(bottom row)
Serial
Port
Back of 470 Switch
• 100/1000 Base-T auto-negotiates speed, duplex, and flow control—100Mbps or
1000Mbps
per port
• 470F supports 1000SX, 1000LX, and 1000LH GBICs
• Half- and full-duplex flow control
• Port settings can be configured manually through management
• Access menu-driven Local Management through the serial port or a Telnet session
• Access the graphical Web Device Manager through a Web browser
1000 Base-SX
Port
1000 Base-T
Port
MAC
Address
GBIC Port
AC Power
Plug
2
470T Ch1.p653/30/00, 5:49 PM2
CHAPTER 1
Setting Up the Intel
®
NetStructure
470T and 470F Switches
LEDs
The LEDs to the left of the ports indicate port status, individual port speed,
and port activity.
470F
Status
Link/Activity
470 Setup
NOTE
After the switch is first powered
on, the Status LED blinks green
once before the diagnostic mode
starts.
Status
470T
Speed
Link/Activity
LEDColorMeaning
StatusBlinking greenSwitch is performing diagnostics and booting.
(This lasts for 20–30 seconds.)
Solid greenDiagnostics have passed, the switch is ready.
Blinking greenDiagnostics have failed. (After the initial 20–
30 seconds, the LED will continue blinking if
diagnostics fail.)
Link/ActivitySolid greenDevice linked.
Blinking greenReceiving activity on that port.
OffNo link detected.
SpeedSolid greenDevice connected at 1000Mbps.
(470T only)OffDevice connected at 100Mbps.
470T Ch1.p653/30/00, 5:49 PM3
3
CHAPTER 1
Intel® NetStructure
470T and 470F Switches User Guide
Connection Guidelines
General
• The 470T switch is capable of auto-negotiating port duplex. It can
operate at half- or full-duplex at 100Mbps, and full duplex at
1000Mbps. The switch matches the highest possible speed of an
attached device.
• The 470F operates at full-duplex and at 1000Mbps.
Cabling
NOTE
If you do not use certified
Category 5 cables to connect
1000Mbps devices to the switch
you may get errors.
• Use Category 5 unshielded twisted-pair (CAT 5 UTP) cable when
connecting 1000Mbps or 100Mbps devices to the switch.
• Limit the cable length between devices to 100 meters (330 feet) for
copper wire.
• Use a straight-through cable to connect the switch to a server or
workstation.
• To connect to another switch or hub, use a crossover cable.
Straight-through vs. Crossover Cables
Switch ports are wired MDI-X, so use a straight-through cable to connect to
a workstation or server (network adapter cards are wired MDI). To connect
to another MDI-X port, use a crossover cable. Following pin arrangements
are for the switch’s Ethernet port and the typical RJ-45 connector. The
wiring diagrams illustrate how to wire a straight-through and crossover
cable for 100Mbps and 1000Mbps devices.
Straight-through UTP cable (100Mbps)
Switch (MDI-X) Adapter (MDI)
4
470T Ch1.p653/30/00, 5:49 PM4
CHAPTER 1
Setting Up the Intel
®
NetStructure
470T and 470F Switches
Crossover UTP cable (100Mbps)
Switch (MDI-X) Hub (MDI-X)
Straight-through UTP cable (1000Mbps)
Switch (MDI) Switch (MDI)
470 Setup
470T Ch1.p653/30/00, 5:49 PM5
5
CHAPTER 1
Intel® NetStructure
470T and 470F Switches User Guide
6
470T Ch1.p653/30/00, 5:49 PM6
Using the Intel
®
2
NetStructure™
470T
and 470F Switches
Overview
Chapter 2 is designed to provide an overview for using the Intel
NetStructure™ 470T and 470F Switches within a network. This chapter
covers switching features like flow control and spanning tree, and includes a
discussion of the more advanced features such as link aggregation and the
types of VLANs available on the switch.
If you are already familiar with switching technology you can skip ahead to
a particular section within the chapter. Here is a basic overview of the
chapter and the pages where you can find a particular topic:
• Sample Configuration page 8
• Flow Control page 9
• Spanning Tree Protocol page 9
• Tagged Frames page 10
• Priority Packet page 10
®
470T Ch2.p653/30/00, 5:54 PM7
• Link Aggregation page 11
• Virtual LANs page 12
• GVRP page 15
• IGMP Snooping page 16
7
CHAPTER 2
100Mbps
1000Mbps
Link Aggregation
group
Intel® NetStructure
470T and 470F Switches User Guide
Sample Configuration
The following example illustrates how the 470T and 470F switches can be
used in a network.
In this example, the 480T functions as the backbone of the network,
providing routing capability. The 470T and 470F switches provide gigabit
connectivity from the 480T to the 460T desktop switches via the 460s’
gigabit uplinks.
8
470T Ch2.p653/30/00, 5:54 PM8
CHAPTER 2
Using the Intel
®
NetStructure™
470T and 470F Switches
Flow Control
During times of heavy network activity, the switch’s port buffers can
receive too much traffic and fill up faster than the switch can send the
information. In cases like this, the switch tells the transmitting device to
wait so the information in the buffer can be sent. This traffic control
mechanism is called flow control.
The method of flow control depends on whether the port is set to full- or
half-duplex. If a port is operating at half-duplex, the switch sends a collision
(also called backpressure) which causes the transmitting device to wait. If
the port operates at full-duplex, the switch sends out an IEEE 802.3x
PAUSE frame. You can enable or disable flow control for each port on the
470 switches.
Spanning Tree Protocol
Spanning Tree Protocol, as referenced in the IEEE 802.1D specification, is a
protocol designed to prevent any loops within the network topology. A loop
can occur if there is more than one path for information to travel between
devices. The Spanning Tree Protocol works by determining the “cost” of a
connection. For example, if two devices are connected by two links,
Spanning Tree uses the connection with the lowest cost and blocks the
second connection.
Using the 470
470T Ch2.p653/30/00, 5:54 PM9
Spanning Tree prevents loops by allowing only one active path between any
two network devices at a time. However, you can also use this protocol to
establish redundant links between devices which can take over in the event
the primary link fails.
Backup Path from Client A to Server B:
Switch A –> Switch B –> Switch C
Primary Path from Client A to Server B: Switch A –> Switch C
In this example, Client A can communicate with Server B over two different
paths. The primary path is Path 1 because the cost of the connection between
switches A and C is lower than the cost between switches A, B and C. If the
primary path fails, then traffic is automatically sent over the backup path.
9
CHAPTER 2
Intel® NetStructure
470T and 470F Switches User Guide
Tagged Frames
The 802.1D (1998 Edition) and 802.1Q specifications published by the
IEEE (Institute of Electrical and Electronic Engineers) extended Ethernet
functionality to add tag information to Ethernet frames and propagate these
tagged frames between bridges. The tag can carry priority information,
VLAN information, or both and allows bridges to intelligently direct traffic
across the network.
Some devices don’t recognize the tagged Ethernet frames. These devices see
a frame that is too big, and then discard it. When operating 802.1Q (tagbased) VLANs, there is a way to configure the switch to work with these
untagged devices. For more information see “How to configure 802.1Q
VLANs” in Chapter 5.
Priority Packet
The IEEE 802.1D (1998 Edition) specification incorporates IEEE 802.1p
and defines information in the frame tag to indicate a priority level. When
these tagged packets are sent out on the network, the higher priority packets
are transferred first. Priority packet tagging (also known as Traffic Class
Expediting) is usually set on the LAN adapter in a PC or switch and works
with other elements of the network (switches, routers) to deliver packets
based on priority. The priority level can range from 0 (low) to 7 (high).
10
470T Ch2.p653/30/00, 5:54 PM10
The 470 switches can read the priority tags and forward traffic on a per port
basis. The switches have two priority queues per port and queue the packet
based on its priority level. For example, when a packet comes into a switch
with a high priority tag, the switch inserts the packet in its high-priority
queue.
Even though there are eight priority levels, the 470 switches can only put a
packet into one of the two queues. The switch maps levels 0-3 to the low
queue and levels 4-7 to the high queue. If a packet is untagged, the switch
can be set to use either the high or low queue for that port. The
470 switches preserve the priority level of the packet.
CHAPTER 2
Using the Intel
®
NetStructure™
470T and 470F Switches
Link Aggregation
Link aggregation allows you to combine from two to four (adjacent) ports
so that they function as a single high-speed link. For example, link
aggregation is useful when making connections between switches or
connecting servers to the switch.
Link aggregation, sometimes known as port trunking, is used to increase the
bandwidth to some devices. Link aggregation can also provide a redundant
link for fault tolerance. If one link in the aggregation fails, the switch
balances the traffic among the remaining links.
To aggregate ports, you must link an “anchor” port with an adjacent port.
The 470 switches support up to four link aggregation groups (anchor ports
1,3, 5, or 7). All aggregated ports must be the same speed.
Using the 470
Guidelines
• The switch treats aggregated links as a single port. This includes
spanning tree and VLAN configurations.
• For the 470F: Anchor ports 1, 3, and 5 can each have up to four
aggregated ports; anchor port 7 can have two.
• For the 470T: Anchor ports 1 and 3 can each have up to four aggregated
ports; anchor ports 5 and 7 can each have two.
• All ports share the same settings as the anchor port. You can change
anchor port settings, but you cannot configure other ports in the link.
• When a port is configured as a member of an aggregated link, it adopts
the configuration of the anchor port. When a port is no longer a member
of an aggregated link, the configuration is reset to the default settings
(auto-negotiate speed/duplex, flow control enabled).
• If a port is part of an aggregated link, it cannot be configured as the
target port for a port mirror. However, a port in an aggregated link can
serve as the source port for a port mirror.
• When connecting to another switch, connect anchor port to anchor port,
and member port to member port.
11
470T Ch2.p653/30/00, 5:54 PM11
CHAPTER 2
Intel® NetStructure
470T and 470F Switches User Guide
Virtual LANs
A Virtual LAN is a logical network grouping that allows you to isolate
network traffic so members of the VLAN receive traffic only from other
members. Creating a VLAN is the virtual equivalent of physically moving a
group of devices to a separate switch (creating a Layer 2 broadcast domain).
The advantage of VLANs is that you can reduce broadcast traffic for the
entire switch, and increase security, without changing the wiring of your
network.
The 470 switches support two types of VLANs:
• Port-based
• Tag-based (IEEE 802.1Q)
Port-based VLANs
This is the simplest and most common form of VLAN. In a port-based
VLAN, the system administrator assigns the switch’s ports to a specific
VLAN. For example, the system administrator can designate ports 1, 2, and
3 as part of the engineering VLAN and ports 5, 6, 7, and 8 as part of the
marketing VLAN. The advantage of port-based VLANs is that they are easy
to configure and all changes happen at the switch so they are transparent to
the users. The 470 switches support a maximum of four port-based VLANs.
A port can belong to only one VLAN at a time.
12
470T Ch2.p653/30/00, 5:55 PM12
If a user changes location, the system administrator reassigns the port to the
new VLAN. Another advantage is if a switch (or hub) is connected to a port
that is part of a VLAN, all devices connected to the switch are also part of
the VLAN. You cannot exclude an individual device on that switch from
becoming part of the VLAN.
CHAPTER 2
Using the Intel
®
NetStructure™
470T and 470F Switches
IEEE 802.1Q (tag)-based VLANs
The other type of VLAN supported by the 470 switches is based on the
IEEE 802.1Q specification. The specification provides a uniform way for
creating VLANs within a network and allows the creation of a VLAN that
can also span across the network. Until the release of the IEEE 802.1Q,
VLAN implementation had been vendor-specific, so it was not possible to
create a VLAN across devices from different vendors.
The 802.1Q VLAN works by using a tag added to the Ethernet frames. The
tag contains a VLAN Identifier (VID) that identifies the frame as belonging
to a specific VLAN. These tags allow switches that support the 802.1Q
specification to segregate traffic between devices and communicate a
device’s VLAN association across switches.
There are multiple advantages to implementing 802.1Q VLANs. First, it
helps to contain broadcast and multicast traffic across the switch thus
improving performance. Second, ports can belong to more than one VLAN.
Third, VLANs can span multiple switches that support the 802.1Q
specification. Finally, it can provide security and improve performance by
logically isolating users and grouping them together.
Using the 470
470T Ch2.p653/30/00, 5:55 PM13
A logical grouping may be mapped to a workgroup. For example, you can
create a VLAN that groups all the users from the engineering department. A
benefit of this logical grouping is that it improves performance by reducing
traffic that belongs to a different logical group (i.e. marketing), improves
security (engineering can’t see marketing), and eases moves since the user
doesn’t have to be physically located in the same group to participate in the
VLAN.
13
CHAPTER 2
Intel® NetStructure
470T and 470F Switches User Guide
Spanning Tree and VLANs
The 470 switches support the Spanning Tree Protocol across the entire
switch, not per VLAN. If a loop occurs in a VLAN the port is disabled and
all VLAN traffic over that port is blocked.
A good example of this is seen below. Both Switch 1 and Switch 2 have two
port-based VLANs configured. Crossover cables connect the ENG_VLAN
on Switch 1 to ENG_VLAN on and Switch 2. Crossover cables also connect
the MRKT_VLAN on Switch 1 to the MRKT_VLAN on Switch 2. When
Spanning Tree is enabled, the redundant link between the MRKT_VLANs is
blocked and those VLANs can no longer communicate.
14
470T Ch2.p653/30/00, 5:55 PM14
CHAPTER 2
Using the Intel
®
NetStructure™
470T and 470F Switches
GARP VLAN Registration Protocol (GVRP)
Since IEEE 802.1Q VLANs can span across the network, it poses a
challenge for network administrators to manage changes to the VLAN. The
GARP VLAN Registration Protocol (GVRP) provides a dynamic
mechanism for switches to share topology information and manage changes
with other switches. This prevents the network administrator from manually
propagating VLAN configuration information across switches.
GARP (Generic Attribute Registration Protocol) is defined by the IEEE
802.1D (1998 Edition) specification and is the mechanism used by switches
and end nodes (servers, PCs, etc.) to propagate configuration across the
network domain. GVRP uses GARP as a foundation to propagate VLAN
configuration to other switches. Devices that support GVRP transmit their
updates to a known multicast address that all GVRP-capable devices
monitor for information updates.
Sending GVRP messages between switches accomplishes the following
tasks:
• Dynamically adds or removes a port from participating in a VLAN
• Sends updates about the switch’s own VLAN configuration to
neighboring GVRP-capable devices.
• Integrates dynamic and static VLANs configurations within the same
switch. Static VLAN configurations are created by the user on the
switch for devices that don’t support GVRP.
It’s important to remember that dynamically created VLANs are not saved
in the switch’s memory. If the device that is sending out the GVRP updates
is removed, then the dynamic VLAN is removed.
When the switch is running 802.1Q VLANs Spanning Tree Protocol is
enabled for GVRP to work properly.
Using the 470
470T Ch2.p653/30/00, 5:55 PM15
15
CHAPTER 2
Intel® NetStructure
470T and 470F Switches User Guide
Internet Group Multicast Protocol (IGMP)
Under normal circumstances, multicast traffic is broadcast by the switch to
all ports. For multicast traffic based on TCP/IP using the IGMP protocol,
the switch can optimize the broadcasting of multicast traffic by forwarding
multicast traffic only to ports that require it.
IGMP Snooping is a feature that allows the switch to forward multicast
traffic intelligently. The switch “snoops” the IGMP query and report
messages and forwards traffic only to the ports that request the multicast
traffic. This prevents the switch from broadcasting the traffic to all ports
and possibly affecting network performance.
IGMP Snooping requires a router that learns about the presence of
multicast groups on its subnets and keeps track of group membership.
16
470T Ch2.p653/30/00, 5:55 PM16
Using Intel® Device
3
View 2.1
Overview
Intel® Device View allows you to manage Intel NetStructure™ 470T and
470F switches and other supported Intel networking devices on your
network.
Intel Device View provides these features:
• The ability to configure new network devices
• Graphical device manager for Intel switches, hubs, and routers
• Autodiscovery, which finds supported Intel devices on the network
• The Device Tree, which shows all the supported devices detected
on your network
• Remote Network Monitoring (RMON)
• Web or Windows* platform
• Plug-in to HP OpenView*, IBM Tivoli NetView*, and Intel
LANDesk
®
Network Manager
470T Ch3.p653/30/00, 9:04 AM17
• Other useful tools such as a TFTP server
17
CHAPTER 3
Intel® NetStructure™
470T and 470F Switches User Guide
Installing Intel Device View
Before you install Intel Device View, make sure your PC meets the system
requirements in the Intel
®
Device View User Guide, which is included on
the Intel Device View CD-ROM.
To install Intel Device View
1 Insert the Intel Device View CD-ROM in your computer’s CD-ROM
drive. The Intel Device View installation screen appears. If it doesn’t
appear, run autoplay.exe from the CD-ROM.
18
470T Ch3.p653/30/00, 9:04 AM18
2 Choose the version of Intel Device View you want to install.
• To install Intel Device View for use on this PC only, click Install
for Windows.
• To install Intel Device View on a Web server, click Install for
Web. You can access the Device View server from any PC on your
network with Internet Explorer* 4.0x or later.
• To install Intel network device support for HP OpenView, IBM
Tivoli NetView, or Intel LANDesk Network Manager, click Installas Plug-in. This option is not available if you don’t have
OpenView, LANDesk Network Manager, or NetView installed on
the PC.
3 Follow the on-screen instructions in the installation program.
CHAPTER 3
NOTE
These are the requirements if you
want to use the Web version of
Device View :
Web browser
Internet Explorer 4.0 or later
Intel Device View 2.1
Starting Intel Device View
Install either the Windows or Web version of Intel Device View.
Windows version
From your desktop, click Start and then point to Programs > Intel Device
View > Intel Device View - Windows. Intel Device View’s main screen
appears.
Web version
•From your desktop, click Start and then point to Programs > Intel
Device View > Intel Device View - Web. Intel Device View’s main
screen appears.
•To view Intel Device View from another PC on your network, type the
following URL. In the example shown below, the URL is entered into
the Address field for Internet Explorer.
http://servername/devview/main.htm
where servername is the IP address or name of the server where Intel
Device View is installed.
Intel Device View’s main screen appears.
Device View 2.1
Web Server
IIS 2.0 or later
Peer Web Services*
Netscape Enterprise* Web
Server 3.01 or later
470T Ch3.p653/30/00, 9:04 AM19
19
CHAPTER 3
Intel® NetStructure™
470T and 470F Switches User Guide
Installing a New Device
After you’ve installed a new switch on your network, you can use Intel
Device View’s Device Install Wizard to configure it for management.
To install and configure a new switch for
management
1 Start Intel Device View. The Device Install Wizard appears. If it
doesn’t appear, click Install from the Device menu or double-click the
appropriate MAC address in the Device Tree under Unconfigured
Devices. (The MAC address is located on the rear of the switch.)
2 On the Device Install Wizard - Start screen, click Next.
3 On the Device Install Wizard - MAC Address screen, click the MAC
address of the new switch and then click Next.
20
470T Ch3.p653/30/00, 9:04 AM20
4 Follow the instructions in the wizard to assign an IP address and a name
to the switch.
CHAPTER 3
Intel Device View 2.1
Using the Device Tree
After you start Intel Device View, the Device Discovery service begins
searching for supported Intel network devices on your network. As it
discovers devices, the Device Discovery service adds an icon for each
device to the Device Tree on the left side of the screen.
Different states of the 470 switches are represented by unique icons in the
Device Tree.
Device Tree icons
Device Tree root
Device View 2.1
Subnet
Intel Switch (if non-responding the icon is red)
Unconfigured Intel Switch
Group of Intel Switches
Intel Router
Intel Switch (Layer 3 capable)
Intel Stackable Hub
The Device Tree works much like Windows Explorer. To expand the root or
a subnet, click the (+) next to the icon. To collapse the view, click the (-)
next to the icon. Double-click a device icon to view the device image.
21
470T Ch3.p653/30/00, 9:04 AM21
CHAPTER 3
Intel® NetStructure™
470T and 470F Switches User Guide
To add a device to the Device Tree
Use this procedure if the device does not automatically appear after
installation.
1 Right-click anywhere on the Device Tree.
2 On the menu that appears, click Add Device.
3 In the Add Device dialog box, type the IP address of the switch you
want to add.
4 Fill in the other fields, as appropriate.
5 Click OK.
The new switch’s icon appears in the Device Tree.
To refresh the Device Tree
1 Right-click anywhere on the Device Tree.
2 On the menu that appears, click Refresh.
Refreshing the Device Tree updates it to show any newly discovered
devices and changes in device status.
To delete a device from the Device Tree
1 Right-click the device you want to remove from the Device Tree.
2 On the menu that appears, click Delete.
Deleting a device from the Device Tree does not affect the actual device.
22
470T Ch3.p653/30/00, 9:04 AM22
To find a device in the Device Tree
1 On the Device Tree, right-click anywhere.
2 On the menu that appears, click Find.
3 In the Find Device dialog box, type the IP address of the device you
want to find in the tree.
4 Click OK.
The device’s icon is highlighted in the Device Tree.
Losing contact with a device
If Intel Device View loses contact with a switch, it replaces the switch icon
with the non-responding switch icon, which is red.
CHAPTER 3
Intel Device View 2.1
If the non-responding switch icon appears, you cannot manage the device in
Intel Device View. If you’re unable to ping the device or start a Telnet
session, try accessing the switch’s Local Management.
Managing a Switch
To manage a 470T or 470F switch, double-click the switch icon in the
Device Tree. In the example shown below, the switch has been assigned an
IP address of 124.123.122.3.
The 470 Web Device Manager appears in the Intel Device View window.
Use the Web Device Manager as described in Chapter 4.
Device View 2.1
470T Ch3.p653/30/00, 9:04 AM23
For complete information on using Intel Device View, refer to the
program’s online help or see the User Guide on the Intel Device View
installation CD-ROM.
23
CHAPTER 3
Intel® NetStructure™
470T and 470F Switches User Guide
Viewing RMON information
The remote monitoring (RMON) specification extends SNMP functionality
to look at traffic patterns on the network instead of merely looking at the
traffic for an individual device. The following RMON groups are supported:
• Group 1 (Statistics): Monitors utilization and error statistics for each
network segment (100Mbps or 1000Mbps).
• Group 2 (History): Records periodic statistical samples from variables
available in the statistics group.
• Group 3 (Alarms): Allows you to set a sampling interval and alarm
thresholds for statistics. When a threshold is passed, the switch creates
an event. For example, you might set an alarm if switch utilization
exceeds 30%.
• Group 9 (Events): Provides notification and tells the switch what to do
when an event occurs on the network. Events can send a trap to a
receiving station or place an entry in the log table, or both. For example,
when the switch experiences an RMON Event, it sends out an alarm.
The switch also keeps a log that shows a list of the RMON Events and
RMON Alarms that have occurred on the switch.
24
To view RMON statistics
1 In the Device Tree, right-click the switch’s icon, then point to RMON.
2 Click the RMON option you want to view:
You can also access RMON features by using LANDesk Network Manager,
or an SNMP application that supports RMON such as OpenView. For more
information about using RMON to monitor the switch, refer to the Intel
Device View Help.
470T Ch3.p653/30/00, 9:04 AM24
Loading...
+ 105 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.