VLAN

With thanks to the 50 staff from across the University for attending please see below the links to the videos and PowerPoints of the day!

Direct link to Playlist – https://www.youtube.com/watch?list=PLRxbdlgJzwyjAf820T0u4GpP0E01a9LEX&v=u-GVJ_0VuRM

Slides as PowerPoint

  1 Intro (4.3 MiB, 417 hits)

  2 MDT (85.2 MiB, 490 hits)

  3 PowerShell (27.5 MiB, 384 hits)

  4 PRTG Network Monitor (47.5 MiB, 411 hits)

  5 OpenVAS (32.9 MiB, 360 hits)

  6 WSUS and Chocolatey (60.3 MiB, 406 hits)

  7 NPS and VLANs (10.7 MiB, 460 hits)

Slides as PDF

  1 Intro (2.0 MiB, 375 hits)

  2 MDT (2.2 MiB, 487 hits)

  3 PowerShell (1.8 MiB, 441 hits)

  4 PRTG Network Monitor (3.2 MiB, 440 hits)

  5 OpenVAS (2.3 MiB, 434 hits)

  6 WSUS and Chocolatey (2.9 MiB, 473 hits)

  7 NPS and VLANs (1.4 MiB, 436 hits)

Stay tuned over the coming days for the scripts that are mentioned through the video which will be linked to from this post.

If you are running an HPE Aruba (formally ProCurve) switch you may come across cases where your switch (in the example above a 5400R zl2) has multiple IP Addresses/VLANs and you need it to talk to another service (in my case syslog and sFlow receivers) on a set interface.

When this occurs you can use the ip source-interface command (make sure you are in config mode first) to define the IP Address or VLAN that you want the switch to talk out on. In my case VLAN2 which is used as the management network for the network switches (VLAN1 being the default network that switches use if multiple addresses are configured).