AP Packet Capture Problem via vSZ 5.0 - ERROR: capture interface must be up

  • 1
  • Question
  • Updated 4 months ago
  • Acknowledged

When tried to capture packets from AP via vSZ5.0 controller, I got error message after clicking the Start button.  Error message "The capture interface must be up" .   How can I bring up "capture interface"?
Photo of Sam Chan

Sam Chan

  • 8 Posts
  • 0 Reply Likes

Posted 4 months ago

  • 1
Photo of Michael Brado

Michael Brado, Official Rep

  • 2589 Posts
  • 353 Reply Likes
Is this Knowledge Base Article helpful?

https://support.ruckuswireless.com/articles/000002607 
Photo of fred bred

fred bred

  • 5 Posts
  • 0 Reply Likes
Hi Sam,

Please ask this question to the SmartCell Gateway and virtual SmartCell Gateway forum. The Ruckus Cloud forum only covers the Ruckus Cloud WiFi products. Since you have a controller the other forum should be able to assist you.

The article Mike Brado sent you should answer your questions also. If you still need assistance don't hesitate to open a support case here... https://support.ruckuswireless.com/contact-us
Photo of Sam Chan

Sam Chan

  • 8 Posts
  • 0 Reply Likes

Michael, I get nowhere when click the link.  Can you email the article to me please?  Or what is the title or the articles, maybe I try to google from internet?  Thanks.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2589 Posts
  • 353 Reply Likes
Hi Sam, from the Support portal homepage, if you click KNOWLEDGE at the top, it takes you to our Knowledge Base Articles.

Article 2607 is titled:  How do I gather a Wireshark packet capture through Ruckus AP.
Photo of Dave B

Dave B, Employee

  • 5 Posts
  • 5 Reply Likes
Hi Sam,

In Smartzone 5.0, Depending on where you are attempting to start capture mode, you may need to provide the MAC address of the AP and DataPlane (DP).  If you highlight the AP in question from the Access Point list, hit the "More" drop down and begin the .pcap from there, you should be presented with options for 2.4GHz/5GHz/Wired interface, and whether to save as a local file or stream to a Wireshark endpoint. 

If you are attempting to capture from a radio interface you have turned off (if you've disabled 2.4GHz in your environment for example) it may throw the error you are describing.