quick question on untagging and tagging

[phjohnso]

in the config below I have 2 vlans

vlan 1 and vlan 800

they are split between odd and even ports on the switch (ProCurve J9021A Switch 2810-24G)

I have 4 uplink ports that I would like to carry the traffic from both vlans

Do I need to use a tagged command and if so where would I put it.

Config below....

hostname "RAW"
max-vlans 256
time timezone -300
time daylight-time-rule User-defined begin-date 3/11 end-date 11/6
no web-management
web-management ssl
no telnet-server
interface 1
   name "VPN Test Connection Towerstream"
exit
interface 2
   name "VPN Test Connection Cox"
exit
interface 3
   name "DC Raw Internet"
exit
interface 4
   name "Cox Feed"
exit
interface 5
   name "Raw Internet IT Storage"
exit
interface 6
   name "Cox Feed"
exit
interface 7
   name "To Rack 4 Netgear VPN Firewall"
exit
interface 8
   name "Cox Feed"
exit
interface 9
   name "DC Raw Internet"
exit
interface 10
   name "Cox Feed"
exit
interface 11
   name "DC Raw Internet"
exit
interface 12
   name "Cox Feed"
exit
interface 13
   name "DC Raw Internet"
exit
interface 14
   name "DC Raw Internet"
exit
interface 15
   name "DC Raw Internet"
exit
interface 16
   name "Cox Feed"
exit
interface 17
   name "Raw Internet to Amano Parking Router"
exit
interface 18
   name "Cox Feed"
exit
interface 19
   name "Xroads Wan1 Towerstream Connection"
exit
interface 20
   name "Cox Feed"
exit
interface 21
   name "DMZ Switch Interconnect DC to AMF"
exit
interface 22
   name "COX RAW INTERNET CONNECTION"
exit
interface 23
   name "DC Raw Internet"
exit
interface 24
   name "Towerstream From 115"
exit
ip default-gateway xxxxxxxxxxxx
sntp server 129.174.93.11
timesync sntp
sntp unicast
sntp 360
logging 10.1.1.18
vlan 1
   name "DEFAULT_VLAN"
   untagged 1,3,5,7,9,11,13,15,17,19,21,23-24
   ip address 64.17.228.162 255.255.255.224
   no untagged 2,4,6,8,10,12,14,16,18,20,22
   exit
vlan 800
   name "COX FEED"
   untagged 2,4,6,8,10,12,14,16,18,20,22
   exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
no stack
spanning-tree
ip ssh
ip ssh filetransfer
no tftp client
no tftp server
loop-protect 1-24
loop-protect disable-timer 300
password manager
password operator

[Justin_Goldberg]

if it comes into the switch tagged on a certain vlan, it will leave the switch untagged if that port where it exits is link type access for the vlan. Also known as changing the pvid. Then make it not a member of the other vlans. So basically it's "nailed" to the vlan you want to interlink with the other switches.

[phjohnso]

So in the example I gave will tagging the ports from vlan 800 on vlan 1 allow that traffic to flow across vlan1 too?

see re-work below please....

vlan 1
   name "DEFAULT_VLAN"
   untagged 1,3,5,7,9,11,13,15,17,19,21,23-24
   ip address 64.17.228.162 255.255.255.224
   tagged 2,4,6,8,10,12,14,16,18,20,22
   exit

[Justin_Goldberg]

I don't know.

untagged will pass untagged, tagged will pass as tagged, all on one "hybrid" port, in 3Com language. I don't know HP commands.

[Richard Litchfield]

Forget the hybrid thing - that has nothing to do with these traditional ProCurve switches; VLAN tagging - 802.1Q is the standard way of carrying multiple VLANs across a single link - even Cisco does it!

Notes:

• A single VLAN may have tagged and untagged ports
• tagged/untagged needs to be matched at each end of the link (ie if VLAN 1 is untagged, VLAN800 tagged on a link, the device at the other end needs to be configured the same way)
• VLANs are separate; they typically carry 1 subnet each
• Different subnets require a router to route between them
• The 2810 is not a router (it doesn't have any routing functions - you will need an external router (eg 3500yl or your Netgear firewall if it supports 802.1Q VLANs) if you want to ping from a device on VLAN1 to VLAN800
• right now you will have 2 completely separated networks.

(BTW, this question should really be in the E-Series set of threads where the traditional ProCurve switches are discussed. A Series really covers the Comware-based traditional 3com/H3C devices.)