We were getting the same log messages on our new ex2300 switches. This is how I fixed it. I am not a Juniper engineer, so I will not go into detail about why this happens or how these changes fix the issue. I hope that someone smarter than me will chime in.
This solution worked for me, however there is not enough information here for me to say it will work for you.
The cause of my issue:
The log message appears when a device connecting to a wireless access point requests a DHCP address. This may not be the only action that generates this log message, but it consistently did for my testing. Our wireless APs connect to a trunk port with several VLANs configured for different wireless SSIDs.
My fix was to add an irb interface with a family of inet (IPv4) to interfasesirb. Then I set the l3-interface for the vlan to the irb I created. Once I did this the error messages stopped. I did not need to configure the interface for dhcp or give it a static ip address for this to work. See the examples below.
Here is an example of how our WIFI ports and vlans were configured on our ex2200's <--- This configuration works fine on the older switches.
interfaces {
ge-0/0/17 {
unit 0 {
familyethernet-switching {
port-mode trunk;
vlan {
members [ VLAN1 VLAN2 VLAN3 VLAN4 ];
}
native-vlan-id VLAN5;
}
}
}
vlan {
unit 4 {
familyinet {
address X.X.X.X/XX;
}
}
}
}
vlans {
VLAN1 {
vlan-id 1;
}
VLAN2 {
vlan-id 2;
}
VLAN3 {
vlan-id 3;
}
VLAN4 {
vlan-id 4;
l3-interface vlan.4;
}
VLAN5 {
vlan-id 5;
}
}
Here is how they were translated to enhanced layer 2 <--- This configuration caused all the same error messages you are reporting.
interfaces {
ge-0/0/42 {
native-vlan-id 5;
unit 0 {
familyethernet-switching {
interface-mode trunk;
vlan {
members [ VLAN1 VLAN2 VLAN3 VLAN4 VLAN5 ];
}
storm-controlsc;
}
}
}
irb {
unit 4 {
familyinet {
address X.X.X.X/XX;
}
}
}
}
vlans {
VLAN1 {
vlan-id 1;
}
VLAN2 {
vlan-id 2;
}
VLAN3 {
vlan-id 3;
}
VLAN4 {
vlan-id 4;
l3-interface irb.4;
}
VLAN5 {
vlan-id 5;
}
}
Here is my new EX2300 configuration <--- This configuration stopped all the same error messages you are reporting.
interfaces {
ge-0/0/42 {
native-vlan-id 5;
unit 0 {
familyethernet-switching {
interface-mode trunk;
vlan {
members [ VLAN1 VLAN2 VLAN3 VLAN4 VLAN5 ];
}
storm-controlsc;
}
}
}
irb {
unit 1 {
familyinet; <---- Added to interfaces irb
}
unit 2 {
familyinet;
}
unit 3 {
familyinet;
}
unit 4 {
familyinet {
address X.X.X.X/XX;
}
}
unit 5 {
familyinet;
}
}
}
vlans {
VLAN1 {
vlan-id 1;
l3-interface irb.1; <---- Added to each vlan
}
VLAN2 {
vlan-id 2;
l3-interface irb.2;
}
VLAN3 {
vlan-id 3;
l3-interface irb.3;
}
VLAN4 {
vlan-id 4;
l3-interface irb.4;
}
VLAN5 {
vlan-id 5;
l3-interface irb.5;
}
}