Issues
- badly formed ip addresses can be accepted as critical path ipNMS-6587Resolved issue: NMS-6587Bill Ayres
- Sort notifications by severityNMS-6504Resolved issue: NMS-6504Alejandro Galue
- The Valere devices with broken SNMP agents are hanging Provisiond.NMS-6484Resolved issue: NMS-6484Alejandro Galue
- Create an opennms-release file in $OPENNMS_HOME/etc directoryNMS-6433
- report.netsnmp.swapinout uses incorrect units and scaleNMS-6357
- Frequent interface counter wrapsNMS-6335
- notification destination paths aren't traversed on occasionNMS-6248
- Event description text sent by e-mail includes raw HTML tagsNMS-6246
- Opennms WeatherMap Plugin v1NMS-6244Markus Neumann
- Users don't see current notifications for themselves until logging out and back inNMS-6209
- The threshold processor doesn't work well with complex JEXL ExpressionsNMS-6194Resolved issue: NMS-6194Alejandro Galue
- ThresholdingSet isn't catching the exceptions thrown by the threshold evaluatorsNMS-6193Resolved issue: NMS-6193Alejandro Galue
- The SnmpMonitor is not returning the status with the responseTime valueNMS-6192Resolved issue: NMS-6192Alejandro Galue
- NPE on output.log due to null ifSpeed when calling PhysicalInterfaceRow.getSpeedNMS-6169Resolved issue: NMS-6169Alejandro Galue
- maint_events.sh is not workingNMS-6168Resolved issue: NMS-6168Alejandro Galue
15 of 15
badly formed ip addresses can be accepted as critical path ip
Fixed
Description
Environment
All
Acceptance / Success Criteria
None
Lucidchart Diagrams
Created June 5, 2014 at 5:20 PM
Updated January 30, 2017 at 11:18 AM
Resolved June 6, 2014 at 2:43 PM
Activity
Show:
Bill AyresJune 6, 2014 at 2:43 PM
Fixed in master 6/5/14
Go to admin -> Configure Notifications -> Configure Path Outages
enter a badly formed ip address for the critical path IP address
some bad addresses will be caught, but most will not and will end up in the database.