02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The only way to remove an interface from <strong>the</strong> Default VLAN is to place <strong>the</strong> interface in Default mode by<br />

entering <strong>the</strong> no switchport command in <strong>the</strong> INTERFACE mode.<br />

Assigning an IP address to a VLAN<br />

VLANs are a Layer 2 feature. For two physical interfaces on different VLANs to communicate, you must<br />

assign an IP address to <strong>the</strong> VLANs to route traffic between <strong>the</strong> two interfaces.<br />

The shutdown command in INTERFACE mode does not affect Layer 2 traffic on <strong>the</strong> interface; <strong>the</strong><br />

shutdown command only prevents Layer 3 traffic from traversing over <strong>the</strong> interface.<br />

VLAN interfaces do not support SNMP, FTP, or TFTP.<br />

To assign an IP address, use <strong>the</strong> following command in INTERFACE mode:<br />

Command Syntax Command Mode Purpose<br />

ip address ip-address mask<br />

[secondary]<br />

In <strong>FTOS</strong>, VLANs and o<strong>the</strong>r logical interfaces can be placed in Layer 3 mode to receive and send routed<br />

traffic.<br />

Native VLANs<br />

INTERFACE Configure an IP address and mask on <strong>the</strong><br />

interface.<br />

• ip-address mask — Enter an address in<br />

dotted-decimal <strong>for</strong>mat (A.B.C.D) and <strong>the</strong><br />

mask must be in slash <strong>for</strong>mat (/24).<br />

• secondary — This is <strong>the</strong> interface’s backup<br />

IP address. You can configure up to eight<br />

secondary IP addresses.<br />

Traditionally, physical ports can be ei<strong>the</strong>r untagged <strong>for</strong> membership to one VLAN or tagged <strong>for</strong><br />

membership to multiple VLANs. An untagged port must be connected to a VLAN-unaware station (one<br />

that does not understand VLAN tags), and a tagged port must be connected to a VLAN-aware station (one<br />

that generates and understands VLAN tags). Native VLAN support breaks this barrier so that a port can be<br />

connected to both VLAN-aware and VLAN-unaware stations. Such ports are referred to as hybrid ports.<br />

Native VLAN is useful in deployments where a Layer 2 port can receive both tagged and untagged traffic<br />

on <strong>the</strong> same physical port. The classic example is connecting a VOIP phone and a PC to <strong>the</strong> same port of<br />

<strong>the</strong> switch. The VOIP phone is configured to generate tagged packets (with VLAN = VOICE VLAN), and<br />

<strong>the</strong> attached PC generates untagged packets.<br />

To configure a port so that it can be a member of an untagged and tagged VLANs:<br />

Step Task Command Command Mode<br />

1 Remove any Layer 2 or Layer 3 configurations from <strong>the</strong> interface. INTERFACE<br />

2 Configure <strong>the</strong> interface <strong>for</strong> hybrid mode. portmode hybrid INTERFACE<br />

188 Layer 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!