In this lesson, we will recap on:
- Suzieq’s CLI key strengths.
- How to enter the Suzieq CLI.
- Suzieq's CLI architecture caveats.
Intro to Methods of Interaction
Suzieq provides various methods by which we can interact with it and the data it has learnt about the network. These include the Suzieq CLI, Python library, REST API and GUI.
Up until this point we have solely worked and explored Suzieq using the CLI. This has allowed us to get a feel and understanding of how we can query and explore our data within Suzieq. Therefore, this lesson acts as a recap of what we have already covered.
Suzieq CLI Recap
Therefore, to recap…
The key strength of the CLI is that it provides a quick and easy way to query/explore your network without having to write any code or API calls. This makes it an ideal interface for troubleshooting and lends itself well to quickly validating what is running within the network.
Entering the Suzieq CLI
To enter the Suzieq CLI, we perform execute
suzieq-cli via Docker Compose:
$ docker-compose exec suzieq_poller suzieq-cli root>
Once inside, we can run the various queries against our table:
root> interface show columns="hostname ifname mtu" hostname ifname mtu 0 leaf1-ios GigabitEthernet0/0 1500 1 leaf1-ios GigabitEthernet0/1 1500 2 leaf1-ios GigabitEthernet0/10 1500 3 leaf1-ios GigabitEthernet0/11 1500 4 leaf1-ios GigabitEthernet0/12 1500 .. ... ... ... 302 spine2-nxos Ethernet1/9 1500 303 spine2-nxos default 1500 304 spine2-nxos loopback0 1500 305 spine2-nxos management 1500 306 spine2-nxos mgmt0 1500