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

Can not specify link speed when adding generic system #952

Open
bauerclm opened this issue Oct 24, 2024 · 1 comment
Open

Can not specify link speed when adding generic system #952

bauerclm opened this issue Oct 24, 2024 · 1 comment

Comments

@bauerclm
Copy link

I am trying to add an external system to a rack with this code:

resource "apstra_datacenter_generic_system" "dci"{
blueprint_id = apstra_datacenter_blueprint.datacenter.id
hostname = "dci"
name = "dci"
external = true
links = [
{
target_switch_id = local.rack1_leaf1.id
target_switch_if_name = "et-0/0/52"
target_switch_if_transform_id = 1
}
]
}

the link is made but it creates a logical device for the external system that uses 40 gb speeds for the et interface but I want to make those links 100 gb. I don't see anywhere in the docs where I can specify the logical device of the external system or anywhere to specify the link speed.

@chrismarget-j
Copy link
Collaborator

Hi @bauerclm,

Thank you for opening this issue.

We don't require you to (allow you to? same difference, I guess) specify a logical device when creating a system within a blueprint because it has little to no effect on the outcome.

You'll note that the web UI, while it asks for a logical device, would produce the same result with "et-0/0/52" and transform # 1, regardless of what logical device you select. It will also allow you to make 100Gb/s connections to logical devices with only 40Gb/s interfaces.

If you look at a transaction sent by terraform (blueprint -> staged -> tasks -> task ID -> request data), you'll see that we send a bogus logical device with a single 100Mb/s interface with every request, every time, no matter what.

Selecting the proper speed for each link really comes down to:

  • the interface name
  • the transform ID

Interface name obviously has implications where breakout is concerned (et-0/0/0 vs. et-0/0/0:0), but can also be relevant in some cases as a speed call-out. For example, Juniper MX304 2xLMIC16 MDP refers to the same physical interface as "ge", "xe" and "et" depending on the context.

If we ignore breakout scenarios, the selection usually comes down to the transform ID.

When you're not sure what name or transform to use (I never am), do a dry run in the web UI. You'll find that you're required to select/activate one of these colored buttons before the "Add Link" button becomes available. Making that selection is the web UI's way of specifying both of these fields.

Screenshot 2024-10-31 at 9 30 25 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants