Page 121 / 128 Scroll up to view Page 116 - 120
Benefits of VLANs
z
Grouping users into logical networks for performance enhancement.
z
Provides effective broadcasts containment between Segmented Ports, which prevents
flooding of a network.
z
Offers security by completely isolating from each other the different Broadcast Domains
connected on separate Segmented Ports.
z
Preserving current investment in equipment and cabling.
z
Providing an easy, flexible, economic way to modify logical groups when needed.
z
Network administrators can easily "fine tune" the network.
z
Keeping network structure from the physical topology of the cabling.
z
Making large networks more manageable.
You can group users according to some shared characteristic, such as a common business
function or a common protocol. A single switch may have several independent VLANs within
it. Below is a example that R&D, Manufacturing and Administration group can be partitioned
into two different VLAN group, even members in different group can’t talk directly, but they
still share the same server, such as MRP server, printer server in Adminstration group…etc.
- 121 -
Page 122 / 128
5.2. Trunking Application used with switch
Trunking allows you to increase the available bandwidth between switches by grouping ports
into a trunk. Trunk can also be used to connect server to switches for higher bandwidth service
required. You can use trunking to improve the throughput between segments. Moreover, this
switch further provides trunk with fail-over function, that is, when one of the links of trunk is
fail or broken, the traffic originally go through that link will be automatically re-direct to other
links of trunk, this give the trunk with redundancy and greatly increase the value of trunking.
5.3. Single IP application
Single IP
is a management utility of network devices for administrator to access private IP
devices through a single IP (real/public IP or private IP). By this utility, administrator can
manage many more network devices than ever and reduce the demand of real IPs, because every
real IP switch can be an agent host for any network devices in their private IP domain.
There are some defects in the current solutions of network management. For example, switches
with legacy “stack” capability have to stack together due to their special limited-length cables,
and have the limitation of stacking quantities and brand compatibility due to hardware
specification. Moreover, administrator always has troubles in finding out the target window
among those multi-display interfaces. Though there are expert network management utilities
available in the current market, like HP OpenView, expensive cost and difficult task of
- 122 -
Page 123 / 128
implementation into embedded system are main drawbacks for their practical application.
Because of the rapid development of Ethernet, the scare of real IP shortage becomes a serious
issue when an enterprise continues its IA growth. It is a resource waste and cost a large expense
that every individual host has its own real IP inside the enterprise’s network. Privates IPs and
NAT function (provided by router, gateway or IP sharing) provide a solution to the shortage of
real IP, but new issue gives rise to that remote user from internet has no access permission into
the private IP domain, thus an administrator has no choose but accesses the private IP devices
from the very location of the local area network to trouble shoot any problems that network
clients report, until now “Single IP-Agent mode”, one of this switch special features, provides a
new solution for all issues above.
There are benefits of “Single IP-Agent mode”:
1. Reduce the demand of real IP (public IP).
Since there are up to 32 devices which have a IP agent as “Single IP” switch, meaning that
the switch becomes a network agent and handles all functions of these devices, MIS can
reduce the number of hosts that are directly connected to internet, and make use the saved
real IPs more efficiency.
2. Integrate network devices without modifying hardware or software.
“Single IP” is a technique mainly based on application layer in OSI standard. The
connection between master and slave hosts is linked by Ethernet protocol. It is little concern
of hardware and packet transmits. Modifications of hardware or software of the slave hosts
are not necessary. Thanks to the characteristics, single IP switch gives the best compatibility
with other network devices, router, gateway, web server and even another brand switch.
3. Handy User interface without learning complex setting or changing user’s habit of
operation.
A floating menu gives a comprehensive user interface for administrator to pick the managed
devices. It provides host IP and host name in the same time, saving the trouble that the
administrator tries to remember which IPs those slave hosts are assigned to. Since there is
only one browse windows displaying on the screen in the same time, agent manager play a
role like as TV channel controller. Administrator can easily switch to the device he/she
wants and enter the setting webpage as did before.
4. Totally remote control of network devices in private IP domain.
It is not necessary for MIS to put all devices together in one place. Single IP function will
operate normally no matter how far the distance is between the master and the slave hosts if
their packets can reach each other in local area network. Moreover, a remote administrator
can access the far-side servers in the private domain through the intermediary of single IP
switch, which is directly connected to Internet.
- 123 -
Page 124 / 128
5. No up-link limitation through Gigabit port.
Unlike stacking mode, up-link in agent mode can be achieved through any port rather than
Gigabit port only. This provides great flexibility as long as network administrator can
access them, and hence Gigabit ports can be saved for other applications.
Typical setup of Single IP network:
There are three typical examples to demonstrate the usage of “Single IP-Agent mode”.
1.
Master and slave switches in the same LAN domain.
In this example, master switch manages 2 slave switches and 1 router.
Switch IP of master is 192.168.223.100. Set its management mode to “Agent Master”.
Since the IP domain of slaves and router are in the IP domain 192.168.223.0, Agent IP of master
should be set as same as switch IP (192.168.223.100).
Add slave1 and slave2 into agent list by auto-discover or by manual. Router can only be added
by manual. A
dministrator (192.168.223.30) can access those slaves through master.
LAN IP: 192.168.223.254
WAN IP: 211.23.53.250
Switch IP: 192.168.223.102
Gateway: 192.168.223.254
Switch IP: 192.168.223.101
Gateway: 192.168.223.254
IP: 192.168.223.30
Switch IP: 192.168.223.100
Agent IP: 192.168.223.100
Gateway: 192.168.223.254
2. Master and slave switches in different LAN domain.
In this example, master will manage 2 slave switches and 1 router in other IP domain.
- 124 -
Page 125 / 128
IP: 192.168.1.30
LAN IP: 192.168.223.254
WAN IP: 211.23.53.250
Switch IP: 192.168.1.100
Agent IP: 192.168.223.100
Gateway: optional
Switch IP: 192.168.223.101
Gateway: 192.168.223.254
Switch IP: 192.168.223.102
Gateway: 192.168.223.254
The differences from example1 are that administrator and master switch IP are in the other IP
domain (192.168.1.0).
Switch IP of master is 192.168.1.100. Set its management mode to “Agent Master”.
According to the basic rule 1, agent IP should be set in the same domain of slaves, that is,
192.168.223.100. The other procedures are the same as example 1.
Now administrator (192.168.1.30) can access the slaves in other domain (192.168.223.0).
3. Master in WAN domain and slaves in LAN domain.
This example gives the practice application for remote management.
The differences from example 2 are that master switch links directly to Internet and administrator
from worldwide can access it through Internet.
Set the Switch IP and gateway of master switch to real IP (211.23.53.251 and 211.23.53.249)
and make sure administrator can access the master switch from Internet. The other procedures
are the same as example 1.
Now administrator from Internet can access the slaves in other domain (192.168.223.0).
Somewhat we can image the master is playing a role of tiny virtual server for these slaves.
- 125 -

Rate

4.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top