Contents
Dashboard
The Dashboard is the home page of Atlas. It gives you a quick summary of everything in the system at a glance.
The top row of cards shows the total number of Sites, Network Devices, AV Devices, IP Prefixes, and Circuits in the system. These counts update automatically as records are added.
Below the summary cards, the Status Summary panel breaks down devices and circuits by their current status: Active, Maintenance, or Offline. This gives network staff an instant view of anything that is not in normal operation.
To navigate to any section, use the sidebar on the left. The sidebar is always visible and grouped into three areas: Navigation (Dashboard), Data (Sites, devices, IPAM, Circuits), and Tools (Ping, Traceroute, Routing Check).
Sites
The Sites section shows all physical office locations and data centers managed by the network team. Each site has a name, a short location code (such as "NYC" or "CHI"), and a status.
Click any site name in the list to open its detail page. The detail page shows the full address, the on-site office manager contact information, and a list of floors.
Navigating the Site Hierarchy
Atlas organises each site into Floors and Rooms. From a site detail page, click a floor name to see the rooms on that floor. From a floor page, click a room name (or the room's heading) to see the individual devices assigned to that room.
The breadcrumb trail at the top of each page shows your current location in the hierarchy, for example: Sites › New York HQ › Floor 2 › Server Room A. Click any breadcrumb link to navigate back up the hierarchy.
Status indicators use consistent colour coding across all sections: Active (green) means normal operation, Maintenance (yellow) means the site is temporarily in a reduced-service state, and Offline (red) means the site is not currently operational.
Network Devices
The Network Devices section lists all routers, switches, firewalls, access points, and servers managed by the network team. Each row shows the device's hostname, its management IP address (the address used to log in and manage the device), its type and role, the site it is located at, and its current status.
Click a hostname to open the device detail page, which shows the full record: physical location (floor and room), serial number, operating system version, and a table of the device's network interfaces with their IP addresses and MAC addresses.
Device roles are abbreviated in the system. Here is what each abbreviation means:
- SW — Switch (connects devices on a local network)
- FW — Firewall (controls traffic between network zones)
- RTR — Router (directs traffic between networks)
- AP — Access Point (provides Wi-Fi coverage)
- SRV — Server (provides computing services)
AV Devices
The AV Devices section tracks audio/visual equipment such as displays, projectors, video conferencing systems, and digital signage. This equipment is typically installed in meeting rooms and common areas.
The list view shows each device's name, its room location, model, and status. Click a device name to open the detail page, which shows the full record including manufacturer, serial number, network IP address (if the device is network-connected), display size or type, and install date.
The same status colour coding applies: Active, Maintenance, and Offline.
IPAM
IPAM stands for IP Address Management. This section shows all the IP address ranges (called prefixes) that have been assigned within the organisation's network.
Each prefix is shown in CIDR notation (Classless Inter-Domain Routing — a standard shorthand for describing IP address ranges), for example 10.1.4.0/24. The number after the slash (the prefix length) tells you how large the address range is — a /24 contains 254 usable addresses. You will also see the VRF (Virtual Routing and Forwarding instance — a way to separate network traffic into different routing tables) and the tenant the prefix belongs to.
Click a prefix to open its detail page. The detail page shows a utilisation bar indicating how many of the available addresses have been assigned. Below that, a table lists every individual IP address within the prefix, along with a description of what it is assigned to (such as a device's management interface) and its status.
Circuits
The Circuits section lists all wide-area network connections (also called circuits or links) provided by external carriers. These are the connections that link your office sites together and connect your network to the internet.
Each row in the list shows the provider (the carrier company), the circuit ID (the provider's reference number for the connection), the circuit type (such as MPLS — Multi-Protocol Label Switching, a technology used for fast private network links — Internet, or Dark Fibre), the A-side and Z-side (the two ends of the connection — usually two office sites), and the current status.
Click a circuit ID to open the detail page, which shows the full record including bandwidth, installation date, contract expiry date, provider account number, and any notes added by the network team.
Tools
The Tools section provides three network diagnostic utilities. Each tool works the same way: fill in the input field(s), click the button, and the result appears below the form on the same page. All output is generated for demonstration purposes.
Ping
Purpose: Ping tests whether a device is reachable on the network by sending small test packets and measuring how long they take to return.
How to use: Enter the IP address or hostname of the device you want to test in the IP Address or Hostname field, then click Run. The result appears below.
Reading the output: Each line starting with "64 bytes from" represents one test packet that was successfully returned. The time= value (in milliseconds, abbreviated "ms") shows how long the round trip took — lower numbers indicate a faster, more responsive connection. The statistics summary at the bottom shows the minimum, average, and maximum round-trip times across all packets sent.
Sample Output
PING 10.1.0.1 (10.1.0.1): 56 data bytes 64 bytes from 10.1.0.1: icmp_seq=0 ttl=64 time=1.234 ms 64 bytes from 10.1.0.1: icmp_seq=1 ttl=64 time=1.456 ms 64 bytes from 10.1.0.1: icmp_seq=2 ttl=64 time=2.103 ms 64 bytes from 10.1.0.1: icmp_seq=3 ttl=64 time=1.789 ms 64 bytes from 10.1.0.1: icmp_seq=4 ttl=64 time=1.601 ms 64 bytes from 10.1.0.1: icmp_seq=5 ttl=64 time=1.312 ms 64 bytes from 10.1.0.1: icmp_seq=6 ttl=64 time=1.987 ms 64 bytes from 10.1.0.1: icmp_seq=7 ttl=64 time=2.245 ms 64 bytes from 10.1.0.1: icmp_seq=8 ttl=64 time=1.544 ms 64 bytes from 10.1.0.1: icmp_seq=9 ttl=64 time=1.876 ms --- 10.1.0.1 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 1.234/1.715/2.245/0.253 ms
Traceroute
Purpose: Traceroute maps the path that network traffic takes from your location to a destination, showing each intermediate network device (called a hop) along the way.
How to use: Enter the IP address or hostname of the destination in the IP Address or Hostname field, then click Run. The result appears below.
Reading the output: Each numbered line represents one hop — one network device that the traffic passed through on its way to the destination. The IP address shown is the address of that device. The three time values (in milliseconds) are three separate measurements of how long it took to reach that hop — they should be similar to each other. The final hop is the destination you entered.
Sample Output
traceroute to 10.5.0.1 (10.5.0.1), 30 hops max, 60 byte packets 1 10.0.1.1 0.512 ms 0.598 ms 0.643 ms 2 10.0.2.14 1.234 ms 1.289 ms 1.301 ms 3 192.168.1.1 2.056 ms 2.112 ms 2.198 ms 4 10.1.3.254 3.401 ms 3.489 ms 3.512 ms 5 10.2.0.1 4.123 ms 4.234 ms 4.301 ms 6 10.3.1.45 5.678 ms 5.712 ms 5.801 ms 7 10.4.0.2 7.234 ms 7.301 ms 7.389 ms 8 10.5.0.1 8.456 ms 8.512 ms 8.601 ms
Routing Check
Purpose: Routing Check performs a policy and route lookup to show whether traffic from one IP address to another would be allowed or blocked by the firewall, and which path it would take.
How to use: Enter the Source IP (where the traffic originates) and the Destination IP (where the traffic is going), then click Check Route. The result appears below.
Reading the output: The Policy lookup section shows whether a firewall rule was matched (the "Policy ID" and "Name") and what the firewall's decision is — PERMIT means traffic is allowed, DENY means it is blocked. The Route lookup section shows which network interface the traffic would exit through and the IP address of the next device it would be handed off to (Next-hop).
Sample Output
Policy lookup: src=10.1.0.50 dst=10.5.0.1
Policy ID : 347
Name : corp-to-corp-347
Action : PERMIT
From zone : trust
To zone : untrust
Route lookup: dst=10.5.0.1
Prefix : 10.5.0.1/24
Next-hop : 10.2.0.1
Interface-in : ge-0/0/0.10
Interface-out: ge-0/0/2.30
Metric : 0
Result: Traffic from 10.1.0.50 to 10.5.0.1 would be PERMITTED
via ge-0/0/2.30 -> 10.2.0.1