Thank you for your reply Seth,
I don't believe that is possible… I haven't been giving any specifics about the additional subnet, except that it was said it would be able to handle some 8000 addresses.
I agree w/ you. Everything I read about multiple subnets in a single VLAN (elsewhere i.e. Cisco) says that it is not a standard best practice, NOT RECOMMENDED, but possible. I've opened a ticket w/ TAC, & I was told that the Aruba Controller (3600 v. 6.1.3.7) does NOT support secondary IP Address assignements for VLAN interfaces.
I don't know why they don’t just migrate to a new VLAN, or create a new one & pool it. My guess is that we cannot (or will not) create the VLAN & that the plan is to eventually do away w/ the old network. The hash that VLAN pooling utilizes to assign VLANs doesn't help us create a seamless migration. As it is, I don’t think anything does; we'll have to simply swap the IP Address assigned to the existing VLAN & migrate our cp-redirect-address to a new address in the new subnet & wait for users to switch.
I'm not certain if they were expecting this to be a clean, seamless, interruption-less, migration. The more & more I find out, the more inclined I'm to suggest we announce an interruption of service. I don't see anyway to implement this & test it w/o impacting users.
I'm assuming that if we add the additional network to the VLAN, the wirless controller will recognize it. ??? I also assume that clients will eventually join the new network once DHCP begins handing out addresses in that network. ??? What I haven't gotten a definative answer on yet, is whether or not clients on this new network will be able to reach the cp-redirect-address on the old network in the same VLAN. I don't know if a static route on my wireless controller may help w/ this, or if it simply will not work until we migrate off of the old network.
Thanks,