beautypg.com

Vlan connections – Amer Networks E5Web GUI User Manual

Page 169

background image

A physical interface does not need to be dedicated to VLANs and can carry a mixture of VLAN
and non-VLAN traffic.

Physical VLAN Connection with VLAN

The illustration below shows the connections for a typical cOS Core VLAN scenario.

Figure 3.1. VLAN Connections

With cOS Core VLANs, the physical connections are as follows:

One of more VLANs are configured on a physical Clavister Security Gateway interface and this
is connected directly to a switch. This link acts as a VLAN trunk. The switch used must support
port based VLANs. This means that each port on the switch can be configured with the ID of
the VLAN or VLANs that a port is connected to. The port on the switch that connects to the
security gateway should be configured to accept the VLAN IDs that will flow through the
trunk.

In the illustration above the connections between the interfaces if1 and if2 to the switches
Switch1 and Switch2 are VLAN trunks.

Other ports on the switch that connect to VLAN clients are configured with individual VLAN
IDs. Any device connected to one of these ports will then automatically become part of the
VLAN configured for that port. In Cisco switches this is called configuring a Static-access VLAN.

On Switch1 in the illustration above, one interface is configured to be dedicated to VLAN2 and
two others are dedicated to VLAN1.

The switch could also forward trunk traffic from the security gateway into another trunk if
required.

Chapter 3: Fundamentals

169

This manual is related to the following products: