We use a routed infrastructure so a single subnet of IP’s handed out by prizm won’t work for us. If I try to configure different networks so that I can use them to hand out different subnets for SM management I always get a failure on acceptance that the server IP must be changed. Specifically, the server route ip address (this is the drop down box that has the prizm MAC and IP address). The only way to make a different subnet is to rename that field. Rename it and on acceptance the unit is rejected saying it has to have the IP of the server in the server route ip address spot.
So the question is, does anyone out there try to use prizm to hand out management IP’s to their equipment with a routed network?
If so, what are the magic words to whiser in Prizm’s ear to allow it to use more than one defined subnet.
I have like missed something very basic but I just can’t get the acceptance to work. Creating the new subnet… no problem. Using it… big trouble.
The only workaround seems to be to create a new network for each subnet and then assign the AP’s to that instead of creating a network with subnets under it. What am I missing? Or, is the workaround how it was designed and that is the way it was meant to work?
lbergman wrote: We use a routed infrastructure so a single subnet of IP's handed out by prizm won't work for us. If I try to configure different networks so that I can use them to hand out different subnets for SM management I always get a failure on acceptance that the server IP must be changed. Specifically, the server route ip address (this is the drop down box that has the prizm MAC and IP address). The only way to make a different subnet is to rename that field. Rename it and on acceptance the unit is rejected saying it has to have the IP of the server in the server route ip address spot.
So the question is, does anyone out there try to use prizm to hand out management IP's to their equipment with a routed network?
If so, what are the magic words to whiser in Prizm's ear to allow it to use more than one defined subnet.
I have like missed something very basic but I just can't get the acceptance to work. Creating the new subnet.... no problem. Using it.... big trouble.
The only workaround seems to be to create a new network for each subnet and then assign the AP's to that instead of creating a network with subnets under it. What am I missing? Or, is the workaround how it was designed and that is the way it was meant to work?
It won't work the way you described it. I too tried to create separate subnets for each AP and ran across the same problem.
We ended up having all of the AP's on one network ie; 10.10.0.1, 2, 3 and so on, and all the SM's were assigned an ip out of a supernet IP pool of 10.10.10.0 - 10.10.13.0 We reserved the next 10 consecutive netblocks for SM IP assignment.
subnet mask of 255.255.0.0 allows all devices to talk to each other, we filter everything out at the SM's and AP except PPPoE. VLAN's will be implemented fairly soon, our network isn't that large yet (2 full clusters, 100+ radios, 3 Orthogon backhaul pairs) We are about to install 2 more clusters.
Thanks for the reply. I think we are going to create different networks for ours so we can segment those out to smaller subnets. I need to investigate further how I can assign those AP’s to the proper networks using the sdk. I think I saw that. have to go back and look.