Re: Procurve Routing Issue

[Ben Scott]

On Fri, Oct 8, 2010 at 4:02 PM, Joseph L. Casale
 wrote:
> I have a 2824 with two vlans, 100 for prod and 103 for ip san. It’s not
> currently in routed mode, but I want assign ips to the two vlans and set
> it up in routed mode so the switch can route traffic between servers
> and the san vlan for bandwidth reasons.

  I would not use the 2824 as a router for anything serious, and
"bandwidth reasons" makes it sound serious.

  The 2800 series is intended as a layer two switch.  It's an
excellent layer two switch.  Routing, not so much.  IMO, the layer
three features of that switch are mainly intended for management
purposes, not for production payload traffic.

>  ...  anyone know what to do here?

  Use something else as the router.  HP makes layer-3-and-higher
switches, but the 2800 series isn't one of them.

  If you want to keep your existing 2800, use an external device as a router.

  If you're short on ports and don't need a *ton* of bandwith but do
need high packets-per-second, you could put multiple VLANs tagged on a
single switch port, and then put a router-on-a-stick on that port.
(Router-on-a-stick = router with only a single physical connection,
using VLANs.)

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Procurve Routing Issue

[Joseph L. Casale]

>  I would not use the 2824 as a router for anything serious, and
>"bandwidth reasons" makes it sound serious.

Do you know what it takes to route even at gig speeds? It doesn't
need to be serious at all to desire to route faster than most routers:)
Its iSCSI traffic, letting even a 2824 pass it around is better than most
options.

>  Use something else as the router.  HP makes layer-3-and-higher
>switches, but the 2800 series isn't one of them.

Heh, not an option:(

I just re-confirmed with an HP guy, as the switch process "connected"
routes first than best match, any downstream user in client vlan can
route traffic and jump vlans (stupid imho to make the order process this
way, when it could do static first so a null/reject could actually be of use).

Bah, in Linux we use one physical interface and tag a virtual int into a vlan.
So I use one port for example. I am not that savvy with Windows, but I sure
have never seen a way to do this with Windows drivers:( I guess I could bridge
but that's just getting messy...

jlc

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Procurve Routing Issue

[Ben Scott]

On Fri, Oct 8, 2010 at 4:31 PM, Joseph L. Casale
 wrote:
>>  I would not use the 2824 as a router for anything serious, and
>>"bandwidth reasons" makes it sound serious.
>
> Do you know what it takes to route even at gig speeds?

  To the best of my knowledge, simply sending or receiving full frames
at gig speeds is enough to stress most PCs, let alone forwarding them.
 The bottleneck is usually bus bandwidth or interrupt load.  While I
don't know, I would expect  the routing on the 2800 to be done on the
management CPU, not the switch ASIC, so you're talking about a PowerPC
running at 266 MHz, with very little bandwidth to the network.

  But if you disagree, find an old PC, install Linux and a gigabit
NIC, and do the router-on-a-stick configuration.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Procurve Routing Issue

[Joseph L. Casale]

>  To the best of my knowledge, simply sending or receiving full frames
>at gig speeds is enough to stress most PCs, let alone forwarding them.
> The bottleneck is usually bus bandwidth or interrupt load.  While I
>don't know, I would expect  the routing on the 2800 to be done on the
>management CPU, not the switch ASIC, so you're talking about a PowerPC
>running at 266 MHz, with very little bandwidth to the network.

The 2824 routes on its backplane at wire speed until the route table fills,
then it routes at/in software (slowly).

>  But if you disagree, find an old PC, install Linux and a gigabit
>NIC, and do the router-on-a-stick configuration.

I disagree, but I won't play with the old PC:)

jlc

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin