Sure. So I could have checked the length and simply used index of the switch list, but since we don't have a good frame of reference for how a switch should look outside of other switches, we're relying on existing ones to decide. In this method, we're getting the transport zone information and whether or not it has a VLAN associated with it, and then returning those. 

We take that information, and make a new switch with all of the pertinent attributes to match. In the optimized driver, we'll store these in the lswitch tables (working on that now) so we don't have to look up switches in NVP to copy their attributes.