Troubleshooting Network Publisher Operations

Problem

The network publisher is not collecting the expected data.

Solution

1. Make sure that the network publisher can connect to the configured routers.
2. Make sure that authentication is configured correctly for the network publisher and on the router.
3. Verify the configuration for the network publisher.

   [edit slot 0 network-publisher]

   user@host# show

   directory-connection {

   url ldap://127.0.0.1:389;

   base-dn o=Network,o=UMC;

   principal cn=umcadmin,o=umc;

   credentials ********;

   }

   select {

   }

   logger log1 {

   file {

   filter /debug-;

   filename var/log/netpub_debug.log;

   rollover-filename var/log/netpub_debug.alt;

   maximum-file-size 2000000000;

   }

   }

   logger log2 {

   file {

   filter /info-;

   filename var/log/netpub_info.log;

   rollover-filename var/log/netpub_info.alt;

   maximum-file-size 2000000000;

   }

   }

   logger log3 {

   file {

   filter /error-;

   filename var/log/netpub_error.log;

   rollover-filename var/log/netpub_error.alt;

   maximum-file-size 2000000000;

   }

   }

   routers {

   router-release-number 7.6R1;

   authentication {

   login-name admin2;

   credentials ********;

   }

   router elf {

   address 10.227.7.115;

   }

   router giant {

   address 10.227.7.124;

   }

   }

4. Configure the network publisher to use an input file to ensure that the network publisher is collecting information as configured. Modify the content of the input file to reflect the router information.

   See Configuring Information to Test the Network Publisher

5. Configure the network publisher to use an output file, and review the file.

   See Reviewing the Information Collected from a JUNOS Routing Platform

Related Topics

• Overview of the Network Publisher
• Before You Configure and Run the Network Publisher
• Configuring the Network Publisher

Copyright © 2008, Juniper Networks, Inc. All Rights Reserved. Trademark Notice.