RARE user and assistance email list

[<>]

I just realized that I made a mistake, sigh. I mixed up the values for
RS and FC FEC. For the record: the correct numbers are

2  Firecode FEC
3  Reed-Solomon FEC

Sorry for the confusion :/

-- 
Alex

On Mon, 23 Aug 2021 15:58:36 +0200, <> said:

> On Mon, 23 Aug 2021 15:43:27 +0200, mc36 <> said:

>> not too much documentation exists on the topic, and the numbers are highly 
>> platform dependent...
>> for example wedge ports have different meaning compared to gearbox ports...

> What I'm piecing together from reading the source code (just to
> provide more help to Marcos, please correct if I'm saying anything
> wrong), the following should apply to all "Wedge" flavors:

> <fec> can be one of

> 0  undefined, interpreted as no FEC (not sure why this choice exists)
> 1  no FEC
> 2  Reed-Solomon FEC
> 3  Firecode FEC

> In this case, only 1 or 2 are valid choices (though 0 is equivalent to
> 1).  <autoneg> should be 0 (I think) and <flow-control> is effectively
> ignored.

> -- 
> Alex


>> regards,
>> cs

>> mchome(cfg-server)#export-port ?
>> <name> - interface name

>> mchome(cfg-server)#export-port sdn13 ?
>> <num> - port number

>> mchome(cfg-server)#export-port sdn13 123 ?
>> <cr>
>> <num> - speed in gbps

>> mchome(cfg-server)#export-port sdn13 123 1 ?
>> <cr>
>> <num> - fec, see hw vendor manual

>> mchome(cfg-server)#export-port sdn13 123 1 2 ?
>> <cr>
>> <num> - autoneg, see hw vendor manual

>> mchome(cfg-server)#export-port sdn13 123 1 2 3?
>> type <num> to autoneg, see hw vendor manual

>> mchome(cfg-server)#export-port sdn13 123 1 2 3 ?
>> <cr>
>> <num> - flowctrl, see hw vendor manual

>> mchome(cfg-server)#export-port sdn13 123 1 2 3 4 ?
>> <cr>

>> mchome(cfg-server)#


>> On 8/23/21 2:43 PM, Marcos Felipe Schwarz wrote:
>>> Thank you for all information!
>>> 
>>> Is there a documentation where I can have the meaning of the fields? It 
>>> will help our team.
>>> I expect something like:
>>> export-port  port_name tofino_port_id, rs_feec, autonegotiation, ?
>>> export-port sdn7 180 100 1 1 0
>>> 
>>> Regards,
>>> 
>>> Marcos Schwarz
>>> 
>>> -----Mensagem original-----
>>> De:  <>
>>> Enviada em: segunda-feira, 23 de agosto de 2021 05:45
>>> Para: 
>>> Cc: ; Marcos Felipe Schwarz 
>>> <>; Pedro Diniz <>; 
>>> Fernando Nazareno Nascimento Farias <>; Michael 
>>> Prieto Hernandez <>
>>> Assunto: Re: [RARE-users] RES: Wedge interconnection using Juniper DAC 
>>> cable.
>>> 
>>> On Sat, 21 Aug 2021 12:39:24 +0200, mc36 <> said:
>>> 
>>>> as far as i know, for 100g, the setting the fec is mandatory...
>>> 
>>> Not in general, e.g. it's not mandatory for LR4 or ER4. But it is 
>>> mandatory for SR4, which is what AOC is. However, it is usually 
>>> configurable anyway. I have used the same 3m AOC successfully with and 
>>> without FEC with the Wedge, as long as both sides are configured the 
>>> same.  By default, Juniper (and Cisco as well) enables FEC with SR4.
>>> 
>>> To answer Marcos' question in more detail: either disable FEC on the 
>>> Juniper or enable it on the Wedge with (unfortunately this is a bit 
>>> cryptic, the first "1" after the speed setting enables RS-FEC)
>>> 
>>> export-port sdn7 180 100 1 1 0
>>> 
>>> --
>>> Alex
>>> 
>>>> regards,
>>>> cs
>>> 
>>> 
>>>> On 8/20/21 3:39 PM, Marcos Felipe Schwarz wrote:
>>>>> Just correcting that the cable is AOC not DAC.
>>>>> 
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Marcos Schwarz
>>>>> 
>>>>> *De:*Marcos Felipe Schwarz
>>>>> *Enviada em:* sexta-feira, 20 de agosto de 2021 08:52
>>>>> *Para:* 
>>>>> *Cc:* Pedro Diniz <>; Fernando Nazareno
>>>>> Nascimento Farias <>; Michael Prieto Hernandez
>>>>> <>
>>>>> *Assunto:* Wedge interconnection using Juniper DAC cable.
>>>>> 
>>>>> Hi everyone,
>>>>> 
>>>>> We are using RARE OS at RNP on a EdgeCore Wedge, and we are trying to 
>>>>> setup an interconnect from it to a Juniper Router using a 100G DAC 
>>>>> cable from Juniper.
>>>>> 
>>>>> I setup the port using the configuration below, but the cort continues 
>>>>> DOWN. IÃ,â?Td like some help with the configuration or with some 
>>>>> troubleshoot options to try to find the problem.
>>>>> 
>>>>> interface sdn7
>>>>> 
>>>>> lldp enable
>>>>> 
>>>>> vrf forwarding inet
>>>>> 
>>>>> ipv4 address 200.143.232.255 255.255.255.254
>>>>> 
>>>>> no shutdown
>>>>> 
>>>>> log-link-change
>>>>> 
>>>>> exit
>>>>> 
>>>>> server p4lang p4
>>>>> 
>>>>> export-port sdn7 180 100 0 1 0
>>>>> 
>>>>> exit
>>>>> 
>>>>> -----+----+---+----+-------+----+--+--+---+---+---+--------+----------------+----------------+-
>>>>> 
>>>>> PORT |MAC |D_P|P/PT|SPEEDÃ,  |FEC |AN|KR|RDY|ADM|OPR|LPBKÃ, Ã, Ã,
>>>>> |FRAMES RXÃ, Ã, Ã, Ã, Ã, Ã,  |FRAMES TXÃ, Ã, Ã, Ã, Ã, Ã,  |E
>>>>> 
>>>>> -----+----+---+----+-------+----+--+--+---+---+---+--------+----------------+----------------+-
>>>>> 
>>>>> 7/0Ã,  |17/0|180|3/52|100GÃ, Ã,  |NONE|Ds|Au|YES|ENB|DWN|Ã,  
>>>>> NONEÃ,  |Ã, Ã,
>>>>> Ã, Ã, Ã, Ã, Ã, Ã, Ã, Ã, Ã, Ã, Ã, Ã,  0|Ã, Ã, Ã, Ã, Ã, 
>>>>> Ã, Ã, Ã, Ã, Ã, Ã, Ã, Ã, Ã,  0|
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Marcos Schwarz
>>>>> 
>>>>> *Gerente de P&D | /R&D Manager/*
>>>>> 
>>>>> GerÃfªncia de ExecuÃf§Ãf£o de P&D em Ciberinfraestrutura | 
>>>>> /Management
>>>>> of R&D Execution in Cyberinfrastructure/
>>>>> 
>>>>> Diretoria de Pesquisa e Desenvolvimento | /Board of Research and
>>>>> Development/
>>>>> 
>>>>> RNP - Rede Nacional de Ensino e Pesquisa | /Brazilian National
>>>>> Research and Educational Network/
>>>>> 
>>>>> Promovendo o uso inovador de redes avanÃf§adas | /Promoting the
>>>>> innovative use of advanced networks/
>>>>> 
>>>>> http://www.rnp.br <http://www.rnp.br/> | +55 (19) 3787-3386 | Skype
>>>>> ID: marcos.f.sch**
>>>>> 
>>>>> Campinas - SP - Brasil | E-mail: 
>>>>> <>
>>>>>