Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Troubleshooting Puppet for Junos OS Errors

The following sections outline errors that you might encounter when using Puppet to manage devices running Junos OS. These sections also present potential causes and solutions for each error.

Troubleshooting Junos OS Configuration Exclusive Lock Errors

Problem

Description

The Puppet agent cannot obtain an exclusive lock on the configuration. Thus, the dependency on the netdev_device fails causing the Puppet agent to skip configuration updates for all netdev resources.

Cause

Another user currently has the exclusive lock on the candidate configuration or is modifying the configuration.

The following sample error output indicates that the configuration database is locked by another user:

The following sample error output indicates that the configuration database has modifications in progress:

Solution

Wait until the lock on the configuration is released. When the Puppet agent retrieves the configuration and can obtain an exclusive lock on the configuration database, the agent updates the system configuration accordingly.

Troubleshooting Junos OS Configuration Load Errors

Problem

Description

The Puppet agent is unable to load the requested configuration changes into the candidate configuration.

Cause

The configuration change might contain invalid syntax, elements, or values.

The following sample error output indicates that the Puppet agent attempted to set the VLAN ID to 9999, which is out of the accepted range of 1 through 4094:

Solution

Correct the corresponding Puppet manifest file so that it contains valid configuration changes for the agent node.

Troubleshooting Junos OS Configuration Commit Errors

Problem

Description

The Puppet agent is unable to commit the requested configuration changes.

Cause

The configuration change might contain invalid syntax, elements, or values.

The following sample error output indicates that the Puppet agent attempted to associate an interface with a nonexistent VLAN:

Solution

Correct the corresponding Puppet manifest file so that it contains valid configuration changes for the agent node.

Troubleshooting Junos OS Configuration Errors

Problem

Description

The log files indicate that the Puppet agent successfully committed the configuration, but the agent node does not reflect the desired configuration changes.

Cause

There can be multiple reasons why the agent node does not reflect the correct configuration.

  • The Puppet manifest contains incorrect configuration information.

  • The Puppet agent has not yet performed the configuration update for the latest catalog.

    To verify that the Puppet agent has downloaded and committed a specific catalog, issue the show system commit operational mode command on the agent node running Junos OS to view the commit history and catalog versions.

Solution

If the Puppet manifest file contains incorrect configuration changes, correct the file to include the desired configuration changes for the agent node.

If the Puppet agent has not yet installed the changes in the latest catalog, wait until the update is made and then verify the configuration.

Troubleshooting Agent Errors on an EX4300 Switch

Problem

Description

On an EX4300 switch, the Puppet agent reports errors during a run which involves configuring a large number of number of VLANs. For example, you might see a “Could not send report” or "Could not run: failed to allocate memory" message.

Cause

Memory limitation on EX4300 devices.

Solution

Divide the VLAN configuration across multiple manifest files and apply each manifest file in a separate Puppet agent run.

For example, suppose you have 1024 VLANs. You can split the VLAN configuration across four manifest files (vlan1.pp, vlan2.pp, vlan3.pp, and vlan4.pp) so that each manifest file contains configuration for 256 VLANs. Then run the Puppet agent four times, changing the node definition in the main manifest file as follows on each agent run:

  • First agent run:

  • Second agent run:

  • Third agent run:

  • Fourth agent run: