Skip to Content.
Sympa Menu

rare-dev - Re: [rare-dev] [RARE-users] RARE/freeRtr first release for [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and APS6064X]

Subject: Rare project developers

List archive

Re: [rare-dev] [RARE-users] RARE/freeRtr first release for [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and APS6064X]


Chronological Thread 
  • From: mc36 <>
  • To: Eoin Kenny <>, Alexander Gall <>
  • Cc: "" <>, "" <>
  • Subject: Re: [rare-dev] [RARE-users] RARE/freeRtr first release for [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and APS6064X]
  • Date: Fri, 15 Jul 2022 11:05:27 +0200

hi,

On 7/15/22 10:33, Eoin Kenny wrote:
So I think I should use port "sdn156" to identify the QSFP in port 49. Is
this correct?
The reason I have doubts is that the output of "show p4land p4 port-names"
does not reference frontpanel-49/x or port 156.

you're right, first of all, that seemingly the bfforwarder does not populate
the upper ports available on this platform...
fortunately enough, later, it does not enforce the discovery so, you should
be able to bring up the port with the following:

int sdn49
desc qsfp 49/0 to xxx
exit
serv p4 p4
export-port sdn49 156 100 3 1 1
exit

you may need to adjust the numbers, 3 could be 2 depending on the fec in use
on the link,
also, the first 1 could be 2 if the autoneg is in use on the link...

br,
cs



Archive powered by MHonArc 2.6.19.

Top of Page