upd3

Author: tarTech23

articles/defender-for-iot/organizations/cli-ot-sensor.md

@@ -57,6 +57,17 @@ shell> system sanity
 
 System is UP! (medium)
 ```
+
+### Common commands
+
+At each level of the CLI you can use the following commands:
+
+- back - returns to the previous CLI level.
+- exit - exits the CLI connection.
+- help - lists available commands.
+
+when you need to enter a password, you have three attempts before the command closes and returns you to the previous command line.
+
 ### Reboot and shutdown
 
 #### Reboot an appliance
@@ -112,7 +123,7 @@ Version: 22.2.5.9-r-2121448
 
 #### Update sensor software from CLI
 
-For more information, see [Update your sensors](update-ot-software.md#update-ot-sensors).
+For more information, see [Update your sensors](update-ot-software.md?tabs=cli#update-ot-sensors).
 
 ### Date, time, and NTP
 
@@ -133,7 +144,7 @@ shell> date
 Thu Sep 29 18:38:23 UTC 2022
 ```
 
-#### Turn on NTP time sync   ??????
+#### Turn on NTP time sync  
 
 Use the following commands to turn on synchronization for the appliance time with an NTP server.
 
@@ -165,7 +176,7 @@ Monit restart chronyd process: 0
 Finished ntp-enable
 ```
 
-#### Turn off NTP time sync    ????
+#### Turn off NTP time sync 
 
 Use the following commands to turn off the synchronization for the appliance time with an NTP server.
 
@@ -205,23 +216,20 @@ Use the following commands to list the backup files currently stored on your OT
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
-|**admin**     |   `system backup-list`      |   No attributes      |
+|**admin**     |   `system backup list`      |   No attributes      |
 |**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   ` cyberx-xsense-system-backup-list`      |   No attributes      |
 
-
 For example, for the *admin* user:
 
 ```bash
-root@xsense: system backup-list
+shell> system backup list
 backup files:
         e2e-xsense-1664469968212-backup-version-22.3.0.318-r-71e6295-2022-09-29_18:30:20.tar
         e2e-xsense-1664469968212-backup-version-22.3.0.318-r-71e6295-2022-09-29_18:29:55.tar
-root@xsense:
 ```
 
-
 ### Start an immediate, unscheduled backup
-
+<!-- is there a scheduled backup command? if this is the only one, maybe change to start a backup or start and unscheduled backup? -->
 Use the following commands to start an immediate, unscheduled backup of the data on your OT sensor. For more information, see [Set up backup and restore files](../how-to-manage-individual-sensors.md#set-up-backup-and-restore-files).
 
 > [!CAUTION]
@@ -232,17 +240,16 @@ Use the following commands to start an immediate, unscheduled backup of the data
 |**admin**     |   `system backup`      |   No attributes      |
 |**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   ` cyberx-xsense-system-backup`      |   No attributes      |
 
-
 For example, for the *admin* user:
 
 ```bash
-root@xsense: system backup
+shell> system backup
 Backing up DATA_KEY
 ...
 ...
 Finished backup. Backup is stored at /var/cyberx/backups/e2e-xsense-1664469968212-backup-version-22.2.6.318-r-71e6295-2022-09-29_18:29:55.tar
 Setting backup status 'SUCCESS' in redis
-root@xsense:
+
 ```
 
 ### Restore data from the most recent backup
@@ -257,11 +264,10 @@ Use the following commands to restore data on your OT network sensor using the m
 |**admin**     |   `system restore`      |   No attributes      |
 |**cyberx**, or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)   |   ` cyberx-xsense-system-restore`      |   `-f` `<filename>`      |
 
-
 For example, for the *admin* user:
 
 ```bash
-root@xsense: system restore
+shell> system restore
 Waiting for redis to start...
 Redis is up
 Use backup file as "/var/cyberx/backups/e2e-xsense-1664469968212-backup-version-22.2.6.318-r-71e6295-2022-09-29_18:30:20.tar" ? [Y/n]: y
@@ -270,10 +276,10 @@ WARNING - the following procedure will restore data. do not stop or power off th
 ...
 watchdog started
 starting components
-root@xsense:
-```
 
+```
 
+<!-- did find backup-memory-check
 ### Display backup disk space allocation
 
 The following command lists the current backup disk space allocation, including the following details:
@@ -296,11 +302,10 @@ root@xsense:/# cyberx-backup-memory-check
 Backup limit is: 20Gb
 root@xsense:/#
 ```
-
+-->
 
 ## TLS/SSL certificates
-
-
+<!-- this entire section doesnt seem to exist anymore - has it been moved??-->
 ### Import TLS/SSL certificates to your OT sensor
 
 Use the following command to import TLS/SSL certificates to the sensor from the CLI.
@@ -361,20 +366,30 @@ root@xsense:/#
 
 
 ## Local user management
-
+<!-- this entire section doesnt seem to exist anymore - has it been moved??-->
 ### Change local user passwords
 
-Use the following commands to change passwords for local users on your OT sensor.
+Use the following commands to change passwords for local users on your OT sensor. The new password must be at least 8 characters, contain lowercase and uppercase, alphabetic characters, numbers and symbols.
 
 When you change the password for the *admin*, *cyberx*, or *cyberx_host* user, the password is changed for both SSH and web access.
 
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
+|**admin**     |   `system password`      |   <username>      |
 |**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   `cyberx-users-password-reset`      | `cyberx-users-password-reset -u <user> -p <password>`      |
 |**cyberx_host**, or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)  |   `passwd` | No attributes   |
 
+For example, for the *admin* user:
+
+```bash
+shell> system password user1
+Enter New Password for user1:
+Reenter Password:
+
+```
 
+<!-- exclude the following examples.-->
 The following example shows the *cyberx* user resetting the *admin* user's password to `jI8iD9kE6hB8qN0h`:
 
 ```bash
@@ -399,7 +414,7 @@ passwd: all authentication tokens updated successfully.
 cyberx_host@xsense:/#
 ```
 
-
+<!-- are these 2 still relevant??-->
 ### Control user session timeouts
 
 Define the time after which users are automatically signed out of the OT sensor. Define this value in a properties file saved on the sensor.
@@ -424,6 +439,8 @@ Use the following command to rerun the OT monitoring software configuration wiza
 - Configure network settings for the management interface (IP, subnet, default gateway, DNS)
 - Assigning a backup directory
 
+First enter Network to be at the network level of the CLI.
+
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
 |**cyberx_host**, or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)      |   `sudo dpkg-reconfigure iot-sensor`      |   No attributes     |
@@ -449,7 +466,7 @@ Use the following commands to validate and show the current network interface co
 For example, for the *admin* user:
 
 ```bash
-root@xsense: network validate
+shell> network validate
 Success! (Appliance configuration matches the network settings)
 Current Network Settings:
 interface: eth0
@@ -458,7 +475,6 @@ subnet: 255.255.192.0
 default gateway: 10.1.0.1
 dns: 168.63.129.16
 monitor interfaces mapping: local_listener=adiot0
-root@xsense:
 ```
 
 ### Network connectivity
@@ -472,6 +488,13 @@ Use the following commands to send a ping message from the OT sensor.
 |**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)     |   `ping <IP address>`      |   No attributes |
 
 In these commands, `<IP address>` is the IP address of a valid IPv4 network host accessible from the management port on your OT sensor.
+```bash
+shell> network ping 170.20.248.140
+PING 170.20.248.140 (170.20.248.140) 56(84) bytes of data.
+
+--- 170.20.248.140 ping statistics ---
+5 packets transmitted, 0 received, 100% packet loss, time 4082ms
+```
 
 #### Check network interface current load
 
@@ -579,7 +602,7 @@ In this command, `<INT>` is a physical ethernet port on the appliance.
 The following example shows the *admin* user blinking the *eth0* interface:
 
 ```bash
-root@xsense: network blink eth0
+shell> network blink eth0
 Blinking interface for 20 seconds ...
 ```
 
@@ -595,7 +618,7 @@ Use the following commands to list the connected physical interfaces on your OT
 For example, for the *admin* user:
 
 ```bash
-root@xsense: network list
+shell> network list
 adiot0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 4096
         ether be:b1:01:1f:91:88  txqueuelen 1000  (Ethernet)
         RX packets 2589575  bytes 740011013 (740.0 MB)
@@ -618,8 +641,6 @@ lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 837196  bytes 259542408 (259.5 MB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
-
-root@xsense:
 ```
 
 ## Traffic capture filters