27.04.2013 Views

RingMaster Management Guide - Juniper Networks

RingMaster Management Guide - Juniper Networks

RingMaster Management Guide - Juniper Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Displaying Rogue Information<br />

To display rogue information, select the Monitor button on the main <strong>RingMaster</strong> Navigation Bar and<br />

click on Details in the Alarm Summary area to see the Alarms Detail window below.<br />

Each rogue is listed only once, even if multiple entries for it appear in the Alarms log. If a rogue is<br />

detected during three polling intervals, separate entries for each interval appear in the Alarms log.<br />

You can adjust selection criteria on the fault dashboard to filter an alarm list to display the following<br />

types of entries:<br />

❑ Rogue APs — Unauthorized APs on the Trapeze network.<br />

❑ Interfering APs — Devices that are not part of the Trapeze network but also are not rogues.<br />

No clients connected to these devices have been detected communicating with any network<br />

entity listed in the forwarding database (FDB) of any MX in a Mobility Domain. Although<br />

interfering devices are not connected to your network, they might be causing RF interference<br />

with AP radios.<br />

❑ Suspect APs — Devices that are not part of the Trapeze network and are suspected as rogues<br />

❑ Ad-hoc clients — Clients configured to communicate wirelessly outside of the network<br />

infrastructure. Ad-hoc clients are not necessarily malicious, but they steal bandwidth from your<br />

infrastructure users. Ad-hoc clients are further categorized into rogues and interfering devices.<br />

The word Rogue or Interfering appears in parentheses next to the word Ad-hoc.<br />

154 Detecting Rogue Devices Copyright © 2011, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!