On Feb 9, 2008 2:10 PM, Eldridge, Dave <[EMAIL PROTECTED]> wrote: > Yes there are sort of. Hp calls them tagged ports what Cisco calls trunks.
FYI: HP uses "tagged" and "untagged" for VLANs. HP uses "trunk" for link aggregation. VLANs and link aggregation don't have much to do with each other in HP-land. In HP-land, one can configure a given port with one or more VLANs. Zero or more of those VLANs can be configured as "tagged", which means traffic for those VLANs is expected to be identified in the Ethernet frame with a VLAN tag. The switch will add the tag to VLAN traffic sent out the port, and look for it on incoming traffic. Zero or one of those VLANs can be "untagged", which means traffic on the port is not expected to be tagged. Untagged incoming traffic is assumed to be on the untagged VLAN, and traffic on the VLAN associated as "untagged" (if any) is sent without a tag on that port. This makes "untagged" sort of like the default VLAN for a given port, but be warned that HP uses "DEFAULT_VLAN" for something else. Still in HP-land, link aggregation can be done automatically, with LACP, or manually, with the "trunk" command. If LACP is abled, you basically just hook it up and the switch figures it out (hopefully). Manually, you do something like "trunk 5-6 trk1 trunk" (ports 5 and 6 are in link aggregation group "trk1"). I don't know much about Cisco, but from what I've heard, Cisco uses a "VLAN trunk port" to mean a port carrying traffic for multiple VLANs (multiple tagged ports, in HP-speak). Dunno about link aggregation. -- Ben ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
