0. Monitoring Your Automation Infrastructure
Using the TOP Server SNMP Driver Presenter: Boyce Baine, Sr. Applications Engineer
Welcome to today’s presentation, Monitoring your automation infrastructure using the TOP Server SNMP Driver. My name is Boyce Baine and I’m one of the Applications Engineers here at software toolbox. I will be your presenter today. <CLICK>

1. Agenda TOP Server Introduction What is SNMP? SNMP Driver Overview
How can TOP Server help monitor my infrastructure?
What is SNMP?
SNMP Driver Overview
Overview of SNMP
Overview of Driver settings & configuration
Testing your configuration
Q & A plus other Available Resources
Today we will give you a brief overview of what TOP Server is and how it can help monitor the infrastructure. We will then have a high-level introduction to the basics of SNMP. We will also cover the basics of the driver and how it is configured followed by testing your communications. Finally we will give you links to other helpful resources before opening the floor to your questions. Now that we know where we are going, let’s begin. <CLICK>

2. What is TOP Server?
First, for those of you who may not have seen or used TOP Server previously, TOP Server is a Data Acquistion or I/O Server. (click)
It allows your Client Software connect using OPC DA, Suitelink, iFix native interface or DDE. These can be used individually or in combination (click)
so all of these different types of Clients can get the data they need. (Click)
The TOP Server driver plug-ins let you gather data though over a 100 different protocols depending on the licenses you have, giving you an enormous number of potential data sources. (Click)

3. TOP Server Gets You Connected!
This is a partial listing of the drivers and driver suites available for TOP Server. The complete listing of drivers and suites can be found at the url on the screen or by <Click>
clicking on the Drivers List tab at the toolboxopc.com website. Just click on the link to get all the detailed information about the item for which you are interested . <Click>

4. How Can TOP Server help?
So, how can TOP Server help? Traditionally TOP Server drivers will monitor process and control data, providing that to your HMI or Client application. With the SNMP driver suite, TOP Server allows you to monitor health and status information of your Ethernet infrastructure, that is, any device that has an IP address. Now let’s dig into the meat of the presentation and see what this can do for us. <CLICK>

5. What is SNMP? SNMP – Simple Network Management Protocol
An Ethernet protocol
Unlike regular drivers, we aren’t getting PLC or control system data via SNMP
So, just what is SNMP? I know this may be basic for some or maybe many of you but I don’t want to make assumptions and leave anyone behind.
SNMP stands for Simple Network Management Protocol.
SNMP is an Ethernet protocol, and unlike most drivers you are used to using, you use the SNMP driver to get network and IT infrastructure health information instead of control/process data.
Think of SNMP as being a way to monitor the health of the infrastructure that delivers the control and process data. <CLICK>

6. What is SNMP?
SNMP standardizes access to managed device health and configuration information
All major IT devices that are “managed” support the SNMP Protocol
Routers
Network Switches & Hubs
Firewalls
UPS power backups
Generators
Even some control devices!
As an industry standard, SNMP provides a uniform way to access information from your IT infrastructure devices such as routers, switches, UPS systems, firewalls, generators and more, including an ever growing number of control devices.
Devices that support the SNMP protocol are typically known as “Managed” devices in the IT world. If you buy a “Managed Switch” you can be pretty sure it will support SNMP. You do absolutely pay more for Managed devices, but the information and flexibility they provide usually more than justifies the cost difference.
We’ll talk more about how we can still help you if you don’t have managed devices shortly. <CLICK>

7. Why SNMP? Automation depends on critical IT infrastructure
IT infrastructure uptime directly impacts operational profitability
Putting network/infrastructure “health” information in front of the right users empowers them to act sooner when problems occur
Less downtime = More Profitability
A message that fits for any industry!
So, why do controls or SCADA engineers need SNMP? The benefit of using SNMP to get information on the health and status of your IT infrastructure up your HMI or Client Application should be obvious – the quicker an operator or engineer can take action with useful data in hand when a problem occurs, the sooner the issue can be resolved. This translates into less downtime, and higher profitability.
The TOP Server is an “enabler” to get that IT infrastructure data up to your HMI or Client application.
The good news is that the TOP Server SNMP suite also provides a “ping” driver that can tell you the status of non-managed devices – so if your customer doesn’t have a fully SNMP managed infrastructure, they can still see benefits until they add more managed devices to their infrastructure. <CLICK>

8. Examples of Information Provided by SNMP
UPS battery capacity remaining
UPS battery failure warnings
UPS power/battery status (on utility power or battery)
Switch port traffic volume
Switch port status (connected/not connected)
Alerts of system problems
And many more
Here are just a few examples of the types of information that you can get from your devices, such as UPS battery information, Managed Switch port information, system alerts and more. The SNMP standard does not define WHAT the device MUST provide – it just provides a standardized way of addressing the information. You’ll need to consult your device documentation to learn what is available in the device. <CLICK>

9. Terminology Introduction
OID = Object Identifier
A big sequence of numbers that represents the “address” for a parameter
MIB file = Management Information Base
A text file that lists the OIDs and their uses for each status parameter available in the device
SNMP Trap = an event that a managed network device generates based on configured conditions
Example: UPS goes off utility power and onto battery power
Ping = a simple command you type at the DOS prompt followed by the IP address to see if a device is responding on the network. Useful to see if non-managed devices are responding and working
SNMP Community Name – like a password
SNMP Agent = an SNMP Slave Device
SNMP Manager – in this case TOP Server, but in the IT world, this would be a Network Management System like HP Openview or Tivoli.
If you are unfamiliar with SNMP there is some terminology that you may not already know that will be useful in working with the IT group. Here’s a quick glossary so you can be “ready” and speak with knowledge. <CLICK>
Object Identifier: A sequence of numbers that is equivalent to a PLC address, in that it tells the server where the information is in the device. <CLICK>
MIB: or Management Information Base. This is a file that lists the parameters available in a device and their OIDs <CLICK>
SNMP Trap: an event generated by the device based on configured conditions and is then transmitted unsolicited rather than waiting to be polled. An example would be that a UPS goes off of utility power and onto battery power. <CLICK>
Ping: is a simple network command that sends a message to the device to see if it is responding on the network. This is especially useful in monitoring the status of an unmanaged device. <CLICK>
SNMP Community name is like a password to network users wishing to gain access to the data. <CLICK>
SNMP Agent is the SNMP enabled device. <CLICK>
And finally SNMP Manager – this is a network management system. In the IT world it would be a system like HP Openview or Tivoli. In the context of the automation industry, the HMI or Client Application and the TOP Server can be used like a network manager for controls/automation engineers, just exposing the information you care about, in a way that makes sense to your typical user. <CLICK>

10. Now before the IT Manager Asks..
TOP Server SNMP Suite
Is not a replacement for their IT tools like HP Openview or Tivoli, rather a complement to these systems.
Is typically used in a read only configuration
Can limit what an operator or control engineer sees to a “need to know” list of items
Should be used to have the controls group provide more helpful information when they report a problem to IT
If used properly should actually make the IT team’s job easier
To be clear though, the TOP Server SNMP suite <CLICK>
is NOT a replacement for IT management tools. It is used to help controls engineers and operators have information readily available when needed. <CLICK>
Also, the SNMP driver is typically used in a read only configuration, and if the IT manager doesn’t give you the password (i.e. SNMP Community name) for writes… then there is no worry or risk of unwanted writes. <CLICK>
You can limit what the operators or engineers see by configuring tags only for necessary data. <CLICK>
This information can and should then be used by controls group to provide useful information to the IT department when they report problems, <CLICK>, which in turn should make IT’s job easier. <CLICK>,

11. What Tools are Needed? TOP Server SNMP Suite
Three levels of licensing
1-15 device license, US$895
16-50 device license, US$1795
Unlimited device license, US$2495
License for a single computer
Annual support and free upgrades: US$175 – US$495 depending on license level
Also part of the vertical industry IT & Infrastructure Suite
So, what do we need to have a fully licensed product?
Obviously, a license for the TOP Server SNMP Suite. The license grants use on a single computer. There are three levels as shown here and the unlimited license is also included as part of the TOP Server IT & Infrastructure vertical industry suite. The Support component is optional but when renewed annually gives you access to all the future enhancements. Including Remote configuration, OPC Alarms and Events tags for the Event Log, OPC UA and device auto-discovery and generation for SNMP.
So now that we know a little bit about SNMP and the full licensing of the TOP Server, let’s look at what the driver suite offers and how it is configured. <CLICK>

12. TOP Server SNMP Suite Overview
Includes SNMP and Ping Drivers
Ping Driver is available for non-managed ethernet devices and provides online/offline status of these devices
SNMP v1 and v2c supported (SNMP v3 not presently supported)
Supports standard TOP Server protocol diagnostics
Includes a number of standard device MIBs as part of the install.
The SNMP Suite includes both the SNMP driver and the Ping driver for non-managed ethernet devices.
The driver supports SNMP v1 and 2c. V3 is not currently supported.
It supports standard TOP Server protocol diagnostics and includes a number of standard device MIBs as part of the install.
Example MIBs included with the install are:
General SNMP system configuration
General TCP/IP configuration
Standard UPS configuration
As a note, the rest of the presentation focuses on the SNMP driver. The Ping driver is a simple driver with very limited configuration options, so we will not spend any time on this topic.
<CLICK>

13. Key Features and Considerations
Use primarily for monitoring of managed network systems
Polled points (SNMP GET) and unsolicited events (TRAPs).
Data is organized in hierarchies.
Network Analyst for Managed Ethernet Switches.
Configuration works best if you have device MIB files.
Important to Understand
SNMP Communications settings
SNMP Trap Settings
Network Analyst Settings
Naming syntax of items and correlation with MIB files
SNMP is a network management protocol, designed primarily for monitoring of managed network systems.
This is a key difference if you have been using TOP Server drivers to acquire process control data.
SNMP also has the ability for both polled points (SNMP GET) and unsolicited events (TRAP). Most PLCs you are used to just doing polling. In the SNMP world it is more common to receive data in an unsolicited fashion, known as traps, using a report by exception model.
The variables accessible via SNMP are organized in hierarchies. These hierarchies, and other metadata (such as type and description of the variable), are described by Management Information Bases (MIBs). These are information files loaded to the device, not programs like with a PLC.
The SNMP driver also comes with a Network Analyst for Managed Ethernet Switches.
This is a built in set of statistics and calculations made based on the parameters defined for the device.
It is important to have access to your MIB files for your managed device. They usually come with the device or can be downloaded from the device manufacturer’s website. It will be important to understand item naming syntax and how to pull what you need from the MIB file. You’ll need to understand how an MIB file is set up and how that is used by the server. We’ll talk more about this later.
As you configure the SNMP driver, you’ll need to understand your SNMP communications and trap settings to get best results. We’ll talk more about that later. There are settings that must be made in the device if you want SNMP’s report by exception or TRAP features to work properly.
<CLICK>

14. User Interface Review Configuring the SNMP Driver
So let’s see how to configure the driver – we’ll highlight these differences as we get to them in configuration
So, now that we have covered the basics of SNMP and what is required, how do we configure this driver?
<CLICK>

15. Configuration – Channel Setup Channel Naming and Driver Selection
First, when you open a new project, you will see a blank tree in the left pane. Click here to add a channel. <CLICK>
Next, name the channel something meaningful to the customer or project. <CLICK>
Now, select your driver…in this case SNMP <CLICK>
Transition to next slide:

16. Configuration – Channel Setup Network Interface and Write Optimization
In systems with more than one network card and subnet, you can pick which card & subnet to bind to using this combo box
Write Optimization settings and why you might change them are covered in detail in the product help file – best to leave at default in most cases
Next, we can choose the network adapter, or IP address to use if our system has multiple network cards or IP addresses configured. <CLICK>
Then we set our write optimaztion methods. These are covered in detail in the product help file. It is generally best practice to leave these at the default. <CLICK>

17. Configuration – Channel Summary
After you have configured your channel parameters, you have the opportunity to review your selections and go back to make changes if necessary.
Transition to next slide: Now that we have our channel setup, lets get the device configured. <CLICK>

18. Configuration – Device Settings Name and ID
You’ll see this under the channel you just configured – click it to start the Device Configuration Wizard
Give your device a name that is useful to you.
Give the correct IP address of the SNMP-enabled device you wish to monitor.
Now, in the tree in the left pane you will see the channel you created and underneath, Click to add device. Clicking this will start the Device configuration wizard. <CLICK>
The first thing we do, just like at the channel level, is to give this device a meaningful name. <CLICK>
Then, after clicking next, we enter the IP address for the SNMP-enabled device you wish to monitor. <CLICK>

19. Configuration – Device Settings Timing
You will need to set your timing. In most cases the defaults are acceptable.
This is how long we wait for a response from the device in response to an SNMP GET request.
This is the number of times we will repeat the request after timeout before failing and moving on.
When using TCP, this is how long we wait for a socket connection to the device. In most cases with SNMP, UDP is in use so this is how long we wait for the first response from the device.
There are three settings related to timing. These are standard to most drivers in the TOP Server. <CLICK>
First is the connect timeout. If using TCP, this is how long we wait for a TCP socket connection to the device. In most cases with SNMP, UDP is used. When UDP is in use, this setting is how long we wait for the first poll response from the device. <CLICK>
Next is the request timeout. This is how long we wait for poll responses from the device before timing out. <CLICK>
Finally the Fail after is the number of times we repeat the poll request after the timeout period has been reached before failing.
Transition: Now we need to configure our autodemotion settings <CLICK>

20. Configuration – Device Settings Auto-Demotion
Auto-Demotion improves system responsiveness when devices go offline
Use of the Auto-Demotion option for each device is recommended when device communications may be unreliable.
This indicates how many successive cycles of request timeouts and retries will occur before placing the device off-scan. The valid range is 1 to 30.
Check the checkbox. By default this is not enabled.
allows you to control whether or not write requests should be attempted during the off-scan period. The default setting is to always send write requests
Device auto-demotion parameters allow a driver to temporarily place a device off-scan in the event that a device is not responding. By placing a non-responsive device off-line, the driver can continue to optimize its communications with other devices on the same channel by stopping communications with the non-responsive device for a specific time period. After the specific time period has been reached, the driver will re-attempt to communicate with the non-responsive device. If the device is responsive, the device will be placed on-scan, otherwise it will restart its off-scan time period. <CLICK>
Because of the way the SNMP Driver processes OPC tags, a non-responsive device with many tags may impede communications with other devices on the same channel, due to the timeout period being used on each successive query to the non-responsive device. Use of the Auto-Demotion option for each device is recommended when device communications may be unreliable. <CLICK>
Now to configure these settings <CLICK>
We must first enable the feature by checking the checkbox. <CLICK>
The demote after setting indicates how many successive cycles of request timeouts and retries occur before placing the device off-scan <CLICK>
The demote for time indicates for how long the device will be placed off-scan once the demote after parameter has been reached. <CLICK>
The xxx Checkbox allows you to control whether write requests from the client application should be sent to the device during the off-scan period. By default, it is unchecked so that write requests are always sent. <CLICK>
Indicates how long the device should be placed off-scan when the "Demote after" parameter has been reached.

21. Configuration – SNMP Communications SNMP Version
3 official SNMP versions
1, 2, and 3
1 draft SNMP Version
2c – known as the “real” Version 2 in practical use
TOP Server supports
Version 1 and 2c.
Does not currently support version 3 but most V3 devices still support 1 and 2c
SNMPv3 provides three important services that are incompatible with previous versions, which is why we do not yet support V3
Authentication,
Privacy
Access control
Now we begin to get into some SNMP specific settings.
There have been three official versions and one draft version of the SNMP protocol released.
The three official versions are 1, 2 and 3. Version 2 was never universally adopted due to an overly complex security system. This lead to draft standard version 2c which is viewed in practice as the “real” version 2.
TOP Server supports version 1 and 2c. It does not currently support version 3. However, many devices support more than one version of SNMP. Just because the device supports version 3, doesn’t mean it is completely unsupported.
SNMP v3 adds three new services: authentication, privacy and access control that are incompatible with previous versions, which is why we do not yet support this. This is still relatively new and has not gained wide acceptance in the marketplaces to replace version 2c.
<CLICK>
You can see in the drop down, you can select if your device is SNMP v1 or 2c compatible.
Click Next to proceed after your selection. <CLICK>

22. Configuration – SNMP Communications SNMP Port and Protocol
The Port number and Protocol are used when communicating to the remote device. Ports may range from 1 to The default Port is 161. UDP and TCP protocols are available. UDP is the default Protocol.
If you change these at the server, you must configure this on your device as well.
Next you set up your port and protocol to be used when communicating to your devices.
Ports may range from 1 to By default this is If you choose a different port, your SNMP enabled devices will need to be configured with the same port.
UDP and TCP protocols are available for selection from the drop down. UDP is the default transport protocol for SNMP. Once again, your device must be configured with the same protocol selection. <CLICK>

23. Configuration – SNMP Communications SNMP Community
The next screen allows you to configure the SNMP Community and Items per request.
Community name = a password for network devices.
Common options are public and private
Public usually read only
Private may allow writes if device configured for it
The common options, public and private exist in a dropdown, but you may enter any community name you have defined in your device.
The Community name is used when accessing the remote SNMP device. It is like a password for network devices.
<CLICK>
Common options are public and private, but the Community name can be defined by the user and depends entirely on the configuration of the remote device. Typically the public Community is for reading data and the private Community is for writing data to an Agent. Consult the device documentation for the correct Community name. The driver limits the Community field to 256 characters. <CLICK>

24. Configuration – SNMP Communications Request Size
Items per request used with SNMP Get or polled requests
SNMP V2c devices typically can handle maximum
SNMP V1 devices may require 1 item/request
Set your items per request between 1 and 25, depending on your device capabilities.
Items Per Request controls how many SNMP data items will be bundled together in each read request. For Agents/devices supporting SNMP v1, this may need to be set to a value as low as 1. SNMP version 2c devices can typically handle the maximum items per request. The valid range is from 1 to is the default.
<CLICK>

25. Configuration – SNMP Communications Error Logging
Namespaces in SNMP devices can change on the fly
Define how you want to handle the error
Check or Uncheck this box depending on if you would like to suppress the error messages as noted above.
The namespace (MIB information available) in an SNMP Agent/device is dynamic and may change during operation. The OPC server will display an error notice when a specified OID address does not exist on the target device. Clear the checkbox to suppress these messages
<CLICK>

26. Configuration – SNMP Communications Scan Rate Floor
SNMP scan rates are generally slower than control rates
Use Scan Rate Floor to protect from an over-demanding client application
Set your Scan Rate Floor and decide if you want to lock it at that rate for OPC clients.
SNMP devices are typically scanned at much slower rates than other controls equipment. Scanning an SNMP device too quickly may result in degraded device performance. The Scan Rate Floor has been added to prevent users from inadvertently overloading Agent/devices with read requests in the order of milliseconds.
The Scan Rate Floor is the minimum rate at which the driver will scan SNMP devices. The valid range is 0 to a little more than 2 billion milliseconds or roughly 25 days. The default is 1000 milliseconds.
If set to 0 the feature will be disabled, and the client scan rate, no matter how fast will determine the rate at which the devices are scanned. When set to a non-zero value, the SNMP driver will never scan the remote device more often than the specified scan rate. Note that a client can still poll the server and obtain the last read value at a much faster OPC Group Update Rate. Finally, the Lock option will lock the Scan Rate for this device to the given value. When Locked, the driver will always poll at the Scan Rate setting regardless of OPC client update rates that are below or above this rate.
When not locked, if the OPC Client has a slower scan rate, say 5000 milliseconds, we will use 5000 milliseconds as the device scan rate but if the client scan rate is 100 ms, we will still poll at only 1000 ms. What locking does is that it sets the scan rate to the specified rate, in this case 1000ms regardless of whether the client scan rate is 100 ms or 10000ms.
Earlier we mentioned MIB files. Now that we’ve covered some of the basic device configuration, let’s take a look at what these are and how the server handles them.<CLICK>

27. Configuration – SNMP Communications MIB Import – What is a MIB?
The SNMP MIB, or Management Information Base for a device, is
A collection of variables which is shared between the network manager and the network device.
Extensible
Hierarchical
Contain OIDs or Object Identifiers
MIB hierarchy
A tree with a nameless root
Levels assigned by different organizations.
The top-level MIB OIDs belong to different standards organizations
Lower-level object IDs are allocated by associated organizations
Managed object=MIB object=object=MIB is
One of any number of specific characteristics of a managed device.
Managed objects are made up of one or more object instances (identified by their OIDs), which are essentially variables.
What is an MIB?
It is a collection of variables (much like PLC points) that are shared between the network manager and device. <CLICK>
The MIB is extensible, which means that hardware and software manufacturers can add new variables to the MIB. These new MIB definitions must be added both to the network element and to the network management system. <CLICK>
MIBs use a hierarchical namespace containing object identifiers (OID). Each OID identifies a variable that can be read or set via SNMP. <CLICK>
The MIB hierarchy can be depicted as a tree with a nameless root, the levels of which are assigned by different organizations. The top-level MIB OIDs belong to different standards organizations, while lower-level object IDs are allocated by associated organizations <CLICK>
A managed object (sometimes called a MIB object, an object, or a MIB) is one of any number of specific characteristics of a managed device. Managed objects are made up of one or more object instances (identified by their OIDs), which are essentially variables. <CLICK>

28. Configuration – SNMP Communications MIB Import – What is a MIB?
This is an example of an MIB Hierarchy and shows you how to trace an object identifier. For example The Sysname object is attached to the upper tree object System with index number 5. By taking each consecutive object definition, it is possible to walk the tree up to the root. The definitions of SNMP objects that are nodes in the tree representation use the keyword OBJECT IDENTIFIER and not OBJECT-TYPE like leaf objects. We’ll see what object Identifiers and Types look like momentarily.
<CLICK> So, we said the Sysname object is attached to the tree object System by index 5. Here you see the system object.
The system object is part of the MIB2 group of 11 objects <CLICK>
as shown here and is linked to the mib object <CLICK> with index 1 The mib object is linked to the mgmt object <CLICK> with index 1 The mgmt object is linked to the internet object <CLICK>with index 2 The internet object is linked to the dod object <CLICK> with index 1 The dod or Department of Defense object is linked to the indentified organization object <CLICK> with index 6 The identified organziation object is linked to the iso or international organization for standards object <CLICK> with index 3
The iso object is attached to the root as index 1.
This gives in the numerical format: where .0 is the instance number of the Sysname object.
Next, let’s briefly look at an MIB file.<CLICK>

29. Configuration – SNMP Communications MIB Import – What is a MIB?
This happens to be RFC1213, which defines SNMP system object such as system description, system name, and system up time among others.
You will see in the beginning are some descriptions for naming conventions and group definitions. As you can see, the groups are marked with Object Identifier meaning they are a node or branch in the tree structure<CLICK>
Later on in the file, you will see the object definitions as well. <CLICK>
These define the object name. Notice that this is marked with Object type, which as we said, means that these are leaf objects in the tree structure. <CLICK>
syntax to be used, basically this is the data type, <CLICK>
Access rights – whether it is read only or read/write<CLICK>
Status – defining wheter the object is mandatory or optional<CLICK>
And a description of the object. <CLICK>
As you can see, there are several objects defined here….but these are only a small fraction of what is available in this particular MIB.
This information can be used to help you troubleshoot a problem, if for instance a single point has bad quality and you need to find out if the OID is correct in the server
Transition: Now let’s look at how we actually set up the MIB import in the server. . <CLICK>

30. Configuration – SNMP Communications MIB Import – How Do we do it?
First you need to specify your template, if any and the number of ethernet ports on the device.
First you will select your template type. . <CLICK>
As you can see there are several predefined device types. <CLICK>
Select the device type, then set the number of ethernet ports in the device. . <CLICK>
After clicking next, you will see what MIBs are loaded for that template. <CLICK>
Transition: What do we do if our device does not fit any of the categories and we need to build our own configuration? <CLICK>

31. Configuration – SNMP Communications MIB Import – How Do we do it?
If your device doesn’t fit any of the categories what do you do? There are a number of common device MIBs that install with the server. You may select those here.
Select “None” as the template type to enable the “Customize Template” button and set the number of ethernet ports on the device
Click, the Customize Template button
<CLICK>
Select none for your template type to start. Then set the number of ethernet ports in the device.
This activates the Customize Template button. Click this button.
This brings up the custom device profile selection menu. You can choose any of the major MIB groups listed that your device supports. Once done and you click OK, this brings you back to the template selection screen. Click Next to continue.

32. Configuration – SNMP Communications MIB Import – How Do we do it?
If your device has custom MIB files not listed here, then you can import them from a file location by clicking the “Choose MIB file to import” button.
If your device has custom MIBs, you can add them here by clicking the add button.
<CLICK>
This enables the MIB Module Selection Menu. As you see there are also a number of common device MIBs that can be selected here as well.
To select your custom MIB file click the browse button:
This opens the standard Windows file selection menu. Choose your file. Here I am selecting a file specific to HP switches. <CLICK>
Then you will be presented with a description of the module as read from the MIB. Click Yes to import the MIB <CLICK>
You will now see this listed in your MIB modules list. Make sure the module or modules are highlighted and click OK to continue.
Which brings you back to the MIB Import screen, now showing the module added. Click Next to continue to the trap parameter definitions for the device.

33. Configuration – SNMP Communications SNMP Traps Port & Protocol
You can disable and ignore trap notifications by unchecking this checkbox.
Set the trap port, by default 162
An SNMP TRAP is a message which is initiated by a network device and sent to the network manager. For example, a router could send a message if one of it's redundant power supplies fails or a printer could send an SNMP trap when it is out of paper.
The idea behind SNMP Traps is that if a manager is responsible for a large number of devices, and each device has a large number of objects, it is impractical for the manager to poll or request information from every object on every device. The solution is for each agent on the managed device to notify the manager without solicitation. It does this by sending a message known as a trap of the event.
After the manager receives the event, the manager displays it and can choose to take an action based on the event. Trap-directed notification can result in substantial savings of network and agent resources by eliminating the need for frivolous SNMP requests. However, it is not possible to totally eliminate SNMP polling. SNMP requests are required for discovery and topology changes. In addition, a managed device agent can not send a trap, if the device has had a catastrophic outage.
Now let’s look at the configuration options.
<CLICK>
First you must enable SNMP Trap support by checking the enable checkbox. <CLICK>
Next You must set the trap port, which by default is If you reconfigure this on the TOP Server then you must reconfigure this on the device. <CLICK>
You also must set the protocol. By default the Trap protocol is UDP. Once again if you reconfigure this on the TOP Server then you must reconfigure this on the device. Click Next to continue. <CLICK>
Set the Trap Protocol, by default, UDP

34. Configuration – SNMP Communications SNMP Traps Community and Requests
Set your Trap Community
Set the number of Trap events to retain. This can be configured between 1 and 100
Next you must select the trap community. As with the SNMP general community, common options are public and private which are listed as a dropdown, but the Community name can be manually entered by the user if the community name is different. This depends entirely on the configuration of the remote device. Typically the public Community is for reading data and the private Community is for writing data to an Agent. Consult the device documentation for the correct Community name. The driver limits the Community field to 256 characters. <CLICK>
Next you will set the number of events that will be returned per request. The range is 1 to 100
Configure the number of data fields to pass with each trap event

35. Configuration – SNMP Communications Network Analyst
Enable or disable by a simple check box.
Define the number of ports in your switch
Set the first percent bandwidth usage threshold
Set the second percent bandwidth usage threshold
For Ethernet switches, the network analyst allows you to monitor a switch’s capacity and bandwidth utilization. This is available for each port in the switch. When enabled the driver will automatically create the Network Analyst tags for the switch device.
<CLICK>
First you enable the network analyst by checking the checkbox. <CLICK>
Then you set the number of ports in your switch <CLICK>
Finally you will set the 1st and 2nd port % bandwidth utilization threshholds. We will discuss these more in a few minutes. Click next to continue <CLICK>

36. Configuration – SNMP Communications Network Analyst
Set your sample size.
If you wish to exclude ports from monitoring and calculation, exclude them here.
You will next specify your sample size for the Moving Average Calculations.
<CLICK>
If you wish to exclude ports from monitoring and calculation, you specify that here.
As I said, the driver automatically creates the Network Analyst tags for the switch, so let’s take a look at what those are and what information they provide. <CLICK>

37. Network Analyst – Available Tags
buPctIn
buPctOut
buStat
buSwitchStat
When the tags are created, they are grouped in tag groups by port for each statistic calculated. There are four buPctIn, buPctOut, buStat, and buSwitchStat – which as you can see is does not have a group. We’ll discuss this one momentarily. <CLICK>
buPctIn: shows the percent inbound bandwidth usage of each port, averaged over a number of sample periods. The client's scan rate is the sample period. You can see when you highlight the buPctIn group, there are tags for each port. <CLICK>
You will also see if you expand the buPctIn Group that you also are given historical moving averages for each port. <CLICK>
buPctOut: shows the percent outbound bandwidth usage of each port, averaged over these same sample periods.
If you were to expand the buPctOut Group, you would see historical moving averages for each port just the same as the buPctIn group. <CLICK>
buStat: The buStat tags utilize the two Port Status threshold settings to present a simple health status indicator. When buPctIn for a given port rises above the 0 limit, buStat for that port changes from 0 to 1. Likewise, when buPctIn rises above the 1 limit, buStat changes to 2. This provides a simple "traffic light" style of indicator showing available capacity. Because this is only a status indicator there are no moving averages to display here. <CLICK>
buSwitchStat: assumes the highest value of the buStat tags, giving a single indication of the available capacity of the device as a whole. A list of ports to exclude provides the opportunity to tune the behavior of buSwitchStat. For example, a switch may have two ports that always run at or near capacity. By excluding these two ports, buSwitchStat can indicate when the rest of the switch's capacity is nearing exhaustion without the known high-capacity activity causing false alerts. As you can see here, this is a single tag under the root Network Analyst tag group.
Let’s complete our device setup now <CLICK>

38. Configuration – Device Settings Summary
After configuring your device, just like at the channel level, you have an opportunity to review your settings and go back to change anything you may need to change.
Transition to next slide: Now that we’ve completed our device configuration, lets look at how you address memory in your SNMP device.
Click “Finish” and you’re Done!

39. Configuration Setting up SNMP Tags/Items
SNMP does not have “addresses” but rather object identifiers as defined by the associated MIB files.
You do not have to set up tags as they are automatically generated when you define your device and MIBs.
SNMP does not have addresses. It uses object identifiers defined by the associated MIB files.
As you can see here. These are tied to the configuration in the associated MIB that we discussed earlier.
You do not need to set up tags because the TOP Server automatically generates them when you define the device and MIBs to be used.
<CLICK>
Transition:
Let’s see how we can test our communications.

40. Testing Communications OPC Quick Client
If launched from the Server, it will auto-populate all tags configured in the Server
Tag detail view
Server connection and OPC Group tree
Now let’s see how some live data will look it the OPC Quick Client. <Switch to Quick Client>
For ease of viewing data, I have selected just a few points from an HP Switch in our office.
OPC Quick Client Event Log

41. Tips & Tricks
Loads of free help at:
Quick Start Guide
Training Videos
Papers and Utilities – Trouble Shooting Guide
More information on the Product Details tab
Contact Software Toolbox while you are in the planning stage, so we can help
We have a large volume of free documentation to help make connectivity easier, including our Trouble Shooting Guide. You can see some of the links on the screen.
Please do send us s and get us involved at the beginning, we love to help you find solutions.
(Click)

42. Want to know about health of your actual Workstations/Servers also?
TOP Server System Monitor Driver
Part of TOP Server Standard License
Uses Microsoft Performance Data Helper API
Item Import Browser allows Auto Tag Generation
Performance Objects
Instances
Counters
Monitor Health of Underlying Systems
Network Interfaces
Memory Utilization
CPU Usage
So Much More…
Contact us for information about our other tools we have that can supplement TOP Server in monitoring your infrastructure.
System Monitor Driver
OPC, Suitelink,PDB, DDE
TOP Server
Now before we move into questions, there is one other TOP Server driver that we’d like to briefly review.
The System Monitor Driver is available as a stand-alone driver or included as part of the IT & Infrastructure Vertical Industry suite. It provides the ability to read data from any Windows Performance Counter value and feed it up to the HMI or client application.
The System Monitor driver can be used to look at the actual health of a specific PC or server. It runs on the PC or server of interest and lets you look at things like network utilization, memory, disk space, disk I/O, SQL server performance, and many other items.
Combine the System Monitor with the SNMP Suite and you can have complete visibility from your HMI or Client Application into your system health.
Please contact us if you have questions about these or any of our other tools such as OPC DataHub or IntraVue to find out how they can help you monitor the status of your plant network.
Now lets open up the lines for questions and discussion. <CLICK>

43. Contact Information & Other Learning Opportunities
Questions later?
Boyce Baine or
Other learning opportunities
Visit
Now I’ll answer any questions you may have.