You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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?
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.
Hi,
In the usage example you use a device chassis (
PTX10008
) as theHardwareModel
. 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 expandingHardwareModel
to include both, the chassis and line card to accurately identify the port naming convention.Thanks!
The text was updated successfully, but these errors were encountered: