-
-
-
Traffic distribution in multiple routes based on five tuples information
-
Troubleshooting Routing Issues
-
Troubleshooting OSPF-Specific Issues
-
Configure to source NetScaler FreeBSD data traffic from a SNIP address
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Troubleshooting OSPF-Specific Issues
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:
- show interface from both nscli and VTYSH
- show ip ospf interface
- show ip ospf neighbor detail
- show ip route
- show ip ospf route
-
show ip ospf database summary
- 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.
- If there are a large number of LSAs in the database, enter the show ip ospf database self-originated command.
- show ip ospf
- show ns ip. This ensures that the details of all VIPs of interest are included.
-
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:
-
Enable logging of error messages by entering the following command from the global configuration view in VTYSH:
ns(config)# log file /var/ospf.log <!--NeedCopy-->
-
Enable debugging ospf events and log them by using the following command:
ns(config) #log file /var/ospf.log <!--NeedCopy-->
Enable debug ospf lsa packet only if the number of LSAs in the database is relatively small (< 500).
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.