Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About soypablocr
soypablocr
Comes here often
Member since Jan 2, 2019
Feb 1 2019
Community Record
11
Posts
0
Kudos
0
Solutions
Badges
Jan 28 2019
11:54 AM
Chande made. still not working
... View more
Jan 28 2019
11:31 AM
Yes. I lives in the MX Here is the config
... View more
Jan 28 2019
11:14 AM
I can ping the phone and the phone is getting its IP address thru DHCP. But the phone is not registering to the Call Manager
... View more
Jan 28 2019
9:51 AM
I configured an MX64 with a site-to-site VPN connection. I'm able to ping my call manager from the MX but the Cisco Phone that I'm trying to setup is not registering to the Call Manager (Cisco Phone Model 8865) I also check the DHCP configuration and it looks good. The weirdest thing is that I have another Network with the same model of MX and same site-to-site VPN connectivity and same Call Manager but different model of phone (Cisco 8945) and is working fine. Both Networks and phones are located in Israel What other thing can I check?
... View more
Jan 9 2019
12:46 PM
Hi PhilipDAth Let me try to explain myself again. Currently MX1 is up and running it has IP segment 10.175.255.136/29 and the LAN IP address 10.175.255.138 interface 1 and 2 are connected to my CORE Switch connected to interface VLAN 2102, here is the configuration of the VLAN 2102 at the CORE: interface Vlan2102 no shutdown ip address 10.175.255.137/29 ip router ospf 1 area 0.0.0.1 Now I want to connect to my CORE a new MX (MX2) also connecting Interface 1 and 2 in the MX to the CORE, my question is for this new MX can I assign IP segment 10.175.255.136/29 LAN IP 10.175.255.139 and setup the ports in VLAN 2102 same as MX1 or do I need to create a new Interface VLAN and add that to the OSPF that I have MX1 belongs to a different organization and I will setup MX2 to a new organization. Also MX1 it is setup as a Hub for site-to-site VPN and I will setup MX2 the same way MX1 and MX2 will have different Public IP Addresses I'm also adding a hand writing diagram:
... View more
Jan 9 2019
5:56 AM
Hi Adam, what I’m trying to do is to connect the MX2 to my CORE Currently MX1 is connected to the Core with the values I showed in my post. My Core switch has an Interface VLAN with IP Address 10.175.255.136/29 and two ports of the MX1 are connected to it. That segment is part of a OSPF. I don’t know if I need to create another Interface VLAN for MX 2 and the segment that I’m creating added to the current OSPF. MX2 needs to be part of a different organization than MX1 but should have the same accesses. Let me know if this is a little bit clear or is more confusing. thanks
... View more
Jan 8 2019
5:51 PM
I will setup two Netowrks in the same organization and thinking of doing the LAN config as follows: MX1 LAN Segment 10.175.255.136/29 MX IP 10.175.255.138 MX2 LA Segment 10.175.255.136/29 MX IP 10.175.255.139 Am I right?
... View more
Jan 2 2019
7:53 AM
Hi I'm trying to use API to retrieve information related to CDP and LLDP I found this document but I don't know how ti implement it: Devices List the devices in a network HTTP RequestGET/networks/[networkId]/devices Parameters None Sample Request curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -H 'Content-Type: application/json' -X GET 'https://api.meraki.com/api/v0/networks/[networkId]/devices' Sample Response Successful HTTP Status: 200 [
{
"name": "My AP",
"lat": 37.4180951010362,
"lng": -122.098531723022,
"serial": "Q234-ABCD-5678",
"mac": "00:11:22:33:44:55",
"model": "MR34",
"address": "1600 Pennsylvania Ave",
"lanIp": "1.2.3.4",
"tags": " recently-added ",
"networkId": "N_24329156",
"beaconIdParams": {
"uuid": "00000000-0000-0000-0000-000000000000",
"major": 5,
"minor": 3
}
}
] Return a single device HTTP RequestGET/networks/[networkId]/devices/[serial] Parameters None Sample Request curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -H 'Content-Type: application/json' -X GET 'https://api.meraki.com/api/v0/networks/[networkId]/devices/[serial]' Sample Response Successful HTTP Status: 200 {
"name": "My AP",
"lat": 37.4180951010362,
"lng": -122.098531723022,
"serial": "Q234-ABCD-5678",
"mac": "00:11:22:33:44:55",
"model": "MR34",
"address": "1600 Pennsylvania Ave",
"lanIp": "1.2.3.4",
"tags": " recently-added ",
"networkId": "N_24329156",
"beaconIdParams": {
"uuid": "00000000-0000-0000-0000-000000000000",
"major": 5,
"minor": 3
}
} Return the uplink information for a device. HTTP RequestGET/networks/[networkId]/devices/[serial]/uplink Parameters None Sample Request curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -H 'Content-Type: application/json' -X GET 'https://api.meraki.com/api/v0/networks/[networkId]/devices/[serial]/uplink' Sample Response Successful HTTP Status: 200 [
{
"interface": "WAN 1",
"status": "Active",
"ip": "1.2.3.4",
"gateway": "1.2.3.5",
"publicIp": "123.123.123.1",
"dns": "8.8.8.8, 8.8.4.4",
"usingStaticIp": false
}
] Update the attributes of a device HTTP RequestPUT/networks/[networkId]/devices/[serial] Parameters name The name of a device tags The tags of a device lat The latitude of a device lng The longitude of a device address The address of a device moveMapMarker Whether or not to set the latitude and longitude of a device based on the new address. Only applies when lat and lng are not specified. Sample Request curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -H 'Content-Type: application/json' -X PUT --data-binary '{"name":"My AP","lat":37.4180951010362,"lng":-122.098531723022,"serial":"Q234-ABCD-5678","mac":"00:11:22:33:44:55","tags":" recently-added "}' 'https://api.meraki.com/api/v0/networks/[networkId]/devices/[serial]' Sample Response Successful HTTP Status: 200 {
"name": "My AP",
"lat": 37.4180951010362,
"lng": -122.098531723022,
"serial": "Q234-ABCD-5678",
"mac": "00:11:22:33:44:55",
"model": "MR34",
"address": "1600 Pennsylvania Ave",
"lanIp": "1.2.3.4",
"tags": " recently-added ",
"networkId": "N_24329156",
"beaconIdParams": {
"uuid": "00000000-0000-0000-0000-000000000000",
"major": 5,
"minor": 3
}
} Claim a device into a network HTTP RequestPOST/networks/[networkId]/devices/claim Parameters serial The serial of a device Sample Request curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -H 'Content-Type: application/json' -X POST --data-binary '{"serial":"Q234-ABCD-5678"}' 'https://api.meraki.com/api/v0/networks/[networkId]/devices/claim' Sample Response Successful HTTP Status: 201 {
"name": "My AP",
"lat": 37.4180951010362,
"lng": -122.098531723022,
"serial": "Q234-ABCD-5678",
"mac": "00:11:22:33:44:55",
"model": "MR34",
"address": "1600 Pennsylvania Ave",
"lanIp": "1.2.3.4",
"tags": " recently-added ",
"networkId": "N_24329156",
"beaconIdParams": {
"uuid": "00000000-0000-0000-0000-000000000000",
"major": 5,
"minor": 3
}
} Remove a single device HTTP RequestPOST/networks/[networkId]/devices/[serial]/remove Parameters None Sample Request curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -H 'Content-Type: application/json' -X POST 'https://api.meraki.com/api/v0/networks/[networkId]/devices/[serial]/remove' Sample Response Successful HTTP Status: 204 {
"name": "My AP",
"lat": 37.4180951010362,
"lng": -122.098531723022,
"serial": "Q234-ABCD-5678",
"mac": "00:11:22:33:44:55",
"model": "MR34",
"address": "1600 Pennsylvania Ave",
"lanIp": "1.2.3.4",
"tags": " recently-added ",
"networkId": "N_24329156",
"beaconIdParams": {
"uuid": "00000000-0000-0000-0000-000000000000",
"major": 5,
"minor": 3
}
} List LLDP and CDP information for a device HTTP RequestGET/networks/[networkId]/devices/[serial]/lldp_cdp Parameters timespan The timespan for which LLDP and CDP information will be fetched. Must be in seconds and less than or equal to a month (2592000 seconds). LLDP and CDP information is sent to the Meraki dashboard every 10 minutes. In instances where this LLDP and CDP information matches an existing entry in the Meraki dashboard, the data is updated once every two hours. Meraki recommends querying LLDP and CDP information at an interval slightly greater than two hours, to ensure that unchanged CDP / LLDP information can be queried consistently. Sample Request curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -H 'Content-Type: application/json' -X GET 'https://api.meraki.com/api/v0/networks/[networkId]/devices/[serial]/lldp_cdp?timespan=7200' Sample Response Successful HTTP Status: 200
... View more
© 2024 Cisco Systems, Inc.
