Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Wake on LAN > Scenario 3: Using an Application Role Server to Manage Console Connections

Scenario 3: Using an Application Role Server to Manage Console Connections

Table of contents
No headers
Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 44 Votes: 0 Revisions: 4

A typical example of this scenario is using multiple Application role servers to manage a large number of console connections. This example also serves to address High Availability (HA) requirements. For the HA scenario, deploy at least three Application role servers:

  • The PAS, which Patch Manager does not use for console connections.
  • At least two Secondary Application Servers (SAS), which can segregate groups of console users and/or back one another up in case of a failure.

Additional Application Role Servers for High Availability (HA)

File:Success_Center/New_Articles/PatchManager_Admin_Guide_MT/0F0/0D0/0300000B_427x382.png

This HA scenario scales to as many Application role servers as you require. If necessary, each console user could have a dedicated Application role server for their console connection.

Last modified
01:13, 23 Jun 2016

Tags

Classifications

Public