[f-nsp] FastIron: many vlans

[Jared Valentine]

I'm guessing that when you create a VLAN group, you are limited to
performing operations against the entire VLAN group.  Ie: you tagged e 1 to
4 in the VLAN group.  

An untagged port is something that can only be done on a single VLAN.
Chances are you'll have to remove vlan 303 from the vlan group, create it
individually, and then configure the ports appropriately (tagged and
untagged).

Jared Valentine
hidden at xmission.com



-----Original Message-----
From: foundry-nsp-bounces at puck.nether.net
[mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Randy McAnally
Sent: Thursday, October 13, 2011 10:26 AM
To: Randy McAnally; Maarten Bollen | Atrato IP Networks
Cc: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] FastIron: many vlans

On Thu, 6 Oct 2011 12:03:14 -0400, Randy McAnally wrote
> On Thu, 6 Oct 2011 17:11:36 +0200, Maarten Bollen | Atrato IP 
> Networks wrote
> > how about:
> > vlan-group 1 vlan 200 to 400
> >  tag e 1 to 4
> > 
> > Confirmed on TurboIron, not sure if it is an fastiron command.

Followup for the foundry experts... now that we have vlan group for the
trunk
port, how to add an untagged port?

telnet at fesx(config)#vlan 303
error - L2 vlan 303 was already configured in vlan group 1

~Randy

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp