Juniper MEDIA FLOW MANAGER 2.0.2 - ADMINISTRATOR S GUIDE AND CLI, Руководство администратора

Страница: 27 / 156

Central Management Console 27
Media Flow Manager Administrator’s Guide CHAPTER 2 Media Flow Manager Overview
Central Management Console
This section describes how the Central Management Console (CMC) works; first, terminology:
•
Media Flow Manager Server: The machine running the CMC software managing clients.
•
CMC Client: The software on a Media Flow Controller being managed by a CMC server.
•
CMC Rendezvous: A way to establish the connection between the CMC server and the
CMC client. In this method the Media Flow Controller is pre-configured with the CMC
server information and when the Media Flow Controller comes up it requests connectivity
to the CMC; on the CMC you authorize the Media Flow Controller and the connection gets
established. The other method for connectivity is explicitly configuring the Media Flow
Controller information on the CMC.
The CMC function of Media Flow Manager is server-client based. You configure the CMC
server with a list of Media Flow Controller appliances and it runs the Remote Box
Management Daemon (RBMD). In the standard server-initiated connection scenario, the CMC
server is configured with a means of logging into an administrator account on each client
Media Flow Controller using a password, or SSH v2 RSA or DSA keys, opening a connection,
and proxying requests between the two.
In the client-initiated connection scenario, the Media Flow Controller CMC client logs into the
CMC server using a password, or SSH v2 RSA or DSA keys, opens a connection, and the
same lines of communication are established as with the server-initiated connection.
Some of CMC’s management tasks are accomplished through requests that are proxied.
Other tasks are accomplished by sending the client lists of CLI commands that are executed
locally.
Appliances (Media Flow Controllers)
An appliance represents a single remote system that the CMC manages. It contains the
address of the system, and credentials that can be used to log into it. The credentials may
either be a password, or the name of an identity record (see
“Identities," below), depending on
which authentication type is selected. Each authentication type can specify with a username to
log in as; the user specified should have administrative privileges for the CMC to manage the
appliance correctly;
admin
is the default user. Note that for client-initiated connections, the
server does not need these credentials in the appliance record. The central administrator sets
up one or more local accounts for the clients to log into, and gives this login information to the
remote administrators.
Groups
A group record contains references to any number of appliance records. Any action that can
be performed on an appliance, such as applying a profile (executing a set of CLI commands),
can also be performed on a group. An appliance may belong to any number of groups. There
is one reserved group,
all
, which is automatically maintained to contain every configured
appliance.