User Tools
Writing /app/www/public/data/meta/support/extenet_-_mnet.meta failed
support:extenet_-_mnet
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| support:extenet_-_mnet [2019/12/23 11:35] – pmurphy | support:extenet_-_mnet [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== mNET Technology ====== | ||
| + | Author: Paddy Murphy | ||
| + | |||
| + | ==== Overview ==== | ||
| + | mNET is a system that allows 4G-LTE services to be provided to rural areas in the US, there is also a migration path for 5G. mNET can support standalone rural networks, private and virtual private wireless networks, network expansion and wireless roaming, integrated LTE and Wi-Fi networks and multi-carrier small cell networks. | ||
| + | |||
| + | ==== Unique Features ==== | ||
| + | The implementation of the mNET trap rule differs from traditional DAS technologies. | ||
| + | * mNET traps are received through a VPN server on the load balancer. | ||
| + | * mNET traps are received at the Controller level only | ||
| + | * Clear traps are not received. | ||
| + | * Tickets are only created for major and critical alarms. | ||
| + | * There are no waiting periods for mNET ticket creation, tickets are created instantly. | ||
| + | * A groovlet automatically clears the active alarms when a mNET ticket is created. | ||
| + | * When a mNET controller in under maintenance active alarms are not created. | ||
| + | * mNET tickets are created on the ExteNet mNET Alarm workflow. | ||
| + | |||
| + | ==== OpenVPN Server ==== | ||
| + | mNET traps are received through a VPN server installed on the ExteNet Load balancer. For more information, | ||
| + | |||
| + | Restart OpenVPN Client | ||
| + | |||
| + | sudo service openvpn start | ||
| + | | ||
| + | Check if OpenVPN service is running on load balancer | ||
| + | ps -edf | grep openvpn | ||
| + | | ||
| + | Confirm that OpenVPN service is configured correctly on load balancer; an entry should be returned for the command below | ||
| + | ifconfig tun0 | ||
| + | |||
| + | ==== mNET Trap Rule ==== | ||
| + | The following requirements have been received from ExteNet (Gevara Tali) regarding mNET traps: | ||
| + | * Tickets should be created instantly for all critical and major alarms - see mNET trap rule for list of traps that should create critical & major alarms. | ||
| + | * If a repeat major or critical trap is received a new ticket should be created for this trap. | ||
| + | * Tickets are not created for minor alarms. | ||
| + | * The interfaceTrap creates critical tickets when the varbind value interfaceState is 16 (iWlanLinkDown) or 25 (iS5S8Down) | ||
| + | * Include all mNET trap varbind values in the SNMP Trap Text field in the SNMP trap form. | ||
| + | |||
| + | |||
| + | ==== mNET auto-clear active alarm groovlet ==== | ||
| + | New mNET tickets were not been created because an existing open active alarm already existed for the mNET trap. A solution to this issue was to implement a groovlet that automatically clears the mNET active alarms when a mNET ticket is created. The cleared reason for active alarms cleared by this groovlet is ' | ||
| + | |https:// | ||
| + | |||
| + | === MIB File === | ||
| + | * EXTENET-MNET-MIB.mib | ||
Page Tools
