From: chwarren@cox.net
Date: Thu May 08 2003 - 13:05:23 GMT-3
Yeah, I started by trying to replicate what Tom did, created int VLAN16 (no vlan db config beforehand), tried 'no shut' -- didn't work until I shut vlan1;
then proceeded to do the same with vlan3 (again, no vlan db config beforehand). In order to bring int vlan3 up, had to shut vlan16 first.
both vlans were automatically added to the vlan db upon creation of vlan interfaces.
my summation, you must close the active vlan interface prior to activating another...each 'active' vlan interface was in an up,up status....no other port level assignments of the specific vlans was applied.
Chuck
CCIE# 10653
>
> From: MADMAN <dave@interprise.com>
> Date: 2003/05/08 Thu AM 11:14:17 EDT
> To: chwarren@cox.net
> CC: Tom Young <gitsyoung@yahoo.co.jp>, ccielab@groupstudy.com
> Subject: Re: no shut the vlan interface
>
>
> Sounded strange so I tried creating a new VLAN interface of a VLAN
> that does not exist. It seems to default to the no shut state though
> obviously since the VLAN isn't active the interface is down, down.
>
> I tried both ways, via the VLAN database and simply creating the
> interface VLAN in config mode.
>
> Dave
>
> chwarren@cox.net wrote:
> > do a 'shut' on int vlan16 first, then try 'no shut' on int vlan3.
> >
> > Only one active 'management' interface.
> >
> >
> >>From: Tom Young <gitsyoung@yahoo.co.jp>
> >>Date: 2003/05/08 Thu AM 03:39:28 EDT
> >>To: ccielab@groupstudy.com
> >>Subject: no shut the vlan interface
> >>
> >>hi,group,
> >>
> >> I added a new vlan 3 into my cat3550XL switch, but I
> >>couldn't do no shut for int vlan 3 whatever I had done.
> >>The interface of VLAN 3 always int the SHUT status.Why?
> >>
> >>Thanks alot
> >
> >
> >
>
>
> --
> David Madland
> CCIE# 2016
> Sr. Network Engineer
> Qwest Communications
> 612-664-3367
>
> "Government can do something for the people only in proportion as it
> can do something to the people." -- Thomas Jefferson
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:39 GMT-3