cannot ping serverip from u-boot.

cannot ping serverip from u-boot.

[Mahesh Kurapati]

[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]

Hi all,

I am using openbmc-2.9.0 on AST2500 BMC.  From the u-boot, I could not ping to any external node be it on the same network, or a different network.  I configured static ip 192.168.0.81 for my laptop and attached wireshark to the same interface.  I don't see any ARP requests when I issued ping command from BMC to the laptop.  I see that link status is up from the debug prints, and also the MDIO status registers.  Don't see anything wrong.  Not sure what/where to look for to debug the issue further.  Appreciate any suggestions.  We are using Marvel Alaska 88 series Phy.  If this works, I want to tftpboot the board, and flash the eMMC.  That is my goal.

ast# printenv
baudrate=115200
bootargs=console=ttyS4,115200n8 root=/dev/ram rw
bootcmd=bootm 20080000
bootdelay=2
bootfile=all.bin
eth1addr=c2:d1:29:f8:1b:e3
ethact=ethernet@1e680000
ethaddr=be:f3:fa:8c:cd:e8
fdtcontroladdr=bcf82138
gatewayip=192.168.0.1
ipaddr=192.168.0.45
netmask=255.255.255.0
serverip=192.168.0.81
stderr=serial@1e784000
stdin=serial@1e784000
stdout=serial@1e784000
verify=yes
ast#

ast# ping $serverip
Trying ethernet@1e680000
ethernet@1e680000: link up, 1000 Mbps full-duplex mac:c2:d1:29:f8:1b:e3
Using ethernet@1e680000 device
ARP broadcast 1
ARP broadcast 2
ARP broadcast 3
ARP broadcast 4

ARP Retry count exceeded; starting again
ping failed; host 192.168.0.81 is not alive
ast#

ast# mdio read  1.0-60
Reading from bus eth1
PHY at address 1:
1.0 - 0x1000
1.1 - 0x796d  ===>link is up
1.2 - 0x141
1.3 - 0xdd4
1.4 - 0x21e1
1.5 - 0xc5e1
1.6 - 0xd
1.7 - 0x2001
1.8 - 0x4a38
1.9 - 0x300
1.10 - 0x3800
1.11 - 0x0
1.12 - 0x0
1.13 - 0x3
1.14 - 0x0
1.15 - 0x3000
1.16 - 0x3070
1.17 - 0xac08
1.18 - 0x0
1.19 - 0x0
1.20 - 0x20
1.21 - 0x0
1.22 - 0x0
1.23 - 0x0
1.24 - 0x0
1.25 - 0x0
1.26 - 0x40
1.27 - 0x0
1.28 - 0x0
1.29 - 0x0
1.30 - 0x0

Thank you,
Mahesh


[-- Attachment #2: Type: text/html, Size: 10028 bytes --]

Re: cannot ping serverip from u-boot.

[Johnathan Mantey]

[-- Attachment #1.1: Type: text/plain, Size: 2864 bytes --]

On 10/26/21 10:53, Mahesh Kurapati wrote:
> Hi all,
> 
> I am using openbmc-2.9.0 on AST2500 BMC.  From the u-boot, I could not 
> ping to any external node be it on the same network, or a different 
> network.  I configured static ip 192.168.0.81 for my laptop and attached 
> wireshark to the same interface. I don’t see any ARP requests when I 
> issued ping command from BMC to the laptop.  I see that link status is 
> up from the debug prints, and also the MDIO status registers.  Don’t see 
> anything wrong.  Not sure what/where to look for to debug the issue 
> further. Appreciate any suggestions.  We are using Marvel Alaska 88 
> series Phy.  If this works, I want to tftpboot the board, and flash the 
> eMMC.  That is my goal.

Does your system have two NICs?

Is your network cable plugged into the NIC specified by the ethact 
U-Boot setting?

Have you tried changing the ethact line to point to the second NIC 
address (e.g. ethernet@1e690000)?

> 
> ast# printenv
> 
> baudrate=115200
> 
> bootargs=console=ttyS4,115200n8 root=/dev/ram rw
> 
> bootcmd=bootm 20080000
> 
> bootdelay=2
> 
> bootfile=all.bin
> 
> eth1addr=c2:d1:29:f8:1b:e3
> 
> ethact=ethernet@1e680000
> 
> ethaddr=be:f3:fa:8c:cd:e8
> 
> fdtcontroladdr=bcf82138
> 
> gatewayip=192.168.0.1
> 
> ipaddr=192.168.0.45
> 
> netmask=255.255.255.0
> 
> serverip=192.168.0.81
> 
> stderr=serial@1e784000
> 
> stdin=serial@1e784000
> 
> stdout=serial@1e784000
> 
> verify=yes
> 
> ast#
> 
> ast# ping $serverip
> 
> Trying ethernet@1e680000
> 
> ethernet@1e680000: link up, 1000 Mbps full-duplex mac:c2:d1:29:f8:1b:e3
> 
> Using ethernet@1e680000 device
> 
> ARP broadcast 1
> 
> ARP broadcast 2
> 
> ARP broadcast 3
> 
> ARP broadcast 4
> 
> ARP Retry count exceeded; starting again
> 
> ping failed; host 192.168.0.81 is not alive
> 
> ast#
> 
> ast# mdio read  1.0-60
> 
> Reading from bus eth1
> 
> PHY at address 1:
> 
> 1.0 - 0x1000
> 
> 1.1 - 0x796d  =èlink is up
> 
> 1.2 - 0x141
> 
> 1.3 - 0xdd4
> 
> 1.4 - 0x21e1
> 
> 1.5 - 0xc5e1
> 
> 1.6 - 0xd
> 
> 1.7 - 0x2001
> 
> 1.8 - 0x4a38
> 
> 1.9 - 0x300
> 
> 1.10 - 0x3800
> 
> 1.11 - 0x0
> 
> 1.12 - 0x0
> 
> 1.13 - 0x3
> 
> 1.14 - 0x0
> 
> 1.15 - 0x3000
> 
> 1.16 - 0x3070
> 
> 1.17 - 0xac08
> 
> 1.18 - 0x0
> 
> 1.19 - 0x0
> 
> 1.20 - 0x20
> 
> 1.21 - 0x0
> 
> 1.22 - 0x0
> 
> 1.23 - 0x0
> 
> 1.24 - 0x0
> 
> 1.25 - 0x0
> 
> 1.26 - 0x40
> 
> 1.27 - 0x0
> 
> 1.28 - 0x0
> 
> 1.29 - 0x0
> 
> 1.30 - 0x0
> 
> Thank you,
> 
> Mahesh
> 

-- 
Johnathan Mantey
Senior Software Engineer
*azad te**chnology partners*
Contributing to Technology Innovation since 1992
Phone: (503) 712-6764
Email: johnathanx.mantey@intel.com <mailto:johnathanx.mantey@intel.com>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

RE: cannot ping serverip from u-boot.

[Mahesh Kurapati]

Hello Jonathan, 

We have two NICs.  One is connected to i350 for NC-SI, and other one is over the Marvel PHY on which I am trying to connect.  ethact variable is set correctly. I have not tried the NC-SI Interface @1e660000).

Thank you
Mahesh

-----Original Message-----
From: Johnathan Mantey <johnathanx.mantey@intel.com> 
Sent: Tuesday, October 26, 2021 2:54 PM
To: Mahesh Kurapati <mahesh.kurapati@keysight.com>; openbmc@lists.ozlabs.org
Subject: Re: cannot ping serverip from u-boot.

On 10/26/21 10:53, Mahesh Kurapati wrote:
> Hi all,
> 
> I am using openbmc-2.9.0 on AST2500 BMC.  From the u-boot, I could not 
> ping to any external node be it on the same network, or a different 
> network.  I configured static ip 192.168.0.81 for my laptop and 
> attached wireshark to the same interface. I don’t see any ARP requests 
> when I issued ping command from BMC to the laptop.  I see that link 
> status is up from the debug prints, and also the MDIO status 
> registers.  Don’t see anything wrong.  Not sure what/where to look for 
> to debug the issue further. Appreciate any suggestions.  We are using 
> Marvel Alaska 88 series Phy.  If this works, I want to tftpboot the 
> board, and flash the eMMC.  That is my goal.

Does your system have two NICs?

Is your network cable plugged into the NIC specified by the ethact U-Boot setting?

Have you tried changing the ethact line to point to the second NIC address (e.g. ethernet@1e690000)?

> 
> ast# printenv
> 
> baudrate=115200
> 
> bootargs=console=ttyS4,115200n8 root=/dev/ram rw
> 
> bootcmd=bootm 20080000
> 
> bootdelay=2
> 
> bootfile=all.bin
> 
> eth1addr=c2:d1:29:f8:1b:e3
> 
> ethact=ethernet@1e680000
> 
> ethaddr=be:f3:fa:8c:cd:e8
> 
> fdtcontroladdr=bcf82138
> 
> gatewayip=192.168.0.1
> 
> ipaddr=192.168.0.45
> 
> netmask=255.255.255.0
> 
> serverip=192.168.0.81
> 
> stderr=serial@1e784000
> 
> stdin=serial@1e784000
> 
> stdout=serial@1e784000
> 
> verify=yes
> 
> ast#
> 
> ast# ping $serverip
> 
> Trying ethernet@1e680000
> 
> ethernet@1e680000: link up, 1000 Mbps full-duplex 
> mac:c2:d1:29:f8:1b:e3
> 
> Using ethernet@1e680000 device
> 
> ARP broadcast 1
> 
> ARP broadcast 2
> 
> ARP broadcast 3
> 
> ARP broadcast 4
> 
> ARP Retry count exceeded; starting again
> 
> ping failed; host 192.168.0.81 is not alive
> 
> ast#
> 
> ast# mdio read  1.0-60
> 
> Reading from bus eth1
> 
> PHY at address 1:
> 
> 1.0 - 0x1000
> 
> 1.1 - 0x796d  =èlink is up
> 
> 1.2 - 0x141
> 
> 1.3 - 0xdd4
> 
> 1.4 - 0x21e1
> 
> 1.5 - 0xc5e1
> 
> 1.6 - 0xd
> 
> 1.7 - 0x2001
> 
> 1.8 - 0x4a38
> 
> 1.9 - 0x300
> 
> 1.10 - 0x3800
> 
> 1.11 - 0x0
> 
> 1.12 - 0x0
> 
> 1.13 - 0x3
> 
> 1.14 - 0x0
> 
> 1.15 - 0x3000
> 
> 1.16 - 0x3070
> 
> 1.17 - 0xac08
> 
> 1.18 - 0x0
> 
> 1.19 - 0x0
> 
> 1.20 - 0x20
> 
> 1.21 - 0x0
> 
> 1.22 - 0x0
> 
> 1.23 - 0x0
> 
> 1.24 - 0x0
> 
> 1.25 - 0x0
> 
> 1.26 - 0x40
> 
> 1.27 - 0x0
> 
> 1.28 - 0x0
> 
> 1.29 - 0x0
> 
> 1.30 - 0x0
> 
> Thank you,
> 
> Mahesh
> 

--
Johnathan Mantey
Senior Software Engineer
*azad te**chnology partners*
Contributing to Technology Innovation since 1992
Phone: (503) 712-6764
Email: johnathanx.mantey@intel.com <mailto:johnathanx.mantey@intel.com>