Problem between Cisco 891F-K9 router DHCP and one third party device

[Kekun]

Hi,

In short, my problem consists in one of my devices not receiving DHCP provided by the router. Here is an explanation of the device I'm trying to connect :

It is called "Acurite Access", which is some kind of access point used to receive a wifi signal from an outdoor thermometer. The device itself cannot be configured whatsoever, which means no manual IP addressing. It must receive DHCP from the router in which it is plugged via an ethernet cable or it cannot be accessed nor used. It was intended to work in a "plug and play" fashion on home routers, with which it works well. On the Cisco 891F-K9 router, however, it just doesn't want to recieve DHCP no matter what I try.

EDIT: Any Ideas of what I could try to get it to work? I saw another post from someone saying the acurite access wouldn't work if plugged into a catalyst switch but works perfectly plugged in an unmanaged switch.

The Acurite support said that port 80 must be active and that Mac Address filtering must be disabled for it to work (and that it needs DHCP, that there's no other way). As far as I know, Mac Address filtering is not supported on this router and setting up NAT on the WAN interface and vlan used for the network should take care of port 80 since every other device (computers / cellphones) already has access to the internet.

when the acurite access is plugged, the console shows the interface going up and down every few seconds. It just doesn't want to stay up.

*Jun 8 16:44:48.542: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to down
*Jun 8 16:44:49.550: %LINK-3-UPDOWN: Interface GigabitEthernet2, changed state to up
*Jun 8 16:44:50.550: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to up
*Jun 8 16:45:15.178: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to down
*Jun 8 16:45:16.186: %LINK-3-UPDOWN: Interface GigabitEthernet2, changed state to up
*Jun 8 16:45:17.186: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to up

The device appears in the MAC address table : 

24c8.6exx.xxxx Dynamic 1 GigabitEthernet2  --> This is the MAC address of the acurite device

Here is the current config : 

Router#sh run
Building configuration...

Current configuration : 2152 bytes
!
! Last configuration change at 17:26:33 UTC Mon Jun 8 2020
!
version 15.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router
!
boot-start-marker
boot-end-marker
!
!
no logging console
!
no aaa new-model
!
!
!
!
!
!
!
!
!
!

!
ip dhcp excluded-address 192.168.1.1
!
ip dhcp pool ferme
network 192.168.1.0 255.255.255.0
dns-server      ---You don't need to know that---
default-router 192.168.1.1
!
!
ip dhcp class ferme
!
!
ip cef
no ipv6 cef
!
!
!
!
!
multilink bundle-name authenticated
!
!
!
!
!
!
!
license udi pid C891F-K9 sn XXXXXXXXXXX
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface BRI0
no ip address
encapsulation hdlc
shutdown
isdn termination multidrop
!
interface FastEthernet0
no ip address
shutdown
duplex auto
speed auto
!
interface GigabitEthernet0
no ip address
!
interface GigabitEthernet1
no ip address
!
interface GigabitEthernet2
no ip address
!
interface GigabitEthernet3
no ip address
!
interface GigabitEthernet4
no ip address
!
interface GigabitEthernet5
no ip address
!
interface GigabitEthernet6
no ip address
!
interface GigabitEthernet7
no ip address
!
interface GigabitEthernet8
description Internet
ip address dhcp
ip nat outside
ip virtual-reassembly in
duplex auto
speed auto
!
interface Vlan1
ip address pool ferme
ip broadcast-address 192.168.1.255
ip nat inside
ip virtual-reassembly in
!
interface Async3
no ip address
encapsulation slip
!
router rip
network 192.168.1.0
!
ip forward-protocol nd
no ip http server
no ip http secure-server
!
!
ip nat inside source list 1 interface GigabitEthernet8 overload
ip route 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xxx
!
!
access-list 1 permit 192.168.1.0 0.0.0.255
!
control-plane
!
!
mgcp behavior rsip-range tgcp-only
mgcp behavior comedia-role none
mgcp behavior comedia-check-media-src disable
mgcp behavior comedia-sdp-force disable
!
mgcp profile default
!
!
!
!
!
!
!
line con 0
no modem enable
line aux 0
line 3
modem InOut
speed 115200
flowcontrol hardware
line vty 0 4
login
transport input none
!
scheduler allocate 20000 1000
!
!
end

Thanks in advance for taking the time to help a noob

[Georg Pauwen]

Hello,

assign a static IP address to Vlan 1:

interface Vlan1
--> ip address 192.168.1.1 255.255.255.0
ip broadcast-address 192.168.1.255
ip nat inside
ip virtual-reassembly in

[Kekun]

Unfortunately, assigning a static IP to vlan 1 did not solve the issue. I restarted the DHCP server using on the router

no service dhcp

service dhcp

I then unplugged the ethernet cable that goes to my computer and replugged it to make sure the DHCP was still operational and it worked flawlessly.

I also power-cycled the Acurite device and reset it to factory defaults but alas... still nothing.

At first, I thought it was necessary to set the VLAN's IP to the pool that was to be used but it still works for everything else with a static IP so thank you for suggesting this nonetheless :)

[kruel0001]

Try hard coding the the switchport to 10/Full or 100/Full.  I've seen a good number of HVAC devices not negotiate properly and need a hard coded port.

[Georg Pauwen · Accepted solution]

Hello,

which port on the 891 is the Acurite connected to ? Configure that port with:

interface GigabitEthernet4
no ip address

--> spanning-tree portfast

[Kekun]

Hi,
Thank you very much, this instantly solved the issue. There also was no need to change the speed nor duplex settings on the interface. By the way, the Acurite device is connected to GigabitEthernet2 to make sure it is clear to anyone who might have a similar issue.

Have a nice day and thanks again :)