Configuring the switch using the console interface, Before you start, General deployment strategy – D-Link DES-3326 User Manual
Page 87: Onfiguring the, Witch, Sing the, Onsole, Nterface
DES-3326 Layer 3 Fast Ethernet Switch User’s Guide
6
C
ONFIGURING THE
S
WITCH
U
SING THE
C
ONSOLE
I
NTERFACE
The DES-3326 supports a console management interface that allows the user to connect to the switch’s
management agent via a serial port and a terminal or a computer running a terminal emulation
program. The console can also be used over the network using the TCP/IP Telnet protocol. The console
program can be used to configure the switch to use an SNMP-based network management software over
the network.
This chapter describes how to use the console interface to access the switch, change its settings, and
monitor its operation.
Switch configuration settings that are saved to non-volatile RAM using Save
Changes from the Main Menu are retained in the switch’s memory, and are
reloaded when the switch is rebooted.
Before You Start
The DES-3326 supports a wide array of functions and gives great flexibility and increased network
performance by eliminating the routing bottleneck between the WAN and the intranet. Its function in a
network can be thought of as a new generation of wire-speed router that performs routing functions in
hardware, rather than in software.
General Deployment Strategy
The DES-3326 has many automatic features to detect the network topology and
adapt to changes in this topology, but it is recommended that a network scheme
be developed and entered statically into the DES-3326.
1.
Determine how the network would be best segmented. This is probably done using VLANs in an
existing layer 2 switched network.
2.
Develop an IP addressing scheme. This involves allocating a block of IP addresses to each
network segment. Each network subnet is then assigned a network address and a subnet mask.
3.
Determine which network resources must be shared by the subnets. Shared resources may be
connected directly to the Layer 3 switch, if need be. Static routes to each of the shared
resources should be determined.
4.
Determine how each subnet will communicate with the WAN or Internet. Again, static routes
should be determined and default gateways identified.
5.
Develop a security scheme. Some subnets on the network need more security or should be
isolated from the other subnets. IP or MAC filtering can be used. Also, one or more VLANs on
the Layer 3 switch can be configured without an IP subnet – in which case, these VLANs will
87