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

VRF name changed when using multiple VRFs #212

Closed
ServerForge opened this issue Aug 27, 2022 · 0 comments
Closed

VRF name changed when using multiple VRFs #212

ServerForge opened this issue Aug 27, 2022 · 0 comments
Labels
fixed-in-next-release Issue has already been fixed in the next release

Comments

@ServerForge
Copy link

Bug Description

When you define multiple VRFs for a single router you get a selector on the page to choose the route table, However it appears to change the VRF name so only the first letter is capaitalized causing the "VRF is not defined." Error because it has changed the name.

Expected behavior

The VRF name should not be altered from what is defined in the config file.

Steps to Reproduce

Setup multiple routers with multiple and overlapping VRFs.

Local Configurations

  • name: Hampton, VA-1
    address: 2a0e:b100:107::101
    network:
    name: production
    display_name: AS207556
    credential:
    username: redacted
    key: redacted
    port: 22
    nos: linux
    vrfs:
    • name: AS207556
      ipv4:
      source_address: 23.136.232.26
      ipv6:
      source_address: 2a0e:b100:107::101
    • name: AS23428
      ipv4: null
      ipv6:
      source_address: 2602:fb68:c0::0

Logs

<logs>

Possible Solution

Environment

Server

Metric Value
hyperglass Version 1.0.4
hyperglass Path /etc/hyperglass
Python Version 3.7.13
Node Version 14.19.1
Platform Info Linux-5.15.0-43-generic-x86_64-with-Ubuntu-22.04-jammy
CPU Info Common KVM processor
Logical Cores 16
Physical Cores 16
Processor Speed 2.493988GHz
Total Memory 8.33 GB
Memory Utilization 16.3%
Total Disk Space 134.68 GB
Disk Utilization 8.6%

Client

  • OS & Version: Windows 11
  • Browser: Chrome

Smartphone Details (if applicable)

  • Device:
  • OS:
  • Browser:
@ServerForge ServerForge added the possible-bug Something isn't working label Aug 27, 2022
@thatmattlove thatmattlove added fixed-in-next-release Issue has already been fixed in the next release and removed possible-bug Something isn't working labels Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed-in-next-release Issue has already been fixed in the next release
Projects
None yet
Development

No branches or pull requests

2 participants