Can't create Intellegent Capture

Jcuperus
Comes here often

Can't create Intellegent Capture

Hello,

 

I don't know if other people has the same issue. But when I try to make a Packet Capture for a switch port I get an error. I can fill in the information to start the capture. Then I see a screen that the capture is running but after that I get an error screen with Unknown Error.

When I then look in my Stored captures I see the capture I tried to make but it has the status Capturing, and the File Size is null bytes. The name of the Packet Capture is greyed out.

 

When I try to download the Packet Capture instead of saving it in the cloud I have the same result. 

Do other people also experience this issue?

 

Packet Capture Issue.png

7 Replies 7
alemabrahao
Kind of a big deal
Kind of a big deal

Do you have full admin rights in the organization?

If so, I suggest opening a support case.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Jcuperus
Comes here often

Yes I do have full admin rights, that was one of the reasons why the customer asked me if I could try it. I also opened a support case.

I created this post to see if other people also have the same issue.

Ryan_Miles
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Jcuperus
Comes here often

I tested this on a network with switches that run on version MS 17.2.1. And it also has some 9300 switches running on version CS17.2.1

Pasha
Comes here often

I have the same issues, and our switches are running 17.1.4

Pasha
Comes here often

I have the same issue! But when I set the output to "view output live" it works!

AlexL1
Meraki Employee
Meraki Employee

Hi Jcuperus,
Welcome to Meraki Community 🙂

 

We would like to sincerely apologize for the caused inconvenience.

 

There is known issue on our side that has been raised with our Development Team. They are actively working on a fix.

 

Workaround: using "/manage/dashboard/tcpdump" at the end.

 

New version - Change this:
https://nXXX.meraki.com/XXXXXX/manage/packet_captures/new_capture


To Old version:
https://nXXX.meraki.com/XXXXXX/manage/dashboard/tcpdump

 

If you have any questions, please don't hesitate to contact us.

 

Have a wonderful weekend ahead.

 

If you found this post helpful, please give it kudos.
If my answer solved your problem, click "accept as solution" so that others can benefit from it.
Get notified when there are additional replies to this discussion.