The AES67 RAVENNA Interface has to be placed in an extension slot within a series 52 XC2/XS2 core device or a series 52 XC2 concentrator.
To work with the interface:
Although the XC2 AES67 RAVENNA interface is housed in an XC2/XS2 Core or XC2 Concentrator, the XC2 AES67 RAVENNA interface is running as an own device instance within the DHD ecosystem. It has its own management interface which can be accessed by DHD Communication Server (DHDCS). It will appear as an own DHD device at DHDCS.
With DHDCS you can set up general network parameters, such as:
See DHDCS / Network Config for more information.
Note
The AES67 RAVENNA Interface is a separate different device in the DHDCS. You can only see it if you have a network connection between its primary Ethernet port (left port) and the computer running Toolbox.
Note
Network configuration of secondary interface and VLAN seetings are availabe using Settings page on the Web GUI.
With DHDCS you can update the device firmware and device kernel. See DHDCS / Update for more information.
The web interface also offers a password protection. Once activated, all pages except the overview page are password protected. See chapter Device Password on how to setup and change password protection of the AES67 device.
The device logging works via DHDCS. The DHDCS log contains (depending on log level) all firmware log messages, as well as PTP log messages.
A PTP log is additionally implemented in the user interface in the PTP Logs
menu point. See System/PTP Log for more information.
Note
For debugging and communication with DHD, logging via DHDCS is always recommended.
To enter additional licenses in the AES67 RAVENNA Interface, follow the instructions specified in the Licensing Manual.