SRX Services Gateway
Highlighted
SRX Services Gateway

SRX340 DHCP wrong pool

[ Edited ]
‎02-07-2020 04:06 AM

Hello,

 

End-devices receive IP addresses from wrong DHCP pool. This situation is described here:

 

https://kb.juniper.net/InfoCenter/index?page=content&id=KB3222

 

But unfortunately using parameter requested-ip-interface-match or requested-ip-network-match doesn't change this behavior. 

 

 

root@SRX2# show system services dhcp-local-server    
group office {
    interface reth0.10;
}
group mobile {
    interface reth0.100;
}
requested-ip-interface-match;


root@SRX2# show access address-assignment 
pool office {
    family inet {
        network 192.168.4.0/24;
        range range1 {
            low 192.168.4.10;
            high 192.168.4.253;
        }
        dhcp-attributes {
            name-server {
                192.168.4.1;
            }
            router {
                192.168.4.1;
            }
        }

pool mobile {
    family inet {
        network 192.168.100.0/24;
        range range1 {
            low 192.168.100.20;
            high 192.168.100.253;
        }
        dhcp-attributes {
            name-server {
                192.168.100.1;
            }
            router {
                192.168.100.1;
            }
        }

root@SRX2# show interfaces reth0 unit 10 
description cable-network;
vlan-id 10;
family inet {
    address 192.168.4.1/24 {
        primary;
    }
    address x.x.x.x/24;
}

{primary:node1}[edit]
root@SRX2# show interfaces reth0 unit 100   
description mobile-network;
vlan-id 100;
family inet {
    address 192.168.100.1/24 {
        primary;
    }
    address y.y.y.y/24;
}

.

 Do you have any idea what else to do?

1 REPLY 1
Highlighted
SRX Services Gateway
Solution
Accepted by topic author Gabriel-
‎02-07-2020 05:11 AM

Re: SRX340 DHCP wrong pool

‎02-07-2020 04:22 AM

Ok, I fixed the issue.

 

After using the parameter:

 

requested-ip-interface-match

And commiting, restarting softly and gracefully DHCP server nothing worked better.

 

I had to manually clear BAD bindings from wrong pools.

 

I found them using the command:

 

root@SRX2# run show dhcp server binding | match reth0.100 | grep 192.168.4.    

And then cleared each binding.

Feedback