Quantcast
Channel: All SRX Services Gateway posts
Viewing all 17645 articles
Browse latest View live

Re: 1-to-1 NAT setup to untrust /24?

$
0
0

Okay, I enabled traceoptions like:

set security flow traceoptions file 20debug
set security flow traceoptions flag basic-datapath
set security flow traceoptions packet-filter MatchTraffic source-prefix 10.20.0.0/24 destination-prefix 0.0.0.0/0

and it showed:

May 19 08:01:30 08:01:30.324521:CID-0:RT:  ge-0/0/1.7:10.20.0.3->10.20.0.1, icmp, (8/0)
May 19 08:01:30 08:01:30.324521:CID-0:RT: find flow: table 0x523bd198, hash 14452(0xffff), sa 10.20.0.3, da 10.20.1.1, sp 203, dp 12056, proto 1, tok
16, conn-tag 0x00000000
May 19 08:01:30 08:01:30.324521:CID-0:RT:  no session found, start first path. in_tunnel - 0x0, from_cp_flag - 0
May 19 08:01:30 08:01:30.324521:CID-0:RT:check self-traffic on ge-0/0/1.7, in_tunnel 0x0
May 19 08:01:30 08:01:30.324521:CID-0:RT:retcode: 0x201
May 19 08:01:30 08:01:30.324521:CID-0:RT:pak_for_self : proto 1, dst port 12056, action 0x0
May 19 08:01:30 08:01:30.324521:CID-0:RT:  flow_first_create_session
May 19 08:01:30 08:01:30.324521:CID-0:RT:Save init hash spu id 0 to nsp and nsp2!
May 19 08:01:30 08:01:30.324521:CID-0:RT:First path alloc and instl pending session, natp=0x59cb72e8, id=139732
May 19 08:01:30 08:01:30.324521:CID-0:RT:  flow_first_in_dst_nat: in <ge-0/0/1.7>, out <N/A> dst_adr 10.20.0.1, sp 203, dp 12056
May 19 08:01:30 08:01:30.324521:CID-0:RT:  chose interface ge-0/0/1.7 as incoming nat if.
May 19 08:01:30 08:01:30.324521:CID-0:RT:  packet dropped: for self but not interested
May 19 08:01:30 08:01:30.324521:CID-0:RT:  packet dropped, packet dropped: for self but not interested.

Doesn't that seem to say I don't have a sane rule allowing incoming traffic on ge0/0/1.7? Just trying to understand if my traceoptions logic is sane as well.


Re: 1-to-1 NAT setup to untrust /24?

$
0
0

It looks like the flow has a destination of 10.20.0.1 which happens to be an ip address assigned to the SRX itself.

May 19 08:01:30 08:01:30.324521:CID-0:RT:  packet dropped: for self but not interested
May 19 08:01:30 08:01:30.324521:CID-0:RT:  packet dropped, packet dropped: for self but not interested.

When the source or destination address is on the actual SRX then the rules are based on the security zone assignments for that interface in host inbound services.  If you need more granular policies then we use the junos-host zone.  But in any case none of the nat or polices for normal zones apply to any traffic with an SRX source/destination address.

 

Re: VRRP failover testing

$
0
0

Thanks Nellikka.

I am not sure how to remove this route 0.0.0.0/0 ? do i have to disable the below line ? or i can disable the interface ?

 

set interfaces ae0 unit 201 family inet address X.X.X.X vrrp-group 0 track route 0.0.0.0/0 routing-instance monitor priority-cost 75

Re: SRX 340 occasional panic

$
0
0

Hi!

 

It is predictable - lets say it will panic every 3h or so. Yes, i did zeroize first but it didn't resolve this issue. At the end it won't load kernel.

 

Loading configuration ...
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
usbd_start_next: error=13
Ignoring watchdog timeout during boot/reboot
Time and ticks drifted too much, resetting synchronization...
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
panic: Hardware watchdog timeout
cpuid = 0
KDB: stack backtrace:
SP 0: not in kernel
uart_sab82532_class+0x0 (0,0,0,0) ra 0 sz 0
pid 30, process: swi5: cambio
Uptime: 9m2s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort


NMI Exception on core:0
Watchdog status, core 0: 0xfffeccffffb
FPA INT Summery: 0x2000000000000
Err EPC: 0x8079a9c4
Trapframe Register Dump:
zero: 0000000000000000 at: fffffffffffffffe v0: 0000000050c808e5 v1: 00000000090b0045
a0: 00000000000186a0 a1: ffffffff80dc06b0 a2: 00000000ffff8010 a3: 0000000000000067
t0: 00000000508008a1 t1: 0000000000000000 t2: ffffffff80011800 t3: 0000000000000800
ta0: 0000000000000000 ta1: 0000000000000001 ta2: 0000000000000000 ta3: 0000000000000000
t8: 0000000023c34600 t9: 00000000287f4a94 s0: 000000000551600e s1: 0000000009896800
s2: 0000000003b9a043 s3: ffffffffc6e3a14c s4: ffffffff80a90000 s5: 0000000000000100
s6: 0000000000000001 s7: ffffffffc6ee3000 k0: 00bb3f24808b1101 k1: 0034002000040028
gp: ffffffff80ca2a80 sp: ffffffffeafab5e0 s8: ffffffff80b423cc ra: ffffffff8079a9cc
sr: 0000000050c808e5 mullo: 000000000f023000 mulhi: 0000000019000000
pc: ffffffff8015f7bc cause: 0000000040008408 badvaddr: ffffffffc6efa2dc
ErrPC: 0000000000000840
Current ticks/softticks 540786/55023, curproc [30] swi5: cambio
Core0: CacheErr(I/D: current: 0x2000000000000000/0xffffffffffff0000)

PCPU dump:
cpuid = 0
curthread = 0xc6ee3000: pid 30 "swi5: cambio"
ipis = 0x0
cpuid = 1
curthread = 0xc6e61000: pid 20 "idle: cpu1"
ipis = 0x0
cpuid = 2
curthread = 0xc6e5dc60: pid 19 "idle: cpu2"
ipis = 0x0
cpuid = 3
curthread = 0xc6e5da50: pid 18 "idle: cpu3"
ipis = 0x0
cpuid = 4
curthread = none
ipis = 0x0
cpuid = 5
curthread = none
ipis = 0x0
cpuid = 6
curthread = none
ipis = 0x0
cpuid = 7
curthread = none
ipis = 0x0
cpuid = 8
curthread = none
ipis = 0x0
cpuid = 9
curthread = none
ipis = 0x0
cpuid = 10
curthread = none
ipis = 0x0
cpuid = 11
curthread = none
ipis = 0x0
Memory dump of 1024 words starting at 0x80000000
0x80000000: 0829b8e3 401a4000 00000000 00000000
0x80000010: 00100000 00000000 00000000 00000000
0x80000020: 00000000 00000000 00000000 00000000
0x80000030: 00000000 00000000 00000000 00000000
0x80000040: 00000000 00000000 00000000 00000000
0x80000050: 00000000 00000000 00000000 00000000
0x80000060: 00000000 00000000 00000000 00000000
0x80000070: 00000000 00000000 00000000 00000000
0x80000080: 0829b8e3 401a4000 00000000 00000000
0x80000090: 00000000 00000000 00000000 00000000
0x800000a0: 00000000 00000000 00000000 00000000
0x800000b0: 00000000 00000000 00000000 00000000
0x800000c0: 00000000 00000000 00000000 00000000
0x800000d0: 00000000 00000000 00000000 00000000
0x800000e0: 00000000 00000000 00000000 00000000
0x800000f0: 00000000 00000000 00000000 00000000
0x80000100: 3c1b80df 277b2910 7c1a003b 001ad0c0
0x80000110: 035bd821 403ad801 ff7a0000 401a6000
0x80000120: 335a0002 17400005 00000000 3c1a80a7
0x80000130: 275af740 03400008 00000000 3c1a807c
0x80000140: 275aa92c 03400008 00000000 1000ffff
0x80000150: 00000000 42000018 00000000 00000000
0x80000160: 00000000 00000000 00000000 00000000
0x80000170: 00000000 00000000 00000000 00000000
0x80000180: 401a6000 401b6800 335a0010 001ad0c0
0x80000190: 337b007c 037ad825 3c1a80c9 275ac180
0x800001a0: 035bd021 8f5a0000 00000000 03400008
0x800001b0: 00000000 00000000 00000000 00000000
0x800001c0: 00000000 00000000 00000000 00000000
0x800001d0: 00000000 00000000 00000000 00000000
0x800001e0: 00000000 00000000 00000000 00000000
0x800001f0: 00000000 00000000 00000000 00000000
0x80000200: 00000000 00000000 00000000 00000000
0x80000210: 00000000 00000000 00000000 00000000
0x80000220: 00000000 00000000 00000000 00000000
0x80000230: 00000000 00000000 00000000 00000000
0x80000240: 00000000 00000000 00000000 00000000
0x80000250: 00000000 00000000 00000000 00000000
0x80000260: 00000000 00000000 00000000 00000000
0x80000270: 00000000 00000000 00000000 00000000
0x80000280: 00000000 00000000 00000000 00000000
0x80000290: 00000000 00000000 00000000 00000000
0x800002a0: 00000000 00000000 00000000 00000000
0x800002b0: 00000000 00000000 00000000 00000000
0x800002c0: 00000000 00000000 00000000 00000000
0x800002d0: 00000000 00000000 00000000 00000000
0x800002e0: 00000000 00000000 00000000 00000000
0x800002f0: 00000000 00000000 00000000 00000000
0x80000300: 00000000 00000000 00000000 00000000
0x80000310: 00000000 00000000 00000000 00000000
0x80000320: 00000000 00000000 00000000 00000000
0x80000330: 00000000 00000000 00000000 00000000
0x80000340: 00000000 00000000 00000000 00000000
0x80000350: 00000000 00000000 00000000 00000000
0x80000360: 00000000 00000000 00000000 00000000
0x80000370: 00000000 00000000 00000000 00000000
0x80000380: 00000000 00000000 00000000 00000000
0x80000390: 00000000 00000000 00000000 00000000
0x800003a0: 00000000 00000000 00000000 00000000
0x800003b0: 00000000 00000000 00000000 00000000
0x800003c0: 00000000 00000000 00000000 00000000
0x800003d0: 00000000 00000000 00000000 00000000
0x800003e0: 00000000 00000000 00000000 00000000
0x800003f0: 00000000 00000000 00000000 00000000
Stack trace:
DELAY+0x4c (0x186a0,0x80dc06b0,0xffff8010,0x67) ra 0x801dc318 sz 32
shutdown_panic+0x54 (0x186a0,0x80dc06b0,0xffff8010,0x67) ra 0x801dd608 sz 32
boot+0x7a4 (0x186a0,0x80dc06b0,0xffff8010,0x67) ra 0x801ddee4 sz 48
panic+0x580 (0x186a0,0x1,0x80010700,0x508008a1) ra 0x807b43b4 sz 64
panic_on_watchdog_timeout+0x78 (0x186a0,0x1,0x80010700,0x508008a1) ra 0x807da754 sz 32
re_srxsme_watchdog_intr+0x158 (0x186a0,0x1,0x80010700,0x508008a1) ra 0x8078aaac sz 24
mips_handle_this_interrupt+0x8c (0x186a0,0x1,0x80010700,0x508008a1) ra 0x8078ab38 sz 40
mips_handle_interrupts+0x58 (0x186a0,0x1,0x80010700,0x508008a1) ra 0x8078af5c sz 48
mips_interrupt+0x224 (0x186a0,0x1,0x80010700,0x508008a1) ra 0x80a6ed14 sz 32
MipsKernIntr+0x140 (0xc6f4bc00,0,0x80a8969c,0xd5) ra 0x80122274 sz 368
dadone+0x598 (0xc6f4bc00,0,0x80a8969c,0xd5) ra 0xffffffff sz 776
VA 0xfffffff7: not in kernel or heuristics failed
_start+0x7fefff3f (0xc6f4bc00,0,0x80a8969c,0xd5) ra 0 sz 0
pid 30, process: swi5: cambio
Resetting the system now...
cpu_reset: Stopping other CPUs
timeout stopping cpus


SPI stage 1 bootloader (Build time: Dec 9 2017 - 13:45:17)


U-Boot 2013.07-JNPR-3.5 (Build time: Dec 09 2017 - 13:45:17)

SRX_340 board revision major:1, minor:13, serial #: CY5016AF0253
OCTEON CN7130-AAP pass 1.2, Core clock: 1600 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR)
Base DRAM address used by u-boot: 0x10fc00000, size: 0x400000
DRAM: 4 GiB
Clearing DRAM...... done
Using default environment

SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
Found valid SPI bootloader at offset: 0x80000, size: 1377808 bytes


U-Boot 2013.07-JNPR-3.5 (Build time: Dec 09 2017 - 13:47:20)

Using DRAM size from environment: 4096 MBytes
SATA0: not available
SATA1: not available
SATA BIST STATUS = 0x0
SRX_340 board revision major:1, minor:13, serial #: CY5016AF0253
OCTEON CN7130-AAP pass 1.2, Core clock: 1600 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR)
Base DRAM address used by u-boot: 0x10f000000, size: 0x1000000
DRAM: 4 GiB
Clearing DRAM...... done
SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
PCIe: Port 0 link active, 1 lanes, speed gen2
PCIe: Link timeout on port 1, probably the slot is empty
PCIe: Port 2 not in PCIe mode, skipping
Net: octrgmii0
octeon_fdt_broadcom_config: Unknown broadcom phy for octrgmii0
Interface 4 has 1 ports (AGL)
Type the command 'usb start' to scan for USB storage devices.

Boot Media: eUSB usb
Found TPM SLB9660 TT 1.2 by Infineon
TPM initialized
Hit any key to stop autoboot: 0
SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
SF: 1048576 bytes @ 0x200000 Read: OK
## Starting application at 0x8f0000a0 ...
Consoles: U-Boot console
Found compatible API, ver. 3.5
USB1:
Starting the controller
USB XHCI 1.00
scanning bus 1 for devices... 2 USB Device(s) found
USB0:
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... WARN halted endpoint, queueing URB anyway.
Unexpected XHCI event TRB, type: 33, expected: 32, skipping... (0f3a1430 00000001 13000000 01008401)
Error: Mismatch slot ID or index, 0 != 1, field: 0x0, index: 0xffffffff, expect 0x0
Warning: transfer comp code 0x0 != 0x1a (COMP_STOP)
BUG: failure at xhci-ring.c:589/abort_td()!
BUG!


SPI stage 1 bootloader (Build time: Dec 9 2017 - 13:45:17)


U-Boot 2013.07-JNPR-3.5 (Build time: Dec 09 2017 - 13:45:17)

SRX_340 board revision major:1, minor:13, serial #: CY5016AF0253
OCTEON CN7130-AAP pass 1.2, Core clock: 1600 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR)
Base DRAM address used by u-boot: 0x10fc00000, size: 0x400000
DRAM: 4 GiB
Clearing DRAM...... done
Using default environment

SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
Found valid SPI bootloader at offset: 0x80000, size: 1377808 bytes


U-Boot 2013.07-JNPR-3.5 (Build time: Dec 09 2017 - 13:47:20)

Using DRAM size from environment: 4096 MBytes
SATA0: not available
SATA1: not available
SATA BIST STATUS = 0x0
SRX_340 board revision major:1, minor:13, serial #: CY5016AF0253
OCTEON CN7130-AAP pass 1.2, Core clock: 1600 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR)
Base DRAM address used by u-boot: 0x10f000000, size: 0x1000000
DRAM: 4 GiB
Clearing DRAM...... done
SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
PCIe: Port 0 link active, 1 lanes, speed gen2
PCIe: Link timeout on port 1, probably the slot is empty
PCIe: Port 2 not in PCIe mode, skipping
Net: octrgmii0
octeon_fdt_broadcom_config: Unknown broadcom phy for octrgmii0
Interface 4 has 1 ports (AGL)
Type the command 'usb start' to scan for USB storage devices.

Boot Media: eUSB usb
Found TPM SLB9660 TT 1.2 by Infineon
TPM initialized
Hit any key to stop autoboot: 0
SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
SF: 1048576 bytes @ 0x200000 Read: OK
## Starting application at 0x8f0000a0 ...
Consoles: U-Boot console
Found compatible API, ver. 3.5
USB1:
Starting the controller
USB XHCI 1.00
scanning bus 1 for devices... unable to get device descriptor (error=-1)
1 USB Device(s) found
USB0:
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

FreeBSD/MIPS U-Boot bootstrap loader, Revision 2.9
(builder@haku.juniper.net, Thu Nov 5 23:17:51 UTC 2015)
Memory: 4096MB
SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
[6]Booting from eUSB slice 1

can't load '/kernel'
can't load '/kernel.old'
Press Enter to stop auto bootsequencing and to enter loader prompt.

CTRL-A Z for help | 9600 8N1 | NOR | Minicom 2.7 | VT102 | Offline | ttyUSB0

Firewall srx 340 issues

$
0
0
Hello, i have trunk the fibre port (ge-0/0/15)of srx 340 firewall. However , the same donot work. Any suggestions

Re: Firewall srx 340 issues

$
0
0

When you insert the optic what do you see on these hardware check commands.

 

show chassis hardware

 

show chassis pic fpc-slot 0 pic-slot 0

 

show interface terse ge-0/0/15

 

Re: Firewall srx 340 issues

Re: SRX 340 occasional panic


Re: SRX 340 occasional panic

$
0
0

After shutdown from button it boots up as expected. Now i installed 15.1X49-D50.3 ( image from 2016 ) and seems, it stays up. Only configuration issue that came up when booted from old image was missing application-set that latest reccomended software didn't complain so i cleaned it up and we will see ...

 

[edit security policies global policy FTP-ACCESS-TO--EXTERNAL match application]
'junos-ftp-data'
application or application-set must be defined

Re: SRX220H2 - Cluster Issues (secondary node flapping): High CPU JSRPD

$
0
0
Just to update and close: we still could not determine the root cause, but were able to resolve the issue by rebooting node0. The cluster reformed, the jsprd process process utilization returned to normal levels, along with the cpu utilization.

Re: 1-to-1 NAT setup to untrust /24?

$
0
0

Thank you! I had two issues, one was my interface ge0/0/1.7 was in the wrong zone, and also I did:

host-inbound-traffic {
        system-services {
            all;
        }
        protocols {
            all;
        }
    }
    interfaces {
        ge-0/0/1.7;
    }

which now allows me to ping the interface, but not route out to the internet :/

When I look at traceoptions it seems it's not really trying to map to the public IP (I guess)?

May 22 01:49:25 01:49:25.936483:CID-0:RT: in_ifp <20:ge-0/0/1.7>
May 22 01:49:25 01:49:25.936483:CID-0:RT:setting rtt to:0x657cc050 based on VR ID:0 carried over in flow ctxt,  proto 2(ipv4)
May 22 01:49:25 01:49:25.936483:CID-0:RT:flow_process_pkt_exception: setting rtt in lpak to 0x657cc050
May 22 01:49:25 01:49:25.936483:CID-0:RT: jsf reinj: ctxt flag 0 sess 614180704232 src pid 28 reinj flag 6
May 22 01:49:25 01:49:25.936483:CID-0:RT:host inq check inq_type 0x6
May 22 01:49:25 01:49:25.936483:CID-0:RT:  flow session id 380904
May 22 01:49:25 01:49:25.936483:CID-0:RT:flow_xlate_pak
May 22 01:49:25 01:49:25.936483:CID-0:RT:  post addr xlation: 10.20.0.181->8.8.8.8.
May 22 01:49:25 01:49:25.936483:CID-0:RT:  post addr xlation: 10.20.0.181->8.8.8.8.

The weird part is that the post port xlation seems to start at 10.20.0.x and increments, I'm not sure what's happening:

May 22 01:57:24 01:57:23.944281:CID-0:RT:Doing DESTINATION addr route-lookup
May 22 01:57:24 01:57:23.944281:CID-0:RT:flow_ipv4_rt_lkup success 1.2.3.1, iifl 0x54, oifl 0x48
May 22 01:57:24 01:57:23.944281:CID-0:RT:  routed (x_dst_ip 1.2.3.1) from 20 (ge-0/0/1.7 in 0) to ge-0/0/0.0, Next-hop: 1.2.3.1
May 22 01:57:24 01:57:23.944281:CID-0:RT:flow_first_policy_search: policy search from zone 20-> zone untrust (0x0,0x1d12d2,0x12d2)
May 22 01:57:24 01:57:23.944281:CID-0:RT:Policy lkup: vsys 0 zone(18:20) -> zone(8:untrust) scope:0
May 22 01:57:24 01:57:23.944281:CID-0:RT:             10.20.0.3/2048 -> 1.2.3.1/53036 proto 1
May 22 01:57:24 01:57:23.944281:CID-0:RT:  app 0, timeout 60s, curr ageout 60s
May 22 01:57:24 01:57:23.944281:CID-0:RT:  permitted by policy permit-all(8)
May 22 01:57:24 01:57:23.944281:CID-0:RT:  packet passed, Permitted by policy.
May 22 01:57:24 01:57:23.944281:CID-0:RT:flow_first_src_xlate:  nat_src_xlated: False, nat_src_xlate_failed: False
May 22 01:57:24 01:57:23.944281:CID-0:RT:flow_first_src_xlate:  incoming src port is : 29.
May 22 01:57:24 01:57:23.944281:CID-0:RT:flow_first_src_xlate: src nat returns status: 1, rule/pool id: 2/4, pst_nat: False.
May 22 01:57:24 01:57:23.944281:CID-0:RT:  dip id = 4/0, 10.20.0.3/29->10.20.0.29/24921 protocol 1
May 22 01:57:24 01:57:23.944281:CID-0:RT:  choose interface ge-0/0/0.0(P2P) as outgoing phy if
May 22 01:57:24 01:57:23.944281:CID-0:RT:is_loop_pak: No loop: on ifp: ge-0/0/0.0, addr: 1.2.3.1, rtt_idx:0
May 22 01:57:24 01:57:23.944281:CID-0:RT:-jsf : Alloc sess plugin info for session 618475332531
May 22 01:57:24 01:57:23.944281:CID-0:RT:[JSF]Normal interest check. regd plugins 28, enabled impl mask 0x0
May 22 01:57:24 01:57:23.944281:CID-0:RT:+++++++++++jsf_test_plugin_data_evh: 3
May 22 01:57:24 01:57:23.944281:CID-0:RT:[JSF]Plugins(0x0, count 0) enabled for session = 618475332531, impli mask(0x0), post_nat cnt 0 svc req(0x0)
May 22 01:57:24 01:57:23.944281:CID-0:RT:-jsf : no plugin interested for session 618475332531, free sess plugin info
May 22 01:57:24 01:57:23.944281:CID-0:RT:[JSF]Releasing plugin info blocks
May 22 01:57:24 01:57:23.944281:CID-0:RT:flow_first_service_lookup(): natp(0x56e712f8): app_id, 0(0).
May 22 01:57:24 01:57:23.944281:CID-0:RT:  service lookup identified service 0.
May 22 01:57:24 01:57:23.944281:CID-0:RT:  flow_first_final_check: in <ge-0/0/1.7>, out <ge-0/0/0.0>

 So here's my NAT setup:

nat {
    source {
        pool src-nat-pool20 {
            address {
                10.20.0.10/32 to 10.20.0.249/32;
            }
        }
        rule-set 20 {
            from zone 20;
            to zone untrust;
            rule 20rule {
                match {
                    source-address 10.20.0.0/24;
                    destination-address 0.0.0.0/0;
                }
                then {
                    source-nat {
                        pool {
                            src-nat-pool20;
                        }
                    }
                }
            }
    static {
        rule-set untrust-to-20 {
            from zone untrust;
            rule 20rule {
                match {
                    destination-address 1.2.3.5/32;
                }
                then {
                    static-nat {
                        prefix {
                            1.2.3.5/32;
                        }
                    }
                }
            }
        }
    }
    proxy-arp {
        interface ge-0/0/0.0 {
            address {
                1.2.3.2/32;
                1.2.3.4/32;
                1.2.3.5/32;
            }
        }
    }

Re: Windows Server 2016 MSRPC Issues

$
0
0

Does this also occour on 12.3X48-D50.6

 

We have had similar issues with MSRPC and the new windows server 2016 schemea that was loaded

Re: SRX 340 occasional panic

$
0
0

Today i got this Smiley Happy

 

Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
xhci_process_cmd_event+0x124 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801891bc sz 64
xhci_scan_ring_event+0xd8 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801894c4 sz 64
xhci_poll+0x10 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80199d30 sz 24
usbd_dopoll+0x20 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80191e68 sz 24
umass_cam_poll+0x24 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8011d1f0 sz 24
xpt_polled_action+0x70 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8012184c sz 48
dashutdown+0xa0 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207318 sz 664
boot+0x7a4 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207bf4 sz 48
panic+0x580 (0xc6e3d400,0,0x80011800,0xf8) ra 0x80781730 sz 64
trap+0x1250 (0xc6e3d400,0,0x80011800,0xf8) ra 0x80a570ac sz 144
0x80a56f14+0x198 (0xc6e3d400,0,0x80011800,0xf8) ra 0 sz 0
pid 23, process: swi7: clock
cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
badvaddr = 0x1010, pc = 0x80187fd4, ra = 0x801891bc, sr = 0x508008a3
panic: trap
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
xhci_process_cmd_event+0x124 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801891bc sz 64
xhci_scan_ring_event+0xd8 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801894c4 sz 64
xhci_poll+0x10 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80199d30 sz 24
usbd_dopoll+0x20 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80191e68 sz 24
umass_cam_poll+0x24 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8011d1f0 sz 24
xpt_polled_action+0x70 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8012184c sz 48
dashutdown+0xa0 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207318 sz 664
boot+0x7a4 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207bf4 sz 48
panic+0x580 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80781730 sz 64
trap+0x1250 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80a570ac sz 144
0x80a56f14+0x198 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0 sz 0
pid 23, process: swi7: clock
cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
badvaddr = 0x1010, pc = 0x80187fd4, ra = 0x801891bc, sr = 0x508008a3
panic: trap
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
xhci_process_cmd_event+0x124 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801891bc sz 64
xhci_scan_ring_event+0xd8 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801894c4 sz 64
xhci_poll+0x10 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80199d30 sz 24
usbd_dopoll+0x20 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80191e68 sz 24
umass_cam_poll+0x24 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8011d1f0 sz 24
xpt_polled_action+0x70 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8012184c sz 48
dashutdown+0xa0 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207318 sz 664
boot+0x7a4 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207bf4 sz 48
panic+0x580 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80781730 sz 64
trap+0x1250 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80a570ac sz 144
0x80a56f14+0x198 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0 sz 0
pid 23, process: swi7: clock
cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
badvaddr = 0x1010, pc = 0x80187fd4, ra = 0x801891bc, sr = 0x508008a3
panic: trap
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
xhci_process_cmd_event+0x124 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801891bc sz 64
xhci_scan_ring_event+0xd8 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801894c4 sz 64
xhci_poll+0x10 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80199d30 sz 24
usbd_dopoll+0x20 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80191e68 sz 24
umass_cam_poll+0x24 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8011d1f0 sz 24
xpt_polled_action+0x70 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8012184c sz 48
dashutdown+0xa0 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207318 sz 664
boot+0x7a4 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207bf4 sz 48
panic+0x580 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80781730 sz 64
trap+0x1250 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80a570ac sz 144
0x80a56f14+0x198 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0 sz 0
pid 23, process: swi7: clock
cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
badvaddr = 0x1010, pc = 0x80187fd4, ra = 0x801891bc, sr = 0x508008a3
panic: trap
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
xhci_process_cmd_event+0x124 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801891bc sz 64
xhci_scan_ring_event+0xd8 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801894c4 sz 64
xhci_poll+0x10 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80199d30 sz 24
usbd_dopoll+0x20 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80191e68 sz 24
umass_cam_poll+0x24 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8011d1f0 sz 24
xpt_polled_action+0x70 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8012184c sz 48
dashutdown+0xa0 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207318 sz 664
boot+0x7a4 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207bf4 sz 48
panic+0x580 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80781730 sz 64
trap+0x1250 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80a570ac sz 144
0x80a56f14+0x198 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0 sz 0
pid 23, process: swi7: clock
cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
badvaddr = 0x1010, pc = 0x80187fd4, ra = 0x801891bc, sr = 0x508008a3
panic: trap
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
xhci_process_cmd_event+0x124 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801891bc sz 64
xhci_scan_ring_event+0xd8 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801894c4 sz 64
xhci_poll+0x10 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80199d30 sz 24
usbd_dopoll+0x20 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80191e68 sz 24
umass_cam_poll+0x24 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8011d1f0 sz 24
xpt_polled_action+0x70 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8012184c sz 48
dashutdown+0xa0 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207318 sz 664
boot+0x7a4 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207bf4 sz 48
panic+0x580 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80781730 sz 64
trap+0x1250 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80a570ac sz 144
0x80a56f14+0x198 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0 sz 0
pid 23, process: swi7: clock
cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
badvaddr = 0x1010, pc = 0x80187fd4, ra = 0x801891bc, sr = 0x508008a3
panic: trap
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
xhci_process_cmd_event+0x124 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801891bc sz 64
xhci_scan_ring_event+0xd8 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801894c4 sz 64
xhci_poll+0x10 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80199d30 sz 24
usbd_dopoll+0x20 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80191e68 sz 24
umass_cam_poll+0x24 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8011d1f0 sz 24
xpt_polled_action+0x70 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8012184c sz 48
dashutdown+0xa0 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207318 sz 664
boot+0x7a4 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207bf4 sz 48
panic+0x580 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80781730 sz 64
trap+0x1250 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80a570ac sz 144
0x80a56f14+0x198 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0 sz 0
pid 23, process: swi7: clock
cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
badvaddr = 0x1010, pc = 0x80187fd4, ra = 0x801891bc, sr = 0x508008a3
panic: trap
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
xhci_process_cmd_event+0x124 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801891bc sz 64
xhci_scan_ring_event+0xd8 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x801894c4 sz 64
xhci_poll+0x10 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80199d30 sz 24
usbd_dopoll+0x20 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80191e68 sz 24
umass_cam_poll+0x24 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8011d1f0 sz 24
xpt_polled_action+0x70 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x8012184c sz 48
dashutdown+0xa0 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207318 sz 664
boot+0x7a4 (0xc6e3d400,0xc6ee6270,0x80121cdc,0x13c0401) ra 0x80207bf4 sz 48
panic+0x580 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80781730 sz 64
trap+0x1250 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0x80a570ac sz 144
0x80a56f14+0x198 (0xc6e3d400,0x3,0x8000cfe4,0x67) ra 0 sz 0
pid 23, process: swi7: clock
cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
badvaddr = 0x1010, pc = 0x80187fd4, ra = 0x801891bc, sr = 0x508008a3
panic: trap
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801ee088 ADR 0xeac19ef0
SR 8f043a00 CR 8f040e98 SP 0x8010013c boundary 0x7
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 80dd8568 CR eac1c098 SP 0 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s
Cannot dump. No dump device defined.
(da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0
ktlbmiss: PC 0x801edf54 RA 0x801891bc ADR 0x1010
SR 13 CR 80a70000 SP 0x80a70000 boundary 0x80a58098
panic: kernel stack overflow
cpuid = 0
Uptime: 19h42m13s

Re: Screen logs

$
0
0

Hello,

 

            I don't know if you managed to find the solution to this old problem but for the sake of documentation you will need to check if your logging mode is stream or event mode as the logs can be only shown in the J-WEB when you are using only event mode as in this mode the logs are processed in the routing engine unlike stream mode it's sent directly from data plane and not passing through the routing engine.

 

Best Regards,

Kareem Maher

Re: 1-to-1 NAT setup to untrust /24?

$
0
0

Your source nat pool is a private address, for internet acces this is generally a public address as private addresses are not routable.  The pool is the address that your source gets changed to before leaving the SRX.

pool src-nat-pool20 {
            address {
                10.20.0.10/32 to 10.20.0.249/32;
            }
        }

For your static nat rule you are not changing the address at all but using the same address as both the match and the nat address.  Typically you match on the inbound public address and nat this to the desired internal address.

 

rule 20rule {
                match {
                    destination-address 1.2.3.5/32;
                }
                then {
                    static-nat {
                        prefix {
                            1.2.3.5/32;
                        }

 

 


NAT via snmp

$
0
0

Good Day,

Has anyone setup or know how NAT graphing can be achieved with the use of SNMP. Some detail that can be extracted using SNMP for example, pool utilization, number of translation and current traslations etc. Similar detail that can be seen as on JWEB. Please no suggestions or links, only if you know how or know of documentation you used sucsessfully. The platform in use is an SRX5800 and solarwinds server.

 

Thanks,

Re: 1-to-1 NAT setup to untrust /24?

$
0
0

Okay, but all I want to do is route all traffic from the /24 on ge0/0/1.7, which is VLAN 10.20.1.0 all to one public static IP of 1.2.3.5, so do I really need a pool at all?

 

Once I get that working, I want to similarly route the /24 on ge0/0/1.6 VLAN 10.10.1.0 all to one public static IP of 1.2.3.4 and so on for each respective VLAN.

SRX boot error CHASSISD_IOCTL_FAILURE

$
0
0

hello,

 

I have a SRX 550 wiout any module in it. when we boot it, we have this message poping at the start :

 

CHASSISD_IOCTL_FAILURE: readpcireg: ioctl failed for PCIOCREAD (Operation not supported by device)

 

Some one have a idea on what can cause this failure ? Do this unit need to be replace ?

 

Thx

Re: is it Sky ATP create realm down?

$
0
0

Hi there,

 

Juniper Networks’ User Experience team is conducting user research on Sky Advanced Threat Prevention (SkyATP). To ensure that we build a simple, reliable, and efficient interface, we need your input. If you have experience with SkyATP,  please join our study.

 

Study Details:

  • The usability study will last 1.5 hours, and we will use GoToMeeting to hold the study remotely
  • It will take place at your convenience between May 23rd – June 11th
  • You will receive a $100 Amazon gift card as a token of our appreciation for your participation (subject to your company’s gift policy)

 

To participate in the study, please select a convenient time!

 

Thanks,

Natasha

 

 

Natasha Shimuk

User Experience Researcher | Juniper Networks

Re: SRX 300 series with Security Subscription and Junos Space

$
0
0

Hi there,

 

Juniper Networks’ User Experience team is conducting user research on Sky Advanced Threat Prevention (SkyATP). To ensure that we build a simple, reliable, and efficient interface, we need your input. If you have experience with SkyATP,  please join our study.

 

Study Details:

  • The usability study will last 1.5 hours, and we will use GoToMeeting to hold the study remotely
  • It will take place at your convenience between May 23rd – June 11th
  • You will receive a $100 Amazon gift card as a token of our appreciation for your participation (subject to your company’s gift policy)

 

To participate in the study, please select a convenient time!

 

Thanks,

Natasha

 

 

Natasha Shimuk

User Experience Researcher | Juniper Networks

Viewing all 17645 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>