Routing

 View Only
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.
Expand all | Collapse all

Check the ms-x/x/x.x interface on service pic 2g at vMX.

  • 1.  Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-13-2020 23:54
    Hi,

    I would like to have my test environment to using an advanced NAT feature, which it is requires using MS-MPC. I ran the vMX and setup with the following FPCs set.

    {master}
    lab@lab-r2-re0> show chassis fpc pic-status
    Slot 0   Online       MS-MPC
      PIC 0  Online       Virtual
      PIC 2  Online       MS-MPC-PIC
    Slot 1   Online       Virtual FPC
      PIC 0  Online       Virtual
    
    {master}
    lab@lab-r2-re0> show chassis hardware
    Hardware inventory:
    Item             Version  Part number  Serial number     Description
    Chassis                                VM5FD19DC4F6      VMX
    Midplane
    Routing Engine 0                                         RE-VMX
    Routing Engine 1                                         RE-VMX
    CB 0                                                     VMX SCB
    CB 1                                                     VMX SCB
    FPC 0                                                    MS-MPC
      CPU            Rev. 1.0 RIOT-LITE    BUILTIN
      MIC 0                                                  Virtual
        PIC 0                 BUILTIN      BUILTIN           Virtual
      MIC 1                                                  MS-MPC-PIC
        PIC 2                 BUILTIN      BUILTIN           MS-MPC-PIC
    FPC 1                                                    Virtual FPC
      CPU            Rev. 1.0 RIOT-LITE    BUILTIN
      MIC 0                                                  Virtual
        PIC 0                 BUILTIN      BUILTIN           Virtual
    ​

    I also set up the FPCs using following chassis configuration as follow.

    {master}
    lab@lab-r2-re0> show configuration chassis
    redundancy {
        routing-engine 0 master;
        routing-engine 1 backup;
        graceful-switchover;
    }
    fpc 0 {
        lite-mode;
    }
    fpc 1 {
        lite-mode;
    }
    network-services enhanced-ip;​


    Just curious. I don't think I configured well on NAT, but at least I would know the cause. I need to check if the MS-MPC is running correctly. It should able to use the ms interface as well.

    {master}
    lab@lab-r2-re0> show interfaces terse | match ms
    mams-0/2/0              up    up
    ms-0/2/0                up    down
    ms-0/2/0.0              up    down inet
    ms-0/2/0.1              up    down inet
    ms-0/2/0.2              up    down inet
    ms-0/2/0.64000          up    down inet
    


    Any idea how to check the ms interface as working?



  • 2.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-14-2020 06:28
    Which version of vMX do you using?


  • 3.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-14-2020 11:32
    Hi SongYue,

    I'm using 18.2R3.4.  I found something else, that the ms interfaces didn't show up stable when frequently I check them by "show interface terse | match ms". On certain seconds, the are gone. And next to those seconds, the interfaces are reappear. Maybe there were a problem during the setup on vFPC. Any ideas?


  • 4.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.
    Best Answer

    Posted 12-15-2020 10:02
    Please increase the number of CPUs and the memory size for the vfpc VM.


  • 5.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-21-2020 08:56

    Hi gedebook,

    May i know whether u are success to simulate CGNAT using vMX? Currently i'm try but it still not work.

    Thanks and appreciate your feedback




  • 6.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 05:14

    It is working. It is changing the state from ms interface down to up, but just appear once and it is gone. Maybe it is requiring a lot of resources. I need some time to test it further. Can't say straightly that I have done it. I'll came back later after success the test.




  • 7.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 05:34

    Hi,

    In my case the vMS-MPC is up but CGNAT not function (I'm test in EVE-NG / PNETLAB). Even i'm use same config that working on MX480 with MS-MPC. Hopefully someone here can share experience whether vMS-MPC is  can do CGNAT or not to prevent me from wasting time do a thing that will not work.

    [edit]
    root# run show version
    Model: vmx
    Junos: 18.3R3.8

    [edit]
    root# run show interfaces terse | match ms
    mams-0/2/0 up up
    mams-0/2/0.1 up up ams --> ams0.1
    mams-0/2/0.2 up up ams --> ams0.2
    mams-0/2/0.64000 up up ams --> ams0.64000
    ms-0/2/0 up up
    ms-0/2/0.0 up up inet
    ms-0/2/0.64001 up up inet
    ams0 up up
    ams0.1 up up inet
    ams0.2 up up inet
    ams0.64000 up up inet

    [edit]
    root# run show services nat statistics
    Interface: ms-0/2/0

    Session statistics

    Session statistics
    Total Session Interest events :83825
    Total Session Create events :0
    Total Session Destroy events :83821
    Total Session Pub Req events :0
    Total Session Accepts :0
    Total Session Discards :83825
    Total Session Ignores :0
    Control Session Not Xlated Child Sess Ignored :0
    Total Session Time events :0
    Session interest thru pub event :0
    ALG Session interest :0
    ALG Session Create :0
    Total Session close :0
    Packet Dst in NAT route :0
    Packet drop in backup state :83825




  • 8.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-06-2021 14:11
    Hi kronicklez,

    I follow up your version but it is turned out into unresponsive fpc.

    exercise@exercise-r1-re0> show chassis hardware
    Jan 06 22:59:45
    Hardware inventory:
    Item             Version  Part number  Serial number     Description
    Chassis                                VM5FE96091F8      VMX
    Midplane
    Routing Engine 0                                         RE-VMX
    CB 0                                                     VMX SCB
    CB 1                                                     VMX SCB
    FPC 0                                                    MS-MPC
      CPU
    
    {master}
    exercise@exercise-r1-re0> show chassis fpc
    Jan 06 22:59:46
                         Temp  CPU Utilization (%)   CPU Utilization (%)  Memory    Utilization (%)
    Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
      0  Offline         ---Unresponsive---
      1  Empty
      2  Empty
      3  Empty
      4  Empty
      5  Empty
      6  Empty
      7  Empty
      8  Empty
      9  Empty
     10  Empty
     11  Empty
    
    {master}
    exercise@exercise-r1-re0> show version | no-more
    Jan 06 22:59:49
    Hostname: exercise-r1-re0
    Model: vmx
    Junos: 18.3R3.8
    JUNOS OS Kernel 64-bit  [20190907.2386fa2_builder_stable_11]
    JUNOS OS libs [20190907.2386fa2_builder_stable_11]
    JUNOS OS runtime [20190907.2386fa2_builder_stable_11]
    JUNOS OS time zone information [20190907.2386fa2_builder_stable_11]
    JUNOS network stack and utilities [20190926.144104_builder_junos_183_r3]
    JUNOS libs [20190926.144104_builder_junos_183_r3]
    JUNOS OS libs compat32 [20190907.2386fa2_builder_stable_11]
    JUNOS OS 32-bit compatibility [20190907.2386fa2_builder_stable_11]
    JUNOS libs compat32 [20190926.144104_builder_junos_183_r3]
    JUNOS runtime [20190926.144104_builder_junos_183_r3]
    JUNOS Packet Forwarding Engine Simulation Package [20190926.144104_builder_junos_183_r3]
    JUNOS sflow mx [20190926.144104_builder_junos_183_r3]
    JUNOS py extensions [20190926.144104_builder_junos_183_r3]
    JUNOS py base [20190926.144104_builder_junos_183_r3]
    JUNOS OS vmguest [20190907.2386fa2_builder_stable_11]
    JUNOS OS crypto [20190907.2386fa2_builder_stable_11]
    JUNOS na telemetry [18.3R3.8]
    JUNOS mx libs compat32 [20190926.144104_builder_junos_183_r3]
    JUNOS mx runtime [20190926.144104_builder_junos_183_r3]
    JUNOS common platform support [20190926.144104_builder_junos_183_r3]
    JUNOS Openconfig [18.3R3.8]
    JUNOS mtx network modules [20190926.144104_builder_junos_183_r3]
    JUNOS modules [20190926.144104_builder_junos_183_r3]
    JUNOS mx modules [20190926.144104_builder_junos_183_r3]
    JUNOS mx libs [20190926.144104_builder_junos_183_r3]
    JUNOS mtx Data Plane Crypto Support [20190926.144104_builder_junos_183_r3]
    JUNOS daemons [20190926.144104_builder_junos_183_r3]
    JUNOS mx daemons [20190926.144104_builder_junos_183_r3]
    JUNOS Simulation Linux Package [20190926.144104_builder_junos_183_r3]
    JUNOS Simulation Package [20190926.144104_builder_junos_183_r3]
    JUNOS Services URL Filter package [20190926.144104_builder_junos_183_r3]
    JUNOS Services TLB Service PIC package [20190926.144104_builder_junos_183_r3]
    JUNOS Services Telemetry [20190926.144104_builder_junos_183_r3]
    JUNOS Services SSL [20190926.144104_builder_junos_183_r3]
    JUNOS Services SOFTWIRE [20190926.144104_builder_junos_183_r3]
    JUNOS Services Stateful Firewall [20190926.144104_builder_junos_183_r3]
    JUNOS Services RPM [20190926.144104_builder_junos_183_r3]
    JUNOS Services PCEF package [20190926.144104_builder_junos_183_r3]
    JUNOS Services NAT [20190926.144104_builder_junos_183_r3]
    JUNOS Services Mobile Subscriber Service Container package [20190926.144104_builder_junos_183_r3]
    JUNOS Services MobileNext Software package [20190926.144104_builder_junos_183_r3]
    JUNOS Services Logging Report Framework package [20190926.144104_builder_junos_183_r3]
    JUNOS Services LL-PDF Container package [20190926.144104_builder_junos_183_r3]
    JUNOS Services Jflow Container package [20190926.144104_builder_junos_183_r3]
    JUNOS Services Deep Packet Inspection package [20190926.144104_builder_junos_183_r3]
    JUNOS Services IPSec [20190926.144104_builder_junos_183_r3]
    JUNOS Services IDS [20190926.144104_builder_junos_183_r3]
    JUNOS IDP Services [20190926.144104_builder_junos_183_r3]
    JUNOS Services HTTP Content Management package [20190926.144104_builder_junos_183_r3]
    JUNOS Services Flowd MS-MPC Software package [20190926.144104_builder_junos_183_r3]
    JUNOS Services Crypto [20190926.144104_builder_junos_183_r3]
    JUNOS Services Captive Portal and Content Delivery Container package [20190926.144104_builder_junos_183_r3]
    JUNOS Services COS [20190926.144104_builder_junos_183_r3]
    JUNOS AppId Services [20190926.144104_builder_junos_183_r3]
    JUNOS Services Application Level Gateways [20190926.144104_builder_junos_183_r3]
    JUNOS Services AACL Container package [20190926.144104_builder_junos_183_r3]
    JUNOS Extension Toolkit [20190926.144104_builder_junos_183_r3]
    JUNOS J-Insight [20190926.144104_builder_junos_183_r3]
    JUNOS Online Documentation [20190926.144104_builder_junos_183_r3]
    JUNOS jail runtime [20190907.2386fa2_builder_stable_11]
    ​

    Just curious, did anybody know the following probe is run just normally for latency between vcp em1.0 interface and vfp service-pic-2g em1.0 interface? Do you have any information, what minimum number of millisecond latency for running the vfp normally? I make a simulation only running two nodes, 1 vcp and1 vfp.

    {master}
    exercise@exercise-r1-re0> show arp interface em1.0
    Jan 06 23:06:33
    MAC Address       Address         Name                      Interface               Flags
    50:01:00:06:00:01 128.0.0.16      fpc0                      em1.0                   none
    50:01:00:06:00:01 128.0.3.16      fpc0.pic2                 em1.0                   none
    Total entries: 2
    
    {master}
    exercise@exercise-r1-re0> ping rapid count 50 interface em1.0 128.0.0.16
    Jan 06 23:06:35
    PING 128.0.0.16 (128.0.0.16): 56 data bytes
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    --- 128.0.0.16 ping statistics ---
    50 packets transmitted, 50 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 2.540/3.321/4.803/0.708 ms
    
    {master}
    exercise@exercise-r1-re0> ping rapid count 50 interface em1.0 128.0.3.16
    Jan 06 23:06:38
    PING 128.0.3.16 (128.0.3.16): 56 data bytes
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    --- 128.0.3.16 ping statistics ---
    50 packets transmitted, 50 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 2.614/3.325/4.895/0.731 ms
    ​

    I'm going through the test to version 19.4R1.10.


  • 9.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 05:54

    I catch this when investigating the fpc. The fpc for servicepic-2g didn't established well when I checked "show chassis fpc" regularly at slot 0.

    ---(refreshed at 2020-12-23 17:48:20 WIB)---
                         Temp  CPU Utilization (%)   CPU Utilization (%)  Memory    Utilization (%)
    Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
      0  Present          Testing
      1  Online           Testing  46         0       65     47     28    511        32          0
      2  Empty
      3  Empty
      4  Empty
      5  Empty
      6  Empty
      7  Empty
      8  Empty
      9  Empty
     10  Empty
     11  Empty
    ---(refreshed at 2020-12-23 17:48:25 WIB)---
                         Temp  CPU Utilization (%)   CPU Utilization (%)  Memory    Utilization (%)
    Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
      0  Empty
      1  Online           Testing  46         0       65     47     28    511        32          0
      2  Empty
      3  Empty
      4  Empty
      5  Empty
      6  Empty
      7  Empty
      8  Empty
      9  Empty
     10  Empty
     11  Empty
    

    Perhaps the vMX version that I tested isn't the best for picking the vMS-MPC case. Any advice? Thanks.

    {master}
    exerciserad@exercise-r1-re0> show version | no-more
    Dec 23 17:53:17
    Hostname: exercise-r1-re0
    Model: vmx
    Junos: 18.2R3.4
    JUNOS OS Kernel 64-bit  [20190605.30b921f_builder_stable_11]
    JUNOS OS libs [20190605.30b921f_builder_stable_11]
    JUNOS OS runtime [20190605.30b921f_builder_stable_11]
    JUNOS OS time zone information [20190605.30b921f_builder_stable_11]
    JUNOS network stack and utilities [20190620.215446_builder_junos_182_r3]
    JUNOS libs [20190620.215446_builder_junos_182_r3]
    JUNOS OS libs compat32 [20190605.30b921f_builder_stable_11]
    JUNOS OS 32-bit compatibility [20190605.30b921f_builder_stable_11]
    JUNOS libs compat32 [20190620.215446_builder_junos_182_r3]
    JUNOS runtime [20190620.215446_builder_junos_182_r3]
    JUNOS Packet Forwarding Engine Simulation Package [20190620.215446_builder_junos_182_r3]
    JUNOS sflow mx [20190620.215446_builder_junos_182_r3]
    JUNOS py extensions [20190620.215446_builder_junos_182_r3]
    JUNOS py base [20190620.215446_builder_junos_182_r3]
    JUNOS OS vmguest [20190605.30b921f_builder_stable_11]
    JUNOS OS crypto [20190605.30b921f_builder_stable_11]
    JUNOS mx libs compat32 [20190620.215446_builder_junos_182_r3]
    JUNOS mx runtime [20190620.215446_builder_junos_182_r3]
    JUNOS common platform support [20190620.215446_builder_junos_182_r3]
    JUNOS mtx network modules [20190620.215446_builder_junos_182_r3]
    JUNOS modules [20190620.215446_builder_junos_182_r3]
    JUNOS mx modules [20190620.215446_builder_junos_182_r3]
    JUNOS mx libs [20190620.215446_builder_junos_182_r3]
    JUNOS mtx Data Plane Crypto Support [20190620.215446_builder_junos_182_r3]
    JUNOS daemons [20190620.215446_builder_junos_182_r3]
    JUNOS mx daemons [20190620.215446_builder_junos_182_r3]
    JUNOS Simulation Linux Package [20190620.215446_builder_junos_182_r3]
    JUNOS Simulation Package [20190620.215446_builder_junos_182_r3]
    JUNOS Services URL Filter package [20190620.215446_builder_junos_182_r3]
    JUNOS Services TLB Service PIC package [20190620.215446_builder_junos_182_r3]
    JUNOS Services Telemetry [20190620.215446_builder_junos_182_r3]
    JUNOS Services SSL [20190620.215446_builder_junos_182_r3]
    JUNOS Services SOFTWIRE [20190620.215446_builder_junos_182_r3]
    JUNOS Services Stateful Firewall [20190620.215446_builder_junos_182_r3]
    JUNOS Services RPM [20190620.215446_builder_junos_182_r3]
    JUNOS Services PCEF package [20190620.215446_builder_junos_182_r3]
    JUNOS Services NAT [20190620.215446_builder_junos_182_r3]
    JUNOS Services Mobile Subscriber Service Container package [20190620.215446_builder_junos_182_r3]
    JUNOS Services MobileNext Software package [20190620.215446_builder_junos_182_r3]
    JUNOS Services Logging Report Framework package [20190620.215446_builder_junos_182_r3]
    JUNOS Services LL-PDF Container package [20190620.215446_builder_junos_182_r3]
    JUNOS Services Jflow Container package [20190620.215446_builder_junos_182_r3]
    JUNOS Services Deep Packet Inspection package [20190620.215446_builder_junos_182_r3]
    JUNOS Services IPSec [20190620.215446_builder_junos_182_r3]
    JUNOS Services IDS [20190620.215446_builder_junos_182_r3]
    JUNOS IDP Services [20190620.215446_builder_junos_182_r3]
    JUNOS Services HTTP Content Management package [20190620.215446_builder_junos_182_r3]
    JUNOS Services Flowd MS-MPC Software package [20190620.215446_builder_junos_182_r3]
    JUNOS Services Crypto [20190620.215446_builder_junos_182_r3]
    JUNOS Services Captive Portal and Content Delivery Container package [20190620.215446_builder_junos_182_r3]
    JUNOS Services COS [20190620.215446_builder_junos_182_r3]
    JUNOS AppId Services [20190620.215446_builder_junos_182_r3]
    JUNOS Services Application Level Gateways [20190620.215446_builder_junos_182_r3]
    JUNOS Services AACL Container package [20190620.215446_builder_junos_182_r3]
    JUNOS Extension Toolkit [20190620.215446_builder_junos_182_r3]
    JUNOS J-Insight [20190620.215446_builder_junos_182_r3]
    JUNOS Online Documentation [20190620.215446_builder_junos_182_r3]
    JUNOS jail runtime [20190605.30b921f_builder_stable_11]



  • 10.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 06:26

    Hi,

    If u used EVE-NG / PNETLAB then please allocate enough vCPU and RAM as per below snapshot.

    Thanks




  • 11.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 07:17

    It still not came up online. I am using EVE-NG environment. Perhaps I need to use another version of vMX like yours. Although, I need some time. Thanks.




  • 12.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 07:21

    Hi,

    Please make sure your VFP using below command on qemu.

    -machine type=pc-1.0,accel=kvm -serial mon:stdio -nographic -cpu host

    Thanks




  • 13.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 07:38

    root> show chassis fpc    
                         Temp  CPU Utilization (%)   CPU Utilization (%)  Memory    Utilization (%)
    Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
      0  Online           Testing 100         0       99     87     49    2047        7          0
      1  Empty           
      2  Empty           
      3  Empty           
      4  Empty           
      5  Empty           
      6  Empty           
      7  Empty           
      8  Empty           
      9  Empty           
     10  Empty           
     11  Empty           
    
    root> show chassis hardware 
    Hardware inventory:
    Item             Version  Part number  Serial number     Description
    Chassis                                VM5FE336D263      VMX
    Midplane        
    Routing Engine 0                                         RE-VMX
    CB 0                                                     VMX SCB
    FPC 0                                                    MS-MPC
      CPU            Rev. 1.0 RIOT-PERF    BUILTIN          
      MIC 0                                                  Virtual
        PIC 0                 BUILTIN      BUILTIN           Virtual
      MIC 1                                                  MS-MPC-PIC
        PIC 2                 BUILTIN      BUILTIN           MS-MPC-PIC
    root> show interfaces terse 
    Interface               Admin Link Proto    Local                 Remote
    ge-0/0/0                up    up
    ge-0/0/0.16386          up    up  
    pfe-0/0/0               up    up
    pfe-0/0/0.16383         up    up   inet    
                                       inet6   
    pfh-0/0/0               up    up
    pfh-0/0/0.16383         up    up   inet    
    pfh-0/0/0.16384         up    up   inet    
    ge-0/0/1                up    up
    ge-0/0/1.16386          up    up  
    ge-0/0/2                up    up
    ge-0/0/2.16386          up    up  
    mams-0/2/0              up    up
    ms-0/2/0                up    up
    pc-0/2/0                up    up
    pc-0/2/0.16383          up    up   inet    
    pc-0/2/0.16384          up    up   inet     20.0.0.1            --> 20.0.0.18
    cbp0                    up    up
    demux0                  up    up
    dsc                     up    up
    em1                     up    up
    em1.0                   up    up   inet     10.0.0.4/8      
                                                128.0.0.1/2     
                                                128.0.0.4/2     
                                       inet6    fe80::5200:ff:fe03:1/64
                                                fec0::a:0:0:4/64
                                       tnp      0x4             
    esi                     up    up
    fti0                    up    up
    fti1                    up    up
    fti2                    up    up
    fti3                    up    up
    fti4                    up    up
    fti5                    up    up
    fti6                    up    up
    fti7                    up    up
    fxp0                    up    up
    fxp0.0                  up    up   inet     192.168.1.6/24  
    gre                     up    up
    ipip                    up    up
    irb                     up    up
    jsrv                    up    up
    jsrv.1                  up    up   inet     128.0.0.127/2   
    lo0                     up    up
    lo0.16384               up    up   inet     127.0.0.1           --> 0/0
    lo0.16385               up    up   inet    
    lsi                     up    up
    mif                     up    up
    mtun                    up    up
    pimd                    up    up
    pime                    up    up
    pip0                    up    up
    pp0                     up    up
    rbeb                    up    up
    tap                     up    up
    vtep                    up    up



  • 14.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 12:01

    Did i make it correctly?

    {master}
    exerciserad@exercise-r1-re0> show chassis fpc | refresh 5 | match "0|1"
    ---(refreshed at 2020-12-23 23:53:12 WIB)---
    Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
      0  Empty
      1  Online           Testing  82         0       51     58     57    511        32          0
     10  Empty
     11  Empty
    ---(refreshed at 2020-12-23 23:53:17 WIB)---
    Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
      0  Empty
      1  Online           Testing 100         0       59     59     57    511        32          0
     10  Empty
     11  Empty
    ---(*more 100%)---[abort]
    
    



  • 15.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 12-23-2020 20:50

    Hi,

    Do u already try with other version?

    Thanks




  • 16.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-04-2021 23:29
    Hi SongYue,

    Which JUNOS version you used? And which eve-ng edition you used? I'm using eve-ng community edition.


  • 17.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-05-2021 01:23
    Juniper vMX 19.4R1.10
    pnetlab 4.2.4


  • 18.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-05-2021 04:06
    Hi SongYue,

    Since u area used PNET ver 4.2.4 could u please test vMX version 20.2 and 20.3 whether VCP can be up without detect as Olive? Currently i'm still use 4.2.3 and cannot made vMX ver 20.2 and above boot up as vMX. I'm still not upgradeto ver 4.2.4 coz i see some bug.

    Thanks and appreciate your help.


  • 19.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-05-2021 08:44

    root> show version    
    Model: vmx
    Junos: 20.2R2-S1.3
    JUNOS OS Kernel 64-bit  [20201028.e1cef1d_builder_stable_11]
    
    root> show version    
    Model: vmx
    Junos: 20.3R1-S1.2
    JUNOS OS Kernel 64-bit  [20200922.4042921_builder_stable_11]
    
    root> show version    
    Model: vmx
    Junos: 20.4R1.12
    JUNOS OS Kernel 64-bit  [20201028.e1cef1d_builder_stable_11]​



  • 20.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-06-2021 05:24
    Hi Hi SongYue,,

    May i know whether u already test CGNAT functionality on vMX version 19.4? Coz i'm try on version 18.3 it cannot work.

    Thanks


  • 21.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-06-2021 05:31
    Yes, it works on  version 19.4r1.10.


  • 22.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-06-2021 05:47
    Hi SongYue,

    Thanks for the info. Let me spin up and test CGNAT on this version.


    Thanks again


  • 23.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-06-2021 08:00
    Hi SongYue,

    I'm test with your vMX version with same setup as yours but cannot made the vMS-MPC up. Below is my snapshot.






  • 24.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-06-2021 20:43
    Only for 19.4r1.10


  • 25.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-06-2021 23:24
    Hi SongYue,

    It's work using exact 19.4R1.


    Thanks


  • 26.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-09-2021 22:40
    Did you all install pnetlab on laptop,  or vm? I got 19.4R1 but stucked at 'present' fpc state in eve-ng.


  • 27.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-10-2021 05:18
    Hi gedebook2009,


    I'm using server and baremetal on EVE also PNET. If u using pc pr laptop then it possibility due to your pc requirement not enough.

    Thanks


  • 28.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-10-2021 05:51
    I got esxi on bare metal. I arise the cpu numbers and cores and it got to up in 19.4R1.

    {master}
    exercise@exercise-r1-re0> show chassis fpc
                         Temp  CPU Utilization (%)   CPU Utilization (%)  Memory    Utilization (%)
    Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
      0  Online           Testing   0         0        0      0      0      0         0          0
      1  Empty
      2  Empty
      3  Empty
      4  Empty
      5  Empty
      6  Empty
      7  Empty
      8  Empty
      9  Empty
     10  Empty
     11  Empty
    
    {master}
    exercise@exercise-r1-re0> show interfaces terse | match ms-
    Jan 10 17:35:42
    mams-0/2/0              up    up
    ms-0/2/0                up    up
    ms-0/2/0.64000          up    up   inet
    ​


    But I don't understand. I was only setup the port at the node only 3 ports. Why would my vmx detects 10 ports of ge-0/0/x? I would like to setup the ports only for ms-x/x/x interface to reduce the performance costs. Any idea why about?

    {master}
    exercise@exercise-r1-re0> show interfaces terse
    Interface               Admin Link Proto    Local                 Remote
    ge-0/0/0                up    up
    ge-0/0/0.16386          up    up
    pfe-0/0/0               up    up
    pfe-0/0/0.16383         up    up   inet
                                       inet6
    pfh-0/0/0               up    up
    pfh-0/0/0.16383         up    up   inet
    pfh-0/0/0.16384         up    up   inet
    ge-0/0/1                up    down
    ge-0/0/1.16386          up    down
    ge-0/0/2                up    down
    ge-0/0/2.16386          up    down
    ge-0/0/3                up    down
    ge-0/0/3.16386          up    down
    ge-0/0/4                up    down
    ge-0/0/4.16386          up    down
    ge-0/0/5                up    down
    ge-0/0/5.16386          up    down
    ge-0/0/6                up    down
    ge-0/0/6.16386          up    down
    ge-0/0/7                up    down
    ge-0/0/7.16386          up    down
    ge-0/0/8                up    down
    ge-0/0/8.16386          up    down
    ge-0/0/9                up    down
    ge-0/0/9.16386          up    down
    mams-0/2/0              up    up
    ms-0/2/0                up    up
    ms-0/2/0.64000          up    up   inet
                                       inet6
    pc-0/2/0                up    up
    pc-0/2/0.16383          up    up   inet
    pc-0/2/0.16384          up    up   inet     20.0.0.1            --> 20.0.0.18
    cbp0                    up    up
    demux0                  up    up
    dsc                     up    up
    em1                     up    up
    em1.0                   up    up   inet     10.0.0.4/8
                                                128.0.0.1/2
                                                128.0.0.4/2
                                       inet6    fe80::5201:ff:fe02:1/64
                                                fec0::a:0:0:4/64
                                       tnp      0x4
    esi                     up    up
    fti0                    up    up
    fti1                    up    up
    fti2                    up    up
    fti3                    up    up
    fti4                    up    up
    fti5                    up    up
    fti6                    up    up
    fti7                    up    up
    fxp0                    up    up
    fxp0.0                  up    up   inet
    gre                     up    up
    ipip                    up    up
    irb                     up    up
    jsrv                    up    up
    jsrv.1                  up    up   inet     128.0.0.127/2
    lo0                     up    up
    lo0.0                   up    up   inet     192.168.0.2         --> 0/0
    lo0.16384               up    up   inet     127.0.0.1           --> 0/0
    lo0.16385               up    up   inet
    lsi                     up    up
    mif                     up    up
    mif.64000               up    up   inet
                                       inet6
    mtun                    up    up
    pimd                    up    up
    pime                    up    up
    pip0                    up    up
    pp0                     up    up
    rbeb                    up    up
    tap                     up    up
    vtep                    up    up


    Now I facing the problem that my vms-mpc isn't stands stable.

    {master}
    exercise@exercise-r1-re0> show chassis fpc | no-more
    Jan 10 17:35:45
                         Temp  CPU Utilization (%)   CPU Utilization (%)  Memory    Utilization (%)
    Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
      0  Offline         ---Chassis connection dropped---
      1  Empty
      2  Empty
      3  Empty
      4  Empty
      5  Empty
      6  Empty
      7  Empty
      8  Empty
      9  Empty
     10  Empty
     11  Empty
    



  • 29.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-07-2021 07:12
    Hi SongYue,


    Could u guide me how u can make the CNAT is success on vMX version 19.4R1. Below is my output result. It still fail to translate the pool that i create.


    [edit]
    root@BNG-CGNAT# run show services nat pool


    [edit]
    root@BNG-CGNAT# run show services nat statistics
    Interface: ms-0/2/0

    Session statistics

    Session statistics
    Total Session Interest events :184
    Total Session Create events :0
    Total Session Destroy events :177
    Total Session Pub Req events :0
    Total Session Accepts :0
    Total Session Discards :184
    Total Session Ignores :0
    Control Session Not Xlated Child Sess Ignored :0
    Total Session Time events :0
    Session interest thru pub event :0
    ALG Session interest :0
    ALG Session Create :0
    Total Session close :0
    Packet Dst in NAT route :0
    Packet drop in backup state :184
    Session Ext Alloc Failures :0
    Session Ext Set Failures :0
    Session Created for EIF :0
    Session Created for EIM :0
    NAT rule lookup failures :0
    No NAT session ext in xlate packet :0
    Pool session count update failed on create :0
    Pool session count update failed on close :0


    [edit]
    root@BNG-CGNAT# run show interfaces descriptions
    Interface Admin Link Description
    ge-0/0/0 up up Connection to GPON-SW (ge-0/0/)
    ge-0/0/1 up up --> IGW (ge-0/0/0)
    ms-0/2/0 up up MultiService PIC
    ams0 up up CGNAT INTERFACE
    ams0.1 up up Inside Service NAT
    ams0.2 up up Outside Service NAT


    Thanks and appreciate your or anyone feedback


  • 30.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-11-2021 02:49
    Thanks everybody.

    It is already up in 19.4R1 version. So the cause is the cpu numbers didn't set up correctly in my eve-ng. And since it is hosts reside in VM. The resource set is not enough compared with the vcpu number required. The cpu number x cpu cores, will help overcame the vcpu number requirement. I also set up the lite-mode on fpc to keep the vms-mpc able to run. Performance-mode or unconfigured one will result of the cpu is being threaten as unsupported cpu by the vfp.

    {master}
    exercise@exercise-r1-re0> show services stateful-firewall flows extensive
    Jan 11 14:14:06
    Interface: ms-0/2/0, Service set: if-service-1
    Flow                                                State    Dir       Frm count
    ICMP         172.16.1.1        ->  192.168.77.254        Watch    I              77
      Byte count: 6468
      Flow role: Initiator, Timeout: 0
    ICMP     192.168.77.254        ->  192.168.77.210        Watch    O               0
      Byte count: 0
      Flow role: Responder, Timeout: 0
    
    {master}
    exercise@exercise-r1-re0> show services service-sets summary
    Jan 11 14:14:17
                 Service sets                                           CPU
    Interface    configured             Bytes used   Policy bytes used  utilization
    ms-0/2/0           1  1183760672      (55.82%)   10480768 (15.61%)  0.00 %
    ​


    Although I'm not yet able to set up the advanced nat correctly for now. I will put another question later.





  • 31.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-11-2021 03:12
    Hi gedebook2009,

    Congrat finally u can bring up the vMS-MPC. Secondly may i know how u get "watch" in your output? Do u already configure anything so that "watch" can be see? I'm get drop.

    root@BNG-CGNAT> show services stateful-firewall flows extensive
    Interface: mams-0/2/0, Service set: AMS0_NAT_SS
    Flow State Dir Frm count
    ICMP 10.70.0.2 -> 33.33.0.255 Drop I 1
    Byte count: 60
    Flow role: Initiator, Timeout: 0
    UDP 10.70.0.2:51264 -> 8.8.8.8:53 Drop I 1
    Byte count: 70
    Flow role: Initiator, Timeout: 0
    UDP 10.70.0.2:51264 -> 8.8.4.4:53 Drop I 1
    Byte count: 70
    Flow role: Initiator, Timeout: 0


    Thanks


  • 32.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-11-2021 14:51
    I'm not pretty sure. But I'll make a guess that you should configure the stateful-firewall and include them to your service-set. My configuration is as follow.
    set services service-set if-service-1 stateful-firewall-rules r-st1
    set services stateful-firewall rule r-st1 match-direction input
    set services stateful-firewall rule r-st1 term t1 from source-address any-ipv4
    set services stateful-firewall rule r-st1 term t1 from destination-address any-ipv4
    set services stateful-firewall rule r-st1 term t1 then accept​



  • 33.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-11-2021 22:01
    Hi gedebook2009,

    May i know whether u use AMS interface or just ms-x/x/x interface only?

    Thanks and appreciate your feedback


  • 34.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-12-2021 04:14

    I use simple ms-x/x/x interface without ams.

    At another of discussion, how you can run the vmx on pnetlab? I have tried on pnet lab using vmx at provided download link but it is not running when I started the node.




  • 35.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-12-2021 08:46
    Hi gedebook2009,


    The step on PNET is same as EVE-NG community. U can just transfer the image "hda.qcow2" or "virtioa.qcow2" into PNET. Also u can use the template.yml from EVE and transfer to PNET.

    Let me try using ms-x/x/x

    Thanks



  • 36.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-12-2021 09:23
    Hi gedebook2009,

    After change to interface ms-0/2/0 then i can see the flow session and pool CGNAT. But unfortunately still fail to ping to destination.

    root@BNG-CGNAT> show services stateful-firewall flows extensive
    Interface: ms-0/2/0, Service set: AMS0_NAT_SS
    Flow State Dir Frm count
    UDP 10.70.0.2:50637 -> 8.8.8.8:53 Forward I 1
    Byte count: 70
    Flow role: Initiator, Timeout: 0
    UDP 8.8.8.8:53 -> 203.179.68.1:64668 Forward O 0
    Byte count: 0
    Flow role: Responder, Timeout: 0
    UDP 10.70.0.2:50637 -> 8.8.4.4:53 Forward I 1
    Byte count: 70
    Flow role: Initiator, Timeout: 0
    UDP 8.8.4.4:53 -> 203.179.68.1:64664 Forward O 0
    Byte count: 0
    Flow role: Responder, Timeout: 0
    UDP 10.70.0.2:53785 -> 8.8.8.8:53 Forward I 1
    Byte count: 62
    Flow role: Initiator, Timeout: 0
    UDP 8.8.8.8:53 -> 203.179.68.1:64897 Forward O 0
    Byte count: 0
    Flow role: Responder, Timeout: 0
    UDP 10.70.0.2:64797 -> 8.8.8.8:53 Forward I 1

    Thanks


  • 37.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-06-2021 05:31
    是的,它适用于版本19.4r1.10。


  • 38.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-13-2022 14:41
    Edited by spuluka 01-16-2022 15:08

    Hi can you share naming  file in folder vmxvfp-fpc? for enable vMS-MPC and resuouce each cpu and memory

    i use vmx version  18.2R1.9

    vFPC-20180605.img
    metadata-usb-fpc0.img
    metadata-usb-service-pic-2g.img

    Thanks you sir



    ------------------------------
    Sicak
    ------------------------------



  • 39.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 01-14-2022 05:31
    Hi bro,

    CGNAT is not working properly in vMX. So u dont need to waste time to test it.

    Thanks


  • 40.  RE: Check the ms-x/x/x.x interface on service pic 2g at vMX.

    Posted 02-08-2021 01:40

    Hi,
    anyone ever use kvm for this vms-mpc?
    can share the vmx.conf?

    i tried below and seem the vms-mpc is can't online.
    # cat /Downloads/vmx/config/vmx-vCGNAT.conf
    ##############################################################
    #
    # vmx.conf
    # Config file for vmx on the hypervisor.
    # Uses YAML syntax.
    # Leave a space after ":" to specify the parameter value.
    #
    ##############################################################

    ---
    #Configuration on the host side - management interface, VM images etc.
    HOST:
    identifier : vNAT # Maximum 6 characters
    host-management-interface : eno2
    routing-engine-image : "/home/ipnet/Downloads/vmx/images/junos-vmx-x86-64-17.3R3.10.qcow2"
    routing-engine-hdd : "/home/ipnet/Downloads/vmx/images/vmxhdd.img"
    forwarding-engine-image : "/home/ipnet/Downloads/vmx/images/vFPC-20180530.img"

    ---
    #External bridge configuration
    BRIDGES:
    - type : external
    name : br-ext-vNAT # Max 10 characters

    ---
    #vRE VM parameters
    CONTROL_PLANE:
    vcpus : 4
    memory-mb : 16384
    console_port: 8601

    interfaces :
    - type : static
    ipaddr : 10.102.144.94
    macaddr : "CA:00:DD:C0:DE:0E"

    ---
    #vPFE VM parameters
    FORWARDING_PLANE:
    memory-mb : 34576
    vcpus : 24
    console_port: 8602
    device-type : virtio

    interfaces :
    - type : static
    ipaddr : 10.102.144.98
    macaddr : "CA:00:DD:C0:DE:10"

    pic-name : service-pic-2g

    ---
    Interfaces
    JUNOS_DEVICES:
    - interface : ge-0/0/0
    mac-address : "CA:06:0A:0E:FF:F0"
    description : "ge-0/0/0 interface"
    virtual-function : 0

    - interface : ge-0/0/1
    mac-address : "CA:06:0A:0E:FF:F1"
    description : "ge-0/0/0 interface"
    virtual-function : 0