[j-nsp] Good practice for EX-series interface config management
Hi all, I'm curious about what people have found is the best way to manage interface configurations on EX-series devices. There are a number of ways to apply configuration to interfaces -- direct to each interface, using interface-ranges etc. We've been burnt a couple of times with people making adjustments to interface-ranges and not paying close enough attention to the net effect of their change (e.g. leaving out all interfaces on a switch). Direct application of config to interfaces, while precise, kind of feels 'wrong' as JUNOS provides more elegant ways to achieve the same end result. Maybe in carefully planned, static environments where access port VLAN assignments and other port specific configs rarely change, interface-ranges are more workable. Or maybe we're just doing it wrong. I'm hoping that this sparks some discussion. What works best for you? Cheers, Dale ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Good practice for EX-series interface config management
On Tue, Nov 2, 2010 at 2:31 PM, Dale Shaw dale.shaw+j-...@gmail.com wrote: Hi all, I'm curious about what people have found is the best way to manage interface configurations on EX-series devices. There are a number of ways to apply configuration to interfaces -- direct to each interface, using interface-ranges etc. We've been burnt a couple of times with people making adjustments to interface-ranges and not paying close enough attention to the net effect of their change (e.g. leaving out all interfaces on a switch). Direct application of config to interfaces, while precise, kind of feels 'wrong' as JUNOS provides more elegant ways to achieve the same end result. Maybe in carefully planned, static environments where access port VLAN assignments and other port specific configs rarely change, interface-ranges are more workable. Or maybe we're just doing it wrong. I'm hoping that this sparks some discussion. What works best for you? Cheers, Dale We use apply group to manage EX interfaces. In case we change settings in a specific group, it will only affect those member interfaces who explicitly have the group configed. -- Michel~ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Good practice for EX-series interface config management
On Nov 2, 2010, at 5:31 PM, Dale Shaw dale.shaw+j-...@gmail.com wrote: Hi all, I'm curious about what people have found is the best way to manage interface configurations on EX-series devices. There are a number of ways to apply configuration to interfaces -- direct to each interface, using interface-ranges etc. We've been burnt a couple of times with people making adjustments to interface-ranges and not paying close enough attention to the net effect of their change (e.g. leaving out all interfaces on a switch). Direct application of config to interfaces, while precise, kind of feels 'wrong' as JUNOS provides more elegant ways to achieve the same end result. Maybe in carefully planned, static environments where access port VLAN assignments and other port specific configs rarely change, interface-ranges are more workable. Or maybe we're just doing it wrong. I suppose it depends on what you use the switch for. We mostly use them as access in hosting environments. I like using config groups where you can group anything related to a particular customer together. But that's just my preference. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
