Information Systems:LAN infrastructure at uniPHARM

Overview

This is the main page for the LAN (wired network configuration) at uniPHARM.

Switches

This table outlines the physical network switches that make up the network.

Hostname	IP address	Switch model	Location	Username	Password	Notes
coresw.unipharm.local	172.30.16.2	3Com 3870	Server room	admin	visionit	Core switch. Stack of 4.
atpsw.unipharm.local	172.30.16.3	3Com 4200	Server room	admin	visionit	Feeds data to POE injectors for Mirador temp. sensors
accountingsw.unipharm.local	172.30.16.11	Cisco SG300-28P	Accounting Wallmount Network Rack	adminit	NewVisionIT2051	POE, ~175W power budget
buyersw.unipharm.local	172.30.16.5	3Com 4200G?	Buying department closet	admin	visionbs	-
itsw.unipharm.local	172.30.16.6	3Com 4200G	IT department ceiling tile. Yup.	admin	visionis	-
dumpsw.unipharm.local	172.30.16.7	3Com 4200G?	Electrical Room?	admin	visionds	-
pickingsw.unipharm.local	172.30.16.8	3Com 3870?	Rx picking zone network rack	admin	visionps	-
receivingsw.unipharm.local	172.30.16.10	3Com 4200G?	Outside Gerald's office, ceiling tile	admin	visionrs	-
wallsw.unipharm.local	172.30.16.7	3Com 4200G?	Candy Mezzanine	admin	visionns	Functions merely to bridge the physical wiring between Receiving area and core network
jeremymsw	172.30.16.16	TP-Link SG105E	Jeremy's office	admin	visionit	Used for testing Yealink, web-managed smart switch
norwinusw	172.30.16.15	Netgear GS105PE	Norwin's office	-	visionit	Used to access multiple VLANs, network administration, and testing. This switch has PoE passthrough.

• External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
• There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

VLANs

We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

VLAN ID	Name	L3 Network / IP Range	Description	Notes
1	Main LAN	172.30.16.0/21 (172.30.16.1 - 172.30.23.255)	Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all).	Routed out Telus Fibre
2	Staff and guest WiFi	192.168.0.1/23 (192.168.0.1 - 192.168.1.254)	Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created.	Routed out Shaw Business Internet
3	vMotion LAN	??	Small network to isolate vMotion traffic between the 3 virtual hosts.
4	Shaw WAN	Network of the WAN IP (/22?)	Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here!
5	Telus WAN	Network of the WAN IPs (/27)	Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network.
6	VoIP LAN	192.168.2.0/24	Contains PBX and IP phones	Routed out dedicated Shaw SIP internet connection.
7	Alt LAN	192.168.3.0/24	Network containing business devices that we do not want in our main LAN e.g. shipping terminals, digital signage player	Routed out Shaw Business Internet, uses Telus Fibre as a backup.