Good morning.
This just started happening to me with 1 of my SRX100's (brand new, H2, etc.) It has 1 ipsec tunnel, NAT, nothing special that an SSG5 can't do. But it comes with the added benefit of spurious meltdowns.
I'm an SRX amateur, so it is entirely possibly that I don't know what I am doing.
Not being able to copy-paste configs doesn't help ^^;
| Serial Number: | BZ4915AFXXXX | |
| Host Name: | ginzaXXXXX | |
| Software Version: | JUNOS Software Release [12.1X46-D40.2] | |
| Bios Version: | 2.8 | |
| System Up Time: | 1 day(s) 14:42 since 2016-04-04 23:33:45 GMT+9 | |
| System Time: | 2016-04-06 14:16:35 GMT+9 |
When it melts down, there's nothing logged that I can see, the tunnel drops and telnet becomes completely unresponsive, sometimes it recovers in a few minutes, sometimes it takes 20+. After being up for 30 days, it just started doing this.
Searching this forum shows that this has been going on for a couple of years with no effective solution beyond going back to now discontinued SSG5's.
The only thing of interest I can find is it complaining about the Routing Engine 0 being warm. However, I can't see 64'C being noteworthy in a fanless router.
I also see people saying what does "show chassis forwarding" etc do. Minor problem, when it is unresponsive, it is serious about it and it remains that way until recovery.
The GUI shows the control cpu as 100%, which people post as being "inaccurate, use the CLI" which sort of defeats the purpose of having a GUI.
So,
1) Where do I really look *after* it has recovered from a meltdown.
2) What is the real solution? (Since going back to SSG's isn't possible now.)