Cisco VOIP

405 pts.
Cisco 4506
Cisco VLAN
Cisco VoIP System
merging data and voice network

We hae seperate Data and voice network. For data network we have interface vlan 1 ip address in one core switch 4506. For voice network we have interface vlan 1

Now i am going to merge data and voice network. But vlan 1 on these core switches are different as mentioned above. i can add another network in core switch for voice traffic, but the voice management vlan is vlan 1 ( in voice core switch and the CCM and TFTP server for the ip phone image load and boot and Gateway router are lies in this vlan due to this i am not able to ping from my data network.

please suggest hopefully.  



Software/Hardware used:
CCM 4.1, Cisco 4506,

Answer Wiki

Thanks. We'll let you know when a new response is added.

Do I understand correctly that you have two separate switches where both switches are configured with Vlan1?

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Ekansh
    We have two seperate switches one 4506 switch for VOIP having vlan 1 ip add, another switch 4506 for data having vlan 1 ip add both r seperate networks. Now i want to merge it ? please suggest if any ?
    405 pointsBadges:
  • Snapper70
    What IOS version is on the 4506's? If they support routing, you can create a new vlan on each, and connect the two through a "separate" network. For instance, on each you have something like int gi 3/1 no switchport ip address on one, and the other You can then connect the two switches via crossover using these non-vlan-capable ports, and then use a routing protocol (i.e. EIGRP) on each. If you're not already running one, then add to each: ip routing router eigrp 1 network network no auto-summary You should then be able to link the 2 networks "transparently" - this assumes you are running a level of IOS on each that supports basic routing. If you DON'T have a version that supports it, then you can put static routing. on the voip one, add ip route; and on the data one add ip route If your network is actually more complex than this, you may have more work to do.
    920 pointsBadges:
  • Sixball
    Snapper has a great solution for routing, but first your overall configuration of VLANs seems a little off... Data and VOICE VLANs really should NOT be "merged". Data communications are a constant stream of bits, whereas Voice comes in chunks. Merging them will almost completely kill your voice call quality. A better solutions would be to keep them on seperate VLANS (VLAN1 for data, and say VLAN 5 for voice - Cisco best practices states that a lower VLAN number for voice is better, but i digress) Your current configuration of "Interface VLAN 1" w/ 2 different VLAN ID's on it is really unusual and seems to be causing a few of your issues. I would suggest creating a VLAN 5 (Name Voice) and put the Voice VLAN IP on "Interface VLAN 5". Once the data and voice are segregated, then go with Snappers suggestion of settin up trunking between devices and using EIGRP if needed (theyre both cisco, so why not?) Put BOTH VLANS on BOTH swithes, trunk between them, and enable a bit of QOS to prioritize VLAN 5 (Voice) traffic over the data traffic and you should see a marked difference In summary: Data: VLAN 1 -, Voice: VLAN 5 - Put Both VLANs on BOTH switches, then trunk between them - your 4500's are more than capable of handling this config..
    8,705 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: