Front page TBA from Marketing Starter Kit
Table of Contents Before you start... 3... 3 Activity 1 Current Network Device Status... 4 Activity 2 Node Voltage Monitoring... 5 Activity 3 Personnel Device Report Battery status/tag status... 6 Activity 4 Sending Node Up/Down notifications to MinePhones... 6 Rev B 2
Before you start In order to view meaningful data and use cases, this Starter Kit requires you to have completed the MinePhone Communications and Tracking Starter Kits, as the Starter Kit relies on setup and configuration done in these Starter Kits. If you have not completed these starter kits, go to the following URLs to download the kits. Please note: the MinePhone Communications Starter Kit requires the purchase of MinePhones. Tracking Starter Kit: http://downloads.minesite.com.au/releases/training/starter%20kits/03_skt_tracking_starter_kit/ MinePhone Communications Starter Kit: http://downloads.minesite.com.au/releases/training/starter%20kits/03_skt_minephone_communicati ons/ MinePhone Communications Hardware Order #: SKT-MP ($990) The Starter Kit introduces you to the various monitoring facilities available in the ICA. The ICA gives you the facilities to monitor your network, infrastructure and devices in real time, as well as the ability to produce historical reporting data about the same. The data gathered by monitoring these elements is used to create meaningful visualisations of the information in MineDash and the Network Console. This information can then be used by system rules to trigger alarms when there are any outages or issues. These alarms can then be sent as notifications to the MinePhone and/or email address of relevant personnel. This starter kit does not cover the monitoring and event notification of business rules, e.g.: Tracking rules AC Power Tag monitoring DPM events Trip Cycle events Data Logger parameter rules Unassigned ICCLs rules. These rules are covered in the relevant starter kits, e.g. Tracking, MinePhone communications, etc. Rev B 3
The ICA can monitor and create notifications on the following: Network devices: o MST Network Devices up / down status, port status, device configuration diagnostics, device voltage, SNMP agent status. o Network Links monitoring and status display only, for network link events the Node Port Status event is used. o MST Appliances (e.g. Voice Head-End) up / down status. Non MST IP Infrastructure: o Switches and Access Points from other vendors - node up / down status, port status. o Signs Sign status (including status of the associated Access Point). o Exciters, cameras, fixed phones, fixed tags, etc. up / down status. Mobile devices: o Phones battery status, distress button press. o Tags battery status, distress button press. o Mobile nodes battery status, node up / down status. Proximity System diagnostics. We will now go through a series of exercises to introduce you to the various monitoring capabilities of the ICA. Activity 1 Current Network Device Status Both the Network Console and the MineDash Network tab allow us to visualise basic current network device status. To open the Network Console, browse to http://10.20.0.5/network/. 1. In the Positioned Elements section of the Network Console (on the right-hand side), type in the name of your WAP (South Tunnel Portal). 2. Click on the WAP, and the information frame on the right hand side will update to show information about your AP and its connections and paths. 3. Under the Monitoring section, you should see that the AP is being monitored by the ICA, and the current firmware version of the device. It also shows the last time a tag was read. 4. Now go to the NS50 (SUBSTN 4), and take a look at the Wireless Connections section. You will see a list of all the clients currently connected to this AP. If you have the MinePhones setup as per the MinePhone Communications SKT, you may see some of them listed here. Rev B 4
5. If the APs are configured for Link Discovery (using LLDP), you should see a green line connecting the WAP to the NS50. The link will change to orange if it goes down. 6. Any active alarms will be displayed in this panel, and the icon for the device will change colour. From ICA v 2.2.2 onwards this will reflect the severity of the alarm: a. No alarm = green b. Info = blue c. Warning = yellow d. Critical = orange. Activity 2 Node Voltage Monitoring Let s setup the voltage monitoring rule to see how this is notified in MineDash. In the Admin Console: 1. Go to Events and System Rules> System Rules 2. Select the SNMP Voltage Monitoring rule 3. Set this rule as on site 4. Add the NS50 Radio 1 (SUBSTN 4) to the list of monitored devices. 5. Ensure Critical is selected in the severity of generated alarm dropdown 6. Click Save Note: The voltage threshold for this rule is defined in a configuration file that can be found here: /usr/local/fusion/runtime/etc/com.mst.fusion.runtime.event.cfg.the default threshold is 45V. Our SKT power supply is around 19V 23V, so we will expect this rule to trigger an alarm. Keep in mind that this rule relies on the NS50 running firmware version 2.26.16 or later. To view this rule in action: 1. Open MineDash, and go to the Network view. a. Notice how this AP is now orange b. Click on the AP and then on the Warning link to see the details of the alarm. 2. Go to the Alarms tab and select Alarm History from the secondary navigation dropdown. You can filter by System Rules, and you should see the SNMP VOLTAGE THRESHOLD BROKEN notification. You can acknowledge the alarm, but because the condition is still in place (power supply voltage < 45V), the alarm status will stay OPEN, and the icon will stay orange. 3. If you have Administrator level privileges, you are also allowed to close the alarm. This should generally only be done if the condition no longer applies, but the system is not able to Rev B 5
automatically close the alarm. This happens, for example, when an Access Point is permanently removed. We know the voltage condition is not going to change with our starter kit, so after completing this activity you can remove this alarm by marking it as not on-site in the Admin Console. Activity 3 Personnel Device Report Battery status/tag status The ICA is able to monitor and report on the battery status of your mobile devices, e.g. ICCL cap lamps, tags, mesh nodes and MinePhones. We can configure battery thresholds and set up alarms to provide notifications to control room operators and MinePhone users, via email and/or MinePhone text messages. We can also run reports on the battery status of the personnel devices (ICCL cap lamps, tags and MinePhones). To view a report on the battery status of your personnel devices: 1. Go to the Reports tab in MineDash 2. Select Birt Reports > Personnel Device Reports in the secondary navigation dropdown 3. Set the Minimum Battery Level as All, and the Maximum Battery Level as Medium to get a report of all the personnel currently carrying a device with a low or medium battery level (or battery status unknown). 4. Note the Starter Kit data set does not have any pre-populated personnel with a low or medium battery level device. If you leave any of the MinePhones to run down their batteries, the associated personnel will be listed in this report. Activity 4 Sending Node Up/Down notifications to MinePhones The ICA can monitor your Access Points, and provide notifications and alarms when they go down. In this exercise we will take the WAP off the network, and configure the ICA to deliver a notification of the event to a MinePhone. If you are currently accessing the network wirelessly via the WAP, your computer will be disconnected from the network when the WAP is disconnected. In order to monitor the event in MineDash, it is recommended that you connect to the NS50 via Ethernet on Port 7 instead. If you have completed the Network Configuration Starter Kit, you will need to change your Port 7 back to a trunk port before you can connect to that port via Ethernet. Rev B 6
Before disconnecting the WAP, we need to set up the notification set that will determine who is notified, and how, where there is an issue. We then assign this notification set to our rules. To create the notification set, using the Admin Console: 1. Go to Local entities > Entity groups. 2. Create an Entity Group called On-Site Support Staff, and add the following persons to that group: a. Mike Leff b. Scot Frier 3. Go to System > Notification sets 4. Click Add 5. Name the set On-Site Support Staff 6. Select On-Site Support Staff from the Entity Group dropdown 7. Click Save. In a real-life situation, you can also enter email addresses into the notification set if you want emails to be sent, too. The ICA should be setup with the details of an SMPT server and user account for email to be delivered. To allocate the notification sets to our monitoring-related rules: 1. Go to Events and Rules > System Rules 2. Click on Node Monitoring 3. From the Notification Set dropdown, select On-Site Support Staff 4. Click Save. Once these have been set up, ensure your laptop is connected to your NS50 via Ethernet, and disconnect your WAP from the Network. Within a few minutes of disconnecting the WAP, you should get a notification text message on the MinePhones linked to the users in our notification set (Mike Leff and Scot Frier). Rev B 7
Let s see what happens when the WAP comes back online. 1. Log into MineDash, and go to the Active Critical Alarms page. The South Tunnel Portal node will be listed as being down. The alarm is still unacknowledged and also not closed yet. 2. Reconnect the WAP, and wait a few moments for the ICA to pick up on this. Notice how the South Tunnel Portal node down alarm is no longer on the Active Critical page. You can still find it in the Alarm History page. Notice as well that the alarm is closed, but still unacknowledged. It will remain this way until an operator with the required privileges acknowledges the alarm. The MinePhones will also have received a text message notification when the node came back up. Rev B 8
Notes Rev B 9