Just an update to try to fully explain the symptoms I'm getting. * I've configured the gig port on the HP that I want to use for this task as being Tagged for all 4 VLANS that we have (but not the DEFAULT_VLAN). * I have configured the Cisco switch for Port 24 to pass all the appropriate VLAN traffic. * I have configured Port 23 on the Cisco to connect to the firewall on the next step towards Outside. * I plug straight-thru cables into these connections. * I get green link lights on all ports. (Except firewall, which gives me a yellow Gig link light) * From my desk, the persistent pings I've had going to the remote site servers are now alternating between Destination Host Unreachable, and Request timed out. * I use TeraTerm to connect to the HP switch. It is not showing a MAC address for Port C1, where the Cisco is plugged in. Also, I cannot ping the Cisco from inside the HP. * I log into the firewall, and cannot ping the 192 address of the Cisco port. * I console into the Cisco, and cannot ping in either direction. * I put things back the way they were, and everything works.
I have put the Auto-MDIX command on my list of things to try next time I get a shot at this, but that by itself doesn't explain why I can't talk to the firewall on the other side, which is simply a server box, with Checkpoint loaded. There is a mode button on the front of the Cisco, and I'm wondering if somehow that got pushed while mounting the switch, or something, and maybe I've turned communication off somehow. At the moment, the SYST light, and the STAT light are lit on the front of the switch. Joe Heaton -----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 7:54 AM To: NT System Admin Issues Subject: Re: Help with HP/Cisco switch communication 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> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
