Invalid address value NaN shown in 3.1.7

Showing results for 
Search instead for 
Did you mean: 

Invalid address value NaN shown in 3.1.7

L3 Networker

Since updating to PAN 3.1.7 the committing dialogue shows

device: Invalid address value 'NaN'

Nevertheless the rule installs successfull.

Does anybody have the same strange message?


Not applicable

I get the same error in 3.1.7

L6 Presenter

This is a bug in 3.1.7 and this message is harmless. Here's the KP link that provides more information.

Link removed, bug fixed in 3.1.8


L1 Bithead

I'm having the same issue. The documentation states that a 'Commit Force' will avoid the error; however, it is silent on the question of is the force is needed to actually get the configuration to commit. It would be helpful if we could get some guidance on the question of do we need to do the force or not.


L4 Transporter

Hi There,

Commit force simply supresses the message.  A regular commit still results in a success, assuming all other items are in order.



Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!