08-14-2013 07:41 PM - edited 03-01-2019 11:11 AM
Dear Team,
All of a sudden we were not able to take KVM of Servers,for all servers from
both chasis
In Java console it was showing Connection time out error
og4j:WARN No appenders could be found for logger (com.nuova.centrale.core.log4j.NuRollingFileAppender).
log4j:WARN Please initialize the log4j system properly.
Connection failed.
Not even able to ping the KVM Console IP that was working fine all these days (IP are of same range as of FI)
After 1 hour of trouble shooting ,we finally decided to reboot FI-A
and FI-B took over as cluster lead-primary,then we were able to take KVM of servers.
We also looked at the PDF UCSM-kvm-troubleshooting-00
Now after reboot FIA came up and we did not wait for the primary role switch over,but logged into FIB and made FIA as primary on doing this we lost KVM COnsole access.
So now we rebooted FIA again and FI-B took over as cluster lead-primary,then we were able to take KVM of servers.Now this time after FI-A came up after reboot we waited for the primary switch over to happen by itself and after sometime FI-A got its role back as primary and KVM access started working fine
so would like to know..the initial issue with FI-A is it because of CIMC hung? and on forcefull manual change over of FI-A as primary did not help in getting KVM console access any reason?
Thanks and Regard
Jose
08-14-2013 10:41 PM
Hello Jose,
CIMC software runs on each blade and FI does NAT of it's IP address with it's mgmt interface ip address.
Are you able to ping FI A and B mgmt interface IP address ?
Have you ever rebooted CIMC of the blade ?
Did it happen for all blades managed by FI A ?
Padma
08-15-2013 05:03 AM
Hi Padma,
We have 2 FI A and B
say A is 21 B is 22 and 20 cluster ip
Are you able to ping FI A and B mgmt interface IP address ?
how we are connecting is ,we connect from FI A mgmt port to a switch
and there we manage at this point we can ping 21 and 20 not 22 and vice versa
Have you ever rebooted CIMC of the blade ?
We did not reboot CIMC alone ,we rebooted a server itself
how to reboot CIMC alone?
Did it happen for all blades managed by FI A ?
yes we checked from both chasis,physical connectvity given from both FI
Thanks and Regards
Jose
12-09-2020 04:12 AM - edited 12-09-2020 04:17 AM
I faced a similar issue & tried the following steps as a part of my own troubleshooting & was able to get the issue resolved. If you do not want to undergo the hardship of rebooting the FI or re-seating a blade, You may give it a shot ;-).
KVM Console is not Working
Thanks ! !
Sriram V S
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