Adding a vlan

Hello,
We have a 4506 router/switch that we have been running 4 vlans on. I wanted to add anothe vlan, vlan 5 and configure two ports for this vlan. I created the vlan 5 and set these two ports for vlan5 but when I do a sh vlan command, their is no vlan 5 and nobody on vlan 5 gets the dhcp address range 192.168.128.0 255.255.224.0, it cannot find the dhcp server.
Any help or advice with a document or syntax useage is greatly welcome.
TIA,
Gary

how did you create the vlan?
do you have a 'VTP Server' switch running and you created it there?
do you have multiple switches and created it on a VTP Client?
if your switch is configured as a 'VTP Client', you will not be able to create vlans on it. you must create vlans on a VTP Server or VTP Transparent configured switch.
the configuration commands depend on the OS running; either CatOS or IOS:
CatOS - (must be run on VTP Server or VTP Transparent configured switch only)
switch>(enable) set vlan 5 name NEWVLAN
switch>(enable) set vlan 5 2/3-4
these commands create the vlan 5 named NEWVLAN and then adds the ports 2/3 & 2/4 to vlan 5
IOS - (must be run on VTP Server or VTP Transparent configured switch only)
(there are two ways to configure vlans; globalConfigMode or vlanDatabaseMode)
globalConfigurationMode -
switch(config)# vlan 5
switch(config-vlan)# end
switch# show vlan id 5
or
switch# show vlan
vlanDatabaseMode -
switch(config)# vlan database
switch(config-vlan)# vlan 5
switch(config-vlan)end
switch# show vlan 5
switch(config)# interface 3/1-2
switch(config-if)# switchmode access vlan 5
switch(config)# end
the above commands create a vlan with ID 5 and add the two ports, 3/1 & 3/2 to vlan 5.
be sure to check your VTP configuration on the switch you are attempting to create the new vlan on.
please see the following links for more info on 4500 vlan configuration:
IOS -
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_configuration_guide_chapter09186a00804d78fa.html#wp1020887
CatOS -
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_configuration_guide_chapter09186a008007d8ff.html
NOTE: you'll need to configure interVLAN routing if your DHCP server does not exist on vlan 5 or you need vlan 5 to communicate with other vlans.

Similar Messages

Adding a VLAN via ARD

Does/Has anyone added a VLAN to a Lab via ARD?
If so how did you do it?

I've found a workaround using terminal. It would have been nice to have the ability to do it through system preferences!
sudo ifconfig vlan1900 create
sudo ifconfig vlan1900 vlan 1900 vlandev en1
sudo ifconfig vlan1900 inet 10.0.0.1 netmask 255.255.255.224

Adding more VLANs for mapping for an H-REAP AP

Why can't I add more locally switched VLANs to the VLAN mapping table of an H-REAP AP... I have a total of 3 but as I understand it I can have a maximum of 8 locally switch H-REAP VLANs...
What abd
Basic config from command line is
interface create lme-spare 703
interface vlan lme-spare 703
interface port lme-spare 1 2
apgroup add default-group
apgroup interface-mapping add default-group 4 lme-spare
wlan apgroup nac-snmp disable default-group 4
wlan create 4 XTS testing xts-lme
wlan nac snmp disable 4
wlan interface 4 lme-spare
wlan multicast interface 4 disable
wlan broadcast-ssid disable 4
wlan radio 4 802.11g-only
wlan session-timeout 4 1800
wlan h-reap local-switching 4 enable
wlan h-reap learn-ipaddr 4 enable
wlan wmm allow 4
However, add another mapping doesn't work...
(Cisco Controller) config>ap h-REAP vlan wlan 4 703 ?
<Cisco AP> Enter the name of the Cisco AP.
(Cisco Controller) config>ap h-REAP vlan wlan 4 703 tradefloorAP1
Invalid parameter specified.
(Cisco Controller) config>
Where am I going wrong- could have couple of pointers please?

Hello Adrian,
The VLAN mapping is not taking hold because that AP is currently not servicing WLAN 4 (from the screenshot). Is this AP part of an ap group? If so, have you added wlan 4 to that AP group configuration?
If the AP is in the default-group, then it should be servicing wlan 4...
What version of WLC code and model of AP are in use?
-Patrick Croak
Wireless TAC

Adding & removing VLAN tags?

As I recall, switches will add the VLAN tag on frames entering a VLAN configured port & remove the tag once the frame exits the switch. Assuming VTP is enabled in a LAN topology because all VLAN members do not reside on the same switch, is the VLAN tag added & removed on *each* switch traversed?
Thanks for any clarification provided.

The tags are added and stripped on ingress and egress from access ports.
If a host sends a frame into a VLAN port on switch A, then the frames traverses a trunk port to switch B, then exits to a host from an access port on switch B, the TAG is applied on switch A, then stripped on switch B. THe frame keeps the tag through the trunk.
Good Luck
Scott

Adding a VLAN to MST

Hi all,
If I have a 6513 with two MST instances and I want to add a VLAN to instance one what is the best way? Does the 6513 have to be reloaded?
Thanks

Assuming that your current MST configuration is properly configured...
set spantree mst {instance} vlan {vlan}
set spantree mst config commit
should be the required command syntax on both switches. A reset is not necessary.

Adding VLAN to Po-Group and OSPF routing what is the correct way?

Hi Community,
I recently had an issue that brought down the links between a couple of switches...luckily this was done after hours and I did not save the config so was able to revert back.
The basic scope of my project is:
We are running out of IP's on the 192.168.1.0/24 sunbnet so wanted to create a seperate VLAN/Subnet for physical workstations.
He is what I orginally did;
1) On our core switch; (Switch1)
     Create the VLAN,
     VLAN interface,
     DHCP pool,
     excluded address'
2) On second switch (Switch 2)
     Add VLAN name, no interface
3) I then updated the PO-group on Switch1 with new VLAN (this brought down the link before I was able to finish my config)
    Therefore I was not able to complete the following:
          add vlan to spanning-tree or updated OSPF routing
Here is what I assume to be the correct order?
1) On Core Switch (Switch 1)
     Create VLAN
     VLAN interface
     DHCP pool
     excluded address'
     add vlan to spanning-tree
     add vlan (passive interface) and sunbet to OSPF routing
2) On Switch 2
     Add vlan name/interfaces with no ip
3) Update PO groups after the above has been configured
     Add new VLAN to Po-Group on Switch 2
     Add new VLAN to Po-Group on Switch 1
4) Last steps
     Updated specific access ports with new VLAN and test
     upon completion of testing, update all other access ports connected ot workstations with new VLAN
Questions:
Did my links go down because I added new VLAN to Po-group BEFORE updating spanning-tree and OSPF routing?
Can anyone verify the order as outlined in the section "Here is what I assume to be the correct order"

So the order in which to apply TASKS is correct?
also just to clarify the following TASK based on your comments.
Step 4- Add new VLANs to OSPF as passive interface
On Switch 1 (core)
We have this line of code
router ospf 100
router-id 192.168.1.10
log-adjacency-changes
passive-interface Vlan10
passive-interface Vlan30
passive-interface Vlan50
passive-interface Vlan500
network 192.168.0.2 0.0.0.0 area 0
network 192.168.1.10 0.0.0.0 area 0
network 192.168.30.254 0.0.0.0 area 0
network 192.168.33.254 0.0.0.0 area 0
network 192.168.51.254 0.0.0.0 area 0
network 192.168.99.5 0.0.0.0 area 0
network 192.168.200.254 0.0.0.0 area 0
TASK: OSPF - Add new VLANs(40 & 41) to OSPF as Passive Interface
******* Begin Here *********
config t
router ospf 100
passive-interface vlan40
passive-interface vlan41
!WE SHOULD ADD THIS LINE OF CODE
network 192.168.40.254 0.0.0.0 area 0
network 192.168.41.254 0.0.0.0 area 0
******* End Here *********
RESULT:
router ospf 100
router-id 192.168.1.10
log-adjacency-changes
passive-interface Vlan10
passive-interface Vlan30
passive-interface Vlan40
passive-interface Vlan41
passive-interface Vlan50
passive-interface Vlan500
network 192.168.0.2 0.0.0.0 area 0
network 192.168.1.10 0.0.0.0 area 0
network 192.168.30.254 0.0.0.0 area 0
network 192.168.33.254 0.0.0.0 area 0
network 192.168.40.254 0.0.0.0 area 0
network 192.168.41.254 0.0.0.0 area 0
network 192.168.51.254 0.0.0.0 area 0
network 192.168.99.5 0.0.0.0 area 0
network 192.168.200.254 0.0.0.0 area 0
Better??
Again thanks...your feedback have been a tremendous help!

Adding vlans to a trunk ...

[1] What is the allowed time duration between the two switches if we have added the vlans on one end of the trunk
and waiting to enter this on the other end of the trunk ?
[2] I understand if the vlans on the trunk are not the same, then there will be a problem. What would be the problem be and the reasoning behind it.
Thank you.
-SN-

I'll assume you are running transparent if you adding vlans on both ends . There is no time requirement other than you have to have the vlan that you manage the switch on both ends or otherwise you'll lock yourself out . If the vlans are not the same on both ends then the ones that are different will not be allowed across the trunk . The easiest way is to just allow everything initially then delete the vlans you don't need on the trunk one the link is up and you can manage the switch. If you are running client/server then you only have to make your changes on the server anyway.

Switch not remote manageable after adding VLAN

Hello,
I have a cisco 2960.
I've added a VLAN with a different subnet after I gave the switch it's initial IP.
Now, I can't remote manage the switch from any client on the new VLAN/subnet.
Do I have to add a route or something to the old VLAN/initial switch IP?
Thanks in advance

Hi
a 2960 is a L2 switch.
That means that there can only ever be 1 IP address configured at any 1 time after a "interface vlan x" command. the other vlans do not need IP addresses on a L2 switch to work. ie just
vlan x
name test-vlan
and that should activate the vlan on that switch if it is in VTP transparent or Server mode.
otherwise if in VTP Client mode just so
show vlan
to see if it has already that VLAN configured in the VLAN database.
The switch will only then be manageable from the VLAN with the IP address.
Thanks
fraser

Red X on Network drives and Unknown Publisher when running apps after VLAN config

We have been running the SG500-52P switches (2 switches stacked) for 2 years with No issues. We recently moved our office and added a new VoIP phone system. We had some trouble getting everything installed originally but its all working now with this one pesky problem. After putting the switches in Layer 3 mode, adding a VLAN for the phone system and setting up a route between VLAN1 (data) and VLAN2 (phones). We are now having this problem: Users are randomly getting Red X's showing disconnected network drives. There appears to be no pattern to when the disconnect happens. It can happen almost instantly after a reboot or sometimes be fine for a few days before disconnecting. If you click on the drives you can access the data but the Red X DOES NOT go away. Although when accessing some applications we get an "Unknown Publisher" message and usually the program crashes. All our Workstations are Win 7 Pro and Servers are 2008 R2. We map server and NAS drives, when the issue happens is disconnects all the mapped drives and NOT just one server.

Definitely not a good situation to be in, as you never know who will call and complain of loosing connectivity. Have you opened a ticket with TAC?
Unfortunately we don't get a lot of comments/questions on the SG series here.

Vlan config issues

I have a 6509 with a vlan 105 configure. I have also added a vlan 100. vlan 100 and 105 work for internal routing. vlan 105 workstation can get to the internet. however any vlan 100 workstation can not access the internet. A tracert from a workstation on vlan 100 stops at the 6509. attached is the 6509 config, i have included IP just because they already have changed.
any ideas? Does the port connecting to my firewall have to allow all vlan traffic? if so how do i do this.
thanks,

Hi,
Please provide more information on setup( other devices, connectivity diagram) to have a clear idea, so that we can help you.
From the config provided, i could see the following default route
ip route 0.0.0.0 0.0.0.0 10.175.105.3
What is 10.175.105.3 ? Is this your firewall / WAN router??
Also what is the need for this static route.?
ip route 10.175.100.0 255.255.255.0 10.175.105.3
10.175.100.0/24 is the subnet for vlan 100, which a directly connected network on this switch. Hence you dont need that route. Remove that route.
Finally whatever device is 10.175.105.3, please add a route in that device for vlan 100 so that traffic can reach vlan 100.
The route that you should add in 10.175.105.3 is
ip route 10.175.100.0 255.255.255.0 10.175.105.1.
Hope this helps.
-VJ

1242AG Bridge, VLAN and Multiple SSIDs

I have two buildings that I'm trying to configure a bridge in between them using 2 1242AG APs.
Building A
PCOFFICE SSID on VLAN 200 Radio G
ROOT_1 SSID on Native VLAN 1 Radio A
Root Bridge
Building B
FDAPC SSID on Native VLAN 1 Radio G
ROOT_1 SSID on Native VLAN 1 Radio A
We are using directional antenna. I know they are lined up properly because I have them both down and in front of me. I'm getting an error on the Building B AP that says "
No SSID with VLAN configured. Dot11Radio1 not started." and I'm unable to get this to work. The bridge was working before I added the VLAN and encryption/WPA information for the PCOFFICE and FDAPC SSIDs
Any assistance would be amazing. Thanks! Please see attached files for configurations. I know the switch is configured properly because I had this working before and forgot to save the damn configuration off the devices. I'm not having to do it over from scratch.

That did not work.
I've managed to fix the ROOT_1 and FDAPC... now I'm having an issue where I can attempt to connect to the PCOFFICE SSID but I'm unable to get a DHCP address from the server.
Here is the config for the AP with PCOFFICE on it and the switch.
SWITCH
interface GigabitEthernet3/2
switchport trunk allowed vlan 1,200
switchport mode trunk
interface Vlan1
ip address 192.168.3.4 255.255.255.0
interface Vlan200
ip address 192.168.30.2 255.255.255.0
ip helper-address 192.168.3.98
ip default-network 192.168.3.0
ip route 0.0.0.0 0.0.0.0 192.168.3.1
no ip http server
ACCESS POINT
version 12.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname AP1_ROOT_AP
enable secret 5 REMOVED
ip subnet-zero
no aaa new-model
dot11 vlan-name VLAN1 vlan 1
dot11 vlan-name pcCopper vlan 200
dot11 ssid PCOFFICE
   vlan 200
   authentication open
   authentication key-management wpa
   guest-mode
   wpa-psk ascii 7 REMOVED
dot11 ssid ROOT_1
   vlan 1
   authentication open
   authentication key-management wpa
   infrastructure-ssid optional
   wpa-psk ascii 7 REMOVED
dot11 network-map
dot11 arp-cache optional
power inline negotiation prestandard source
username Cisco password 7 REMOVED
username admin privilege 15 password 7 REMOVED
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption mode ciphers tkip
encryption vlan 200 mode ciphers tkip
ssid PCOFFICE
speed basic-2.0 5.5 11.0 12.0 18.0 24.0 36.0 48.0 54.0
no power client local
power client 17
power local cck 17
power local ofdm 17
channel 2462
station-role root access-point
antenna receive right
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 port-protected
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.200
encapsulation dot1Q 200
no ip route-cache
bridge-group 200
bridge-group 200 subscriber-loop-control
bridge-group 200 block-unknown-source
no bridge-group 200 source-learning
no bridge-group 200 unicast-flooding
bridge-group 200 spanning-disabled
interface Dot11Radio1
no ip address
no ip route-cache
encryption mode ciphers tkip
encryption vlan 1 mode ciphers tkip
ssid ROOT_1
dfs band 3 block
speed basic-6.0 9.0 basic-12.0 18.0 basic-24.0 36.0 48.0 54.0
no power client local
power client 11
power local 11
channel 5180
station-role root bridge
antenna receive right
antenna transmit right
interface Dot11Radio1.1
encapsulation dot1Q 1 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
interface FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
hold-queue 160 in
interface FastEthernet0.1
encapsulation dot1Q 1 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
interface FastEthernet0.200
encapsulation dot1Q 200
no ip route-cache
bridge-group 200
bridge-group 200 spanning-disabled
interface BVI1
ip address 192.168.3.241 255.255.255.0
no ip route-cache
ip default-gateway 192.168.3.1
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
control-plane
bridge 1 route ip
line con 0
line vty 0 4
login local

Cant find the vlan-membership command

I cant find the vlan-membership command on my 3700 layer 3 switch, i've searched google on whether the command has upgraded to a new syntax to no avail, i'm using GNS3 and the IOS is c3725-adventerprisek9-mz.124-25d.bin

Now I got your problem. Layer 3 switch has routed ports require ip address and can't be added in vlan.
if you want to add ports into vlan then it should be swtiched port not a routed port. to make routed port as switch port use "switchport" command under interface and use switchport acess vlan to add a port in vlan.
Further more it can communicate with VLAN1 and VLAN2 through the SVI interfaces of the VLANs (int vlan1 and int vlan2).
I hope the above info will solve your problem.

Unable to add allowed VLANs to TenGig trunk port

Hi,
I've got a ten gig interface on a 6509 running 12.2(33) configured as a trunk, but I've not been able to add any allowed VLANs as I've done before on other ten gig ports on different 6509 chassis. Am I missing something obvious?
I'm assuming that the reason I'm unable to set the encapsulation to dot1q is because the new hardware doens't support ISL, hence no need. The command to add the VLANs however doesn't get rejected, it just doesn't appear to do anything.
I've tried adding single VLANs and multiples, but no joy. Any ideas?
Here's what I've done:
SWITCH_1631(config)#default int t4/1
Interface TenGigabitEthernet4/1 set to default configuration
SWITCH_1631#sh ru int t4/12
Building configuration...
Current configuration : 65 bytes
interface TenGigabitEthernet4/12
no ip address
shutdown
end
SWITCH_1631(config)#int t4/1
SWITCH_1631(config-if)#switchport
SWITCH_1631(config-if)#switchport mode trunk
SWITCH_1631(config-if)#switchport trunk allowed vlan ?
WORD VLAN IDs of the allowed VLANs when this port is in trunking mode
add add VLANs to the current list
all all VLANs
except all VLANs except the following
none no VLANs
remove remove VLANs from the current list
SWITCH_1631(config-if)#switchport trunk allowed vlan add 700
SWITCH_1631(config-if)#
SWITCH_1631#sh vlan id 700
VLAN Name Status Ports
700 VLAN_NAME active <snip>
SWITCH_1631#sh ru int t4/1
Building configuration...
Current configuration : 74 bytes
interface TenGigabitEthernet4/1
switchport
switchport mode trunk
end

Steve,
Thanks for getting back to me. You're right that it is by default a dot1q trunk allowing all VLANs, therefore it should work for what I want to do.
Port Mode Encapsulation Status Native vlan
Gi3/39 on 802.1q trunking 1
Te4/1 on 802.1q trunking 1
Po1 on 802.1q trunking 50
Po2 on 802.1q trunking 50
Po3 on 802.1q trunking 50
Po4 on 802.1q trunking 50
Po5 on 802.1q trunking 50
Port Vlans allowed on trunk
Gi3/39 15-16,20-23,30,401,608
Te4/1 1-4094
Po1 10,13,20-21,25,30,50,52,61,70,600,700-701,950
Po2 10,20,30,50,52,61,70,600,700-701,950
Po3 10,20,30,50,61,70,600,700-701,950
Po4 10,20,30,50,61,70,600,700-701,950
Po5 2-3,10-23,25-26,30,35-36,40,50-53,56,58,61,65,70,77,101-102,145-146,155-158,401-402,600-602,608,700-701,800,950
The problem was that I've always been advised that best practise is to only allow the VLANs that are actually required on a trunk to avoid broadcasting traffic unnecessarily. I worked out what the issue was though, and it was a pretty simple one!
Once I saw that 1-4094 was allowed I tried "switchport trunk allowed vlan remove 700" which worked and left me with 1-699,701-4094.
Then I realised what the problem was trying to use the "add" command when all possible VLANs had already been added. As soon as I got rid of it and used "switchport trunk allowed vlan 700" followed by "switchport trunk allowed vlan add 701" I was back in business.
So it was a very simple issue, but thank you Steve for pointing me in the right direction and confirming that all the VLANs were already allowed!

VLANs 133-134 on Interface port-channel10 are being suspended. (Reason: Vlan is not allowed on Peer-link)

I just added 2 vlans Port-channel10 on two of my Nexus 5000's that go from the to a 6509 Catalyst switch. I get this error when I do a show log:(VLANs 133-134 on Interface port-channel10 are being suspended. (Reason: Vlan is not allowed on Peer-link) When I do a sh int trunk I see Po10 (int Eth1/3) that Vlans Err-disabled on Trunk. Another odd thing when I do an spanning tree summary neith 133 or 134 is added in to the summary? Why would spanning-tree be ignoring these two new vlans?
They are configured as so:
interface port-channel10
description "vpc 10 eth1/3 to 6506 po10 ten5/4"
switch port mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 130.,133-134,139,145,155,160-175,239,242,254,999
vpc10
What can I do to get 133 and 134 vlans to stop erroring on Port-channel 10 on both Nexus 5000's?

Firstly I should say I have not used Nexus switches so the following advice should be treated with caution.
Have you added the same vlans to the allowed vlans on your vPC peer link. That is what the error message seems to be telling you ie. they are not currently allowed.
They need to be allowed otherwise the vlans are suspended which is what is happening.
As I say I haven't used these switches so I can't say for sure if there is any downtime/disruption when you modify the allowed list but I think that is your problem from what I can see.
Jon

Spanning Tree MST per Vlan, best practice

Hi Community.
I did the following MST Spanning Tree Config
spanning-tree mst configuration
name xxxxxxx
revision1
instance 1 vlan 1, 10-20, 25, 30
So I added every Vlan to the config which we use. But every time when I add one more vlan to the config the whole network get a little outage.
I see lots of MAC Flaps on ports with two Server links and the outage is for some seconds.
Is it a better practice to add all possible Vlans to the config. So I do the config like that:
instance 1 vlan 1-4096
What you think.
Best Regards patrick

Hi,
So I added every Vlan to the config which we use. But every time when I add one more vlan to the config the whole network get a little outage.
Correct, that is normal behavior with MST.
I would just add "instance 1 vlan 1-4094" this way there is no outage when you bring up a new vlan.
HTH

Adding a vlan

Similar Messages

Maybe you are looking for