Netgate SG-1000 microFirewall

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dennypage

Pages: [1] 2 3 4 5 ... 56
1
Packages / Re: NUT package
« on: Today at 02:14:25 pm »
The docu said a write community is needed to facilitate shutdowns. I wanted the UPS and NUT to coordinate that NUT will shut down pfSense when there's not much runtime left and then tell the UPS to shut off the outlet in x minutes and come back up when AC power is restored and battery has at least y % charge.

Ah, yes. Needing write permission to kill power makes sense. Note that the pfSense NUT package version 2.7.4_5 does not support issuing the final power kill order. This will come with NUT package 2.7.4_6 which requires pfSense 2.4.3.

2
Packages / Re: NUT package
« on: Today at 01:22:40 pm »
That makes sense. For what it's worth, most people use a read-only SNMPv1 group for UPS monitoring. There isn't any sensitive information in the stream.

3
Packages / Re: NUT package
« on: Today at 12:30:56 pm »
SNMP parameters are part of the UPS specification. As such, they go in the "Extra Arguments to driver" rather than in the "Additional configuration lines for ups.conf" section. The advanced section is only for Global Directives (see ups.conf), and anything that is not recognized as a global directive is ignored by NUT. I know it's confusing, but it's how NUT's configuration works. Anything that comes from the driver man page (snmp-ups in your case) goes into Extra Arguments to driver.

4
Packages / Re: NUT package
« on: Today at 12:12:44 pm »
I just deployed a second AP9631 out of the box. Factory reset, flashed 6.5.0, factory reset again, set up SNMPv3 and had the same issues I described before where NUT cannot communicate.

I have now noticed that if I have SNMPv1 DISABLED, NUT will fail to connect via SNMPv3 no matter what extra settings I provide. Simply turning on SNMPv1 in the AP9631 (fw 6.5.0) immediately lets them communicate. Very strange. Further testing is needed.

I have replicated this on the previous installation where I can break the SNMPv3 communication between NUT and the AP9631 by disabling SNMPv1, don't even need to reboot.

It sounds like SNMPv3 may not be properly configured/functioning in NUT. Can you post the contents of /usr/local/etc/nut/ups.conf please?

5
Packages / Re: LLDP daemon package
« on: February 22, 2018, 11:37:07 am »
The status page code is pretty simple. You can see it in /usr/local/www/lldpd_status.php.

6
Packages / Re: LLDP daemon package
« on: February 22, 2018, 11:22:36 am »
I don't think its any sort of "issue"... But would be slicker looking if was broken out into the subtype line vs listed on the port id is all..

I can't disagree, however the format of status data is from upstream rather than the pfSense package. The output is directly from the command lldpcli show neighbors.

7
Packages / Re: LLDP daemon package
« on: February 22, 2018, 11:10:55 am »
Just FYI, the version of lldpd currently distributed for pfSense is 0.9.4 because this was the version available in FreeBSD Ports at the time the package was introduced. The current version of lldpd is 0.9.9, which has just been committed to FreeBSD Ports. Movement into the pfSense repo is pending.

8
Packages / Re: LLDP daemon package
« on: February 22, 2018, 10:49:02 am »
Looking good, one slight issue, marked in red :-
  Port:       
    PortID:       ifname gi1
    PortDescr:    gigabitethernet1

I don't understand. Why is this an issue?

9
Packages / Re: NUT package
« on: February 21, 2018, 10:11:43 am »
That's good news. Now that it's working, you can probably tune the variables down quite a bit. In particular, the settings in Extra Arguments can likely be returned to their default values of 1 & 5. Or simply deleted.

10
Packages / Re: NUT package
« on: February 20, 2018, 06:01:35 pm »
Please give the following a try:

Get rid of pollfreq and pollinterval.

Set these variables in the Extra Arguments to driver section:
Code: [Select]
snmp_timeout=2
snmp_retries=10

Set these variables in the Advanced section for ups.conf:
Code: [Select]
retrydelay=30
maxretry=20

Now reboot the box. When the box comes up, go to the UPS status page. [Do not attempt to start the service manually] If the UPS shows as needing attention, wait for the page to refresh automatically. If it doesn't auto refresh, after a couple minutes refresh the page manually. Does the UPS show as running? Or is it still down?

11
Packages / Re: NUT package
« on: February 18, 2018, 02:15:13 pm »
Thank you - I'll give it a try.

I've noticed the following errors appearing in my logs, any idea why this would be?

Code: [Select]
...
Feb 18 11:01:52 snmp-ups 44002 dstate_setflags: base variable (battery.runtime.low) is immutable
Feb 18 11:01:20 snmp-ups 44002 dstate_setflags: base variable (battery.runtime.low) is immutable
Feb 18 11:00:48 snmp-ups 44002 dstate_setflags: base variable (battery.runtime.low) is immutable
...

I believe it means that the variable is marked read-only in the SNMP MIB. For more information on this, I would suggest checking the nut users list.

FWIW, if it were me I would just remove the setting of runtime and use charge %. You donít need both.

12
Packages / Re: NUT package
« on: February 18, 2018, 11:08:18 am »
How can I delay pfsense powering down until esxi has completed shutting down?

The HOSTSYNC variable controls how long the master will wait for slaves to initiate their shutdown. You can find information on this in the ups.conf man page.

13
Packages / Re: NUT package
« on: February 13, 2018, 03:19:49 pm »
Also, will the ups power back on automatically after mains is restored after a power kill?

It should. Most all UPSs are designed to.

14
Packages / Re: NUT package
« on: February 13, 2018, 12:43:19 pm »
The ISSUE is my APC is not shutting down after pfsense and synology shuts off. It keeps running till battery  becomes 0.

See post #1, version 2.7.4_6 which addresses this issue.

15
Packages / Re: LLDP daemon package
« on: February 08, 2018, 05:18:21 pm »
The pr is in. Reviews are complete, but not sure how long before it would appear in the package repos though. Folks are busy. :)

Pages: [1] 2 3 4 5 ... 56