shahzebasif
asked on
wrong ip address from vlan
Hi all,
we have 2 dhcp server.
DCHP 1 (10.80.60.10)
Vlan 7
10.80.60.x
DHCP 2 (10.92.60.45)
Vlan 331
10.224.60.x
Cisco Core switch configuration.
interface Vlan7
description Staff&Fac_VLAN
ip address 10.80.60.1 255.255.252.0
ip access-group FAC_7_STU in
ip helper-address 10.80.60.10
interface Vlan331
ip address 10.224.60.1 255.255.252.0
ip helper-address 10.92.60.45
edge switch contains only Vlan 331 but the users taking ip from Vlan7.
any idea whats going worng.
we have 2 dhcp server.
DCHP 1 (10.80.60.10)
Vlan 7
10.80.60.x
DHCP 2 (10.92.60.45)
Vlan 331
10.224.60.x
Cisco Core switch configuration.
interface Vlan7
description Staff&Fac_VLAN
ip address 10.80.60.1 255.255.252.0
ip access-group FAC_7_STU in
ip helper-address 10.80.60.10
interface Vlan331
ip address 10.224.60.1 255.255.252.0
ip helper-address 10.92.60.45
edge switch contains only Vlan 331 but the users taking ip from Vlan7.
any idea whats going worng.
ASKER
yes default vlan 1 is disabled
interface Vlan1
no ip address
shutdown
cabling is fine cross checked.
interface Vlan1
no ip address
shutdown
cabling is fine cross checked.
You don't need/want an Ip helper on vlan 7 for starters. Any device on that subnet can already see the servers.
The IP helper is to let devices know where to go when not on the same subnet.
Try that first.
The IP helper is to let devices know where to go when not on the same subnet.
Try that first.
ASKER
tried that....but still taking ip 10.80.60.x
Do you have a dhcp scope for the correct subnet.
Somehow, arp messages sent to dhcp2 is going to dhcp1
Check the VLAN configuration on the ports the computers are plugged into. Make sure it is set to VLAN 331.
Check the scopes on the dhcp servers.
Somehow, arp messages sent to dhcp2 is going to dhcp1
Check the VLAN configuration on the ports the computers are plugged into. Make sure it is set to VLAN 331.
Check the scopes on the dhcp servers.
Sorry - just missed the obvious. your DHCP2 (10.92.60.45) server is not a valid address for either of those ranges. So unless that's a typo , where ever it sits it will be unable to respond to anything on another subnet.
I think we need to know more about the delivered DHCP scope on the servers and any core routing too.
You could try adding a new scope to the DHCP1 server for that range (10.224.60.1 255.255.252.0) and delivering it from there - at least as a short term test. And change the ip helper to match
interface Vlan331
ip helper-address 10.80.60.10
I think we need to know more about the delivered DHCP scope on the servers and any core routing too.
You could try adding a new scope to the DHCP1 server for that range (10.224.60.1 255.255.252.0) and delivering it from there - at least as a short term test. And change the ip helper to match
interface Vlan331
ip helper-address 10.80.60.10
ASKER
it was a switch porblem. wrong vlan was configured on it.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for shahzebasif's comment #a39627162
for the following reason:
thanks for the help
Accepted answer: 0 points for shahzebasif's comment #a39627162
for the following reason:
thanks for the help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 200 points for Akinsd's comment #a39627421
Assisted answer: 0 points for shahzebasif's comment #a39627162
for the following reason:
thats the solution
Accepted answer: 200 points for Akinsd's comment #a39627421
Assisted answer: 0 points for shahzebasif's comment #a39627162
for the following reason:
thats the solution
Check the VLAN configuration on the ports the computers are plugged into. Make sure it is set to VLAN 331.ID: 39467112
it was a switch porblem. wrong vlan was configured on it.ID: 39627162
ASKER
thanks
also did you have a check on the cabling?