![background image](http://html1.mh-extra.com/html/verizon/volicon-mip/volicon-mip_admin-manual_1005053066.webp)
66
AG-7.2.B1-092414 • Restricted - customer use only
11
MIP
WEB
BASED
CONFIGURATION
AND
MONITORING
MIP configuration is web based, except for a few specific exceptions. Your admin tools are a superset
of the user tools. As a MIP administrator you have the ability to set which aspects of MIP each user
account is able to access.
Figure: User vs Admin Tools
←
Configuration – configure Probe groups, Probes and Encoders
←
Settings – configure the Central Server
←
Active Users – displays list of currently logged in users
←
Preferences – user specific setting and time zone
←
System Health – displays status of various MIP components
←
Help – link to the customer support page
←
About – displays MIP and Observer ActiveX player version
←
Reset Cache – clears all application caches, such as selected channels
←
Log Out – terminate user session
11.1
System Architecture
The Central Server that is the heart of the MIP. It has overarching responsibility for all aspects of the
system. Depending on size, the MIP will utilize one or more Probe servers. The responsibility of the
Probe is to ingest and store programs. The Probe utilizes capture cards to enable MIP to interface
with various program sources.
The MIP Probe ecosystem is organized in a hierarchal manner. There are several layers which make
up the entire system: Groups, Probes, and Encoders.
←
Group(s) – This level associates multiple Probes under one unified heading. Groups can be
created by input source, geography, network capture location, etc.
←
Probe(s) - Each server, as a whole unit, contains anywhere from 1 to 16 video, audio, and
metadata capturing inputs/channels. It stores all the recorded content locally and streams
out the recorded content to end users. A Probe server contains one or more Encoder-
streams or channels.