Example below shows port status on an FMADIO100Gv2 Analytics system
[Wed Apr 27 07:16:43 2022] > show interface status
[Wed Apr 27 07:16:43 2022] Port Description Status Speed Transciver RxPower TxPower Temperature FEC Vendor Vendor PN
[Wed Apr 27 07:16:43 2022] ------------------------------------------------------------------------------------------------------------------------------------
[Wed Apr 27 07:16:43 2022] man0 connected 1G
[Wed Apr 27 07:16:43 2022] man10 connected 40G 40G Base-SR4 0.7565 mW 0.0000 mW 36.21 C AVAGO AFBR-79EQDZ
[Wed Apr 27 07:16:43 2022] cap0 notconnected 100G 100G CR 0.000 mW 0.000 mA 0.000 C Ar Networks Q28-PC01
[Wed Apr 27 07:16:43 2022] cap1 connected 100G 100G CR 0.000 mW 0.000 mA 0.000 C Ar Networks Q28-PC01
[Wed Apr 27 07:16:43 2022] >
show interface ip
FW: 8336+
Shows the currently configured IP address information for the management and BMC/IPMI/Capture ports
show interface ip
Example below shows the status on an FMADIO20Gv3 system
[Tue Dec 13 04:18:36 2022] > show interface ip
[Tue Dec 13 04:18:37 2022] Port Mode IP Netmask Gateway DNS0 DNS1
[Tue Dec 13 04:18:37 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Tue Dec 13 04:18:38 2022] bmc static 192.168.187.2 255.255.255.0 192.168.187.30
[Tue Dec 13 04:18:38 2022] man0 static 192.168.187.10 255.255.255.0 192.168.187.30 1.1.1.1
[Tue Dec 13 04:18:38 2022] man1 disabled 192.168.1.2 255.255.255.0 192.168.1.1
[Tue Dec 13 04:18:38 2022] man10 static 192.168.91.50 255.255.255.0
[Tue Dec 13 04:18:38 2022] cap0
[Tue Dec 13 04:18:38 2022] cap1
[Tue Dec 13 04:18:38 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Tue Dec 13 04:18:38 2022] >
show interface counter
Shows RMON1 counter information on each capture port.
show interface counter
Example below is FMADIO20Gv3 system output
[Tue Dec 13 04:40:01 2022] > show interface counter
[Tue Dec 13 04:40:01 2022] Port Packet Byte
[Tue Dec 13 04:40:01 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:01 2022] cap0 Total : 0 0
[Tue Dec 13 04:40:01 2022] Under : 0 0
[Tue Dec 13 04:40:01 2022] 64 : 0 0
[Tue Dec 13 04:40:01 2022] 65-127 : 0 0
[Tue Dec 13 04:40:01 2022] 128-255 : 0 0
[Tue Dec 13 04:40:01 2022] 256-511 : 0 0
[Tue Dec 13 04:40:01 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:01 2022] 1024-1518 : 0 0
[Tue Dec 13 04:40:01 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:01 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:01 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:01 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:01 2022] Over : 0 0
[Tue Dec 13 04:40:01 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:01 2022] cap1 Total : 303349 125359723
[Tue Dec 13 04:40:01 2022] Under : 0 0
[Tue Dec 13 04:40:01 2022] 64 : 58765 0
[Tue Dec 13 04:40:01 2022] 65-127 : 146476 0
[Tue Dec 13 04:40:01 2022] 128-255 : 11891 0
[Tue Dec 13 04:40:01 2022] 256-511 : 8283 0
[Tue Dec 13 04:40:01 2022] 512-1023 : 15793 0
[Tue Dec 13 04:40:01 2022] 1024-1518 : 62140 0
[Tue Dec 13 04:40:01 2022] 1024-2047 : 62141 0
[Tue Dec 13 04:40:01 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:01 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:01 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:01 2022] Over : 0 0
[Tue Dec 13 04:40:01 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:01 2022] >
Example below shows FMADIO100v2 in 8x10G port output
[Tue Dec 13 04:40:57 2022] > show interface counter
[Tue Dec 13 04:40:58 2022] Port Packet Byte
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:58 2022] cap0 Total : 0 0
[Tue Dec 13 04:40:58 2022] Under : 0 0
[Tue Dec 13 04:40:58 2022] 64 : 0 0
[Tue Dec 13 04:40:58 2022] 65-127 : 0 0
[Tue Dec 13 04:40:58 2022] 128-255 : 0 0
[Tue Dec 13 04:40:58 2022] 256-511 : 0 0
[Tue Dec 13 04:40:58 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-1518 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:58 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:58 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:58 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:58 2022] Over : 0 0
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:58 2022] cap1 Total : 0 0
[Tue Dec 13 04:40:58 2022] Under : 0 0
[Tue Dec 13 04:40:58 2022] 64 : 0 0
[Tue Dec 13 04:40:58 2022] 65-127 : 0 0
[Tue Dec 13 04:40:58 2022] 128-255 : 0 0
[Tue Dec 13 04:40:58 2022] 256-511 : 0 0
[Tue Dec 13 04:40:58 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-1518 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:58 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:58 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:58 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:58 2022] Over : 0 0
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:58 2022] cap2 Total : 0 0
[Tue Dec 13 04:40:58 2022] Under : 0 0
[Tue Dec 13 04:40:58 2022] 64 : 0 0
[Tue Dec 13 04:40:58 2022] 65-127 : 0 0
[Tue Dec 13 04:40:58 2022] 128-255 : 0 0
[Tue Dec 13 04:40:58 2022] 256-511 : 0 0
[Tue Dec 13 04:40:58 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-1518 : 0 0config capture
[Tue Dec 13 04:40:58 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:58 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:58 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:58 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:58 2022] Over : 0 0
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:58 2022] cap3 Total : 0 0
[Tue Dec 13 04:40:58 2022] Under : 0 0
[Tue Dec 13 04:40:58 2022] 64 : 0 0
[Tue Dec 13 04:40:58 2022] 65-127 : 0 0
[Tue Dec 13 04:40:58 2022] 128-255 : 0 0
[Tue Dec 13 04:40:58 2022] 256-511 : 0 0
[Tue Dec 13 04:40:58 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-1518 : conf 0 0
[Tue Dec 13 04:40:58 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:58 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:58 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:58 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:58 2022] Over : 0 0
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:58 2022] cap4 Total : 0 0
[Tue Dec 13 04:40:58 2022] Under : 0 0
[Tue Dec 13 04:40:58 2022] 64 : 0 0
[Tue Dec 13 04:40:58 2022] 65-127 : 0 0
[Tue Dec 13 04:40:58 2022] 128-255 : 0 0
[Tue Dec 13 04:40:58 2022] 256-511 : 0 0
[Tue Dec 13 04:40:58 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-1518 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:58 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:58 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:58 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:58 2022] Over : 0 0
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:58 2022] cap5 Total : 0 0
[Tue Dec 13 04:40:58 2022] Under : 0 0
[Tue Dec 13 04:40:58 2022] 64 : 0 0
[Tue Dec 13 04:40:58 2022] 65-127 : 0 0
[Tue Dec 13 04:40:58 2022] 128-255 : 0 0
[Tue Dec 13 04:40:58 2022] 256-511 : 0 0
[Tue Dec 13 04:40:58 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-1518 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:58 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:58 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:58 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:58 2022] Over : 0 0
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:58 2022] cap6 Total : 0 0
[Tue Dec 13 04:40:58 2022] Under : 0 0
[Tue Dec 13 04:40:58 2022] 64 : 0 0
[Tue Dec 13 04:40:58 2022] 65-127 : 0 0
[Tue Dec 13 04:40:58 2022] 128-255 : 0 0
[Tue Dec 13 04:40:58 2022] 256-511 : 0 0
[Tue Dec 13 04:40:58 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-1518 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:58 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:58 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:58 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:58 2022] Over : 0 0
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
[Tue Dec 13 04:40:58 2022] cap7 Total : 0 0
[Tue Dec 13 04:40:58 2022] Under : 0 0
[Tue Dec 13 04:40:58 2022] 64 : 0 0
[Tue Dec 13 04:40:58 2022] 65-127 : 0 0
[Tue Dec 13 04:40:58 2022] 128-255 : 0 0
[Tue Dec 13 04:40:58 2022] 256-511 : 0 0
[Tue Dec 13 04:40:58 2022] 512-1023 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-1518 : 0 0
[Tue Dec 13 04:40:58 2022] 1024-2047 : 0 0
[Tue Dec 13 04:40:58 2022] 2048_4095 : 0 0
[Tue Dec 13 04:40:58 2022] 4096_8191 : 0 0
[Tue Dec 13 04:40:58 2022] 8192_9216 : 0 0
[Tue Dec 13 04:40:58 2022] Over : 0 0
[Tue Dec 13 04:40:58 2022] -----------------+----------------------------------------------------------
config interface shutdown
FW: 7856+ support for 100Gv2 2x100G 2x40G
This shuts down a specific capture interface as specified, usually this is cap0 or cap1 and depends on the SKU and Port configuration on which ports can be shutdown
Re-enables the specified capture interface from shutdown status. Depending on the link peer, the link peer might need to be bounced as it may be in a shutdown error state.
Example below sets the man0 management interfaces default gateway address
[Tue Dec 13 04:33:11 2022] > config interface gateway man0 192.168.187.30
[Tue Dec 13 04:33:11 2022] UPDATING: sudo /opt/fmadio/bin/setup_network.lua --nocal
.
.
<snip>
.
.
[Tue Dec 13 04:33:14 2022] set interface [man0] Gateway (192.168.187.30) -> (192.168.187.30)
[Tue Dec 13 04:33:14 2022]
[Tue Dec 13 04:33:14 2022] Port Mode IP Netmask Gateway DNS0 DNS1
[Tue Dec 13 04:33:14 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Tue Dec 13 04:33:17 2022] bmc static 192.168.187.2 255.255.255.0 192.168.187.30
[Tue Dec 13 04:33:17 2022] man0 static 192.168.187.10 255.255.255.0 192.168.187.30 1.1.1.1
[Tue Dec 13 04:33:17 2022] man1 disabled 192.168.1.2 255.255.255.0 192.168.1.1
[Tue Dec 13 04:33:17 2022] man10 static 192.168.91.50 255.255.255.0
[Tue Dec 13 04:33:17 2022] cap0
[Tue Dec 13 04:33:17 2022] cap1
[Tue Dec 13 04:33:17 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Tue Dec 13 04:33:17 2022] >
config interface dns
Sets the DNS server for the specified interface
config interface <interface> <IPv4 DNS address>
Example below sets the DNS server for man0 interface to be 1.1.1.1
config interface dns man0 1.1.1.1
[Tue Dec 13 04:35:33 2022] > config interface dns man0 1.1.1.1
[Tue Dec 13 04:35:34 2022] UPDATING: sudo /opt/fmadio/bin/setup_network.lua --nocal
.
.
<snip>
.
.
[Tue Dec 13 04:35:37 2022] set interface [man0] DNS (nil) -> (1.1.1.1)
[Tue Dec 13 04:35:37 2022]
[Tue Dec 13 04:35:37 2022] Port Mode IP Netmask Gateway DNS0 DNS1
[Tue Dec 13 04:35:37 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Tue Dec 13 04:35:40 2022] bmc static 192.168.187.2 255.255.255.0 192.168.187.30
[Tue Dec 13 04:35:40 2022] man0 static 192.168.187.10 255.255.255.0 192.168.187.30 1.1.1.1
[Tue Dec 13 04:35:40 2022] man1 disabled 192.168.1.2 255.255.255.0 192.168.1.1
[Tue Dec 13 04:35:40 2022] man10 static 192.168.91.50 255.255.255.0
[Tue Dec 13 04:35:40 2022] cap0
[Tue Dec 13 04:35:40 2022] cap1
[Tue Dec 13 04:35:40 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Tue Dec 13 04:35:40 2022] >
Configure Capture
show capture status
Shows the current capture status
Sun Jan 15 11:21:17 2023] > show capture status
[Sun Jan 15 11:21:17 2023]
[Sun Jan 15 11:21:17 2023] Current Capture Status
[Sun Jan 15 11:21:17 2023] ------------------+--------------------
[Sun Jan 15 11:21:17 2023] Capture Running | true
[Sun Jan 15 11:21:17 2023] Capture Name | asdf_20230115_1041
[Sun Jan 15 11:21:17 2023] Capture Bytes | 0
[Sun Jan 15 11:21:17 2023] Capture Packets | 0
[Sun Jan 15 11:21:17 2023] Capture Drop | 0
[Sun Jan 15 11:21:17 2023] Capture FCS Error | 0
[Sun Jan 15 11:21:17 2023] Capture Rate | 0.000000 Gbps
[Sun Jan 15 11:21:17 2023] | 0.000000 MPps
[Sun Jan 15 11:21:17 2023] Capture Start |
[Sun Jan 15 11:21:17 2023] Capture Duration |
[Sun Jan 15 11:21:17 2023] ------------------+--------------------
[Sun Jan 15 11:21:17 2023] >
show capture schedule
Shows the current capture schedule
[Sun Jan 15 11:22:07 2023] > show capture schedule
[Sun Jan 15 11:22:07 2023]
[Sun Jan 15 11:22:07 2023] Scheduled Capture Status
[Sun Jan 15 11:22:07 2023]
[Sun Jan 15 11:22:07 2023] | 24/7 | Start | Stop |Mon|Tue|Wed|Thu|Fri|Sat|Sun|
[Sun Jan 15 11:22:07 2023] -----------------------------------------+--------+----------+----------+---+---+---+----+--+---+---+
[Sun Jan 15 11:22:07 2023] wan_colo0 | false | 00:00:00 | 24:00:00 | | | | | | | |
[Sun Jan 15 11:22:07 2023] -----------------------------------------+--------+----------+----------+---+---+---+----+--+---+---+
[Sun Jan 15 11:22:07 2023] >
show capture list
Displays list of all captures on the system
[Sun Jan 15 11:23:21 2023] > show capture list
[Sun Jan 15 11:23:21 2023] Showing captures
[Sun Jan 15 11:23:21 2023] [wan_colo0_20221230_0000] 1310720 B (Wed . 18:04:08 . 28-12-2022)
[Sun Jan 15 11:23:21 2023] [wan_colo0_20221228_0000] 29613621248 B (Wed . 18:03:58 . 28-12-2022)
[Sun Jan 15 11:23:21 2023] [wan_colo0_20221227_0000] 3442999296 B (Tue . 23:59:35 . 27-12-2022)
[Sun Jan 15 11:23:21 2023] [wan_colo0_20221226_0000] 16513236992 B (Mon . 23:59:38 . 26-12-2022)
[Sun Jan 15 11:23:21 2023] [wan_colo0_20221225_0000] 1869873152 B (Sun . 23:59:42 . 25-12-2022)
[Sun Jan 15 11:23:21 2023] [wan_colo0_20221224_0000] 6031671296 B (Sat . 23:59:39 . 24-12-2022)
[Sun Jan 15 11:23:21 2023] [wan_colo0_20221223_0000] 33109311488 B (Fri . 23:59:36 . 23-12-2022)
[Sun Jan 15 11:23:21 2023] >
show capture roll
FW: 8367+
Shows the current capture roll setting
[Sun Jan 15 11:25:18 2023] > show capture roll
[Sun Jan 15 11:25:18 2023] Capture Roll Setting:
[Sun Jan 15 11:25:18 2023] Roll every 1.00 Hour
[Sun Jan 15 11:25:18 2023] >
show capture flush
FW: 8367+
Shows the current capture flushing behaviour
[Sun Jan 15 11:25:55 2023] > show capture flush
[Sun Jan 15 11:25:56 2023] Capture Flush Setting:
[Sun Jan 15 11:25:56 2023] Periodic Flush: 10 Sec
[Sun Jan 15 11:25:56 2023] >
config capture start <name>
Starts a capture with the specified name
[Sat Jan 21 01:39:12 2023] > config capture start test-capture
[Sat Jan 21 01:39:12 2023]
[Sat Jan 21 01:39:12 2023] Starting Quick Capture [test-capture]
[Sat Jan 21 01:39:12 2023] OK: [Sat Jan 21 01:39:12 2023] successfully started capture [test-capture]
[Sat Jan 21 01:39:12 2023] >
Use config capture status to verify the current state
config capture stop
Stops the currently active capture
NOTE: This will only stop captures manually started, for scheduled captures please disable the schedule entry to stop the capture
[Sat Jan 21 01:40:33 2023] > config capture stop
[Sat Jan 21 01:40:33 2023]
[Sat Jan 21 01:40:33 2023] Stopping Capture
[Sat Jan 21 01:40:33 2023] OK: [Sat Jan 21 01:40:33 2023] successfully stopped capture [test-capture]
[Sat Jan 21 01:40:33 2023] >
Use config capture status to verify the current state
config capture flush
FW: 8367+
Sets the capture flushing behavior.
Default setting is flush 1sec after capture is idle
Flush always every 1 second. NOTE: 1sec is very aggressive mode and will consume additional storage. However it does provide low latency when watching low bandwidth captures.
// Some code
[Sun Jan 15 11:27:34 2023] > config capture flush period 1
[Sun Jan 15 11:27:35 2023] Setting Flush Mode[period] Timeout 1 sec
[Sun Jan 15 11:27:35 2023]
[Sun Jan 15 11:27:35 2023] **** requires restarting of capture to take effect ****
[Sun Jan 15 11:27:35 2023]
Flush when capture is idle for >= 1sec
[Sun Jan 15 11:27:44 2023] > config capture flush idle 10
[Sun Jan 15 11:27:44 2023] Setting Flush Mode[idle] Timeout 10 sec
[Sun Jan 15 11:27:44 2023]
[Sun Jan 15 11:27:44 2023] **** requires restarting of capture to take effect ****
[Sun Jan 15 11:27:44 2023]
[Sun Jan 15 11:27:44 2023] >
config capture roll
FW: 8367+
Configures the capture rolling behavior. Default (0) is roll at midnight.
Example configures capture to roll every 1 hour.
[Sun Jan 15 11:31:46 2023] > config capture roll 1
[Sun Jan 15 11:31:47 2023] Setting Capture Roll Every 1 Hour
[Sun Jan 15 11:31:47 2023]
[Sun Jan 15 11:31:47 2023] **** requires restarting of capture to take effect ****
[Sun Jan 15 11:31:47 2023]
[Sun Jan 15 11:31:47 2023] >
Configure PCAP Download
show pcap timestamp
Shows the current PCAP timestamp mode. e.g. from the FMADIO FPGA or extract timing information from a packet broker
Example below shows the PCAP timestamp uses the Arista 7130 (Metamako) footer timestamp
show pcap timestamp
[Mon Jun 12 16:48:09 2023] > show pcap timestamp
[Mon Jun 12 16:48:10 2023] TimeStamp Mode: arista7130 : (Arista 7130 (Metamako))
[Mon Jun 12 16:48:10 2023]
[Mon Jun 12 16:48:10 2023] >
config pcap timestamp <tsmode>
Configures the default PCAP timestamp mode when downloading PCAP data. this value can be overidden by URI option TSMode.
[Mon Jun 12 16:50:30 2023] > config pcap timestamp
[Mon Jun 12 16:50:31 2023] Example Usage:
[Mon Jun 12 16:50:31 2023] > config pcap timestamp <mode> : configure default PCAP timestamp mode
[Mon Jun 12 16:50:31 2023] arista7280_mac48 : Arista 7280 (Source MAC 48bit)
[Mon Jun 12 16:50:31 2023] arista7130 : Arista 7130 (Metamako)
[Mon Jun 12 16:50:31 2023] arista7280_eth64 : Arista 7280 (Ethernet 64bit)
[Mon Jun 12 16:50:31 2023] arista7150_overwrite : Arista 7150 (Overwrite FCS)
[Mon Jun 12 16:50:31 2023] erspanv3 : CISCO ERSPANv3 Timestamp
[Mon Jun 12 16:50:31 2023] arista7150_insert : Arista 7150 (Insert FCS)
[Mon Jun 12 16:50:31 2023] nic : Timestamp is the FMADIO FPGAs internal timestamp
[Mon Jun 12 16:50:31 2023] cisco3550 : CISCO 3550 Timestamp (Exablaze)
[Mon Jun 12 16:50:31 2023]
[Mon Jun 12 16:50:31 2023] ERROR: Unknown Command [config pcap timestamp]
[Mon Jun 12 16:50:31 2023] >
Example to set the default behavior to use Arista 7130 footer. It takes 60sec to restart the processes after the setting.
config pcap timestamp arista7130
[Mon Jun 12 16:54:04 2023] > config pcap timestamp arista7130
[Mon Jun 12 16:54:04 2023] TimeStamp Mode set to [arista7130] : (Arista 7130 (Metamako))
[Mon Jun 12 16:54:04 2023]
[Mon Jun 12 16:54:04 2023] Restarting Processes
[Mon Jun 12 16:54:14 2023] Wait 60sec for processes to restart
[Mon Jun 12 16:54:14 2023] 0/60
[Mon Jun 12 16:54:15 2023] 1/60
[Mon Jun 12 16:54:16 2023] 2/60
[Mon Jun 12 16:54:17 2023] 3/60
[Mon Jun 12 16:54:18 2023] 4/60
.
.
[Mon Jun 12 16:55:07 2023] 53/60
[Mon Jun 12 16:55:08 2023] 54/60
[Mon Jun 12 16:55:09 2023] 55/60
[Mon Jun 12 16:55:10 2023] 56/60
[Mon Jun 12 16:55:11 2023] 57/60
[Mon Jun 12 16:55:12 2023] 58/60
[Mon Jun 12 16:55:13 2023] 59/60
[Mon Jun 12 16:55:14 2023] 60/60
[Mon Jun 12 16:55:15 2023] done
[Mon Jun 12 16:55:15 2023] >
LXC Container Management
Following provides commands for configuration and managing LXC containers on the system
show lxc status
Shows the current LXC container status of the system
show lxc status
Example shows 2 containers "suricata" and "centos7"
Suricata is enabled to start at boot time.
[Sat Jun 24 15:39:35 2023] > show lxc status
[Sat Jun 24 15:39:35 2023]
[Sat Jun 24 15:39:35 2023] Name OnBoot Install State Desc
[Sat Jun 24 15:39:35 2023] ---------------------------------------------------------------------------------------------------------------------------------
[Sat Jun 24 15:39:35 2023] suricata true yes STOPPED suricata ids service
[Sat Jun 24 15:39:35 2023] centos7 false yes STOPPED
[Sat Jun 24 15:39:35 2023] ---------------------------------------------------------------------------------------------------------------------------------
[Sat Jun 24 15:39:35 2023] >
config lxc add <lxc name>
Adds an already installed container to the configuration file
config lxc add <lxc name>
In the example below adding an already installed container named "ubuntu20" to the system
[Sat Jun 24 15:45:56 2023] > config lxc add ubuntu20
[Sat Jun 24 15:45:57 2023] Added container [ubuntu20] to the configuration
[Sat Jun 24 15:45:57 2023] >
config lxc del <lxc name>
Removes the specified container from the configuration
NOTE it does not delete the container on disk. Only removes it from the configuration files
config lxc del <lxc name>
Example deletes the container "ubuntu20" from the configuration files
[Sat Jun 24 15:48:24 2023] > config lxc del ubuntu20
[Sat Jun 24 15:48:25 2023] Removed container [ubuntu20] to the configuration
[Sat Jun 24 15:48:25 2023] >
config lxc desc <lxc name> "<description>"
Adds a human description to the lxc to provide context
config lxc desc <lxc name> "<description>"
Example set a human readable description for the container "ubuntu20" this is visibile when using the show lxc command
[Sat Jun 24 15:51:01 2023] > config lxc desc ubuntu20 "general purpose ubuntu20 container"
[Sat Jun 24 15:51:01 2023] Set container [ubuntu20] to description to [general purpose ubuntu20 container]
[Sat Jun 24 15:51:02 2023] >
config lxc boot <lxc name>
Sets the specified container to boot on startup
config lxc boot <lxc name>
Example set the "ubuntu20" container to boot on system startup
[Sat Jun 24 15:53:06 2023] > config lxc boot ubuntu20
[Sat Jun 24 15:53:07 2023] Set container [ubuntu20] to boot on system start
[Sat Jun 24 15:54:11 2023] >
config lxc no-boot <lxc name>
Sets the specified LXC container to not boot at startup
config lxc no-boot <lxc name>
Example sets the LXC container "ubuntu20" to not boot on startup
[Sat Jun 24 15:57:50 2023] > config lxc no-boot ubuntu20
[Sat Jun 24 15:57:50 2023] Set container [ubuntu20] to NOT boot on system start
[Sat Jun 24 15:57:50 2023] >
config lxc start <lxc name>
Starts the specified container named <lxc name> if the container starts successfully system will return back to the prompt
config lxc start <lxc name>
Example starts the fshark2 container on the system
[Sat Jun 24 16:03:05 2023] > config lxc start fshark2
[Sat Jun 24 16:03:05 2023] sudo lxc-start -n fshark2 --logfile /tmp/lxc_fshark2_1687593785847943936
[Sat Jun 24 16:03:07 2023]
[Sat Jun 24 16:03:07 2023] use the following on a shell to attach to the conatiners console
[Sat Jun 24 16:03:07 2023] sudo lxc-attach -n fshark2
[Sat Jun 24 16:03:07 2023]
[Sat Jun 24 16:03:07 2023] >
When a container fails to start the output will look similar to below.
[Sat Jun 24 16:04:24 2023] > config lxc start ubuntu20
[Sat Jun 24 16:04:24 2023] sudo lxc-start -n ubuntu20 --logfile /tmp/lxc_ubuntu20_1687593864919910912
[Sat Jun 24 16:04:24 2023] lxc: lxc-start: ubuntu20: tools/lxc_start.c: main: 322 Executing '/sbin/init' with no configuration file may crash the host
[Sat Jun 24 16:04:24 2023] lxc: lxc-start ubuntu20 20230624080424.927 ERROR lxc_start_ui - tools/lxc_start.c:main:322 - Executing '/sbin/init' with no configuration file may crash the host
[Sat Jun 24 16:04:24 2023]
[Sat Jun 24 16:04:24 2023] >
config lxc stop <lxc name>
Stops the specified container from running
config lxc stop <lxc name>
Example stops the fshark2 container running
[Sat Jun 24 16:06:49 2023] > config lxc stop fshark2
[Sat Jun 24 16:06:50 2023] sudo lxc-stop -n fshark2 --logfile /tmp/lxc_fshark2_1687594010169326080
[Sat Jun 24 16:06:50 2023]
config lxc list
TBD lists all available containers in the public repo
contact support@fmad.io for more info
config lxc install
TBD installs the specified container from the public repo
contact support@fmad.io for more info
config lxc uninstall
TBD removes the specified container from the configuration and disk
contact support@fmad.io for more info
Automatic Push PCAP
Configure and monitor the automatic push generation of PCAPs to storage locations.
show push pcap status
FW: 7963+
Shows the currently configured automatic push pcaps
[Thu Jun 9 08:30:42 2022] > show push pcap status
[Thu Jun 9 08:30:42 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Thu Jun 9 08:30:42 2022] FollowStart : true
[Thu Jun 9 08:30:42 2022] Decap : true
[Thu Jun 9 08:30:42 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Thu Jun 9 08:30:42 2022] [tcp] #1
[Thu Jun 9 08:30:42 2022] Mode : File
[Thu Jun 9 08:30:42 2022] Path : /mnt/remote0/push/ttest/
[Thu Jun 9 08:30:42 2022] Split : --split-time 3600e9
[Thu Jun 9 08:30:42 2022] FileName : --filename-tstr-HHMMSS
[Thu Jun 9 08:30:42 2022] FilterBPF : host 192.168.1.1
[Thu Jun 9 08:30:42 2022] FilterFrame :
[Thu Jun 9 08:30:42 2022] ---------------------------------------------------------------------------------------------------------------------------------
[Thu Jun 9 08:30:42 2022] >
config push pcap add <push target>
FW: 7963+
Creates a new push pcap target called <push target>
NOTE: all target names should be unique
[Thu Jun 9 08:32:13 2022] > config push pcap add udp-all
[Thu Jun 9 08:32:13 2022] Add Push PCAP target [udp-all]
[Thu Jun 9 08:32:13 2022] >
config push pcap del <push target>
Deletes the current push pcap entry name <push target>
[Thu Jun 9 08:33:17 2022] > config push pcap del udp-all
[Thu Jun 9 08:33:18 2022] deleting: [udp-all] row 2
[Thu Jun 9 08:33:18 2022] >
config push pcap name <push target> <new name>
Renames the specified <push target> entry with an updated one <new name>
[Thu Jun 9 08:36:21 2022] > config push pcap name udp-all udp-port-1900
[Thu Jun 9 08:36:23 2022] Rename [udp-all] -> [udp-port-1900]
[Thu Jun 9 08:36:23 2022] >
Updates the push write path to the specified <new write path>. Typically this is the NFS remote path or rclone write path.
[Thu Jun 9 08:41:41 2022] > config push pcap path udp-port-1900 /mnt/remote0/push/
[Thu Jun 9 08:41:44 2022] Set Path [] -> [/mnt/remote0/push/]
[Thu Jun 9 08:41:44 2022] >
config push pcap split-time <push target> <value>
Configure PCAPs to be split by the specified time value. By default <value> is scientific notation in nanoseconds. In addition s (seconds) m (minutes) h (hours) suffix can be used also
Description
1e9
1 second in scientific notation
60s
60 seconds
1m
1 minute
1h
1 hour
Example configure to split every 1 minute
[Thu Jun 9 08:48:05 2022] > config push pcap split-time udp-port-1900 1m
[Thu Jun 9 08:48:06 2022] Set Split to [--split-time 3600e9] -> [--split-time 60000000000]
[Thu Jun 9 08:48:06 2022] >
config push pcap split-size <push target> <value>
Configure PCAPs to be split by total byte size <value>
Description
1e9
1 Gigabyte specified in scientific notation
100M
100 Megbyte
5G
5 Gigabyte
Example below shows splitting on 1GB boundaries
[Thu Jun 9 08:53:32 2022] > config push pcap split-size udp-port-1900 1G
[Thu Jun 9 08:53:33 2022] Set Split to [--split-time 60000000000] -> [--split-byte 1000000000]
[Thu Jun 9 08:53:33 2022] >
config push pcap filename <push target> <value>
Specifies the filename format for each individual split PCAP
Value
Example
Description
epoch-sec
_1654610221.pcap
Second Epoch
epoch-sec-startend
_1654610221-1654620221.pcap
Epoch start and End
epoch-msec
_1654610221012.pcap
Epoch in msec
epoch-usec
_1654610221012345.pcap
Epoch is micro sec
epoch-nsec
_1654610221012345678.pcap
Epoch in Nano sec
HHMM
_20200101_1201.pcap
Hour Min
HHMMSS
_20200101_120159.pcap
Hour Min Sec
HHMMSS_TZ
2020-01-01_12:01:59+09:00.pcap
House Min Sec + Timezone
HHMMSS_NS
_20200101_120159.012345678.pcap
House Min Sec Nanos
Example uses a simple Hour Min Sec format
[Thu Jun 9 09:02:52 2022] > config push pcap filename udp-port-1900 HHMMSS
[Thu Jun 9 09:02:53 2022] Set Filename to [--filename-tstr-HHMMSS_TZ] -> [--filename-tstr-HHMMSS]
[Thu Jun 9 09:02:53 2022] >
NOTE: the BPF filter must be enclosed in double quotes
Example sets for udp and port 1900
[Thu Jun 9 09:07:05 2022] > config push pcap filter-bpf udp-port-1900 "udp and port 1900"
[Thu Jun 9 09:07:05 2022] Set FilterBPF [] -> [udp and port 1900]
[Thu Jun 9 09:07:05 2022] >
config push pcap restart
Shutsdown the current push procesess and restarts them
config push pcap restart
Example output
[Thu Sep 28 12:18:53 2023] > config push pcap restart
Killing 78246 {push_pcap.lua}
Killing 78403 /opt/fmadio/bin/stream_cat
Killing 78406 /opt/fmadio/bin/pcap_split
Killing 78412 /opt/fmadio/bin/pcap_split
wait for respawn 0/120
wait for respawn 1/120
wait for respawn 2/120
wait for respawn 3/120
wait for respawn 4/120
wait for respawn 5/120
wait for respawn 6/120
wait for respawn 7/120
wait for respawn 8/120
wait for respawn 9/120
wait for respawn 10/120
process respawned
[Thu Sep 28 12:19:05 2023] >
Automatic Push to LXC (Container)
The system can push automatically into a lxc_ring enabling a container to consume the data. These functions are to add/delete/modify these push functions.
NOTE this requires the push_lxc analytics script to be running
show push lxc
Shows the current push lxc targets configured on the system
show push lxc
Example shown below, indicates a single suricata ring is enabled with a BPF filter to remove all traffic from subnet 192.168.100.0/24
[Sat Jun 24 14:22:12 2023] > show push lxc
[Sat Jun 24 14:22:12 2023]
[Sat Jun 24 14:22:12 2023] Ring name : Enable : From : Description : Filter Frame : Filter BPF
[Sat Jun 24 14:22:12 2023] ------------------------------------------------+--------+------------+---------------------------------+----------------------+-----------------------------------------------------------------
[Sat Jun 24 14:22:12 2023] /opt/fmadio/queue/lxc_ring_suricata : true : start : suricata ids feed : : not net 192.168.100.0/24
[Sat Jun 24 14:22:12 2023] ------------------------------------------------+--------+------------+---------------------------------+----------------------+-----------------------------------------------------------------
[Sat Jun 24 14:22:12 2023] >
config push lxc add <ring name>
This adds a new LXC push to the ring named <ring name>.
By default the push is disabled when created.
config push lxc add <ring name>
Example below shows adding a push to the ring named "general"
[Sat Jun 24 14:25:26 2023] > config push lxc add general
[Sat Jun 24 14:25:26 2023] New Push LXC target [/opt/fmadio/queue/lxc_ring_general]
[Sat Jun 24 14:25:26 2023] >
NOTE this does not create the ring, it only creates the push to the specified ring
config push lxc del <ring name>
Removes the specified LXC push target
config push lxc del <ring name>
Example removes the push lxc target named "general"
[Sat Jun 24 14:32:31 2023] > config push lxc del general
[Sat Jun 24 14:32:32 2023] Delete Push LXC target [/opt/fmadio/queue/lxc_ring_general]
[Sat Jun 24 14:32:32 2023] >
config push lxc enable <ring name>
Enables the specified lxc ring push target. By default when adding a new target the state is disabled.
config push lxc enable <ring name>
Example enables the push lxc ring target named "general"
[Sat Jun 24 14:36:29 2023] > config push lxc enable general
[Sat Jun 24 14:36:29 2023] Set LXC target [/opt/fmadio/queue/lxc_ring_general] Enable
[Sat Jun 24 14:36:29 2023] >
config push lxc disable <ring name>
Disables the specified lxc push <ring name>
config push lxc disable <ring name>
Example disables the lxc ring named "general"
[Sat Jun 24 14:39:44 2023] > config push lxc disable general
[Sat Jun 24 14:39:45 2023] Set LXC target [/opt/fmadio/queue/lxc_ring_general] to Disable
[Sat Jun 24 14:39:45 2023] >
Example add a Frame filter of capture port 0 only to the ring named "general"
[Sat Jun 24 14:46:56 2023] > config push lxc filter-frame general "capture.port=0"
[Sat Jun 24 14:46:56 2023] Set LXC target [/opt/fmadio/queue/lxc_ring_general] filter frame to (capture.port=0)
[Sat Jun 24 14:46:56 2023] >
config push lxc from-now <ring name>
Sets the push to start from the current capture position into the lxc ring.
This is the default behaviour
config push lxc from-now <ring name>
Example sets the ring "general" to push data into the ring from now.
[Sat Jun 24 14:50:03 2023] > config push lxc from-now general
[Sat Jun 24 14:50:04 2023] Set LXC target [/opt/fmadio/queue/lxc_ring_general] fetch from current capture position
[Sat Jun 24 14:50:04 2023] >
config push lxc from-start <ring name>
Sets the push to start from the beginning of the capture.
config push lxc from-start <ring name>
Example sets the ring "general" to start from the begnining of the capture
[Sat Jun 24 14:51:48 2023] > config push lxc from-start general
[Sat Jun 24 14:51:48 2023] Set LXC target [/opt/fmadio/queue/lxc_ring_general] fetch from start of capture
[Sat Jun 24 14:51:48 2023] >
config push lxc restart
This shutsdown and then restarts the push lxc processes.
config push lxc restart
Example output
[Thu Sep 28 12:14:27 2023] > config push lxc restart
Killing 78263 {push_lxc.lua}
Killing 78376 /opt/fmadio/bin/stream_cat
wait for respawn 0/120
wait for respawn 1/120
wait for respawn 2/120
wait for respawn 3/120
wait for respawn 4/120
wait for respawn 5/120
wait for respawn 6/120
.
.
wait for respawn 29/120
wait for respawn 30/120
wait for respawn 31/120
wait for respawn 32/120
wait for respawn 33/120
wait for respawn 34/120
wait for respawn 35/120
wait for respawn 36/120
process respawned
[Thu Sep 28 12:15:05 2023] >
Ring management
Various functions for monitoring the ring status both push pcap and push lxc
show ring status
Shows all rings status information
show ring status
Example, this can be helpful for monitoring data is being produced and consumed correctly.
Various functions for configuration and monitoring time
show timezone
Shows the current timezone the system is configured
show timezone
Example showing the current timezone
[Sat Jun 24 15:25:29 2023] > show timezone
[Sat Jun 24 15:25:30 2023] Timezone: Asia/Singapore
[Sat Jun 24 15:25:30 2023] UTC +08:00 (SGT)
[Sat Jun 24 15:25:32 2023] >
config timezone "<city>"
Configures the timezone by searching the timezone list for the location named "<city>"
System uses the first found match
For cities with spaces in the name, ensure to use double quotes around the city name
config timezone "<city>"
Example set the timezone to New York
[Sat Jun 24 15:32:00 2023] > config timezone "New York"
[Sat Jun 24 15:32:01 2023] setting timezone to [/usr/share/zoneinfo/America/New_York]
[Sat Jun 24 15:32:01 2023] UTC -04:00 M (EDT)
[Sat Jun 24 15:32:01 2023] *** System requires a reboot to take effect ****
[Sat Jun 24 15:32:01 2023] >
NOTE change only takes effect on next reboot
User Management
FW: 8336+
FMADIO Web GUI supports multiple users with 2 levels of access
Permission
Description
full
Provides full admin level access to all functions
user
User level only, no ability to modify config and start/stop captures
Using fmadiocli to setup and configure is shown below
show userlist
This shows the currently configured list of users on the system
show userlist
Example output, it shows 2 users fmadio (full access), bob (user access)
[Tue Dec 13 04:05:54 2022] > show userlist
[Tue Dec 13 04:05:55 2022] Showing User List
[Tue Dec 13 04:05:55 2022]
[Tue Dec 13 04:05:55 2022] UserList Enable: true
[Tue Dec 13 04:05:55 2022]
[Tue Dec 13 04:05:55 2022] --------------------------------------------------
[Tue Dec 13 04:05:55 2022]
[Tue Dec 13 04:05:55 2022] UserName : fmadio
[Tue Dec 13 04:05:55 2022] Permission : full
[Tue Dec 13 04:05:55 2022] SecBPF :
[Tue Dec 13 04:05:55 2022]
[Tue Dec 13 04:05:55 2022] UserName : bob
[Tue Dec 13 04:05:55 2022] Permission : user
[Tue Dec 13 04:05:55 2022] SecBPF :
[Tue Dec 13 04:05:55 2022]
[Tue Dec 13 04:05:55 2022] --------------------------------------------------
[Tue Dec 13 04:05:55 2022] >
config userlist add
Adds a new user with default permissions and no password
config userlist add <username>
Example adds the username "bob" to the system
[Tue Dec 13 04:08:14 2022] > config userlist add bob
[Tue Dec 13 04:08:17 2022] Created new User [bob]
[Tue Dec 13 04:08:17 2022] >
config userlist del
Deletes the specified username
config userlist del <username>
Example below deletes the username "bob"
[Tue Dec 13 04:09:15 2022] > config userlist del bob
[Tue Dec 13 04:09:16 2022] deleted username [bob]
[Tue Dec 13 04:09:16 2022] >
config userlist password
Sets the WEB user password. This has no effect on SSH access to the system
config userlist password <username>
Example below sets the web password for user "bob"
[Tue Dec 13 04:12:19 2022] > config userlist password bob
[Tue Dec 13 04:12:20 2022] New Password : ***********
[Tue Dec 13 04:12:22 2022] Re-enter Password: ***********
[Tue Dec 13 04:12:24 2022] web password for username [bob] set
[Tue Dec 13 04:12:24 2022] >
config userlist permission
Sets the userlevel permission for the specified username
config userlist permission <username> <level>
Level types are 2
full - provides full unrestricted GUI access
user - provides download and analysis only access (no configuration or capture state change)
Example below shows setting the username "bob" to be a "user" level (e.g. can not change system configuration or capture states)
[Tue Dec 13 04:13:55 2022] > config userlist permission bob user
[Tue Dec 13 04:13:55 2022] modified username [bob] to permission level [user]
[Tue Dec 13 04:13:55 2022] >
Example below shows setting username "bob" to be a full access user (e.g. can change any configuration using the GUI)
[Tue Dec 13 04:14:42 2022] > config userlist permission bob full
[Tue Dec 13 04:14:42 2022] modified username [bob] to permission level [full]
[Tue Dec 13 04:14:42 2022] >
Security Management
Various commands to set and modify the security settings of the system
show security
Shows the current security settings
show security
[Wed May 17 13:56:44 2023] > show security
[Wed May 17 13:56:44 2023] Authentication: PAM-LDAP
[Wed May 17 13:56:44 2023] HTTP Access : enabled
[Wed May 17 13:56:44 2023] Timeout SSH : 0.166667min (idle)
[Wed May 17 13:56:44 2023] Timeout WWW : 1.000000min (session
[Wed May 17 13:56:44 2023] >
config security auth
This sets the authentication method of the system. Number of options as follows
BASIC - this is basic authencation, low security level
OAUTH - OAUTH 2.0 includding Active Directory, Google, Ping Identity
RADIUS - Use Radius based authentication
PAM-LDAP - Use the linux PAM system with an LDAP authentication mode
Example to set PAM-LDAP as follows
config security auth pam-ldap
Output as follows
[Fri Mar 3 14:24:34 2023] > config security auth pam-ldap
[Fri Mar 3 14:24:35 2023] Authentication [BASIC] -> [PAM-LDAP]
[Fri Mar 3 14:24:35 2023] rebooting the system may be required
[Fri Mar 3 14:24:35 2023] >
For some authentication methods it requires a system reboot. In this case a reboot is required as the system needs to start LDAP client daemons.
config security http
This enables/disables HTTP as a mode of access to the device. HTTP is plain clear text transport protocol, meaning all private data such as username and password are sent in the clear.
For private and secure networks this is ok(ish) for most situations HTTP should be disabled, allowing only HTTPS as the mode of access.
To disable HTTP access (HTTPS only)
config security http false
Example output
[Fri Mar 3 14:27:34 2023] > config security http false
[Fri Mar 3 14:27:34 2023] HTTP Access [enable] -> [false]
[Fri Mar 3 14:27:35 2023] please wait 60sec for web access to restart
[Fri Mar 3 14:27:35 2023] >
config security timeoutSSH
This sets the SSH idle timeout timeout value. Use "show security" to validate the value is correct.
Time units supported are
s - second
m - minute
h - hour
disable - disable timeout
An example of setting a 30 sec idle timeout as follows
config security timeoutSSH 30s
With the following output
[Wed May 17 13:57:23 2023] > config security timeoutSSH 30s
[Wed May 17 13:57:24 2023] SSH Timeout [10000000000] -> [30000000000]
[Wed May 17 13:57:24 2023] please reboot for new setting to take effect
[Wed May 17 13:57:24 2023] >
NOTE: the system requires a reboot for the changes to take effect.
config security timeoutWWW
This sets the WWW session timeout value. This is the maximum session duration. Once the session duration is reached the web interface will require a re-login.
Time units supported are
// Some code
s - second
m - minute
h - hour
disable - disable timeout
An example setting a 1 hour maximum session timeout
config security timeoutWWW 1h
Example output
[Wed May 17 14:00:35 2023] > config security timeoutWWW 1h
[Wed May 17 14:00:35 2023] WWW Timeout [60000000000] -> [3600000000000]
[Wed May 17 14:00:35 2023] please reboot for new setting to take effect
[Wed May 17 14:00:35 2023] >
NOTE: a the system requires a reboot for the changes to take effect.
Disk Management
Configuration and status information for disks and disk encryption
Stored disk password
NOTE: the default password is stored in
/opt/fmadio/etc/disk-password
This may or maynot include whitespace charaters such as 0xa. Which may cause confusion about the password entered vs the saves on disk password.
When editing this file in VIM we recommend setting, to avoid any additional whitespace charaters in the pawwrod
:set binary noendofline
show disk status
Shows the current disk status information
show disk status
Example below shows a fully setup 100Gp3 system with PSID and Encryption enabled
[Sat Jun 24 17:48:45 2023] > show disk status
[Sat Jun 24 17:48:45 2023] SSD Cache
[Sat Jun 24 17:48:46 2023] Disk : Serial : Size : Temp : Used : Error : Total Write : Total Read : SED : PSID : SED Enb : SED Lock :
[Sat Jun 24 17:48:46 2023] ------+----------------------+----------+--------+-------+-------+-------------+-------------+-----+------+---------+----------+
[Sat Jun 24 17:48:46 2023] os0 : 50026B7685513F33 : 0.00 TB : 0 C : 0 % : 0 : 0.00 TB : 0.00 TB : N : N : N : N :
[Sat Jun 24 17:48:46 2023] par0 : 22443E9D2087 : 0.00 TB : 30 C : 0 % : 0 : 0.00 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd0 : 22443E9D204F : 0.15 TB : 29 C : 0 % : 0 : 0.01 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd1 : 22223AD5BFC3 : 0.15 TB : 32 C : 0 % : 0 : 0.02 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd2 : 22443E9D3AFF : 0.15 TB : 28 C : 0 % : 0 : 0.01 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd3 : 22443E9DC543 : 0.15 TB : 30 C : 0 % : 0 : 0.01 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd4 : 22443E9D2076 : 0.15 TB : 29 C : 0 % : 0 : 0.01 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd5 : 22443E9D3B41 : 0.15 TB : 29 C : 0 % : 0 : 0.01 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd6 : 22443E9D3B65 : 0.15 TB : 30 C : 0 % : 0 : 0.01 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd7 : 22443E9D20A4 : 0.15 TB : 28 C : 0 % : 0 : 0.01 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ssd8 : 22443E9DC54E : 0.15 TB : 31 C : 0 % : 0 : 0.01 TB : 0.00 TB : Y : Y : Y : Y :
[Sat Jun 24 17:48:46 2023] ------+----------------------+----------+--------+-------+-------+-------------+-------------+-----+------+---------+----------+
[Sat Jun 24 17:48:46 2023] >
config disk sanitize
Using TCG OPAL2 sedutils the system will factory reset the device using the PSID values, initialize the drives for encryption and set a default password.
When complete the drives data is encrypted with a default password to access a randomly generated AES256 encryption key.
When complete the drives are in the unlocked state. To enable locking use the config disk lock comand
config disk sanitize
Example shows a partial log of the 100G systems sanitize operation. Entire operation takes about 60 seconds
[Sat Jun 24 17:53:32 2023] > config disk sanitize
[Sat Jun 24 17:53:32 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:53:32 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme9n1
[Sat Jun 24 17:53:32 2023] [par0] /dev/nvme9n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:53:32 2023]
[Sat Jun 24 17:53:32 2023] [par0] factory reset 22443E9D2087
[Sat Jun 24 17:53:32 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --PSIDrevert 11EDDF5767CA7C0BBC0FD8643803B657 /dev/nvme9n1
[Sat Jun 24 17:53:35 2023] [par0] revertTper completed successfully
[Sat Jun 24 17:53:35 2023]
[Sat Jun 24 17:53:35 2023] [par0] set default password
[Sat Jun 24 17:53:35 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --initialSetup ***** /dev/nvme9n1
[Sat Jun 24 17:53:35 2023] [par0] SID password changed
[Sat Jun 24 17:53:36 2023] [par0] takeOwnership complete
[Sat Jun 24 17:53:37 2023] [par0] Locking SP Activate Complete
[Sat Jun 24 17:53:38 2023] [par0] LockingRange0 disabled
[Sat Jun 24 17:53:38 2023] [par0] LockingRange0 set to RW
[Sat Jun 24 17:53:39 2023] [par0] MBRDone set on
[Sat Jun 24 17:53:40 2023] [par0] MBREnable set on
[Sat Jun 24 17:53:40 2023] [par0] Initial setup of TPer complete on /dev/nvme9n1
[Sat Jun 24 17:53:40 2023]
[Sat Jun 24 17:53:40 2023] [par0] disable MBR
[Sat Jun 24 17:53:40 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --setMBREnable off ***** /dev/nvme9n1
[Sat Jun 24 17:53:40 2023] [par0] MBRDone set on
[Sat Jun 24 17:53:41 2023] [par0] MBREnable set off
[Sat Jun 24 17:53:41 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:53:41 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme10n1
[Sat Jun 24 17:53:41 2023] [ssd0] /dev/nvme10n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:53:41 2023]
[Sat Jun 24 17:53:41 2023] [ssd0] factory reset 22443E9D204F
[Sat Jun 24 17:53:41 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --PSIDrevert 7306CD8CE0BE5F694793FBD8409E7CFE /dev/nvme10n1
[Sat Jun 24 17:53:43 2023] [ssd0] revertTper completed successfully
[Sat Jun 24 17:53:43 2023]
[Sat Jun 24 17:53:43 2023] [ssd0] set default password
[Sat Jun 24 17:53:43 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --initialSetup ***** /dev/nvme10n1
[Sat Jun 24 17:53:44 2023] [ssd0] SID password changed
[Sat Jun 24 17:53:44 2023] [ssd0] takeOwnership complete
[Sat Jun 24 17:53:46 2023] [ssd0] Locking SP Activate Complete
[Sat Jun 24 17:53:47 2023] [ssd0] LockingRange0 disabled
[Sat Jun 24 17:53:47 2023] [ssd0] LockingRange0 set to RW
[Sat Jun 24 17:53:48 2023] [ssd0] MBRDone set on
[Sat Jun 24 17:53:49 2023] [ssd0] MBREnable set on
[Sat Jun 24 17:53:49 2023] [ssd0] Initial setup of TPer complete on /dev/nvme10n1
[Sat Jun 24 17:53:49 2023]
[Sat Jun 24 17:53:49 2023] [ssd0] disable MBR
[Sat Jun 24 17:53:49 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --setMBREnable off ***** /dev/nvme10n1
[Sat Jun 24 17:53:49 2023] [ssd0] MBRDone set on
[Sat Jun 24 17:53:50 2023] [ssd0] MBREnable set off
[Sat Jun 24 17:53:50 2023] -----------------------------------------------------------------------------------
.
.
.
[Sat Jun 24 17:54:53 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:54:53 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme8n1
[Sat Jun 24 17:54:53 2023] [ssd8] /dev/nvme8n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:54:53 2023]
[Sat Jun 24 17:54:53 2023] [ssd8] factory reset 22443E9DC54E
[Sat Jun 24 17:54:53 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --PSIDrevert 8287AD621B440D756AB1D1E8273C6F94 /dev/nvme8n1
[Sat Jun 24 17:54:56 2023] [ssd8] revertTper completed successfully
[Sat Jun 24 17:54:56 2023]
[Sat Jun 24 17:54:56 2023] [ssd8] set default password
[Sat Jun 24 17:54:56 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --initialSetup ***** /dev/nvme8n1
[Sat Jun 24 17:54:57 2023] [ssd8] SID password changed
[Sat Jun 24 17:54:57 2023] [ssd8] takeOwnership complete
[Sat Jun 24 17:54:58 2023] [ssd8] Locking SP Activate Complete
[Sat Jun 24 17:54:59 2023] [ssd8] LockingRange0 disabled
[Sat Jun 24 17:54:59 2023] [ssd8] LockingRange0 set to RW
[Sat Jun 24 17:55:00 2023] [ssd8] MBRDone set on
[Sat Jun 24 17:55:01 2023] [ssd8] MBREnable set on
[Sat Jun 24 17:55:01 2023] [ssd8] Initial setup of TPer complete on /dev/nvme8n1
[Sat Jun 24 17:55:01 2023]
[Sat Jun 24 17:55:01 2023] [ssd8] disable MBR
[Sat Jun 24 17:55:01 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --setMBREnable off ***** /dev/nvme8n1
[Sat Jun 24 17:55:01 2023] [ssd8] MBRDone set on
[Sat Jun 24 17:55:02 2023] [ssd8] MBREnable set off
[Sat Jun 24 17:55:02 2023] >
config disk password
Changes the password used for all encryption related disk operations.
Enter Old Password may be ENTER/NULL in which case the default password will be used
Enter Old Password can be read without keyboard input from the file /tmp/disk-password-old if the file exists
Enter New Password can be read without keyboard input from the file /tmp/disk-password if the file exists
config disk password
Example of setting a new password from the default password
[Sat Jun 24 17:58:51 2023] > config disk password
[Sat Jun 24 17:58:53 2023] Enter Old Password:
[Sat Jun 24 17:58:56 2023] Enter New Password:
****
[Sat Jun 24 17:58:59 2023] Re-Enter New Password:
****
[Sat Jun 24 17:59:28 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:28 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme9n1
[Sat Jun 24 17:59:28 2023] [par0] /dev/nvme9n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:28 2023]
[Sat Jun 24 17:59:28 2023] [par0] set new password 22443E9D2087
[Sat Jun 24 17:59:28 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme9n1
[Sat Jun 24 17:59:29 2023] [par0] Admin1 password changed
[Sat Jun 24 17:59:29 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:29 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme10n1
[Sat Jun 24 17:59:29 2023] [ssd0] /dev/nvme10n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:29 2023]
[Sat Jun 24 17:59:29 2023] [ssd0] set new password 22443E9D204F
[Sat Jun 24 17:59:29 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme10n1
[Sat Jun 24 17:59:30 2023] [ssd0] Admin1 password changed
[Sat Jun 24 17:59:30 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:30 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme1n1
[Sat Jun 24 17:59:30 2023] [ssd1] /dev/nvme1n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:30 2023]
[Sat Jun 24 17:59:30 2023] [ssd1] set new password 22223AD5BFC3
[Sat Jun 24 17:59:30 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme1n1
[Sat Jun 24 17:59:32 2023] [ssd1] Admin1 password changed
[Sat Jun 24 17:59:32 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:32 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme6n1
[Sat Jun 24 17:59:32 2023] [ssd2] /dev/nvme6n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:32 2023]
[Sat Jun 24 17:59:32 2023] [ssd2] set new password 22443E9D3AFF
[Sat Jun 24 17:59:32 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme6n1
[Sat Jun 24 17:59:33 2023] [ssd2] Admin1 password changed
[Sat Jun 24 17:59:33 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:33 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme5n1
[Sat Jun 24 17:59:33 2023] [ssd3] /dev/nvme5n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:33 2023]
[Sat Jun 24 17:59:33 2023] [ssd3] set new password 22443E9DC543
[Sat Jun 24 17:59:33 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme5n1
[Sat Jun 24 17:59:34 2023] [ssd3] Admin1 password changed
[Sat Jun 24 17:59:34 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:34 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme7n1
[Sat Jun 24 17:59:34 2023] [ssd4] /dev/nvme7n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:34 2023]
[Sat Jun 24 17:59:34 2023] [ssd4] set new password 22443E9D2076
[Sat Jun 24 17:59:34 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme7n1
[Sat Jun 24 17:59:36 2023] [ssd4] Admin1 password changed
[Sat Jun 24 17:59:36 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:36 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme2n1
[Sat Jun 24 17:59:36 2023] [ssd5] /dev/nvme2n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:36 2023]
[Sat Jun 24 17:59:36 2023] [ssd5] set new password 22443E9D3B41
[Sat Jun 24 17:59:36 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme2n1
[Sat Jun 24 17:59:37 2023] [ssd5] Admin1 password changed
[Sat Jun 24 17:59:37 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:37 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme3n1
[Sat Jun 24 17:59:37 2023] [ssd6] /dev/nvme3n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:37 2023]
[Sat Jun 24 17:59:37 2023] [ssd6] set new password 22443E9D3B65
[Sat Jun 24 17:59:37 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme3n1
[Sat Jun 24 17:59:39 2023] [ssd6] Admin1 password changed
[Sat Jun 24 17:59:39 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:39 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme4n1
[Sat Jun 24 17:59:39 2023] [ssd7] /dev/nvme4n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:39 2023]
[Sat Jun 24 17:59:39 2023] [ssd7] set new password 22443E9D20A4
[Sat Jun 24 17:59:39 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme4n1
[Sat Jun 24 17:59:40 2023] [ssd7] Admin1 password changed
[Sat Jun 24 17:59:40 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 17:59:40 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme8n1
[Sat Jun 24 17:59:40 2023] [ssd8] /dev/nvme8n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 17:59:40 2023]
[Sat Jun 24 17:59:40 2023] [ssd8] set new password 22443E9DC54E
[Sat Jun 24 17:59:40 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --setPassword ***** Admin1 ***** /dev/nvme8n1
[Sat Jun 24 17:59:41 2023] [ssd8] Admin1 password changed
[Sat Jun 24 17:59:41 2023] >
config disk lock
This sets the disks into the locked state requiring a password.
On any power cycle command (disks loose power) the disks will need to be unlocked using the config disk unlock command and a password
The password can be read without keyboard input from the file/tmp/disk-password if the file exists
config disk lock
Example locks all data disks
[Sat Jun 24 18:03:58 2023] > config disk lock
[Sat Jun 24 18:03:58 2023] Enter Password. or CR for default:
****
[Sat Jun 24 18:04:00 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:00 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme9n1
[Sat Jun 24 18:04:00 2023] [par0] /dev/nvme9n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:00 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme9n1
[Sat Jun 24 18:04:01 2023] [par0] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:01 2023]
[Sat Jun 24 18:04:01 2023] [par0] set to locked22443E9D2087
[Sat Jun 24 18:04:01 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme9n1
[Sat Jun 24 18:04:02 2023] [par0] LockingRange0 set to LK
[Sat Jun 24 18:04:02 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:02 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme10n1
[Sat Jun 24 18:04:02 2023] [ssd0] /dev/nvme10n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:02 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme10n1
[Sat Jun 24 18:04:03 2023] [ssd0] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:03 2023]
[Sat Jun 24 18:04:03 2023] [ssd0] set to locked22443E9D204F
[Sat Jun 24 18:04:03 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme10n1
[Sat Jun 24 18:04:04 2023] [ssd0] LockingRange0 set to LK
[Sat Jun 24 18:04:04 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:04 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme1n1
[Sat Jun 24 18:04:04 2023] [ssd1] /dev/nvme1n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:04 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme1n1
[Sat Jun 24 18:04:05 2023] [ssd1] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:05 2023]
[Sat Jun 24 18:04:05 2023] [ssd1] set to locked22223AD5BFC3
[Sat Jun 24 18:04:05 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme1n1
[Sat Jun 24 18:04:06 2023] [ssd1] LockingRange0 set to LK
[Sat Jun 24 18:04:06 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:06 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme6n1
[Sat Jun 24 18:04:06 2023] [ssd2] /dev/nvme6n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:06 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme6n1
[Sat Jun 24 18:04:07 2023] [ssd2] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:07 2023]
[Sat Jun 24 18:04:07 2023] [ssd2] set to locked22443E9D3AFF
[Sat Jun 24 18:04:07 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme6n1
[Sat Jun 24 18:04:07 2023] [ssd2] LockingRange0 set to LK
[Sat Jun 24 18:04:07 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:07 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme5n1
[Sat Jun 24 18:04:07 2023] [ssd3] /dev/nvme5n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:07 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme5n1
[Sat Jun 24 18:04:08 2023] [ssd3] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:08 2023]
[Sat Jun 24 18:04:08 2023] [ssd3] set to locked22443E9DC543
[Sat Jun 24 18:04:08 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme5n1
[Sat Jun 24 18:04:09 2023] [ssd3] LockingRange0 set to LK
[Sat Jun 24 18:04:09 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:09 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme7n1
[Sat Jun 24 18:04:09 2023] [ssd4] /dev/nvme7n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:09 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme7n1
[Sat Jun 24 18:04:10 2023] [ssd4] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:10 2023]
[Sat Jun 24 18:04:10 2023] [ssd4] set to locked22443E9D2076
[Sat Jun 24 18:04:10 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme7n1
[Sat Jun 24 18:04:10 2023] [ssd4] LockingRange0 set to LK
[Sat Jun 24 18:04:10 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:10 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme2n1
[Sat Jun 24 18:04:10 2023] [ssd5] /dev/nvme2n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:10 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme2n1
[Sat Jun 24 18:04:11 2023] [ssd5] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:11 2023]
[Sat Jun 24 18:04:11 2023] [ssd5] set to locked22443E9D3B41
[Sat Jun 24 18:04:11 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme2n1
[Sat Jun 24 18:04:12 2023] [ssd5] LockingRange0 set to LK
[Sat Jun 24 18:04:12 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:12 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme3n1
[Sat Jun 24 18:04:12 2023] [ssd6] /dev/nvme3n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:12 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme3n1
[Sat Jun 24 18:04:13 2023] [ssd6] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:13 2023]
[Sat Jun 24 18:04:13 2023] [ssd6] set to locked22443E9D3B65
[Sat Jun 24 18:04:13 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme3n1
[Sat Jun 24 18:04:13 2023] [ssd6] LockingRange0 set to LK
[Sat Jun 24 18:04:13 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:13 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme4n1
[Sat Jun 24 18:04:13 2023] [ssd7] /dev/nvme4n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:13 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme4n1
[Sat Jun 24 18:04:14 2023] [ssd7] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:14 2023]
[Sat Jun 24 18:04:14 2023] [ssd7] set to locked22443E9D20A4
[Sat Jun 24 18:04:14 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme4n1
[Sat Jun 24 18:04:15 2023] [ssd7] LockingRange0 set to LK
[Sat Jun 24 18:04:15 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:04:15 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme8n1
[Sat Jun 24 18:04:15 2023] [ssd8] /dev/nvme8n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:04:15 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --enableLockingRange 0 ***** /dev/nvme8n1
[Sat Jun 24 18:04:16 2023] [ssd8] LockingRange0 enabled ReadLocking,WriteLocking
[Sat Jun 24 18:04:16 2023]
[Sat Jun 24 18:04:16 2023] [ssd8] set to locked22443E9DC54E
[Sat Jun 24 18:04:16 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 LK ***** /dev/nvme8n1
[Sat Jun 24 18:04:16 2023] [ssd8] LockingRange0 set to LK
config disk no-lock
This removes the disk locking function of the drives.
config disk no-lock
Example below shows a disk no-lock operation
[Fri Jun 30 08:59:34 2023] > config disk no-lock
[Fri Jun 30 08:59:34 2023] Enter Password. or CR for default:
**********
[Fri Jun 30 08:59:37 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:37 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme8n1
[Fri Jun 30 08:59:37 2023] [par0] /dev/nvme8n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:37 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme8n1
[Fri Jun 30 08:59:38 2023] [par0] LockingRange0 disabled
[Fri Jun 30 08:59:38 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:38 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme2n1
[Fri Jun 30 08:59:38 2023] [ssd0] /dev/nvme2n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:38 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme2n1
[Fri Jun 30 08:59:39 2023] [ssd0] LockingRange0 disabled
[Fri Jun 30 08:59:39 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:39 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme9n1
[Fri Jun 30 08:59:39 2023] [ssd1] /dev/nvme9n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:39 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme9n1
[Fri Jun 30 08:59:40 2023] [ssd1] LockingRange0 disabled
[Fri Jun 30 08:59:40 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:40 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme7n1
[Fri Jun 30 08:59:40 2023] [ssd2] /dev/nvme7n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:40 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme7n1
[Fri Jun 30 08:59:42 2023] [ssd2] LockingRange0 disabled
[Fri Jun 30 08:59:42 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:42 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme6n1
[Fri Jun 30 08:59:42 2023] [ssd3] /dev/nvme6n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:42 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme6n1
[Fri Jun 30 08:59:43 2023] [ssd3] LockingRange0 disabled
[Fri Jun 30 08:59:43 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:43 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme4n1
[Fri Jun 30 08:59:43 2023] [ssd4] /dev/nvme4n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:43 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme4n1
[Fri Jun 30 08:59:44 2023] [ssd4] LockingRange0 disabled
[Fri Jun 30 08:59:44 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:44 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme5n1
[Fri Jun 30 08:59:44 2023] [ssd5] /dev/nvme5n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:44 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme5n1
[Fri Jun 30 08:59:45 2023] [ssd5] LockingRange0 disabled
[Fri Jun 30 08:59:45 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:45 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme3n1
[Fri Jun 30 08:59:45 2023] [ssd6] /dev/nvme3n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:45 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme3n1
[Fri Jun 30 08:59:46 2023] [ssd6] LockingRange0 disabled
[Fri Jun 30 08:59:46 2023] -----------------------------------------------------------------------------------
[Fri Jun 30 08:59:46 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme1n1
[Fri Jun 30 08:59:46 2023] [ssd7] /dev/nvme1n1 SED -2----- SAMSUNG MZQL23T8HCLS-00A07 GDC5602Q
[Fri Jun 30 08:59:46 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --disableLockingRange 0 ***** /dev/nvme1n1
[Fri Jun 30 08:59:48 2023] [ssd7] LockingRange0 disabled
[Fri Jun 30 08:59:48 2023] >
config disk unlock
Unlocks the drives using the specified password
The password can be read without keyboard input from the file /tmp/disk-password if the file exists
config disk unlock
Example of unlocking
[Sat Jun 24 18:07:22 2023] > config disk unlock
[Sat Jun 24 18:07:23 2023] Enter Password:
****
[Sat Jun 24 18:07:24 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:24 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme9n1
[Sat Jun 24 18:07:24 2023] [par0] /dev/nvme9n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:24 2023]
[Sat Jun 24 18:07:24 2023] [par0] set to locked 22443E9D2087
[Sat Jun 24 18:07:24 2023] [par0] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme9n1
[Sat Jun 24 18:07:25 2023] [par0] LockingRange0 set to RW
[Sat Jun 24 18:07:25 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:25 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme10n1
[Sat Jun 24 18:07:25 2023] [ssd0] /dev/nvme10n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:25 2023]
[Sat Jun 24 18:07:25 2023] [ssd0] set to locked 22443E9D204F
[Sat Jun 24 18:07:25 2023] [ssd0] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme10n1
[Sat Jun 24 18:07:25 2023] [ssd0] LockingRange0 set to RW
[Sat Jun 24 18:07:25 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:25 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme1n1
[Sat Jun 24 18:07:25 2023] [ssd1] /dev/nvme1n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:25 2023]
[Sat Jun 24 18:07:25 2023] [ssd1] set to locked 22223AD5BFC3
[Sat Jun 24 18:07:25 2023] [ssd1] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme1n1
[Sat Jun 24 18:07:26 2023] [ssd1] LockingRange0 set to RW
[Sat Jun 24 18:07:26 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:26 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme6n1
[Sat Jun 24 18:07:26 2023] [ssd2] /dev/nvme6n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:26 2023]
[Sat Jun 24 18:07:26 2023] [ssd2] set to locked 22443E9D3AFF
[Sat Jun 24 18:07:26 2023] [ssd2] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme6n1
[Sat Jun 24 18:07:27 2023] [ssd2] LockingRange0 set to RW
[Sat Jun 24 18:07:27 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:27 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme5n1
[Sat Jun 24 18:07:27 2023] [ssd3] /dev/nvme5n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:27 2023]
[Sat Jun 24 18:07:27 2023] [ssd3] set to locked 22443E9DC543
[Sat Jun 24 18:07:27 2023] [ssd3] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme5n1
[Sat Jun 24 18:07:27 2023] [ssd3] LockingRange0 set to RW
[Sat Jun 24 18:07:27 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:27 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme7n1
[Sat Jun 24 18:07:27 2023] [ssd4] /dev/nvme7n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:27 2023]
[Sat Jun 24 18:07:27 2023] [ssd4] set to locked 22443E9D2076
[Sat Jun 24 18:07:27 2023] [ssd4] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme7n1
[Sat Jun 24 18:07:28 2023] [ssd4] LockingRange0 set to RW
[Sat Jun 24 18:07:28 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:28 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme2n1
[Sat Jun 24 18:07:28 2023] [ssd5] /dev/nvme2n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:28 2023]
[Sat Jun 24 18:07:28 2023] [ssd5] set to locked 22443E9D3B41
[Sat Jun 24 18:07:28 2023] [ssd5] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme2n1
[Sat Jun 24 18:07:29 2023] [ssd5] LockingRange0 set to RW
[Sat Jun 24 18:07:29 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:29 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme3n1
[Sat Jun 24 18:07:29 2023] [ssd6] /dev/nvme3n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:29 2023]
[Sat Jun 24 18:07:29 2023] [ssd6] set to locked 22443E9D3B65
[Sat Jun 24 18:07:29 2023] [ssd6] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme3n1
[Sat Jun 24 18:07:29 2023] [ssd6] LockingRange0 set to RW
[Sat Jun 24 18:07:29 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:29 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme4n1
[Sat Jun 24 18:07:29 2023] [ssd7] /dev/nvme4n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:29 2023]
[Sat Jun 24 18:07:29 2023] [ssd7] set to locked 22443E9D20A4
[Sat Jun 24 18:07:29 2023] [ssd7] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme4n1
[Sat Jun 24 18:07:30 2023] [ssd7] LockingRange0 set to RW
[Sat Jun 24 18:07:30 2023] -----------------------------------------------------------------------------------
[Sat Jun 24 18:07:30 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --isValidSED /dev/nvme8n1
[Sat Jun 24 18:07:30 2023] [ssd8] /dev/nvme8n1 SED -2----- Micron_7450_MTFDKCC3T8TFR E2MU110
[Sat Jun 24 18:07:30 2023]
[Sat Jun 24 18:07:30 2023] [ssd8] set to locked 22443E9DC54E
[Sat Jun 24 18:07:30 2023] [ssd8] sudo /usr/bin/sedutil-cli-sha512 --setLockingRange 0 RW ***** /dev/nvme8n1
[Sat Jun 24 18:07:31 2023] [ssd8] LockingRange0 set to RW
[Sat Jun 24 18:07:31 2023] >
System Configuration
config system fpga firmware
This configures the systems FPGA firmware, currently support modes
capture-2x100G (2 x100G packet capture mode)
capture-2x40G (2x40G packet capture mode)
capture-8x10G (8x10G packet capture mode)
NOTE: this only sets up the system. Reboot is required to start the configuration change
Example:
config system fpga firmware capture-2x100G
Output
[Fri Aug 25 15:52:35 2023] > config system fpga firmware capture-2x100G
[Fri Aug 25 15:52:35 2023] fmad fmadlua Aug 24 2023 (/usr/local/bin/fmadiolua /opt/fmadio/bin/firmware_install.lua --portchange )
[Fri Aug 25 15:52:35 2023] calibrating...
[Fri Aug 25 15:52:36 2023] 0 : 2095071170 2.0951 cycles/nsec offset:4.929 Mhz
[Fri Aug 25 15:52:36 2023] Cycles/Sec 2095071170.0000 Std: 0 cycle std( 0.00000000) Target:2.10 Ghz
[Fri Aug 25 15:52:36 2023] Change PortMode
[Fri Aug 25 15:52:36 2023] Copy [cp /mnt/system/boot/bitstream.rom.2x100G /mnt/system/boot/bitstream.rom]
[Fri Aug 25 15:52:36 2023] os[sudo /opt/fmadio/bin/bitstream_update.lua --noreboot --write /mnt/system/boot/bitstream.rom]
[Fri Aug 25 15:52:36 2023] fmad fmadlua Aug 24 2023 (/opt/fmadio/bin/fmadiolua /opt/fmadio/bin/bitstream_update.lua --noreboot --write /mnt/system/boot/bitstream.rom )
[Fri Aug 25 15:52:36 2023] calibrating...
[Fri Aug 25 15:52:37 2023] 0 : 2095073220 2.0951 cycles/nsec offset:4.927 Mhz
[Fri Aug 25 15:52:37 2023] Cycles/Sec 2095073220.0000 Std: 0 cycle std( 0.00000000) Target:2.10 Ghz
[Fri Aug 25 15:52:37 2023] cp: '/mnt/system/boot/bitstream.rom' and '/mnt/system//boot/bitstream.rom' are the same file
[Fri Aug 25 15:52:37 2023] done 0.006711Sec 0.000112Min
[Fri Aug 25 15:52:37 2023] Firmware Install Complete
[Fri Aug 25 15:52:37 2023] done 1.083203Sec 0.018053Min
[Fri Aug 25 15:52:37 2023] set port mode from(2x40G) -> (2x100G)
[Fri Aug 25 15:52:37 2023]
[Fri Aug 25 15:52:37 2023] ****************************************************
[Fri Aug 25 15:52:37 2023] *********** REBOOT IS REQUIRED. ********************
[Fri Aug 25 15:52:37 2023] ****************************************************
[Fri Aug 25 15:52:37 2023]
[Fri Aug 25 15:52:37 2023] Reboot -> Safe Mode -> FPGA Flash -> Reboot -> System ready (5-10 minutes)
[Fri Aug 25 15:52:37 2023]
[Fri Aug 25 15:52:37 2023] >