Re: [j-nsp] Code upgrade to 10.4R4.5
On Wed, May 11, 2011 at 3:11 PM, Cyn D. cynthia_...@yahoo.ca wrote:
Will this be a none (no config loaded at all) and all (if loaded then it is
intact) situation? What I don't want to see is configuration loaded
partially and the lines that are not compatible are missing. When you go
I have encountered quite a few upgrade problems where only part of the
configuration loaded. Verify is by no means a fool-proof check, and
the fool in this case is not you, it's the developers. For example,
an upgrade from EX4200 9.2(?) to 9.3(?) or there-abouts will break if
you have virtual-chassis { pre-provisioned; } configured, because the
syntax changes to preprovisioned (no hyphen), yet this is not caught
by verify. The box will be unusable after it upgrades. EX boxes,
and their spectacular upgrade failures, have justified my OOB
facilities many times over in the past couple of years.
Always have a rain plan. OOB network, remote hands, let router be
down until you can dispatch an employee, whatever.
--
Jeff S Wheeler j...@inconcepts.biz
Sr Network Operator / Innovative Network Concepts
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Code upgrade to 10.4R4.5
On Thu, May 12, 2011 at 04:27:55AM -0400, Jeff Wheeler wrote: syntax changes to preprovisioned (no hyphen), yet this is not caught by verify. The box will be unusable after it upgrades. EX boxes, and their spectacular upgrade failures, have justified my OOB facilities many times over in the past couple of years. Always have a rain plan. OOB network, remote hands, let router be down until you can dispatch an employee, whatever. I've traditionally been more fond of modular chassis-based switches rather than stackable/virtual-chassis switches. A few years ago before EX8200 existed we made the choice to go with EX4200 virtual-chassis, but some cons we thought of were related to the need for lots of extra cabling and OOB resources: 1. 18 power cords vs. 4 2. 9 OOB console server ports vs. 2 3. 9 OOB ethernet ports vs. 2 The last two are particularly troubling, because if you don't have OOB console access to every member of a virtual-chassis, it is impossible to recover from a situation like above remotely. We've already experienced this a couple times, once related to flash corruption on a line-card member, and another time when a software issue crashed line-cards with uplink-modules. I hope vendors would consider these types of issues when designing stackable-type switch architectures. It would be nice to have some built-in way to aggregate/interconnect the console ports (in such a way that didn't require the switch's software or flash disk to be functioning correctly for the consoles to be accessable across the daisy chain console connections.) It gets expensive providing console server ports for every 48-port member switch. Maybe an RS-485 serial console bus would work? ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] mpls question
The EX doesn't support L3VPN/VRF. You'd have to use an MX80 at the least. You could do pseudowires per customer though. On Thu, May 12, 2011 at 7:31 AM, Johan Borch johan.bo...@gmail.com wrote: Hi, I have a question regarding MPLS on ex-series. I have a situation where i need to connect several data centers together. I have never worked with MPLS before but my idea is to use MPLS to transport VLANs between the data centers. An example: a customer is located in it's own VRF and we use VLAN/RVI for servers and client networks, now I wan't to connect my core in DC1 to my core in DC2, is MPLS the right way to go? The data centers will be connected with multiple connections. I read somewhere that I can't use family ccc if the vlan has an RVI, is that correct? Regards Johan ___ 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] mpls question
You could use the EX to do this. However, you will need additional EXs to connect to the existing switches with the RVIs. Terminate your WAN into a WAN EX (assuming its ethernet handoff) and then connect this EX into your existing infrastructure via ethernet trunk. You have two options on the WAN EX: 1. Q-in-Q 2. Pseudowires A more robust and feature-rich options would be the MX. Then you could provide VPLS and Layer 3 services at the edge of your data center of your L2 WAN... - Original Message - From: Johan Borch johan.bo...@gmail.com To: juniper-nsp@puck.nether.net Cc: Sent: Thursday, May 12, 2011 6:31 AM Subject: [j-nsp] mpls question Hi, I have a question regarding MPLS on ex-series. I have a situation where i need to connect several data centers together. I have never worked with MPLS before but my idea is to use MPLS to transport VLANs between the data centers. An example: a customer is located in it's own VRF and we use VLAN/RVI for servers and client networks, now I wan't to connect my core in DC1 to my core in DC2, is MPLS the right way to go? The data centers will be connected with multiple connections. I read somewhere that I can't use family ccc if the vlan has an RVI, is that correct? Regards Johan ___ 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] mpls question
The EX doesn't support vpls either. The implementation described in the pdf also uses an MX for the mpls vpn portion. On Thu, May 12, 2011 at 9:34 AM, Cristiano Monteiro crmont...@gmail.comwrote: Hi, Maybe this link helps you http://www.juniper.net/us/en/local/pdf/implementation-guides/8010050-en.pdf Best Regards, Cristiano Monteiro 2011/5/12 Johan Borch johan.bo...@gmail.com Hi, I have a question regarding MPLS on ex-series. I have a situation where i need to connect several data centers together. I have never worked with MPLS before but my idea is to use MPLS to transport VLANs between the data centers. An example: a customer is located in it's own VRF and we use VLAN/RVI for servers and client networks, now I wan't to connect my core in DC1 to my core in DC2, is MPLS the right way to go? The data centers will be connected with multiple connections. I read somewhere that I can't use family ccc if the vlan has an RVI, is that correct? Regards Johan ___ 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] mpls question
Hi I think the pdf is still a good design but as the rest of the guys said is only available on MX platforms. Today DCI (Datacenter Interconnection) is a big challenge, applications such as vmotion requires the same subnet be extended trough many sites. VPLS is one of the options as well MPLS L2VPN or proprietary stuff like OTV from Cisco. I´m not aware of another operational option from Juniper besides VPLS. However I saw in the last year some efforts from Juniper guys to solve the problem with a new technology BGP MAC VPLS. It still a draft and I didn´t see around in the last Junos Versions. Maybe we can see new developments soon. See draft below http://tools.ietf.org/html/draft-raggarwa-mac-vpn-01 Regards, Cristiano Monteiro 2011/5/12 Johan Borch johan.bo...@gmail.com Thanks for all replies! Interesting document, is the design described in the document still a good design today and a few year ahead? :) Regards Johan On Thu, May 12, 2011 at 3:34 PM, Cristiano Monteiro crmont...@gmail.comwrote: Hi, Maybe this link helps you http://www.juniper.net/us/en/local/pdf/implementation-guides/8010050-en.pdf Best Regards, Cristiano Monteiro 2011/5/12 Johan Borch johan.bo...@gmail.com Hi, I have a question regarding MPLS on ex-series. I have a situation where i need to connect several data centers together. I have never worked with MPLS before but my idea is to use MPLS to transport VLANs between the data centers. An example: a customer is located in it's own VRF and we use VLAN/RVI for servers and client networks, now I wan't to connect my core in DC1 to my core in DC2, is MPLS the right way to go? The data centers will be connected with multiple connections. I read somewhere that I can't use family ccc if the vlan has an RVI, is that correct? Regards Johan ___ 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
