Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 3 subscribers
  • Views 2867 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RED 50 3G/UMTS FAILOVER

Andronix

Hello,

 

I have a question about  3G/UMTS Failover with UTM_SG_330 WAN2 in the scenario no.3.

 

 

#Scenario no.1:

The RED 50 is online via RED_WAN1 and connects to UTM_WAN1 (1st UTM Hostname).

# Scenario no.2:

RED_WAN1 (uplink1) is down

The RED_WAN2 (uplink2) does not exist.

Normally, RED 50 will establish connection between UTM_WAN1 and RED_3G_UMTS.


# Scenario no.3:

3G / UMTS is UP but can not reach the IP address of UTM_WAN1 (1st UTM Hostname), this is due to a constraint at the ISP level.


The UTM_WAN2 will be used if the UTM_WAN1 is unreachable.

The IP address of 3G / UMTS can ping ip of the UTM_WAN2 (2nd UTM Hostname) but during our test the RED50 does not establish a connection between UTM_WAN2 and RED_3G_UMTS.

Please find below the 3G/UMTS configuration.


As i see during from previous test, 3G/UTMS Failover works with this configuration  if only the IP of 3G could reach both the two UTM Hostnames.
The 3G/UMTS failover fails because the 3G can only reach the 2nd UTM Hostname. How do we fix it ?.

Thanks,



This thread was automatically locked due to age.
Parents
  • 0

    Hello  

    What do you see on the LCD display when the 3G/UMTS connection tries to connect to 2nd Hostname for UTM? Further, do you see anything coming up in RED logs on the UTM? Or if you do a packet capture for TCP Port 3400 on UTM, do you see any traffic coming from RED50? In packet capture, you will need to ignore the traffic going to the RED provisioning server.

    Regards

    Jaydeep

Reply
  • 0

    Hello  

    What do you see on the LCD display when the 3G/UMTS connection tries to connect to 2nd Hostname for UTM? Further, do you see anything coming up in RED logs on the UTM? Or if you do a packet capture for TCP Port 3400 on UTM, do you see any traffic coming from RED50? In packet capture, you will need to ignore the traffic going to the RED provisioning server.

    Regards

    Jaydeep

Children
  • 0 in reply to Jaydeep

    Hello Jaydeep,

    Jaydeep said:
    What do you see on the LCD display when the 3G/UMTS connection tries to connect to 2nd Hostname for UTM?


    try wan1

    try umts
    no connection to UT

    >reboot
    shutting down

     

    Jaydeep said:
    Further, do you see anything coming up in RED logs on the UTM?

    =>
    #The last logs show the deconnection of RED when RED_WAN1 is down.


    <M> hff-sph-prim:/var/log # tail -f red.log | grep A3400EA5XXXXXXX
    2019:09:10-14:53:45 hff-sph-prim-1 red_server[22207]: A3400EA5XXXXXXX: command 'PORTSTATE 1E04,1004,1004,1004,1004'
    2019:09:10-14:53:45 hff-sph-prim-1 red_server[22207]: A3400EA5XXXXXXX: PORTSTATE LAN1: Down,LAN2: Down,LAN3: Down,LAN4: Down
    2019:09:10-14:53:45 hff-sph-prim-1 red_server[22207]: A3400EA5XXXXXXX: command 'PING 0 uplink=WAN uplinkstate=0'
    2019:09:10-14:53:45 hff-sph-prim-1 red_server[22207]: A3400EA5XXXXXXX: PING remote_tx=0 local_rx=0 diff=0
    2019:09:10-14:53:45 hff-sph-prim-1 red_server[22207]: A3400EA5XXXXXXX: PONG local_tx=0
    2019:09:10-14:54:16 hff-sph-prim-1 red_server[22207]: A3400EA5XXXXXXX: No ping for 30 seconds, exiting.
    2019:09:10-14:54:16 hff-sph-prim-1 red_server[22207]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="A3400EA5XXXXXXX" forced="0"
    2019:09:10-14:54:16 hff-sph-prim-1 red_server[22207]: A3400EA5XXXXXXX is disconnected.

    Jaydeep said:
    Or if you do a packet capture for TCP Port 3400 on UTM, do you see any traffic coming from RED50?

    #Packet capture
    NOTE:
    -UTM_WAN1 = 10.168.71.66 (UTM eth5.402)
    -UTM_WAN2 = 197.158.x.x  (UTM eth4.98)
    -RED_WAN1 = 41.204.x.x
    -RED_3G = 10.193.183.181

    <M> hff-sph-prim:/ # tcpdump -i eth5.402 port 3400 and host 41.204.x.x -n
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth5.402, link-type EN10MB (Ethernet), capture size 65535 bytes
    14:53:45.051468 IP 41.204.x.x.34619 > 10.168.71.66.3400: Flags [P.], seq 326149310:326149374, ack 2896907112, win 1187, length 64
    14:53:45.051504 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [.], ack 64, win 283, length 0
    14:53:45.093877 IP 41.204.x.x.34619 > 10.168.71.66.3400: Flags [P.], seq 64:125, ack 1, win 1187, length 61
    14:53:45.093915 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [.], ack 125, win 283, length 0
    14:53:45.166125 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [P.], seq 1:32, ack 125, win 283, length 31
    14:53:45.178830 IP 41.204.x.x.34619 > 10.168.71.66.3400: Flags [.], ack 32, win 1187, length 0
    #When RED_WAN1 is down
    14:54:16.327651 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [P.], seq 32:63, ack 125, win 283, length 31
    14:54:16.329658 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [F.], seq 63, ack 125, win 283, length 0
    14:54:16.375845 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [F.], seq 63, ack 125, win 283, length 0
    14:54:16.599833 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [FP.], seq 32:63, ack 125, win 283, length 31
    14:54:17.047834 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [FP.], seq 32:63, ack 125, win 283, length 31
    14:54:17.943850 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [FP.], seq 32:63, ack 125, win 283, length 31
    14:54:19.739834 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [FP.], seq 32:63, ack 125, win 283, length 31
    14:54:23.331843 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [FP.], seq 32:63, ack 125, win 283, length 31
    14:54:30.519842 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [FP.], seq 32:63, ack 125, win 283, length 31
    14:54:37.699837 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [FP.], seq 32:63, ack 125, win 283, length 31
    14:54:44.883848 IP 10.168.71.66.3400 > 41.204.x.x.34619: Flags [FP.], seq 32:63, ack 125, win 283, length 31


    <M> hff-sph-prim:/ # tcpdump -i eth5.402 port 3400 and host 10.193.183.131 -n
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth5.402, link-type EN10MB (Ethernet), capture size 65535 bytes
    ^C
    0 packets captured
    2 packets received by filter
    0 packets dropped by kernel

    I don't see any traffic when  the 3G/UMTS connection tries to connect to 2nd Hostname .
    <M> hff-sph-prim:/ # tcpdump -i eth4.98 port 3400 and host 10.193.183.131 -n
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth4.98, link-type EN10MB (Ethernet), capture size 65535 bytes
    ^C
    0 packets captured
    8 packets received by filter
    0 packets dropped by kernel

    Regards,

Unfiltered HTML