Engineering

From AVNOC

Engineering

This is the fulfillment server for Agent deployment. It is the backbone of the framework. It is where all agents send the monitoring results for processing.

Your login determines available options.

Administrative Login

0001.PNG

A full access login is for administrators. Full access is granted to VM owners.

Tenant Login

0002.PNG

Add Users

This is one of the key components to having a successful installation. Delegation of duties enable balancing of work flow.

Click on Users 0003.PNG

On the left sidebar three options appear

  • Search - Display Search Screen
  • Add - Add a New User
  • Pins - Work With Pins

Click on Add 0004.PNG

User Fields

Add User Fields
Field Value Required
User Logon Identification For LDAP use Windows Logon, non LDAP last.first YES
User Password For LDAP anything, non LDAP make it hard YES
User Authority * Administrator * Dealer(Tenant) YES
Salesman Identification Always Use None Selected NO
Customer Identification For Tenant Only NO
User Email Full email address YES

If you are using LDAP or Active Directory then use the windows login name without the domain.

Tenant login must be mapped to a master customer. Note that a master customer might need to be created first then this field can be selected.

Always test the login before giving credentials to the user.

Passwords are store as a hash value, it must be reentered every time this screen is accessed.

Pins

Add a New Pin

Adding a new pin can only be done for a customer. After a customer has been added click on outside providers to a a pin user to this customer.

0006.PNG 0007.PNG

Click on Add a New Customer Service Provider Record

Service Provider Fields

Add Customer Provider
Field Value Required
On-Site Service Provider Name last.first YES
On-Site Service Provider Phone YES
User Authority * Administrator * Dealer(Tenant) YES
On-Site Service Provider Email YES
On-Site Service Provider Contract Number This becomes their logon pin number NO
On-Site Service Provider Comments NO

Once this records is saved the pin number becomes active for this customer only.

To assign this service provider to additional customers Work with Existing Pins.


Work With Existing Pins

0007.PNG

Click on View Record next to Provider you wish to work with.

Add Pin to Another Customer

Click on Users

Click on Pins

0008.PNG

This brings a list of pins up.

Under Distinct PIN Numbers is a list of all service providers.

  • Remove Pin - deletes this pin from the system including all customer references
  • Change Pin - change the pin contract number

Under PINS By Customer is a list of assignments to a customer for each service provider.

  • Remove Pin - delete the pin assignment for an individual customer

Under Add PINS to Customer is a list of available service providers for each customer.

  • Add PIN - adds the service provider to a customer.

Work With Customers

The fist level under Customer shows all open tickets.

0009.PNG

Click Search to display all customers.

0010.PNG

Add a New Customer

Adding a new customer is considered adding a new network. Each customer has an appliance associated with it. The appliance can be software for monitoring a VLAN or hardware for small VLAN installations or private network monitoring when the network is bridged.

Adding a customer sends a notification to AVNOC to build a and provision a device.

Click on Add Customer

0011.PNG

Add Customer Master

Customer Master Fields
Field Value Required
Customer ID YES
Organization YES
Contact Last Name YES
Contact First Name YES
Address Line 1 YES
Address Line 2 NO
City YES
State YES
Zip Code YES
Zone Select the Management Region YES
First On-Site Service Provider Service Provider First to Call First NO
Second On-Site Service Provider Service Provider to call Second NO
Third On-Site Service Provider Service Provider First to Call Third NO
Primary Phone YES
Secondary Phone NO
Fax Phone Number NO
Email Address Primary Contact for Appliance Host Alive Emails YES
Email Address AV Contact NO
Email Address IT Contact NO
Email Address Help Desk Contact 1 NO
Email Address Help Desk Contact 2 NO
Web Site Address to be Monitored by AVNOC NO
Status YES
Type YES
Master Customer ID Select a Master Customer Number for Account Consolidation. NO
This options allows you to specify whether or not the links at the bottom of a service ticket are show. Security Alert!
Enable this links at your own risk. The url exposed in these links, while obfuscated will give a hacker an opportunity to change the arrive times and leave times on a ticket and provide a hacker with a reason to hack. It is just the way they are.
For integrators, this link might be enabled to track time but should not be used as a payroll feed.
YES
Type of Installation. Select the type of device deployed in customer location. YES
Maximum Number of Assets Allowed In DataBase. Select the number of Assets allowed in this configuration. YES
Open Tickets NO
Closed Tickets NO
Select the method for sending alerts from remote systems Select EMAIL to send alerts from appliance via email or HTTPS to send alerts using HTTPS post to EDI Server YES
Select NO to omit scanning the customers network from this host SAMENET to scan the network that the devices is on or ALLNET to scan all networks that this host has access to Use the appropriate option and be carefull, some networks will flag this operation as an intrusion detection. Once this happens the IP of the appliance must be removed or allowed or all subsequent requests will fail and a false positive may occur YES
Select YES to auto populate assets from the Net Scan, otherwise select NO Selecting YES will compare devices from the netscan to the entered assets. If there is an asset in the scan but not in assets the device will be added with default values YES
Salesman Salesman Assigned To This Customer YES
IP Address from which Portal Traffic is Allowed. Use ALL during setup. Security Alert!
Consult with your IT Department before changing this parameter.
This is the outgoing public IP address that you will login from. It is usually your gateways public IP address. It must be a static IP. To allow access from anywhere enter ALL for this parameter. This field must be entered correctly or else customer access will be denied.
YES
IP Address from which Portal Traffic is Allowed for Second Network, Do not enter a FQDN here! Security Alert!
Consult with your IT Department before changing this parameter.
This is an alternative outgoing public IP address that you will login from. Use this only if there are multiple offices in separate publid networks. Do not enter a FQDN here!
NO
IP Address from which Portal Traffic is Allowed for Third Network. Use this only if there are multiple offices in separate public networks, Do not enter a FQDN here! Security Alert!
Consult with your IT Department before changing this parameter.
This is an alternative outgoing public IP address that you will login from.
NO
Last Contact This is the date/time of last contact from remote units NO
Interface ID of Customer in Remote System Enter the Remote System Customer ID NO
Response Time Per Contract YES
Last Alert NO
Last User NO
Last Date NO

Once a customer saves associated tables will be built upon first access.

Select the customer to build the tables and start populating data associated with this customer

Setup Global Fields

Global fields are accessed by each customer. They populate Drop Downs and Word Values.

WARNING: Please exercise caution when working with global fields because they effect every customer.

Table Interface

The tables interface is used to maintain drop downs and word strings used through out the system.

Clink on Tables

0012.PNG

Navigation within Tables is on the left.

  • AUX Tables - Drop Downs
  • WRD Tables - Word Selectors

Lets examine the AUX interface

There are many options available. Lets take a look at some that can be used to setup the system.

WARNING: If you are unsure what an AUX does, leave it alone

AUXASSETTYPE

Click on AUXASSETTYPE.

0013.PNG

This will bring a list of asset types.

0014.PNG

All of the items listed can be deleted.


  • Code - Internal reference
  • Value - Alias

At the bottom of the lists is an area to Enter a New Code

0015.PNG

Enter your values int Code and Desc fields.

WARNING: Use All CAPS and NO SPACES for the CODE WARNING: Desc should not contain any special characters

If you try to delete a CODE in use the following error occurs

0016.PNG

Navigate to the bottom of the page and migrate the code. Most of the time it is necessary to create a new code to migrate to and then migrate the old code to the new code.

0015.PNG

The maintenance process is the same for all AUX.

Here are a few more interesting AUX:

AUXSNMPCOMMANDS

0017.PNG

These are special codes that you should never change. They are internal control commands which incite action withing the compiler.

Work with Tasks

Tasks are special features that work with a selected customer.

0018.PNG

In order to run a tasks a password may be required. The password is todays date in YYYYMMDD format without delimiters.

Send Email to avnoc.notice@avnoc.com

This is a test function for new server installs and usually done by AVNOC to make sure email is working.

TICKETS Close All Open Tickets

This function closes all open tickets for the selected customer.

ASSETS: Clearing ASSETS, TICKETS and Histories

This function is used to clear ASSETS, TICKETS and Histories from the selected customer. It is used usually to fix Asset Import problems. This give you an easy way to start the import multiple times until the resulting data set is correct.

DATABASE: Consistency Check

Every once in a while it is a good idea to consistency check the data base.

Upload a 250 x 60 logo to the system to display on the Plug In and Service Console interfaces.

Admin

These are administrative tasks associated with every instance.

0019.PNG

Whos On

This is the default entry point. It lets you know who is logged into Engineering.

There are links to the rest of the interfaces which can be accessed by opening in a new tab/window.

On the left navigation are the following functions:

Software Update

WARNING: DO NOT do this unless instructed to do so by AVNOC

System Processes

A detailed view of the notice processing system.

Queue verification notices indicate that there is a backlog of xml files to process in the queue. To reset the queue, xml files are deleted from the queue and the notice processor is restarted.

Delete XML Files from the Queue

Select:

Customer -XML Queue

QueueVerify001.PNG

Enter the Date for Password Click Clear all Files in the XML Queue

Any asset that is alerting will continue to alert. There is a possibility that a recovery notice is hung in the queue. If a recovery notice is deleted then the ticket associated with the recovery notice must be manually closed.

Restart the Notice Processor

After every system update the Notice Processor needs to be restarted.

Stop the Current Process

Select:

Admin - System Processes

QueueVerify002.PNG

The very first line Active Processes contains the process id, in the above example it is 2744. Copy this program id and scroll to the bottom of the list.

QueueVerify003.PNG

If the list does not contain a line for Active Processes, skip this step.

Enter the Date for Password Paste the Process ID into the Process ID field.

Click Process Command

Click on System processes again to make sure the Process ID has been stopped.

Restart the Notice Processor

Scroll to the bottom of the list again.


QueueVerify004.PNG

Enter the Date for Password

In the Process Restart Command enter:

/opt/avnoc/bin/notices.sh

Click Process Command

The Active Process should indicate a new process id now.

Certificates

A how to on certificate processing.


Customer Appliance Setup

Appliance setup is performed on each monitoring device, both Software and Hardware. This is the spot do dial in customer network configurations.

Special consideration for the IP Address.

A permanent IP address is required for processing traps, otherwise, a DHCP can be used to specify DHCP enter DHCP in all of the ETH0 parameters.

DNS Processing is usually setup to use google 8.8.8.8, If assets are to be monitored using internal DNS resolution, enter the customers internal DNS server IP.

Select a customer and then click on the sidebar Appliance Setup

0020.PNG

Appliance Setup Fields

Setup Monitoring Device
AVNOC Appliance Host Name Host name is used for monitoring provisioning and phone home alerts.
If the monitored customers website is avnoc.com, then an appropriate host name would be psc07ts.avnoc.com for a device installation and appliance.avnoc.com for a virtual machine installation
YES
AVNOC Remote Update User ID This id is used by the panel to receive updates from avnoc.com using a secure connection YES
AVNOC Remote Update Password This id is used by the panel to receive updates from avnoc.com using a secure connection.
When browsing to the device this is password to be used to login.
YES
Apache monitoringadmin Administrative Customer Password Panel monitoringadmin Password. When browsing to the device this is password to be used to login. YES
Pin Number Pin number for support. The call in pin number is always 9901 when calling for service. The operator will ask you to confirm a portion of this pin for service. YES
LAN ETH0 Ip Address for ETH0 Monitoring Network Connection 1 - ETH0 IP Address. When viewing the back of the panel, ETH0 is the rj-45 jack on the far left. Enter a network IP address for the panel to reside on. The device must live on the network it is monitoring or have routing to it. YES
LAN ETH0 Network for ETH0 Monitoring Network Connection 1 - ETH0 Network. The device must live on the network it is monitoring or have routing to it. YES
LAN ETH0 Subnet Mask Network LAN Enter the ETH0 Subnet Mask YES
LAN ETH0 Gateway Network LAN Enter the ETH0 Gate Way YES
Network LAN ETH0 DNS Panel LAN Enter the ETH0 DNS Server. If you wish to use a FQDN (Fully Qualified Domain Name) rather than IP Address to locate devices for monitoring, you must provide a DNS Server for name lookups YES
LAN ETH1 Ip Address Monitoring Network Connection 2 - ETH1 IP Address. When viewing the back of the panel, ETH1 is the rj-45 jack second to left. Enter a network IP address for the panel to reside on. The device must live on the network it is monitoring or have routing to it.
If your networks are segmented this IP address will be used to access the device by secure https. Having a second network connection provides additional security as the person viewing the monitoring interface may not have access directly to that network, but can manage the monitoring instance. If a second network address is not specified, then the unit will boot to 192.168.0.100
NO
LAN ETH1 Network for ETH1 Monitoring Network Connection 2 - ETH1 Network. The device must live on the network it is monitoring or have routing to it. NO
Network LAN ETH1 Subnet Mask LAN Enter the ETH1 Subnet Mask NO
PSC07TS LAN ETH1 Gateway Network LAN Enter the ETH1 Gate Way NO
WAN ETH1 DNS LAN Enter the ETH1 DNS Server. If you wish to use a FQDN (Fully Qualified Domain Name) rather than IP Address to locate devices for monitoring, you must provide a DNS Server for name lookups NO
Time Server Enter the Time Server that this appliance will use for date and time synchronization. NO
SMTP Host Name Enter the smtp mail user domain for sending email from the Appliance ex: google.com or yahoo.com. This is used in the Appliance Setup. Use avnoc.com if unsure. YES
Last User NO
Last Date NO

Customer Time Periods

The default monitoring time period is 27x7, do not delete this entry.

Additional time periods can be entered to tell the appliance when to emit notices. For instance a walk in wall that operates from 08:00 to 18:00.

Select a customer and then click on the sidebar Time Periods

0021.PNG

Time periods can be migrated. First create a new time period, then migrate the old time period to the new period.

Time Period Fields

Time Periods
Field Value Required
Customer ID YES
Time Period Id YES
Time Period Alias Enter Alias of the time period definition. Spaces are not allowed! ex: 24x7 ex: Weekdays ex: Weekends Time periods are used to define when a device gets monitored and when notifications occur. A device can be monitored 24x7 and only report issues Weekdays, Weekdays may be defined as 06:00 - 18:00 a 12 hour sequence. YES
Sunday Start Monitoring Time Select the starting hour for monitoring and notification YES
Sunday End Monitoring Time Select the ending hour for monitoring and notification YES
Monday Start Monitoring Time Select the starting hour for monitoring and notification YES
Monday End Monitoring Time Select the ending hour for monitoring and notification YES
Tuesday Start Monitoring Time Select the starting hour for monitoring and notification YES
Tuesday End Monitoring Time Select the ending hour for monitoring and notification YES
Wednesday Start Monitoring Time Select the starting hour for monitoring and notification YES
Wednesday End Monitoring Time Select the ending hour for monitoring and notification YES
Thursday Start Monitoring Time Select the starting hour for monitoring and notification YES
Thursday End Monitoring Time Select the ending hour for monitoring and notification YES
Friday Start Monitoring Time Select the starting hour for monitoring and notification YES
Friday End Monitoring Time Select the ending hour for monitoring and notification YES
Saturday Start Monitoring Time Select the starting hour for monitoring and notification YES
Saturday End Monitoring Time Select the ending hour for monitoring and notification YES
Last User NO
Last Date NO

Customer Contact Groups

The default monitoring time period is 27x7, do not delete this entry.

Additional contact groups can be entered. It will contain override information the monitoring plan along member information. These members are slated for deprecation in lieu of host group overrides.

0022.PNG

Contact Group Fields

Contact Group
Field Value Required
Customer ID YES
Sequence YES
Contact Group Name Enter a contact group name. This will be assigned to each asset for notification purposes YES
Contact Group Alias Enter the alias for the contact group YES
Host Notifications Enabled Select True to enable host notifications YES
Host Notification Time Period Select the Host time period for host failure notification YES
Host Notification Options Select all of the notification options that apply YES
Host Notification Command Select a host notification cammand to be used to send alerts. Notification commands start with notify YES
Service Notifications Enabled Select True to enable service notifications YES
Service Notification Time Period Select the Service time period for host failure notification YES
Service Notification Options Select all of the notification options that apply YES
Service Notification Command Select a host notification cammand to be used to send alerts. Notification commands start with notify YES
Member 1 Enter the email address for this contact that will get notifications from the panel YES
Member 2 Enter the email address for this contact that will get notifications from the panel NO
Member 3 Enter the email address for this contact that will get notifications from the panel NO
Member 4 Enter the email address for this contact that will get notifications from the panel NO
Member 5 Enter the email address for this contact that will get notifications from the panel NO
Member 6 Enter the email address for this contact that will get notifications from the panel NO
Member 7 Enter the email address for this contact that will get notifications from the panel NO
Member 8 Enter the email address for this contact that will get notifications from the panel NO
Member 9 Enter the email address for this contact that will get notifications from the panel NO
Member 10 Enter the email address for this contact that will get notifications from the panel NO
Last User NO
Last Date NO


Contact groups can be migrated. First create a new contact group, then migrate the old contact group to the contact group.

Host Groups

The default monitoring time period is AVGEAR, do not delete this entry.

Host groups are used to group like devices for a customer into a top list.

0023.PNG

Host Groups Fields

Host Groups
Field Value Required
Customer ID YES
Sequence YES
Host Group Name Enter a host group name. This will be assigned to each asset for classifications purposes. Host group names are used to categorize printer, servers, DSP, Codec and so on for easy viewing from the panel web page YES
Host Group Alias Enter the alias for the host group YES
Host Group Email Override for Notices Select Email addresses here to override email processing on the Customer Master. An email selection here will cause all notices for this particular host group to be sent to the selection. NO
Last User NO
Last Date NO

Host groups can be migrated. First create a new host group, then migrate the old host group to the new host group.


Rooms

The default monitoring room is DEFAULT, do not delete this entry.

Rooms are used to define geo location data for an assets location.

0024.PNG

Room Fields

Rooms
Field Value Required
Customer ID YES
Sequence YES
Room Name Enter a name for the room EX: Small Conference Room YES
Room Location Enter the room location EX: 3rd Floor Room 303 YES
Response Time Per Contract NO
Address Enter the physical address location NO
City Enter the physical address city NO
State or Provence Enter the physical address state or provence NO
Postal code Enter the physical address zip or postal code NO
Last User NO
Last Date NO

Rooms can be migrated. First create a new room, then migrate the old room to the new room.

Makes and Models

The default make and model is AVGEAR, do not delete this entry.

Makes and models are used to define general manufacturer families. IE: Crestron.

0025.PNG

Make and Model Fields

Make and Model
Field Value Required
Customer ID YES
Sequence YES
Asset Make and Model Enter the Asset Manufacturer, Make and Model.
EX: NEC-NP200 for a Projector
CLEARONE-880-880T for a Clear One DSP Model Group
YES
Last User NO
Last Date NO

Makes and models can be migrated. First create a make and model, then migrate the make and model to the new make and model.

Assets

The default asset that AVNOC uses to setup monitoring is your web site.


0026.PNG

Asset Fields

Assets
Field Value Required
Customer Id YES
Sequence YES
Asset Type This selection creates the grouping on the panel HTML Display Page YES
Manufacturer and Model YES
Room Select the physical location that this asset is serviced. This is the primary sort field for the default asset display YES
Asset Alias Enter a short name for this asset. No spaces allowed. This field becomes the asset name in monitoring. Use a name like missing.yourdomain.com to ensure clarity. YES
FDQN or IP Address For security purposes, use a FQDN (Fully Qualified Domain Name) here.
For example put all of your devices on myname.local or myname.av
Contact your IT Departement and ask them to map your Equipment to DHCP boot to a static ip address for internal lookups.
If this asset is shelfed, notifications disabled, then enter SHELF for the IP address. Enter the IP Address of the device to be monitored. This directive is used to define the address of the host. Normally, this is an IP address, although it could really be anything you want (so long as it can be used to check the status of the host). You can use a FQDN to identify the host instead of an IP address, but if DNS services are not available this could cause problems
YES
Fully Qualified Http Access URL Example: http://192.168.0.2/admin, this field is used to cut and paste into a browser for device management NO
MIBS Port Select the MIBS port. ** check_snmp option -p ** The standard MIBS port is 161. If the device is setup to use a different port, select the correct port. Use this if you have activated MIBS on the target device. NO
MIBS Protocol Version Select the Version Number. ** check_snmp option -P ** This version number is the version number of snmp that the device uses. Use this if you have activated MIBS on the target device. NO
MIBS Community Enter the MIBS community. ** check_snmp option -C ** For version 1 and 2c of MIBS this is the unsecure password for the system. This is a password to the asset. Extreme Caution Use this if you have activated MIBS on the target device. V-1,2,3. NO
MIBS Authentication Protocol Select the authentication protocol for authentication.** check_snmp option -a ** Select MD5 or SHA as the authentication protocol for the community. Use this if you have activated MIBS on the target device. V-3 Only Devices. NO
MIBS Authentication Passphrase Enter the MIBS community pass phrase for authentication. ** check_snmp option -A ** Enter the pass pharase that the device is expecting. Use this if you have activated MIBS on the target device. V-3 Only Devices NO
MIBS Security Engine ID Select the Security Engine ID. ** check_snmp option -???Future Use ** Each SNMPv3 agent has an engine ID that uniquely identifies the agent in the device. The engine ID may be set by the network administrator and is unique to that internal network, alternatively, it may be pre-configured by the device manufacturer.. Use this if you have activated MIBS on the target device. V-3 Only Devices NO
MIBS Context Engine ID Select the Context Engine ID.** check_snmp option -???Future Use ** Contexts were really designed to allow talking through an agent to a remote device. You can also use them to distinguish overlapping data.. Use this if you have activated MIBS on the target device.V-3 Only Devices NO
MIBS Security Level Select the Security Level. ** check_snmp option -L **Use noAuthNoPriv for read only access, authNoPriv for authenticated read only access, or authPriv for full control Use this if you have activated MIBS on the target device. V-3 Only Devices NO
MIBS Context Name Enter the MIBS Context Name ex: bridge1 or enter the User name for CISCO Telnet Access ** Use this if you have activated MIBS on the target device. V-3 Only Devices NO
MIBS User Name Enter the MIBS Security Name. ** check_snmp option -U ** This is the user name defined on the device. Use this if you have activated MIBS on the target device. V-3 Only Devices NO
MIBS User Protocol Select the MIBS Protocol to use when sending the User Name. ** check_snmp option -x ** Select DES or AES depending on your device. Use this if you have activated MIBS on the target device. V-3 Only Devices NO
MIBS User Passphrase Enter the MIBS User Passphrase. Enter Telnet Password. ** check_snmp option -A ** This is the passphrase set on the device. Use this if you have activated MIBS on the target device. V-3 Only Devices NO
MIBS User Privileged Passphrase Enter the MIBS Privileged User Passphrase. ** check_snmp option -X ** This is the passphrase set on the device. Use this if you have activated MIBS on the target device. V-3 Only Devices NO
MIBS File For This Asset Use the Vendor Specific MIBS For this Asset. Upload a MIBS file if you have one. All Devices NO
Comments Enter any information about the assets that may help with monitoring and diagnostics NO
Firmware Revision Level Enter the Firmware Revision Level, enter Unknown if the revision level is not available NO
Serial Number For new installs enter the Assets serial number for warranty information and identification NO
Purchase Date For new Installs, enter the purchase date for warranty Tracking NO
Warranty Period For new installs, select the warranty period NO
Preventative Maintenance Select YES if this item is covered under a Preventative Maintenance Plan, this feature applies maily to projectors. NO
Preventative Maintenance Last Date Last Date of Preventative Maintenance. NO
Preventative Maintenance Notice Frequency Select the number of days for scheduled PM work on this device NO
Configuration File 1 Type Select the type of file being uploaded for file position 1 NO
Configuration File 1 Contents Security Alert!
If your configuration file contains user ids and passwords encrypt the file using a zip utility before uploading the configuration file!!!. Security Alert!
Upload or download the configuration file for this device
NO
Configuration File 2 Type Select the type of file being uploaded for file position 2 NO
Configuration File 2 Contents Security Alert!
If your configuration file contains user ids and passwords encrypt the file using a zip utility before uploading the configuration file!!!. Security Alert!
Upload or download the configuration file for this device
NO
Configuration File 3 Type Select the type of file being uploaded for file position 3 NO
Configuration File 3 Contents Security Alert!
If your configuration file contains user ids and passwords encrypt the file using a zip utility before uploading the configuration file!!!. Security Alert!
Upload or download the configuration file for this device
NO
In Service Date NO
Time Activity Added NO
Open Tickets NO
Closed Tickets NO
Service Exit Date NO
Service Exit Reason Select the reason for exiting this asset from service NO
Component ID External Interface The component id is used to provide a cross reference to external systems when reporting failures. This is the external systems asset id that AVNOC will report about. NO
MIBS History MIBS Notification History NO
Last User NO
Last Date NO

Asset Monitoring

The monitoring tab is accessed from the asset. Click on an asset to retrieve its monitoring parameters


0027.PNG

Asset Monitoring Fields

Asset Monitoring
Host Groups Select the Host Group that this asset belongs to. The web page on the panel is built using this directive to organize equipment types YES
Contact Group for Notification Select the contact group that notifications will be made to YES
Time Periods Select the time period for this device for monitoring and notifications YES
SNMP Commands Select batch snmp commmand to execute for this asset NO
SNMP Scan Of MIBS History Select string of data that if found in the SNMP MIBS History will generate an alert. Maintain these checks in WRDSNMPSCANS and be specific, general strings will generate false alerts NO
SNMP Scan Of MIBS History Omit From Logging Select string of data that if found in the SNMP MIBS History will be omitted from the log entry. Removes unwanted log entries before updating. NO
Host Notification Options This directive is used to determine when notifications for the host should be sent out. Valid options are a combination of one or more of the following: d = send notifications on a DOWN state, u = send notifications on an UNREACHABLE state, r = send notifications on recoveries (OK state), f = send notifications when the host starts and stops flapping, and s = send notifications when scheduled downtime starts and ends. If you specify n (none) as an option, no host notifications will be sent out. If you do not specify any notification options, monitoring will assume that you want notifications to be sent out for all possible states. Example: If you specify d,r in this field, notifications will only be sent out when the host goes DOWN and when it recovers from a DOWN state. YES
Service Notification Options This directive is used to determine when notifications for the host should be sent out. Valid options are a combination of one or more of the following: d = send notifications on a DOWN state, u = send notifications on an UNREACHABLE state, r = send notifications on recoveries (OK state), f = send notifications when the host starts and stops flapping, and s = send notifications when scheduled downtime starts and ends. If you specify n (none) as an option, no host notifications will be sent out. If you do not specify any notification options, monitoring will assume that you want notifications to be sent out for all possible states. Example: If you specify d,r in this field, notifications will only be sent out when the host goes DOWN and when it recovers from a DOWN state. YES
Notification Enabled Use this directive to enaable the asset for monitoring. If this assets notifications are not enabled then this assets will not be downloaded to the panel for monitoring.
When an asset is not notifying it is considered shelfed. This directive is used to determine whether or not notifications for this host are enabled. Values: 0 = disable host notifications, 1 = enable host notifications..
YES
Notification Interval This directive is used to define the number of time units to wait before re-notifying a contact that this service is still down or unreachable. Unless youâve changed the interval_length directive from the default value of 60, this number will mean minutes. If you set this value to 0, monitoring will not re-notify contacts about problems for this host - only one problem notification will be sent out... YES
First Notification Delay This directive is used to define the number of time units to wait before sending out the first problem notification when this host enters a non-UP state. Unless youâve changed the interval_length directive from the default value of 60, this number will mean minutes. If you set this value to 0, monitoring will start sending out notifications immediately... YES
Parents Please select from the list of routers and switches any uplink devices. This directive is used to define a comma-delimited list of short names of the parent hosts for this particular host. Parent hosts are typically routers, switches, firewalls, etc. that lie between the monitoring host and a remote hosts. A router, switch, etc. which is closest to the remote host is considered to be that hostâs parent. Read the Determining Status and Reachability of Network Hosts document located here for more information. If this host is on the same network segment as the host doing the monitoring (without any intermediate routers, etc.) the host is considered to be on the local network and will not have a parent host. Leave this value blank if the host does not have a parent host (i.e. it is on the same segment as the monitoring host). The order in which you specify parent hosts has no effect on how things are monitored.. NO
Host Check Command Select the check command that applies. This directive is used to specify the short name of the command that should be used to check if the host is up or down. Typically, this command would try and ping the host to see if it is alive. The command must return a status of OK (0) or monitoring will assume the host is down. If you leave this argument blank, the host will not be actively checked. Thus, monitoring will likely always assume the host is up (it may show up as being in a PENDING state in the web interface). This is useful if you are monitoring printers or other devices that are frequently turned off. The maximum amount of time that the notification command can run is controlled by the host_check_timeout option.. YES
Service Check Command Select the check command that applies. This directive is used to specify the short name of the command that should be used to check if the host is up or down. Typically, this command would try and ping the host to see if it is alive. The command must return a status of OK (0) or monitoring will assume the host is down. If you leave this argument blank, the host will not be actively checked. Thus, monitoring will likely always assume the host is up (it may show up as being in a PENDING state in the web interface). This is useful if you are monitoring printers or other devices that are frequently turned off. The maximum amount of time that the notification command can run is controlled by the host_check_timeout option.. YES
Initial State By default monitoring will assume that all hosts are in UP states when it starts. You can override the initial state for a host by using this directive. Valid options are: o = UP, d = DOWN, and u = UNREACHABLE.. YES
Check Interval This directive is used to define the number of time units between regularly scheduled checks of the host. Unless youâve changed the interval_length directive from the default value of 60, this number will mean minutes. More information on this value can be found in the check scheduling documentation.. YES
Retry Interval This directive is used to define the number of time units to wait before scheduling a re-check of the hosts. Hosts are rescheduled at the retry interval when they have changed to a non-UP state. Once the host has been retried max_check_attempts times without a change in its status, it will revert to being scheduled at its normal rate as defined by the check_interval value. Unless youâve changed the interval_length directive from the default value of 60, this number will mean minutes. More information on this value can be found in the check scheduling documentation. YES
Max Check Attempts This directive is used to define the number of times that monitoring will retry the host check command if it returns any state other than an OK state. Setting this value to 1 will cause monitoring to generate an alert without retrying the host check. Note: If you do not want to check the status of the host, you must still set this to a minimum value of 1. To bypass the host check, just leave the check_command option blank. YES
Active Checks Enabled This directive is used to determine whether or not active checks (either regularly scheduled or on-demand) of this host are enabled. Values: 0 = disable active host checks, 1 = enable active host checks (default).. YES
Passive Checks Enabled This directive is used to determine whether or not passive checks are enabled for this host. Values: 0 = disable passive host checks, 1 = enable passive host checks (default)... YES
Last User NO
Last Date NO


Assets Import


0028.PNG

Assets can be imported from a spreadsheet.

The best use case is to use the Task Manager to remove all assets, tickets and history for this customer.

Then Upload the assets csv file.

During the creation of the csv file please make sure there are no embedded commas. Punctuation is not really necessary here.

While importing assets certain things will happen:

  • Asset Types - will be created
  • Rooms - will be created
  • Makes and Models - will be created
  • Host Groups - will be created
  • Default Contact Group 24x7 will be used
  • Default Time Periods 24x7 will be used

Download the Asset Stub File

0029.PNG


Which can be opened by your favorite spreadsheet program.

Asset Stub File View

0030.PNG

There are some hints stored in the file which must be removed before uploading the file.

Asset Stub File Upload

0031.PNG

When the file is uploaded a presentation of field mapping is available. Map the csv fields to data base fields and

0032.PNG

When you are done press Process Import

Look at your assets and try to save a few of them, look at the monitoring tab.

If everything looks good lets make sure the environment will provision.

Provisioning

Provisioning is a process to check your work. It provides compile time errors for the system and alerts you of problems.

0033.PNG

Scroll to the bottom of the report

0034.PNG

There are other options available

Here are the highlights of the rest of the options:

  • UPC - setup sequenced power supplies that can reboot outlets using the agent
  • SNMP - setup SNMP command processing for a particular device
  • Monitoring Defaults - mass update monitoring parameters, use with caution.
  • Billing Setup - provide billing address information
  • Billing Tokens - provision and use billing tokens. These are reported in the EiS system
  • Contract - upload contact PDF to the system
  • Credit App - upload the credit app for the customer
  • Connections - interface for creating fields within the system

These sections need to be created.