VLAN 1 down

Hi,
My Cat6 is running on intervlan routing (L3), with Vlan 1 shutdown status (coz I don't wan to utilize VLAN 1).
But recently, need to enabled that for some unforeseen cases. But once I've enabled it, the VLAN won't come up.
Experts, any idea ??
Thanks

only can show you one of the switch trunk status..didnt managed to capture the other switch status.
SW1> (enable) show trunk
* - indicates vtp domain mismatch
# - indicates dot1q-all-tagged enabled on the port
$ - indicates non-default dot1q-ethertype value
Port Mode Encapsulation Status Native vlan
1/24 on dot1q trunking* 1
Port Vlans allowed on trunk
1/24 1
Port Vlans allowed and active in management domain
1/24 1
Port Vlans in spanning tree forwarding state and not pruned
1/24 1
hope this helps.

Similar Messages

Ip address on created Mangement VLAN shuts down 255 VLAN 1.0 subnet

My predecessor created a VLAN 255 to replace VLAN 1 as the Management VLAN. I noticed a some of the switches had there IP's on Fas0 out of band interface. To me it made more sense to put that ip address on a int vlan 255 on all the switches. As I did to my 4th Core Switch I added the ip address *.1.24 and it shut down the entire 255 vlan with affect the .1.0 subnet. I for the life of me can can't figure out what is causing the problem. It is not like any other device is using the 1.24 ip address and even if it was it should affect access to that device not all other devices on the 1.0 subnet.
The message in the log (doing the show log command) only shows interface 255 going up and down. The subnet mask is 255.255.255.0 (/24). I just put the ip in the interface again and pinged devices in the 1.0 subnet when I brought the interface back up yet I could not access any services on the 1.0 subnet from my workstations. I shut the interface again and could access services In that subnet again.

The VLAN is in the trunk. shouldn't that be enough as for as putting it in the port goes? I already have the interface shut and configured. When I unshut the entire .1.0 subnet does down. To me it's just so unlogical.

Cisco 2950 VLAN shutting down

Hi,
i have got cisco 2950T-24, in that vlan 2 has got ip address of 10.1.1.1 /24, it is up & running, now when i create vlan 3 interface & type "no shutdown", vlan 2 interface goes down, why is that so? how to i make both the interface up & running?

As others have said you are not creating a vlan , you are creating a layer 3 SVI . This is used to manage the switch only and thus you only need one address to do this , thus the switch shuts down the other SVI. To create a layer 2 vlan just do a "conf t" enter, type vlan XX where XX is the vlan number you want to create, enter . Verify with the "show vlan" command , should show the vlan you just created and it should show active .

Vlan interface down

How do figure out why? I tryed no shut down, still down...
41-Switch-1#sh int vlan 3
Vlan3 is down, line protocol is down
Hardware is EtherSVI, address is 000a.f421.e800 (bia 000a.f421.e800)
Internet address is 10.7.41.210/24
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 packets output, 0 bytes, 0 underruns
0 output errors, 1 interface resets
0 output buffer failures, 0 output buffers swapped out

Thanks for helping actually i was reading this part from book
There are no SVIs active on the MSFC-not even VLAN 1. Let's add an SVI for VLAN 20 and see what happens:
Code View: Scroll / Show All
MSFC-6509# conf t
Enter configuration commands, one per line. End with CNTL/Z.
MSFC-6509(config)# int vlan 20
MSFC-6509(config-if)# ip address 10.20.20.1 255.255.255.0
MSFC-6509(config-if)# no shut
MSFC-6509(config-if)# ^Z
MSFC-6509#
17w2d: %LINK-3-UPDOWN: Interface Vlan20, changed state to down
17w2d: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan20, changed state to down
MSFC-6509#
MSFC-6509# sho ip int brief
Interface IP-Address OK? Method Status Protocol
Vlan20 10.20.20.1 YES manual down down
The SVI is now there, but it won't come up. The SVI will not come up unless there is an active port in the VLAN in layer two. I often forget this fact and, after adding the SVIs, go off to create my VLANs only to find that none of them will come up. To illustrate the point, I'll assign an IP address to the CatOS management interface SC0, and place it in VLAN 20. This will put an active device in the VLAN:
CatOS-6509: (enable) set int sc0 20 10.20.20.20 255.255.255.0
Interface sc0 vlan set, IP address and netmask set.
Now, with something active in VLAN 20, the VLAN 20 SVI comes up in the MSFC:
Code View: Scroll / Show All
MSFC-6509# sho ip int brief
Interface IP-Address OK? Method Status Protocol
Vlan20 10.20.20.1 YES manual up up
Now i know that Sc0 management IP of Cat OS is assigned at switching side.and we can assign only 1 ip at switching side which is using CatOS right?

RSM 5302 put Vlan in down

I had a strange issue on my Catalyst WS-5500 with RSM-5302 where I had 10 Vlan configured in HSRP mode with another Catalyst redundated on the same site.
In certain condition the Vlan11 close the communication with the switch and nobody on the LAN can work anymore.
I have no log on the RSM neither in Catalyst !
The only way is to reload the RSM (both side: primary and backup) and the connectivity restart.
I think its an HSRP problem
But the priority is correct
Anyone have some idea?
Thanks a lot!

I am sorry for the late .
But It happen again :
Jun 20 07:55:23.802: %C5IP-0-MSG: slot0 %DB-0-RESTART: Waiting for restart
Jun 20 07:55:24.810: %DBUS-3-DBUSINTERR: Slot 0, Internal Error
Jun 20 07:55:27.202: %RSP-3-RESTART: cbus complex
We change already :
Chassis
RSM 5302 ( routing module)
this is the config :
Current configuration : 4854 bytes
! No configuration change since last restart
version 12.2
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
no service password-encryption
no service single-slot-reload-enable
hostname wpa-lansrv-01-cstel
boot system flash slot0:c5rsm-isv-mz.122-7c.bin
logging buffered 128000 debugging
aaa new-model
aaa authentication login default group tacacs+ local
aaa authorization exec default group tacacs+ local
aaa authorization network default group tacacs+ local
enable secret 5
username wpa-lansrv-01-cstel password 0
clock timezone MET 1
clock summer-time MET-DST recurring last Sun Mar 2:00 last Sun Oct 2:00
ip subnet-zero
ip cef
ip tftp source-interface Loopback0
ip domain-name wind-lan
ip name-server 10.154.225.101
ip name-server 10.154.225.102
interface Loopback0
ip address 10.x.x.x 255.255.255.255
interface Vlan1
description Vlan di Management
ip address 10.x.x.x 255.255.255.0
no ip redirects
standby 100 ip 10.x.x.x
standby 100 priority 200
standby 100 preempt
interface Vlan2
description Vlan di Trasporto
ip address 10.x.x.x 255.255.255.248
ip access-group 173 out
interface Vlan3
description Vlan di Trasporto
ip address 10.x.x.x 255.255.255.248
ip access-group 173 out
interface Vlan5
description Vlan Servizi
ip address 10.x.x.x 255.255.255.0
no ip redirects
standby 5 ip 10.x.x.x
standby 5 priority 200
standby 5 preempt
interface Vlan10
description Piano Terra CC
ip address 10.154.233.252 255.255.255.0
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
no ip redirects
standby 10 ip 10.x.x.x
standby 10 priority 150
standby 10 preempt
interface Vlan11
description Primo Piano CC
ip address 10.154.235.252 255.255.255.0
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
no ip redirects
standby 11 ip 10.x.x.x
standby 11 priority 200
standby 11 preempt
interface Vlan12
description Secondo Piano CC
ip address 10.x.x.x 255.255.255.0
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
no ip redirects
standby 12 ip 10.x.x.x
standby 12 priority 150
standby 12 preempt
interface Vlan20
description Piano Terra CC 2
ip address 10.154.232.252 255.255.255.0
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
ip helper-address 10.x.x.x
no ip redirects
standby 20 ip 10.x.x.x
standby 20 priority 150
standby 20 preempt
interface Vlan23
description TEST
ip address 10.x.x.x 255.255.255.0
ip helper-address 10.x.x.x
no ip redirects
standby 23 ip 10.x.x.x
standby 23 priority 200
standby 23 preempt
router ospf 69
log-adjacency-changes
passive-interface default
no passive-interface Vlan2
no passive-interface Vlan3
network 10.x.x.x 0 0.0.31.255 area 10
ip classless
ip tacacs source-interface Loopback0
no ip http server
ip ospf name-lookup
ip pim bidir-enable
Many thanks for your help

CSM VLANs down on 6513

Hi
I configured a CSM for a customer on a 6513 a couple of weeks ago and it worked fine. It's configured in routed mode with a client and server VLAN. There are no clients on the client VLAN and no servers on the server VLAN as they are all mutilpe hops away.It's not in prodcution yet as they want to do some testing.
Today I got an email saying taht it had stopped working and when the client looked at the 6500 both the client and server VLANs showed as down.
To fix it he recreated the VLANs on the CSM module and it all burst into life. Unfortunatley they don't have suslog on the 6500 so there is no record of any errors.
Has anyone seen anything like this before ?
Thanks
Pat

Hi Pat,
This problem description is too vague to comment on. Would help to know:
-version of chassis IOS and CSM code.
-relevant configuration snippet.
-for 'when looked at 6500 both client & server VLANs showed down':
    -what command(s) showed this?
    -provide actual output seen here?
-for 'it stopped working':
    -what type of traffic was it? LB or pass through?
-did this config disappear or did they do delete/recreate?
Best regards.

RVS4000 DHCP server on all but VLAN 1 broken in v1.3.2.0

I'm trying so subdivide my home network into VLANs to split Jumbo Frame capable devices from the rest.
Using the preinstalled 1.3.0.5 version I could configure this correctly. After upgrading to v1.3.2.0 the DHCP server on any VLAN (except 1) no longer responds to DHCP requests.
I have tried going back to factory defaults and rebuilding the config step by step but this did not help.
Has anyone else come across this issue?
Setup:
Port 1 (VLAN 1) - laptop 100Mbps
Port 2 (VLAN 1) - Down
Port 3 (VLAN 2) - NAS 1Gbps
Port 4 (VLAN 2) - PC 1Gbps
VLAN1 is configured as 192.168.1.0/24, VLAN2 is configured as 192.168.2.0/24.
(Originally I tried 192.168.1.0/25 and 192.168.1.128/25).

Well - my update for the day...
Fully charged last night and unplugged. Woke up to about 24 minutes usage which is ok. PUSH and used a little before retiring for the night. This morning, I left 3G and PUSH on as well as GPS. I don't live in a 3G area so until I got into the "city", I didn't have 3G. So my short trip through town did use 3G and tested for a short time(at a red light). At work I don't have 3G in my office so all day was EDGE. I do listen to the iPod both ways to work and some at work. Anyways, before leaving work I had about 4 hours usage and about 60 percent battery left. A little lower than I am used to but liveable. On the way home I made a few stops, hammering on the 3G with a passion. Before I got home, I was below the 20 percent warning...All for about 40 minutes of usage between GPS, iPod, and 3Ging.
Bottom line - the 3G experience was very power hungry. More than I can remember with my other 3G devices that I have owned.
I think Apple has some tuning to do and they probably know it now. I have no regrets as I wanted the GPS more than the 3G. Doesn't suck power? I am sure it does to some degree but I don't intend to use for constantly on door to door(even it doesn't do this). I would power via my car anyways if I did.
Basically, many have said to turn off the 3G when not being used. I agree . I wish there was a fast way to turn on and off as it is numerous clicks deep. When you know you need some "umph" to your connection, turn it on and get after it.
I am sure there will many posts similar to this one as expected.
Hope this helps.
--Mickey

Query vlan in cisco ACE

I've configured query vlan FT internface as follow:
class-map type management match-any query_VLAN
2 match protocol icmp any
policy-map type management first-match query_VLAN_MGT
class query_VLAN
    permit
interface vlan 11
description ##query vlan##
ip address 192.30.3.196 255.255.255.252
peer ip address 192.30.3.195 255.255.255.252
access-group input ANY-ANY
service-policy input query_VLAN_MGT
no shutdown
ft interface vlan 10
ip address 192.30.3.192 255.255.255.252
peer ip address 192.30.3.191 255.255.255.252
no shutdown
ft peer 1
heartbeat interval 300
heartbeat count 10
ft-interface vlan 10
query-interface vlan 11
and when I do "sh ft peer sum" I see following:
sh ft peer sum
Peer Id                      : 1
State                        : FSM_PEER_STATE_COMPATIBLE
Maintenance mode             : MAINT_MODE_OFF
FT Vlan                      : 10
FT Vlan IF State             : UP
My IP Addr                   : 192.30.3.191
Peer IP Addr                 : 192.30.3.192
Query Vlan                   : 11
Query Vlan IF State          : UP, Manual validation - please ping peer
Peer Query IP Addr           : 192.30.3.196
Heartbeat Interval           : 300
Heartbeat Count              : 10
SRG Compatibility            : COMPATIBLE
License Compatibility        : COMPATIBLE
FT Groups                    : 5
would you please advise why "Query Vlan IF State " is showing "Manual validation - please ping peer" do I need to configure anything else?
Thanks....

You don't need to configure anything further. Your config looks good.
The query interface thing can be a bit misleading. The ACE does not use the query interface until the FT vlan goes down. This is the reason why we added a etxt to request users to manually verify query interface is functioning properly as below :
"Manual validation - please ping peer"
So if you need to check if the query vlan is up, then manually ping the peer ip address. That's what the message means.
- Andrew

Guest Vlan on umnaged network

I've bought some unifi wifi access points which I want to add to our network. We use a mix of cisco and netgear switches (I'll be phasing out the netgears over time). I'd like to make a guest vlan for the wifi, I'm just not sure how is best to do it, there are some details on a possible setup here.
At the moment we have an unmanaged network so everything is using vlan1
We use 2 Cisco Pix 515e firewall's (One as backup), they go directly to a switch, then we use a Windows server for DHCP. The config for firewall (fw1) the interface that connects to a switch is:
speed 100
duplex full
nameif inside
security-level 100
ip address 192.168.135.248 255.255.192.0 standby 192.168.135.249
on the switch it connects to called sw1 (C2950-I6Q4L2-M) the port is configured like so:
interface FastEthernet0/15
switchport mode trunk
switchport nonegotiate
speed 100
duplex full
Port Gi/02 connects to the next switch which is a netgear GS748T (sw2) which then connects to various other switches
interface GigabitEthernet0/2
description Netgear GS748T
switchport trunk allowed vlan 1-4
switchport mode trunk
switchport nonegotiate
speed 1000
duplex full
flowcontrol receive desired
(There are some other vlans created, not sure what they are for yet, I'm new here!)
We've just bought a Cisco WS-C3650-24PS - sw3
I was thinking of only plugging in the wifi access points into cisco switches only and creating a Vlan - Vlan20 and only allowing Vlan20 to specific ports if this is possible?
I'm a beginner at this so the theory is there but not sure how to execute it!
I'm thinking on the firewall fw1
eth2
speed 100
duplex full
nameif guest
security-level 90
ip address 192.168.0.248 255.255.255.0 standby 192.168.0.249
on sw1 connect Gi0/2 to sw3 Gi1/1/1
config to be
switchport trunk allowed vlan 20
switchport mode trunk
switchport nonegotiate
speed 1000
duplex full
sw3 will already have vlan1 going to it as part of the unmanaged network as it is connected to another switch on another port already.
So my question is how do I setup the dhcp server on sw3 for vlan20 (192.168.0/24)
And how would both vlans get sent to the wifi access points which are patched into sw3 but without vlan 20 traffic being sent other ports which do not have the ap's connected to them? I would also like to allow vlan20 to another cisco switch.
Or if is the wrong way of doing it let me know a better solution
Apologies in advanced if this is not making much sense!

I actually use UniFi APs in our environment too, great little APs as long as you buys the Pro models (the standard ones have their short falls).
I think your PIX config looks good (it's been a while since I've touched one so I'd have to login to the 525 I have at home to confirm) Just ensure it's configured to disallow traffic from your guest VLAN to the internet network, if memory serves there's an option that's on by default to disallow traffic from a higher security if to a lower.
It may be better to configure Sw1/0/2 and Sw3/1/1/1 with all of your VLANs, if you want redundancy you can create a LAG between the two with multiple ports. If you use different links for different VLANs and down the road something happens and both of those ports become active on the same VLAN (I/E you or someone else forgets that you're using different uplinks for different VLANs) if STP isn't setup properly you'll create a loop on that VLAN potentially flooding the network with broadcast traffic.
As for the UniFi config, you configure the ports that the APs connect to as trunks, I assume you'll be managing the APs over VLAN 1 so the ports should be VL1 untagged, VLAN 20 tagged.
The UniFi Controller software is used setup and manage the APs if you haven't already done so install it. Once you have it installed you want to create two SSIDs one without VLAN tagging enabled which will be your internal SSID, and another with VLAN tagging enabled for VL20 which will be your guest SSID. This way when a client connects to the Guest SSID the AP(s) will tag their traffic VLAN 20, so on ingress to SW3 the traffic will be tagged with the correct VLAN.
The attached is a screen from my UniFi guest SSID config, you can also assign guests to a user group, which allows you to limit the bandwidth at the AP.

ACE - Query VLAN Interfaces Status

Hi,
I am wondering what the status of the query vlan interface means in the command 'show ft peer detail':
Query Vlan IF State : UP, Manual validation - please ping peer
I am pretty sure that I did not see this status when I configured query vlan last time. Current version is A2(2.3).
Unfortunately this status does not seem to be documented anywhere on CCO.
I appreciate any help!
Thanks,
Daniel

Hi Daniel,
The FT Query VLAN interface is an optional, yet very good, feature to be used when using redundant ACE modules or appliances. Without it, if the FT VLAN was to go down, the standby ACE will no longer receive FT heartbeats from the active ACE and therefore take the active role. However, if the active ACE is still running fine in the active role, then you don't want the standby ACE to take over as active because that will put them into an active/active scenario, which may lead to connectivity issues.
This is where the FT Query VLAN interface comes in. If the FT VLAN goes down, the standby ACE will notice this, but before taking the active role, it will ping it's peer IP address configured on the interface that is designated as the FT Query VLAN. If the ping is successful, then it will stay in the standby role, thereby saving you some headaches.
The status that you are seeing is the ACE's way of telling you that the interface is UP, but if you want to know if it can successfully ping the peer IP address, then you would have to manually ping the peer IP address from the CLI. The ACE does not periodically check the ping connectivity through any automatic mechanism. The automatic mechanism is only triggered by the FT VLAN going down.
Does this help?
Sean

How to exclude the monitoring (device avaibility) on an interface vlan?

Hello All,
How can i exclude the monitoring on an "intervace vlan"
My switch 3750X have many interface vlan , LMS 4.2.2 discover the device and have an automatic poller that test the reachability on the IP for these interface vlan.
And i have many Critical alarmes when the interface vlan is down, because no end host are in this vlan
(Operationaly Down, Unresponsive).
Thank you.
Alain Pernelle.

Hello pkr_legend,
Take a look at these symptoms and see if the troubleshooting steps help to resolve your issues. Please let me know.
Good luck!
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Does it need add the native vlan to allowed vlan list ?

If I confiured the port like this "
switchport trunk native vlan 10
switchport trunk allowed vlan 11,12"
does the vlan 10 allowed passing ? or it still need add vlan 10 to the allowed vlan list like "
switchport trunk native vlan 10
switchport trunk allowed vlan 10,11,12"
Thanks

Yes you can remove the native VLAN from the list, and it does prevent the native VLAN from traversing the trunk. That is, if you look at the Spanning Tree for the native VLAN, the trunk will be absent from the list of ports on the VLAN.
The question of untagged frames is a different one. There are some control protocols, particularly link-local ones, that are sent untagged, and these will traverse the trunk regardless. However, they are not considered as part of the native VLAN Spanning Tree as such.
But beware: there is a bug in earlier IOS and in all CatOS switches! If you use a non-1 VLAN as your trunk native VLAN, and you disallow it from the trunks, and there are no other ports carrying that native VLAN, then the Spanning Tree for that VLAN shut down. That is fair enough. But the bug is that the Spanning Tree for VLAN 1 also breaks down, sending your network into meltdown.
Kevin Dorrell
Luxembourg

Boadcast control in management vlan

Hi...
I faced a problem where the management vlan was down due to exessive broadcast caused by some fiber uplink going bad.
I can use udld but not sure whether it can be used where the uplink is UTP.
I am thinkung of having several mamangement vlans, instead o keeping all my switches in a single one.
Is that a good practise? Any other ideas?
Thanks.

You can enable UDLD with UTP. Creating multiple management VLANs depends on how much broadcast traffic is there within that vlan under normal circumstances, how many nodes are in the vlan, how many trunks are there, are there any hubs in use and a few other factors. It doesn't hurt to create another management vlan for management and the reason why many networks out there just have one management vlan is for simplification.
Pls. rate all helpful posts.
--Sundar

Management vlan

What are the reasons line protocol of management vlan is down ? when you check with sh int vlan1...vlan1 as management vlan

Yes, a VLAN (SVI) interface would be up only when there is atleast one active port on that VLAN (or) an active trunk that carries traffic for that VLAN. I am sure you know that if the VLAN interface isn't up then you wouldn't be able to telnet/access that IP.
HTH
Sundar

Create vlan on SRW2024

Hi guys,
I need help the proper way to create vlan on SRW2024....
i have 3 segments vlan 10,20 and 30...how to create and make sure this 3 vlan can ping each other, the proper steps, i've tried to follow the manual but have problem to understand the term using in linksys.
thank you guys

You won't be able to "ping" the vlan's from the same switch. Also, you can only setup one vlan from which the switch can be managed. This is defined under the SETUP->NETWORK SETTINGS section. Look for "Management VLAN." You'll only be able to ping the switch from ports assigned to that VLAN.
I'm betting you have no problems creating VLANs. What can be unclear is how to assign ports.
To add a port to a VLAN...
1-identify port
2-go into "VLAN Management" and then "Ports to VLAN"
3-go into the VLAN you want the port to be in (from the SELECT VLAN drop down)
4-set switch port mode to "Access" (if not already)
5-set membership to "UnTagged"
6-ensure the trunk is tagged in this VLAN
7-save
To MOVE a port to a different VLAN...
1-identify port
2-go into "VLAN Management" and then "Ports to VLAN"
3-go into the VLAN you want the port to be in (from the SELECT VLAN drop down)
4-set membership to "UnTagged"
5-save
As I've said before on this forum, I've found it is sometimes more straight forward with the srw2024 to setup a TFTP server on your PC...backup the config...edit the config...upload new config...reboot switch.

VLAN 1 down

Similar Messages

Maybe you are looking for