I see various people are recommending networks setup regional ASN's. I
am in the process of setting up a new network which will serve as a
transit network for all our operating units. I was planning on using
one ASN for North America, Asia and Europe. Is this not recommended?
Cheers
Ryan
You can use one AS and communities to seperate your traffic/policies.
-jim
--Original Message--
From: Ryan Finnesey
To: NANOG list
Subject: regional ASN's
Sent: Dec 1, 2010 1:13 PM
I see various people are recommending networks setup regional ASN's. I
am in the process of setting up
--
From: Ryan Finnesey
To: NANOG list
Subject: regional ASN's
Sent: Dec 1, 2010 1:13 PM
I see various people are recommending networks setup regional ASN's. I
am in the process of setting up a new network which will serve as a
transit network for all our operating units. I was planning
session hacks).
Or just have disparate networks using the same ASN. Works fine.
Why waste ASNs and try to explain to others how asX,Y,Z, etc., are all the same
company?
--
TTFN,
patrick
--Original Message--
From: Ryan Finnesey
To: NANOG list
Subject: regional ASN's
Sent: Dec 1, 2010
On Dec 1, 2010, at 4:43 PM, Jack Bates wrote:
On 12/1/2010 3:37 PM, Patrick W. Gilmore wrote:
Or just have disparate networks using the same ASN. Works fine.
Why waste ASNs and try to explain to others how asX,Y,Z, etc., are all the
same company?
I dislike the problem of routes not
On 12/1/2010 3:56 PM, Patrick W. Gilmore wrote:
Having islands which point default is not ugly. They are probably pointing
default anyway.
If all sites strictly do default, fine. However, one could say static
routing would work fine there too; and then you don't need an ASN. If
each site
On Dec 1, 2010, at 5:05 PM, Jack Bates wrote:
On 12/1/2010 3:56 PM, Patrick W. Gilmore wrote:
Having islands which point default is not ugly. They are probably pointing
default anyway.
If all sites strictly do default, fine. However, one could say static routing
would work fine there
7 matches
Mail list logo
