Difference between revisions of "Main Page"

From AVNOC

 
(36 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>
 +
 +
The instructional videos are highly compressed.  Keep you pointer on the pause button to stop these videos.
  
 
[[Instructional Videos]]
 
[[Instructional Videos]]
  
<h1>Browser Tips</h1>
+
<h1>Training</h1>
  
[[Browser Tips]]
+
Agendas for three training sessions.
  
<h1>Installing AVNOC</h1>
+
* General concepts introduces AVNOC
 +
* Programming Crestron and Cisco
 +
* Support Gateway
  
[[Installing AVNOC]]
+
[[Training Agendas]]
  
 +
<h1>Browser Tips</h1>
  
<h1>Patching</h1>
+
Everyone knows how to use a browser.  These tips are meant to improve the AVNOC experience.
  
[[Patching Process]]
+
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]]
  
<h1>Best Practices for End Customer Setup</h1>
+
<h1>Installing AVNOC</h1>
  
[[Best Practices]]
+
Here are the work flow para metrics and the installation strategy used by AVNOC to deliver products to your network or your customers network.
<h1>On Boarding Dealers Agents Hosting Portals and Support Gateways</h1>
 
  
Use this form [[Special:Contact|IP Information Form]] to submit information for setup.
+
[[Installing AVNOC]]
  
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.
+
<h1>Patching</h1>
  
<h2>Server Data Fields Definitions</h2>
+
Information on the patching process and security updates employed by AVNOC.
{| 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>
+
[[Patching Process]]
{| 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>
+
<h1>Steps After Initial Server Installation</h1>
{| class="wikitable"
+
[[Installation Steps]]
! 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>
+
<h1>Best Practices for End Customer Setup</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
 
|}
 
  
 +
Some bits of information we have cataloged over the years to improve the experience.
  
<h1>Application User ID Definitions</h1>
+
[[Best Practices]]
{| 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.
+
<h1>On Boarding Dealers Agents Hosting Portals and Support Gateways</h1>
  
After we notify the MAC ID, fill out relevant data concerting IP and mail processing(only for server)
+
Step by step instructions and guidelines.
  
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.
+
[[On Boarding]]
  
 
<h1>General Guide Lines</h1>
 
<h1>General Guide Lines</h1>
Line 174: Line 67:
  
 
<h2>Server - Agent - Gateway - Details</h2>
 
<h2>Server - Agent - Gateway - Details</h2>
 +
 +
Installation details and deployment strategies.
  
 
* [[Server Requirements]]
 
* [[Server Requirements]]
Line 184: Line 79:
  
 
<h1>Device Family Monitoring Use Cases</h1>
 
<h1>Device Family Monitoring Use Cases</h1>
 +
 +
What can be monitored in general.  Vendors like to break firmware, so use this as a general guide.
  
 
* [[Monitoring a VLAN]]
 
* [[Monitoring a VLAN]]
Line 193: 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>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.
 +
 +
Reboot customer equipment plugged into a SNMP capable power unit.
  
<h1>Managing Power</h1>
 
 
* [[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>
* [[Managing Agent HTTPS Prooxies]]
+
 
 +
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.
 +
 
 +
* [[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>
 +
 +
Here comes the spam, well not really.
 +
 
* [[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