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

Break down of Device Chassis and LineCard #35

Open
nleiva opened this issue Jun 27, 2024 · 2 comments
Open

Break down of Device Chassis and LineCard #35

nleiva opened this issue Jun 27, 2024 · 2 comments
Assignees

Comments

@nleiva
Copy link

nleiva commented Jun 27, 2024

Hi,

In the usage example you use a device chassis (PTX10008) as the HardwareModel. If you used a different chassis (MX960 for example), the port name might depend on the line card per chassis slot. I'm wondering if you considered expanding HardwareModel to include both, the chassis and line card to accurately identify the port naming convention.

Thanks!

@lgomez9
Copy link

lgomez9 commented Jul 22, 2024

Hi again Nicolas,

I had not realized this dependency existed, but that is a good question. I don't think we've had a use case where that has come up yet, but I'm all for preparation. Do you know how many models have this line card per chassis slot <-> port name dependency?

@nleiva
Copy link
Author

nleiva commented Jul 24, 2024

I'm not a Hardware expert, but I believe Juniper probably has more than a hundred different Modular Interface Cards (MICs) or Physical Interface Cards (PICs) for the MX Series that name the ports from ge, te, et to so.

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