Aruba & ProVision-based
1752795 Members
5898 Online
108789 Solutions
New Discussion юеВ

Re: Use HP2920-48G as a replacement for a router?

 
jrp7591
Occasional Contributor

Use HP2920-48G as a replacement for a router?

We are looking at replacing routers and switches this year. It has been suggested that we could eliminate replacing the router and just using the HP2920 as a switch and the router. We have two branch offices setup in a standard hub and spoke topology with about 150 users, 50 at each branch. Is this a viable solution? Has anybody actually done this? Pros and cons about this setup?

 

Thanks,

4 REPLIES 4
Vince-Whirlwind
Honored Contributor

Re: Use HP2920-48G as a replacement for a router?

To answer this, you would have to look at exactly what functions your current router provides.

 

In general, WAN links are nowadays presented as Layer2 ethernet interfaces and a dedicated router may well no longer be required in your network.

 

You should get a network professional to design your new network for you just to make sure you're not overlooking something.

jrp7591
Occasional Contributor

Re: Use HP2920-48G as a replacement for a router?

Which leads me to ask, what "functions" can a router perform that a layer 3 switch can't?

Vince-Whirlwind
Honored Contributor

Re: Use HP2920-48G as a replacement for a router?

Interfaces supporting non-ethernet media types is the main one, but you also have various applications that run on routers and not necessarily on switches, eg, QoS policies, netflow, NAT, routing protocols, firewalling, etc...

 

 

Chrisd131313
Trusted Contributor

Re: Use HP2920-48G as a replacement for a router?

The key area you wil need to check is routing protocols, such as IEGRP, BGP, OSPF, MPLS. switches do offer support for theser protocols, but sometimes they are slightly stripped down versions (iBGP, MPLS-Lite), so you really need to understand your routing requirements. From what you are stating it sounds like you just have a basic router performing standard NAT/PAT RIPv2 or maybe some static routing functions. This would not be too hard to migrate to a Layer3 switch. But make sure you fully understand the requirements first before taking the plunge.. A router is a router and a switch is a switch for a reason, they both do their designated jobs well - switches have just started to creep in to the router arena because these functions are becoming easier to implement with the current switch architectures available.

 

Firewalling can be coverd, if you really want to manage a buttload of ACLS ;P

 

QoS policies (DSCP, Precedence) are pretty standard these days in most switches, but some of teh lower level switches have less options available.

 

HTH

-----------------------------------------------------

Don't forget to mark a post resolved if your question was answered.