Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

APC-Pwerchute Network Shutdown Service unreachable due to filtering

3 views
Skip to first unread message

ka...@kunze-stade.de

unread,
Jun 12, 2009, 7:31:21 AM6/12/09
to
We (NW60-SP5 + BM36) installed the service for gracefully
shutting down the server while the UPS (192.168.xxx.5) runs
out of energy and this shutdown-service on the
bordermanager-server (192.168.xxx.3 private ip-address on
the private nic) has a communication-problem with the UPS.

From my vision (set tcp debug = 1) the following describes
the problem (ping works, rest does not):

RECEIVE:pktid:256 192.168.xxx.5->192.168.xxx.3 ttl:64
(ICMP)Echo Request
LOCAL:pktid:256 192.168.xxx.5->192.168.xxx.3 ttl:64
(ICMP)Echo Request
TRANSMIT:pktid:35060 192.168.xxx.3->192.168.xxx.5 ttl:128
(ICMP)Echo Reply

RECEIVE:pktid:42304 192.168.xxx.5->192.168.xxx.255 ttl:64
(UDP)
UDP:Source Port:37078Destination Port:3052

LOCAL:pktid:42304 192.168.xxx.5->192.168.xxx.255 ttl:64
(UDP)
UDP:Source Port:37078Destination Port:3052

Discard Incoming: cause(FILTERING), reason(5)

When disabling filtering it works fine. But I do not see
what filter-exception I have to set up for the privat nic or
the private ip-address.

Any hint is highly appreciated.

Sincerely

Karl

KeN Etter

unread,
Jun 12, 2009, 9:35:38 AM6/12/09
to
On Fri, 12 Jun 2009 11:31:21 GMT, ka...@kunze-stade.de wrote:

>We (NW60-SP5 + BM36) installed the service for gracefully
>shutting down the server while the UPS (192.168.xxx.5) runs
>out of energy and this shutdown-service on the
>bordermanager-server (192.168.xxx.3 private ip-address on
>the private nic) has a communication-problem with the UPS.

Karl,

When you run APC's Network Shutdown on a Border Manager server, you
need to SET FILTER SUBNET BROADCAST PACKETS=OFF in order for the the
software to communicate with the UPS. You can see that setting in
Monitor, Server Parameters, Communications.

Regards,
Ken Etter

Novell....it does a server good!

ka...@kunze-stade.de

unread,
Jun 12, 2009, 10:04:41 AM6/12/09
to
Bingo! Thanks a lot!

Do I have to be afraid of any side effects with this
setting?

Karl

>>> KeN Etter<kle@_remove_this_msktd.com> 12.06.2009 15:35

KeN Etter

unread,
Jun 12, 2009, 1:08:59 PM6/12/09
to
On Fri, 12 Jun 2009 14:04:41 GMT, ka...@kunze-stade.de wrote:

>Bingo! Thanks a lot!
>
>Do I have to be afraid of any side effects with this
>setting?
>
>Karl

Not that I'm aware of. I've been running APC Network Shutdown on my
BMgr server for years with that setting and it never caused me an
issue.

Regards,
Ken

ka...@kunze-stade.de

unread,
Jun 15, 2009, 2:44:53 AM6/15/09
to
Thanks a lot again!

Sincerely

Karl

>>> KeN Etter<kle@_remove_this_msktd.com> 12.06.2009 19:08

Craig Johnson

unread,
Jun 15, 2009, 1:03:11 PM6/15/09
to
In article <nr25351j25grvad4a...@4ax.com>, KeN Etter
wrote:

> Not that I'm aware of. I've been running APC Network Shutdown on my
> BMgr server for years with that setting and it never caused me an
> issue.
>
I use the same setting on all my BM cluster servers without issues.
Same sort of problem - filtering subnet broadcasts kills cluster
heartbeat. (At least with most typical subnet addresses).

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***


0 new messages