Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wicket RSS display includes includes rack_network_config.bgp output as a sub item of the final uplink #7391

Open
leftwo opened this issue Jan 23, 2025 · 0 comments
Labels
wicket Operator Interaction Via Technician Port

Comments

@leftwo
Copy link
Contributor

leftwo commented Jan 23, 2025

We had a config-rss.toml with 4 BGP uplinks, and a final few lines for an asn and the originate array.

After the uplink configuration information, the toml file had this:

[[rack_network_config.bgp]]
asn = 65019
originate = ["10.101.240.0/21", "10.101.248.0/21"]

In the wicket screen when verifying the configuration before RSS, this item was included as a
member of the final uplink, and not an element on its own line as I believe it should have been:

Here is a small section of the output on wicket

 │                  ││Uplink 4: 
 │                  ││  • Port          : qsfp30 on switch switch1
 │                  ││  • Speed         : 100G  
 │                  ││  • FEC           : None   
 │                  ││  • Autoneg       : disabled  
 │                  ││  • Address       : 10.99.255.14/30 
 │                  ││  • BGP peer      : 10.99.255.13 asn=64044 port=qsfp30 
 │                  ││    Intervals     : hold=18s idle_hold=13s delay_open=0s connect_retry=30s keepalive=6s 
 │                  ││    Auth key      : key: TCP-MD5 (SHA-256: <sha hash redacted>) 
 │                  ││  • BGP config    : asn=65019 originate=10.101.240.0/21,10.101.248.0/21 
 │                  ││NTP servers:
 │                  ││  • 172.23.109.33
 │                  ││  • 172.22.101.170
 │                  ││  • 172.23.103.110

This config did work, and set things as expected, so it's most likely a display issue.

@askfongjojo askfongjojo added the wicket Operator Interaction Via Technician Port label Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wicket Operator Interaction Via Technician Port
Projects
None yet
Development

No branches or pull requests

2 participants