Cisco IOS to ProCurve translation

1) I want the CLI commands

2) I understand what etherchannel and how to enable an 802.1q (dot1q) trunk in cisco. The problem is what cisco calls a trunk (ISL or dot1q) is not what Procurve calls a trunk. What procurve calls a trunk is similar (but not the same) to what cisco calls an etherchannel.

http://www.experts-exchange.com/Hardware/Networking_Hardware/Routers/Q_22823407.html
 
but thanks for responding.

Jim,
I can tell you right now that Cisco Etherchannel will not work with an HP Procurve switch.  The best you can do is enable a standard 802.1q trunk on a per interface basis.  If you're looking for failover, you can simply connect two 802.1q interfaces on the Cisco to two 802.1q interfaces in the HP and let spanning tree handle the rest.  The HP's java-based web interface should be pretty self explanitory for you to setup the VLAN trunk.

What exactly are you trying to accomplish with this configuration?  There may be a better way to do it.
-Todd

I am looking for the equivalent CLI commands on HP Procurve switches. I am not in any way trying to connect an HP Procurve "trunk" to a Cisco etherchannel. (by the way, you should not use the GUI over the CLI, and any decent network engineer would agree with me on that.)

If I were to "let spanning-tree to handle the rest" I'd be wasting 50% of my bandwidth, while that would work it's not really a good network design.

I appreciate your response but your going down the wrong path.


 

Insulting people is not going to get you very far in life, Jim.

The command line features in a Procruve switch depend upon the model you are using.  The 4000M, for example, has a very limited command line that will only enable you to set the most basic parameters.  In a 4000M, the console menus or the web-based GUI are the only facilities available to configure 100% of the features.

In Procurve lingo, a 802.1Q trunk port is called a "tagged VLAN."  When you set a port as "tagged" you can connect that interface to any 802.1Q compliant device and the VLAN information will be sent across the link.  You can also assign multiple VLAN IDs to a single port.  This enables you to span  multiple VLANs across 802.1Q compliant switches.

After some research, I found that some Procurves support FEC (Fast Etherchannel) that is supposedly compatible with Cisco devices.  I have not tested this feature so I do not know if it truely is interoperable.  According to HP, you can configure FEC to aggregate multiple physical ports (what HP calls a "trunk") and set those ports for "tagged" in order to send your VLAN info to a FEC/802.1Q compatible/compliant switch.

An HP "tagged" port = a Cisco dot1q trunk port
An HP "trunk" port = a Cisco Etherchannel/Port-channel

Since the command line features vary by model, which HP Procurve model will you be using?  The more advanced models have a more robust command line and it may be possible to get the command line config you need, just send us the model# and we'll give you the command line.
-Todd

I am sorry you felt insulted, but according to HP all Procurve products use an Industry-standard CLI (command-line interface) to minimize training and certification costs.

I found my solution below:
ftp://ftp.hp.com/pub/networking/software/

Jim,
First off, you're wrong.  All Procurve products do not use an industry standard CLI, that's just not true.  If you had used those products before you would know that (or did a little bit of research).  Also, that FTP site has the manuals for all HP Procurve products.  Which model did you have a question about?  I assume by industry standard you mean Cisco IOS CLI.  The HP Procurve 6200yl, 5400zl, and 3500yl have a Cisco-like CLI.  While the HP Procurve 4000M/8000M switches have nothing like the Cisco CLI.  And, like I said, you can not configure all of the features of the 4000M/8000M without using the GUI or the console menus.
Since you won't tell me what model switch you would like information about, here's a link to the HP Procurve 6200yl, 5400zl, and 3500yl  command line reference.  Perhaps this will help you:
ftp://ftp.hp.com/pub/networking/software/6200-5400-3500-CLI-k1201-Feb2007.pdf
And here's a guide for configuring the 1600M, 2424M, 4000M, and 8000M:
ftp://ftp.hp.com/pub/networking/software/59692320.pdf
Does this answer your questions?
-Todd

Thank you for your efforts but I located my solution via that ftp site.

Jim if you located the solution, would you post in the same format your original questions were.
I am trying to crossover the commands and you really formed a forward thinking smart question seeking out the equivelance in commands.
-PJ

See these docs to answer the trunk / etherchannel questions

http://www.hp.com/rnd/support/faqs/8000_4000_2424.htm
http://cdn.procurve.com/training/Manuals/2900-MCG-Jan08-11-PortTrunk.pdf

See this doc for the MSTP questions:
http://cdn.procurve.com/training/Manuals/2900-AdvTrafficMgmt-Jan2008-59916197.pdf

See this doc for dot1q in dot1q:
http://www.procurve.com/NR/rdonlyres/248E44DF-9B1D-4D00-A9E7-28141BFFA2E1/0/QinQWhitePaper_Nov_07_WW_Eng_Ltr.pdf

See this doc for SSH
http://www.hp.com/rnd/pdfs/Hardening_ProCurve_Switches_White_Paper.pdf

Let me know if this was helpful.

Googling for a solution om how to connect Cisco and HP switches via Cisco Etherchannel, this question on E-E came up right away. Therefore I want to post the working configuration I worked out for future reference, even though the switches themselves are low-end and the question itself is closed.
The Cisco was configured from the command-line only and the Procurve through the webinterface (screenshots attached), the ProCurve is so low-end it doesn´t seem to have a CLI avaliable, at least not one I could find by reading the manual :-)
So here are the goodies - snippets from the configs from a Cisco Catalyst 3650-48TS running IOS 12.2(35)SE5 interconnected with a HP ProCurve 1810G-24 through 2 ethernet cables (irrelevant parts suppressed):

ProCurve 1810G ports 23 and 24 connected to Cat3560G interfaces g0/33 and g0/34 respectively.

---------------- Beginning output --------------------
Cat3560# sh ru
...
...
interface Port-channel2
 switchport access vlan 81
 switchport mode access
...
interface GigabitEthernet0/33
 switchport access vlan 81
 switchport mode access
 channel-group 2 mode on
!
interface GigabitEthernet0/34
 switchport access vlan 81
 switchport mode access
 channel-group 2 mode on
...
...
---------------- End of output -------------------


Here is a diagnostic output from the Cat3560G:
---------------------Beginning output -------------------
Cat3560#sh etherchannel 2 summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 2
Number of aggregators:           2

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
2      Po2(SU)          -        Gi0/33(P)   Gi0/34(P)

Cat3560#
----------------------- End of output ---------------------------

Here is another:
---------------------Beginning output -------------------
Cat3560#sh etherchannel 2 detail
Group state = L2
Ports: 2   Maxports = 8
Port-channels: 1 Max Port-channels = 1
Protocol:    -
                Ports in the group:
                -------------------
Port: Gi0/33
------------

Port state    = Up Mstr In-Bndl
Channel group = 2           Mode = On              Gcchange = -
Port-channel  = Po2         GC   =   -             Pseudo port-channel = Po2
Port index    = 0           Load = 0x00            Protocol =    -

Age of the port in the current state: 0d:00h:40m:25s

Port: Gi0/34
------------

Port state    = Up Mstr In-Bndl
Channel group = 2           Mode = On              Gcchange = -
Port-channel  = Po2         GC   =   -             Pseudo port-channel = Po2
Port index    = 0           Load = 0x00            Protocol =    -

Age of the port in the current state: 0d:00h:40m:24s

                Port-channels in the group:
                ---------------------------

Port-channel: Po2
------------

Age of the Port-channel   = 7d:02h:57m:46s
Logical slot/port   = 2/2          Number of ports = 2
GC                  = 0x00000000      HotStandBy port = null
Port state          = Port-channel Ag-Inuse
Protocol            =    -

Ports in the Port-channel:

Index   Load   Port     EC state        No of bits
------+------+------+------------------+-----------
  0     00     Gi0/33   On                 0
  0     00     Gi0/34   On                 0

Time since last port bundled:    0d:00h:40m:25s    Gi0/34
Time since last port Un-bundled: 0d:00h:40m:50s    Gi0/33

Cat3560#
----------------------- End of output ---------------------------

As written I have also attached the images of the 3 relevant Procurve GUI parts. They show Trunk status, Trunk configuration and trunk membership.

I will move on to try to create a Cisco trunking config to the ProCurve, if I manage that to creating it on top of the Etherchannel. If successful I will post the configs as above.

It looks like the etherchannel is correct but this is not a dot1q trunk, since the cisco has switchport mode access. This puts the port in permanent nontrunking mode. "sh int trunk" will verify this. Keep in mind that what HP calls a "trunk", Cisco calls an etherchannel. You can verify the etherchannel with "sh etherchannel summary"

 I think what is happening is the Cisco will only forward vlan 81 without any tags and I am not clear on the HP config, but if it's forcing a dot1q trunk, then vlan 81 on the Cisco will be talking to the default native vlan (vlan 1) on the HP. No other vlans will work. Try converting interface po2 to this:

switchport trunk encap dot1q
switchport trunk native vlan 1
switchport mode trunk
switchport nonnegotiate  

Thanks Jim,

You are right on the money in your summing up. This being my first ever post at E-E I actually did not realize it would be forwarded to you believe it or not :-), or I would have taken greater care in using the unbelievably easy to confuse Cisco-HP lingo. Being a Cisco guy throughout I tend to use the Cisco terms even when doing HP stuff, which certainly leaves room for improvement on my part.

Also, since I have both limited "experimenting" time at my disposal, coupled with a half-assed business requirement to actually use this setup before we get budget for proper switches approved, I am holding my own reins hard in doing this very much step by step so as not to get muddled up as to what is working and what is not.

So the "Cisco Etherchannel - HP Trunk" is verified as working as seen in the diagnostic output, but I have not yet tried my hands at the "Cisco VLAN Trunk - HP tagged VLAN", just as you say. I believe I will have time to do this over the weekend, so I´ll report back with the results when done.

I did get this flash of inspiration that if I backed up the HP config file maybe it would be in a regular CLI-style, providing the "translated" commands. However it turns out I was wrong in that regard. It just looked like garbage :-(

Thanks for your suggestions also, and I´ll be sure to try them out.

Well, with great success it turned out I was able to log time on this today after all...so for the benefit of those not having done the same extensive background research as you have Jim, I will be a bit over-obvious in my description below of what I have done.
I confirm the suggestions you state above work, in so far as they apply to the 802.1q VLAN part. I haven´t yet done this over a "Cisco Etherchannel - HP trunk" yet but will get to that next time.

So with the Cisco 3650G port g0/34 connected directly to the HP port 24 I managed to "Cisco Trunk - HP tagged VLAN" all the network VLANs using 802.1q over to the HP switch. Using a workstation connected to port 13 on the ProCurve I could pick VLANs off one by one through the process of
1) changing it´s ports "HP Untagged" status to the desired VLAN id.
2) setting the workstation ip address to match the subnet of the current VLAN.
3) pinging hosts on local and remote subnet.
All in all it took me about 30 minutes to set this up and verify the function.

The Cisco config snippet (irrelevant parts suppressed):
---------------------Beginning output -------------------
Cat3560# sh ru
...
...
!
interface GigabitEthernet0/34
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 81
 switchport mode trunk
!
...
...
---------------------End of output -------------------

Here is a diagnostic output for g0/34:
---------------------Beginning output -------------------

Cat3560#sh int g0/34 switchport
Name: Gi0/34
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 81 (New)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL

Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
Cat3560#
---------------------End of output -------------------

Here is another:

---------------------Beginning output -------------------
Cat3560#sh int g0/34 trunk

Port        Mode         Encapsulation  Status        Native vlan
Gi0/34      on           802.1q         trunking      81

Port        Vlans allowed on trunk
Gi0/34      1-4094

Port        Vlans allowed and active in management domain
Gi0/34      1,81-96,130-143

Port        Vlans in spanning tree forwarding state and not pruned
Gi0/34      1,81-96,130-143
Cat3560#
---------------------End of output -------------------

As for the Procurve, the relevant screenshots are attached as above. I have edited the VLAN ID´s in the Cisco output as I don´t want info on our network configs circulating, and therefore saw no option but to obscure the ID´s in the ProCurve screenshots. Hidden behind the "blocks" are regular VLAN numbers though, i.e. 81, 82, 83 et.c.

In the ProCurve I first created the VLAN ID´s at the VLAN-Configuration page, the VLAN ID´s must be identical to the ID´s in the Cisco switch. Then, at the VLAN Participation/Tagging page, I chose in sequence every VLAN ID defined and for each set port 24 to T as in Tagged. Lastly I plugged the workstation to port 13 and started testing the VLANs. Port 13 was set to U as in Untagged for each VLAN ID in turn. When testing a VLAN ID I set the workstation ip address to be part of the ip subnet in use on that VLAN. Then I pinged about a great deal, when getting successful replies I moved on to the next VLAN ID & subnet and so on.

So, "Cisco Trunk - HP Tagged VLAN" on a "Cisco Etherchannel - HP Trunk" next...

OK, done it.
"Cisco VLAN trunk - HP tagged VLAN" over "Cisco Etherchannel - HP Trunk" also works between Cisco 3560G and Procurve 1810G switches. Having verified the above steps this was really easy and quick in setting up. Cisco Catalyst ports g0/41-g0/42 connected directly to Procurve ports g23-g24 respectively.

Cisco config (irrelevant parts supressed):
---------------------Beginning output -------------------
Cat3560# sh ru
...
...
!
interface Port-channel2
 switchport trunk encapsulation dot1q
 switchport mode trunk
!
...
!
!
interface GigabitEthernet0/41
 switchport trunk encapsulation dot1q
 switchport mode trunk
 channel-group 2 mode on
!
interface GigabitEthernet0/42
 switchport trunk encapsulation dot1q
 switchport mode trunk
 channel-group 2 mode on
!
...
...
Cat3560#
---------------------End of output -------------------

Here is a diagnostic output:
---------------------Beginning output -------------------
Cat3560#sh etherchannel 2 summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 2
Number of aggregators:           2

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
2      Po2(SU)          -        Gi0/41(P)   Gi0/42(P)

Cat3560#
---------------------End of output -------------------

Here is another:
---------------------Beginning output -------------------
Cat3560#sh etherchannel 2 detail
Group state = L2
Ports: 2   Maxports = 8
Port-channels: 1 Max Port-channels = 1
Protocol:    -
                Ports in the group:
                -------------------
Port: Gi0/41
------------

Port state    = Up Mstr In-Bndl
Channel group = 2           Mode = On              Gcchange = -
Port-channel  = Po2         GC   =   -             Pseudo port-channel = Po2
Port index    = 0           Load = 0x00            Protocol =    -

Age of the port in the current state: 0d:02h:52m:09s

Port: Gi0/42
------------

Port state    = Up Mstr In-Bndl
Channel group = 2           Mode = On              Gcchange = -
Port-channel  = Po2         GC   =   -             Pseudo port-channel = Po2
Port index    = 0           Load = 0x00            Protocol =    -

Age of the port in the current state: 0d:00h:11m:07s

                Port-channels in the group:
                ---------------------------

Port-channel: Po2
------------

Age of the Port-channel   = 0d:03h:43m:52s
Logical slot/port   = 2/2          Number of ports = 2
GC                  = 0x00000000      HotStandBy port = null
Port state          = Port-channel Ag-Inuse
Protocol            =    -

Ports in the Port-channel:

Index   Load   Port     EC state        No of bits
------+------+------+------------------+-----------
  0     00     Gi0/41   On                 0
  0     00     Gi0/42   On                 0

Time since last port bundled:    0d:00h:11m:09s    Gi0/42
Time since last port Un-bundled: 0d:02h:52m:38s    Gi0/41

Cat3560#
---------------------End of output -------------------

Here is a third:
---------------------Beginning output -------------------
Cat3560#sh int port-channel2 trunk

Port        Mode         Encapsulation  Status        Native vlan
Po2         on           802.1q         trunking      1

Port        Vlans allowed on trunk
Po2         1-4094

Port        Vlans allowed and active in management domain
Po2         1,81-96,130-143

Port        Vlans in spanning tree forwarding state and not pruned
Po2         1,81-96,130-143
Cat3560#
---------------------End of output -------------------

The only noteworthy thing with the Procurve web interface configuration is displayed on the VLAN Participation / Tagging page. Since ProCurve ports g23 and g24 are busy doing a "Cisco Etherchannel - HP Trunk" these interfaces are greyed out. Instead a "HP Trunking interface" has popped up, allowing one to mark as Tagged the VLANs to be forwarded to/from the Procurve. Simple and straightforward, screenshot attached of VLAN participation/tagging + status of trunking interface.