These technologies represent Switches and Routers. When these systems were initially loaded into the IDMS, there were done so as child elements of the Ruckus CGWF controllers. The reason for this is because each Ruckus CGWF site is made up of a number of Access Points (AP's), Core Routers (CR's) and Core Switches (CS's), with the AP's being Wi-Fi and the CR's/CR's being routers and switches respectively.

It is important to note that each Brocade and Mikrotik router and switch has its own IP address. American Tower requested that Errigal perform link checks against each of the Brocade and Mikrotik devices as they need to be made aware when they are unreachable. As this were child level elements, this was not possible as of the time of writing, link checks can only be performed against Controllers (Please note that the ability to ping node/remote level elements is included in the 3.5 sprint). To overcome this, all Brocade and Mikrotik systems were converted to be a controller network element type, allowing link checks to be performed.

Both technologies use the same trap rule called linkDown and linkUp. Please note that this is completely different from the Errigal linkDown/Up URL and SNMP link check process. The Brocade and Mikrotik linkDown/Up traps are sent when a specific port on the switch or router changes state. This linkDown/up trap originates from the IF-MIB.mib, which is a common MIB file and not technology specific.

• IF-MIB.mib

• FOUNDRY-SN-NOTIFICATION-MIB.mib
• FOUNDRY-SN-AGENT-MIB.mib
• FOUNDRY-SN-ROOT-MIB.mib

• Mikrotik.mib