Hi to all!
I have question
Is responsible for what this process?
PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND
38 root1 -36 -155 0K16K WAIT 279:04 31.25% swi3: ipopt
ip6opt
Without specific reasons for increased load average and cpu, will clarify
at
Dear group,
Does anyone has the files from the CD that comes with this text book
(JNCIE-M Study Guide published by Sybex)? I recently bought the book from
Amazon, but the CD is not included. This book was released few years ago,
and I can no longer buy brand new copy anymore. I do not think there
Awesome, thank you very much :-)
Both work great!
Scott H.
On 9/9/14, 9:32 PM, Ben Dale wrote:
On 10 Sep 2014, at 7:54 am, Scott Harvanek scott.harva...@login.com wrote:
This is a silly/OCD question;
I've faced this before and I can't recall how it was prettied up...
If I recall there is
I have placed copies of the configs files for case studies and the chapter on
google drive:
https://drive.google.com/folderview?id=0ByOb4tf4FcWGd2VlNHRoNDNyVmMusp=sharing
HTHs.
-Original Message-
From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of
Huan Pham
Hi Aqeel - thanks for the reply.
Agree 100% - the problem is, we only seem to be getting power to FPC0 from
one PEM... have a look below (and also note that FPC1 is fine, as are the
rest of the FPCs).
The question is - are we looking at a PEM fault here, or a midplane fault?
As per previous
Pins 'seem' ok from a visual inspection.
Our support vendor is involved, however because of reasons I'm getting the
feeling we're now playing whack-a-mole with randomly replacing components,
as opposed to actually using the results from previous tests such as moving
the FPC to guide us towards a
6 matches
Mail list logo