Configuration Error for peeringdb-cache in Pathvector
Opened this issue · 0 comments
Description:
I'm encountering an issue with the configuration in the Pathvector documentation related to the peeringdb-cache option. According to the documentation under Configuration, it suggests using a boolean value for the peeringdb-cache setting. I have set it to false, but when I run Pathvector, I receive the following error:
FATA[0000] YAML unmarshal: yaml: unmarshal errors:
line 92: field peeringdb-cache not found in type config.Peer
Objective:
I want to configure a specific peer such that Pathvector does not read data from PeeringDB. My intention is to prevent Pathvector from automatically fetching information from PeeringDB for a particular peer.
Steps to Reproduce:
Add peeringdb-cache: false under the peer configuration in the /etc/pathvector.yml
Run Pathvector.
The error occurs on line 92 of the configuration file:
line 92: field peeringdb-cache not found in type config.Peer
Expected Behavior:
Pathvector should allow the option to disable PeeringDB data fetching for specific peers when peeringdb-cache is set to false, as indicated by the documentation.
Actual Behavior:
Instead, Pathvector throws an unmarshal error, indicating that the peeringdb-cache field is not found in config.Peer.
Questions:
Is there a different configuration option I should be using to prevent Pathvector from reading PeeringDB data for a specific peer?
Is the peeringdb-cache option not applicable to individual peers, or is it a global setting?
Additional Information:
Pathvector version: 6.3.2
Configuration file snippet:
xxxIX:
asn: 49962
template: routeserver
local-pref: 150
import-limit6: 9999999
peeringdb-cache: false
neighbors:
- xx.xx.xx.xx
- xx:xx:xx:xx::x
Thank you for your support!