In this lesson, you will learn:

  • The security caveats of the Suzieq GUI.
  • How to validate the Path between spine1-nxos and spine2-nxos.

Suzieq GUI Intro

In addition to all the other interfaces and interaction methods we have covered, a GUI is also provided.

To confirm the port that we are running the Suzieq GUI on, we use the docker-compose ps suzieq_gui command:

$ docker-compose ps suzieq_gui
   Name       Command     State                    Ports                  
--------------------------------------------------------------------------
suzieq_gui   suzieq-gui   Up      0.0.0.0:8501->8501/tcp,:::8501->8501/tcp

Security

Authentication

Out of the box, the Suzieq GUI does not provide any form of authentication. Therefore, it is recommended that, for production-based environments, a device upstream is configured to provide an authentication layer for sessions coming into the Suzieq GUI.

Members Only Content
Join today and get access to:
  • Full deep-dive course library (inc. Batfish, pyATS, Netmiko)
  • Code repositories inc. full course code, scripts and examples
  • 24x7 Multi-vendor labs (Arista, Cisco, Juniper)
  • Private online community
  • Monthly online meetups

100% Satisfaction Guaranteed!
Cancel your membership at any time.


Join Today
Close You've successfully subscribed to Packet Coders.
Close Success! Your account is fully activated, you now have access to all content.
Close Welcome back! You've successfully signed in.
Close Nearly there! To activate your account, please click the link in the email we just sent you.