이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 8. Troubleshooting RHOSO dynamic routing
Diagnosing problems in a Red Hat OpenStack Services on OpenShift (RHOSO) environment that uses dynamic routing begins with examining the appropriate logs and querying the various FRRouting components with VTY shell.
8.1. OVN BGP agent and FRRouting logs 링크 복사링크가 클립보드에 복사되었습니다!
The OVN BGP agent writes its logs on the Compute and Networker nodes at this location: /var/log/containers/stdouts/ovn_bgp_agent.log.
The Free Range Routing (FRRouting, or FRR) components such as the BGP, BFD, and Zebra daemons write their logs on all Red Hat OpenStack Services on OpenShift (RHOSO) nodes at this location: /var/log/containers/frr/frr.log
8.2. Using VTY shell commands for troubleshooting BGP 링크 복사링크가 클립보드에 복사되었습니다!
You can use the shell for Virtual Terminal Interface (VTY shell) to interact with the Free Range Routing (FRRouting, or FRR) daemons. In Red Hat OpenStack Platform, FRR daemons like bgpd run inside a container. Using the VTY shell can help you troubleshoot BGP routing issues.
Prerequisites
- You must have sudo privileges on the host where you want to run VTY shell commands.
Procedure
-
Log in to the host where you want to troubleshoot the BGP daemon,
bgpd. Typically,bgpdruns on all of the overcloud nodes. Enter the FRR container.
$ sudo podman exec -it frr bashYou have two options for running VTY shell commands:
Interactive mode
Type
sudo vtyshonce to enter interactive mode to run multiple VTY shell commands.- Example
$ sudo vtysh > show bgp summary
Direct mode
Preface each VTY shell command with
sudo vtysh -c.- Example
$ sudo vtysh -c 'show bgp summary'
Here are several VTY shell BGP daemon troubleshooting commands:
TipOmit the
ipargument when you are using IPv6.- Display a particular routing table or all routing tables
> show ip bgp <IPv4_address> | all > show bgp <IPv6_address> | all- Output routes advertised to a BGP peer
> show ip bgp neighbors <router-ID> <advertised-routes>
+ Output routes received from a BGP peer::
> show ip bgp neighbors <router-ID> <received-routes>