Product Documentation

Troubleshooting OSPF-Specific Issues

Mar 20, 2012

Before you start debugging any OSPF specific issue, you must collect information from the NetScaler appliance and all systems in the affected LAN, including upstream and downstream routers. To begin, enter the following commands:

  1. show interface from both nscli and VTYSH
  2. show ip ospf interface
  3. show ip ospf neighbor detail
  4. show ip route
  5. show ip ospf route
  6. show ip ospf database summary
    1. If there are only few LSAs in the database, then enter show ip ospf database router, show ip ospf database A. network, show ip ospf database external, and other commands to get the full details of LSAs.
    2. If there are a large number of LSAs in the database, enter the show ip ospf database self-originated command.
  7. show ip ospf
  8. show ns ip. This ensures that the details of all VIPs of interest are included.
  9. Get the logs from peering devices and run the following command:

    gcore -s -c xyz.core /netscaler/ospfd <pid>

Note: The gcore command is non-disruptive.
Collect additional information from the NetScaler as follows:
  1. Enable logging of error messages by entering the following command from the global configuration view in VTYSH:

    ns(config)#log file /var/ospf.log

  2. Enable debugging ospf events and log them by using the following command:

    ns(config)#log file /var/ospf.log

    Enable debug ospf lsa packet only if the number of LSAs in the database is relatively small (< 500).