===========
First Steps
===========

This section focuses on two key commands to check the device is running properly.
These commands are :osdx:op:`show version` and :osdx:op:`show running`.


:osdx:op:`show version` shows a summary with the relevant details of an OSDx device (such as the OS version, hardware cpu and so on).
This command is useful to know if the device is using the appropriate version, the license uploaded,
reboot reasons, logged users, CPU and memory usage, etc.

.. code-block:: none

  admin@osdx$ show version

  Bootloader name:           U-Boot
  Bootloader version:        2018.03-1.33
  Bootloader build date:     Oct 25 2024 - 12:38:23

  OS vendor:                 Windbit
  OS name:                   OSDx
  OS version:                v4.2.1.3
  OS Linux kernel:           6.1.55
  OS built by:               jenkins@daphne
  OS build date:             Mon Feb 3 09:56:32 UTC 2025
  OS installation:           physical
  OS boot mode:              user
  OS min bootloader:         0
  License:                   RS420_BASE CELL RD-ETSI WLAN

  Hardware vendor:           Windbit
  Hardware model:            RS420
  Hardware S/N:              DAAXZ-005104
  Hardware UUID:             7e38e8af-7a1c-57fd-828d-18b22076eed7
  Hardware architecture:     arm64
  Hardware fwid:             mmc_a
  Hardware base MAC:         00:a0:26:0e:3a:a4
  Hardware cpu:              1 x Cortex-A53 (2 cores)
  Hardware mfg date:         2023W47

  WLAN regulatory domain:    etsi

  Last reboot reason:        Performed by user

  Date:                      Thu 13 Feb 2025 09:18:16 +00:00
  Uptime:                    0:01:28
  CPU load (1m, 5m, 15m):    1.21 0.41 0.15
  CPU usage % (1m):          54.05
  Storage usage (kB):        1331876/3707814
  Memory usage (kB):         304508/993080
  Users logged in:           1
  Mode (current/next boot):  user/user

  Hostname:                  osdx
  Description:               DESC


The :osdx:op:`show running` command displays information about the active
configuration running at the device. In many situations, an unexpected
behavior could happen if the applied configuration is incomplete
and another configuration is needed, or if the configuration was
accidentally modified and the device stops working. For all these reasons,
**knowing the exact device configuration is very important**.


.. code-block:: none

  admin@osdx$ show running
    # Teldat OSDx RS420 version v4.2.1.3
    # Tue 25 Feb 2025 09:24:18 +00:00
    # Warning: Configuration has not been saved
    set interfaces dummy dum0 address 10.1.0.1/24
    set interfaces ethernet eth0 address 192.168.122.3/24
    set protocols route-map PERMIT rule 1 action permit
    set protocols static route 0.0.0.0/0 next-hop 192.168.122.1
    set protocols static route 10.3.0.0/24 interface dum0
    set service dns resolver name-server 192.168.212.3
    set service ssh login-grace-time 20
    set system cli configuration logging global debug
    set system host-name osdx
    set system login user admin authentication encrypted-password '$6$0KEbgj.xmAkxRXdj$xVuuG83x3ve/7ga650eNlliN8d/ByVOB39/VWGXv/4w5k.Gt4V74bKsIpd0IerBZ/sBESKHYpzBB00Nx6N4DW.'
    set system security medium