Routing

last person joined: 2 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  EX4600: IRB round-trip time

    Posted 04-16-2015 23:10

    Hello *,

    anyone experiencing high round-trip times when configuring basic L2 local bridging + RVI on EX4600 (13.2X51-D30.4)?

    I use recommended ELS syntax for configuring vlan tagged ports and assigning IRB to vlans.

     

    L2 interface:
    set interfaces ge-0/0/1 description ANY-SERVER
    set interfaces ge-0/0/1 unit 0 family ethernet-switching interface-mode access
    set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members SOME-VLAN
    set interfaces ge-0/0/1 unit 0 family ethernet-switching storm-control default

    VLan and IRB:
    set interfaces irb unit 1234 family inet address XXX.XXX.XXX.XXX/XX
    set interfaces irb unit 1234 family inet6 address YYYY::/YY
    set vlans SOME-VLAN vlan-id 1234
    set vlans SOME-VLAN l3-interface irb.1234

    Pinging (ICMP echo) those IRBs on EX4600 through direct connected access/trunk ports within same vlan (bridge domain)  results in avarage roud-trip of 14-20ms. (CPU is idle, media does not matter- same on 1Gb copper as 10Gb optic)

    Normally non-ELS EX4500/4550 using RVI in form interface vlan have round-trip below 1ms.

    Anyone experienced similar behavior?


    I came around this KB https://kb.juniper.net/InfoCenter/index?page=content&id=KB27335 but 20ms is much higher as those round-trips on lower EX family



  • 2.  RE: EX4600: IRB round-trip time

     
    Posted 04-17-2015 13:40

    Hi,

     

    The article you have pasted says that it can be higher due to cpu usage. Have you tried to do icmp from host A connected to the devices to an host b on the otherside of the device ? What is the latency then.

     

    The article also states that

    Do not use ICMP-echo request to measure performance.

    The latency measure with an ICMP-echo request does not apply to line-rate performance or transit traffic that is hardware switched.
     
    I have checked the release notes of the 13.2X51-D35 and 14.1X53-D25 releases but, don't see a change in the notes about the high latency.
     
     
     


  • 3.  RE: EX4600: IRB round-trip time

    Posted 04-20-2015 07:08

    IRBs are working as expected and also E2E round-trips are fine.

     

    I just wondered that although ICMP echos exception traffic is handled by RE, i got 4 to 5 times the round-trip average on and IDLE EX4600 as compared to an idle EX4550-  OK, EX4600 is i386 and EX4550 is powerpc but in nearly complete idle a delta of times 4-5 comparing EX4600 and EX4550?!

     

    I dont use vlan L3-interfaces as performance indication- i just was surprised.

    I experienced that also on MX80- but OK, the EX4600 (ELS) is closer to those MX as to the original EX family.

     

     



  • 4.  RE: EX4600: IRB round-trip time
    Best Answer

     
    Posted 04-27-2015 04:41

    EX4600 is closer to QFX5100 than to MX/other EX.

     

    The latency is because Junos runs in a VM.

     

    Check this PR:

     

    https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR966905

     

    There are some improvements in 14.11X53-D25 and later releases.



    =====

    If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.



  • 5.  RE: EX4600: IRB round-trip time

    Posted 04-29-2015 03:40

    updating to version suggested will have to wait until maintenace window- but lets see if rt`s change then



  • 6.  RE: EX4600: IRB round-trip time

    Posted 12-22-2016 09:40

    Good evening everyone

    well version JUNOS Base OS Software Suite [14.1X53-D40.8] same problem

    irb round trip nighmare

     

    EX3300 directly conneted to a virtual chassis EX4600 with lacp link, pinging default gateway (EX4600 irb)

    EX3300>
    PING 172.17.169.225 (172.17.169.225): 56 data bytes
    64 bytes from 172.17.169.225: icmp_seq=0 ttl=64 time=30.237 ms
    64 bytes from 172.17.169.225: icmp_seq=1 ttl=64 time=19.656 ms
    64 bytes from 172.17.169.225: icmp_seq=2 ttl=64 time=31.374 ms
    64 bytes from 172.17.169.225: icmp_seq=3 ttl=64 time=14.048 ms
    64 bytes from 172.17.169.225: icmp_seq=4 ttl=64 time=23.723 ms
    64 bytes from 172.17.169.225: icmp_seq=5 ttl=64 time=11.387 ms
    64 bytes from 172.17.169.225: icmp_seq=6 ttl=64 time=30.875 ms
    64 bytes from 172.17.169.225: icmp_seq=7 ttl=64 time=16.032 ms
    64 bytes from 172.17.169.225: icmp_seq=8 ttl=64 time=15.145 ms
    64 bytes from 172.17.169.225: icmp_seq=9 ttl=64 time=24.664 ms
    ^C
    --- 172.17.169.225 ping statistics ---
    10 packets transmitted, 10 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 11.387/21.714/31.374/7.125 ms

     

    and routing engine is doing nothing

    EX4600> show chassis routing-engine
    Routing Engine status:
      Slot 0:
        Current state                  Backup
        Temperature                 41 degrees C / 105 degrees F
        CPU temperature             41 degrees C / 105 degrees F
        DRAM                      1953 MB
        Memory utilization          40 percent
        CPU utilization:
          User                       6 percent
          Background                 0 percent
          Kernel                     3 percent
          Interrupt                  0 percent
          Idle                      91 percent
        Model                          EX4600-40F
        Serial ID                      BUILTIN
        Uptime                         16 days, 2 hours, 55 minutes, 35 seconds
        Last reboot reason             0x2000:hypervisor reboot
        Load averages:                 1 minute   5 minute  15 minute
                                           0.08       0.11       0.08
    Routing Engine status:
      Slot 1:
        Current state                  Master
        Temperature                 36 degrees C / 96 degrees F
        CPU temperature             36 degrees C / 96 degrees F
        DRAM                      1953 MB
        Memory utilization          47 percent
        CPU utilization:
          User                       6 percent
          Background                 0 percent
          Kernel                     3 percent
          Interrupt                  1 percent
          Idle                      90 percent
        Model                          EX4600-40F
        Serial ID                      BUILTIN
        Uptime                         22 days, 3 hours, 16 minutes, 34 seconds
        Last reboot reason             0x1:power cycle/failure
        Load averages:                 1 minute   5 minute  15 minute
                                           0.13       0.15       0.13