Here's the config for one of my 2510s, which should be similar to the 2810:
----------Begin 2510 configuration---------- hostname "2510-48 Dist 1" max-vlans 10 time timezone -480 time daylight-time-rule Continental-US-and-Canada ip default-gateway 192.168.xx.1 sntp server 192.168.yy.191 timesync sntp logging 192.168.yy.225 snmp-server community "priv" Operator Unrestricted snmp-server community "pub" Operator vlan 1 name "DEFAULT_VLAN" untagged 50-52 ip address dhcp-bootp tagged 49 no untagged 1-48 exit vlan 111 name "vlan111" untagged 2,4,6,8,10,12,14-32,34,36-38,40-46,48 tagged 49 exit vlan 112 name "vlan112" untagged 7,9,11,35,39,47 tagged 49 exit vlan 124 name "vlan124" untagged 1,3,5,13,33 tagged 49 exit vlan 99 name "vlan99" ip address 192.168.xx.2 255.255.255.0 tagged 49 exit vlan 113 name "vlan113" tagged 49 exit vlan 115 name "vlan115" tagged 49 exit password manager password operator ----------End 2510 configuration---------- VLAN 99 is my management VLAN - nothing lives on that except switches. VLAN 1 is unpopulated. The other VLANs are the various production subnets. The switch's IP address is 192.168.xx.2 - it's DG is 192.168.xx.1 Port 49 is tagged in each VLAN, which means that all of the VLANs run over that port to my backbone switch - all of the other ports (except 50-52, which aren't used) go to various desktops, as shown by the "untagged" setting in each VLAN. Thus, all packets on the 2510 that are not destined for a port on the same VLAN on the same switch, go to the router - actually an HP 3400cl, which is a 48-port layer3 switch. My backbone switch has the all of the 192.168.aa.1 addresses for the various subnets, and when a packet comes over port 49 from one VLAN destined for another VLAN, or for a port on the same VLAN but on a different swtich, the backbone switch figures that out, and routes the packet to where it is supposed to go. Last note: you won't find a DHCP helper address in the above configuration. That's because my backbone switch handles that. Kurt On Tue, Oct 27, 2009 at 17:49, Webster <[email protected]> wrote: > Goal is to setup a VLAN for the iSCSI traffic from my Windows Storage Server > 2008 box I built. > > I can barely spell VLAN so I have my work cut out for me. :) I know I will > make a lot of ID10T errors but this is my personal lab so I am not going to > hurt anything. If I screw something up, I can just reset the switch back to > factory defaults and start all over. > > > Webster > >> -----Original Message----- >> From: Ben Scott [mailto:[email protected]] >> Subject: Re: HP ProCurve 2810 CLI ref guide >> >> On Tue, Oct 27, 2009 at 8:38 PM, Webster <[email protected]> wrote: >> > I must be doing something wrong on my switch as I was told to >> > enter "ip routing" but I get "Invalid command: routing". >> >> The 2810 doesn't do routing. It's a layer two switch. It's not a >> router (or a "layer three switch", as routers are sometimes called). >> >> > I am at the (config)# prompt but can't figure >> > out what I am doing wrong. >> >> What are you trying to accomplish? What's the end goal? > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
