Difference between revisions of "Main Page"

From AVNOC

 
(45 intermediate revisions by the same user not shown)
Line 1: Line 1:
<strong>AVNOC provides a secure monitoring framework.</strong>
+
<strong>AVNOC Provides a Secure Monitoring Framework.</strong>
  
<h1>Instructional Videos</h1>
+
<h1>Remote Desktop Support Using Chrome Web Browser</h1>
  
A brief introduction to what role the Agent Plays in the monitoring plan.
+
For many support sessions Google Chrome provides a reasonable solution for remote desktop sharing for support incidents.
  
[http://avnoc.com/videos/agent.mp4 | Agent Introduction ]
+
[[Chrome Desktop Support]]
  
Introduction on hosting scenarios.
+
<h1>Videos</h1>
  
[http://avnoc.com/videos/hosting.mp4 | Hosting Introduction ]
+
The instructional videos are highly compressed. Keep you pointer on the pause button to stop these videos.
  
Having trouble Logging In?
+
[[Instructional Videos]]
  
[http://avnoc.com/videos/login.mp4 | Login Help ]
+
<h1>Training</h1>
  
<h1>Browser Tips</h1>
+
Agendas for three training sessions.
  
To find things on a web page use CTRL-F (CONTROL-F).
+
* General concepts introduces AVNOC
 +
* Programming Crestron and Cisco
 +
* Support Gateway
  
To Enlarge test use CTRL+ (CONROL-PLUS)
+
[[Training Agendas]]
To Decrease Text use CTRL- (CONTROL-MINUS)
 
  
<h1>Browser Cache Settings</h1>
+
<h1>Browser Tips</h1>
 
 
Most browsers think they are smarter than the user and want to cache certain portions of a web page and present them to the user.
 
This does not work for dynamic web applications that use java script to build web pages. AVNOC is java script based and requires the browser cache to be turned off.
 
 
 
<h2>Turn Chrome Cache Off</h2>
 
 
 
There are two more options to disable page caching in Chrome for good:
 
 
 
<h3>Deactivate Chrome Cache in the Registry</h3>
 
 
 
Open Registry (Start -> Command -> Regedit)
 
 
 
Search for: HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command
 
 
 
Change the part after ...chrome.exe" to this value:  –disable-application-cache –media-cache-size=1 –disk-cache-size=1 — "%1"
 
 
 
Example: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -disable-application-cache –media-cache-size=1 –disk-cache-size=1 — "%1"
 
 
 
IMPORTANT:
 
 
 
there is a space and a hyphen after ...chrome.exe"
 
leave the path to chrome.exe as it is
 
If you copy the line, be sure to check, if the quotes are actual quotes.
 
 
 
<h3>Deactivate Chrome cache by changing the shortcut properties</h3>
 
 
 
Open Windows Start Menu
 
 
 
Find Chrome Shortcut
 
 
 
Right Click on Properties
 
 
 
Right-click on the Chrome icon and select "Properties" in the context menu. Add following value to the path:  –disk-cache-size=1
 
 
 
Example: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" –disk-cache-dir=null
 
 
 
IMPORTANT:
 
 
 
there is a space and a hyphen after ...chrome.exe"
 
leave the path to chrome.exe as it is
 
  
<h2>Turn Firefox Cache Off</h2>
+
Everyone knows how to use a browser.  These tips are meant to improve the AVNOC experience.
  
1. enter about:config in the url bar
+
There are also some hints on what to do to disable browser cacheing. Browser cacheing needs to be disabled so your web browser ALWAYS loads the page from the site.
2. Find browser.cache.disk.enable (Non Private Browsing)
 
2.1 Click to toggle value to false
 
  
<h2>Turn Internet Explorer Cache Off</h2>
+
[[Browser Tips]]
Click on Tools
 
Click on Settings
 
Click on Every time I visit the webpage
 
  
 
<h1>Installing AVNOC</h1>
 
<h1>Installing AVNOC</h1>
  
AVNOC is delivered as:
+
Here are the work flow para metrics and the installation strategy used by AVNOC to deliver products to your network or your customers network.  
 
 
* Hardware Agent: Pre-configured to be plug and play once it lands in the customers network.
 
* Software Agent: ISO Installer Pre-configured to be plug and play once it lands in the customers network.
 
* Hosting Portal: ISO Installer Pre-configured to be plug and play once it lands in the customers network.
 
* Support Gateway: ISO Installer Pre-configured to be plug and play once it lands in the customers network. Require final configuration once installed.
 
 
 
<h2>ISO Installer</h2>
 
 
 
Our installer is a DISK DRIVE DUPLICATOR. The bootable iso uses Clonezilla to copy a disk drive image from our servers to a VM or Bare Metal device in your environment.
 
 
 
<h2>Misconceptions</h2>
 
 
 
* It is not w Windows Installer. It can be installed under windows HyperVisor.
 
* It is not a RedHat RPM. It is a current version Debian Install.
 
* It is not a Linux Debian Package.
 
 
 
<h2>Why a Disk Image</h2>
 
 
 
Disk images are compatible across multiple VM strategies including VM Ware, Citrix XEN and Bare Metal installations.
 
 
 
<h2>Questions about OVA's</h2>
 
 
 
Why not use an OVA?
 
 
 
OVA installations are huge, the size of the hard drive.  OVA files are not cross compatible between Citrix and VM Ware.
 
 
 
Moving huge files around are not an option using our installation we achieve small file sizes and cross platform compatibility.
 
  
<h1>OS Patching</h1>
+
[[Installing AVNOC]]
  
Hosting Portals and Agents are patched daily using an automated script. OS and Security patches are included. It may take a little longer for some processes to update but it time well spent.
 
  
Automating the patching process without any intervention was a requirement.
+
<h1>Patching</h1>
  
<h1>Application Patches</h1>
+
Information on the patching process and security updates employed by AVNOC.
 
 
We have a 6 month release cycle for platform updates.
 
 
 
Security patches are rolled out as needed.
 
 
 
Bug fixes are rolled out as needed.
 
  
 +
[[Patching Process]]
  
 +
<h1>Steps After Initial Server Installation</h1>
 +
[[Installation Steps]]
  
 
<h1>Best Practices for End Customer Setup</h1>
 
<h1>Best Practices for End Customer Setup</h1>
  
On boarding the end customer is crucial.  End customers come in different levels of experience and can be a hindrance  when trying to implement AVNOC.  Customers are looking to the dealer for taking a role in ensuring a successful monitoring solution.
+
Some bits of information we have cataloged over the years to improve the experience.  
  
 +
[[Best Practices]]
  
<h2>Manage DCHP Reservation System for Asset Management</h2>
+
<h1>On Boarding Dealers Agents Hosting Portals and Support Gateways</h1>
  
* Setup target device for DHCP BOOT, can be endpoints for direct monitoring
+
Step by step instructions and guidelines.
* Put Program On
 
* Ask for DHCP Reservation From Customer For target MAC ID and IP Subnet of the RJ45 Jack
 
* Update Target Device with Host Name Assigned By Customer
 
* Move Target Device to Customer Once Reservation is Complete
 
* [[https://wiki.avnoc.com/index.php/Main_Page#Agent_Commands | Test Device During Installation]]
 
  
 +
[[On Boarding]]
  
 +
<h1>General Guide Lines</h1>
  
 +
* [[Introduction]]
 +
* [[Networking]]
 +
* [[Security]]
 +
* [[Applications]]
  
<h2>Obtaining a List of Assets to Monitor</h2>
+
<h2>Server - Agent - Gateway - Details</h2>
  
Some customers may already have the needed information available in electronic form.  
+
Installation details and deployment strategies.
  
Customers with lists are the easiest to on board because we can use their data for importing into the asset data base with some modifications to make a correct CSV file.
+
* [[Server Requirements]]
 +
* [[Load Balancing]]
 +
* [[Server Installation]]
 +
* [[Agent Requirements]]
 +
* [[Agent Installation]]
 +
* [[Support Gateway Requirements]]
 +
* [[Support Gateway Installation]]
  
However, we have found the lists to be out of date and may a general guideline for assets in the building.
+
<h1>Device Family Monitoring Use Cases</h1>
  
The best method for on boarding customers is to perform a site survey, fixing things that need to be fixed along the wayThings like authentication in setting up a secure environment should be fixed during the survey.
+
What can be monitored in generalVendors like to break firmware, so use this as a general guide.
  
During the site survey the asset can be populated for monitoring into the hosting portal.
+
* [[Monitoring a VLAN]]
 +
* [[Monitoring a Stand Alone Room]]
 +
* [[Monitoring Crestron]]
 +
* [[Monitoring Crestron Fusion]]
 +
* [[Monitoring Cisco]]
 +
* [[Monitoring Polycom]]
 +
* [[Monitoring AMX]]
 +
* [[Monitoring Extron]]
 +
* [[Monitoring Samsung]]
 +
* [[Monitoring Using SNMP Queries]]
 +
* [[Monitoring Using SNMP Traps]]
 +
* [[Monitoring Using Logs]]
 +
* [[Monitoring Using POST Command ]]
 +
* [[Monitoring Windows Service Using Windows Agent]]
  
<h3>Site Survey Tools for Network Scanning</h3>
+
<h1>Hosting Portal</h1>
  
Scanning a customers network should be performed with care. The customer may employ intrusion detection and scanning will cause intrusion detection to black list the Agent.
+
The hosting portal is the end point where the agents communicate their monitoring results. It is usually accessed via DNS name lookup for public facing systems and by permanent ip address or internal dns internal name lookup for private systems.  All of the configuration and ticket management functions are included here.
  
It is safe to scan a private network.  If your AV is on a private network say: 192.168.1.XXX, then it is safe to scan the network to obtain the current ip address on the sub net.
+
<h2>Dash Board</h2>
  
Here is a Windows based IP scanner [[https://nmap.org/download.html#windows| NMAP IP Address Scanner]]. We use the command line version of this by creating a shortcut to cmd in the installation zip folder and setting its properties to start in the same folder.  Run nmap to get the options and start scanning.
+
Dash Board Consolidates Access For:
  
A sample scan of the 192.168.15 sub net would be nmap -sn 192.168.15.0-255.
+
* Customer Centric View
 +
* Ticket Centric View
 +
* Map
 +
* Reports
 +
* Engineering
  
This will reveal all ip address that answer for ping.  Some of the ip addresses will have net bios names and some will not.  This is the down fall of scanning a network, but it is a good starting point.  Also, take into consideration that some devices may be DHCP boot and the IP address will not be the same after a power reset.
+
* [[DashBoard]]
  
The information from the scanner can be used to populate Assets.
 
  
<h3>Fixing Setup During Survey</h3>
+
<h2>Engineering</h2>
  
* Enable SSH Login for supported devices to retrieve log filesAt the time of this writing, Cisco, Polycom (Telnet) Lifesize and Crestron are some of the devices which the log files can be retrieved.
+
Engineering is the core configuration systemIt is used to manage all aspects of monitoring.
  
* Enable SNMP on Crestron in Toolbox and send traps to Agent.  Useful for OS related trapping only.
+
* [[Engineering]]
  
* Enable SNMP on other devices for Trapping
+
<h3>Managing Time Periods</h3>
  
* Setup permanent IP address for those devices which are DHCP
+
Time periods are used to indicate to the Agent when notices are to be emitted.
  
Preparing a room for monitoring is a very important step.
+
* [[Managing_Time_Periods]]
  
In some cases where there was no network connectivity to the corporate LAN, a bridge needs to be made between the private LAN to the corporate LAN.
+
<h3>Managing Contact Groups</h3>
  
We suggest using a router to bridge the networks. See [[https://wiki.avnoc.com/index.php/Monitoring_a_Stand_Alone_Room: this]] for details.
+
Contact groups are used when the Agent is using email as the notice mechanism.
  
The end customer is looking to the dealer for guidance.  Establishing a leading position ensures a successful relationship and add on business in the future.
+
* [[Managing Contact Groups]]
  
Most end customers do not understand networking, which is a crucial ingredient for pushing monitoring events to a hosting portal. The hosting portal takes care of ticket management and notification.
+
<h3>Managing Host Groups</h3>
  
Dealers that establish their knowledge in secure networking will be rewarded with continuing business.
+
Host Groups provide device type grouping.  It is used to apply monitoring defaults to groups of assets when needed.
  
<h2>Handling Engineering Changes</h2>
+
* [[Managing Host Groups]]
  
Once a network has been analyzed and a monitoring plan established, change orders play a big role.
+
<h3>Managing Rooms</h3>
  
Some changes are transparent such as equipment swap out using the same parameters as original equipment.
+
Rooms provide location information for ticket processing.  
  
Challenging changes are ones where additional equipment is placed in the customers network.  This equipment requires on boarding into the hosting portal.
+
* [[Managing Rooms]]
  
<h2>Ip Requests for Agent</h2>
+
<h3>Managing Makes and Models</h3>
  
We usually operate in an environment where SNMP traps will be sent to the Agent. Using SNMP trapping requires am Agent with a permanent IP address.  If this is not the case then the device can be setup with a DHCP boot option.
+
Makes and Models are used to define device family groupings
  
<h2>Customer Firewall Rules</h2>
+
* [[Managing Makes and Models]]
  
It is VERY important to make sure that the network that the Agent is on can reach the Hosting Portal Port 443 HTTPS.  Outbound connections to the hosting portal is all that is required.
+
<h3>Managing Onsite Providers</h3>
  
<h2>Agent Commands</h2>
+
Onsite Providers establish PIN number access to the Service Console for field technicians and Plug-In for Customer Access.
  
It is recommended to make sure everything is operating as expected during the installation process.
+
* [[Managing Onsite Providers]]
  
The Agent will contact the Hosting Portal upon power on.  This can be verified by logging into the portal and seeing if the last check alive date is recent.
+
<h3>Managing Assets</h3>
  
There are some situations that require a forced download and phonehome from the Agent to make sure Crestron, Cisco, etc are communicating with the portal and the local device.
+
Assets are the basis for monitoring.  
  
Use putty [[http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html?| Download putty.exe]] and run it on your windows desktop.
+
* [[Engineering#Assets]]
  
Putty Tips
+
<h3>Managing Power</h3>
  
Right click the title bar to start another session.
+
Powerful tool to be used as the first line of problem determination.
  
Save your connections for recall.
+
Reboot customer equipment plugged into a SNMP capable power unit.
  
Change the number of scroll back line
+
* [[Managing Power]]
  
[[File:5004.PNG|640px]]
+
<h3>Managing Messaging to Outside Service</h3>
  
Change the font size
+
* [[Managing Outside Services]]
  
[[File:5005.PNG|640px]]
+
<h3>Managing Email Configurations</h3>
  
Connect to the Agent IP Address and logon.
+
Email configuration provides access to back end server configuration parameters.
  
<h3>Force a Download to get current monitoring information</h3>
+
* [[Managing Email Configurations]]
  
Enter /opt/bin/download PRESS ENTER KEY
+
<h3>Managing Agent HTTPS Proxies</h3>
  
<h3>Force a Phone Home which does discovery of your Crestron SNMP Devices</h3>
+
Special considerations for setting up proxies in the customer network.
  
Enter /opt/bin/phonehome PRESS ENTER KEY
+
* [[Managing Agent HTTPS Proxies]]
  
Once the download and phone home are completed check the hosting portal in about 30 minutes to see if the Crestron devices populated and the log files are retrieved for those assets which can be accessed.
+
<h3>Managing Agent DNS Reservations</h3>
  
 +
How to use Customer DNS System to Monitor By DNS Name.
  
<h3>Change IP Address of Agent</h3>
+
* [[Managing Agent DNS Reservations]]
  
Exercise great caution here.  If your foul the network setting up, you will need to connect a USB keyboard and HDMI monitor to repair the settings.
 
  
Make sure the hosting portal Appliance Setup is changed to match.
+
<h1>MPLS Ready Kernels</h1>
  
Login in using putty and
+
MPLS (Multi Protocol Label Switching) is an emerging standard for telecommunications.  It directs data from from one network node to the next based on short path labels rather than long network address.  This avoids comples lookups in a routing table.  MPSL can encapsulate packets of network protocols.
  
Type nano /etc/network/interfaces PRESS ENTER
+
It is used to eliminate DDOS Attacks. The AVNOC Software Agent employs a MPLS kernel in case it is expected to act as a node in a MPLS network.
  
[[File:5000.PNG|640px]]
+
[[Managing a MPLS Connection]]
  
Edit the settings
+
<h1>Daily Notices</h1>
 
 
[[File:5001.PNG|640px]]
 
 
 
Use the cursor keys to navigate the settings and change the necessary values
 
 
 
Press CTRL-X to exit the editing session
 
 
 
[[File:5002.PNG|640px]]
 
 
 
Enter Y to save the file Press enter
 
 
 
Type service network restart to execute the changes
 
 
 
Log out of Agent then Log in again to work with the Agent on the new IP Address
 
 
 
[[File:5003.PNG|640px]]
 
 
 
After changing the IP address use putty to log in to the new IP address
 
 
 
 
 
<h1>On Boarding Dealers Agents Hosting Portals and Support Gateways</h1>
 
 
 
Use this form [[Special:Contact|IP Information Form]] to submit information for setup.
 
 
 
AVNOC delivers plug and play Hosting Portals and Agents.
 
 
 
When we on board a new customer a form is sent to the particular parties to be filled out. We use this information in the production process to notify you of the mac id and initial authentication.  When you send the data back, we can complete the build and deliver the product to you.
 
 
 
<h2>Server Data Fields Definitions</h2>
 
{| class="wikitable"
 
! colspan="3"|Server Properties
 
|-
 
! style="text-align:center;"| Field
 
! style="text-align:center;"| Value
 
! style="text-align:center;"| Chain
 
|-
 
| Server Mac ID
 
|
 
| AVNOC When Server is Initialized
 
|-
 
| Server IP Address
 
 
| Customer when MAC ID Received
 
|-
 
| Server IP Network
 
| ____________________________________________
 
| Customer when MAC ID Received
 
|-
 
| Server IP Netmask
 
| ____________________________________________
 
| Customer when MAC ID Received
 
|-
 
| Server IP Gateway
 
| ____________________________________________
 
| Customer when MAC ID Received
 
|}
 
 
 
<h3>Server Mail Processing</h3>
 
{| class="wikitable"
 
! colspan="3"|Server Mail Properties
 
|-
 
! style="text-align:center;"| Field
 
! style="text-align:center;"| Value
 
! style="text-align:center;"| Chain
 
|-
 
| Mail Server
 
| ____________________________________________
 
| Customer when MAC ID is Received
 
|-
 
| Mail User ID
 
| ____________________________________________
 
| Customer when MAC ID Received
 
|-
 
| Mail Password
 
| ____________________________________________
 
| Customer when MAC ID Received
 
|}
 
 
 
<h2>Agent Data Fields Definitions</h2>
 
{| class="wikitable"
 
! colspan="3"|Agent Properties
 
|-
 
! style="text-align:center;"| Field
 
! style="text-align:center;"| Value
 
! style="text-align:center;"| Chain
 
|-
 
| Agent Mac ID
 
| ____________________________________________
 
| AVNOC When Server is Initialized
 
|-
 
| Agent IP Address
 
| ____________________________________________
 
| Customer when MAC ID Received can be DHCP
 
|-
 
| Agent IP Network
 
| ____________________________________________
 
| Customer when MAC ID Received
 
|-
 
| Agent IP Netmask
 
| ____________________________________________
 
| Customer when MAC ID Received
 
|-
 
| Agent IP Gateway
 
| ____________________________________________
 
| Customer when MAC ID Received
 
|}
 
 
 
<h1>Software Downloads Definitions</h1>
 
{| class="wikitable"
 
! colspan="3"|Download Properties
 
|-
 
! style="text-align:center;"| Field
 
! style="text-align:center;"| Value
 
! style="text-align:center;"| Chain
 
|-
 
| Download ISO Location
 
| ____________________________________________
 
| AVNOC after IP Data Received
 
|-
 
| Download User ID
 
| ____________________________________________
 
| AVNOC after IP Data Received
 
|-
 
| Download Password
 
| ____________________________________________
 
| AVNOC after IP Data Received
 
|-
 
| Download Server
 
| ____________________________________________
 
| AVNOC after IP Data Received
 
|}
 
 
 
 
 
<h1>Application User ID Definitions</h1>
 
{| class="wikitable"
 
! colspan="3"|User ID Hosting Portal
 
|-
 
! style="text-align:center;"| Field
 
! style="text-align:center;"| Value
 
! style="text-align:center;"| Chain
 
|-
 
| Application User ID
 
| ____________________________________________
 
| AVNOC after server is built
 
|-
 
| Application Password
 
| ____________________________________________
 
| AVNOC after server is built
 
|-
 
| Application Password
 
| ____________________________________________
 
| AVNOC after server is built
 
|-
 
| Application Pin Number
 
| ____________________________________________
 
| AVNOC after server is built
 
|}
 
 
 
We pass information back and forth the first phase lets you know the MAC ID of the device. This is usefull for IT Departments for setting up fire wall rules and provisioning.
 
 
 
After we notify the MAC ID, fill out relevant data concerting IP and mail processing(only for server)
 
 
 
When we have the returned information, the server/agent will be provisioned or shipped.  For software products, we provide an installation iso.  This ISO can be placed in a vm repository or written to a cd.  The ISO is booted and the software image is placed on the booting computer.
 
 
 
<h1>General Guide Lines</h1>
 
  
* [[Introduction]]
+
Here comes the spam, well not really.
* [[Networking]]
 
* [[Security]]
 
* [[Applications]]
 
  
<h2>Server - Agent - Gateway - Details</h2>
 
 
* [[Server Requirements]]
 
* [[Load Balancing]]
 
* [[Server Installation]]
 
* [[Agent Requirements]]
 
* [[Agent Installation]]
 
* [[Support Gateway Requirements]]
 
* [[Support Gateway Installation]]
 
 
<h1>Device Family Monitoring Use Cases</h1>
 
 
* [[Monitoring a VLAN]]
 
* [[Monitoring a Stand Alone Room]]
 
* [[Monitoring Crestron]]
 
* [[Monitoring Crestron Fusion]]
 
* [[Monitoring Cisco]]
 
* [[Monitoring Polycom]]
 
* [[Monitoring AMX]]
 
* [[Monitoring Extron]]
 
* [[Monitoring Using SNMP Queries]]
 
* [[Monitoring Using SNMP Traps]]
 
* [[Monitoring Using Logs]]
 
* [[Monitoring Using POST Command ]]
 
 
<h1>Managing Power</h1>
 
* [[Managing Power]]
 
 
<h1>Managing Messaging to Outside Service</h1>
 
* [[Managing Outside Services]]
 
 
<h1>Managing Agent HTTPS Proxies</h1>
 
* [[Managing Agent HTTPS Prooxies]]
 
 
 
<h1>Daily Notices</h1>
 
 
* [[Notices Sent Daily]]
 
* [[Notices Sent Daily]]
  
 
<h1>Selling to End Users</h1>
 
<h1>Selling to End Users</h1>
 
* [[Strategies]]
 
* [[Strategies]]

Latest revision as of 19:16, 1 October 2018

AVNOC Provides a Secure Monitoring Framework.

Remote Desktop Support Using Chrome Web Browser

For many support sessions Google Chrome provides a reasonable solution for remote desktop sharing for support incidents.

Chrome Desktop Support

Videos

The instructional videos are highly compressed. Keep you pointer on the pause button to stop these videos.

Instructional Videos

Training

Agendas for three training sessions.

  • General concepts introduces AVNOC
  • Programming Crestron and Cisco
  • Support Gateway

Training Agendas

Browser Tips

Everyone knows how to use a browser. These tips are meant to improve the AVNOC experience.

There are also some hints on what to do to disable browser cacheing. Browser cacheing needs to be disabled so your web browser ALWAYS loads the page from the site.

Browser Tips

Installing AVNOC

Here are the work flow para metrics and the installation strategy used by AVNOC to deliver products to your network or your customers network.

Installing AVNOC


Patching

Information on the patching process and security updates employed by AVNOC.

Patching Process

Steps After Initial Server Installation

Installation Steps

Best Practices for End Customer Setup

Some bits of information we have cataloged over the years to improve the experience.

Best Practices

On Boarding Dealers Agents Hosting Portals and Support Gateways

Step by step instructions and guidelines.

On Boarding

General Guide Lines

Server - Agent - Gateway - Details

Installation details and deployment strategies.

Device Family Monitoring Use Cases

What can be monitored in general. Vendors like to break firmware, so use this as a general guide.

Hosting Portal

The hosting portal is the end point where the agents communicate their monitoring results. It is usually accessed via DNS name lookup for public facing systems and by permanent ip address or internal dns internal name lookup for private systems. All of the configuration and ticket management functions are included here.

Dash Board

Dash Board Consolidates Access For:

  • Customer Centric View
  • Ticket Centric View
  • Map
  • Reports
  • Engineering


Engineering

Engineering is the core configuration system. It is used to manage all aspects of monitoring.

Managing Time Periods

Time periods are used to indicate to the Agent when notices are to be emitted.

Managing Contact Groups

Contact groups are used when the Agent is using email as the notice mechanism.

Managing Host Groups

Host Groups provide device type grouping. It is used to apply monitoring defaults to groups of assets when needed.

Managing Rooms

Rooms provide location information for ticket processing.

Managing Makes and Models

Makes and Models are used to define device family groupings

Managing Onsite Providers

Onsite Providers establish PIN number access to the Service Console for field technicians and Plug-In for Customer Access.

Managing Assets

Assets are the basis for monitoring.

Managing Power

Powerful tool to be used as the first line of problem determination.

Reboot customer equipment plugged into a SNMP capable power unit.

Managing Messaging to Outside Service

Managing Email Configurations

Email configuration provides access to back end server configuration parameters.

Managing Agent HTTPS Proxies

Special considerations for setting up proxies in the customer network.

Managing Agent DNS Reservations

How to use Customer DNS System to Monitor By DNS Name.


MPLS Ready Kernels

MPLS (Multi Protocol Label Switching) is an emerging standard for telecommunications. It directs data from from one network node to the next based on short path labels rather than long network address. This avoids comples lookups in a routing table. MPSL can encapsulate packets of network protocols.

It is used to eliminate DDOS Attacks. The AVNOC Software Agent employs a MPLS kernel in case it is expected to act as a node in a MPLS network.

Managing a MPLS Connection

Daily Notices

Here comes the spam, well not really.

Selling to End Users