vSRX HA Configuration

Features you'd like to see in the upcoming version of EVE-NG

Moderator: mike

Post Reply
venerzky
Posts: 30
Joined: Sat Jun 03, 2017 3:18 pm

vSRX HA Configuration

Post by venerzky » Tue Sep 25, 2018 7:02 am

Anyone who successfully configure juniper vsrx ha cluster? Thank you.

venerzky
Posts: 30
Joined: Sat Jun 03, 2017 3:18 pm

Re: vSRX HA Configuration

Post by venerzky » Mon Oct 15, 2018 5:08 am

Anyone configured vSRX using VMWare Workstation? I'm not seeing any ge-/0/0/x interfaces after I configured the HA clusters.

root>
Consoles: serial port
BIOS drive C: is disk0
BIOS 639kB/2096120kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.2
(builder@chamuth.juniper.net, Tue Mar 3 20:07:26 UTC 2015)
Loading /boot/defaults/loader.conf
/kernel text=0x985784 data=0x538f0+0x1020ec syms=[0x4+0xa1c50+0x4+0xe7666]
/boot/modules/if_em.ko text=0x15404 data=0x79c+0x14 -
/boot/modules/libmbpool.ko text=0xd9c data=0x100
/boot/modules/if_em_vjx.ko text=0xb94c data=0x600+0x204 -
/boot/modules/virtio.ko text=0x21f8 data=0x1f8 syms=[0x4+0x7e0+0x4+0x972]
/boot/modules/virtio_pci.ko text=0x2e98 data=0x208+0x8 syms=[0x4+0x8f0+0x4+0xb22]
/boot/modules/virtio_blk.ko text=0x2a08 data=0x1f0+0xc syms=[0x4+0x960+0x4+0xa0f]
/boot/modules/if_vtnet.ko text=0x6004 data=0x37c+0x10 syms=[0x4+0xde0+0x4+0xf0f]
/boot/modules/if_vtnet_vsrx.ko text=0x1f44 data=0x480+0x304 syms=[0x4+0x820+0x4+0xacb]


Hit [Enter] to boot immediately, or space bar for command prompt.
Booting [/kernel]...
platform_early_bootinit: Early Boot Initialization
GDB: debug ports: sio
GDB: current port: sio
KDB: debugger backends: ddb gdb
KDB: current backend: ddb
Copyright (c) 1996-2015, 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.1X47-D20.7 #0: 2015-03-03 21:53:50 UTC
builder@chamuth.juniper.net:/volume/build/junos/12.1/service/12.1X47-D20.7/obj-i386/junos/bsd/kernels/VSRX/kernel
acpi_alloc_wakeup_handler: can't alloc wake memory
ACPI APIC Table: <BOCHS BXPCAPIC>
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: QEMU Virtual CPU version 1.0 (3220.23-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x623 Stepping = 3
Features=0x783fbfd<FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2>
Features2=0x80802001<SSE3,CX16,POPCNT,<b31>>
AMD Features=0x20100800<SYSCALL,NX,LM>
AMD Features2=0x21<LAHF,ABM>
real memory = 2147475456 (2047 MB)
avail memory = 1146937344 (1093 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0 <Version 1.1> irqs 0-23 on motherboard
netisr_init: !debug_mpsafenet, forcing maxthreads from 2 to 1
Initializing VSRX platform properties ..
acpi0: <BOCHS BXPCRSDT> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc240-0xc24f at device 1.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
smb0: <Intel 82371AB SMB controller> irq 9 at device 1.3 on pci0
em0: <Intel(R) PRO/1000 Network Connection Version - 3.2.18> port 0xc000-0xc03f mem 0xfe9e0000-0xfe9fffff irq 10 at device 2.0 on pci0
em0: Memory Access and/or Bus Master bits were not set!
em1: <Intel(R) PRO/1000 Network Connection Version - 3.2.18> port 0xc040-0xc07f mem 0xfea20000-0xfea3ffff irq 11 at device 3.0 on pci0
em1: Memory Access and/or Bus Master bits were not set!
em2: <Intel(R) PRO/1000 Network Connection - EM Lite Version - 3.2.18> port 0xc080-0xc0bf mem 0xfea60000-0xfea7ffff irq 11 at device 4.0 on pci0
em3: <Intel(R) PRO/1000 Network Connection - EM Lite Version - 3.2.18> port 0xc0c0-0xc0ff mem 0xfeaa0000-0xfeabffff irq 10 at device 5.0 on pci0
em4: <Intel(R) PRO/1000 Network Connection - EM Lite Version - 3.2.18> port 0xc100-0xc13f mem 0xfeae0000-0xfeafffff irq 10 at device 6.0 on pci0
em5: <Intel(R) PRO/1000 Network Connection - EM Lite Version - 3.2.18> port 0xc140-0xc17f mem 0xfeb20000-0xfeb3ffff irq 11 at device 7.0 on pci0
em6: <Intel(R) PRO/1000 Network Connection - EM Lite Version - 3.2.18> port 0xc180-0xc1bf mem 0xfeb60000-0xfeb7ffff irq 11 at device 8.0 on pci0
em7: <Intel(R) PRO/1000 Network Connection - EM Lite Version - 3.2.18> port 0xc1c0-0xc1ff mem 0xfeba0000-0xfebbffff irq 10 at device 9.0 on pci0
virtio_pci0: <VirtIO PCI Block adapter> port 0xc200-0xc23f mem 0xfebe0000-0xfebe0fff irq 10 at device 10.0 on pci0
vtblk0: <VirtIO Block Adapter> on virtio_pci0
virtio_pci0: host features: 0x710006d4 <EventIdx,RingIndirect,NotifyOnEmpty,Topology,FlushCmd,SCSICmds,BlockSize,DiskGeometry,MaxNumSegs>
virtio_pci0: negotiated features: 0x10000254 <RingIndirect,FlushCmd,BlockSize,DiskGeometry,MaxNumSegs>
vtblk0: 1844MB (3776512 512 byte sectors)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse Explorer, device ID 4
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x90 on acpi0
sio0: type 16550A, console
orm0: <ISA Option ROM> at iomem 0xed800-0xeffff on isa0
vga0: <Generic ISA VGA> at port 0x3b0-0x3bb iomem 0xb0000-0xb7fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: MDA <16 virtual consoles, flags=0x300>
sio1: configured irq 5 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio2: configured irq 3 not in bitmap of probed irqs 0
sio2: port may not be enabled
sio3: configured irq 7 not in bitmap of probed irqs 0
sio3: port may not be enabled
Initializing product: 131 ..
fxp1: bus=0, device=3, func=0, Ethernet address 50:00:00:01:00:01
fxp0: bus=0, device=2, func=0, Ethernet address 50:00:00:01:00:00
###PCB Group initialized for udppcbgroup
###PCB Group initialized for tcppcbgroup
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/vtbd0s1a
WARNING: / was not properly dismounted
Attaching /cf/packages/junos via /dev/mdctl...
Mounted junos package on /dev/md0...

Automatic reboot in progress...
** /dev/vtbd0s1a
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
PARTIALLY TRUNCATED INODE I=161
SALVAGE? yes

** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=325 OWNER=root MODE=100640
SIZE=25 MTIME=Oct 15 04:29 2018
CLEAR? yes

** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? yes

SUMMARY INFORMATION BAD
SALVAGE? yes

BLK(S) MISSING IN BIT MAPS
SALVAGE? yes

394 files, 123932 used, 701103 free (39 frags, 175266 blocks, 0.0% fragmentation)

***** FILE SYSTEM MARKED CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****
** /dev/bo0s1e
** Last Mounted on /config
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
5 files, 4 used, 102779 free (3 frags, 25694 blocks, 0.0% fragmentation)

***** FILE SYSTEM MARKED CLEAN *****
Verified junos signed by PackageProduction_12_1_0
Verified jboot signed by PackageProduction_12_1_0
Verified junos-vsrx-12.1X47-D20.7-domestic signed by PackageProduction_12_1_0
Loading configuration ...
Interface control process: [edit interfaces]
Interface control process: 'ge-0/0/0'
Interface control process: HA management port cannot be configured

mgd: error: configuration check-out failed
Warning: Commit failed, activating partial configuration.
Warning: Edit the router configuration to fix these errors.
Setting initial options: .
Starting optional daemons: .
Doing initial network setup:
.
Initial interface configuration:
additional daemons: eventd.
Additional routing options:kern.module_path: /boot//kernel;/boot/modules -> /boot/modules;/modules/peertype;/modules/ifpfe_drv;/modules/platform;/modules;
kld netpfe drv: ifpfed_ism ifpfed_ml_ha ifpfed_ppeer ifpfed_st ifpfed_vtkld platform: fileassoc if_em if_em_vjx if_vtnet if_vtnet_vsrx virtio virtio_blk virtio_pcikld peertype: peertype_fwdd peertype_pfpc ipsec kld resrsv.
Doing additional network setup:.
Starting final network daemons:.
setting ldconfig path: /usr/lib /opt/lib
ldconfig: /opt/lib: ignoring directory not owned by root
starting standard daemons: cron.
Initial rc.i386 initialization:.

Lock Manager
RDM Embedded 7 [04-Aug-2006] http://www.birdstep.com
Copyright (c) 1992-2006 Birdstep Technology, Inc. All Rights Reserved.

Unix Domain sockets Lock manager
Lock manager 'lockmgr' started successfully.
Error: Profile database dictionary file missing.
Profile database initialized
Local package initialization:.
starting local daemons:set cores for group access
.
kern.securelevel: -1 -> 1
Mon Oct 15 05:02:41 UTC 2018

Amnesiac (ttyd0)

login:

venerzky
Posts: 30
Joined: Sat Jun 03, 2017 3:18 pm

Re: vSRX HA Configuration

Post by venerzky » Mon Oct 15, 2018 6:39 am

Got it working.

Solution: delete existing interface configuration.

{primary:node0}
root> show interfaces terse
Interface Admin Link Proto Local Remote
gr-0/0/0 up up
ip-0/0/0 up up
ge-0/0/2 up up
ge-0/0/3 up up
ge-0/0/4 up up
ge-0/0/5 up up
ge-0/0/6 up up
ge-0/0/7 up up
ge-7/0/2 up up
ge-7/0/3 up up
ge-7/0/4 up up
ge-7/0/5 up up
ge-7/0/6 up up
ge-7/0/7 up up
dsc up up
fab0 up down
fab0.0 up down inet 30.17.0.200/24
fab1 up down
fab1.0 up down inet 30.18.0.200/24
fxp0 up up
fxp1 up up
fxp1.0 up up inet 129.16.0.1/2
tnp 0x1100001
gre up up
ipip up up
irb up up
lo0 up up
lo0.16384 up up inet 127.0.0.1 --> 0/0
lo0.16385 up up inet 10.0.0.1 --> 0/0
10.0.0.16 --> 0/0
128.0.0.1 --> 0/0
128.0.0.4 --> 0/0
128.0.1.16 --> 0/0
lo0.32768 up up
lsi up up
mtun up up
pimd up up
pime up up
pp0 up up
ppd0 up up
ppe0 up up
st0 up up
tap up up

{primary:node0}
root>


================================================

{primary:node0}
root> show chassis cluster status
Monitor Failure codes:
CS Cold Sync monitoring FL Fabric Connection monitoring
GR GRES monitoring HW Hardware monitoring
IF Interface monitoring IP IP monitoring
LB Loopback monitoring MB Mbuf monitoring
NH Nexthop monitoring NP NPC monitoring
SP SPU monitoring SM Schedule monitoring
CF Config Sync monitoring

Cluster ID: 1
Node Priority Status Preempt Manual Monitor-failures

Redundancy group: 0 , Failover count: 1
node0 1 primary no no None
node1 1 secondary no no None

{primary:node0}
root>

{primary:node0}
root>

{primary:node0}
root>

================================================

Post Reply