Everyone, I appreciate everyone's response - to bring everyone up to date I am working with network security team (owners of Nessus scans) and we are trying to isolate with Nessus vendor (unfortunately not much help - they point to us working with Tectia vendor which we already are - gotta love the finger pointing) but there are literally 100's of these scans packed into one iteration which runs ~30 mins so today we plan on running wireshark to try and "trap" offending activity that locks up the address space.
Dennis Mruz, to answer your question / point we've updated the SSHD2_config file to latest updates that vendor / development recommends and still hang condition persists. Any other ideas please share but this is a fleeting one to "trap". Thanks again. Steve ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
