New VLAN problem

Hello,
I have problem in configuring new VLAN in 2950, when ever i established a more than one VLAN previous one is shutdown.
Only one VLAN is up at the time
Thank You

Hi Mansoor,
Are you talking about the "interface vlan " i.e layer 3 SVI on the 2950. id yes, then as it is a layer 2 switch you can only enable one 1 interface vlan on this switch only to manage it. You can not have multiple Vlan SVI on this switch as it is on Layer 3 switches like 3550.
HTH, please rate if it does.
-amit singh

Similar Messages

  • Problem with MAC Pinning and new VLAN

    [Cross posting to Nexus 1000V and UCS forums]
    Hi all, I have a working setup of UCS 1.4 (3i) and Nexus 1000V 1.4 and as per the best practice guide am using 'channel-group auto mode on mac-pinning' on the Nexus uplinks. I am having trouble when adding a new VLAN into this environment, and it is a reproducable problem across two different installations.
    I go through the usual VLAN creating process on the Nexus, the upstream network and within UCS itself. I create the new vethernet port profile and set it as an access port in the new VLAN. However when I attach a VM (either existing or new) to this new vethernet port profile within vCentre the VM cannot communicate with anything. However, if I disable MAC pinning with 'no channel-group auto mode on mac-pinning', the VM instantly starts to talk to the outside world and the new VLAN is up and running. I can then turn MAC pinning back on again and everything continues to work.
    So the question is, is this behaviour normal or is there a problem? Disabling MAC pinning does have a brief interruption to the uplink so is not a viable long-term solution for the customer when they want to add new VLANs. Is there a way to add new VLANs in this scenario without any network downtime, however brief?
    Thanks

    Simon,
    Let's gather some further outputs if you're able to recreate this (if this is prod, let me know and I'll whip this up in my lab).
    Go through the process of setting up the new VLAN.  Once you confirmed your VM has no connectivity when using a PP tied to the new VLAN, gather the following outputs into a text file and attach to this thread:
    From the VSM:
    show vlan
    show int trunk
    show log last 15
    module vem x execute vemcmd show vlan y (x = module of VEM where VM is running, y is the VLAN ID)
    module vem x execute vemcmd show bd y (y = VLAN ID)
    module vem x execute vemcmd show pc
    module vem x execute vemcmd show port
    module vem x execute vemcmd show pinning
    module vem x execute vemcmd show trunk
    From the CLI of UCS Interconnect:
    connect NXOS
    show vlan
    show int trunk
    Also please highlight or Identify:
    - Problem VLAN ID #
    - VM veth # in question (1000v)
    - vEth # for each Service Profile vNIC used for your VEM uplinks (UCS)
    We'll start with this and work from here.   Once I have these outputs I'll let you know if I need anything else.
    Regards,
    Robert
    (I'll keep this as the main thread, and update the 1000v forum once we resolve)

  • Problems trying to migrating ports to a new Vlan using an externar DHCP server

    Hello, here is the thing. I have the following configuration in my Core Switch:
    interface Vlan1
     ip address 10.24.74.1 255.255.254.0 secondary
     ip address 192.0.2.54 255.255.255.0
     ip helper-address 10.24.86.22
     no ip redirects
    As you see, we are using an external DHCP server for the Vlan1 and it is working:
    Internet  192.0.2.98              0   3c97.0e23.3d8d  ARPA   Vlan1
    Internet  192.0.2.194             0   e89a.8f77.36a0  ARPA   Vlan1
    Internet  192.0.2.195             0   e89a.8f77.01ab  ARPA   Vlan1
    Internet  192.0.2.198             2   001c.25de.acaa  ARPA   Vlan1
    Internet  192.0.2.199             0   d8eb.97a6.30a4  ARPA   Vlan1
    Internet  192.0.2.196             0   f0de.f1f1.1e06  ARPA   Vlan1
    Internet  192.0.2.203             0   e89a.8f77.016f  ARPA   Vlan1
    Internet  192.0.2.207             4   d0c7.89d6.3ba3  ARPA   Vlan1
    Internet  192.0.2.211             0   4437.e636.7ef7  ARPA   Vlan1
    But, when a try to migrate this port to a new Vlan (Vlan50), I got the following issue: 
    001290: Jul 23 08:27:44.705 GMT: DHCPD: DHCPREQUEST received from client 013c.970e.233d.8d.
    001291: Jul 23 08:27:44.705 GMT: DHCPD: client has moved to a new subnet.
    001292: Jul 23 08:27:44.705 GMT: DHCPD: Sending DHCPNAK to client 013c.970e.233d.8d.
    001293: Jul 23 08:27:44.705 GMT: DHCPD: broadcasting BOOTREPLY to client 3c97.0e23.3d8d.
    001294: Jul 23 08:27:44.725 GMT: dhcp_snooping_get_ingress_port: Interface src_index 0xF
    001295: Jul 23 08:27:44.725 GMT: DHCPD: DHCPDISCOVER received from client 013c.970e.233d.8d on interface Vlan50.
    001296: Jul 23 08:27:44.725 GMT: DHCPD: there is no address pool for 10.24.76.1.
    001297: Jul 23 08:27:44.725 GMT: DHCPD: setting giaddr to 10.24.76.1.
    001298: Jul 23 08:27:44.725 GMT: DHCPD: BOOTREQUEST from 013c.970e.233d.8d forwarded to 10.24.86.21.
    Any suggestions,
    Thank you in advance,

    Just to help someone who has the same issue.
    I found this on the web site:
    When the server receives a DHCPREQUEST from a client in the RENEWING (or REBINDING) state, it normally grants the renewal only if the client has an unexpired lease with this server. Otherwise the server ignores the request; the server to which the client is bound should answer the client. (The only exception is normally that if a server is sure the IP address the client is asking for is inappropriate for the client, the server will send a DHCPNAK, which forces the client back to the INIT state.)
    Thank you anyway

  • New vlan creating problem in FWSM Context

    Hi,
    We need to add a new IP range in the Network.  In my network there are lot of Context in FWSM.  Now to add a new network, I have created a new vlan and allowed to FWSM and same created in Context.  but the vlan is not getting up in FWSM and Context.
    Please help me out on this.

    All these process has been done and fine.  in the context the new vlan is showing down.  its not getting up.
    What to do to make this vlan up.
    find the output in RED.
    FWSM-1/CDR# show int ip brief
    Interface                  IP-Address      OK? Method Status                Prot                                                                           
    Vlan101                    172.19.60.4     YES CONFIG up                    up
    Vlan112                    10.128.112.254  YES CONFIG up                    up
    Vlan301                    172.16.11.254   YES CONFIG up                    up
    Vlan302                    172.16.12.254   YES CONFIG up                    up
    Vlan303                    172.16.13.254   YES manual down                  down

  • SFE2000: default VLAN problem

    Hi, i have a problem with SFE2000.
    I have 2 VLAN -> 1 (default) and 77
    on port 1 i have VLAN 1 untagged
    on LAG1 (G3+G4) i have VLAN 77T and 1U
    on LAG1 i have attached a vmware esxi 4.1 that has management interface on 192.168.1.254 (VLAN 1) and virtual machine traffic data on VLAN 77 (tagged)
    now ... from pc connected to port 1 ... i see 192.168.1.254 only for some seconds ... then i loose it (usualy i don't ...)
    that's really strange ... seems something about defalut vlan 1
    i could change all management port on new vlan 100 ... but ... is there any way to manage switch on a vlan different from default one (1)?
    tks

    Hi Stefano.
    I guess you have the latest version of code on the SFE2000.
    Version 1 code was not as flexible as current code versions  and only wanted to use the predefined vlans.  Version 3 code made the switch so much much more flexible.
    So if your switch isn't on version 3 code, go the link below and download the code via 'download software' option.
    http://www.cisco.com/en/US/products/ps9980/index.html
    I could check the manual, but I believe this layer 3 switch, you can select the management vlan when you are at version 3 of the code..
    So if your SFE2000 is at version 3 code and under phone  warranty and still having issues, why not see if a SBSC technician can look at the switch to determine operator or switch error?  To get to a SBSC technician check the link directly below.
    http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
    Hope this provides a direction for you to move forward.
    regards Dave

  • Simple VLAN Problem?

    I'm pretty sure this is a simple problem whose resolution I am overlooking. I just added a new VLAN to a 6513. VLAN 241 shows as active and looks no different from any other VLAN when I execute show vlan on the switch. The correct ports are shown in the VLAN and when I use show port 6/1, the port shows as connected. The VLAN is 241 and the interface for the VLAN is 10.241.234.1. I can ping the interface from within any router on the network just fine but I can't ping the station's IP address on the other side of port 6/1. The VLAN show's up correctly in show ip route. VLAN 241 does show up as allowed on the trunk line. I've compared the VLAN to a working one in the running-config for the switch and the router and nothing appears different. There ar eno access lists being used. Any ideas what I am overlooking here?

    show ip route 10.241.234.1:
    Routing entry for 10.241.0.0/16
    Known via "connected", distance 0, metric 0 (connected, via interface)
    Redistributing via eigrp 100
    Routing Descriptor Blocks:
    * directly connected, via Vlan241
    Route metric is 0, traffic share count is 1
    show vlan:
    204 LAB204 active 309 3/30-35
    241 LAB241 active 449 6/1-25,6/27-28,6/32
    show port 6/1:
    * = Configured MAC Address
    Port Name Status Vlan Duplex Speed Type
    6/1 connected 241 full 100 10/100BaseTX
    Port AuxiliaryVlan AuxVlan-Status InlinePowered PowerAllocated
    Admin Oper Detected mWatt mA @42V
    6/1 none none auto off no 0 0
    Port Security Violation Shutdown-Time Age-Time Max-Addr Trap IfIndex
    6/1 disabled shutdown 0 0 1 disabled 27
    Port Num-Addr Secure-Src-Addr Age-Left Last-Src-Addr Shutdown/Time-Left
    6/1 0 - - - - -
    Port Flooding on Address Limit
    6/1 Enabled
    Port Broadcast-Limit Multicast Unicast Total-Drop Action
    6/1 - - - 0 drop-packets
    Port Send FlowControl Receive FlowControl RxPause TxPause
    admin oper admin oper
    6/1 off off off off 0 0
    Port Status Channel Admin Ch
    Mode Group Id
    6/1 connected auto silent 296 0
    Port Status ErrDisable Reason Port ErrDisableTimeout Action on Timeout
    6/1 connected - Enable No Change
    Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize
    6/1 3203 649 0 0 363
    Port Single-Col Multi-Coll Late-Coll Excess-Col Carri-Sen Runts Giants
    6/1 0 0 0 0 0 389437 1
    Port Last-Time-Cleared
    6/1 Mon Apr 24 2006, 00:59:18
    Idle Detection

  • VLAN problem with SRW2048

    I'm having problem with a setup with multiple SRW2048 connected together.  However, I can see the problem when simplifying my setup and using only two SRW2048 together.
    The first SRW2048 receives one connection from many different servers and sends these connections to many other SRW2048.   I have configured one VLAN (untagged) per server for this switch.  The goal is instead of having 4 switches to do this job, I am using only one.
    The second SRW2048 receives the server connections from the other switch.  It then distributes these connections to various ports.  I use a different VLANs on this switch to group these connections and the server uplink together).
    Everything works fine until a plug the two switches together (i.e. I can verify the VLAN connections are working by connecting directly to each switch).  However, when both switches are connected, I get a flooding of all interfaces (like there is a bypass of the VLANs or a loop in the connections).  This happens as soon as I have two servers connected.  If I connect only one, there is no problem.
    If I connect a second server through a dumb switch instead of the first SRW2048, everything works fine, so I don't think that there is a loop.  The problem seems to be with the VLANs (how they "cascade" together). Anybody got an idea of what the problem is?
    For those who need a better visual representation:
    Server1->Port 1-8 Switch1 (VLAN1 on these ports)->Port 1 (and others) Switch2 (VLAN10 on these ports)
    Server2->Port 9-16 Switch1 (VLAN2 on these ports)->Port 2 (and others) Switch2 (VLAN11 on these ports)
    Etc for other servers...
    All VLANs are using the default settings from the Web Interfaces on the switches (Access mode, Untagged, other ports Excluded, etc.)

    1. The SRW switches are standalone devices. Unlike more expensive switches like those from the Cisco Small Business Pro series they don't automatically recognize each other and configure themselves to play nicely together.
    2. Generally, if you create a new VLAN on one SRW you have to create the same VLAN on all other switches and also add these to the trunks connecting the switches. Same applies to the ASA if you connect the SRWs to ASA. As long as a switch is not configured for a particular VLAN it won't accept traffic for it.
    3. The only thing that you may try is GVRP. I never tried this but I think it may do what you want: add a VLAN on a single switch and then propagate this to the trunks and other switches. I can't tell how well this works and whether the ASA will accept that, too.

  • VLAN Problem

    I have just Created a new VLAN on a 4507 and I am getting Ip addresses. The problem that I am having is that I can't hit the internet. Any Idea? I am thinking it might have to deal with DNS because DHCP is working fine?

    Matt
    If you are not able to ping to Internet resources by IP address then it takes any question of being a DNS issue out. In troubleshooting it is good to be able to eliminate some of the possibilities.
    I am not clear from your response what is the answer to the question that I asked about whether the PCs on the new VLAN are able to access resources within the organization network. If the PCs are able to access things that are several hops away, it shows that their network is being advertised within the organization network.
    So one followup question would be: can the PCs on the new VLAN ping to the device that is the gateway to the Internet for your network?
    I believe that there are several possible causes of this problem that we need to investigate:
    - it could be a problem of routing within your network. We need to verify whether the PCs can get to the network edge.
    - it could be a problem of routing in the Internet. We need to verify if the Internet has routes back to the new VLAN. (Is there any possibility that the addressing on the new VLAN is different from the addressing of the rest of your network?)
    - it could be a problem of doing NAT or PAT at the network edge and the new addresses not being properly translated.
    If you could provide a few specifics (IP addressing of the new VLAN, IP addressing of the organization network, if NAT/PAT are being done) it might help us to find answers to your problem.
    HTH
    Rick

  • What's the easiest way to create a new VLAN and then move all existing devices to it?

    One of our locations was implemented using VLAN1 as the main (native) VLAN. My goal is to create a new sub-interface on the router and then move all the existing switches (all Layer 2) into the new VLAN, without disrupting the network (and remotely). I am trying to determine the best way to proceed. Thanks.

    I wanted to shed a little more light on the situation. The "new" VLAN has actually been in existence since the network was initially setup. The network runs VTP and the new VLAN already has an interface on the router and already shows up on all the switches when you do a "sh vlan" command. We have about 10 VLANs in all. In reality, I am simply trying to migrate about 8 switches from VLAN1 (which they never should have been on) to the new VLAN. I know that I need to create an interface for the new VLAN on each of the switches and then swap the management IP to that interface. If I could connectly directly into each switch via the console port, this would be a simple task. However, the switches are in extremely remote locations with special circumstances, thus I have no physical access to them. This fact has me a little reluctant to making the changes, as we can't afford any mistakes that would potentially cause network downtime. I am looking for some guidance on exactly the steps to take to achieve my goal. Let's call the new vlan, VLAN2. During testing, I logged into a local switch that was on VLAN1 (that's where it had it's management address). It did have VLAN2-VLAN10 as well, via VTP. I created an interface for VLAN3 on the switch and then accessed it via VLAN3 to swap the main management interface from VLAN1 to VLAN2. The changes took, but I couldn't access it via VLAN2. I am assuming this is because the router still has VLAN1 listed as the native vlan and the VLAN2 IP address is still assigned to VLAN1 on the router. What would be the best way for me to make the required changes on the 8 switches that need swapped, without losing remote access? It wouldn't hurt if the network went down for 5 minutes or less, but we can't have a big outage. Thanks.

  • Was just loading indesign and cannot start it. seem to have no rights for some presets. i deinstalled and installed new, same problem. help!

    was just loading indesign and cannot start it. seem to have no rights for some presets. i deinstalled and installed new, same problem. who can help?

    Not easy if vital information is missing. Sometimes it seems like people are using the internet the first time...
    What version of Indesign?
    What OS? "Rights" sounds like Windows
    What is happening when starting it?
    If Windows, where was it installed?
    If Windows, do you have admin permissions?

  • New VLan can't talk to DHCP server

    We have just created a new vlan (172.18.1.0/24 vlan 3) on our network and we are trying to use an exsisting DHCP server (192.168.0.1 vlan 8) But the clients on the 172.18.1.0 network can't connect to this DHCP server on vlan 8. My questions are.
    1. Do we need to specify vlan 3 on the switchport that the DHCP server is plugged into?
    2. Is there something @ L3 we need to enable to pass these DHCP server messages too across these vlans?
    Has any used DHCP servers on different subnets?
    Any info would be great.

    You need to configure an IP helper on the appropriate VLAN interface(s). Routers, by default, will not forward broadcast packets. Since DHCP client messages use the destination IP address of 255.255.255.255 (all Nets Broadcast), DHCP clients will not be able to send requests to a DHCP server on a different subnet unless the DHCP/BootP Relay Agent is configured on the router. The DHCP/BootP Relay Agent will forward DHCP requests on behalf of a DHCP client to the DHCP server. The DHCP/BootP Relay Agent will append its own IP address to the source IP address of the DHCP frames going to the DHCP server. This allows the DHCP server to respond via unicast to the DHCP/BootP Relay Agent. The DHCP/BootP Relay Agent will also populate the Gateway IP address field with the IP address of the interface on which the DHCP message is received from the client. The DHCP server uses the Gateway ip address field to determine the subnet from which the DHCPDISCOVER, DHCPREQUEST, or DHCPINFORM message originates.
    See more at the following document, with configuration steps and examples:
    http://www.cisco.com/warp/public/473/100.html#configdhcpbootpciscoios

  • The spanning-tree add strange value when I create new Vlans

    Hi,
    On all switchs access, the spanning-tree add strange value when I create new Vlans from Distrib Layer,
    and no association is created with any interface with spanning-tree vlan 700, see below in this exemple,
    until I reboot the switch.
    somebody already saw this values ?
    DSFDS112#sh span sum
    Switch is in rapid-pvst mode
    Root bridge for: none
    EtherChannel misconfig guard is enabled
    Extended system ID           is enabled
    Portfast Default             is disabled
    PortFast BPDU Guard Default  is disabled
    Portfast BPDU Filter Default is disabled
    Loopguard Default            is enabled
    UplinkFast                   is disabled
    Stack port is StackPort1
    BackboneFast                 is disabled
    Configured Pathcost method used is long
    Name                   Blocking Listening Learning Forwarding STP Active
    VLAN0001                     0         0        0          3          3
    VLAN0002                     0         0        0         22         22
    VLAN0006                     0         0        0          3          3
    VLAN0007                     0         0        0          8          8
    VLAN0009                     0         0        0          4          4
    VLAN0010                     0         0        0          3          3
    VLAN0011                     0         0        0          3          3
    VLAN0012                     0         0        0          3          3
    VLAN0013                     0         0        0          3          3
    VLAN0090                     0         0        0         15         15
    VLAN0109                     0         0        0          3          3
    VLAN0200                     0         0        0          4          4
    VLAN0300                     0         0        0         26         26
    VLAN0302                     0         0        0          4          4
    VLAN0700               -   253  -1872756560  2087191206  -1872756549  2080375982
    VLAN0702               -   253  -1872756560  2087191206  -1872756549  2080375982
    VLAN0704                     0         0        0          4          4
    VLAN0710               -   253  -1872756560  2087191206  -1872756549  2080375982
    VLAN0816                     0         0        0          3          3
    VLAN0820                     0         0        0          3          3
    20 vlans               -   759  -1323302384  1966606322  -1323302237  1946160764
    DSFDS112#sh span vlan 700
    VLAN0700
      Spanning tree enabled protocol rstp
      Root ID    Priority    4796
                 Address     0008.e3ff.fcbc
                 Cost        10000
                 Port        608 (Port-channel1)
                 Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
      Bridge ID  Priority    62140  (priority 61440 sys-id-ext 700)
                 Address     885a.9213.6880
                 Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
                 Aging Time  300 sec
    Interface           Role Sts Cost      Prio.Nbr Type
    Po1                Root FWD 10000     128.608  P2p
    DSFDS112#sh run int Gi1/0/25
    Building configuration...
    Current configuration : 194 bytes
    interface GigabitEthernet1/0/25
     description Station12
     switchport access vlan 700
     switchport mode access
    end
    DSFDS112#sh span interface Gi1/0/25
    no spanning tree info available for GigabitEthernet1/0/25
    DSFDS112#sh int status interface Gi1/0/25
    Port      Name               Status       Vlan       Duplex  Speed Type
    Gi1/0/25  Station12          connected    700          full    100 10/100/1000BaseTX
    Thanks for your help,
    Regards.

    Venki,
    The ORA-00942 is okay because there is no existing object. But what stuck me is the ORA-01921 error which may indicate that this might not be a new database.
    CREATE ROLE exp_full_database
    ERROR at line 1:
    ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role name
    CREATE ROLE imp_full_database
    ERROR at line 1:
    ORA-01921: role name 'IMP_FULL_DATABASE' conflicts with another user or role name
    Are there any existing databases on this server? Have you tried to create it on other machine?I searched on Metalink too and found Doc ID: 237486.1 ORA-29807 Signalled While Creating Database using DBCA which say that eroror could be ignored. You may want to review that as well.
    Ittichai

  • New year problem? - files 'deleted'

    i open up an aw file - make changes - try to save - get a window that says file has been deleted - cannot save as either - and other funny garbled window mesages appear when i try and open other aw docs - evrything else is fine
    seems like it could be some sort of new year thing -
    any ideas what to do

    New! Re: new year problem? - files 'deleted'
    Posted: Jan 1, 2006 10:33 AM in response to: heidig
    Reply Email
    Hi Heidig,
    Welcome to the discussions and the AppleWorks Forum.
    It's unlikely that this is a "New Year's" issue. The most probable cause is a corrupted preferences file.
    Check Peggy's post here:
    http://discussions.apple.com/message.jspa?messageID=607287&ft=y&#607287
    Regards,
    Barry
    For future reference: Using the search feature can lead to a quick answer to many problems. For this one, a search, restricted to the AppleWorks forum, using "has been deleted" (without the quotes) brought up four posts on this topic, including a reference by Peggy to her User Contributed Tip, on the first page of results.

  • Multinet or new VLAN

    Company wants to move all DHCP for computers and voice to a new Windows DHCP server from Linux. Right now the DHCP pool at headquarters is 192.168.1.100 - 192.168.1.200 and there are servers on that same subnet. They want to use 192.168.3.0/24 as a new pool and ditch 192.168.1.100 - 192.168.1.100 leaving that for only servers. Below is the switch and router info.
    Company has 192.168.1.0/24 and 192.168.8.0/24 on VLAN 100 which is their access vlan at their headquarters
    SWITCHES:
     Access VLAN 100
     Voice VLAN 10
     VLAN 10
      ip address 192.168.101.254 255.255.255.0
      ip helper-address 192.168.101.3
     VLAN 100
      ip address 192.168.8.2 255.255.255.0 secondary
      ip address 192.168.1.2 255.255.255.0
     We are moving from a Linux DHCP that has two addresses:
     192.168.1.6
     192.168.101.3
    NOTE: I do not know why it has 2 addresses. All IP helpers at the remote locations point to 192.168.1.6
    ROUTER:
     Interface Gigabit0/0.100
      IP Address 192.168.1.1 255.255.255.0
      IP Address 192.168.8./1 255.255.255.0 (secondary)
    Would I just add another address to VLAN 100 (192.168.3.2) and another address to the 0/0.100 interface (192.168.3.1) to the router then an IP helper on VLAN 100 on the core switch to point to 192.168.1.21 (new DHCP server)? I'd also modify the VLAN 10 IP Helper to point to 192.168.1.21.
    Or, would it be better to create another VLAN and modify all the switchports "access" VLAN's via the appropriate Macro/individual switchport? I suppose I'd also have to add all the routing as well as a new sub interface on the router like 0/0.80 and add the new VLAN to all the trunks if this were done as well.
    Thanks in advance.

    Change the IP of VLAN 100 and the corresponding g/w address on the router, that way you don't need to move ports.
    Create another VLAN for the servers, you will need to create a sub interface for the same on the router.
    Correct, you need to specify the address of the DHCP server via 'IP Helper', as by this plan, the DHCP server will be in the server VLAN.
    Remember to add your new g/w address to your DHCP configuration.
    You don't need to change any routing!
    The interface that connects to the router needs to remain as a trunk.
    You would only need to add the new VLAN to the trunk, if you have only allowed certain VLAN's, by default all are allowed.
    Martin

  • New VLAN impact, PVST+

    Point of debate. On a LAN running PVST+, if a new VLAN is added, does the convergence impact the existing VLANs? Assume all cross-link interfaces are default trunked, carrying all VLANs.
    I've heard both that the trunked port will go through the convergence process, impacting traffic on all VLANs, and that since PVST+ uses separate STP instances per VLAN, the trunk is not impacted, just the new VLAN.
    The question seems academic until considered on a large production network, where any time lost for convergence on an existing VLAN could cause issues.

    PVST+ is Per VLAN Spanning Tree with the support for uplink fast and backbone fast.
    With that being said each VLAN runs its own spanning tree instance. By you adding a new vlan you will not have a topology change on any other vlan.
    All trunk ports will go through the STP process for that VLAN only.

Maybe you are looking for