Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2017December15 - Deletes > Investigate errors related to Import Rule Documentation

Investigate errors related to Import Rule Documentation

Table of contents
Created by Justin Rouviere, last modified by Jessica Solis on Dec 15, 2017

Views: 584 Votes: 0 Revisions: 5


This article discusses errors related to the Import Rule Documentation feature. 


All FSM versions


The Track Rules > Import Rule Documentation feature generates a response window that contains the number of successes, errors and warnings. When errors are reported the errors are logged to C:\Program Files\SolarWinds\SolarWinds FSMServer\logs

Example 1:

2016-02-08 09:21:49,454 [RuleDocumentationManager] ERROR [ModalContext] - The Rule documentation entry with firewall name <hostname> and FSM Rule ID <####> is not valid and will be ignored as the corresponding rule is not present in the system.

Comparing the Rule ID in the error to the rule documentation spreadsheet, the spreadsheet will correlate the update with a line in the configuration.  This error typically relates to the documentation applied to a line that is invalid (such as a line with a closing bracket instead of the actual rule data).


Example 2:

The date is displayed as <null> in the rule documentation when <> is the expected result.

This occurs when using an SSH import that causes the dates to appear blank in rule documentation under Firewall Inventory. 


Last modified