Router model MX67W is returning empty list of device ports

Mfibrahim
Comes here often

Router model MX67W is returning empty list of device ports

I'm trying to get the ports for router model MX67W using the API request:

https://api.meraki.com/api/v1/devices/{device_serial}/lldpCdp

as in the API documentation get-device-lldp-cdp but I'm getting an empty list of device ports.

Device lldpCdp: 
{}

While it is working in model MX67:

Device lldpCdp: 
{'ports': {'wan1': {'cdp': {'sourcePort': 'wan1', 'deviceId': '3456fe2a6e44', 'address': '192.168.86.5', 'portId': 'Port 2'}, 'lldp': {'sourcePort': 'wan1', 'systemName': 'Meraki MS120-8 - Main Floor Living room Switch', 'managementAddress': '192.168.86.5', 'portId': '2'}}, 'port3': {'cdp': {'sourcePort': 'port3', 'deviceId': '3456fe2a6e44', 'address': '192.168.86.5', 'portId': 'Port 1'}, 'lldp': {'sourcePort': 'port3', 'systemName': 'Meraki MS120-8 - Main Floor Living room Switch', 'managementAddress': '192.168.86.5', 'portId': '1'}}, 'port4': {'cdp': {'sourcePort': 'port4', 'deviceId': '3456fec81bbe', 'address': '192.168.86.15', 'portId': 'Port 0'}, 'lldp': {'sourcePort': 'port4', 'systemName': 'Meraki MR74 - Back Yard', 'portId': '0'}}, 'port5': {'cdp': {'sourcePort': 'port5', 'deviceId': 'a8469d1bc422', 'address': '192.168.86.11', 'portId': 'Port 0'}, 'lldp': {'sourcePort': 'port5', 'systemName': 'Meraki MR56 - LivingRoomnew', 'portId': '0'}}}, 'sourceMac': 'ac:17:c8:bb:b2:a4'}

 

Could you please advise what should I do to make it work?

7 Replies 7
RaphaelL
Kind of a big deal
Kind of a big deal

And you have confirmed ( with packet captures ) that you have devices sourcing LLDP/CDP packets on your MX67W ?

 

If so , I would suggest opening a ticket.

Also might be worth trying with the latest MX firmware version.

Hi RaphaelL, 
Thank you for your reply, how do I know that I have devices sourcing LLDP/CDP packets on my MX67W from the packet captures log?

This is part of the MX67W packet captures log:

--- Start Of Stream ---

tcpdump: verbose output suppressed, use -v[v]... for full protocol decode

listening on wan0_sniff, link-type EN10MB (Ethernet), snapshot length 262144 bytes

15:20:45.178699 IP 67.221.158.220 > 1.1.1.1: ICMP echo request, id 22530, seq 14699, length 64

15:20:45.178699 IP 67.221.158.220 > 8.8.8.8: ICMP echo request, id 22786, seq 14699, length 64

15:20:45.251074 IP 1.1.1.1 > 67.221.158.220: ICMP echo reply, id 22530, seq 14699, length 64

15:20:45.254601 IP 8.8.8.8 > 67.221.158.220: ICMP echo reply, id 22786, seq 14699, length 64

15:20:46.178699 IP 67.221.158.220 > 1.1.1.1: ICMP echo request, id 22530, seq 14700, length 64

15:20:46.178699 IP 67.221.158.220 > 8.8.8.8: ICMP echo request, id 22786, seq 14700, length 64

15:20:46.259967 IP 8.8.8.8 > 67.221.158.220: ICMP echo reply, id 22786, seq 14700, length 64

15:20:47.178699 IP 67.221.158.220 > 1.1.1.1: ICMP echo request, id 22530, seq 14701, length 64

15:20:47.178699 IP 67.221.158.220 > 8.8.8.8: ICMP echo request, id 22786, seq 14701, length 64

15:20:47.256263 IP 8.8.8.8 > 67.221.158.220: ICMP echo reply, id 22786, seq 14701, length 64

15:20:47.289867 IP 1.1.1.1 > 67.221.158.220: ICMP echo reply, id 22530, seq 14701, length 64

15:20:48.178699 IP 67.221.158.220 > 1.1.1.1: ICMP echo request, id 22530, seq 14702, length 64

15:20:48.178699 IP 67.221.158.220 > 8.8.8.8: ICMP echo request, id 22786, seq 14702, length 64

15:20:48.246359 IP 1.1.1.1 > 67.221.158.220: ICMP echo reply, id 22530, seq 14702, length 64

15:20:48.252682 IP 8.8.8.8 > 67.221.158.220: ICMP echo reply, id 22786, seq 14702, length 64

15:20:49.178699 IP 67.221.158.220 > 1.1.1.1: ICMP echo request, id 22530, seq 14703, length 64

15:20:49.178699 IP 67.221.158.220 > 8.8.8.8: ICMP echo request, id 22786, seq 14703, length 64

15:20:49.248849 IP 1.1.1.1 > 67.221.158.220: ICMP echo reply, id 22530, seq 14703, length 64

15:20:49.256052 IP 8.8.8.8 > 67.221.158.220: ICMP echo reply, id 22786, seq 14703, length 64

15:20:49.414394 IP 67.221.158.220.3111 > 8.8.8.8.443: Flags [S], seq 0, win 0, options [mss 536], length 0

15:20:49.414852 IP 67.221.158.217 > 67.221.158.220: ICMP time exceeded in-transit, length 52

RaphaelL
Kind of a big deal
Kind of a big deal

Those are ICMP requests/replies. I don't see any CDP/LLDP packets

Do you have any thoughts on why there are no CDP/LLDP packets being received?

RaphaelL
Kind of a big deal
Kind of a big deal

What firmware are you using.

 

Make sure that you have devices sending cdp/lldp first.

it's MX 17.10.2

Mfibrahim
Comes here often

Is there any other api request that can return the port count and status, for each device?

Get notified when there are additional replies to this discussion.