Re: [j-nsp] Shaping on regular PIC

2009-12-17 Thread Ramesh Karki
Hi Alex,

Thanks for your response. There is no option like GTS (Cisco feature) for
traffic shaping on juniper regular PIC. Current i have 4FE regular PIC, need
to shaped the traffic and i am looking for configuring exact scheduling
matching all traffic with best effort for 64K and delay buffer upto 128K.

Thank You

Regards,
Ramesh

On Tue, Dec 15, 2009 at 5:21 PM, Ramesh Karki rameshka...@gmail.com wrote:

 Hi experts,

 I m trying to shape traffic on Regular 4FE-PIC  with JunOS 9.2. I think
 shaping on regular PIC can only be done using DiffServe queue.

 if someone have already done or configured, configuration will be really
 appreciated.

 Thank you,

 Ramesh



___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Urgent

2009-12-17 Thread Dilip Srivastava
Hi Shekhar

u can type this question on juniper.net site

u will get the answer proper way

thanks
Dilip

On Thu, Dec 17, 2009 at 11:09 AM, chandrasekaran iyer
shekar1...@gmail.comwrote:

 Hi,

 How to enable DHCP server in MX240:MX480:MX960 platforms

 --
 Thanks with regards

 Shekar.B
 --
 ___
 juniper-nsp mailing list juniper-nsp@puck.nether.net
 https://puck.nether.net/mailman/listinfo/juniper-nsp




-- 
Thanks  Regards

Dilip Kumar Srivastava
Engineer Wipro
9650410022
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Urgent

2009-12-17 Thread Masood Shah
Here you go...
 
http://www.juniper.net/techpubs/software/junos/junos91/swconfig-system-basics/configuring-a-dhcp-server.html
 
 



From: juniper-nsp-boun...@puck.nether.net on behalf of chandrasekaran iyer
Sent: Thu 12/17/2009 6:39
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Urgent



Hi,

How to enable DHCP server in MX240:MX480:MX960 platforms

--
Thanks with regards

Shekar.B
--
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] PE Monitoring Tools

2009-12-17 Thread Jason Alex
Dear All,
 Kindly i am working in a Service Provider environment
We have daily upgrade in the network and moving customer from one PE to
another PE

Is there is any Management tool can check the status of the Customer (VRF)
before and after the migration of the customer to another PE ?

This can be useful in checking the customer's status after moving the
configuration from one PE to another

Any advice ?

Thanks In Advance

Regards
Jason
CCIE#24775
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] cflowd/netflow exporting broken (removed?) SRX series on JunOS 10.0R2.10

2009-12-17 Thread Chris Kawchuk
Hi All,

Anyone else's netflow simply stop working after they upgraded an SRX-series 
to JunOS 10.0R2? (Specifically on an SRX650, but might appliy to any of the 
srx-sme line, SRX240, etc...)

Worked fine under 10.0 R1. (shrug.. and 9.6R1, and 9.6 R2...etc...)

@CLGR01-CR01 show configuration forwarding-options 
sampling {
traceoptions {
file sampling-log size 100m files 10 world-readable;
}
input {
rate 10;
run-length 9;
max-packets-per-second 7000;
}
family inet {
output {
flow-server 10.6.0.13 {
port 9996;
autonomous-system-type origin;
source-address 10.6.0.21;
version 5;
}
}
}
}

... nothing in the log file.. =P

and


interfaces {
ge-0/0/1 {  
unit 0 {
family inet {
filter {
input packetmode-ipv4;
}   
sampling {
input;
}   
address removed.to.protect.the.guilty.x.x.x.225/29;
}   
}   
}   

Yep.. sampling pretty much everything coming in...

(And yes, this box is in packet mode for the majority of it's interfaces... 
using it as a nice JunOS BGP core router in the 1Gbps/sec range...)

- Chris.


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Urgent

2009-12-17 Thread Pekka Savola

On Thu, 17 Dec 2009, Masood Shah wrote:

Here you go...

http://www.juniper.net/techpubs/software/junos/junos91/swconfig-system-basics/configuring-a-dhcp-server.html


According to that doc, DHCP server functionality is only available in 
J-series, not MX series.





From: juniper-nsp-boun...@puck.nether.net on behalf of chandrasekaran iyer
Sent: Thu 12/17/2009 6:39
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Urgent



Hi,

How to enable DHCP server in MX240:MX480:MX960 platforms

--
Thanks with regards

Shekar.B
--
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp



___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Stealing from MX firewall jtree space

2009-12-17 Thread Richard A Steenbergen
On Wed, Dec 16, 2009 at 11:37:06PM +0200, Krasimir Avramski wrote:
 What about terminating bgp neighbor in inet.0 with bgp operating over
 a rib-group under family inet:
 
 protocols bgp
 group xy {
 neighbor x.x.x.x {
 import xy;
 family inet {
 unicast {
 rib-group xy;
 }
 }
 }
 }
 
 Then import routing-policy xy states:
 
 policy-statement xy
 term 1 {
 from community to_inet_0;
 to rib inet.0;
 then accept;
 }
 term 2 {
 to rib inet.0;
 then reject;
 }
 term 3 {
 from community to_vrf;
 to rib vrf.inet.0;
 then accept;
 }
 term 4 {
 to rib vrf.inet.0;
 then reject;
 }

Hrm so I was testing this, and noticed an odd behavior... When you
reject the route from inet.0 (for example, like you're doing in term 2)
it also rejects the route in all other ribs, even if you explicitly
accept them (like in your term 3). Term order doesn't seem to matter
(putting term 3 before term 2 doesn't help), and it only happens to
routes that you reject to inet.0 (rejecting the routes to another rib
doesn't reject it from inet.0). Other attribute modifications appear to
work as expected, I only see this problem when you reject the route, but
setting localpref to 0 doesn't help if this is a more specific route so
it isn't a true replacement for a working reject into inet.0.

The multi-topology routing features are much closer to what I'm actually
trying to accomplish, but unfortunately it is missing pretty much every
feature that would be needed to do anything useful with it (ability to
import from another topology, ability to use policy-statements to
control your protocol import, etc). Sigh, no way to win. :)

-- 
Richard A Steenbergen r...@e-gerbil.net   http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp