Internal Errigal Collaboration Wiki

User Tools

Site Tools

Trace: • res-p1701
support:american_tower_-_ruckus

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
support:american_tower_-_ruckus [2019/02/05 15:02] – robriensupport:american_tower_-_ruckus [2021/06/25 10:09] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Ruckus Smart Zone ======
 +
 +==== Overview ====
 +
 +The implementation of the Ruckus technology on American Tower differs from the implementation of a traditional technology in several ways. Each Ruckus controller sends its traps to a single, centralised controller which then forwards the traps onto the Errigal. Because of this, all Ruckus traps are received from a single IP address which is the IP address of the centralised controller:
 +
 +{{ :support:ruckus_setup.jpg |}}
 +
 +
 +==== Trap Rule Implementation ====
 +
 +=== Example Varbind Values ===
 +
 +{{:support:ruckus_trap.png|}}
 +
 +=== Hub Level Logic ===
 +
 +As all traps originate from the same IP address, the only way of determining what controller the trap belongs to is by using a varbind value called ruckusSCGEventZoneName, which contains the name of the controller e.g. 284487 One Daytona, 347112 Miracle Mile Shops etc. Please note that the name of the controller in the varbind usually differs from the name in the database, in that the name in the database also has CGWF (Carrier Grade Wi-Fi) appended to the end. The trap rule searches for the controller using a GORM dynamic finder, using the name and technology Wi-Fi as the search criteria:
 +
 +
 +<code java>
 +    // Find the hub using the name
 +    hub = com.errigal.snmpmanager.knowledge.DasHub?.findByNameLikeAndTechnology("${zoneName}%", "WIFI")
 +</code>
 +
 +=== Node Level Logic ===
 +
 +Each Ruckus controller can have any number of Access Points (APs) as child elements. Ruckus is unique in that instead of using the name of the child element for alarm association as done with other technologies, the varbind value **ruckusSCGEventAPIP** is used, which is the IP address of the AP. If no AP with the specified IP address is found, the MAC address is used, which is stored in the **ruckusSCGEventAPMacAddr** varbind value:
 +
 +
 +<code java>
 +      //Search for the AP using the IP address
 +      if(apIpAddress){      
 +           networkElement = com.errigal.snmpmanager.knowledge.DasNode?.findByParentAndIpAddress(hub, apIpAddress)} 
 +
 +      //If no AP is found, we search using the MAC address
 +      if (!networkElement) {
 +             networkElement = com.errigal.snmpmanager.wrapper.NetworkElementWrapper?.findNetworkElement(hub.name, apMacAddress, false)}
 +</code>
 +
 +=== MIB Files ===
 +
 +  * RUCKUS-SCG-EVENT-MIB
 +  * RUCKUS-SCG-SYSTEM-MIB
 +  * RUCKUS-SCG-TTG-MIB
 +  * RUCKUS-SCG-WLAN-MIB
 +
 +
 +
  

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki