Adtran P2P - Data/Voice configuration

[Anonymous]

I have two (2) 908e unit's P2P via T1 Circuit and would like to have some help with configuring correctly.

P2P - T1 circuit

7 IP Phones .49 subnet

7 Computers .48 subnet

GW - Data .48.1

GW - Voice 49.1

DNS - 48.8 and 5.2

Can anyone point me in the right direction on how can to configure my 908e so that they work together either on the same lan port or on their own port?

Thanks for your help.

[Anonymous]

Hello David,

Thank you for posting on our Support Forum.  In a point to point setup with TA 908es, you will need to do the following:

Main Location w/Internet Router (Firewall)

1.  Configure a default route in TA 908e Main to the firewall (0.0.0.0 0.0.0.0 X.X.48.1, where X.X.48.1 is the firewall LAN IP)

2.  Configure a T1 PPP interface with 255.255.255.252 (/30) subnet for the point to point between the TA 908es

3.  Configure the main location LAN IPs on TA 908e Main Ethernet interfaces

4.  Configure static routes to each remote location LAN network using TA 908e Remote PPP IP address as the next hop

5.  Configure static routes in the Firewall to each remote location subnet using TA 908e Main eth IP as the next hop

Remote Location

1.  Configure a default route in TA 908e Remote to TA 908e Main (0.0.0.0 0.0.0.0 Y.Y.Y.Y, where Y.Y.Y.Y is the PPP IP of TA 908e Main)

2.  Configure a T1 PPP interface with 255.255.255.252 (/30) subnet for the point to point between the TA 908es

3.  Configure the remote location LAN IPs on TA 908e Remote ethernet interfaces

NOTE: This is a routing application/environment so the Ethernet LAN subnets/networks will need to be unique on each TA 908e.  Using different routable networks will allow the TA 908e to use Quality of Service to ensure priority for voice traffic.

Once you get this setup and there is connectivity, we can work on the Quality of Service configuration.

Regards,

Geoff

ADTRAN Technical Support

[Anonymous]

Thanks for the reply; I appreciate the awesome help that the team have been
offering me to get this configured.

I have run into another problem, I cannot get a data link with the P2P T1. I
had Century Link come out and they found a bad port and moved the T1. I am
getting an uplink Green for the P2P T1, but for Data connection ADTRAN to
ADTRAN, I am getting a RED.

I have noticed that when I try to do a command line Cross-Connect, I get an
error that the interface does not exist.

Cross-Connect 1 T1 0/1 1 PPP 1

To resolve this, I have to go into the GUI and do a point and click to
activate the link. After doing this, I still cannot get the DATA link up.

I am using

1. 172.16.28.49 255.255.255.252 at the REMOTE
2. 172.16.28.50 255.255.255.252 at the MAIN SITE

I have ever since, removed the ADTRANS from the mounted areas and placed
them in my office. I have hence CRAFT into each, erased the STARTUP-CONFIG and
rebuilt, I am still unable to do the CROSS-CONNECT 1 t1 0/1 1 PPP 1 even after
created the INT and issuing the WRITE command to save the CONF.

I am going to issue these commands from the GUI and place the ADTRANS back
in place and try again.

Is there a way to BRIDGE the ADTRANS in my lab to test before putting back
in the field?

[Anonymous]

Hello Dave,

If you want to set the unit back to back, you will need a T1 cross-over cable to connect the T1 ports.  A T1 cross-over cable uses pins:

1-->4

2-->5

4-->1

5-->2

Note that an ethernet cross-over cable uses pins:

1-->3

2-->6

3-->1

6-->2

Thanks,

Geoff

ADTRAN Technical Support

[Anonymous]

T1 Crossover cable worked Great! Thanks Geof...

[Anonymous]

I have all the routes in the Adtran at this time.

ENG

0.0.0.0 0.0.0.0 172.16.28.50

MAIN

0.0.0.0 .0.0.0.0 172.16.48.1

192.168.101.48 255.255.255.0 172.16.28.49

I have both ADTRANS connected with the T1 Crossover. When I try to ping from MAIN Adtran to 172.16.48.1 I get a reply, when I connect to ENG Adtran and ping 172.16.48.1 I get no reply.

[Anonymous]

Hello Dave,

Make sure that you have routes in your firewall (172.16.48.1) back to the PPP network (172.16.28.48 /30) and any networks on the Eng (Remote TA 908e) LAN.  Use the Main TA 908e Eth IP Address as the next hop when setting up the static routes in the firewall.

Thanks,

Geoff

ADTRAN Technical Support

[Anonymous]

Thanks Geof, I have done all that I can do and I am still not able to Traceroute from one adtran to another to connected devices.

TRACEROUTE --> REMOTE to MAIN ... DIES

TRACEROUTE --> MAIN to REMOTE .. DIES

TRACEROUTE --> MAIN to a DEVICE that is attached works

TRACEROUTE --> REMOTE to a DEVICE that is attached works

THanks for your help.

[Anonymous]

Hello David,

Make sure that the only static route at the Remote side is the default route.  Also, you do not need static routes in the TA 908es for directly connected networks.  Double check the static routes and routing table and re-test.  If you are still having issues, send me the configs and I will look over them.

Thanks,

Geoff

ADTRAN Technical Support

[Anonymous]

I have verified all Routes. I am able to see the route through my firewall and when it hits the ADTRAN on the remote side it dies at the Adtran at the REMOTE SITE

Tracing route to 192.168.101.2 over a maximum of 30 hops

  1     1 ms    <1 ms     1 ms  172.16.48.246
  2     1 ms    <1 ms     1 ms  172.16.48.246
  3     3 ms     2 ms     3 ms  172.16.28.49
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.

Trace complete.

The same thing happens when I TRACE from the REMOTE side to the MAIN side.

It dies at  172.16.28.50

Thanks..

[Anonymous]

Hello Dave,

Double check the def routes for the PCs on the Remote Eng side.  Also check the DHCP information to ensure the PCs are getting the correct default route.  Once this is verified, you should have end to end connectivity.

To ensure that voice gets priority in the network, you can set up a basic QoS map for each TA 908e.  Here is what you can use to match SIP (26) and RTP (46):

qos map voip 10

  match dscp 26

  match dscp 46

  priority percent 75

Those commands are done in global configuration mode.  You can create the same map for each TA 908e.  After making the map, you will need to apply it to the PPP interface with this command:

  qos-policy out voip

Here is what the Main side PPP interface would look like:

interface ppp 1

  description p2p to ENG

  ip address  172.16.28.50  255.255.255.252

  qos-policy out voip

  no shutdown

  cross-connect 1 t1 0/1 1 ppp 1

Note:  You will want to check in your Firewall (172.168.48.1) and see if it can do QoS in the direction of the TA 908es.

Regards,

Geoff

ADTRAN Technical Support

[Anonymous]

Great, I will upload this as soon as we have our MPLS set with the previous routes.

[Anonymous]

Ok, I am totally confused at this point. I have taken the Adtrans an put them back out in the field and connected to the T1's. They link up, but now they do not talk, so the DATA light is red. The following LCP message shows in the DEBUG PPP Verbose.

1970.01.01 04:05:12 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Req ID=191 Len=10 M

AGIC(043fdf45)

1970.01.01 04:05:14 PPP.NEGOTIATION PPPrx[t1 0/1] LCP: Conf-Req ID=240 Len=27 M

RU(1520) MAGIC(413d853c) MRRU(1520) ED(3:00a0c871f4b5)

1970.01.01 04:05:14 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Rej ID=240 Len=8 MR

RU(1520)

1970.01.01 04:05:16 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Req ID=192 Len=10 M

AGIC(043fdf45)

1970.01.01 04:05:18 PPP.NEGOTIATION PPPrx[t1 0/1] LCP: Conf-Req ID=241 Len=27 M

RU(1520) MAGIC(413d853c) MRRU(1520) ED(3:00a0c871f4b5)

1970.01.01 04:05:18 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Rej ID=241 Len=8 MR

RU(1520)

1970.01.01 04:05:20 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Req ID=193 Len=10 M

AGIC(043fdf45)

1970.01.01 04:05:22 PPP.NEGOTIATION PPPrx[t1 0/1] LCP: Conf-Req ID=242 Len=27 M

RU(1520) MAGIC(413d853c) MRRU(1520) ED(3:00a0c871f4b5)

1970.01.01 04:05:22 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Rej ID=242 Len=8 MR

RU(1520)

1970.01.01 04:05:24 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Req ID=194 Len=10 M

AGIC(4e75de73)

1970.01.01 04:05:24 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Req ID=195 Len=10 M

AGIC(4e75de73)

1970.01.01 04:05:26 PPP.NEGOTIATION PPPrx[t1 0/1] LCP: Conf-Req ID=243 Len=27 M

RU(1520) MAGIC(413d853c) MRRU(1520) ED(3:00a0c871f4b5)

1970.01.01 04:05:26 PPP.NEGOTIATION PPPtx[t1 0/1] LCP: Conf-Rej ID=243 Len=8 MR

[Anonymous · Accepted solution]

Hello Dave,

It looks like the 1520 MTU is preventing PPP from coming up.  I believe the Eng side is set to 1520.  You will need to go into the ppp interface and change the MTU to 1500.

Regards,

Geoff

ADTRAN Technical Support

[Anonymous]

The connection is up and I am so happy!

The T1 was a mess. We had the CO come out and evaluate the circuit and there were some conflicts in the circuit. Once they were able to fix, I changed the MTU and BAMMM! We have DATA...

Thanks to all and GEO for the awesome help that they gave. I have gained so much knowlege from the JIVE and the support material and the awesome tech.

I will post my configuration so that if anyone else has this type of setup they casn see my configuration and maybe it will help.

Dave

[Anonymous]

Hello Dave,

I am glad to hear you are up and running!  Thanks again for contributing to our Support Forum.  Feel free to post your config.  I am going to mark this post as answered.

Regards,

Geoff

ADTRAN Technical Support

[renvar2112]

where is the config?

[Anonymous]

Sorry that I did not see this earlier. I will go ahead an post the config when I return the office. Sorry thought I had posted.