How Cenovel reaches a device

One model of the network

Cenovel builds one model of the network from facts it read and dated: links, ports, VLANs, neighbors, addresses, gateways and routes. Pages reason over it, from Health risks and Room diagnostics to the reachability verdict on a switch change. Anything not read is said to be unknown, never assumed.

Read “How Cenovel reaches it”

On a switch page, the How Cenovel reaches it card is dated with when it was worked out. Its rows:

Management interface

Where the switch’s management address lives, and which stack member holds it.

Gateway

The switch’s gateway, or “Cenovel is on the switch’s own subnet”.

Uplink

The port the path to Cenovel leaves by.

Access lists

“No access list on the SSH lines”, an access list that lets Cenovel in, or one that would not let Cenovel in.

SSH and account

Whether Cenovel’s sign-in can reach the switch.

The path

For example “Cenovel reads it from 10.20.0.5 through 3 links”. Anything that blocks the path is shown in red.

Address devices see Cenovel at

To check a switch’s access lists, Cenovel needs the address its reads come from as the switch sees them. On the appliance it works this out from its route to each switch. When something on the way changes that address, such as Cenovel running in a container or a firewall that translates addresses, set it:

1. As an Administrator EX, open Settings › System › Deployment and find Where Cenovel may connect.
2. Enter the address in Address devices see Cenovel at and save.

Left blank in a container install, the card says “Cenovel’s own address toward it not known”, and the access-list check is unknown rather than passed.

See also: Change a switch port · Health risks · Configuration & access