Networks

Question

Locked

Can't connect HP Procurve 2848 SFP to Cisco 3548XL GBIC 1000SX

By GerryC ·
Hi all,

I am trying to uplink an HP Procurve 2848 switch with a Cisco Catalyst 3548XL using an SFP on the Procurve and the GBIC fiber module on the Cisco. I have updated the firmware on the Cisco to 12.5(WC17) but I am not sure of the correct configuration. not have any VLANs configured, just the default VLAN1 on both devices.

CISCO Catalyst Config
interface GigabitEthernet0/2
flowcontrol
no negotiation auto
switchport trunk encapsulation dot1q
switchport mode trunk
no cdp enable

HP PROCURVE Config
interface 48
name "Cisco Uplink"
flow-control

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Re: Take a look at this

by GerryC In reply to Take a look at this

NetMan1958,

I think I have the problem resolved. I wasn't getting anywhere with the configuration changes so I swapped out the Catalyst 3548 and that did the trick. Must have been an issue with the GBIC slot. Now no CRC/alignment errors on HP Status page. Here are the configs being used. Would welcome any input for improvement.

HP Config Procurve 2848 w/1000Base SX SFP [SW=I.10.77]
interface 48
name "Cisco Uplink"
flow-control
speed-duplex 1000-full


Cisco 3548XL-EN w/1000BaseSX GBIC [Cisco IOS Software Release 12.0(5)WC10]

interface GigabitEthernet0/2
no negotiation auto
switchport trunk encapsulation dot1q
switchport mode trunk
no cdp enable

Collapse -

Hardware Issues

by NetMan1958 In reply to Re: Take a look at this

I re-read all of your posts last night and had started to think you had a hardware issue however I suspected it was on the Procurve end. Fooled me.

If you are no longer getting the CRC/alignment errors and can communicate with hosts across the switches, then your config should be OK.

Also, it's been a while since I worked with an HP switch but while I was re-reading your posts last night it started coming back to me. In HP Procurve land a "trunk" is equivalent to an "etherchannel" in Cisco land. So you don't really need to configure a trunk on the HP.

Also, the Procurve switches let you specify dot1Q tagging on a per/vlan - per/port basis where the Cisco inserts tags on trunk ports. The Cisco dot1Q by default does not tag frames belonging to the "native vlan" which is vlan 1 according to the output you posted from "sh vlan br".

So you should be good to go unless or until you add more vlans, then you will need to configure tagging on the HP switch.

Collapse -

Hardware Issues

by GerryC In reply to Hardware Issues

Netman1958,

All is quiet on the error logs. Thanks for all of your help.

Related Discussions

Related Forums