RE: Managing CE eBGP details & common/accepted CE-facing BGP practices

> Have a read after "Communities accepted from customers" in > the RADB WHOIS for AS3356 for a fairly comprehensive example. > Other's might have better examples, but I've often used this > one as being pretty good. > (whois -h whois.radb.net AS3356) You can also read this here:

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

On 21/12/2008, at 2:22 PM, Justin Shore wrote: While I'm sure this could be easily stored in a spreadsheet I think the best piece of advice I ever saw RE network management, is teach your network ops people basic SQL. Spreadsheets work OK for one- off calculations, use SQL for any sort of d

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

Evening, Justin. Thanks for the reply. Justin M. Streiner wrote: You could certainly store all of the relevant config details in a database of some sort, and it certainly can't hurt to do so. Same goes for backing up your device configurations - always a good idea. As far as storing things

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

On 22/12/2008, at 10:47 AM, Danny Thomas wrote: I'd also like to add a feature that recognizes the significant blocks in a config and store in a database so you can do queries like "when was vlan777 modified" This sounds like a job for captain SNMP(trap/inform) or RADIUS or TACACS+! --

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

Suresh Ramasubramanian wrote: On Sun, Dec 21, 2008 at 8:31 AM, Justin Shore wrote: I should have said it earlier when I mentioned config backups. I'm already a heavy user of RANCID, archiving my configs hourly. Been using it since right around v2.0-2.1 which would be several years ago (fe

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

On Sun, Dec 21, 2008 at 8:31 AM, Justin Shore wrote: > I should have said it earlier when I mentioned config backups. I'm already > a heavy user of RANCID, archiving my configs hourly. Been using it since > right around v2.0-2.1 which would be several years ago (feels like a > lifetime). So my

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

Suresh Ramasubramanian wrote: Heck, you could store all that in Rancid .. even cvs/svn I should have said it earlier when I mentioned config backups. I'm already a heavy user of RANCID, archiving my configs hourly. Been using it since right around v2.0-2.1 which would be several years ago (

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 20, 2008, at 8:11 PM, Suresh Ramasubramanian wrote: On Sun, Dec 21, 2008 at 6:52 AM, Justin Shore wrote: Does anyone have any preferred ways to manage their customer-facing BGP details? I'm thinking about the customer's ASN (SP assigned

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

On Sun, Dec 21, 2008 at 6:52 AM, Justin Shore wrote: > Does anyone have any preferred ways to manage their customer-facing BGP > details? I'm thinking about the customer's ASN (SP assigned private ASN or > RIR assigned ASN), permitted prefixes, etc? While I'm sure this could be > easily stored i

Re: Managing CE eBGP details & common/accepted CE-facing BGP practices

On Sat, 20 Dec 2008, Justin Shore wrote: Does anyone have any preferred ways to manage their customer-facing BGP details? I'm thinking about the customer's ASN (SP assigned private ASN or RIR assigned ASN), permitted prefixes, etc? While I'm sure this could be easily stored in a spreadsheet

Managing CE eBGP details & common/accepted CE-facing BGP practices

Does anyone have any preferred ways to manage their customer-facing BGP details? I'm thinking about the customer's ASN (SP assigned private ASN or RIR assigned ASN), permitted prefixes, etc? While I'm sure this could be easily stored in a spreadsheet I'm not sure if there is any merit to stor