404 Error for LLDP/CDP using Postman

[Hex]

Hello,

I'm very new to using API's and I am currently fiddling with this with the purpose of trying to figure out information on connected devices on one of our remote Z3 firewalls. I can get simple things like getNetworkDevices just fine but getNetworkDeviceLldp_cdp returns a 404. I was able to successfully get the networkID and serial for this particular device using other API commands.

Anyone have any idea what I should be looking for here?

[alemabrahao]

I'm not sure if it's possible to get this information for the Z3. I'm almost sure not.

[alemabrahao]

You can try this one.

https://developer.cisco.com/codeexchange/github/repo/routetonull/getMerakiNeighbor

[ShawnHu · Accepted solution]

@Hex The endpoint getNetworkDeviceLldp_cdp reminds me that you probably were using V0 API instead of V1. Meraki dashboard API V0 has been end of support. In V1, the endpoint is getDeviceLldpCdp. 

https://developer.cisco.com/meraki/api-v1/get-device-lldp-cdp/

[Hex]

I think this may be my issue. I do have my baseUrl set to V1 but maybe i imported out of date API commands.

[ShawnHu]

Yep, that's where the 404 not found came from.

[Ryan_Miles]

I just tested this endpoint against a Z3 with a Polycom phone connected on the PoE port and I see neighbor info.

• ports:{

  • port5:{

    • lldp:{

      • sourcePort: "port5",
      • systemName: "Polycom SoundStation - Polycom VVX 311",
      • managementAddress: "172.25.90.251",
      • portId: "omitted"

      }

    }

  },
• sourceMac: "omitted"

[Ryan_Miles]

One more example of a Cisco phone on the Z3 PoE port showing both CDP and LLDP info.

{

• ports:{

  • port5:{

    • cdp:{

      • sourcePort: "port5",
      • deviceId: "SEPxxxxxxx",
      • address: "10.244.200.227",
      • portId: "Port 1"

      },
    • lldp:{

      • sourcePort: "port5",
      • systemName: "SEPxxxxxxx",
      • managementAddress: "10.244.200.227",
      • portId: "omitted:P1"

      }

    }

  },
• sourceMac: "omitted"

}