On 9-May-2006, at 08:29 , Alastair Johnson wrote:
200 : customer 175 : private peering 170 : public peering 150 : domestic transit 130 : international transit
When building a list like this it can sometimes be useful to consider what happens to a route which (through configuration error) avoids receiving the standard import policy, e.g. through a session that is missing a route-map. Since the default LOCAL_PREF attribute is 100, I always liked to set the LOCAL_PREF on expensive paths below that, e.g. by choosing something like 80 for international transit and 90 for domestic. This has been known to avoid expensive weekends following last-minute- before-the-pub Friday session changes. In any case, having a dummy IBGP peer running OpenBGPd or Quagga or similar which sends alerts when it sees routes with non-standard LOCAL_PREF values can be a handy thing. Joe