Failed to reach remote network when i changed to direct connect lag

[wchan1]

I have 3 direct connect links. 2 of them bind into a port-channel to form LAG with AWS. Remain 1 has a l2tp tunnel on it and is working fine. the problem is, when i changed to LAG. i fail to reach x.x.x.x:50001(ip is pingable but tcp fail). i don't know the issue is bgp or l2tp or something else? i made a wireshark it seems i can't get syn reply from remote network. appreciate your help in advance.

[Georg Pauwen]

Hello,

you blanked out all interface descriptions, so it is very difficult to figure out which interface is connected to what. 

What is the active/working interface ?

Actually, what would really be helpful would be a simplified diagram showing both connections and corresponding interfaces. Also, in your original post you say:

--> ip is pingable but tcp fail

so I still do not know what the actual problem is. Keep in mind that we do not have any knowledge of your network other than what you tell us, so you have to kind of dumb it down in order for us to understand.

[wchan1]

Hi, Georg, 

I ran test days ago and confirm these outcomes.

case 1: 

With LAG formed, 

interface Port-channel1
no ip address
negotiation auto
!
interface Port-channel1.3282
encapsulation dot1Q 3282
ip address 10.266.121.209 255.255.255.252
!
interface Port-channel1.4017
encapsulation dot1Q 4017
ip address 169.254.227.13 255.255.255.252

the l2tp cannot form result in not reaching remote network

case2: 

when i spilt LAG into 2 individual lines, remote host is pingable but tcp 50001 fail.

So i have 1 question, does l2tp tunnel supports LAG? Thanks in advance

[wchan1]

problem fixed by moving the config from 2/0/x to 0/0/x. below is show inventory. it is weird that same config applied to both module, 1 work 1 fail.

NAME: "NIM subslot 0/0", DESCR: "Front Panel 3 ports Gigabitethernet Module"
PID: ISR4351-3x1GE , VID: V01 , SN:

NAME: "SM subslot 2/0", DESCR: "SM-X-6X1G"
PID: SM-X-6X1G , VID: V02 , SN: