Cycle Port

[Jason-907]

We are having an issue with a PoE device that only seems to crop up every few days. It appears that the devices have an inherent problem that the vendor needs to fix with a firmware update. In the meantime, the workaround is to go into the switch and click the "cycle port" button. I'll end up writing a python script that will loop through the switches in my organization and cycle to ports that have a tag for the problem devices. Is there a way to cycle a port through the API?

I know I could disable and enable the port using: 

meraki.updateswitchport(apikey, serialnum, portnum, name=None, tags=None, enabled=False, 
    porttype=None, vlan=None,voicevlan=None, allowedvlans=None, poe=None, isolation=None,
    rstp=None,   stpguard=None, accesspolicynum=None, suppressprint=False)

meraki.updateswitchport(apikey, serialnum, portnum, name=None, tags=None, enabled=True, 
    porttype=None, vlan=None,voicevlan=None, allowedvlans=None, poe=None, isolation=None,
    rstp=None,   stpguard=None, accesspolicynum=None, suppressprint=False)

However, this sends alerts of changes to the switch ports whereas the "cycle port" button doesn't send any alerts. I'd like to cut down on the spam if possible as I would end up with alerts from all of our networks every morning.

[NolanHerring]

I've never been able to find an API that has cycle port option. I looked for it because I wanted to use it to reboot access points (which I ended up doing a separate python script/API call for which is the reboot API call).

So as of right now, there isn't an option for API to cycle port. Hopefully in the future they'll provide that.

[PhilipDAth]

If this is a Meraki Switch (MS) then configure a port schedule instead.

https://documentation.meraki.com/MS/Access_Control/Port_Schedules

[Jason-907]

---

@PhilipDAth wrote:

If this is a Meraki Switch (MS) then configure a port schedule instead.

---

I'll take a look at it, but I want it go off and back on immediately. It seems like this method would require the port to be down for 1/2 an hour at a minimum.

---

[PhilipDAth]

> It seems like this method would require the port to be down for 1/2 an hour at a minimum.

Correct.  You can't do it at a horrible time of the day like 2am?

[Jason-907]

---

@PhilipDAth wrote:

> It seems like this method would require the port to be down for 1/2 an hour at a minimum.

Correct.  You can't do it at a horrible time of the day like 2am?

---

No--Security cameras. What's happening is if we use the most efficient format, the cameras will lose communication with the server and ends up buffering everything until the server or camera reboots. Our camera guy just does it manually, but he was hoping we could automate. I'll test it out and just deal with the spam.

[Raphael_M]

Since the API endpoint doesn't seem to exist, have you tried adapting your script to:

• Disable the email alert that is triggered by the port status change
• Disable the port
• Enable the port
• Enable the email alert again

Of course you'll need to get the network ID for each switch but that shouldn't be a big problem.

[Jason-907]

---

@Raphael_M wrote:

Since the API endpoint doesn't seem to exist, have you tried adapting your script to:

• Disable the email alert that is triggered by the port status change
• Disable the port
• Enable the port
• Enable the email alert again

Of course you'll need to get the network ID for each switch but that shouldn't be a big problem.

---

That is a clever solution, but the alerts are set for configuration changes, not port status changes, so this wouldn't actually solve this one for me.