Switching

 View Only
last person joined: 6 days ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
  • 1.  EX3300 vc mode {linecard}

    Posted 08-18-2022 11:12
    Hi all, 

    First-time poster, long-time reader.
     I have a problem with switch EX3300,

    rebooting has no effect here. I get the same problems when trying to log in.

    When I boot up with boot -s and recovery the switch tells me this:
    warning: This chassis is operating in a non-master role as part of a virtual-chassis (VC) system.
    warning: Use of interactive commands should be limited to debugging and VC Port operations.
    warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
    warning: The VC-M can be identified through the show virtual-chassis status command executed at this console.
    warning: Please logout and log into the VC-M to use CLI.​​


    I tried this:
    + request system zeroize 

    + loader> install --format file:///<Junos package name>  , i try upgrade OS with USB boots

    +  I try to delete file Vchassic  then reboot it

    I tried but it is still mode linecard, I can't use the switch in this state, I need it in Master or stand-alone mode.


    Thanks



  • 2.  RE: EX3300 vc mode {linecard}

    Posted 08-18-2022 12:05
    Edited by ankurv 08-18-2022 12:07
    The chassis this was connected as line card have this switch listed as member and are the VC cables still connected to this switch? On the line card switch you may also want to try the following if not executed earlier. 

    configure
    delete virtual-chassis
    commit and-quit


    ------------------------------
    ANKUR
    ------------------------------



  • 3.  RE: EX3300 vc mode {linecard}

     
    Posted 08-18-2022 14:38
    Your console output is a bit nonsensical -- it shows a single master member yet the switch is running in linecard mode. Are you sure it's not connected to another switch? The two styles of console windows in your post make me think we don't have the full picture. Did you really reboot or did you just kill the vccpd process (and why?)

    Make sure there are no other VC switches attached. Check with 'show virtual-chassis vc-port'

    start shell
    rm -rf /config/vchassis/
    *
    exit
    request system reboot at now



  • 4.  RE: EX3300 vc mode {linecard}

    Posted 08-19-2022 05:01

    Hi Smicker,

    thank you for reply. 

    I make sure its not connect to another switch.
     
    Yes, The two styles of console windows in my post, because i deleted file vchasssic and then reboot but its still mode linecard , i follow guide form juniper:  https://supportportal.juniper.net/s/article/EX-QFX-Routing-Engine-stuck-in-Linecard-role?language=en_US

    Now, i show virtual-chassis vc-port,  and remove file again.

    i have log session :

    Logging to master
    ...
    Connection to master failed, enabling local login

    --- JUNOS 12.3R12.4 built 2016-01-20 04:27:28 UTC

    ***********************************************************************
    ** **
    ** WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE **
    ** **
    ** It is possible that the primary copy of JUNOS failed to boot up **
    ** properly, and so this device has booted from the backup copy. **
    ** **
    ** Please re-install JUNOS to recover the primary copy in case **
    ** it has been corrupted and if auto-snapshot feature is not **
    ** enabled. **
    ** **
    ***********************************************************************

    HHHHHHHHH root@:LC:0% cli
    warning: This chassis is operating in a non-master role as part of a virtual-chassis (VC) system.
    warning: Use of interactive commands should be limited to debugging and VC Port operations.
    warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
    warning: The VC-M can be identified through the show virtual-chassis status command executed at this console.
    warning: Please logout and log into the VC-M to use CLI.
    {linecard:0}
    root> en  show    show ir
    ^
    syntax error, expecting <command>.
    root> show ir   virtual-chassis vc-port ?
    Possible completions:
    <[Enter]> Execute this command
    all-members Show virtual chassis ports on all virtual chassis members
    diagnostics Show virtual chassis port diagnostics
    lag-hash VC ports lag hashing information
    local Show virtual chassis ports on local virtual chassis member
    member Show virtual chassis ports on specific virtual chassis member
    statistics Show virtual chassis port statistics
    | Pipe through a command
    {linecard:0}
    root> show virtual-chassis vc-port 
    error: Could not connect to fpc0 : Can't assign requested address

    {linecard:0}
    root> show virtual-chassis

    Virtual Chassis ID: 86dc.98d5.6f25
    Virtual Chassis Mode: Enabled
    Mstr Mixed Neighbor List
    Member ID Status Serial No Model prio Role Mode ID Interface
    0 (FPC 0) Prsnt GD0215400832 ex3300-24t 128 Master* NA

    Member ID for next new member: 1 (FPC 1)

    {linecard:0}
    root> stt art shell
    root@:LC:0% rm -rf /config/vchassis/*
    root@:LC:0% exit
    exit

    {linecard:0}
    root> request system reboot a
    ^
    'a' is ambiguous.
    Possible completions:
    all-members Reboot all virtual chassis members
    at Time at which to perform the operation
    {linecard:0}
    root> request system reboot a t now
    Reboot the system at now? [yes,no] (no) yes


    *** FINAL System shutdown message from root@ ***

    System going down IMMEDIATELY


    Shutdown NOW!
    [pid 1522]

    {linecard:0}
    root> DWaiting (max 60 seconds) for system process `vnlru_mem' to stop...done
    Waiting (max 60 seconds) for system process `vnlru' to stop...done
    Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
    Waiting (max 60 seconds) for system process `syncer' to stop...
    Syncing disks, vnodes remaining...3 2 2 1 1 1 1 1 0 0 0 0 0 done

    syncing disks... All buffers synced.
    Uptime: 30m29s
    Rebooting...


    U-Boot 1.1.6 (Jun 4 2012 - 01:56:18)

    Board: EX3300-24T 5.17
    EPLD: Version 04.130327 (0x02)
    DRAM: Initializing (1GB)
    Flash: 8 MB

    Firmware Version: --- 01.00.00 ---
    USB: scanning bus for devices...
    Root Hub 0: 2 USB Device(s) found
    Root Hub 1: 1 USB Device(s) found
    scanning bus for storage devices... 1 Storage Device(s) found

    ELF file is 32 bit
    Consoles: U-Boot console

    FreeBSD/arm U-Boot loader, Revision 1.1
    (builder@greteth, Mon Jun 4 01:40:05 UTC 2012)
    Memory: 1024MB
    bootsequencing is enabled
    bootsuccess is set
    new boot device = disk0s2:
    |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\Loading /boot/defaults/loader.conf



    Hit [Enter] to boot immediately, or space bar for command prompt.
    Booting [/kernel] in 1 second... Booting [/kernel]...
    Kernel entry at 0x1400100 ...
    GDB: debug ports: uart
    GDB: current port: uart
    KDB: debugger backends: ddb gdb
    KDB: current backend: ddb
    Copyright (c) 1996-2016, Juniper Networks, Inc.
    All rights reserved.
    Copyright (c) 1992-2006 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
    JUNOS 12.3R12.4 #0: 2016-01-20 04:27:28 UTC
    builder@kessuth.juniper.net:/volume/build/junos/12.3/release/12.3R12.4/obj-arm/junos/bsd/kernels/JUNIPER-EX-3300/kernel
    can't re-use a leaf (all_slot_serialid)!
    CPU: Early Feroceon 88FR571 rev 0 (Marvell core)
    cpu55: Early Feroceon 88FR571 revision WB enabled EABT branch prediction enabled
    32KB/32B 4-way Instruction cache
    32KB/32B 4-way write-back-locking-C Data cache
    real memory = 1073741824 (1024 MB)
    avail memory = 1029824512 (982 MB)
    SOC: Marvell MV78100, TClock 200MHz
    Security policy loaded: Junos MAC/veriexec (mac_veriexec)
    MAC/veriexec fingerprint module loaded: SHA256
    MAC/veriexec fingerprint module loaded: SHA1
    ETHERNET SOCKET BRIDGE initialising
    Initializing EXSERIES properties ...
    mbus0: <Marvell Internal Bus (Mbus)> on motherboard
    ic0: <Marvell Integrated Interrupt Controller> at mem 0xf1020200-0xf102023b on mbus0
    timer0: <Marvell CPU Timer> at mem 0xf1020300-0xf102032f irq 8 on mbus0
    gpio0: <Marvell Integrated GPIO Controller> at mem 0xf1010100-0xf101011f irq 56,57,58,59 on mbus0
    uart0: <16550 or compatible> at mem 0xf1012000-0xf101201f irq 12 on mbus0
    uart0: console (9600,n,8,1)
    uart1: <16550 or compatible> at mem 0xf1012100-0xf101211f irq 13 on mbus0
    ehci0: <88F5XXX Integrated USB 2.0 controller> at mem 0xf1050000-0xf1050fff irq 72,16 on mbus0
    usb0: EHCI version 1.0
    usb0 on ehci0
    usb0: USB revision 2.0
    uhub0: Marvell EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
    uhub0: 1 port with 1 removable, self powered
    umass0: STMicroelectronics ST72682 High Speed Mode, rev 2.00/2.10, addr 2
    ehci1: <88F5XXX Integrated USB 2.0 controller> at mem 0xf1051000-0xf1051fff irq 72,17 on mbus0
    usb1: EHCI version 1.0
    usb1 on ehci1
    usb1: USB revision 2.0
    uhub1: Marvell EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
    uhub1: 1 port with 1 removable, self powered
    ehci2: <88F5XXX Integrated USB 2.0 controller> at mem 0xf1052000-0xf1052fff irq 72,18 on mbus0
    usb2: EHCI version 1.0
    usb2 on ehci2
    usb2: USB revision 2.0
    uhub2: Marvell EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
    uhub2: 1 port with 1 removable, self powered
    mge0: <Marvell Gigabit Ethernet controller> at mem 0xf1072000-0xf1073fff irq 41,42,43,40,70 on mbus0
    mge0: hardware MAC address ec:3e:f7:5a:65:ff
    miibus0: <MII bus> on mge0
    e1000phy0: <Marvell 88E1310 Gigabit PHY> on miibus0
    e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
    i2c0: <Marvell I2C ARM OnChip Controller> at mem 0xf1011000-0xf101101f on mbus0
    8564 rtc0: <8564 RTC> on i2c0
    poe0: <POE> on i2c0
    poe_attach: re-types method failed
    device_attach: poe0 attach returned 19
    i2c1: <Marvell I2C ARM OnChip Controller> at mem 0xf1011100-0xf101111f on mbus0
    pcib0: <Marvell MV78100 PCI-Express host controller> at mem 0xf1040000-0xf1041fff,0xe8000000-0xebffffff on mbus0
    pci0: <PCI bus> on pcib0
    mpfe0: <Juniper EX-series Packet Forwarding Engine> mem 0xe8000000-0xebffffff irq 112 at device 1.0 on pci0
    mpfe0: 0x100000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
    syspld0 at mem 0xf9000000-0xf90fffff on mbus0
    cfi0: <SPI flash - 8MB> at mem 0xf1010600-0xf101062f,0xf8800000-0xf8ffffff irq 1 on mbus0
    Initializing product: 112 ..
    bmeb: bmeb_lib_init done 0xc41c8800, addr 0xc1d87ae4
    bme0:Virtual BME driver initializing
    Timecounter "CPU Timer" frequency 200000000 Hz quality 1000
    ###PCB Group initialized for udppcbgroup
    ###PCB Group initialized for tcppcbgroup
    da0 at umass-sim0 bus 0 target 0 lun 0
    da0: <ST ST72682 2.10> Removable Direct Access SCSI-2 device
    da0: 40.000MB/s transfers
    da0: 1000MB (2048000 512 byte sectors: 64H 32S/T 1000C)
    Kernel thread "wkupdaemon" (pid 46) exited prematurely.
    Trying to mount root from ufs:/dev/da0s2a
    Attaching /packages/jbase via /dev/mdctl...
    Mounted jbase package on /dev/md0...
    Verified manifest signed by PackageProduction_12_3_0
    Verified jboot signed by PackageProduction_12_3_0
    Verified jbase-ex-12.3R12.4 signed by PackageProduction_12_3_0
    Mounted fips-mode-arm package on /dev/md2...
    Verified manifest signed by PackageProduction_12_3_0
    Verified fips-mode-arm-12.3R12.4 signed by PackageProduction_12_3_0
    Mounted jcrypto-ex package on /dev/md4...
    Verified manifest signed by PackageProduction_12_3_0
    Verified jcrypto-ex-12.3R12.4 signed by PackageProduction_12_3_0
    Mounted jdocs-ex package on /dev/md6...
    Verified manifest signed by PackageProduction_12_3_0
    Verified jdocs-ex-12.3R12.4 signed by PackageProduction_12_3_0
    Mounted jkernel-ex-3300 package on /dev/md8...
    Verified manifest signed by PackageProduction_12_3_0
    Verified jkernel-ex-3300-12.3R12.4 signed by PackageProduction_12_3_0
    Mounted jpfe-ex33x package on /dev/md10...
    Verified manifest signed by PackageProduction_12_3_0
    Verified jpfe-ex33x-12.3R12.4 signed by PackageProduction_12_3_0
    Mounted jroute-ex package on /dev/md12...
    Verified manifest signed by PackageProduction_12_3_0
    Verified jroute-ex-12.3R12.4 signed by PackageProduction_12_3_0
    Mounted jswitch-ex package on /dev/md14...
    Verified manifest signed by PackageProduction_12_3_0
    Verified jswitch-ex-12.3R12.4 signed by PackageProduction_12_3_0
    Mounted jweb-ex package on /dev/md16...
    Verified manifest signed by PackageProduction_12_3_0
    Verified jweb-ex-12.3R12.4 signed by PackageProduction_12_3_0
    Executing /packages/mnt/jweb-ex-12.3R12.4/mount.post..
    Automatic reboot in progress...
    Media check on da0 on ex platforms
    ** /dev/da0s2a
    FILE SYSTEM CLEAN; SKIPPING CHECKS
    clean, 36763 free (27 frags, 4592 blocks, 0.0% fragmentation)
    ** /dev/da0s3e
    FILE SYSTEM CLEAN; SKIPPING CHECKS
    clean, 62437 free (77 frags, 7795 blocks, 0.1% fragmentation)
    Computing slice and partition sizes for /dev/da0 ...
    savecore: could not be determined
    No dump exists
    ** /dev/da0s3d
    FILE SYSTEM CLEAN; SKIPPING CHECKS
    clean, 185346 free (34 frags, 23164 blocks, 0.0% fragmentation)
    ** /dev/da0s4d
    FILE SYSTEM CLEAN; SKIPPING CHECKS
    clean, 31593 free (33 frags, 3945 blocks, 0.1% fragmentation)
    rm: /var/etc/pam.conf: Operation not permitted
    ln: /var/db/dcd.snmp_ix: File exists
    ln: /var/db/snmp_engine.db: File exists
    Creating initial configuration...mgd: Running FIPS Self-tests
    veriexec: no signatures for device. file='/sbin/kats/cannot-exec' fsid=71 fileid=51404 gen=1 uid=0 pid=531
    mgd: FIPS Self-tests Passed
    mgd: commit complete
    Setting initial options: debugger_on_panic=NO debugger_on_break=NO.
    Starting optional daemons: .
    Doing initial network setup:
    .
    Initial interface configuration:
    additional daemons:.
    Additional routing options:kern.module_path: /boot//kernel;/boot/modules -> /boot/modules;/modules/peertype;/modules/ifpfe_drv;/modules/plaLoading the EX-series platform NETPFE module
    tform;/modules;
    kld netpfe drv: ifpfed_eth ifpfed_ml_cmnkld platform: ex_ifpfe if_vcpkld peertype: peertype_hcm peertype_pfem peertype_sfi peertype_slavere grat_arp_on_ifup=YES: net.link.ether.inet.grat_arp_on_ifup: 1 -> 1
    ipsec kld.
    Doing additional network setup:.
    Starting final network daemons:.
    setting ldconfig path: /usr/lib /opt/lib
    starting standard daemons: cron.
    Local package initialization:.
    Initialize /var subdirs
    starting local daemons:set cores for group access
    .
    Tue Dec 1 08:20:12 UTC 2020
    Boot media /dev/da0 has dual root support
    ** /dev/da0s1a
    FILE SYSTEM CLEAN; SKIPPING CHECKS
    clean, 36251 free (27 frags, 4528 blocks, 0.0% fragmentation)

    Amnesiac (ttyu0)

    login: root

    Logging to master
    ..Dec 1 08:20:52 init: chassis-manager (PID 1336) terminated by signal number 11. Core dumped!
    Dec 1 08:20:52 init: chassis-manager (PID 1367) started
    .
    Connection to master failed, enabling local login

    --- JUNOS 12.3R12.4 built 2016-01-20 04:27:28 UTC

    ***********************************************************************
    ** **
    ** WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE **
    ** **
    ** It is possible that the primary copy of JUNOS failed to boot up **
    ** properly, and so this device has booted from the backup copy. **
    ** **
    ** Please re-install JUNOS to recover the primary copy in case **
    ** it has been corrupted and if auto-snapshot feature is not **
    ** enabled. **
    ** **
    ***********************************************************************

    HHHHHHHHH root@:LC:0%
    root@:LC:0%

    root@:LC:0% cli
    warning: This chassis is operating in a non-master role as part of a virtual-chassis (VC) system.
    warning: Use of interactive commands should be limited to debugging and VC Port operations.
    warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
    warning: The VC-M can be identified through the show virtual-chassis status command executed at this console.
    warning: Please logout and log into the VC-M to use CLI.
    {linecard:0}
    root>


    thanks,




  • 5.  RE: EX3300 vc mode {linecard}

    Posted 08-19-2022 07:46
    Hi,

    If u already reformat it then it should back to master. Please try reformat again using loader step USB.


    Thanks


  • 6.  RE: EX3300 vc mode {linecard}

     
    Posted 08-19-2022 08:05
    Agreed--please do a boot loader USB install with format. It's booting from the backup image, and the chassis manager is core-dumping.

    https://supportportal.juniper.net/s/article/EX-Performing-and-resolving-any-common-issues-during-Format-Install-on-legacy-EX-platforms?language=en_US#


  • 7.  RE: EX3300 vc mode {linecard}

    Posted 08-21-2022 10:34
    Thanks for all the support, problem solved

    - Change booting from the primary image
    - Re-install Junos from boot loader USB install with --format

    The device is already working in master mode