cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
38952
Views
1
Helpful
32
Replies

DHCP Issue on VRF

Learnercisco
Level 1
Level 1

Hi Teck People

 

i am facing on strang issue in my Distribution 9600 if some body face this issue guide me please

IP phone is not getting IP Address from Cisco 96000 DHCP Server but Serve is showing the binding:

DHCP SERVER Binding:

Switch-1A#show ip dhcp binding

Bindings from all pools not associated with VRF:

IP address      Client-ID/              Lease expiration        Type       State      Interface

                Hardware address/

                User name

 

Bindings from VRF pool Telephone:

IP address      Client-ID/              Lease expiration        Type       State      Interface

                Hardware address/

                User name

172.17.30.14    01a4.b239.4805.6f       Infinite                Automatic  Active     Vlan67

Switch-1A#




DHCP Server Confguration 




ip dhcp use vrf connected

ip dhcp excluded-address vrf Telephone 172.17.30.1 172.17.30.2




ip dhcp pool TPH-67

vrf Telephone

network 172.17.30.0 255.255.255.0

default-router 172.17.30.1

option 150 instance 1 ip 172.17.50.5

option 150 instance 2 ip 172.17.50.6

lease infinite

ip dhcp snooping information option allow-untrusted

can somebody suggest

 

32 Replies 32

Hi George,

 

Thanks for reply

 

the actula vlan is 67 

As per my understanding the issue is that may be i am wrong. 

 

ARP entry is not coming into the VRF Table for specifice vlan  from Access Switch to distribution.

Access and distribution are vtp transparent. so we need to allow same vlan on trunk from access to distribution and vice versa. may be  i am wrong

 

Hello,

 

just to be sure (since the switches are in transparent mode): does Vlan 67 actually exist on both switches (sh vlan) ?

vlan exist on access and distirbution

 

distribution switch

vlan 67
name Telephone
!
vlan 911
name MGMT




access switch

vlan 67
name Telephone
!
vlan 911
name MGMT

 

Hello,

 

do you have DHCP snooping enabled on the access switch ? Better post the full running configs of both the access and distribution switches, otherwise we will keep asking questions...

check the attached config

 

Access switch and distribution cluster 1 config

 

Search access switch in distribution config

 

thannks

 

 

i didnt give u latest config just miss the following config in access switch

Access port configuration on the Access switch

 

int g1/0/1

switchport mode access

switchport access voice vlan 67

spanning-tree portfast default

 

Hello,

 

for the sake of testing, try and make the port channel part of the VRF:

 

ip vrf forwarding Telephone

thanks George for your reply

 

Portchannel in Distribution is layer 2 portchannel and same is also in Access Switch. 

So L2 Port channel will accep this

ip vrf forwarding Telephone

 

thanks

on the access switch, i do not see VLAN created, create VLAN 67 and 911 and test

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

thanks balaji.

 

let me check this also, but in that case IP Phone  mac should not bind with the VLAN Telephone DHCP.

 

thanks for your answer

Hi balaji 

configuration is correct. you can see the below output

Bindings from VRF pool Telephone:
IP address Client-ID/ Lease expiration Type State Interface
Hardware address/
User name
172.16.30.11 01a4.b239.4805.6f Jul 14 2020 12:06 PM Automatic Selecting Vlan67

 

the issue is very strange. DHCP server is showing the correct entry but the client is without IP address

---------------------------------------------------------------------------------

-------------------------------------------

Vlan Mac Address Type Ports
---- ----------- -------- -----
67 a4b2.3948.056f DYNAMIC Po22
911 bc5a.5607.414c DYNAMIC Po22
Total Mac Addresses for this criterion: 2

 

============

DHCPD: table id 3 = vrf Telephone
*Jul 14 12:10:26.167: DHCPD: interface = Vlan67
*Jul 14 12:10:26.167: DHCPD: class id 436973636f2053797374656d732c20496e632e2049502050686f6e652043502d3738323100
*Jul 14 12:10:26.167: DHCPD: FSM state change INVALID
*Jul 14 12:10:26.167: DHCPD: Workspace state changed from INIT to INVALID
*Jul 14 12:10:26.168: DHCPD: Found previous server binding
*Jul 14 12:10:26.168: DHCPD: Sending DHCPOFFER to client 01a4.b239.4805.6f (172.16.130.12).
*Jul 14 12:10:30.172: DHCPD: Reload workspace interface Vlan67 tableid 3.
*Jul 14 12:10:30.172: DHCPD: Sending notification of DISCOVER:
*Jul 14 12:10:30.172: DHCPD: htype 1 chaddr a4b2.3948.056f
*Jul 14 12:10:30.172: DHCPD: circuit id 000400432316
*Jul 14 12:10:30.172: DHCPD: table id 3 = vrf Telephone
*Jul 14 12:10:30.172: DHCPD: interface = Vlan67
*Jul 14 12:10:30.172: DHCPD: class id 436973636f2053797374656d732c20496e632e2049502050686f6e652043502d3738323100
*Jul 14 12:10:30.172: DHCPD: Sending notification of DISCOVER:
*Jul 14 12:10:30.172: DHCPD: htype 1 chaddr a4b2.3948.056f
*Jul 14 12:10:30.172: DHCPD: circuit id 000400432316
*Jul 14 12:10:30.172: DHCPD: table id 3 = vrf Telephone
*Jul 14 12:10:30.172: DHCPD: interface = Vlan67
*Jul 14 12:10:30.172: DHCPD: class id 436973636f2053797374656d732c20496e632e2049502050686f6e652043502d3738323100
*Jul 14 12:10:30.172: DHCPD: FSM state change INVALID
*Jul 14 12:10:30.172: DHCPD: Workspace state changed from INIT to INVALID
*Jul 14 12:10:30.172: DHCPD: Found previous server binding
*Jul 14 12:10:30.172: DHCPD: Sending DHCPOFFER to client 01a4.b239.4805.6f (172.16.130.12).

i have two seprate cluster for distributions. so this the second cluster and 

ip assigned to client is 172.16.130.12)

*Jul 14 12:10:30.172: DHCPD: Sending DHCPOFFER to client 01a4.b239.4805.6f (172.16.130.12).

Hello,

 

what do you mean by second cluster ? On which Vlan is that second cluster ? Simply post the full, unmodified running configurations of the devices involved.

Hello,

 

where in the access switch configuration you have posted do we see the below:

 

int g1/0/1

switchport mode access

switchport access voice vlan 67

spanning-tree portfast default

 

Are the configurations you have posted the ones of the switches actually in use, did you modify the configurations before you posted them ?

everything is same.

 

i have another Distribution cluster with same configuation.

 

dhcp event




infinite


Jul 14 08:49:32.159: DHCPD: Sending notification of DISCOVER:
*Jul 14 08:49:32.159: DHCPD: htype 1 chaddr a4b2.3948.056f
*Jul 14 08:49:32.159: DHCPD: circuit id 000400432316
*Jul 14 08:49:32.159: DHCPD: table id 3 = vrf Telephone
*Jul 14 08:49:32.159: DHCPD: interface = Vlan67
*Jul 14 08:49:32.159: DHCPD: class id 436973636f2053797374656d732c20496e632e2049502050686f6e652043502d3738323100
*Jul 14 08:49:32.159: DHCPD: Sending notification of DISCOVER:
*Jul 14 08:49:32.159: DHCPD: htype 1 chaddr a4b2.3948.056f
*Jul 14 08:49:32.159: DHCPD: circuit id 000400432316
*Jul 14 08:49:32.159: DHCPD: table id 3 = vrf Telephone
*Jul 14 08:49:32.159: DHCPD: interface = Vlan67
*Jul 14 08:49:32.159: DHCPD: class id 436973636f2053797374656d732c20496e632e2049502050686f6e652043502d3738323100
*Jul 14 08:49:32.159: DHCPD: FSM state change INVALID
*Jul 14 08:49:32.159: DHCPD: Workspace state changed from INIT to INVALID
*Jul 14 08:49:32.159: DHCPD: Found previous server binding
*Jul 14 08:49:32.159: DHCPD: Sending DHCPOFFER to client 01a4.b239.4805.6f (172.16.130.11).
*Jul 14 08:49:36.163: DHCPD: Reload workspace interface Vlan67 tableid 3.
*Jul 14 08:49:36.163: DHCPD: Sending notification of DISCOVER:
*Jul 14 08:49:36.163: DHCPD: htype 1 chaddr a4b2.3948.056f
*Jul 14 08:49:36.164: DHCPD: circuit id 000400432316
*Jul 14 08:49:36.164: DHCPD: table id 3 = vrf Telephone
*Jul 14 08:49:36.164: DHCPD: interface = Vlan67
*Jul 14

 

No arp entry and 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: