SRX Services Gateway
Highlighted
SRX Services Gateway

SRX 5800 cluster, slow speed due asymmetric traffic

Tuesday

 

изображение.png

 

Hello everyone,

 

We have 2 configured SRX5800  in cluster and 2 MX960, each MX has 2 uplinks. All are symmetric, without prepends, local prefference.

South side is without RETH interfaces, redandancy relies on OSPFv3.

North side has 2 redanduncy groups, acitve one on SRX-1. Load balancing is disabled.

So it means outgoing traffic always choose one interface, in our case it's ae1. When incoming traffic comes via ae3 we experience slow speed for TCP connections ~ 100Kb/s or even less for both ipv4 and ipv6 traffic.

ae3 interface is fine, if we make it preferable for outgoing traffic we get issues with slow speed on other interface.

Now to avoid slow speed I put metric on interface in OSPF. Can anyone advise where to look to identify an issue?

 

Version:

node0:
--------------------------------------------------------------------------
Hostname: SRX5800-1
Model: srx5800
JUNOS Software Release [12.3X48-D95.2]

node1:
--------------------------------------------------------------------------
Hostname: SRX5800-2
Model: srx5800
JUNOS Software Release [12.3X48-D95.2]

Inventrory of SRX:

Routing Engine 0 REV 12  SRX5k RE-13-20
CB 0 REV 05 710-024802 SRX5k SCB
CB 1 REV 09 710-024802 SRX5k SCB
CB 2 REV 05 710-024802 SRX5k SCB
FPC 0 REV 18 750-054877 SRX5k SPC II
FPC 1 REV 18 750-054877 SRX5k SPC II
FPC 8 REV 13 750-027945 SRX5k FIOC
FPC 9 REV 11 750-027945 SRX5k FIOC
FPC 10 REV 07 750-027945 SRX5k FIOC
FPC 11 REV 17 750-027945 SRX5k FIOC

 

Cluster config

 

control-link-recovery;
reth-count 5;
control-ports {
    fpc 1 port 0;
    fpc 13 port 0;
}
heartbeat-threshold 8;
redundancy-group 0 {
    node 0 priority 129;
    node 1 priority 128;
}
redundancy-group 1 {
    node 0 priority 129;
    node 1 priority 128;
    preempt;
}
redundancy-group 2 {
    node 0 priority 128;
    node 1 priority 129;
    preempt;
}

SRX OSPFv3

 

realm ipv4-unicast {
    area 0.0.0.0 {
        interface ae1.0;
        interface ae2.0;
        interface reth1.0 {
            passive;
        }
        interface ae3.0;
        interface ae4.0;
    }
}
reference-bandwidth 10g;
area 0.0.0.0 {
    interface ae1.0;
    interface ae2.0 {
        metric 10;
    }
    interface reth1.0 {
        passive;
    }
    interface ae3.0 {
        metric 10;
    }
    interface ae4.0 {
        metric 10;
    }
}

MX-1

realm ipv4-unicast {
    export ps-default-to-OSPF3;
    import ps46-DEFAULT-OSPF3-REJECT;
    area 0.0.0.0 {
        interface lo0.0 {
            passive;
        }
        interface ge-3/0/2.0 {
            passive;
        }
        interface ae3.0;
        interface xe-10/1/0.0;
        interface ae4.0;
        no-context-identifier-advertisement;
    }
}
export ps6-default-to-OSPF3;
import ps46-DEFAULT-OSPF3-REJECT;
reference-bandwidth 10g;
area 0.0.0.0 {
    interface lo0.0 {
        passive;
    }
    interface ae0.100;
    interface ge-3/0/2.0 {
        passive;
    }
    interface ae3.0 
    interface xe-10/1/0.0;
    interface ae4.0;
    no-context-identifier-advertisement;
}

MX-2

realm ipv4-unicast {
    inactive: traceoptions {
        file ospf3;
        flag all;
    }
    export ps-default-to-OSPF3;
    import ps46-DEFAULT-OSPF3-REJECT;
    area 0.0.0.0 {
        interface lo0.0 {
            passive;
        }
        interface xe-0/0/0.0;
        interface ae0.0 {
            metric 10;
        }
        interface ae1.0;
        interface xe-3/1/0.0;
        no-context-identifier-advertisement;
    }
}
inactive: traceoptions {
    file ospf3;
    flag all;
}
export default-to-OSPF3;
import ps46-DEFAULT-OSPF3-REJECT;
reference-bandwidth 10g;
area 0.0.0.0 {
    interface lo0.0 {
        passive;
    }
    interface xe-0/0/0.0;
    interface ae0.0 {
        metric 10;
    }
    interface ae1.0
    no-context-identifier-advertisement;
}