Hey Everyone we are having a weird issue where one of our appliances will go out of sync with our manager. We are running 4.9 code and the appliance that we are having an issue with is a OOB Layer 2 VG. We do have a tac case but we are not seeing anything in the logs. It is very random when it happens sometimes after a few hours then sometime it can go all day before it breaks again. All we have to do to get it to resync is to console into the server and it seems to break whatever is going on then come back online. Any suggestions would be welcome.
There was something wrong with the click in the code so the engineers who wrote the code manipulated my code and they changed the 4.9 download code to fix it. I had to work with TAC and we did a lot of testing.
Thanks for the quick response. Besides the out-of-sync issue, were you losing total communications with the CAS? Also, did they provide you with a patch or did you have to reinstall?
Sorry for all the questions, but TAC isn’t much help at the moment….
Thanks in advance!
I understand that. They gave me a patch but they had to modify it on the fly so I don’t have the correct patch to share. But yes we would lose all connectivity with the server, luckily we had a terminal server where we kept the server that kept going out of sync we would just have to console into the server and hit enter a few times to get the prompt and it would go back in sync for a time.
We had to work with the NAC engineers to manipulate the code on the box to fix the problem. They basically gave us a patch to the original code download. After that the server has been working great. I have seen a few others go out of sync randomly but only once or twice not like this one though.
You probably download the 4.9 ISO before its latest posting in mod Nov. TAC gave me patch to fix the problem. Since I applied it, I have not had an issue…..
BTW- Here’s the bug ID, CSCts58033
This has been a long and difficult road to get this NAC solution deployed.
Never seen so many issues with a new appliance. I've been working this deployment since Nov.....
Yes, it should be fine…I haven’t had this issue since the patch was applied. It’s been running fine for about two weeks in production now…..