Startup file XML for SFPs

Hi Steve,

What is the link partner? do you have control of that end or can you see how it is configured?

By default in our software release 5.1.0-GA, when the switch is configured for 1000BASE-SX/LX auto-neg is disabled. 

If the link partner has auto-neg enabled, this might interfere with the ability to bring up the link properly.

Can you please check if you can modify this on the link partner and see if can get traffic to/from the switch? 

The snippet from google isn't relevant for us.

We have a new release available now which supports configuring auto-neg for SX/LX modes. 

I've given you access to an updated version of software (6.0.0-GA) (via your myAnalog account). 

Please check your myAnalog account, go to resources->downloads and you should see two software packages (one is the EVK/GUI, the other is the TSN driver library). Resources | Analog Devices

There will be a formal update of our software (version 6.0.1) coming on the www.analog.com/adin6310 product page during next week. 

Specifically for software releases 6.0.x and onwards, there is support for auto-neg in the XML configuration , snippet from the fileSystemFolders->FS_SES_InstanceX XML file shown below( auto-neg field is highlighted yellow below). 

For the port configuration, you should only need to change the -if-type. Many of the other parameters are only relevant if there's a standard ethernet PHY connected. 

<interface>
<name>P1</name>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type>
<ethernet xmlns="urn:ieee:std:802.3:yang:ieee802-ethernet-interface">
<if-type xmlns="urn:adi:ses">sgmii-1000base-sxlx</if-type> <!-- MII supported values : rmii, rgmii, sgmii, sgmii-1000base-sxlx, sgmii-1000base-kx, sgmii-100base-fx -->
<!-- NOTE: for all sgmii mode, pass "unmanaged" to phy-type -->
<phy-rx-delay-supported xmlns="urn:adi:ses">false</phy-rx-delay-supported> <!-- RxDelay supported values : false, true (false = disabled, true = enabled) -->
<phy-tx-delay-supported xmlns="urn:adi:ses">false</phy-tx-delay-supported> <!-- TxDelay supported values : false, true (false = disabled, true = enabled) -->
<phy-type xmlns="urn:adi:ses">unmanaged </phy-type> <!-- PhyType supported values : adin1100, adin1200, adin1300, unmanaged -->
<clock-selection xmlns="urn:adi:ses">internal</clock-selection> <!-- ClockSelection supported values : internal, external -->
<phy-address xmlns="urn:adi:ses">1</phy-address> <!-- PhyAddress supported values : 0 to 255 -->
<link-polarity xmlns="urn:adi:ses">active-high</link-polarity> <!-- LinkPolarity supported values : active-low, active-high -->
<phy-pull-up-control xmlns="urn:adi:ses">internal</phy-pull-up-control> <!-- PhyPullupCtrl supported values : internal, external, do-not-disable -->
<speed xmlns="urn:adi:ses">1</speed> <!-- Speed supported values(in Gbps) : 1, 0.1, 0.01 -->
<duplex>full</duplex> <!-- PHY Duplex Mode : full, half, unknown -->
<auto-negotiation><enable>true</enable></auto-negotiation> <!-- Auto-negotiation supported values : true, false-->
</ethernet>
</interface>

Hope that helps, if you continue to struggle with getting sucessful link up, please share more information on the module, link partner etc. 

best regards,

Catherine. 

Catherine:

I was using a Microchip VSC7511 evaluation board on the other end of the link.  I swapped to a Cisco 350 series workgroup switch and the link comes right up, so I expect you are correct about auto-negotiation.  I will log into the Cisco switch and play with its settings and also look at the updated software.  The VSC7511 is unmanaged; I do have the code base and will try to see how it handles SFPs.   

____________

I checked things more thoroughly today.  The VSC7511 does have auto-negotiation enabled.  The 802.3 clause 37 advertisement is 0x0020 if that helps. I found a debug option in the config file that disables auto-negotiation, but that caused other problems and didn't work either.  I am trying to move on from this particular IC, so I don't plan to investigate further.  

The Cisco switch is a CBS350-8P-E-2G.  The web configuration GUI grays out auto-negotiation as soon as the switch detects an SFP.  The Cisco can talk to the VSC7511.

Anyway, I will move on to the 6.0.1 EVKSW so perhaps this is all moot.

Cheers,
-Steve

Catherine:

I checked things more thoroughly today.  The VSC7511 does have auto-negotiation enabled.  The 802.3 clause 37 advertisement is 0x0020 if that helps. I found a debug option in the config file that disables auto-negotiation, but that caused other problems and didn't work either.  I am trying to move on from this particular IC, so I don't plan to investigate further.  

The Cisco switch is a CBS350-8P-E-2G.  The web configuration GUI grays out auto-negotiation as soon as the switch detects an SFP.  The Cisco can talk to the VSC7511.

Behavior is the same with the 6.0.1 EVKSW.  Both devices can talk to the Cisco switch, but I feel the issue is more related to the VSC7511, which perhaps is not negotiating properly.  I'm going to consider this answered.  

Cheers,
-Steve

Thanks for update Steve, let us know if you have further questions. 

best regards,

Catherine.