Unplanned deletion of the VLAN interface

Hello everyone
Few days ago we had a planned change in our network to add a new backup link and add it to the BGP process on the router . but on doing that , the engineer decided to use an old port that was configured for VLAN 14 but wasn't being used , while , the VLAN itself , is trunked on this router through another switch and then goes out the main uplink to the rest of the network .
the problem is , once the guy deleted the config over this port ( including the part linking it to vlan14 ) , the main vlan 14 interfaces was also deleted !!
Anyone knows why did this happen ? is it a bug or something ?
sh ver
Cisco IOS Software, C3750 Software (C3750-IPSERVICES-M), Version 12.2(25)SEB4, R ELEASE SOFTWARE (fc1)
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Tue 30-Aug-05 15:47 by yenanh
ROM: Bootstrap program is C3750 boot loader
BOOTLDR: C3750 Boot Loader (C3750-HBOOT-M) Version 12.1(14r)EA1a, RELEASE SOFTWA RE (fc1)
r1.ako.corp uptime is 1 year, 51 weeks, 5 days, 19 hours, 25 minutes
System returned to ROM by power-on
System restarted at 20:34:44 NZ Wed Aug 23 2006
System image file is "flash:c3750-ipservices-mz.122-25.SEB4/c3750-ipservices-mz. 122-25.SEB4.bin"
cisco WS-C3750G-24TS (PowerPC405) processor (revision M0) with 118784K/12280K by tes of memory.
Processor board ID CAT0946Z3U5
Last reset from power-on
17 Virtual Ethernet interfaces
56 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
512K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address : 00:16:46:5B:E8:00
Motherboard assembly number : 73-7058-13
Power supply part number : 341-0045-01
Motherboard serial number : CAT094705DV
Power supply serial number : LIT093902PG
Model revision number : M0
Motherboard revision number : C0
Model number : WS-C3750G-24TS-E
System serial number : CAT0946Z3U5
Hardware Board Revision Number : 0x09
Switch Ports Model SW Version SW Image
1 28 WS-C3750G-24TS 12.2(25)SEB4 C3750-IPSERVICES-M
* 2 28 WS-C3750G-24TS 12.2(25)SEB4 C3750-IPSERVICES-M
Switch 01
Switch Uptime : 1 year, 51 weeks, 5 days, 19 hours, 12 minutes
Base ethernet MAC Address : 00:16:46:5B:E2:80
Motherboard assembly number : 73-7058-13
Power supply part number : 341-0045-01
Motherboard serial number : CAT094705HK
Power supply serial number : LIT093902VX
Model revision number : M0
Motherboard revision number : C0
Model number : WS-C3750G-24TS-E
System serial number : CAT0946Z3T2
Configuration register is 0xF
the show ver rsults are below .

Following URL will help you for the configuration and dilatation of VLAN .
http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_35_se/configuration/guide/swvlan.html

Similar Messages

  • VPLS with IP in the vlan interface

    I have this config in a Cat6500:
    l2 vfi XXX manual
    vpn id XXX
    neighbor 1.1.1.1
    interface vlan XXX
    ip addrr 2.2.2.2
    xconnect vfi XXX
    With this config I can't reach from 6500 other equipments on this vlan with vpls.
    It is ok to setup an ip address in a VLAN interface even if the interface have VPLS "xconnect" configuration?

    Hi Guys,
    I would like to put my idea only but i do't know if it is correct or not.
    but if we defice any ip address on the interface than this will help us to improve anything but will appear in the routing table of PE router and it could be a part of it's routing and MPLS which is not required.
    secondly we are trying to emulate layer2 briedge accross the VPLS backbone not the Layer 3 switch domain. than it could be possible that you configure routing accross the backbone but there is no such kind of mechanism to enable routing.
    please rate if it helps.
    Kamlesh SHarma

  • VLAN Interface Command

    Ok, I thought I had the reason for the VLAN interface command down. I thought it was either used for switch management or routing between VLANS? However, now I realized that some communication wont work with out this command which doesnt make sense. If I have a VLAN, then the switch will only switch packets to ports on the same VLAN. The only way, communication would work between VLANS is if I either enabled routing between VLANs with the VLAN Interface command, connected the switch to another multi-layer switch that did do routing between VLANS, or connected the switch to a router which routed between the VLANs.
    However, I just got this new 3550 switch in, configured the correct ports with the assigned VLANs, and the only way my cisco ip phone would work is if the VLAN Interface for my voice-ip VLAN was configured. The 3550 is connected to a 4507. Now, can someone tell my why this is? You shouldnt have to configure the VLAN Interface, right?(unless I wanted to route between VLANs, which could be done by the 4507)

    Sounds to me like you either dont have the dot1q trunk interface between your 4506 and 3550 working properly, or your 3550 is running the enhanced image which allows routing.
    It would be nice to see your config on both the 3550 and the 4500 to determine the reason. Just a stab at how it should be configured is that on your 4506, you have it running VTP server or transparent with the defined Data and Voice Vlan's. You have a port configured for trunking (which connects to the 3550). On your 3550, you have configured it as a vtp client or transparent and have verified that it has received (or if transparent VTP you have configured) the appropriate VLAN's. You than specified "interface VLAN #" or whatever number for switch management and configured the port that connects to the 4500 as a trunk. Your port connected to the port has the auxillary or voice vlan configured. If this is how your equipment is configured and it still does not work, than look for the line "ip routing" in your 3550 and negate it with "no ip routing".
    If still no worky worky, post your config.
    Cheers,

  • WLC - 4402/4 - Vlan Interface Addressing

    I currently have 7 WLCs with the same Vlan interfaces defined across all 7 controllers. Does anyone know the best practice for addressing these interfaces on each of the WLCs. I currently have each unique Vlan interface assigned with the same IP address across all 7 WLCs. This is working. Should I leave it this way or should I assign each controller with a different address for the Vlan interface?

    The controllers, assuming you have it configured as such, act as dhcp relay agents. Presumably, if the router got the wrong mac address in its arp entry, the dhcp message would be lost.
    Clients could have taken a while before getting a dhcp addr (race condition for router arp entry) and not been able to work if dhcp was required.
    That said, I've seen the controllers work with the dhcp server set to 255.255.255.255 so the ip helper addresses on the routers would pick up the requests.

  • High VLAN Interface utilization (6500/sup720)

    Can anyone tell me why a VLAN interface would show 100% utilization for a givin VLAN? This is a sup720 we're talking about.
    I understand that the bandwidth of a virtual interface is 1Gig but I thought this was more related to routing metric.
    Users were actually seeing performance issues until we changed how the servers on this particular interface were replicating. Once we did this the VLAN interface utilization went down and performance went up.
    It doesn't make sense to me that the VLAN interface would limit the actual throughput of the various ports that are mapped to it. Throughput should be related to the switch module 61xx, 65xx, 67xx and how it interfaces to the backplan and the backplan speed itself.
    Any insights would be helpful......

    If the layer 3 SVI was showing 100% that means it had a lot of traffic that was being layer 3 processed switched instead of hardware switched . Normally most traffic is hardware switched within the ASICS and never even gets passed up to that layer . What would cause this I'm not sure .

  • Ipv6 Vlan Interface EUI-64 assignation problem

    Hello, I have 2 routers 1800 series with switch modules incorporated connected with IPv6. Everything is working fine except for the problem that when I assign an IPv6 address to a Vlan (using the EUI-64 format to the switch ports), it assigns the SAME interface id (last 64 bits of the IPv6) of a fastEthernet port (FE 0/0), to the vlan, causing an error problem of duplicity:
    " c..T, overlaps with another prefix "
    Why does the EUI-64 assigns the MAC address of the FastEthernet ports instead of the ones in the switch modules?

    Thanks for the reply, but I just solved the problem. The problem was with the command IPV6 ADDRESS AUTOCONFIGURATION. This command definitely brings up a lot of trouble with VLAN ipv6 address assignation.
    After some testing I concluded that:
    1- If one interface has the IPV6 ADDRESS AUTOCONFIGURATION mode on, the interface could end up with more than one ipv6 global interface address.
    2- You cannot assign this mode to a vlan interface without getting into configuration problems.
    3- If a FastEthernet Interface has this mode on(IPV& A. A.), the router does not let you assign a global unicast address to the vlan interface, and gives the following error message:
    %IPV6-6-ADDRESS: 3FFE:C00:C18:F100:213:C4FF:FE44:4961/64 can not be configurex
    4- For the VLAN`s Interface ID you have to manually assign the link local address with the command line
    IPV6 ADDRESS FE80::1 (or any other unique link local address) LINK-LOCAL.
    This is for Vlans that are in a switch module of the same router.
    All this testing was for a Cisco router 1800 series with a switch module integrated in the router.
    Could be that this command is used for other specific occasions which I am not aware of.
    Regards,
    Grupo GTD

  • ASA 5545-X SVI/Vlan Interface

    I am looking to deploy ASA 5545-X with Layer 3 Vlan Interfaces, the device out of the box dosent let you create vlan interfaces. Is there any module available which enables to create Switch Virtual Interfaces.
    I was looking at I/O 6 ports Gigabit Ethernet card, but wanted to make sure before ordering.
    Many Thanks                  

    Hi,
    You are only able to configure Sub Interfaces for the Vlan ID on your ASA model.
    You can only configure actual Vlan interfaces with ASASM and ASA5505 model. This relates to the fact that ASA5505 has a switch module while your model does not.
    I have no expirience with the ASASM but I would imagine its similiar to the FWSM which also used Vlan interfaces as its a module in an actual larger switch/router platform.
    You can check this limitation from the Command Reference also
    interface vlan For the ASA 5505 and ASASM, to configure a VLAN interface and enter interface configuration mode, use the interface vlan command in global configuration mode. To remove a VLAN interface, use the no form of this command. interface vlan number no interface vlan number Syntax Description
    number
    Specifies a VLAN ID.
    For the ASA 5505, use an ID between 1 and 4090. The VLAN interface ID is enabled by default on VLAN 1.
    For the ASASM, use an ID between 2 to 1000 and from 1025 to 4094.
    - Jouni

  • Vlan Interface state constantly disabled

    Hi.
    I have a SF500 in layer 3 mode. I have 5 vlans (10,100,200,201,202)
    Of these 5 vlans, each one has a vlan interface configured.
    However, vlan 10 and 202 don't have an IPv4 route (which is created automatically I believe).
    I had a look and the vlan interface state is set to 'Disabled' (yes I'm using the GUI...)
    Whenever I click 'Edit', it brings up the new window, but it has a tick in the Enabled box. Unchecking and applying and then checking and applying makes no difference.  I just can't seem to change the state of the vlan interface.
    Am I missing something weird?
    Cheers.
    Andy

    Hi.
    Thanks forumers!! 
    Turns out that even thought it was assigned to an interface, the static route never appeared until the end device was connected (even if you tried to access that vlan from a different vlan).
    For example, the internal interface vlan 1 (192.168.1.254) would never have a route added until a device appeared on a vlan1 port - even if a device on a vlan2 port had access to vlan1,  it didn't recognise it as being valid.
    Many thanks for your help!
    Andrew

  • PING TO ACE VLAN INTERFACES

    Hi,
    I am not able to ping the VLAN interfaces defined on the ACE devices unless directly connected to the subnet.
    I tried options - defining Access-list,service-policy.I can ping the servers behind the ACE but i cannt ping the ACE vlan interface.
    I captured the traffic on the ACE.I cannt see any traffic on the interfaces if i ping the VLAN ip address.I can see the traffic if i am pinging the host behind the ACE.
    Is there any option available to enable icmp on the interfaces.

    In order to ping the Vlan Interface you just need management policy applied to the vlan interface.
    Class-maps used in the management-policy
    defines the source addresses from where these management accesses are allowed.
    If you can ping the interfaces from locally connected subnets but not from the remote subnets then there could be 2 reasons.
    1. Some routing issues
    2. Source IPs in Management class maps are not defined.
    Following is an example of typical management policy
    #Allow telnet & SSH from these ip addresses
    #Allow ICMP from any source
    class-map type management match-any MGMT-CLASS
    10 match protocol telnet
    20 match protocol ssh
    30 match protocol icmp any
    policy-map type management first-match MGMT-POLICY
    class MGMT-CLASS
    permit
    interface vlan 10
    ip address x.x.x.x 255.255.255.0
    service-policy input MGMT-POLICY
    no shutdown
    interface vlan 20
    ip address y.y.y.y 255.255.255.0
    service-policy input MGMT-POLICY
    no shutdown
    Syed Iftekhar Ahmed

  • 3550 VLAN Interfaces Problem

    I was setting up two VLAN interfaces for my 3550. I had two VLAN interfaces. One for VLAN 10 and one for VLAN 15. After configuring each VLAN Interface, VLAN 15 was down and wouldnt come up. VLAN 10 was up however. After issuing the no shutdown command for VLAN 15, it said VLAN 15 is not shutdown, but, when i checked the interface again, the VLAN interface was up. Now, I would think, if I had to do the no shutdown command on VLAN 15, why didnt I have to do that on the VLAN 10 interface? With switches, is the first VLAN interface automatically always up and all later VLAN interfaces automatically shut down.

    A 'feature' of all the newer Catalyst switches and newer IOS is that the logical VLAN interface will remain down until a port in that VLAN is up.
    The VTP config/status can also complicate this as a VTP client doesn't have the VLANs that the IOS config actually has because the VTP client hasn't learned the VLANs yet. In other words, the switch is in a state in which the IOS config puts a port in a VLAN that doesn't yet exist because VTP hasn't downloaded the VLAN database.
    Keep in mind that VTP requires an operating trunk and if it is 802.1q then the native VLANs must match (so a native VLAN other than 1 will not work if the VLAN database hasn't been dowloaded by VTP or has been corrupted).
    Not that you are running into the VTP issue, but in the effort of full disclosure...
    Hope that helps...

  • Loopback on vlan interfaces

    Hi there,
    do anyone know about the utility of the "loopback set" flag under the Vlan interface command. Could it help to keep a vlan in up/up state for example?
    Thanx.

    A vlan interface is indeed "virtual". Setting the loopback will have little effect.
    A vlan interface will be up/up when there is at least one member port for the vlan with an active link. A single active trunk port will suffice as well to get the interface active.
    Regards,
    Leo

  • HSRP Issues on VLAN interfaces

    We are experiencing an issue with HSRP and VLANS. We have the VLANS tracked to physical interfaces, with the default decrement value of 10.
    When we physically fail the fiber circuit (pull fiber transmit) the physical port reports down condition. The VLAN reports that it is still up. BOTH routers report that they are the active router and connectivity is lost.
    When the physical port is shut down, the failover takes place and the routers report their state as predicted.
    Any help would be greatly appreciated.
    These routers are 4506's running 12.1(19)EW code
    on WS-X4515 module.

    If there are still active ports, then I would expect the VLAN interface to stay UP on both routers. However, I would not normally expect both routers to be ACTIVE. Could it be that when you take down these physical links, that the routers lose sight of each other as far as the Hellos are concerned?
    About the "If there are still active ports" bit ... don't gorget that a trunk can also constitute an active port in this sense. So if you have go any access switches uplinked to these 4506s, the trunks will be enough to keep the VLAN interface alive.
    Remember also that HSRP has a hold time of only 9 seconds by default, whereas 802.1d Spanning Tree has a convergence time up to 50 seconds by default. So it is possible that if the link you are disconnecting is the active root port of a switch, that the two HSRP routers will lose sight of each other. In that case,they can both become active for a few seconds. Effectively, during the STP convergence the VLAN can be partitioned. It all depends on your topology.
    You are pulling only the transmit fiber. I wonder if enabling UDLD would help here.
    As Georg says, it would be useful to know a bit more about the topology and the configuration.
    Kevin Dorrell
    Luxembourg

  • MSFC - cannot ping vlan interface

    Hi,
    We have several vlans defined on the mfsc. On the msfc we could ping all the vlans interface except 1 vlan. The interface is up and just recently we weren't able to ping it. Any help is much appreciated.
    TIA.
    PF

    Hi PF,
    AFAIK, When you are pinging a particular interface stting on the MSFC the source IP would be of any other available interfaces. If you are pinging vlan 110 it will take source ip of any other available vlan interface and the destination is Vlan 110, but ACL defined on the interface doesnot have any ACE for the same so that packets will be dropped.
    Removing the ACL worked as explained above.
    regards,
    -amit singh

  • What VLAN should the management interface be in on a 4400 controller?

    Hi,
    Some documentations put the management interface on a 4400 controller into a regular tagged VLAN. But some documentations put it in an untagged Native VLAN, the tag=0. What is the difference? Which configuration is optimal?
    Thanks,
    Justin

    The answer is "it depends" :-)
    I would not say any particular config is optimal though. If you have an established VLAN for management interfaces, I would use that. However if you put the management interface in the same VLAN as your AP's, AP's find your controllers easier. Otherwise you can use DHCP to point AP's to controllers.
    I prefer to tag the frame as to which VLAN it belongs to, even if that is the same as the native VLAN.

  • Alias vlan interfaces on the ACE

    I am getting up to speed the ACE module and seeing lots of cases where an alias is configured on both, the client and server side vlan interfaces. Is this a requirement?
    Thanks..

    Hi,
    Yes it is. If you have a pair of ACEs in routed mode, you should use aliases on your VLAN interfaces.
    This VLAN address should then be used by your servers as default-gateway on the server side, and as next-hop for you upstream routers on client-side.
    This way, if the primary ACE fails, the next-hop address and default-gateway of your upstream routers and servers don't have to be changed because the IP Address remains the same.
    Take a look at following doc for configuration guidelines: http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A1/configuration/rtg_brdg/guide/vlansif.html#wp1034811
    HTH,
    Dario

Maybe you are looking for