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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Except <strong>for</strong> hybrid ports, only a tagged interface can be a member of multiple VLANs. Hybrid ports can be<br />

assigned to two VLANs if <strong>the</strong> port is untagged in one VLAN and tagged in all o<strong>the</strong>rs.<br />

When you remove a tagged interface from a VLAN (using <strong>the</strong> no tagged interface command), it will<br />

remain tagged only if it is a tagged interface in ano<strong>the</strong>r VLAN. If <strong>the</strong> tagged interface is removed from <strong>the</strong><br />

only VLAN to which it belongs, <strong>the</strong> interface is placed in <strong>the</strong> Default VLAN as an untagged interface.<br />

Use <strong>the</strong> untagged command to move untagged interfaces from <strong>the</strong> Default VLAN to ano<strong>the</strong>r VLAN:<br />

Step Command Syntax Command Mode Purpose<br />

1 interface vlan vlan-id CONFIGURATION Access <strong>the</strong> INTERFACE VLAN mode of <strong>the</strong><br />

VLAN to which you want to assign <strong>the</strong> interface.<br />

2<br />

untagged interface INTERFACE Configure an interface as untagged.<br />

This command is available only in VLAN<br />

interfaces.<br />

The no untagged interface command removes <strong>the</strong> untagged interface from a port-based VLAN and<br />

places <strong>the</strong> interface in <strong>the</strong> Default VLAN. You cannot use <strong>the</strong> no untagged interface command in <strong>the</strong><br />

Default VLAN. Figure 95 illustrates <strong>the</strong> steps and commands to move an untagged interface from <strong>the</strong><br />

Default VLAN to ano<strong>the</strong>r VLAN.<br />

Figure 95 Example of Moving an Untagged Interface to Ano<strong>the</strong>r VLAN<br />

<strong>Force10</strong>#show vlan<br />

Codes: * - Default VLAN, G - GVRP VLANs<br />

NUM Status Q Ports<br />

* 1 Active U Gi 3/2<br />

2 Active T Po1(So 0/0-1)<br />

T Gi 3/0<br />

3 Active T Po1(So 0/0-1)<br />

T Gi 3/1<br />

4 Inactive<br />

<strong>Force10</strong>#conf<br />

<strong>Force10</strong>(conf)#int vlan 4<br />

<strong>Force10</strong>(conf-if-vlan)#untagged gi 3/2<br />

<strong>Force10</strong>(conf-if-vlan)#show config<br />

!<br />

interface Vlan 4<br />

no ip address<br />

untagged GigabitE<strong>the</strong>rnet 3/2<br />

<strong>Force10</strong>(conf-if-vlan)#end<br />

<strong>Force10</strong>#show vlan<br />

Codes: * - Default VLAN, G - GVRP VLANs<br />

NUM Status Q Ports<br />

* 1 Inactive<br />

2 Active T Po1(So 0/0-1)<br />

T Gi 3/0<br />

3 Active T Po1(So 0/0-1)<br />

T Gi 3/1<br />

4 Active U Gi 3/2<br />

<strong>Force10</strong>#<br />

Use <strong>the</strong> show vlan command to determine<br />

interface status. Interface (gi 3/2) is untagged<br />

and in <strong>the</strong> Default VLAN (vlan 1).<br />

In a port-based VLAN (vlan 4), use <strong>the</strong><br />

untagged command to add <strong>the</strong> interface to that<br />

VLAN.<br />

The show vlan command output displays <strong>the</strong><br />

interface’s changed status (gi 3/2). Since <strong>the</strong><br />

Default VLAN no longer contains any interfaces,<br />

it is listed as inactive.<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 187

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

Saved successfully!

Ooh no, something went wrong!