Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision |
| en:dpi:dpi_components:utilities:management_utilities:start [2024/03/05 10:44] – created elena.krasnobryzh | en:dpi:dpi_components:utilities:management_utilities:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 |
|---|
| {{indexmenu_n>8}} | |
| ======management utilities====== | |
| 1. ''dpdkinfo'' — receive diagnostic data from SFP modules. Parameters: | |
| * ''-h'' – help | |
| * ''module_eeprom'' – SFP module optical diagnostics information (if supported by the module). | |
| |
| 2. ''bpctl_util'' — manual bypass control. DPI controls bypass independently, but manual bypass control is performed by this utility if necessary: | |
| * ''get_bypass'' – get bypass status | |
| * ''set_bypass on'' – activate bypass | |
| * ''set_bypass off'' – deactivate bypass | |
| |
| 3. ''driverctl'' — DPDK management. Parameters: | |
| * ''list-overrides'' – check the list of cards in DPDK mode | |
| * ''unset-override 0000:04:00.0'' – exit the card from the DPDK mode\\ **The fastDPI process must first be stopped with the command ''service fastdpi stop''!** | |
| * ''-v set-override 0000:04:00.0 vfio-pci'' – return the cards back under DPDK control after working with the standard driver\\ **When switching cards to DPDK mode, be careful not to accidentally switch the server control interface to DPDK mode - communication with the server will be immediately interrupted!** | |
| |
| <note>Configuring DPDK in Hyper-V is described in detail in the appropriate [[en:dpi:dpi_components:platform:dpi_config:start#configuration_in_hyper-v|section]].</note> | |
| |
| 4. ''checklock'' — check if an address or port is blacklisted.\\ Example of a port check: | |
| <code bash>checklock 41:00.0</code> | |
| |
| 5. ''checkproto'' — check if the address or port is included in the custom protocol.\\ Example of a port check: | |
| <code bash>checkproto 41:00.0</code> | |
| |
| |
| |
