We are running an HA Avaya SBCE on version 7.2.2. We have added IP addresses to the Blacklist and need to confirm if a restart of the application is required.
That's a good question! The answer is that you shouldn't have to restart the application. (but changing grooming shouldn't either) So i'd say don't restart and do your tests. If it does not do what you expect then restart the application and see if it changes the behaviour.
Our Business Partner states that the SBCE firewall blacklist feature does not require a restart of the application to take effect. Avaya states that SBCE version 7.2.2 does require a restart and the Avaya documentation is lacking in clarity.
I will restart the application in our SBCE HA pairs and post the result.
Here is the last update on our SBCE blacklist issue.
After escalating to Avaya Tier IV (which took almost 6 weeks) we were advised to upgrade from version 7.2.2.0-11-15522 to 7.2.2.2-04-17187 and apply a hot fix provided by the Tier IV engineer to each SBCE HA pair via CLI. Hot fix patch had to be applied via WINSCP to each SBC with a reboot. We now have to apply some IP ranges to the blacklist and test to determine if feature is working correctly.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.