04-20-2017 09:08 PM - edited 03-01-2019 06:24 AM
Greetings,
I've deployed both UCS director and Baremetal agent on vSphere. The services of both are configured and started normally.
The Physical Account added in UCS director is also managed to retrieve the information from the BMA.
The problem is that the database connectivity status is still displayed as "DOWN".
The logfile.txt placed in /opt/infra/networkServices directory on BMA shows the following error message:
2017-04-19 06:36:46,716 [main] ERROR init(ServiceProvider.java:516) - Failed to initialize framework component (non-critical)
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
However, I've confirmed that I did configure the user accessibility of MySQL in UCS director server. And I was able to login into the MySQL using mysql command from BMA. Why the BMA is still not able to connect to UCS director's database?
I wonder if anyone else has experienced the same problem.
Any help would be greatly appreciated!
Thanks.
06-15-2017 01:34 PM
Here is my own check list
Bare Metal EASY Install
=====================
1) Network setup of UCS-D and BMA
UCS-D Front: 172.17.32.155 (VM Network)
UCS-D Back: 192.168.66.2 (VM Provision Net)
BMA Front 192.168.66.3 (Vm Provision Net)
2) Cleaning instructions If there is a previous BMA setup on UCS-D
Step 1) Enable root access on UCS Director (Option 22)
Step 2) Login as root (Option 23)
Step 3) Execute "sudo /opt/scripts/dbCNSAClean.sh” !!! Warning, this will delete all entries for any BMA servers you have !!
3) Import the BMA and IP in vCenter
4) ssh to the BMA (root/pxeboot) (Use UCS-D as jump server to get to BMA)
5) Setup dhcp
cd /etc
cat dhcpd.conf
cp dhcpd.conf.sample dhcpd.conf
vi dhcpd.conf (fix up for your env)
Example:
2 lines are missing here….they are in the sample
subnet 192.168.66.0 netmask 255.255.255.0 {
option routers 192.168.66.1;
option subnet-mask 255.255.255.0;
option nis-domain "ciscodemo.local";
option domain-name "ciscodemo.local";
option domain-name-servers 192.168.66.1;
option time-offset -18000; # Eastern Standard Time
range dynamic-bootp 192.168.66.160 192.168.66.254;
default-lease-time 21600;
max-lease-time 43200;
allow booting;
allow bootp;
next-server 192.168.66.3; # IP of my PXE server
filename "/pxelinux.0";
}
/etc/init.d/dhcpd restart
6) Set up BMA -> UCSD
ping 192.168.66.2 (ping the UCSD)
cd /opt/infra
./stopInfraAll.sh
./configure.sh 192.168.66.2 (IP of UCSD) (Multi node this is the IP of the Inventory DB)
./startInfraAll.sh
7) Enable UCSD -> BMA
ssh shelladmin@172.17.32.155 (UCSD) (changeme)
16) Enable Database for BMA (enter IP of BMA (192.168.66.3))
on multi node this needs to be enabled and configured on the Inventory DB server!
8) BMA
cd /opt/infra
./stopInfraAll.sh
./startInfraAll.sh
9) Check UCSD
administration -> Physical Accounts -> Network Services Agents
10) UCS-D (ASCII shell prompt)
17) Add BMA Hostname/IP
192.168.66.3 BMA
11) BMA
vi /etc/hosts
192.168.66.3 BMA
192.168.66.2 UCSD
12) Update (BMA)
vi /opt/infra/networkServices/run.sh with proper PXE and MGT IP's
Make sure this is between -Dpxe.tftpd.enable=on and -cp
-DpxeServer.ip=192.168.66.3 -DpxeServer.mgmt_vlan_ip=192.168.66.3
13) start httpd (BMA)
service httpd start
chkconfig --list | grep dhcp
chkconfig --list | grep http
chkconfig --level 345 httpd on
chkconfig --level 345 dhcpd on
14) BMA
cd /opt/infra
/opt/infra/stopInfraAll.sh
/opt/infra/startInfraAll.sh
Test PXE Setup
============
Create empty VM on PXE boot network
Grab MAC address from a sample VM (make sure vm is on the right network)
In UCSD go to
Physical -> Compute -> PXE boot requests
Set up the PXE boot request with above MAC address
Select Setup PXE request
The MAC address should show up a file in this directory
cd /opt/cnsaroot/pxelinux.cfg
ls -ltr
[root@localhost pxelinux.cfg]# ls -ltr
total 16
-rw-r--r-- 1 root root 315 Feb 28 2011 01-d4-85-64-51-68-bc
-rw-r--r-- 1 root root 315 Feb 28 2011 01-00-24-81-8a-46-0e.backup
-rw-r--r-- 1 root root 596 Mar 1 2011 01-00-24-81-8a-46-0eoutput
-rw-r--r-- 1 root root 914 Jun 7 18:43 01-00-50-56-a5-38-58
[root@localhost pxelinux.cfg]#
Boot the VM in vCenter
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide