Re: IP polices -> packet rules....

Let us know what you find out. My bad experience was simply losing all
TCP/IP traffic, not the whole machine. You wouldn't think a packet rule,
no matter how bad, would knock out the console and apparently the whole
system. Or perhaps the system was up but not communicating. What kind of
console do you have? I think Richard and I were talking twinax. If you
had a LAN console perhaps I could see a bad packet rule knocking it out
in addition to all regular TCP/IP comms.

IBM SupportLine helped me set up my packet rules and I was glad I asked
them because I would not have known to include the permit all rule.

-Marty

------------------------------

date: Wed, 11 Jul 2007 05:41:03 -0700 (PDT)
from: Bob David <bob_wkot@xxxxxxxxx>
subject: Re: IP polices -> packet rules....

Richard & Marty,


Logged in console and then through the iSeries navigator created the
rule to restrict our one of internal address.

It was verified and then activated. Then I had worst experience.

1. we have our own application and it started firing
ODBC error from different IP address.
2. then I tried to login in iSeries navigator and it
kicked me out saying that CWBC01048.
3. called up IBM for the support then he asked me to
login from my PC using telnet.
4. tried telnet without success.
5. found that even console is blank.
6. we were forced to reboot the server
7. system was up and console was only accessable.
8. Then did RMVTCPTBLE then we were able to access
through Client Access.
9. Tried to find in history logs, SST with out success
for root cause.


Thanks
Bob