User Tools

Site Tools


documentation:end-users_docs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
documentation:end-users_docs [2019/06/04 15:24]
olivier [Hardware Compatibility List]
documentation:end-users_docs [2020/01/16 17:58] (current)
olivier [Enabling crash dump]
Line 8: Line 8:
   * a minimum of 512MB RAM.   * a minimum of 512MB RAM.
  
-[[https://​www.freebsd.org/​releases/​12.0R/​hardware.html|All hardware supported by FreeBSD 12]] are supported by BSDRP with the exception of following drivers:+[[https://​www.freebsd.org/​releases/​12.1R/​hardware.html|All hardware supported by FreeBSD 12.1]] are supported by BSDRP with the exception of following drivers:
  
 Wireless, PCMCIA cards, SCSI adapters, USB printer, fire wire, etc. drivers were removed from the FreeBSD kernel. Wireless, PCMCIA cards, SCSI adapters, USB printer, fire wire, etc. drivers were removed from the FreeBSD kernel.
Line 187: Line 187:
 <​code>​ <​code>​
 fetch '​http://​URL/​BSDRP-upgrade.image.xz'​ -o - | xzcat | upgrade fetch '​http://​URL/​BSDRP-upgrade.image.xz'​ -o - | xzcat | upgrade
 +</​code>​
 +
 +Real example to upgrade to 1.96:
 +<​code>​
 +fetch '​https://​sourceforge.net/​projects/​bsdrp/​files/​BSD_Router_Project/​1.96/​amd64/​BSDRP-1.96-upgrade-amd64-serial.img.xz/​download'​ -o - | xzcat | upgrade
 </​code>​ </​code>​
  
Line 405: Line 410:
 BSDRP v1.4 and earlier have a default configuration that prevent remote syslog. This behavior can be changed by editing /​etc/​rc.conf.misc and replacing syslogd_flags="​-ss"​ by syslogd_falgs="​-s"​ BSDRP v1.4 and earlier have a default configuration that prevent remote syslog. This behavior can be changed by editing /​etc/​rc.conf.misc and replacing syslogd_flags="​-ss"​ by syslogd_falgs="​-s"​
 </​note>​ </​note>​
 +
 +==== Firmware Upgrade ====
 +
 +=== Mellanox ===
 +
 +Stat by identifying your NIC ID:
 +<​code>​
 +# mstfwmanager
 +Querying Mellanox devices firmware ...
 +
 +Device #1:
 +----------
 +
 +  Device Type:      ConnectX4
 +  Part Number: ​     MCX416A-CCA_Ax
 +  Description: ​     ConnectX-4 EN network interface card; 100GbE dual-port QSFP28; PCIe3.0 x16; ROHS R6
 +  PSID:             ​MT_2150110033
 +  PCI Device Name:  pci0:2:0:0
 +  Base GUID:        e41d2d0300fdbd90
 +  Base MAC:         ​e41d2dfdbd90
 +  Versions: ​        ​Current ​       Available
 +     ​FW ​            ​12.26.1040 ​    N/A
 +     ​PXE ​           3.5.0803 ​      N/A
 +     ​UEFI ​          ​14.19.0014 ​    N/A
 +
 +  Status: ​          No matching image found
 +</​code>​
 +
 +Then go to the [[https://​www.mellanox.com/​page/​firmware_download|Mellanox firmware web site]] in section "​Device Type" -> "Part Number"​ -> "​PSID",​ then fetch it into your BSDRP and upgrade it:
 +
 +<​code>​
 +# mount /data
 +# cd /data
 +# fetch http://​www.mellanox.com/​downloads/​firmware/​fw-ConnectX4-rel-12_26_4012-MCX416A-CCA_Ax-UEFI-14.19.17-FlexBoot-3.5.805.bin.zip
 +# unzip fw-ConnectX4-rel-12_26_4012-MCX416A-CCA_Ax-UEFI-14.19.17-FlexBoot-3.5.805.bin.zip
 +# mstfwmanager -u -i fw-ConnectX4-rel-12_26_4012-MCX416A-CCA_Ax-UEFI-14.19.17-FlexBoot-3.5.805.bin
 +Querying Mellanox devices firmware ...
 +
 +Device #1:
 +----------
 +
 +  Device Type:      ConnectX4
 +  Part Number: ​     MCX416A-CCA_Ax
 +  Description: ​     ConnectX-4 EN network interface card; 100GbE dual-port QSFP28; PCIe3.0 x16; ROHS R6
 +  PSID:             ​MT_2150110033
 +  PCI Device Name:  pci0:2:0:0
 +  Base GUID:        e41d2d0300fdbd90
 +  Base MAC:         ​e41d2dfdbd90
 +  Versions: ​        ​Current ​       Available
 +     ​FW ​            ​12.26.1040 ​    ​12.26.4012
 +     ​PXE ​           3.5.0803 ​      ​3.5.0805
 +     ​UEFI ​          ​14.19.0014 ​    ​14.19.0017
 +
 +  Status: ​          ​Update required
 +
 +---------
 +Found 1 device(s) requiring firmware update...
 +
 +Perform FW update? [y/N]: y
 +Device #1: Updating FW ...
 +Initializing image partition -   OK
 +Writing Boot image component -   OK
 +Done
 +
 +Restart needed for updates to take effect.
 +</​code> ​
 +
 +
  
 ===== Debugging ===== ===== Debugging =====
  
 ==== Enabling crash dump ==== ==== Enabling crash dump ====
 +
 +=== Local swap dump device ===
  
 For saving and extracting a crash dump you need: For saving and extracting a crash dump you need:
Line 506: Line 581:
 </​code>​ </​code>​
  
 +=== netdump ===
 +
 +In case where you didn't have enough disk space to localy store dump, you can use netdump(4).
 +
 +On the receiving FreeBSD server (not your router):
 +<​code>​
 +pkg install netdumpd
 +service netdumpd enable
 +service netdumpd start
 +</​code>​
 +
 +Then on your router, declare source interface to use, source IP address, gateway
 +<​code>​
 +sysrc dumpdev=igb1
 +sysrc dumpon_flags="​-s 198.19.0.24 -c 192.168.1.10 -g 192.168.1.254
 +</​code>​
 +
 +and enable it:
 +
 +<​code>​
 +# service dumpon restart
 +kernel dumps on priority: device
 +0: /dev/null
 +server address: 198.19.0.24
 +client address: 192.168.1.10
 +gateway address: 192.168.1.254
 +</​code>​
 ==== Installing debug symbols ==== ==== Installing debug symbols ====
 Symbol files of kernel and binary are available in the separate DEBUG archive file. Symbol files of kernel and binary are available in the separate DEBUG archive file.
documentation/end-users_docs.1559654643.txt.gz ยท Last modified: 2019/06/04 15:24 by olivier