[SOLVED] Multi Wan Gateway Group Monitoring Notification seems wrong

skalvaro

Hi,

pfSense: 2.3-RELEASE (amd64)
Multi Wan setup:
PXSGW > Weight: 1
SCRGW > Weight: 1
Gateway Group: name 'loadBalancing'
Gateway Priority: PXSGW > Tier 1, SCRGW > Tier 1
Trigger Level: Member down

After the update to this latest release it seems the monitor notification mails are incorrect.
Before the upgrade when a member went down the notification read:

MONITOR: SCRGW is down, omitting from routing group loadBalancing

After the upgrade it became:

MONITOR: loadBalancing is down, omitting from routing group SCRGW

As far as I can tel the Gateway Group and its interface members are reversed in the notification.

Regards,
Sammy

jimp

That has been fixed on 2.3.1.

lasocean

Good to know that fix is coming in 2.3.1
Any plans to also send a notification when a Gateway is back up?

Raiker

I'm also interested in the notifications when the gateway is back up. Also, Is there a way to set which gateways i want to be notified about? I have 4 wans, 2 main cablemodems and 2 ADSL backups. I have several groups, and the primary groups have a policy of kicking a member due to latency, the secondary groups do not care about latency. The adsl wans get constantly kicked off the primary groups even though they are not in use (tier2 vs tier1). Maybe send the mails only if the current tier is in use? Should i make a separate thread for this?

luckman212

I can't remember where, but I do remember seeing in either another thread here or over on redmine that there was a reason why sending an alert for "gateway back up" was somehow difficult with the current system in place. I wonder if that was somehow a limitation of apinger that is no longer present (dpinger). This and solving the hysteresis situation that cranks out hundreds of consecutive alerts within a matter of seconds on occasion would be very nice improvements.

skalvaro

Current Base System: 2.3_1
Latest Base System: 2.3_1

Seems not fixed yet.

MONITOR: loadBalancing is down, omitting from routing group SCRGW

After reboot the notification is still the same so I removed all references to the Gateway Group 'loadBalincing' and deleted it, created a new group but it is still the Gateway Group that is down and not the Gateway itself.

MONITOR: LBGWGroup is down, omitting from routing group SCRGW

jimp

2.3_1 is really 2.3.0_1, not 2.3.1. This bug is fixed in 2.3.1, which has not yet been released.

skalvaro

ok, my bad.

skalvaro

2.3.1-RELEASE (amd64)
built on Tue May 17 18:46:53 CDT 2016
FreeBSD 10.3-RELEASE-p3

I can confirm this one is solved :)

Before update:

MONITOR: LBGWGroup is down, omitting from routing group SCRGW

After update:

MONITOR: SCRGW is down, omitting from routing group LBGWGroup