|
Server: bb19c Remote clients: bb1.9e-btf & bbc1.9e-btf
Problem: We went through some network renumbering recently and wound up changing the IP address of our BBDISPLAY and BBPAGER (one and the same) server. In turn, we updated the associated host (BBPAGER and BBDISPLAY directives defined) for all of the clients to now point to the correct address. We brought the server back up and everything was good. Web page was updating etc . . .
A few days later we had an outage on one of the clients and noticed that even though the BB web display was updating with the proper status, we were now not receiving pages for the particular host. I then performed the following: 1. Checked BBOUT on both ends and found nothing out of the ordinary 2. Restarted BB on both the server and client. 3. Doubled checked the bb-hosts on both ends 4. Cleared associated log files from /bbvar/logs/ 5. Double and triple checked bbwarnsetup configurations on both sides (even though these hadn't been touched) 6. Tested an outage on another client that has bb1.9e-btf and it did the exact same thing. 7. Tested an outage on a client running bb19c and it did not have the problem paging.
I finally decided to just try to reset the BBPAGER directive within the bb-hosts file on both client installs (bbc and bb). I removed the BBPAGER directive from the host (server) that controls the paging and restarted the daemon. Low and behold as soon as I did that we started receiving pages, even without the BBPAGER directive defined in the bb-hosts file for the client! I have yet to re-add the BBPAGER to the server entry. Am I missing something here???
-Shad
DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Cicada. Finally, the recipient should check this email and any attachments for the presence of viruses. Cicada accepts no liability for any damage caused by any virus transmitted by this email. |