C H A P T E R  6

Configuring VLAN Parameters

A virtual LAN (VLAN) is a collection of network nodes that share the same broadcast domain regardless of their physical location or connection point in the network. A VLAN serves as a logical workgroup with no physical barriers. Thus users can share information and resources as though located on the same LAN. VLANs also allow a single physical LAN to be divided into multiple logical LANs. By restricting the flow of traffic between the members of different VLANs, this allows the separation of tenants or tiers.

This chapter describes the types of VLANs available and shows how to enable and configure VLAN parameters for the Sun Fire B10n blade.

This chapter includes the following topics:


Available VLAN Types

The Sun Fire B10n blade CLI allows for the confutation of three different VLAN types:

As its name suggests, this VLAN is used for management traffic to and from the load balancing blade. Examples are Telnet traffic and signaling between the load balancer and the server. The latter includes service configuration messages and server module health monitoring. When the management VLAN is enabled, outbound management traffic is enforced for added security, and outbound management is tagged with this VLAN ID. There is one management VLAN per load balancing blade.

This VLAN carries inbound traffic from the client network to the load balancer. The servers are expected to use this VLAN for the response traffic back to the client network. When the load balancing blade sends packets to the client network (such as during the handshake to establish a connection), it tags these packets with this VLAN ID. However, there is no inbound enforcement for the data VLAN. There is one data VLAN per load balancing blade.

This VLAN is used for all data traffic between the load balancing blade, the server, and potentially the SSL proxy blade. Each service on the load balancing blade may have its own service VLAN configured.


Enabling and Disabling VLAN Tagging

The enable vlan command enables the VLAN tagging of data or management traffic from the Sun Fire B10n blade.

By default, VLAN tagging of all traffic from the blade is disabled.

When VLAN tagging is enabled, the VLAN ID used for management traffic is the one set by the management vlan command. The management VLAN setting also filters incoming traffic.

The VLAN ID used for tagging client traffic is the one set by the data vlan command.


procedure icon  To Enable VLAN Tagging

single-step bulletAs admin in config mode, enter the following command:

puma(config){admin}# enable vlan all

The enable vlan all command enables VLAN tagging for both management traffic and client traffic.

single-step bulletAs admin in config mode, enter the following command:

puma(config){admin}# enable vlan management

The enable vlan management command enables VLAN tagging for management traffic only.

single-step bulletAs admin in config mode, enter the following command:

puma(config){admin}# enable vlan data

The enable vlan data command enables VLAN tagging for client traffic only.


procedure icon  To Set Client VLAN Tagging

The data vlan command sets the default VLAN ID to be used on all outbound data traffic destined to and from the client.

This parameter must be set for each blade and serves as a default. This parameter is valid only if the content load balancing blade is enabled for VLAN tagging of outbound traffic by the enable vlan command.

The valid range for VLAN ID values is 1 to 4095.

single-step bulletAs admin in config mode, type the following command:

puma(config){admin}# data vlan vlan_id

Where vlan_id is the data VLAN tag. The default VLAN ID is 1.


procedure icon  To Set Management VLAN Tagging

The management vlan command sets the management VLAN ID on the content load balancing blade. When the management VLAN is enabled, the blade processes inbound management traffic only when it is tagged with this VLAN ID. The blade also uses the VLAN ID to tag all outbound management traffic.

The valid range for VLAN ID values is 1 to 4095.

single-step bulletAs admin in config mode, type the following command:

puma(config){admin}# management vlan vlan_id

Where vlan_id is the management VLAN tag. The default management VLAN is 2.

Example
puma{config}{admin}# management vlan 22


procedure icon  To Disable VLAN Tagging

The no enable vlan command disables the VLAN tagging of outbound data or management traffic from the content load balancing blade.

single-step bulletAs admin in config mode, type the following command:

puma{config}{admin}# no enable vlan <data|management|all>

TABLE 6-1 describes the parameters for the no enable vlan command:Table describing the parameters for the no enable vlan command.

TABLE 6-1 Parameters for the no enable vlan Command

Parameter

Description

data

Disables VLAN tagging of outbound data traffic.

management

Disables VLAN tagging of outbound management traffic.

all

Disables VLAN tagging of all outbound traffic.


By default, VLAN tagging of all outbound traffic is disabled on the content load balancing blade.

single-step bulletAs admin in config mode, type the following command:

puma(config){admin}# no enable vlan all

The no enable vlan all command disables VLAN tagging for both management and client traffic.

single-step bulletAs admin in config mode, type the following command:

puma(config){admin}# no enable vlan management

The no enable vlan management command disables VLAN tagging for management traffic only.

single-step bulletAs admin in config mode, type the following command:

puma(config){admin}# no enable vlan data

The no enable vlan data command disables VLAN tagging for client traffic only.


procedure icon  To Enable VLAN Tagging for a Service

single-step bulletAs admin in config mode, enter the enable service vlan command:

puma(config){admin}# enable service vlan service_name 

By default, VLAN tagging is disabled for a service.

Examples
puma(config){admin}# enable service vlan SVC1


procedure icon  To Set VLAN for Service

The service vlan command sets the VLAN tag to be added to all the traffic of a service.

single-step bulletAs admin in config mode, enter the service vlan command:

puma(config){admin}# service vlan service_name vlan vlan_id

Where:

service_name is the name of the service.

vlan is the qualifier for the VLAN ID.

vlan_id is the VLAN ID.

The valid range for VLAN ID values is 1 to 4095. The default VLAN ID is 1.

Example

The following example uses the vlan_id of 25 for the service SVC1.

puma(config){admin}# service vlan SVC1 vlan 25


procedure icon  To Disable VLAN Tagging for a Service

single-step bulletAs admin in config mode, enter the no enable service vlan command:

puma(config){admin}# no enable service vlan service_name 

By default, VLAN tagging is disabled for a service.

Examples

The following example disables VLAN tagging for the service SVC1.

puma(config){admin}# no enable service vlan SVC1


procedure icon  To Show VLANs

single-step bulletAs admin, enter the show vlan command:

puma{admin}# show vlan 

You will see output similar to the following:

puma{admin}# show vlan
 
System VLAN Table:
==============================================================================
VLAN Type                          VLAN ID      Status
------------------------------------------------------------------------------
Management                         22           Enabled
Data                               21           Enabled
==============================================================================
 
Service VLAN Table:
==============================================================================
Service Name                      VLAN ID      Status
------------------------------------------------------------------------------
SVC1                              25           Enabled
s1                                 1           Disabled
==============================================================================