vlan 1003 parent vlan missing apply vlan changes failed

Technical discussions about Cisco hardware, configuration, network design and troubleshooting.

Moderator: sva

vlan 1003 parent vlan missing apply vlan changes failed

Postby accesshollywood2 on Thu Jun 24, 2010 10:54 am

Guys,

I have added the physical Interface for Vlan101, but when i try to add the logical, i get the error message "vlan 1003 parent vlan missing apply vlan changes failed". All the configurations of VTP are listed below and are correct on all 4 switches...

Any reason why i cant add a logical?

Code: Select all
SW1#show vtp status
VTP Version capable             : 1 to 3
VTP version running             : 2
VTP Domain Name                 : domain

VTP Pruning Mode                : Enabled
VTP Traps Generation            : Disabled
Device ID                       : 001e.bd95.d480
Configuration last modified by 172.27.41.5 at 3-1-93 00:03:43
Local updater ID is 10.234.52.91 on interface Vl2 (lowest numbered VLAN interface found)

Feature VLAN:
--------------
VTP Operating Mode                : Server
Maximum VLANs supported locally   : 1005
Number of existing VLANs          : 11
Configuration Revision            : 0
MD5 digest                        : 0x83 0x29 0x67 0xA1 0xB4 0x76 0xBF 0x15
                                    0x00 0x17 0xE0 0x98 0x7B 0x27 0xC2 0xBC



SW2#show vtp status
VTP Version capable             : 1 to 3
VTP version running             : 2
VTP Domain Name                 : domain
VTP Pruning Mode                : Enabled
VTP Traps Generation            : Disabled
Device ID                       : 001e.f695.8e00
Configuration last modified by 172.27.41.5 at 3-1-93 00:03:43

Feature VLAN:
--------------
VTP Operating Mode                : Client
Maximum VLANs supported locally   : 255
Number of existing VLANs          : 11
Configuration Revision            : 0
MD5 digest                        : 0x83 0x29 0x67 0xA1 0xB4 0x76 0xBF 0x15
                                    0x00 0x17 0xE0 0x98 0x7B 0x27 0xC2 0xBC

Code: Select all
SW3#sho vtp status
VTP Version capable             : 1 to 3
VTP version running             : 2
VTP Domain Name                 : domain
VTP Pruning Mode                : Enabled
VTP Traps Generation            : Disabled
Device ID                       : 001e.f695.e900
Configuration last modified by 172.27.41.5 at 3-1-93 00:03:43

Feature VLAN:
--------------
VTP Operating Mode                : Client
Maximum VLANs supported locally   : 255
Number of existing VLANs          : 11
Configuration Revision            : 0
MD5 digest                        : 0x83 0x29 0x67 0xA1 0xB4 0x76 0xBF 0x15
                                    0x00 0x17 0xE0 0x98 0x7B 0x27 0xC2 0xBC

Code: Select all
SW4#show vtp status
VTP Version capable             : 1 to 3
VTP version running             : 2
VTP Domain Name                 : domain

VTP Pruning Mode                : Enabled
VTP Traps Generation            : Disabled
Device ID                       : 001d.e5c5.d280
Configuration last modified by 172.27.41.5 at 3-1-93 00:03:43

Feature VLAN:
--------------
VTP Operating Mode                : Client
Maximum VLANs supported locally   : 255
Number of existing VLANs          : 11
Configuration Revision            : 0
MD5 digest                        : 0x83 0x29 0x67 0xA1 0xB4 0x76 0xBF 0x15
                                    0x00 0x17 0xE0 0x98 0x7B 0x27 0xC2 0xBC
accesshollywood2
 

Re: vlan 1003 parent vlan missing apply vlan changes failed

Postby Chetan Kumar on Thu Jun 24, 2010 10:55 am

Hi

VLAN Creation Fails with VLAN 1003 parent VLAN missing Error Message
    Switch#conf t
    Enter configuration commands, one per line. End with CNTL/Z.
    Switch(config)#vlan 102
    Switch(config-vlan)#name marketing
    Switch(config-vlan)#exit
    VLAN 1003 parent VLAN missing
    APPLY VLAN changes failed.
    Switch(config)#end
    Switch#
A misconfiguration on a switch can cause the configuration updates of the VTP to fail. In most cases, the problem is that the new VLAN created in the VTP server switch does not propagate to the VTP client switches, which creates host connectivity issues.

A common cause for this issue is a VTP version mismatch between the switches in a VTP domain. VTP version 1 and VTP version 2 are not interoperable on the network devices in the same VTP domain. A VTP version 2 capable network device can operate with a network device that runs VTP version 1, provided that VTP version 2 is disabled on the VTP version 2 capable network device. VTP version 2 is disabled by default. Every network device in the VTP domain must use the same VTP version. Verify the VTP version that runs on a switch. If VTP version 2 is enabled, disable it in order to resolve this issue.

Verify if the switch is configured properly for other VTP parameters:

* Verify that the switches are connected through trunk links, because VTP updates are only exchanged over trunk links.
* Verify that the VTP domain name is exactly the same on the appropriate switches. The name is case sensitive. The VTP updates are only exchanged between switches in the same VTP domain.
* Verify that the VTP password is exactly the same on all the switches in the domain. The password is case sensitive. If a password is configured, it must be configured on all switches in the domain and the password must be the same.

In case of a VTP convergence issue, where a VTP client does not update the VLAN information, the workaround is to force a VTP convergence by the creation, then the removal of a dummy VLAN on the VTP server. This increments the revision number and forces all VTP clients to update their VLAN database


http://www.cisco.com/en/US/tech/tk389/t ... l#vlan1003


Regards
Chetan Kumar
Chetan Kumar
 

Re: vlan 1003 parent vlan missing apply vlan changes failed

Postby accesshollywood2 on Thu Jun 24, 2010 10:56 am

Yeah i read that a small big ago, but all the configurations look good on all 4 switches...Same domain name, no passwords,
etc.... but i am only able to add the physical interface, not logical.....
accesshollywood2
 

Re: vlan 1003 parent vlan missing apply vlan changes failed

Postby accesshollywood2 on Thu Jun 24, 2010 10:56 am

i got it......

you have to go into the VLAN database to add it...... just cant conf t, then vlan 100...

switch# vlan database
switch (vlan) # vlan 101
accesshollywood2
 

Re: vlan 1003 parent vlan missing apply vlan changes failed

Postby Chetan Kumar on Thu Jun 24, 2010 10:57 am

Hi

VLAN Can create through VLAN Database as well as in Global Config Mode also.
I this there was issue with Vlan Database file , May be the VLAN that you create in Global config mode was not added in database file.


Regards
Chetan Kumar
Chetan Kumar
 

Re: vlan 1003 parent vlan missing apply vlan changes failed

Postby giuslar on Thu Jun 24, 2010 10:58 am

Hello,

yes you need to first create the L2 object vlan 101 in vlan database (older mode) or in configuration mode (new mode) and then later you can create the L3 object SVI interface vlan 101

vlan 1003 is a legacy vlan used for token ring and it is not supported in modern switches, probably the IOS code tried to to look for a suitable L2 object for SVI vlan 100 and tried to use vlan 1003 failing


Hope to help
Giuseppe
giuslar
 

Re: vlan 1003 parent vlan missing apply vlan changes failed

Postby Amit Singh on Thu Jun 24, 2010 10:59 am

Hi,

The common cause of this error is when VTP v2 is enabled and there is a device (or devices) on the VTP domain that does not support VTP v2.
Setting your VTP members to use VTP v1 should fix the problem.

Just in case, VTP v2 is not much different than VTP v1. The major difference is that VTP v2 introduces support for Token Ring VLANs. If you use Token
Ring VLANs, you must enable VTP V2. Otherwise, there is no reason to use VTP V2.

Cisco has depreciated the use of Vlan database in the recent IOS's on switch and you should be able to configure the vlans from Global config mode
if using the latest hardware/software.

Let me know if you have any questions.

Cheers,
Amit Singh
 

Re: vlan 1003 parent vlan missing apply vlan changes failed

Postby accesshollywood2 on Thu Jun 24, 2010 10:59 am

This fixed the issue...thank you
accesshollywood2
 


Return to Cisco Systems

Who is online

Users browsing this forum: No registered users and 6 guests

cron