vMX

Expand all | Collapse all

VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP

Jump to Best Answer
  • 1.  VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP

    Posted 11-01-2019 04:08

    Good morning,

     

    I have installed a testing lab in a Dell R710 machine. That machine has Broadcom interfaces, but as I'm using virtio it shouldn't matter by what I have read. The problem I'm facing is that I can't make VCP connect to VFP and then : 

     

    root> show route 1.2.3.4
    error: the routing subsystem is not running

     

    or

     

    root> show chassis routing-engine
    error: the chassis-control subsystem is not responding to management requests

     

    If I do a :

    root> ping 128.0.0.16 routing-instance __juniper_private1__
    PING 128.0.0.16 (128.0.0.16): 56 data bytes
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address

     

    Ok, so let's check the bridge :

     

    root> ping 128.0.0.16
    PING 128.0.0.16 (128.0.0.16): 56 data bytes
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address

     

    root> edit
    Entering configuration mode

    [edit]
    root# edit interfaces vtnet1 unit 0 family inet

    [edit interfaces vtnet1 unit 0 family inet]
    root# set address 128.0.0.1/16

    [edit interfaces vtnet1 unit 0 family inet]
    root# show | compare
    [edit interfaces vtnet1 unit 0 family inet]
    + address 128.0.0.1/16;

    [edit interfaces vtnet1 unit 0 family inet]
    root# commit check
    configuration check succeeds

    [edit interfaces vtnet1 unit 0 family inet]
    root# commit
    commit complete

     

    root> ping 128.0.0.16
    PING 128.0.0.16 (128.0.0.16): 56 data bytes
    64 bytes from 128.0.0.16: icmp_seq=12 ttl=64 time=0.175 ms
    64 bytes from 128.0.0.16: icmp_seq=13 ttl=64 time=0.137 ms
    64 bytes from 128.0.0.16: icmp_seq=14 ttl=64 time=0.201 ms
    64 bytes from 128.0.0.16: icmp_seq=15 ttl=64 time=0.152 ms
    64 bytes from 128.0.0.16: icmp_seq=16 ttl=64 time=0.186 ms
    ^C
    --- 128.0.0.16 ping statistics ---
    17 packets transmitted, 5 packets received, 70% packet loss
    round-trip min/avg/max/stddev = 0.137/0.170/0.201/0.023 ms

    root> ping 128.0.0.16 routing-instance __juniper_private1__
    PING 128.0.0.16 (128.0.0.16): 56 data bytes
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address

     

    As far as I can ping with 128.0.0.16 (if I assign the ip to vtnet1/unit 0 interface BUT not from the __juniper_private1__ routing table) I assume the bridge should be ok.

     

    I attach what I assume are the relevant files...

     

    Please any kind of help with this would be just wonderful, because I'm trying to make this work 3 days now and I can't manage for getting it work.. Please if some more data for clarifying it would be needed, just ask for it and I'll be happy for providing the needed info... I attach the log provided by a root@vmx-host-egoitz:/home/vmx# ./vmx.sh -lvf --start... and I attach a list of interfaces and bridges after that VMX boot...

     

    Thanks a lot in advance,

    Best regards,

     

    Attachment(s)

    zip
    for-the-forum.zip   5 K 1 version
    txt
    interface-list.txt   4 K 1 version


  • 2.  RE: VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP

    Posted 11-01-2019 04:18

    cat vmx_1572606755.log
    ==================================================
    Welcome to VMX
    ==================================================
    Date..............................................11/01/19 12:12:35
    VMX Identifier....................................vmx1
    Config file......................................./home/vmx/config/vmx.conf
    Build Directory.................................../home/vmx/build/vmx1
    Assuming kvm hypervisor...........................
    Virtualization type...............................kvm
    Junos Device type.................................virtio
    Environment file................................../home/vmx/env/ubuntu_virtio.env
    Junos Device Type.................................virtio
    Initialize scripts................................[OK]
    ==================================================
    VMX Environment Setup Completed
    ==================================================
    ==================================================
    VMX Start
    ==================================================
    Check if vMX is running...........................[No]
    Check VCP image...................................[OK]
    Check VFP image...................................[OK]
    Check VCP Config image............................[OK]
    Check management interface........................[OK]
    Setup huge pages to 8192..........................[Already configured]
    [OK]
    Attempt to kill libvirtd..........................[OK]
    Attempt to start libvirt-bin......................[OK]
    Sleep 2 secs......................................[OK]
    Check libvirt support for hugepages...............[OK]
    ==================================================
    System Setup Completed
    ==================================================
    Get Management Address of eno1....................[OK]
    Generate libvirt files............................[OK]
    Sleep 2 secs......................................[OK]
    Find configured management interface..............eno1
    Find existing management gateway..................eno1
    Check if eno1 is already enslaved to br-ext.......[No]
    Gateway interface needs change....................[Yes]
    Get Management Gateway............................10.10.10.1
    Flush eno1........................................[OK]
    Bind eno1 to br-ext...............................[OK]
    Get Management MAC................................00:24:e8:3f:6c:84
    Assign Management MAC 00:24:e8:3f:6c:84...........[OK]
    Add default gw 10.10.10.1.........................[OK]
    [OK]
    Start vcp-vmx1....................................[OK]
    Wait 2 secs.......................................[OK]
    Start vfp-vmx1....................................[OK]
    Wait 2 secs.......................................[OK]
    ==================================================
    VMX Bringup Completed
    ==================================================
    Check if br-ext is created........................[Created]
    Check if br-int-vmx1 is created...................[Created]
    Check if VM vcp-vmx1 is running...................[Running]
    Check if VM vfp-vmx1 is running...................[Running]
    Check if tap interface vfp-ext-vmx1 exists........[OK]
    Check if tap interface vfp-int-vmx1 exists........[OK]
    Check if tap interface vcp-ext-vmx1 exists........[OK]
    Check if tap interface vcp-int-vmx1 exists........[OK]
    ==================================================
    VMX Status Verification Completed.
    ==================================================
    Log file........................................../home/vmx/build/vmx1/logs/vmx_1572606755.log
    ==================================================
    Thank you for using VMX
    ==================================================



  • 3.  RE: VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP

    Posted 11-02-2019 04:47

    Hi!

     

    Still trying to make this work... but have done a try... have said to KVM that guest interfaces are model type e1000 instead of the default rtl8169 (when saying model virtio) and now... at least... it sais there's no fpc0....

     

    root> show chassis fpc
    Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%)
    Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer
    0 Empty
    1 Empty
    2 Empty
    3 Empty
    4 Empty
    5 Empty
    6 Empty
    7 Empty
    8 Empty
    9 Empty
    10 Empty
    11 Empty

     

    but at least I can do a :

     

    root> show chassis alarms
    No alarms currently active

    root> show route 194.30.0.1

     

     

    and is not saying running the re... although anyway it's not working....

     

    after setting the interface to e1000, it seems the __juniper_private1__.inet to be better :

     

    Routing table: __juniper_private1__.inet
    Internet:
    Destination Type RtRef Nexthop Type Index NhRef Netif
    default perm 0 rjct 116 1
    0.0.0.0/32 perm 0 dscd 114 1
    10.0.0.0/8 intf 0 rslv 327 1 em1.0
    10.0.0.0/32 dest 0 10.0.0.0 recv 325 1 em1.0
    10.0.0.4/32 intf 0 10.0.0.4 locl 326 2
    10.0.0.4/32 dest 0 10.0.0.4 locl 326 2
    10.255.255.255/32 dest 0 10.255.255.255 bcst 324 1 em1.0
    128.0.0.0/2 intf 0 rslv 323 1 em1.0
    128.0.0.0/32 dest 0 128.0.0.0 recv 321 1 em1.0
    128.0.0.1/32 intf 1 128.0.0.1 locl 337 3
    128.0.0.1/32 dest 0 128.0.0.1 locl 337 3
    128.0.0.4/32 intf 1 128.0.0.4 locl 322 3
    128.0.0.4/32 dest 0 128.0.0.4 locl 322 3
    191.255.255.255/32 dest 0 191.255.255.255 bcst 320 1 em1.0
    224.0.0.0/4 perm 0 mdsc 115 1
    224.0.0.1/32 perm 0 224.0.0.1 mcst 111 1
    255.255.255.255/32 perm 0 bcst 112 1

     

    Previously not em1 interface appeared...

     

    And by the way I can't know assign the 128.0.0.X ip to em1 unit 0 in order to try to ping 128.0.0.16.....

     

    root@:/var/log # ping 128.0.0.16
    PING 128.0.0.16 (128.0.0.16): 56 data bytes
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address
    ^C

     

    in the VCP, in the dmesg in FreeBSD I see :

     

    rts_ifstate_client_close_job_handler: PHASE 1 entered, client:0xfffff80014b95c00, cl num:62, cl name:ksyncd, next_state:0 ticks 2147198249 start_ticks 2147198249
    rts_ifstate_client_close_job_handler: PHASE 2 entered, client:0xfffff80014b95c00, cl num:62, cl name:ksyncd, next_state:0xfffff80003439b00, ifs_head:0xfffff80003439b00 ticks 2147198249 start_ticks 2147198249
    rts_ifstate_client_close_job_handler: client:0xfffff80014b95c00 client close job done, cl name:ksyncd, cl num:62
    rts_ifstate_client_close_job_handler: Client-closing completed! ksyncd(62):0xfffff80014b95c00 num:0ticks 2147198249 start_ticks 2147198249
    Cleanup of dead ifstate client: ksyncd done Total dead ifstate client : 0
    ifstate client : dfwd closing down Total dead ifstate clients : 1
    rts_ifstate_client_close_job_handler: PHASE 1 entered, client:0xfffff8001385e200, cl num:111, cl name:dfwd, next_state:0 ticks 2147198265 start_ticks 2147198265
    rts_ifstate_client_close_job_handler: PHASE 2 entered, client:0xfffff8001385e200, cl num:111, cl name:dfwd, next_state:0xfffff80003439b00, ifs_head:0xfffff80003439b00 ticks 2147198265 start_ticks 2147198265
    rts_ifstate_client_close_job_handler: client:0xfffff8001385e200 client close job done, cl name:dfwd, cl num:111
    rts_ifstate_client_close_job_handler: Client-closing completed! dfwd(111):0xfffff8001385e200 num:0ticks 2147198265 start_ticks 2147198265
    Cleanup of dead ifstate client: dfwd done Total dead ifstate client : 0
    ifstate client : irsd closing down Total dead ifstate clients : 1
    rts_ifstate_client_close_job_handler: PHASE 1 entered, client:0xfffff8001385e400, cl num:61, cl name:irsd, next_state:0 ticks 2147198287 start_ticks 2147198287
    rts_ifstate_client_close_job_handler: PHASE 2 entered, client:0xfffff8001385e400, cl num:61, cl name:irsd, next_state:0xfffff80003439b00, ifs_head:0xfffff80003439b00 ticks 2147198287 start_ticks 2147198287
    rts_ifstate_client_close_job_handler: client:0xfffff8001385e400 client close job done, cl name:irsd, cl num:61
    rts_ifstate_client_close_job_handler: Client-closing completed! irsd(61):0xfffff8001385e400 num:0ticks 2147198287 start_ticks 2147198287
    Cleanup of dead ifstate client: irsd done Total dead ifstate client : 0
    setsockopt(RTS_ASYNC_NEED_RESYNC) ignored (pppd): client already active
    setsockopt(RTS_ASYNC_NEED_RESYNC) ignored (l2ald): client already active
    ifstate client : snmpd closing down Total dead ifstate clients : 1
    rts_ifstate_client_close_job_handler: PHASE 1 entered, client:0xfffff80016f2a600, cl num:100, cl name:snmpd, next_state:0 ticks 2147202261 start_ticks 2147202261
    rts_ifstate_client_close_job_handler: PHASE 2 entered, client:0xfffff80016f2a600, cl num:100, cl name:snmpd, next_state:0xfffff80003439b00, ifs_head:0xfffff80003439b00 ticks 2147202261 start_ticks 2147202261
    rts_ifstate_client_close_job_handler: client:0xfffff80016f2a600 client close job done, cl name:snmpd, cl num:100
    rts_ifstate_client_close_job_handler: Client-closing completed! snmpd(100):0xfffff80016f2a600 num:0ticks 2147202261 start_ticks 2147202261
    Cleanup of dead ifstate client: snmpd done Total dead ifstate client : 0
    trying to unregister protocol ka format for 179which was never registered
    setsockopt(RTS_ASYNC_NEED_RESYNC) ignored (mib2d): client already active
    rts_ifstate_chk_multi_registration: daemon mib2d(12146) has previously registered 1 time(s)
    setsockopt(RTS_ASYNC_NEED_RESYNC) ignored (pfed): client already active
    rts_ifstate_chk_multi_registration: daemon mib2d(12146) has previously registered 2 time(s)
    rts_ifstate_chk_multi_registration: daemon mib2d(12146) has previously registered 3 time(s)
    rts_ifstate_chk_multi_registration: daemon chassisd(11713) has previously registered 1 time(s)
    setsockopt(RTS_ASYNC_NEED_RESYNC) ignored (chassisd): client already active
    netdaemon_disable_timer:ISSU/GRES in progress. Stopping timer for netdaemon

     

    don't know if it's relevant....

     

    the vendorid in the config... seems to have been changed too....

     

    interfaces {
    fxp0 {
    unit 0 {
    family inet {
    dhcp {
    vendor-id Juniper-vmx-VM5DBD67A54E;
    }
    }
    }
    }
    }

     

    before, just appeared :

     

    interfaces {
    fxp0 {
    unit 0 {
    family inet {
    dhcp {
    vendor-id Juniper-vmx-;
    }
    }
    }
    }
    }

     

    Should say too... I have explicitly enabled the fpc in lite-mode :

     

    root> show configuration
    ## Last commit: 2019-11-02 11:33:09 UTC by root
    version 18.4R2-S1.4;
    system {
    syslog {
    user * {
    any emergency;
    }
    file messages {
    any notice;
    authorization info;
    }
    file interactive-commands {
    interactive-commands any;
    }
    }
    processes {
    dhcp-service {
    traceoptions {
    file dhcp_logfile size 10m;
    level all;
    flag packet;
    }
    }
    }
    ## Warning: missing mandatory statement(s): 'root-authentication'
    }
    chassis {
    fpc 0 {
    lite-mode;
    }
    }
    interfaces {
    fxp0 {
    unit 0 {
    family inet {
    dhcp {
    vendor-id Juniper-vmx-VM5DBD67A54E;
    }
    }
    }
    }
    }

     

     

     

     

     

     

     

     

    Really, any help would be highly appreciated...



  • 4.  RE: VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP

    Posted 11-03-2019 19:40

    Hi,

     

    What is the vMX version you are trying?

     

    Please share uname -a output. 

     

    Did you tried on 16.04.5 as recommended in below document..

     

    https://www.juniper.net/documentation/en_US/vmx/topics/reference/general/vmx-hw-sw-minimums.html

     

    delete that vnet1 config ., and share output of "show interface terse" from vcp.

     

    Also i could see that ipaddr config added under vmx.conf file. please remove that then try to spawn the vMX again.. 

     

    ---
    #Configuration on the host side - management interface, VM images etc.
    HOST:
    identifier : vmx1 # Maximum 6 characters
    ipaddr : 10.10.10.220
    host-management-interface : eno1
    routing-engine-image : "/home/vmx/images/junos-vmx-x86-64-18.4R2-S1.4.qcow2"
    routing-engine-hdd : "/home/vmx/images/vmxhdd.img"
    forwarding-engine-image : "/home/vmx/images/vFPC-20190611.img"

    ---



  • 5.  RE: VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP

    Posted 11-03-2019 23:40

    Hi!

     

     

    Thank you so much for your answer.

     

    The version is exactly 18.4R2-S1.4. Yes I tried with Ubuntu LTS 16.04.5. The interfaces created where vtnet0 and vtnet1 instead of em0 and em1... It seemed it just "knew" using em1 for __juniper_private1__ routing instance... I have been doing tons of tests... I'm afraid I can't paste the show interfaces terse because I have not at present that machine...

     

    The conclusions I have obtained are :

     

    - It seems that when you use e1000 model network in the host... all works as expected (I have not achieved to make it work with performance-mode which I don't mind because this is a testing lab)... it renames em0 to fpx0 and so.... the "ping 128.0.0.16 routing-instance __juniper_private1__  " works and I can do a show chassic fpc and see the fpc0 online...

     

    - With Ubuntu 16, I have not achieved to make it work... although have user a newer libvirt than 1.2.19...

     

    - With Ubuntu 14 server LTS, I achieved it to work* by rebuilding libvirt to 1.2.19... The * of achieved to make it work was because when the fpc0 is online... you get the console (either by ssh or telnet) clogged with errors as the https://forums.juniper.net/t5/vMX/vMX-Flooding-Logs-over-Console/td-p/319972 first comment... so I asssumed it was not working properly....

     

    All the previous tests, where done on a Xen VM with nestedhvm=1 and hap=1 or with nestedhvm=1 and no hap config defined.

     

    As in the nested virtual env (KVM "virtual machine host" virtualized on Xen) I wan't getting lucky... as said is a testing env... this is the reason of setting it up this way...

     

    Now, I'm giving a try to Centos 7.2 on a physical server (I have not done this test yet because it's not easy to have a dedicated several gigabyte ram server for testing).... but that has not Intel nics... it should not be a problem.. because I was planning to have a testing lab, so I was going to use virtio interfaces... the installation is slow... I will upgrade you 🙂

     

    As said before, any clue would be highly appreciated.

     

    Thanks a lot!



  • 6.  RE: VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP

    Posted 11-04-2019 08:17

    Installed all finally in Centos 7.2 (downloaded from the "vault" of Centos). Seems to be working (I need to test properly the vmx instances). The only working mode has been lite-mode.

     

    It seems it was just that it doesn't work in a nested env under Xen (but I didn't have a big dedicated server and as some people said it worked under Vmware fusion...) ... I didn't managed to get it working too under Ubuntu 16 physical too but I think it could be because it boots in performance-mode by default and I have needed to set it in lite-mode for working.... perhaps if you don't have a Ivi bridge it does not work in performance mode ??...



  • 7.  RE: VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP
    Best Answer

    Posted 11-04-2019 23:25

    Hi,

     

    Nested environment is not qualified for vMX at this point. So not sure what was the problem.

     

    Regarding the performance mode, you need to have enough memory/CPU's allocated for the vMX, with IVY bridge it should work in performance if enough resources are applied . Details are as below:

     

    https://www.juniper.net/documentation/en_US/vmx/topics/reference/general/vmx-hw-sw-minimums.html



  • 8.  RE: VMX vmx-bundle-18.4R2-S1.4 on Ubuntu 16.04.6 LTS/KVM : VCP not connecting to VFP

    Posted 11-11-2019 00:09

    Good morning,

     

    First of all, thank you so much for all your time. I have it working now in an old processor (Dell R710). Concretely in an eight core machine with cores like :

     

    processor : 7
    vendor_id : GenuineIntel
    cpu family : 6
    model : 26
    model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz
    stepping : 5
    microcode : 0x1d
    cpu MHz : 2260.941
    cache size : 8192 KB
    physical id : 1
    siblings : 8
    core id : 3
    cpu cores : 4
    apicid : 23
    initial apicid : 23
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida spec_ctrl intel_stibp flush_l1d
    bogomips : 4521.88
    clflush size : 64
    cache_alignment : 64
    address sizes : 40 bits physical, 48 bits virtual
    power management:

     

    It seemed all problem was first, having it in a nested environment (which I assumed it should have worked, due to some other people runs it in a nested virtual env with Vmware Fusion and KVM... although I used it with Xen and KVM). The second one, in the Dell host was to have in non lite mode the router.

     

    After that it worked. Please, be careful on using this in a nested env, even for testing purposes because it doesn't work and just drives you crazy.

     

    Thanks again to all.