Good Afternoon Everyone, Last week, I powered down the active CAM and waited for the standby CAM to become active. The standby CAM became active, however, when I went to the web interface (via service IP as well as the actual ip) the standby user interface was shown. I ssh'ed into the "active" CAM and ran fostate.sh and the following came back as the status:
"My node is active with standby UI, peer node is dead" When I powered up the "dead" CAM nothing was different except when I ran fostate.sh the status came back as: "My node is active with standby UI, peer node is standby" I am thinking this is a bug, but could not find any info in the CleanAccess list. We are running 4.1.1. Also, an easy question- what is the latest version in the 4.1.x train? Thanks so much for your help! Mary My node is active with standby UI, peer node is dead [r...@cam-1 ~]# ./fostate.sh My node is active with standby UI, peer node is dead [r...@cam-1 ~]# ./fostate.sh My node is active with standby UI, peer node is dead [r...@cam-1 ~]# ./fostate.sh My node is active with standby UI, peer node is standby [r...@cam-1 ~]# ./fostate.sh My node is active with standby UI, peer node is standby [r...@cam-1 ~]# ./fostate.sh My node is active with standby UI, peer node is standby [r...@cam-1 ~]# ./fostate.sh My node is active with standby UI, peer node is standby [r...@cam-1 ~]# ./fostate.sh My node is active with standby UI, peer node is standby [r...@cam-1 ~]# ./fostate.sh My node is active with standby UI, peer node is standby [r...@cam-1 ~]# ./fostate.sh Mary Ide Internet Security Engineer Johnson & Wales University SANS GPEN #1514 SANS GCIH #1794 SANS GWAS #1728 [email protected] <BLOCKED::mailto:[email protected]>
