Is that a passive copper cable or some sort of active fiber transceiver thing? If the latter, you might have to install a jumper on the snap to pull the SFP disable sfp high -- see this thread https://www.mail-archive.com/[email protected]/msg07371.html
This is in the process of being fixed in firmware. Sorry it's taking so long. On Tue, 11 Dec 2018, 2:13 pm David Marsh, <[email protected]> wrote: > Jack, > > We are using the 10GbE SFP+ port P1 on the SNAPv1 board. The cable that we > have between the snap and the server is XFP-SFP+ > > Thanks, > David > > On Tue, Dec 11, 2018 at 2:46 PM Jack Hickish <[email protected]> > wrote: > >> Hi David, >> >> What type of transceiver are you using on the snap, and which port are >> you using? >> >> Cheers >> Jack >> >> On Tue, 11 Dec 2018, 1:06 pm David Marsh, <[email protected]> wrote: >> >>> Hi all, >>> >>> I am having a similar issue (to >>> https://www.mail-archive.com/[email protected]/msg07245.html) >>> when trying to program the SNAP board and get an ip address for the 10GbE >>> port. >>> >>> I am able to program the golden image using a Raspberry Pi 3 b+. After >>> programming the image, these are the debug messages from the mini usb: >>> ICAP init ok >>> #JAM starting >>> Using ethernet core gbe0 >>> MAC 0x0034B6A31701 >>> IP 00000000 NM 00000000 GW 00000000 >>> link is DOWN >>> >>> I also used wireshark and no packets were received. I am assuming that >>> the problem is with the link and I was wondering if anyone had some ideas >>> on things to try to get the link up. >>> >>> Some other information that might be useful. >>> On the server side when running ip addr it outputs: >>> eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state UNKNOWN qlen 1000 >>> link/ether f4:52:14:4c:73:b0 brd ff:ff:ff:ff:ff:ff >>> inet 192.168.5.1/24 brd 192.168.5.255 scope global eth0 >>> >>> >>> A dhcp server was set up. Using the dhcp server we were able to assign >>> an ip address to the raspberry pi. For the 10Gbe port the server has the >>> following: >>> subnet 192.168.5.0 netmask 255.255.255.0 { >>> interface eth0; >>> range 192.168.5.10 192.168.5.100; >>> option routers 192.168.5.1; >>> option subnet-mask 255.255.255.0; >>> option broadcast-address 192.168.5.255; >>> } >>> >>> Any help is appreciated. >>> Thanks, >>> David >>> >>> >>> >>> >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "[email protected]" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "[email protected]" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> > -- > You received this message because you are subscribed to the Google Groups " > [email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].
