| 00:04.21 | *** join/#utah bmidgley (~bmidgley@c-24-10-224-87.hsd1.ut.comcast.net) |
| 00:06.29 | *** join/#utah mabes_ (~mabes@66.236.74.194.ptr.us.xo.net) |
| 01:53.25 | *** join/#utah mabes (~mabes@runner.fttp.xmission.com) |
| 02:46.22 | *** join/#utah sshaw (~decriptor@53.250.sfcn.org) |
| 03:42.20 | mheath | "<Sargun_Screen> So, arey ou balancing via BGP?" |
| 03:42.50 | mheath | I'm kinda shocked thats a question. I'm sheltered by our triple-redundancy, BGP peered, disaster failover |
| 03:52.48 | *** join/#utah tiwula (~lane@63.225.228.210) |
| 05:11.52 | *** join/#utah har-od (~dshipp@c-71-195-218-161.hsd1.ut.comcast.net) |
| 06:32.38 | eightyeight | goozbach: i do |
| 07:29.16 | *** join/#utah UnknownU (~UnknownU3@gateway/tor-sasl/unknownu) |
| 07:44.42 | *** part/#utah UnknownU (~UnknownU3@gateway/tor-sasl/unknownu) |
| 09:18.08 | Sargun_Screen | mheath: Yes, but you probably don't know how many bits an ASN is |
| 09:18.16 | Sargun_Screen | "Disaster failover" doesn't mean anything |
| 09:18.40 | Sargun_Screen | and you could have 80 redundancies for all I care... you still need a handful of humans to run it |
| 09:29.41 | Sargun_Screen | [I'm being sarcastic, please don't laugh at me, but with me] |
| 13:55.00 | mheath | Sargun_Screen, I'm not a network engineer, I'm in IT planning and management. |
| 13:55.53 | mheath | ANd no, I don't know how many bits are in an ASN. But I do know what an ASN is, since I recently processed a change associated with us discovering that one of we were erroneously using someone elses ASN for one of our networks. |
| 13:57.11 | mheath | And yes, we have networking teams in 4 countries. Even with fully configured BGP and triple redundancies, a lot of stuff goes wrong. |
| 13:57.44 | mheath | I've never done any serious network configuration (I only have my CCNA), but BGP sounds like a PITA to me, to keep working perfectly. |
| 13:59.46 | mheath | Sargun_Screen, but I didn't want to get into all of that. I was just noting, with mild curiorsity, that I didn't even know "do you use BGP?" was even a question that needed asking for a serious network. |
| 14:48.14 | *** join/#utah bmidgley (~bmidgley@c-24-10-224-87.hsd1.ut.comcast.net) |
| 16:04.44 | *** join/#utah sshaw (~decriptor@53.250.sfcn.org) |
| 17:13.03 | *** join/#utah findlay (~justin@library.xwi.xmission.com) |
| 17:41.12 | *** join/#utah tiwula (~lane@63.225.228.210) |
| 17:44.51 | *** join/#utah cedwards (~cedwards@unaffiliated/zelut) |
| 17:56.34 | *** join/#utah har-od (~dshipp@65.127.208.182) |
| 18:00.16 | *** join/#utah mabes (~mabes@runner.fttp.xmission.com) |
| 19:46.51 | Sargun_Screen | mheath: BGP is pretty simple/easy |
| 19:47.05 | Sargun_Screen | but, lots of companies choose not t odo their own BGP |
| 19:47.15 | Sargun_Screen | because establishing relationships is difficult. |
| 19:47.52 | mheath | shrugs |
| 19:48.20 | mheath | I just know its problematic at best, and can lead to routing loops, etc. |
| 19:48.38 | mheath | I know thats what our networking team spends half their time troubleshooting, on major changes - route propegation, route preference, etc. |
| 19:50.54 | mheath | I would never have the patience to be a networking engineer. |
| 20:12.38 | Sargun_Screen | BGP shouldn't lead to routing loops. |
| 20:13.01 | Sargun_Screen | mheath: Unfortunately, most companies whose job isn't primarily networking, tend to skimp on network infrastructure |
| 20:13.31 | mheath | We're far from primarily networking |
| 20:13.47 | mheath | and we spend about $150,000/month just on the circuits/service |
| 20:31.05 | Sargun_Screen | That's nothing. |
| 23:59.10 | *** join/#utah eggyknap (~jtolley@unaffiliated/eggyknap) |