Slide 3 Invensys Enterprise Control Offerings Manufacturing / Production Operations Corporate Integration and Collaboration Platform Automation Invensys and Third Party Operations Management Invensys and Third Party Enterprise Control System IT Platform Corporate Systems
Slide 4 Where The Offerings We Will Discuss Fit Within The InFusion Enterprise Control System
Slide 5 Topics covered in this Presentation: What is NetSight? NetSight Features –Device Discover, –Topology Mapping –FlexViews Alarming & Events –Alarm Manager Action –vs- Criteria I/A alarming NetSight Event Logs Switch Configurations required for NetSight Console Functionality –Trap messaging, –Syslog messaging, – SNTP
Slide 6 What is NetSight Console: NetSight Console is a network SNMP monitoring application. In the I/A series MESH Network environment NetSight has the ability to: –Poll SNMP enabled devices. –Monitor the networks switch health status via: FlexViews Topology Maps Event Logs (Trap and Syslog messaging) –Generate system alarming on network events. –Aid in troubleshooting of the network. –Generate network status, and event reports. –Allow for remote monitoring of the network. The deployment of the NetSight Console Server allows up to five (5) simultaneous users (Clients).
Slide 8 Device Discovery: Select the Discover Networks Button
Slide 9 Device Discovery: The Discover tool allows you to discover the physical elements (devices) of your network, and add them to the NetSight database. To discover devices on The MESH network, a specified range of IP addresses must be entered.
Slide 10 NetSight Console: Device Display Device groups User-defined device groups User-defined port groups Port groups via FlexView filtering
Slide 11 FlexViews: The default FlexView is Interface Summary 11 Choose from among many pre-defined FlexViews or create your own Right-click column headers to filter, find, print, export, or hide Call up previously opened FlexViews Click to retrieve MIB data for this view
Slide 12 FlexViews: Predefined Predefined FlexViews can be found at: c:// Documents and Settings-> Fox -> Application Data -> NetSight -> System -> FlexViews.
Slide 13 Topology Manager:
Slide 14 Topology Mapping: Topology Manager lets you expand your view of the devices in the network, making it easier to visualize their physical or logical layout. It allows you to arrange your network in a way that is less abstract, graphically depicting links between devices, and showing device groupings.
Slide 16 Alarming & Events: Alarm Manager NetSight can be setup to alarm on specific alarm criteria, such as a Trap, and/or Syslog message, message types, or text within the message itself. The alarm can also be setup to run any type of file such as exe, bat, cmd, txt, etc.. The data within the message can be added as an argument statement for displaying event details.
Slide 17 Alarming & Events: Trap Alarm Criteria The settings on this screen show how to setup an alarm for Loop Detection using Trap messaging.
Slide 18 Alarming & Events: Custom Alarm Criteria The settings on this screen show how to setup an alarm for Loop Protection (LPA) using custom criteria. Syslog Message received: MSTP(1.tMstEvent) Loop Protect Status: PENDING on SID = 0, Port = #.#.# Event Count =1
Slide 19 Alarming & Events: I/A Alarming via NetSight The previous bat file can be modified as follows: Power Online: off Setlocal D:\opt\fox\bin\tools\omsetimp -b TRUE SWT_MON:SWxxPWRFL.IN D:\opt\fox\bin\tools\omsetimp -v -s %1 SWT_MON:SWError.SN0001 D:\opt\fox\bin\tools\omsetimp -v -s %2 SWT_MON:SWError.SN0002 Endlocal By utilizing an I/A CIN and IND blocks, NetSight pre-defined Arguments can be passed on to a FoxView or FCSview window. The below bat file script will pass the NetSight Arguments (Device Name, and Message Info) shown in figure. By using the %1 as shown below will send the Switch name letter bug to the SWError SN0001 text field, and the %2 send the error message info to the SN0002 text field. With modification of the script, NetSight can also pass (Device IP, SNMP credential, and/or Trap Name).
Slide 20 NetSight Console Event Logs: 3
Slide 21 Event Logs: Location of Event Logs: –The Trap and Syslog event logs are located at D:\Program Files\Enterasys Network\NetSight\appdata\logs. – The Console event log is located at C:\Document Settings\Fox\Application Data\NetSight\logs; theFox is the user account name when NetSight was installed. The server synchronizes all of the event logs, meaning that the server will log events and makes them available to all the clients connected to the server. Event Log manipulation
Slide 22 Switch Configurations required for NetSight Console: 4
Slide 23 Switch Configurations required for NetSight Console Functionality: Traps To record and capture Trap Event logs with NetSight each switch within the network must be configured to send these traps. When utilizing SCAS to enable this function the setting shown here circled in red must be entered. Command is as follows: set snmp targetaddr Admin param snmptarget mask taglist snmptag
Slide 24 Switch Configurations required for NetSight Console Functionality: Syslog To record and capture Syslog Event logs with NetSight each switch within the network must be configured to send these messages. When utilizing SCAS to enable this function the setting are as shown. Note: The Alarming Severity Level should not be set to 8 (debug) for day to day operations.
Slide 25 Switch Configurations required for NetSight Console Functionality: SNTP Enabling SNTP time sync is required to sync I/A system time with the NetSight event logs (Console, Trap, Syslog). Note: Event log time stamps saved local to the switch are saved as GMT time. The offset may vary by several hours depending on the GMT offset, shown circled in red.
Slide 26 NetSight Console Install: When installing NetSight Console on an I/A or FCS workstation refer to B0700EJ. The NetSight Console Server application cannot be installed on workstations running the following applications: –1. FCS Galaxy server –2. Historian (FCS / AIM*) –3. Any I/A Series/FCS workstation running system monitor while hosting a switch or SNMP polled device. –4. Domain Controllers (Active Directory) –5. FoxAPI –6. Message Manager (or any dedicated workstation)