Moderator

 • 

9.5K Posts

March 6th, 2017 10:00

Hi,

It looks like you have everything planned out well. It should be the easy to switch over. You will probably want to save the current config to a file in case something goes wrong and doing it after hours would be safer, but if everything works as expected there should not be any downtime on the switch side, clients may need to get new IP addresses. 

1 Rookie

 • 

18 Posts

March 6th, 2017 12:00

Thanks. Is that all there is to this? I haven't over-looked any obscure setting? I don't have to do anything special since I have different switch models?

Thanks

Moderator

 • 

9.5K Posts

March 6th, 2017 13:00

Voice vlan is for voip when you have both a computer and phone connected on the same Ethernet cable, so it puts the phone in a tagged vlan and the computer in an untagged vlan. It just has additional configuration over the normal vlan config. 

Moderator

 • 

9.5K Posts

March 6th, 2017 13:00

There shouldn’t be any other settings in this case since you didn’t say you were doing a voice vlan. The different models will handle VLANs the same way. 

1 Rookie

 • 

18 Posts

March 6th, 2017 13:00

Well what's the difference if I was doing a voice vlan? And what is voice anyway, voip? We currently have our phones connected to our existing powerconnects on the default vlan and I don't think we did anything special, as they just work since voice data is the same as regular data... Say I wanted to put the phones on a 3rd VLAN, what would I need to do differently?

Thanks again.

1 Rookie

 • 

18 Posts

March 6th, 2017 14:00

I see. Thanks for the help!

No Events found!

Top