| Attachment | Size |
|---|---|
 secondary_scope.JPG | 81.5 KB |
I have configured a secondary scope to handle our increased growth. I'm utilizing CNR ver7.0 and since I have created this secondary scope the dhcp server hands out the routers option from the primary scope. For example:
Primary scope 192.168.1.0/24
GW: 192.168.1.1
Secondary Scope: 192.168.2.0/24
GW: 192.168.2.1
When a customer obtains an IP from secondary scope (192.168.2.2 for example) their GW address is 192.168.1.1.
On the CNR server I have the secondary scope configured to use the Attribute "Primary Subnet" of the primary scope (ex: 192.168.1.0/24). Any suggestions?
Been a long time since I used CNR (version 5.5 at least). but it sounds like you have your gateway defined in your policy, which is the same for both scopes.
The easiest way to fix this would to move the routers option to a scope-policy instead of the policy. You would need to update both scopes with this information.
In version 5.5 at least this needed to be done at the command line using syntax like so
scope-policy Policy_Name setOption routers 192.168.1.1
not sure how to do this in latest version but you should be able to figure it out from there.
in CNR world there are at least three sources for fulfulling dhcp requests
They are applied in this order
policy
scope-policy
client-policy
so if you redefine an option in scope-policy that was defined in policy the scope-policy will be used instead and so on....
Thank you I'll give that a try.
FYI, it appears that it's referred to as an "Embedded Policy" in the scope. Technicians are testing it now, I'll let you know if it works.