Options

voice and data lan would like them to integrate

arcolinoarcolino Member Posts: 3 ■□□□□□□□□□
in CCNP Collaboration
I have a data lan on a 192.168.x.x network and a voice lan on a 172.20.x.x I would like to be on my data network and communicate with my voice network interface. I researched and came up with a default route? if so do I put a static route on both data and voice routers or just the data router? or do I need another command to make this work. Also I will not bog down my network when this happens? my friend mentioned setting a qos command? all help appreciated!
· Share on FacebookShare on Twitter

Comments

  • Options
    chmorinchmorin Member Posts: 1,446 ■■■■■□□□□□
    arcolino wrote: »
    I have a data lan on a 192.168.x.x network and a voice lan on a 172.20.x.x I would like to be on my data network and communicate with my voice network interface. I researched and came up with a default route? if so do I put a static route on both data and voice routers or just the data router? or do I need another command to make this work. Also I will not bog down my network when this happens? my friend mentioned setting a qos command? all help appreciated!

    Did I understand this correctly? Your network is like this:


    And you want to be able to access 172.20.1.1 (as an example) from 192.168.1.20 (as an example)? Well, this does not really have anything to do with Voice configurations and shouldn't bog down anything. All you need is a route of some kind on both gateways to identify each other. Static will do.

    In this example I used R3 as the management station with a default route to 192.168.1.1.
    R3#ping 192.168.1.1


Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 64/96/132 ms
R3#ping 172.20.1.1


Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.20.1.1, timeout is 2 seconds:
U.U.U
Success rate is 0 percent (0/5)
R3#

    R3 cannot reach the Voice Router, but can reach the data router. To fix this, we add static routes on the Data and Voice routers to each other 
    Data(config)#ip route 172.20.1.0 255.255.255.0 fa0/0
Data(config)#

    Voice(config)#ip route 192.168.1.0 255.255.255.0 fa0/0
Voice(config)#

    Now R3 can reach Data and Voice networks. 
    R3#ping 172.20.1.1


Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.20.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 64/135/220 ms
R3#

    Show routes on data/voice to confirm routing.
    Data#sho ip routeCodes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route


Gateway of last resort is not set


     172.20.0.0/24 is subnetted, 1 subnets
S       172.20.1.0 is directly connected, FastEthernet0/0
C    192.168.1.0/24 is directly connected, FastEthernet0/0
Data#

    Voice#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route


Gateway of last resort is not set


     172.20.0.0/24 is subnetted, 1 subnets
C       172.20.1.0 is directly connected, FastEthernet0/0
S    192.168.1.0/24 is directly connected, FastEthernet0/0
Voice#

    Week 1 networking stuff. Cakewalk. That is, if I understood your question correctly.
    Currently Pursuing
    WGU (BS in IT Network Administration) - 52%| CCIE:Voice Written - 0% (0/200 Hours)
    mikej412 wrote:
    Cisco Networking isn't just a job, it's a Lifestyle.
    · Share on FacebookShare on Twitter
  • Options
    tokhsstokhss Member Posts: 473
    Week 1 networking stuff. Cakewalk. That is, if I understood your question correctly.

    LOL.... u understood him wrong.. what he said was, HELLO WORLD!
    · Share on FacebookShare on Twitter
Sign In or Register to comment.