-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Added Niagara TAP 3225-PTC-2 #3526
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
base: master
Are you sure you want to change the base?
Conversation
ebde9e7
to
6698bc7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a new Niagara passive TAP device (3225-PTC-2) with support for two single-width TAP modules. The device is configured as a 1U passive fiber optic network TAP with 25 module slots.
- Adds a new 25-slot passive TAP chassis device
- Includes two single-width TAP module definitions for different fiber types
- Provides modules for both 850nm multimode (SR) and 1310nm/1550nm single mode (LR) configurations
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
device-types/Niagara/3225-PTC-2.yaml | Defines the main 25-slot TAP chassis device |
module-types/Niagara/3211-S-SR-50-50.yaml | Single-width TAP module for 850nm multimode fiber |
module-types/Niagara/3211-S-LR-50-50.yaml | Single-width TAP module for 1310nm/1550nm single mode fiber |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
model: Network TAP Passive Fiber Optics Module Single Width 1310nm 1550nm 50/50 | ||
part_number: 3211-S-LR-50/50 | ||
comments: '[TAP Datasheet](https://info.niagaranetworks.com/hubfs/Product%20Data%20Sheets/3225/3225.pdf)' | ||
interfaces: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If these are passive taps then they won't have 100GB interfaces they will just be LC ports
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes they are passive but I can't put lc as an interface type. Should I move them to the front/rear ports?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes these should be probably front ports linked to the same rear ports, I guess is the best way
part_number: 3211-S-SR-50/50 | ||
comments: '[TAP Datasheet](https://info.niagaranetworks.com/hubfs/Product%20Data%20Sheets/3225/3225.pdf)' | ||
interfaces: | ||
- name: Port/{module}/A_Monitor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again if these are passive they should just be LC ports
model: Network TAP Passive Fiber Optics Module Single Width 1310nm 1550nm 50/50 | ||
part_number: 3211-S-LR-50/50 | ||
comments: '[TAP Datasheet](https://info.niagaranetworks.com/hubfs/Product%20Data%20Sheets/3225/3225.pdf)' | ||
interfaces: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes these should be probably front ports linked to the same rear ports, I guess is the best way
Added Niagara passive TAP 3225-PTC-2 with two single width taps.