Well I had a closer look at this question for 3 reasons: a. I was bored this evening, playing bridge, didn;'t have 1 good hand and always seem to be letting my partner play the contract. b. I had equipment sat around doing nothing and most importantly c. I wandered why someone from Cisco was aksing this question.
So a quick test and a. there is nothing wrong wqith having secondary addressing on a VLAN - though why you would want to do this at the moment escapes me. b. DHCP with/without an IP helpder address will respond with an address from the scope relating to the primary IP address range of a VLAN. However.... c. There appears to be one exception. If you specify a static DHCP binding of MAC to IP address and that IP address is from the scope relating to the secondary address range, the the requesting station gets an IP address from the secondary range. No we played around with DHCP on the primary and secondary VLAN as well a sbeing somewher else completely and the rule appears to be For each request provide an address from the primary VLAN Ip address range except where a static MAC-IP address is found. But why do this ? Mahesh Gupta wrote: > > Hi, > > I need some help on knowing about the config of multiple DHCP > scopes in a > single VLAN where we have primary and secondary IP addresses > defined (two > different subnets along with HSRP groups). Config on the MSFC > for the VLAN > is as :- > > ip address 10.2.0.1 255.255.255.0 secondary > > ip address 10.1.0.1 255.255.255.0 > > no ip redirects > > standby 22 ip 10.1.0.254 > > standby 23 ip 10.2.0.254 > > > > IP-helper-address and other parameters remains same as my HDCP > server is > same for both the scopes i.e. 10.2.0.1 255.255.255.0 and > 10.1.0.1 > 255.255.255.0. > > Any suggestions ...? > > Thanks, > > Mahesh > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=27389&t=27163 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
