Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Ip Office 500, Cisco Switch 3560 Layer3, Voice & Data Vlans Guide.

Status
Not open for further replies.

kokolatas

IS-IT--Management
Nov 19, 2007
162
GR
Hello.

I just implemented Voice and Data VLANS on a Cisco Switch 3560 layer3 and an IPO 500, and i would like to give you sort a brief of that, so if any of you need help,could easily find some from that thread.

The Ip Phones i used was the 46xx series.

The IP phones have been statically administered, so if you are looking for DHCP instructions you should look on another
thread.

The idea is to put the PBX on the Voice vlan, the manager PC on the Voice Vlan and the Ip Phones with the PCs on both vlans, by configure the switch ports. Then if you are interesting of communication between those 2 vlans you should implement an Intervlan Routing on a Layer 3 Switch or on a Router. For my lab, i used the Cisco 3560 Layer 3 Switch.

So lets suppose that the vlans design is something like that.

192.168.42.0 ( Data ) VLAN 10
192.168.45.0 ( Voice ) VLAN 20

First lets configure the Switch.

1.) #vlan database
vlan 10 name Data
vlan 20 name Voice

2.) (PBX Switch Port)

conf t
int fa0/1
switchport access vlan 20

3.) (IP Phones & PCs)

conf t
int fa0/2
switchport access vlan 10
switchport voice vlan 20

4.) (Manager PC)

conf t
int fa0/3
switchport access vlan 30

5.) (Stand Alone PCs)

conf t
int fa0/xx
switchport access vlan 10

6.) InterVlan Routing on the switch.

conft> ip routing
exit
#int vlan 10
confif>ip add 192.168.42.254 255.255.255.0
no shut
exit
#int vlan 20
confif>ip add 192.168.45.254 255.255.255.0
no shut
exit

So I have 2 directly connected networks on my switch (voice and data) which of course the are able to communicate each other.

Right now, you should configure the PCs to have as Default Gateway the interface on the switch of their respectively Vlan. (192.168.42.254)

The same, you should do for the Manager PC with the difference that it must have the voice vlan default gateway. (192.168.45.254).

In the Manager PC, you should also change the 46xx settings.
Find the vlan test and L2qvlan fields, and change them on those.
Set vlan test 0
Set L2QVLAN 20 ***(voice vlan)****
Don't forget to delete the ## symbols and of course to save the file.

Then before reboot the phones, you must statically administer them with all the Ip address, the voice vlan which it should be the vlan 2 and the vlantest = 60.

The reason i did that, was that the phones could not download the 46xx settings because by default they boot on the default vlan (vlan 0).

So what i did, was to put them on the voice vlan. After they reboot, they download the 46xx settings which i have previously changed.
So, even i have not test it out, i don't think they will lose their vlan settings on Power Failure.

An other thing is to put a default route on the PBX with exit interface the Lan1 port.

Network :0.0.0.0 SubnetMasn :0.0.0.0 Default Gateway :Blank Exit Interface : Lan1.

You should do that, because the IPO doesn't know where to forward the packets when it receives packets with a source address from the data vlan.

*** If you are looking for DHCP Implemention guide, even though i have never done it before, don't forget to allow the DHCP Broadcasts (DHCPDISCOVER,DHCPREQUEST) to move through the Switch or Routers Interface.
You may have a DCHP Server on one LAN segment, and you also may want to allow this DHCP Server to receive and give DHCP 'informations' on an other segment.
So you should give the <ip helper address ...DCHP IP...> in the interface of the second segment which is not physically communicate direrctly with the DHCP Server.

So that's all from me.

Good Luck and I hope that you find this guide helpful.

Thanks.





 
****This is the same guide but with some corrections****

Hello.

I just implemented Voice and Data VLANS on a Cisco Switch 3560 layer3 and an IPO 500, and i would like to give you sort a brief of that, so if any of you need help,could easily find some from that thread.

The Ip Phones i used was the 46xx series.

The IP phones have been statically administered, so if you are looking for DHCP instructions you should look on another
thread.

The idea is to put the PBX on the Voice vlan, the manager PC on the Voice Vlan and the Ip Phones with the PCs on both vlans, by configure the switch ports. Then if you are interesting of communication between those 2 vlans you should implement an Intervlan Routing on a Layer 3 Switch or on a Router. For my lab, i used the Cisco 3560 Layer 3 Switch.

So lets suppose that the vlans design is something like that.

192.168.42.0 ( Data ) VLAN 10
192.168.45.0 ( Voice ) VLAN 20

First lets configure the Switch.

1.) #vlan database
vlan 10 name Data
vlan 20 name Voice

2.) (PBX Switch Port)

conf t
int fa0/1
switchport access vlan 20

3.) (IP Phones & PCs)

conf t
int fa0/2
switchport access vlan 10
switchport voice vlan 20

4.) (Manager PC)

conf t
int fa0/3
switchport access vlan 20

5.) (Stand Alone PCs)

conf t
int fa0/xx
switchport access vlan 10

6.) InterVlan Routing on the switch.

conft> ip routing
exit
#int vlan 10
confif>ip add 192.168.42.254 255.255.255.0
no shut
exit
#int vlan 20
confif>ip add 192.168.45.254 255.255.255.0
no shut
exit

So I have 2 directly connected networks on my switch (voice and data) which of course the are able to communicate each other.

Right now, you should configure the PCs to have as Default Gateway the interface on the switch of their respectively Vlan. (192.168.42.254)

The same, you should do for the Manager PC with the difference that it must have the voice vlan default gateway. (192.168.45.254).

In the Manager PC, you should also change the 46xx settings.
Find the vlan test and L2qvlan fields, and change them on those.
Set vlan test 0
Set L2QVLAN 20 ***(voice vlan)****
Don't forget to delete the ## symbols and of course to save the file.

Then before reboot the phones, you must statically administer them with all the Ip address, the voice vlan which it should be the vlan 2 and the vlantest = 0.

The reason i did that, was that the phones could not download the 46xx settings because by default they boot on the default vlan (vlan 0).

So what i did, was to put them on the voice vlan. After they reboot, they download the 46xx settings which i have previously changed.
So, even i have not test it out, i don't think they will lose their vlan settings on a Power Failure of the PBX.

An other thing is to put a default route on the PBX with an exit interface the Lan1 port.

Network :0.0.0.0 SubnetMask :0.0.0.0 Default Gateway :Blank Exit Interface : Lan1.

You should do that, because the IPO doesn't know where to forward the packets when it receives packets with a source address from the data vlan.

*** If you are looking for a DHCP Implemention guide, even though i have never done it before, don't forget to allow the DHCP Broadcasts (DHCPDISCOVER,DHCPREQUEST) to move through the Switch or Routers Interfaces.
You may have a DCHP Server on one LAN segment, and you also may want to allow this DHCP Server to receive and give DHCP 'informations' on an other LAN segment.
So you should give the <ip helper address ...DCHP IP...> in the interface of the second segment which is not physically communicate directly with the DHCP Server.

So that's all from me.

Good Luck and I hope that you find this guide helpful.

Thanks.
 
There is one thing in here you may want to change.

An other thing is to put a default route on the PBX with exit interface the Lan1 port.

Network :0.0.0.0 SubnetMasn :0.0.0.0
Default Gateway :Blank Exit Interface : Lan1

The default gateway should have your switch address in it. your IPo route should be
IP 0.0.0.0
subnet 0.0.0.0
Gateway 192.168.45.254
Dest LAN1

Kevin Wing
ACA- Implement IP Office
Carousel Industries
 
Thanks for the comment. I know that the correct configuration is just like you wrote even though i did not do it with that way(for some reason).
Anyway, for the guys who might haven't done this before, they should know that both configurations are good.

And something else. If the switch is connected with a router which give us a way out to the world, you may want to have a default route to forward packets on the router
eg, ip route 0.0.0.0 0.0.0.0 fa0/xx

Thanks.

 
hi all.

kwing you may can help me here.

Yesterday i just went in a flat network site with the same specifications i wrote above, in order to implement voice and data vlan.

everything worked fine but it happened something that i didn't really expected.

So when i was in the manager to configure it with the default quad zero route, i first programmed the IPO with the gateway IP address as you advised and not with the LAN1 interface.
I saved the config and then i reboot a phone to see if it will download from the TFTP the 46xx settings.
Instead of that the phone outputs was TFT TIME OUT/ERROR(something like that).
But when i erased from the config the gateway IP address and i put the Lan1 int as a gateway, then it just worked. The phone was correctly downloadig the 46xx settings.

I must say that it was something that i didn't expect because everything in th config, both in the switch and in the PBX was just correct.

So, any ideas?

Thanks.


 
I've seen that behaviour before...

You do need to set the destination on all routes, otherwise packets will get dropped.

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
on the first route you put in did it have the destination of LAN1 and the IP of the gateway? or just the IP?

Kevin Wing
ACA- Implement IP Office
Carousel Industries
 
it had both. I didn't try with just the IP of the gateway.
was that the problem?
 
I dont think so. i alway put them in like this.

Ip=0.0.0.0
Subnet 0.0.0.0
Gateway 192.168.1.1
Destination LAN1

Did you have any other routes that may have conflicted??

Kevin Wing
ACA- Implement IP Office
Carousel Industries
 
no other routes.
except from the already existent remote managers route.
it is strange, i know. anyway, as far as it works it's fine for me and my customer.but i would really like to know why that happened. I'll do it with that way again in the next installation,when ever it comes, just to see if it will happen again.

Thanks for the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top