I will be honest and not pretend to know anything about frame relay's or T1 lines. But I do know how to assign ip addresses and understand what a subnet is. We have two Atlas 550's connected over a T1 line and on each atlas I have a VOIP device. Yes, I know I could use an E&M card for this but I have to use this VOIP device because of other reasons, it integrates directly with our studio communication system. The non-volatile battery in the Atlas' died and we lost the settings, we only use this system part of the year. The person who configured the system is no longer part of the company but he sent me a copy of a config file that was similar to what we do but the addresses are wrong. I think that I'm missing a static route setting in the adtran. For now I have the two Atlas 550's on my bench with a crossover cable connecting them. They are communicating and I can prove that. I have a PC on each end acting as the VOIP device. Here is my setup:
PC1 ( ip = 192.168.1.102, subnet 255.255.255.0, no gateway ) connected to Atlas1 ( ENO IP = 192.168.1.101, sub = 255.255.255.0, no GW ) crossover cable to Atlas2 ( ENO IP = 192.168.0.151, sub = 255.255.255.0, no GW ) connected to PC2 ( ip = 192.168.0.152, sub=255.255.255.0, no GW ). One each unit the PC is connected to its' Atlas' associated switch and the Atlas' Ethernet port is connected to the switch. I can ping the ENO IP from the PC on each frame. Each Atlas has a PPP network configured, the framer employee had an old file for that. So PPP network on Atlas1 is 192.168.2.1, 255.255.255.0, and on the Atlas2 it is 192.168.2.2, 255.255.255.0. I can ping from one Atlas to the other, using the internal ping command, i.e. I can ping 192.168.2.2 from 192.168.2.1 and vice-versa. I cannot ping from 192.168.1.102 to 192.168.0.152 or.151. I was told I need to have each ENO IP and their associated VOIP on a separate subnet from the other. If I set the PPPnetwork to the same subnet as the ENO IP then I lose the ability to ping the local ENO IP from the PC.
I wonder if I am missing a static route command. I tried some but none worked. I was told that I need each VOIP network on its' own subnet. I would prefer to have the VOIP devices on the same subnet but I can work around that.
Can anyone help me with this? I know this is simple but I am missing the way the ENO IP and the PPP networks relate.
Thanks!
Patrick from support solved this for me. The missing part was that I had not entered a gateway in my PC's ( acting as VOIP's ). So, for the Atlas1 side I have, 192.168.1.102, 255.255.255.0, 192.168.1.101. Atlas2 side, 192.168.0.152, 255.255.255.0, 192.168.0.151
Thanks again to all!
Hello johnvic ,
For traffic to flow between the two networks you will need a static route.
Try the following:
Atlas1:
ip route 192.168.0.0 255.255.255.0 192.168.2.1
Atlas 2:
ip route 192.168.1.0 255.255.255.0 192.168.2.2
If you can post your config I may be able to give you a better answer.
Thank you,
Thanks. I get to work in the morning, actually 3 AM. I'll try what you suggest and report on it. If I still have issues I'll post the configs.
I think what I did when I tried a static route I did the opposite. Atlas 1 192:168.1.0 to 192.168.2.1, and vice-versa. So it may be that I was thinking backwards.
I tried your suggestion. That did not help but I tried switching the addresses around a little and had a little success.I made the static routes as follows:
Atlas1:
ip route 192.168.0.0 255.255.255.0 192.168.2.2
Atlas2:
ip route 192.168.1.0 255.255.255.0 192.168.2.1
This allowed me to ping the opposite ENO IP from the Atlas itself. So I could ping the ENO IP of Atlas2 from Atlas1's Ping Utility. But what I cannot do is ping the external devices on the ethernet switch. I can ping the ENO IP from the attached PC but cannot ping the external PC from the internal PING utility. This is true on both Atlas'. If I put the two PC's on a dumb switch I can ping back and forth, of course I have to have 255.255.0.0 as a subnet on the PC for that. But my point is that the PC's are pingable.
I've attached the two config's.
Thanks agan for your help.
Patrick from support solved this for me. The missing part was that I had not entered a gateway in my PC's ( acting as VOIP's ). So, for the Atlas1 side I have, 192.168.1.102, 255.255.255.0, 192.168.1.101. Atlas2 side, 192.168.0.152, 255.255.255.0, 192.168.0.151
Thanks again to all!