0

So I know that I can configure my switch to trunk a port and tag/untag packets from my Windows and UNIX servers using functionality provided by the NIC. My question is, what are all the downsides of doing something like this vs. having multiple physical NICs on access switches? What I can think of:

  • multiple vlans on a single nic means if the nic dies I lose all my vlans
  • security implications?

Thanks

peelers
  • 11
  • 1

1 Answers1

1

multiple vlans on a single nic means if the nic dies I lose all my vlans

What you are talking about is honestly no different than what most companies do with VOIP phones, where a single nic in the VOIP phone and 802.1Q tagging on the port allows for both the phone and a daisy-chained computer to share the same phy port on the switch. This is done all the time, works just fine.

security implications?

This is way too vague. What kind of security are we talking about? If the port is simply tagged on the switch then any NIC with the same tag setting could potentially connect through that port. 802.1q tagging isn't really a "security" thing, it's a segmentation thing. If you want security, look into port lockdown methods (MAC learning, etc.). Security implications are really separate from actual port/nic tagging.

TheCleaner
  • 32,352
  • 26
  • 126
  • 188