RE: Single AS Number for multiple prefixes in different country

[Eric Morin]

I have 5 discrete networks across Canada using one ASN (will be down to
2 by end of year!). We accept a default (along with full tables) to
route between discrete networks. Not very elegant but gets the job done.


Eric 

-Original Message-
From: Harris Hui [mailto:harris@gmail.com] 
Sent: Friday, January 14, 2011 5:59 AM
To: nanog@nanog.org
Subject: Single AS Number for multiple prefixes in different country

Hi,

We have an AS Number AS2 and have 2 /24 subnets belongs to this AS
Number. It is using in US and peering with US Service Providers now.

We are going to deploy another site in Asia, can we use the same AS
Number
AS2 and have 2 other /24 subnets and peering with other Asia Service
Providers?

Will it affect the routing or BGP Path of our existing subnets in US?

Please advise.

Thanks
Harris :-)

-- 
This message has been scanned by MailScanner

Colo recommendations for 2001 6th (Westin BLDG) Seattle

[Eric Morin]

Hi

I am looking for a few RUs / ¼ rack (~20Amps of VAC) in a carrier neutral 
location with 24x365 smart hands service at 2001 6th Ave in Seattle.



Any recommendations?



Thanks in advance

Eric RR Morin

Internetwork Designer

IP Network Engineering & Carrier Relations

XplorNet Communications Inc

AS22995



506.324.4533 | eric.mo...@corp.xplornet.com NOTE: My email address has changed!



864 Anderson Dr | Saint John, New Brunswick | Canada E2M 4G3





  







This e-mail (including any attachments) is for the sole use of the intended 
recipient and
may contain confidential information protected by duties of confidentiality or 
privilege. If you are not the intended recipient of this e-mail, please 
immediately notify us by return e-mail or by telephone, delete this e-mail and 
destroy any copies.   Thank you.



Ce message est destiné uniquement à la personne prévue et peut contenir des 
renseignements confidentiels et/ou privilégiés au titre d’une obligation de 
confidentialité. Si vous n'êtes pas le destinataire visé, veuillez nous en 
informer sans délai par courriel ou téléphone et détruire ce message ainsi que 
toute pièce jointe, sans en garder de copie. Merci.


<>

Route reflector/server appliance for access router aggregation

[Eric Morin]

Hi

I working on a solution to offload my current internet facing, and soon
to be backbone, routers from terminating IBGP sessions from aggregation
network routers. I currently have 4948s (pizza box version of the
cat4500) in place, mostly bridging traffic, but some routing (OSPF,
couple dozen SVIs with HSRP). The 4948s surpasses all solution
requirements (I think) except when it comes to scaling the number of BGP
sessions to 80-100. The obvious solution is to replace with a much
larger platform (ASR1k, etc), which I am consider as an option but
capital is the killer. A more economical idea is to pair the 4948s with
a route reflector or server. I am looking for recommendations on
platforms that I should consider. I have seen the presentation from
NANOG48 on open source route server applications (Thanks!), and I am
considering a home grown solution, but I want to also consider any other
commercial appliances that we can drop in (with some lab work of course)
and buy support services on. I looked at a Vyatta appliance (2500 looks
good, but single power supply is disappointing). At each PoP I would
plan on having two reflectors/servers clustered, each paired with one
4948. I have 7206 NPE-G2s coming out of service in the future that could
perhaps be used, but the timing wont work.

 

If anyone has a recommendation on a platform, or general criticism of
the idea, please advise. Feedback, positive or negative, is always
welcome.

 

 

Thanks in advance

 

Eric RR Morin

 

RE: Recommendations for router with routed copper gig-e ports?

[Eric Morin]

I have found the MRV OS906 (6 port 10/100/1000/SFP + Eth OBM) to be a
very cost effective and an extremely flexible device. It's a linux based
device with a router shell but all forwarding is done in hardware
(ASICs). It has a very flexible implementation of many L2 features (QnQ,
inner or outer tag swapping, eth OAM, ERP) but also sports standard
routing switch features and protocols like BGP, OSPF, even IS-IS!

The cost of the device is 1/4 of a 3560G (etc). 

MRV's support has been very good. We found a bug in the DHCP-Relay
function where it would not broadcast back to a client that
discovered/requested with the broadcast bit set. They provided a new
spin of code with the fix within days!

http://www.mrv.com/product/MRV-OS-OS900-SDB

I hope this helps
Eric RR Morin

-Original Message-
From: Lorell Hathcock [mailto:lor...@hathcock.org] 
Sent: Sunday, February 14, 2010 4:42 PM
To: 'North American Network Operators Group'
Subject: Recommendations for router with routed copper gig-e ports?

All:

 

I'm involved in a project where we are cutting over a WISP from being a
single broadcast domain into the grownup real world of routing between
tower
nodes.  Of course the equipment is all Mikrotik and the single broadcast
domain was easy to implement, so that's why it was done this way.

 

My problem on the redesign is I want to provide routed, copper gig-e
ports
at a reasonable price per port.

 

My thought is to provide one copper gig-e port for all of the APs at a
tower
and a copper gig-e port for each backhaul to other towers (typically 2
to
4).  On the core nodes, I want to have one fiber gig-e port for the
internet
connection.  BGP would be implemented on the routers that connect to the
internet.  OSPF would be implemented on all of the backhaul ports.

 

So number of routed, copper gig-e ports at each tower would be:

 

1 - AP network (need suggestion for cost effective gig-e switch)

2 to 4 - back haul ports

1 - internet port (on one out of every 4 towers or so)  (and most likely
fiber instead of copper)

 

Does anyone have any suggestions?

 

Sincerely,

 

Lorell Hathcock

 

OfficeConnect.net | 832-665-3400 x101 (o) | 713-992-2343 (f) |
lor...@officeconnect.net

Texas State Security Contractor License | ONSSI Certified Channel
Partner 

Axis Communications Channel Partner | BICSI Corporate Member

Leviton Authorized Installer

 


-- 
This message has been scanned by MailScanner

RE: Recommendations for router with routed copper gig-e ports?

[Eric Morin]

I actually think the 912 is different then the 904 and 906, as I was
discouraged from buying the 912, and I REALLY wanted the extra ports.
That's not to say that the 904/906 doesn't have the same problems. I use
it for a router with a bunch of connected networks, DHCP relay, and BGP.
Other then the below mentioned DHCP-relay bug, and an FTP command bug
(which was also quickly fixed) they have served us well.

Eric RR Morin

-Original Message-
From: Jason Lixfeld [mailto:ja...@lixfeld.ca] 
Sent: Sunday, February 14, 2010 9:54 PM
To: Eric Morin
Cc: North American Network Operators Group
Subject: Re: Recommendations for router with routed copper gig-e ports?

The OS906 may be different than the OS912, but be warned that I had  
major issues with OS912 relating to LDP and OSPF.  Constant crashes of  
both LDP and OSPF made the device totally unusable.  We had to ship  
all 20 back to them.  It was really messy.  This was about 6 months  
ago, and their code may have been fixed, so YMMV.

On 2010-02-14, at 8:47 PM, "Eric Morin"   
wrote:

> I have found the MRV OS906 (6 port 10/100/1000/SFP + Eth OBM) to be a
> very cost effective and an extremely flexible device. It's a linux  
> based
> device with a router shell but all forwarding is done in hardware
> (ASICs). It has a very flexible implementation of many L2 features  
> (QnQ,
> inner or outer tag swapping, eth OAM, ERP) but also sports standard
> routing switch features and protocols like BGP, OSPF, even IS-IS!
>
> The cost of the device is 1/4 of a 3560G (etc).
>
> MRV's support has been very good. We found a bug in the DHCP-Relay
> function where it would not broadcast back to a client that
> discovered/requested with the broadcast bit set. They provided a new
> spin of code with the fix within days!
>
> http://www.mrv.com/product/MRV-OS-OS900-SDB
>
> I hope this helps
> Eric RR Morin
>
> -Original Message-
> From: Lorell Hathcock [mailto:lor...@hathcock.org]
> Sent: Sunday, February 14, 2010 4:42 PM
> To: 'North American Network Operators Group'
> Subject: Recommendations for router with routed copper gig-e ports?
>
> All:
>
>
>
> I'm involved in a project where we are cutting over a WISP from  
> being a
> single broadcast domain into the grownup real world of routing between
> tower
> nodes.  Of course the equipment is all Mikrotik and the single  
> broadcast
> domain was easy to implement, so that's why it was done this way.
>
>
>
> My problem on the redesign is I want to provide routed, copper gig-e
> ports
> at a reasonable price per port.
>
>
>
> My thought is to provide one copper gig-e port for all of the APs at a
> tower
> and a copper gig-e port for each backhaul to other towers (typically 2
> to
> 4).  On the core nodes, I want to have one fiber gig-e port for the
> internet
> connection.  BGP would be implemented on the routers that connect to  
> the
> internet.  OSPF would be implemented on all of the backhaul ports.
>
>
>
> So number of routed, copper gig-e ports at each tower would be:
>
>
>
> 1 - AP network (need suggestion for cost effective gig-e switch)
>
> 2 to 4 - back haul ports
>
> 1 - internet port (on one out of every 4 towers or so)  (and most  
> likely
> fiber instead of copper)
>
>
>
> Does anyone have any suggestions?
>
>
>
> Sincerely,
>
>
>
> Lorell Hathcock
>
>
>
> OfficeConnect.net | 832-665-3400 x101 (o) | 713-992-2343 (f) |
> lor...@officeconnect.net
>
> Texas State Security Contractor License | ONSSI Certified Channel
> Partner
>
> Axis Communications Channel Partner | BICSI Corporate Member
>
> Leviton Authorized Installer
>
>
>
>
> -- 
> This message has been scanned by MailScanner
>
>


-- 
This message has been scanned by MailScanner

WiMAX Multihost CPE/MS MTU enforcement

[Eric Morin]

Hi

Anyone out there deploying multihost CPE/MS with 16e WiMAX? 

Do your CPEs enforce a specific MTU (1400) for upstream traffic? 

I would like to hear from anyone (offline) that is dealing with MTU
challenges with mulithost 16e deployments.

 

 

Thanks!

 

Eric Morin

 

7206 NPE-G2 with 4 full table feeds

[Eric Morin]

Hi

I have an application where I have a 7206 with NPE-G2 (1G RAM) that
currently has a full table from an eBGP peer and a full table from a
co-located IBGP peer. I want to mesh this guy to two other IBGP peers
that will also send their full tables. There is roughly 400Mbps (adding
both direction) with an OSPF process (<30 routes) and an ISIS process
(<20 routes).

 

I haven't been very successful at finding real life BGP scaling for this
platform and was hoping that someone out there may be doing something
similar (4 x full table feeds with ~400Mbps) and can provide feedback on
performance and/or stability. I have soft reconfig inbound enabled on
the current two feeds, I assume that this will make a difference in this
application with regards to available memory for all 4 feeds?

 

 

Thanks in advance

 

Eric