Install DCF using
Console Mode
DCF can be installed on the platform of supported Linux hosts.
This procedure specifically uses the Linux installation procedure as an
example.
Fulfill the following prerequisites before
starting the installation:
- Installation server must have bash installed.
- Installation server must have zip installed.
- Installation server must have installed curl utility.
- When you install DCF on a Linux Platform, assign executable permissions to the installation script.
- Ensure that you have a login with root privileges to run the installer.
- Download the installation file from https://support.broadcom.com/ and place it in a temporary location on the server.
- Login server as root.
- Type./Smarts_dcf-<Version>.bin –i consoleto run the installer in the console-based installer mode, pressEnter.The introduction command prompt screen appears.
- PressEnterto continue.License agreement appears.
- PRESS ANY KEY TO CONTINUE TO READ LICENSE AGREEMENT OR PRESS '0' to ADVANCE TO END. PressEnter.
- TypeYand pressEnterto accept the license agreement.
- Specify the directory to install DCF when installer prompts, or else pressEnterto accept the default folder.Default Install Folder:/opt/DCFIf the target directory already contains an existing DCF installation, then it upgrades (patch or full), else fresh installation takes place.
- PressEnterto continue when pre-install summary displays.Installation continues.Installer triggers rollback action on any kind of failure. Except DCF_Logs, all files and folders gets uninstalled. Errors can be seen insideDCF_Logs/INSTALL_ERR.log
- PressEnterto exit the installer when Install completed message displays.
After successful DCF installation, Install
VMware Smarts Notification
Collector
to pull all the events from Smarts Presentation SAM and
publish the same to KAFKA for consumption. If you shutdown or stop IP/ESM
server which has Cisco ACI / VCD / Cloudify discovered and restart the server
with the same repos / topology using --ignore-restore-errors or --clean-topology
then no issues. However if you shutdown ESM server and restart with --norestore
option then old monitoring collectors for Cisco ACI / VCD / Cloudify will be
running and those need to be stopped manually.