[c-nsp] Forcing VLAN interface to UP state

[Aaron R]

All vlan's are trunked by default? 

I know for routing you can put a static in with a high AD pointing to the
null interface.. I don’t believe this will bring up the interface though.

Cheers,

Aaron.

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jeff Fitzwater
Sent: Wednesday, October 01, 2008 9:29 PM
To: Bagosi Rómeó
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Forcing VLAN interface to UP state

I believe if you just add the vlan to any trunk it will come up, even  
if you don't need that vlan on the trunk port.


On Oct 1, 2008, at 9:02 AM, Bagosi Rómeó wrote:

> Hi,
>
> Is there a way to force a VLAN interface (ex.: interface vlan 400)  
> to UP/UP state on a Cisco UC520 (router, switch...), WITHOUT  
> connecting a device to a port which is in the mentioned VLAN?
>
> The current configuration is:
> int vlan 400
> ip address 10.1.1.1 255.255.255.0
>
> show int vlan 400
> Vlan300 is up, line protocol is down
> ...
>
> Thanks,
> Romeo Bagosi
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com 
Version: 8.0.169 / Virus Database: 270.7.0/1679 - Release Date: 9/18/2008
5:03 PM