Information Systems:LAN infrastructure at uniPHARM
Jump to navigation
Jump to search
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, the reason being the same as 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 | Description |
|---|---|---|
| 1 | Main LAN | 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). |
| 2 | Guest LAN | Guest WiFi |
| 6 | VoIP LAN | efef |