Core Manager: Status and Settings
| Site: | QSC |
| Course: | Q-SYS Level 1 Training |
| Book: | Core Manager: Status and Settings |
| Printed by: | Guest user |
| Date: | Thursday, 21 November 2024, 5:12 AM |
Description
Video Transcript
00:07
The Core Manager provides a variety of management options for your Core,
00:12
which of course can only be configured when your PC is connected to that Core on your network.
00:17
You can access the Core Manager either from the Tools menu and selecting “Show Core Manager,”
00:23
or you can click directly on the name of your Core that is displayed in the top tool bar
00:28
when your design is running.
00:29
You could also simply enter the IP address of your Core into any web browser.
00:34
If your web browser gives you a security warning like this, don’t worry about it.
00:39
Since your Core is a trusted device on your local network, your connection is secure,
00:44
even if your browser doesn’t recognize it.
00:46
We highly recommend you add the “https” designation to your browser when you connect.
00:52
For more information on networking security considerations with your Core,
00:56
you can check out our videos in our Reflect Enterprise Manager training course.
01:00
However you connect to the Core Manager, you’ll come to this: the main dashboard.
01:05
You can navigate different sections on the left,
01:08
which you can also collapse down to smaller icons if you’re already comfortable navigating them.
01:13
Let’s look at each section, going from top to bottom.
01:16
The Status section gives a general overview of your system, including basic information on your Core,
01:22
and the current status of every peripheral in your design.
01:26
For larger designs, you may want to use the Inventory filtering options
01:30
so that you can find specific types or models of devices.
01:34
If any of your devices shows a Fault in its status,
01:38
then you probably want to investigate by going to the next tab: the Event Log.
01:43
The Event Log is a list of notable events that have taken place during the uptime of your running design.
01:49
Normal events are noted in green, warning events are noted in amber,
01:54
and error events are noted in red.
01:57
Once again you can filter this log to find events with a specific severity,
02:02
or a particular category such as paging activity or telephony connections,
02:07
or filter for activity from specific devices.
02:10
You could also constrict your log report by specific dates, or search for a specific word or phrase.
02:18
Or, if you want to clear out your log, simply press the Clear Log button.
02:23
Certain events in a log will repeat – for instance, if a device’s status drops from OK,
02:29
then an error message will log upon the first problem, and then repeat again in 10 minutes,
02:36
and 6 hours, and then every 12 hours thereafter until the problem is corrected.
02:41
The log will also specify how long the problem has persisted.
02:45
There are certain components that allow you to publish custom messages
02:49
to the Event Log based on your design’s activity,
02:52
which makes this a useful troubleshooting tool to keep track of your entire system’s performance.
02:57
Core Manager will store up to 5,000 events or 30 days worth of activity, whichever one comes first.
03:04
After this, the oldest events will be deleted in batches of 1,000 events at a time.
03:09
(So technically, it could store up to 6,000 events before this deletion).
03:13
If you’re using Enterprise Manager,
03:15
its event log follows the same logic, except the limits are 30,000 events and 6 months.
03:21
Next, let’s look through the various sections of the Core Management category.
03:26
In Network Settings, you get access to the same information for your Core
03:31
that you found in the Configurator for your other Q-SYS peripherals – namely, your Core’s name,
03:36
its IP addresses and net masks for each of its LAN ports, and an ID button.
03:42
To change this information, simply press the Edit button, make your adjustments, and then press save.
03:49
Like we mentioned in the Configurator, naming your device and configuring its IP address
03:54
is one of the first steps to getting your system operational.
03:58
At the bottom you’ll also see settings for DNS.
04:01
If you’re connecting your Core to the internet on one of your LAN ports,
04:05
be sure to get your DNS and Gateway settings from your IT administrator to enable that access.
04:11
The Date & Time settings speak for themselves: you can set the Core’s Date and Time,
04:16
as well as determine which Time Zone it should use,
04:19
which is useful if you’re commissioning a system for a region different than the one that you’re in.
04:24
If you enable Time Synchronization,
04:26
that will allow the Core to get its time from a Network Time Protocol server of your choice.
04:31
In the Licensing section,
04:33
you can see a list of all Q-SYS software feature licenses that have been installed on your Core,
04:39
as well as an activation area to install new licenses.
04:42
If you need a Scripting Engine license or a UCI Deployment license, for instance,
04:47
you’ll need your Entitlement ID or License File to activate these.
04:51
You can learn more about license activation in a separate video.
04:55
Let’s take a quick break there, and come back whenever you’re ready.
Lesson Description
Access the Core Manager, monitor your system’s peripherals, and configure your Core’s network settings