Hi Patrick,
I would encourage you that after creating a few VLAN's you apply the configuration, then save it using CCA, then exit out of it and run CCA again. I had this problem when having to create 9 VLAN's and CCA just has a bad habbit of retaining either old information or not following the changes you have made, so closing it and reopening it tends to get it back on track again as it redoes the "show run" command and re-learns the configuration of the system again.
Also Not sure what you mean by this:
But when I'm creating a VLAN with an ip range that is currently used by my Computer (i.e. Wifi), i'm not able to Finish the process.
I am going to go out on a LIMB here and assume that you are not doing this in the native VLAN of the UC and either have WiFi running at the same time as you are connected via Ethernet or doing the changes over WiFi, in each case "STOP" if you are doing it this way. Close CCA down, connect the ethernet cable to the UC, turn of WiFi and make sure you have a vanilla connection to the box with all adapters turned of but the Ethernet connection.
Any changes you make or do should be from the native VLAN (1 is default for data), if you have two routing paths the minute you try and apply the changes the UC will see a conflict, I am betting that if you hit "F2" when trying to apply the changes you will see the errors being spat out in teh debugging console that CCA has built into it.
Try and make all your changes with just a straight vanila connection to the UC, even have firwewalls and UAC turned off when doing it, which is another thing that makes CCA do stupid things.
Let us know how you get on.
Cheers,
David.
Cheers,
David Trad.
**When you rate a persons post, you are indicating a thank you or that it helped, but at the same time you are also helping to maintain the community spirit - You don't have to rate posts and you wont be looked down upon :) *
