Use of this document and web site are governed by the Terms and Conditions of Use for InfoExpress's web site.[/b][/u]
SummaryAn issue exists where physical replacement of an enforced network switch may cause problems. A workaround exists, and the issue will be fixed in the next release of the CyberGatekeeper LAN Enforcement Module.
DetailsThe issue concerns CGS behavior when a switch is replaced. (I.E. an existing switch has been removed and a new one, with the same IP address, has been put in it's place.)
The expected behavior is that when a switch has been replaced, CGS will not manage the new switch. The web pages should show that switch as invalid and the port information should reflect the last state of the previous switch.
Under certain circumstances, CGS would manage the replacement switch. For this to occur, the replacement switch must have the same IP address, the same username, the same password, must be managed in the same manner, and CGS must receive the boot up trap from that switch.
In order to avoid this problem, we recommend that customers remove the switch configuration from CGS prior to installing the replacement switch. (This is the correct procedure regardless of the scenario, due to CyberGatekeeper's error checking mechanism, which prevents it from automatically managing a "swapped" switch.) Ideally, the configuration should be deleted before even removing the switch, however this is not possible in cases of switch failure.
The next CGS release will include a fix for this issue. In this case, the fix is simply for CGS to never manage a new switch. Please note that that best practice is to remove the switch configuration from CGS prior to switch changes/replacements.
If you have any questions about this issue, please contact
InfoExpress Support.
Use of this document and web site are governed by the Terms and Conditions of Use for InfoExpress's web site.[/b][/u]
