Re: [j-nsp] Best route reflector platform
> Date: Wed, 17 Apr 2013 13:34:29 -0500 > From: Richard A Steenbergen > Subject: Re: [j-nsp] Best route reflector platform > I begged them to do this right when that box first came out, but there > were no takers. They cripple it in software so the XRE can't be made to > run rpd stand-alone and act as a route reflector. Weirdly enough, I spotted these (new) guys in the Juniper GPL: * MX240-RR-AC-B: MX240 route reflector AC bundle * S-RR: Route Reflector (RR) Software license for JCS1200 Spacewise I'd opt for the MX240, but an XRE would be better indeed. There's also SRX-BGP-ADV-LTU for "Advanced BGP License for SRX 650 only" (Route Reflector), though I wonder how far it'll scale... Anybody try to see if a Route Reflector in Junosphere's VJX worked ? Kind regards, JP Velders ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] SNMP on logical-system fxp0
I've encountered many other troubles in the past trying to do this in the lab.Lat time I tried it NSR broke?!? I agree this should be pretty standard stuff but it seems to break lots of features. We tend to put everything in inet.0 and point static routes out fxp0 for any traffic initiated by the RE. For requests inbound to the RE, we NAT the source on the routers used as the gateway off fxp0. That way all inbound requests look like they're from gateway. No return routes required. Serge From: Klaus Groeger To: Juniper NSP Sent: Saturday, April 20, 2013 11:23:20 AM Subject: Re: [j-nsp] SNMP on logical-system fxp0 Hi the fxp0 interface is bound to the RE, witch always resides in the first logical system and ist bound to the default routing table or master table, which is inet.0. All route lookups regarding the RE start in inet.0. Just put all your productive interfaces in a separate virtual router and you are done. Klaus --- ___ 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] SNMP on logical-system fxp0
Hi the fxp0 interface is bound to the RE, witch always resides in the first logical system and ist bound to the default routing table or master table, which is inet.0. All route lookups regarding the RE start in inet.0. Just put all your productive interfaces in a separate virtual router and you are done. Klaus --- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] SNMP on logical-system fxp0
Sigh. High end SRX. On Apr 20, 2013 8:31 AM, "Nicholas Oas" wrote: > Hmm. Or set a route to the mgt net in the default table whose next hop is > the mgt table? I've had to do this on high end sex to get traffic loss to > go out the data plane. > On Apr 19, 2013 7:32 PM, "OBrien, Will" wrote: > >> Agreed. That's the way to do it. >> >> On Apr 19, 2013, at 5:37 PM, Brandon Ross >> wrote: >> >> > On Fri, 19 Apr 2013, Chip Marshall wrote: >> > >> >> So, I have an MX5 with it's fxp0 management interface connect to >> >> one network, which I've placed in a logical-system so it can have >> >> it's own default route for out-of-band management. >> > >> > [snip] >> > >> >> The problem is the replies to SNMP queries are being routed out >> >> using the main system's routing table, not the routing table of >> >> the logical-system. I have confirmed this with packet captures. >> > >> > Use the default logical-system for management and put your production >> stuff in a new logical-system. >> > >> > -- >> > Brandon Ross Yahoo & AIM: >> BrandonNRoss >> > +1-404-635-6667ICQ: >> 2269442 >> > Schedule a meeting: https://doodle.com/brossSkype: >> brandonross >> > ___ >> > 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] SNMP on logical-system fxp0
Hmm. Or set a route to the mgt net in the default table whose next hop is the mgt table? I've had to do this on high end sex to get traffic loss to go out the data plane. On Apr 19, 2013 7:32 PM, "OBrien, Will" wrote: > Agreed. That's the way to do it. > > On Apr 19, 2013, at 5:37 PM, Brandon Ross > wrote: > > > On Fri, 19 Apr 2013, Chip Marshall wrote: > > > >> So, I have an MX5 with it's fxp0 management interface connect to > >> one network, which I've placed in a logical-system so it can have > >> it's own default route for out-of-band management. > > > > [snip] > > > >> The problem is the replies to SNMP queries are being routed out > >> using the main system's routing table, not the routing table of > >> the logical-system. I have confirmed this with packet captures. > > > > Use the default logical-system for management and put your production > stuff in a new logical-system. > > > > -- > > Brandon Ross Yahoo & AIM: > BrandonNRoss > > +1-404-635-6667ICQ: > 2269442 > > Schedule a meeting: https://doodle.com/brossSkype: > brandonross > > ___ > > 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
