Logging into the Crosswork Data Gateway is your first step into managing and understanding your network's data flow. Think of it as opening the door to a central hub that connects your network devices to the broader Crosswork Cloud or Network Controller, even if they're miles apart.
Once you successfully log in, you're greeted by an interactive console. This isn't some fancy graphical interface; it's a straightforward command-line environment, designed for efficiency. It’s where the real work of managing and troubleshooting happens. Upon a successful login, you'll see a Main Menu, and what you see there depends entirely on who you are within the system.
There are two main characters in this login story: the Administrator (dg-admin) and the Operator (dg-oper). The dg-admin, created by default during setup, is the all-powerful user. They have the keys to pretty much everything – starting and stopping the gateway VM, registering applications, managing certificates, configuring server settings, and even kernel upgrades. They can't be deleted, which makes sense given their crucial role. It’s like being the captain of the ship, with full command.
On the other hand, the dg-oper is more like the ship's navigator or engineer. Their focus is on monitoring and troubleshooting. They can check the health of the gateway, pull error logs, get notified of issues, and run tests to ensure everything is communicating correctly. They have a more limited, but equally important, set of permissions, centered around keeping an eye on things and diagnosing problems.
This role-based access is key. The Main Menu will look different for each user. For the dg-admin, you'll see options like 'Get Enrollment Package,' 'Show System Settings,' 'Change Current System Settings,' 'Vitals,' 'Troubleshooting,' 'Change Passphrase,' and 'Log out.' The dg-oper will have a similar menu but with fewer options, particularly around changing system configurations. For instance, while both can view system settings, only the administrator can actually change them. This ensures that critical configurations are handled by those with the authority and understanding to do so.
When you're setting things up, especially if you're dealing with IPv6 addresses, remember to enclose them in square brackets, like [1::1]. It's a small detail, but it makes a big difference in ensuring your commands are understood correctly.
User authentication itself is handled locally on the Crosswork Data Gateway. This means the credentials you use are specific to this gateway instance, set up during its initial installation. It’s a straightforward process, ensuring that only authorized personnel can access and manage the gateway's functions.
