Hi Gaurav, The VLAN parameter is not mandatory. Depending on your environment you can either pass a VLAN tag / untagged one. We have updated our documents about the issue with adding same ip range across portable and public VLANs. This is punted for 4.2.1.
Thanks, SWAMY On 04/09/13 8:26 PM, "Gaurav Aradhye" <gaurav.arad...@clogeny.com> wrote: >Hi Swamy, > >As observed, if portable ip range is created with IPs overlapping with any >of the existing public ip ranges, then it gives "Entity already exists" >error while associating any portable ip from the created range. (But it >doesn't give any error while creating portable ip range in this case) > >The question is if we can't use IPs from existing VLANs, why to pass vlan >parameter while creating portable ip range? Keeping the default value >"untagged" serves the purpose and works well. I didn't get this well. > >Can you please explain me the how we can use vlan ids to while creating >portable range and still get it work correctly? > >Regards, >Gaurav
