Difference between revisions of "Main Page"

From AVNOC

 
(32 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>Remote Desktop Support Using Chrome Web Browser</h1>
 +
 +
For many support sessions Google Chrome provides a reasonable solution for remote desktop sharing for support incidents.
 +
 +
[[Chrome Desktop Support]]
  
 
<h1>Videos</h1>
 
<h1>Videos</h1>
Line 6: Line 12:
  
 
[[Instructional Videos]]
 
[[Instructional Videos]]
 +
 +
<h1>Training</h1>
 +
 +
Agendas for three training sessions.
 +
 +
* General concepts introduces AVNOC
 +
* Programming Crestron and Cisco
 +
* Support Gateway
 +
 +
[[Training Agendas]]
  
 
<h1>Browser Tips</h1>
 
<h1>Browser Tips</h1>
  
Everyone know how to use a browser.  These tips are meant to improve the AVNOC experience.
+
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.
 
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.
Line 17: Line 33:
 
<h1>Installing AVNOC</h1>
 
<h1>Installing AVNOC</h1>
  
Here are the work flow para metrics and the installation strategy used by AVNOC to deliver products to your network.  
+
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]]
 
[[Installing AVNOC]]
Line 24: Line 40:
 
<h1>Patching</h1>
 
<h1>Patching</h1>
  
Information on the patching process employed by AVNOC.
+
Information on the patching process and security updates employed by AVNOC.
  
 
[[Patching Process]]
 
[[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>
Line 72: Line 90:
 
* [[Monitoring AMX]]
 
* [[Monitoring AMX]]
 
* [[Monitoring Extron]]
 
* [[Monitoring Extron]]
 +
* [[Monitoring Samsung]]
 
* [[Monitoring Using SNMP Queries]]
 
* [[Monitoring Using SNMP Queries]]
 
* [[Monitoring Using SNMP Traps]]
 
* [[Monitoring Using SNMP Traps]]
 
* [[Monitoring Using Logs]]
 
* [[Monitoring Using Logs]]
 
* [[Monitoring Using POST Command ]]
 
* [[Monitoring Using POST Command ]]
 +
* [[Monitoring Windows Service Using Windows Agent]]
  
<h1>Managing Power</h1>
+
<h1>Hosting Portal</h1>
 +
 
 +
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.
 +
 
 +
<h2>Dash Board</h2>
 +
 
 +
Dash Board Consolidates Access For:
 +
 
 +
* Customer Centric View
 +
* Ticket Centric View
 +
* Map
 +
* Reports
 +
* Engineering
 +
 
 +
* [[DashBoard]]
 +
 
 +
 
 +
<h2>Engineering</h2>
 +
 
 +
Engineering is the core configuration system.  It is used to manage all aspects of monitoring.
 +
 
 +
* [[Engineering]]
 +
 
 +
<h3>Managing Time Periods</h3>
 +
 
 +
Time periods are used to indicate to the Agent when notices are to be emitted.
 +
 
 +
* [[Managing_Time_Periods]]
 +
 
 +
<h3>Managing Contact Groups</h3>
 +
 
 +
Contact groups are used when the Agent is using email as the notice mechanism.
 +
 
 +
* [[Managing Contact Groups]]
 +
 
 +
<h3>Managing Host Groups</h3>
 +
 
 +
Host Groups provide device type grouping.  It is used to apply monitoring defaults to groups of assets when needed.
 +
 
 +
* [[Managing Host Groups]]
 +
 
 +
<h3>Managing Rooms</h3>
 +
 
 +
Rooms provide location information for ticket processing.
 +
 
 +
* [[Managing Rooms]]
 +
 
 +
<h3>Managing Makes and Models</h3>
 +
 
 +
Makes and Models are used to define device family groupings
 +
 
 +
* [[Managing Makes and Models]]
 +
 
 +
<h3>Managing Onsite Providers</h3>
 +
 
 +
Onsite Providers establish PIN number access to the Service Console for field technicians and Plug-In for Customer Access.
 +
 
 +
* [[Managing Onsite Providers]]
 +
 
 +
<h3>Managing Assets</h3>
 +
 
 +
Assets are the basis for monitoring.
 +
 
 +
* [[Engineering#Assets]]
 +
 
 +
<h3>Managing Power</h3>
  
 
Powerful tool to be used as the first line of problem determination.
 
Powerful tool to be used as the first line of problem determination.
Line 85: Line 170:
 
* [[Managing Power]]
 
* [[Managing Power]]
  
<h1>Managing Messaging to Outside Service</h1>
+
<h3>Managing Messaging to Outside Service</h3>
 +
 
 
* [[Managing Outside Services]]
 
* [[Managing Outside Services]]
  
<h1>Managing Agent HTTPS Proxies</h1>
+
<h3>Managing Email Configurations</h3>
 +
 
 +
Email configuration provides access to back end server configuration parameters.
 +
 
 +
* [[Managing Email Configurations]]
 +
 
 +
<h3>Managing Agent HTTPS Proxies</h3>
  
 
Special considerations for setting up proxies in the customer network.
 
Special considerations for setting up proxies in the customer network.
Line 94: Line 186:
 
* [[Managing Agent HTTPS Proxies]]
 
* [[Managing Agent HTTPS Proxies]]
  
 +
<h3>Managing Agent DNS Reservations</h3>
 +
 +
How to use Customer DNS System to Monitor By DNS Name.
 +
 +
* [[Managing Agent DNS Reservations]]
 +
 +
 +
<h1>MPLS Ready Kernels</h1>
 +
 +
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]]
  
 
<h1>Daily Notices</h1>
 
<h1>Daily Notices</h1>

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