-
Notifications
You must be signed in to change notification settings - Fork 1k
adding Watchguard T45 #3050
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?
adding Watchguard T45 #3050
Conversation
type: 1000base-t | ||
- name: eth4 | ||
type: 1000base-t | ||
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.
Rear ports are designed for patch panels not devices, standard USB ports on servers are not something that we are currently mapping in this repository
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.
The best way of modeling this would be to create the rack mount as a parent device with a device-bay
and then the t45 can be a child device and placed inside the rackmount kit. This is how the Palo PA220's are modeled.
Note: if this rack mount kit can support multiple different models as the image has a t20 then I would name it a 'Firebox-Rack-Mount-Kit.yaml' or something similar and adjust this image name accordingly.
manufacturer: WatchGuard | ||
model: Firebox T45 | ||
slug: watchguard-firebox-t45 | ||
u_height: 1.0 |
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.
Note, if you plan to make this a child device you will need to make the U height 0 otherwise you can't put the device in a device-bay
adding Watchguard T45, and images incl. one with 19" rackmount kit