Intel Corporation assumes no responsibility for errors or omissions in this manual. Nor does Intel make any commitment to update the
information contained herein. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and
other countries.
* 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.
Second Edition June 2001 A18558-002
CONTENTS
Intel® NetStructure
Contents
470T and 470F Switches User Guide
1 Setting up the Intel® NetStructure™ 470T and
470F Switches
Save Settings...................................................................117
470T and 470F Switches User Guide
Appendix A: Technical Information119
Index139
Intel Customer Support146
iv
Setting up the Intel
®
NetStructure™ 470T
1
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; 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. You can use any combination of the following
methods to manage the switch.
• SNMP management applications like Intel Device View, LANDesk
Network Manager, HP OpenView*, and IBM Tivoli NetView* are
tailored for Intel products and show a graphical representation of the
device.
®
®
• Onboard management allows control over the switch without using an
SNMP application. The Web Device Manager provides a graphical
interface while Local Management is a menu-driven interf ace.
• Other SNMP-compliant applications can manage the 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-duplex 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
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 activity.
Status
470F
Link/Activity
470 Switch Setup
NOTE
After the switch is turned on, the
Status LED blinks green once
before the diagnostic mode starts.
Status
470T
Speed
Link/Activity
LEDStateMeaning
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 continues blinking.)
Link/ActivitySolid greenDevice linked.
Blinking greenReceiving activity on that port.
OffNo link detected.
SpeedSolid greenDevice connected at 1000Mbps.
(470T only)OffDevice connected at 100Mbps.
3
CHAPTER 1
Intel® NetStructure™ 470T and 470F Switches User Guide
Connection Guidelines
General
• The 470T switch is can auto-negotiate port duplex. It can operate at
half-duplex or full-duplex at 100Mbps, and full-duplex at 1000Mbps.
The switch matches the highest possible speed (up to 1000Mbps) of an
attached device.
• The 470F operates at full-duplex and at 1000Mbps.
Cabling
NOTE
Use certified Category 5 cables to
connect 1000Mbps devices to the
switch.
• Use Category 5 unshielded, twisted-pair (CAT 5 UTP) cable to connect
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. The 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
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 Switch Setup
5
CHAPTER 1
Intel® NetStructure™ 470T and 470F Switches User Guide
6
Using the Intel
®
NetStructure™ 470T
2
and 470F Switches
Overview
Chapter 2 provides 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 familiar with switching technology you can skip ahead to a
particular section within the chapter. The following list shows where you
can find particular topics:
• Sample Configuration page 8
• Flow Control page 9
• Broadcast Storm Control page 10
• Spanning T ree Protocol page 11
• Tagged Frames page 12
• Priority T ag ging page 12
• Link Aggregation page 13
• Virtual LANs page 14
• GVRP page 18
• Internet Group Management Protocol (IGMP) Snooping page 18
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 Intel NetStructure 480T Routing Switch is the
backbone of the network, providing routing capability. The 470T and 470F
switches provide gigabit connectivity from the 480T to the Intel Express
460T Standalone Switches through the 460T gigabit uplinks.
Intel® NetStructure™ 470T Switch
Intel Express 460T
Standalone Switches
Intel® NetStructure™ 470F Switch
Intel Express 460T
Standalone Switches
Intel® NetStructure™ 480T Routing Switch
Servers
8
CHAPTER 2
Using the Intel
®
NetStructure™ 470T and 470F Switches
Flow Control
During 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 until 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-duplex
or half-duplex.
• If a port operates at half-duplex, the switch sends a collision (also called
backpressure) that 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 switch.
Broadcast Storm Control
You can use broadcast storm control to control the amount of broadcast
traffic serviced by the switch. You can prevent broadcasts from taking an
excessive amount of network resources and degrading network
performance.
Using the 470 Switch
To control the amount of broadcast traffic, set an upper threshold
percentage for each port. The upper threshold is the percentage of the
port’s total bandwidth that is available for broadcast traffic. For example, if
a port’s upper threshold percentage is 4%, broadcast traffic can take up to
4% of the port’s total bandwidth.
Broadcast traffic
resumed
160 s.
% of% of
% of
% of% of
BroadcastBroadcast
Broadcast
BroadcastBroadcast
traffic ontraffic on
traffic on
traffic ontraffic on
the portthe port
the port
the portthe port
4%
Upper
threshold
1%
Lower
threshold
40 s.
TimeTime
Time
TimeTime
in secondsin seconds
in seconds
in secondsin seconds
Broadcast traffic
dropped
80 s.120 s.
9
CHAPTER 2
Intel® NetStructure™ 470T and 470F Switches User Guide
The switch checks the amount of broadcast traffic on each port every 20
seconds. If the port detects that the amount of broadcast traffic exceeds the
upper threshold on two subsequent checks, the port drops all broadcast
traffic.
When broadcast traffic is dropped for storm control, the switch continues
to check the amount of broadcast traffic on each port. For the port to begin
accepting broadcast traffic again, the amount of broadcast traffic must fall
below the lower threshold percentage. The lower threshold percentage, 1%,
is a factory default. If broadcast traffic falls below the lower threshold
percentage when the port is checked, the switch automatically resumes
servicing broadcast traffic.
When broadcast traffic servicing resumes, the switch begins checking the
amount of broadcast traffic against the upper threshold.
Spanning Tree Protocol
Spanning Tree Protocol, as described in the IEEE (Institute of Electrical and
Electronic Engineers) 802.1D specification, is a protocol designed to
prevent 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 determines 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.
10
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 that can take over if the primary
link fails.
Backup Path from Client A to Server B:
Switch A –> Switch B –> Switch C
Switch A
Primary Path from Client A to Server B: Switch A –> Switch C
Switch B
P
a
: 3
0
0
th
a
P
t: 1
s
o
C
Path: 1
Cost: 100
th
: 2
C
o
s
t: 2
0
0
Switch C
Server BPC Client A
CHAPTER 2
Using the Intel
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, traffic is automatically sent over the backup
path.
®
NetStructure™ 470T and 470F Switches
Tagged Frames
The 802.1D (1998 Edition) and 802.1Q specifications published by the
IEEE 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, you can configure the switch to work with untagged
devices. For more information, see “How to configure 802.1Q VLANs” in
Chapter 5.
Priority Tagging
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 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).
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.
Using the 470 Switch
11
CHAPTER 2
HIGH
LOW
Incoming
packet
transmit
queue
for the
port
7
6
5
4
3
2
1
0
Express 460T
Network
Intel® NetStructure™ 470T and 470F Switches User Guide
Although 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.
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.
Note
When connecting to another
switch, connect anchor port to
anchor port and member port to
member port.
12
You can use link aggregation, also known as port trunking, 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.
CHAPTER 2
Using the Intel
®
NetStructure™ 470T and 470F Switches
Guidelines
• The switch treats aggregated links as a single port. This includes
spanning tree and VLAN configur ations.
• 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 hav e 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.
Using the 470 Switch
Virtual LANs
A Virtual LAN (VLAN) is a logical network grouping you can use to isolate
network traffic so members of the VLAN receive traffic only from other
members. Creating a VLAN is the virtual equivalent to physically moving a
group of devices to a separate switch (creating a Layer 2 broadcast domain).
With VLANs you can reduce broadcast traffic for the entire switch, and
increase security, without changing the wiring of your network.
The 470 switches support three types of VLANs:
• Port-based
• Tag-based (IEEE 802.1Q)
• Protocol-based
13
CHAPTER 2
Intel® NetStructure™ 470T and 470F Switches User Guide
Port-based VLANs
Port-based VLANs are the simplest and most common form of VLAN. In a
port-based VLAN, the system administrator assigns the 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. Port-based VLANs are easy to configure and all changes
are transparent to the users because they take place at the switch. The 470
switches support a maximum of four port-based VLANs. A port can belong
to only one port-based VLAN at a time.
14
If a user changes to another location, the system administrator reassigns the
port to the new VLAN. 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 prevent an individual device on that switch from becoming part
of the VLAN.
Tag-based (IEEE 802.1Q) VLANs
The tag-based VLAN supported by the 470 switches is based on the IEEE
802.1Q specification. The specification provides a uniform way to create
VLANs within a network and allows you to create a VLAN that can span
across the network. Until the release of IEEE 802.1Q, it was not possible to
create a VLAN across devices from different vendors.
CHAPTER 2
Using the Intel
®
NetStructure™ 470T and 470F Switches
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. The example below shows a
470F switch.
Local
Console: 9600-8-N-1
Management
Flow Ctrl=None
(EIA 232)
12345678
TX RXTX RXTX RXTX RXTX RXTX RXTX RXTX RX
VLAN 2:
Manufacturing
VLAN 1:
Engineering
Intel® NetStructure™ 470F Switch
Status
Link\Activity
Link = Solid Green
12345678
Activity = Blinking Green
Link\Act
Using the 470 Switch
VLAN 1 computers
can't see VLAN 2
computers
Server and Printer
are members of both
VLANs
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.
A logical grouping can be mapped to a workgroup. For example, you can
create a VLAN that groups all the users from the engineering department.
Benefits of this logical grouping are: it improves performance by reducing
traffic that belongs to a different logical group (e.g. marketing), improves
security (engineering can’t see marketing), and eases moves because the
user doesn’t have to be physically located in the same group to participate in
the VLAN.
15
CHAPTER 2
Intel® NetStructure™ 470T and 470F Switches User Guide
Protocol-based VLANs
In a protocol-based VLAN, traffic is bridged through specified ports based
on its protocol. Any packet using a different protocol is dropped as it enters
the switch. This type of VLAN allows you to use a common protocol to
communicate, yet prevents any packets that are not using the specified
protocol, from entering the switch.
For example, you can attach a LAN using NetBEUI traffic to port 1 on the
switch, and attach a LAN using IPX traffic to port 2 on the switch. Then,
attach a router connected to the Internet, to port 8. Create an IP VLAN that
incorportates ports 1, 2, and 8. The NetBEUI traffic on port 1is not passed
to ports 2 or 8. The IPX traffic on port 2 is not passed to ports 1 or 8.
However, computers using the IP protocol can talk freely to ports 1, 2, and
8. This allows the computers to connect to the Internet, yet not be
bombarded with traffic that they do not need to see.
The 470 switches support a maximum of four protocol-based VLANs, and
they can be either IP, IPX, NetBEUI, or all three combined. Each port can
be a member of only one protocol-based VLAN. The example below shows
a 470F switch.
16
Protocol-based VLANs can help optimize network traffic patterns because
protocol-specific broadcast messages are sent only to computers that use
that protocol. For example, if a NetBEUI VLAN is created, only NetBEUI
traffic is allowed to pass through the VLAN.
CHAPTER 2
Using the Intel
®
NetStructure™ 470T and 470F Switches
Spanning Tree Protocol and VLANs
The 470 switches support the Spanning Tree Protocol across the entire
switch, not across each VLAN. If VLANs create a redundant link between
two switches and both of those switches have the Spanning Tree Protocol
enabled, one of the VLANs is disabled.
The following diagram shows an example. 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 MKT_VLAN on Switch 1 to the MKT_VLAN on Switch 2.
When spanning tree is enabled on both switches, the redundant link between
the MKT_VLANs is blocked and those VLANs can no longer communicate.
The example below sho ws 470F switches.
Using the 470 Switch
GARP VLAN Registration Protocol (GVRP)
Because tag-based (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 saves the network administrator from
having to manually propagate VLAN configuration information across
switches.
17
CHAPTER 2
Intel® NetStructure™ 470T and 470F Switches User Guide
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, and so on) 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.
Note
Dynamically created VLANs are
not saved in the switch’s
memory. If the device sending out
the GVRP updates is removed,
the dynamic VLAN is removed.
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 VLAN configurations within the same
switch. For devices that don’t support GVRP, static VLAN configurations
are created by the user on the switch.
When the switch is running 802.1Q VLANs, Spanning Tree Protocol is
enabled for GVRP to work properly .
Internet Group Management Pr otocol (IGMP)
Normally, 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.
18
IGMP Snooping requires a router that detects multicast groups on its subnets
and keeps track of group membership.
Using Intel® Device
3
View
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
• A 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
• Support for Remote Monitoring (RMON)
• Web or Windows* platform
• Plug-in to HP OpenView*, IBM Tivoli* NetView*, and Intel
LANDesk® Network Manager
• Other useful tools such as a TFTP server
19
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 into 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.
20
2 Choose the version of Intel Device View you want to install.
• To install Intel Device View for use on this PC only, click Installfor Windows.
• To install Intel Device View on a Web server, click Install forWeb. 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 available if you have OpenView,
NetView, or LANDesk Network Manager installed on the PC.
3 Follow the instructions in on the installation screens.
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
Starting Intel Device View
Install either the Windows or Web version of Intel Device View.
Windows* version
On your desktop, click Start and then point to Programs > Intel Device View
> Intel Device View - Windows to go to the Intel Device View main screen.
Web version
•On your desktop, click Start and then point to Programs > Intel Device
View > Intel Device View - Web to go to the Intel Device View main
screen.
•To view Intel Device View from another PC on your network, type the
following URL. In the following example, the URL is entered in 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.
Intel
®
Device View
Web Server
IIS* 2.0 or later
Peer Web Services*
Netscape Enterprise* Web
Server 3.01 or later
21
CHAPTER 3
Intel® NetStructure™ 470T and 470F Switches User Guide
Installing a New Switch
After you install a new switch on your network, you can use the Intel
Device View 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.
22
4 Follow the instructions in the wizard to assign an IP address and a name
to the switch.
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.
CHAPTER 3
Intel Device View
Different states of the 470 switches are represented by icons in the Device
Tree.
Device Tree icons
Device Tree root
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
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.
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 icon for the new switch appears in the Device Tree.
23
Intel
®
Device View
CHAPTER 3
Intel® NetStructure™ 470T and 470F Switches User Guide
To refresh the Device Tree
Refreshing the Device Tree updates it to show any newly discovered
devices and changes in device status.
1 Right-click anywhere on the Device Tree.
2 On the menu that appears, click Refresh.
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 remove the device from the
network.
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 icon is highlighted in the Device Tree.
24
Losing contact with a switch
If Intel Device View loses contact with a switch, the color of the switch icon
changes to red, to indicated that the switch is not responding.
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.
Loading...
+ 125 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.