Howdy list,
I experienced a problem today with an Adaptive Services PIC running Link
Services on a Juniper M10i. The PIC is being used to support MLPPP bundled
T1 links. The M10i is currently configured with 2 adaptive services cards
for redundancy.
The setup had been working well for quite a w
I've come across a similar issue to this one with an SSG20. When you
do eventually get some console access to the device, check the event
log for messages such as "Switch error: get phy register (dev 8, reg
4) fail". If this is the same problem I was having, then there was a
patch built o
Thank you, this fixed the issue /
On Wed, Mar 11, 2009 at 12:02 AM, Arda Balkanay wrote:
> You have configured interface fe-5/2/2.100 but used fe-5/2/2.600 at
> l2circuit that's why you get " Mar 10 16:52:06.832065 [l2ckt_vc_update]
> Failure to create/update vc 2.2.2.2:999 --> interface not pres
Tim Eberhard wrote:
Is the firewall itself freezing or is it just not passing traffic?
I understand step 1 when working with a remote device like that is
typically have the customer reboot it to see if that restores service
but is it really frozen?
You could be having interface issues (I see
Hi,
Both DPCE-R and DPCE-R-Q present 8 queues per port accordingly to the "MX DPC
Guide".
Is it hardware queues per physical port?
Or is it 8 queues per logical port (per instance, for a C-VLAN)?
In another document it's said that the DPC-R-Q can manage up to 64.000 queues
per card
UUGGGHH,
major problem for myself over here. I have installed a brand new SSG140
firewall at a client and for some reason it keeps freezing and will not
pass traffic. We are never onsite and can't get console messages or
troubleshoot while it's down. (i'm putting a laptop attached to the
cons
> What I meant was the M120 stopped receiving routes(IGP) from
> its upstream router;
>
> I've tried the term "everything else" thing but didn't work
> out. Also tried this, didn't work either. Looks like the last
> term has to use master routing instance.
>
> filter classify-customers {
> t
What I meant was the M120 stopped receiving routes(IGP) from its upstream
router;
I've tried the term "everything else" thing but didn't work out. Also tried
this, didn't work either. Looks like the last term has to use master routing
instance.
filter classify-customers {
term isp1-customers
Looks obvious - there's always a default term at the end
of a firewall filter to reject anything that gets that
far.
So try adding a 3rd term:
> filter classify-customers {
> term isp1-customers {
> from {
> source-address {
> 10.1.1
On Wed, Mar 11, 2009 at 1:49 PM, ying zhang wrote:
> Hi list,
> Tried to use source-based forwarding on a M120. I created two OTHER routing
> instances: instance-1 and instance-2. Then apply a filter on an M120
> interface which connected to an upstream router.
> If I do this:
> filter c
Hi list,
Tried to use source-based forwarding on a M120. I created two OTHER routing
instances: instance-1 and instance-2. Then apply a filter on an M120 interface
which connected to an upstream router.
If I do this:
filter classify-customers {
term isp1-customers {
f
Hi all
On my side I have a some Jseries running 9.3 (R1 not R2) with only 256Mb of
Flash without problem
As I can remember, the upgrade has done using the command:
"request system storage cleanup"
And
"request system software add no-copy unlink - reboot"
--- JUNOS 9.3R1.7 built 2008-11-12
You have configured interface fe-5/2/2.100 but used fe-5/2/2.600 at
l2circuit that's why you get " Mar 10 16:52:06.832065 [l2ckt_vc_update]
Failure to create/update vc 2.2.2.2:999 --> interface not present" error.
It says "interface does not exist" ...
On Wed, Mar 11, 2009 at 2:14 AM, Dinesh wr
13 matches
Mail list logo
