vMX

Expand all | Collapse all

vMX 18.3 on Ubuntu 16.04 - More problems

Jump to Best Answer
  • 1.  vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-06-2018 08:25

    Not quite sure why this is causing so many issues.... It was so simple with Ubiuntu 14 and vMX 17....

     

    When I login to the console, which works, there are NO ge interfaces and I enable SSH and configure a static address on fxp0 in the same range as the physical host address and cannot get anything working.....

     

    Here's the vmx.conf file

    #Configuration on the host side - management interface, VM images etc.
    HOST:
        identifier                : vmx1   # Maximum 6 characters
        host-management-interface : eno1
        routing-engine-image      : "/home/clive/juniper/vmx/images/junos-vmx-x86-64-18.3R1.9.qcow2"
        routing-engine-hdd        : "/home/clive/juniper/vmx/images/vmxhdd.img"
        forwarding-engine-image   : "/home/clive/juniper/vmx/images/vFPC-20180829.img"
    ---
    #External bridge configuration
    BRIDGES:
        - type  : external
          name  : br-ext                  # Max 10 characters
    ---
    #vRE VM parameters
    CONTROL_PLANE:
        vcpus       : 1
        memory-mb   : 1024
        console_port: 8601
        interfaces  :
          - type      : static
            ipaddr    : 10.102.144.94
            macaddr   : "0A:00:DD:C0:DE:0E"
    ---
    #vPFE VM parameters
    FORWARDING_PLANE:
        memory-mb   : 8192
        vcpus       : 4
        console_port: 8602
        device-type : virtio
        interfaces  :
          - type      : static
            ipaddr    : 10.102.144.98
            macaddr   : "0A:00:DD:C0:DE:10"
    ---
    #Interfaces
    JUNOS_DEVICES:
       - interface            : ge-0/0/0
         mac-address          : "02:06:0A:0E:FF:F0"
         description          : "ge-0/0/0 interface"
       - interface            : ge-0/0/1
         mac-address          : "02:06:0A:0E:FF:F1"
         description          : "ge-0/0/1 interface"
       - interface            : ge-0/0/2
         mac-address          : "02:06:0A:0E:FF:F2"
         description          : "ge-0/0/2 interface"
       - interface            : ge-0/0/3
         mac-address          : "02:06:0A:0E:FF:F3"
         description          : "ge-0/0/3 interface"
     
    And here is the vmx-junosdev.conf file:
    interfaces :

    - link_name : vmx_link1
    mtu : 1500
    endpoint_1 :
    - type : junos_dev
    vm_name : vmx1
    dev_name : ge-0/0/0
    endpoint_2 :
    - type : host_dev
    dev_name : eno2

    # - link_name : vmx_link2
    # mtu : 1500
    # endpoint_1 :
    # - type : junos_dev
    # vm_name : vmx2
    # dev_name : ge-0/0/0
    # endpoint_2 :
    # - type : bridge_dev
    # dev_name : bridge1

    - link_name : vmx_link3
    endpoint_1 :
    - type : junos_dev
    vm_name : vmx1
    dev_name : ge-0/0/1
    endpoint_2 :
    - type : host_dev
    dev_name : eno2

    # - link_name : vmx_link4
    # endpoint_1 :
    # - type : junos_dev
    # vm_name : vmx1
    # dev_name : ge-0/0/2
    # endpoint_2 :
    # - type : junos_dev
    # vm_name : vmx2
    # dev_name : ge-0/0/2
     
    Here is the output from brctl show:
    bridge name                                  bridge id                          STP enabled                        interfaces
    br-ext                                              8000.d067e5edeb90      yes                                     br-ext-nic
                                                                                                                                                  eno1
                                                                                                                                                  vcp-ext-vmx1
                                                                                                                                                  vfp-ext-vmx1
    br-int-vmx1                                     8000.52540077b9be       yes                                   br-int-vmx1-nic
                                                                                                                                                  vcp-int-vmx1
                                                                                                                                                  vfp-int-vmx1
    virbr0                                                 8000.52540069dce4       yes                                  ge-0.0.2-vmx1
                                                                                                                                                   ge-0.0.3-vmx1
                                                                                                                                                    virbr0-nic
    vmx_link1                                           8000.d067e5edeb92       no                                     eno2
                                                                                                                                                    ge-0.0.0-vmx1
    vmx_link3                                           8000.fe060a0efff1           no                                    ge-0.0.1-vmx1
     
    During the install there are some differences, but I do not know if this is the version.... for example:
    ==================================================
    Pre-Install Checks Completed
    ==================================================
    Check RE state....................................[Not Running]
    [OK]
    Check for VM vfp-vmx1.............................[Not Running]
    [OK]
    Check if bridge br-ext exists.....................[No]
    Cleanup VM bridge br-ext..........................[OK]
    Cleanup VM bridge br-int-vmx1.....................[OK]
    Cleanup VM bridge br-fab-vmx1.....................[OK]
     
    Any help please, or I'll just take it back to previous version, which I don't really want to do as I really need 18
     


  • 2.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-06-2018 09:14

    Okay, I'm halfway there. I have managed to sort out the SSH issue and can now SSH to the device directly without having to go through Ubuntu first.

     

    All that leaves me with is why no ge interfaces show up under "show interfaces terse"....

     

    Any help there would be great please as I suspect it to be a binding issue somewhere, even if "brctl show" says it's all bound okay.



  • 3.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

    Posted 12-06-2018 21:01

    What is the output of "show chassis fpc" ? make sure FPC is online..



  • 4.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-07-2018 01:06

    Hi VR,

     

    That would indeed appear to be a problem..... Here's the output:

     

    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

     

     

    Any ideas please?

     

    The server is running 12 CPU and 38gig RAM



  • 5.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-07-2018 01:34

    Okay, I changed the following setting in vmx.conf:

     

    CONTROL_PLANE:
    vcpus : 1
    memory-mb : 2048
    console_port: 8601

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

     

    The memory was 1024 and I changed it to 2048 and I restart everything, and now the output for show chassis fpc is:

     

     0     Present       Absent 



  • 6.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-07-2018 01:46

    Thought it may be a memory issue so changed it to 8192mb but still no ge interfaces are available.

     



  • 7.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

    Posted 12-07-2018 01:47

    FPC should be online to get the interface. In your case i could see FPC is not online.

     

    Can you share message file from vFP?



  • 8.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-07-2018 02:15

    By vFP I'm guessing you mean the messages log file......:

     

    Dec 7 09:57:39 ng-test-data-network fpc0 LOGIN: : SETTING UP DPDK ENVIRONMENT ON
    Dec 7 09:57:39 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/sbin/modprobe uio
    Dec 7 09:57:39 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/sbin/insmod /home/pfe/riot/dpdk/x86_64-native-linuxapp-gcc/kmod/igb_uio.ko
    Dec 7 09:57:39 ng-test-data-network fpc0 LOGIN: : Not enough memory in vFP to set 1G hugepages. Proceeding with 2M hugepages
    Dec 7 09:57:39 ng-test-data-network fpc0 LOGIN: Not enough memory in vFP to set 1G hugepages. Proceeding with 2M hugepages
    Dec 7 09:57:40 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/home/pfe/riot/dpdk/tools/dpdk_nic_bind.py -b virtio-pci 00:03.0 00:04.0 00:05.0
    Dec 7 09:57:42 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/sbin/ifconfig eth2 up
    Dec 7 09:57:42 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/sbin/ifconfig eth2 down
    Dec 7 09:57:44 ng-test-data-network sshd[6500]: Accepted keyboard-interactive/pam for Clive from x.x.x.x port 51772 ssh2
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: Device virtio_net found
    Dec 7 09:57:45 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/sbin/ifconfig eth2 down
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : Creating /mnt/huge and mounting as hugetlbfs
    Dec 7 09:57:45 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/bin/mkdir -p /mnt/huge
    Dec 7 09:57:45 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/bin/mount -t hugetlbfs nodev /mnt/huge
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : Detected Junos Device type VirtIO
    Dec 7 09:57:45 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/home/pfe/riot/dpdk/tools/dpdk_nic_bind.py -u 00:05.0
    Dec 7 09:57:45 ng-test-data-network fpc0 sudo: root : TTY=unknown ; PWD=/home/pfe/riot/dpdk ; USER=root ; COMMAND=/home/pfe/riot/dpdk/tools/dpdk_nic_bind.py -b igb_uio 00:05.0
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : Number of ucode workers : 0
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: start_afi_server.sh : Found /usr/share/pfe/afi-server.tgz tarball
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : Detected Junos Device type VirtIO
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : Number of CPUs available : 4
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : Number of Ucode workers : 0
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : Number of PORTs to service : 1, loopbacks: 0
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : vdev_str:
    Dec 7 09:57:45 ng-test-data-network fpc0 LOGIN: : /home/pfe/riot/build/app/riot -c 0xf -n 2 --lcores='0@0,1@2,2@2,3@3,4@1' --log-level=5 -w 00:05.0 -- --rx "(0,0,0,3)," --tx "(0,3)," --w "4" --f "1" --bbe_mode "0" --rpio "local,3000,3001" --hostif "local,3002" --bsz "(32



  • 9.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-07-2018 03:26
      |   view attached

    Hi VR

     

    Here's the messages log from the vMX

     

    By the way, if I start the fpc in lite-mode, I get the following for show chassis fpc:

    0 Offline ---Restarted by cli command---

     

    Also, I can ping with the following command:

    run ping 128.0.0.16 routing-instance __juniper_private1__
    PING 128.0.0.16 (128.0.0.16): 56 data bytes
    64 bytes from 128.0.0.16: icmp_seq=0 ttl=64 time=0.233 ms
    64 bytes from 128.0.0.16: icmp_seq=1 ttl=64 time=0.325 ms
    64 bytes from 128.0.0.16: icmp_seq=2 ttl=64 time=0.284 ms
    64 bytes from 128.0.0.16: icmp_seq=3 ttl=64 time=0.360 ms

     

     

     

    Thanks

    Attachment(s)

    txt
    vmx-messages.txt   69K 1 version


  • 10.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-07-2018 03:47
      |   view attached

    Found the vfp log.... find it attached

    Attachment(s)

    txt
    vfp log.txt   34K 1 version


  • 11.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-07-2018 03:50

    Okay, I've just retried lite-mode and now I get this:

     

    Interface Admin Link Proto Local Remote
    ge-0/0/0 up up
    lc-0/0/0 up up
    lc-0/0/0.32769 up up vpls
    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/2 up down
    ge-0/0/3 up down
    ge-0/0/4 up down
    ge-0/0/5 up down
    ge-0/0/6 up down
    ge-0/0/7 up down
    ge-0/0/8 up down
    ge-0/0/9 up down

     

    Which is great.... but what's the issue with main mode and lite-mode and what's the difference?



  • 12.  RE: vMX 18.3 on Ubuntu 16.04 - More problems
    Best Answer

    Posted 12-07-2018 03:58

    By default system will boot in performnace mode. the resources are not sufficent for the system to run in performnace mode. so Litemode worked here.



  • 13.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 12-07-2018 07:07

    I will run it in lite mode for now and see where it fails during the configuration or what it does not support.

     

    Thanks



  • 14.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

    Posted 07-08-2019 05:06
      |   view attached

    hi,

    can you tell me how to solve the?SSH issue. I can't SSH to the device directly without having to go through Ubuntu first.

    I've been stuck on this question for a few days

    thanks!

    Attachment(s)

    txt
    vfp log.txt   34K 1 version


  • 15.  RE: vMX 18.3 on Ubuntu 16.04 - More problems

     
    Posted 07-19-2019 01:51

    Apologies for the delay in response. I don't get chance to get on here as much as used to...

     

    Try my website for the info required:

     

    http://clivetechgeek.com/index.php/2018/03/08/juniper-vmx-on-ubuntu-server/

    http://clivetechgeek.com/index.php/2018/12/14/secondthird-or-more-vmx-and-link-to-first-vmx/