Supported alarms, Further reading, Sample workflows – Grass Valley iControl V.6.02 User Manual
Page 387: Supported alarms further reading
iControl
User Guide
377
Supported Alarms
All GSM alarms are supported by the iControl SNMP trap sender and can be polled via the GSM
SNMP Agent.
iControl automatically discovers devices in the system. All Densité cards have their own sub-
folders under the folder iControl, and each card’s respective sub-folder contains all the alarms
and statuses provided by this card.
The alarms for other Grass Valley (as well as third-party) solutions are visible in the GSM Alarm
Browser under descriptive category folders such as EDGE (for iC Edge alarms and statuses),
Cycling (for cycling engine alarms and statuses), and Router (for router alarms and statuses).
Additionally, other alarms related to either the Application Server itself or to generally abstract
categories appear in the GSM Alarm Browser in functional category folders like Health
monitoring (for Application Server health), Scripted alarms, and Virtual alarms.
Further Reading
• Getting Started with SNMP —
http://www.linux-mag.com/id/1054/
• Monitoring Linux Hosts with SNMP —
http://www.linux-mag.com/id/1080/
• Network Device Interrogation —
http://www.linux-mag.com/id/899
Sample Workflows
[Workflow]: Configuring SNMPv3 User Profiles in iControl
If you would like to take advantage of iControl’s support of SNMPv3 and its enhanced security
features, you will have to perform some initial tasks on the Application Server, first. These tasks
require a PuTTY client application on your client PC and network access to your Application
Server.
IMPORTANT:
• iControl’s default setting is to use SNMPv1. If you would like to use SNMPv3
and your Application Server will take on the role of SNMP agent, you must
first perform user configuration tasks.
• It is not necessary to configure user profiles or user templates if your
Application Server is polling external devices in SNMPv3 mode (that is, if your
Application Server is NOT an SNMP agent).
• Grass Valley highly recommends deleting your default user templates after
you have finished creating your user profiles. Failure to do so could pose a
security risk since the template passwords are hard-coded.