recs 1615 and 1735 are dups of one device.

Add to switch documentation.

Move the vlan columns from inventory to the new vlan table.

The inventory table has two distinct uses. First it is a
etailed inventory of the hardware that constitutes the CapCity
LAN(s). Second, a detailed map of our VLANs.

The vlan table is not an inventory, it is a map. There is
duplication of values like the switch's mac, but that is fine.
Queries can identify which devices are on which vlan. Which
vlan a switch port is configured as. Which switch ports are
for trunk lines to other switches and support move that one
vlan. (select base on nodemac and trunk to get the upstream
switch)

Need to show which ports are used by which VLANs (other than
trunk lines). The mac of the device wired to that switch port.
List all switches and their ports for a given vlan. Which vlan
(and switch and port) a device is connected to.

A switch has several ports with CAT6 running to either a
device or another switch. A trunk line connect two switches.
All others are connection ports. All devices are identified by
their mac. Unmanaged switches with no macs are are flagged and
their nodes listed in detail. Unmanaged switches support the
vlan that the upstream switch port is configured for. And, while
that is sort of a trunk line, it only supports the one vlan.
Unmanaged switches have no idea what a vlan is.


When working with a switch via the console (serial connection)
connect with a blue serial cable (which is a rollover cable)
and whatever adapters are needed. Then run putty to connect. You
will often need a DB-9 to USB adapter if the switch has a DB-9
console port. Other switches have RJ45 console ports leaving the
cable's DB-9 for the laptop, which usually does not have a DB-9
port, so you need the DB-9 to USB adapter to connect to the laptop.
Big fun.

Plug in and findout which COM port is being used.
Set "Speed (baud)"" to "115200"
Data bits = 8
Stop bits = 1
Parity = None
Flow Control = None

Start the session.
Enter the username with prompted (cisco or admin)
Enter the password

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/
software/release/3se/consolidated_guide/
b_consolidated_3850_3se_cg_chapter_01.html is a good resource
for getting started with the Cisco console command line.


VLAN table schema;

    id int not null auto_increment primary key,
    (the switch's mac)mac
    (the port on the switch)port
    (mac of the device connected to this switch port)nodemac
    (Yes|No)trunk (is this a trunk line?)
    vlan(number for that non-trunk switch port)
    managed(Yes|No)


In Cisco networking, a trunk port is a type of port on a switch
that is configured to carry traffic for multiple VLANs. Trunk ports
are used to interconnect switches and other network devices,
allowing them to exchange traffic for multiple VLANs over a single
physical link.

When a port is configured as a trunk port on a Cisco switch, it can
carry traffic for multiple VLANs by adding VLAN tags to the Ethernet
frames. These tags allow the receiving switch to distinguish which
VLAN the traffic belongs to and ensure that it is forwarded to the
correct destination within the VLAN.

Trunk ports use VLAN tagging protocols such as IEEE 802.1Q or Cisco's
proprietary Inter-Switch Link (ISL) to add and remove VLAN tags as
traffic passes between switches. By using trunk ports, network
administrators can efficiently segment traffic into different VLANs
while simplifying network topology and reducing the number of
physical links needed to connect multiple switches.

It's important to configure trunk ports correctly with the appropriate
VLAN configurations to ensure proper communication between devices
across VLANs in a network.

----
A Trunk port (on any switch) is one that is configured to carry data
frames for multiple VLANs (possibly, ALL known ones). This is in
contrast to a “normal” port called an Access port, which only carries
data frames for a single VLAN.

A trunk link (two Trunk ports on different devices directly connected
by a patch cable), provides connectivity between switches (or from a
switch to a router) for many VLANs, using only a single physical
connection. This minimizes port usage on each device while maximizing
the flexibility to assign ports to any VLAN on any switch.

To differentiate the VLAN to which a frame belongs as it traverses a
trunk, each frame is tagged to include VLAN information as it
egresses the source switch and untagged at the ingress device.

The common open standard for trunking is IEEE 802.1q, often
abbreviated to dot1q. This standard also includes the concept of a
native VLAN - any untagged frame ingressing on a trunk port is deemed
to belong to the native VLAN configured for the trunk. A dot1q trunk
can be configured to only allow certain VLAN IDs (typically, the
default is to allow ALL VLANs). A valid trunk will only be formed
between 2 devices if both sides agree on the allowed VLANs and the
native VLAN.

https://www.quora.com/What-is-a-trunk-port-on-a-Cisco-switch