Configuring trunks on Dual Personality Ports on a HP ProCurve Switch

Hi I have a ProCurve 3500yl-24G.

I am creating a Trunk between this switch and our Core switch via SX Fiber.

I am using the CLI and when I show interface it lists all the ports 1-24.

looking on the panel I have
1-20,
21T-24T,
21M-24M,

I have installed the gigabit transceivers installed but not sure how to set the trunk on the interfaces. How do I reference the 21M-24M??

Does it automatically recognise the interfaces which are connected?

Was going to attempt to use

trunk 21-24 Trk12 Trunk

Any help is much appreciated.

BF
bigfooterAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
jburgaardConnect With a Mentor Commented:
Without topology, config's & logs my guesswork would include:
-double-check the vlan-settings in both ends for the trunks as it is now (that is after setting GBIC's in the ports)
-supported GBIC's vs firmware version. New firmware does not 'like' old GBIC's JxxxxA=old JxxxxC=new
-did you try swap the fibers from TXa--TXb & RXa--RXb to RXa--TXb & TXa--RXb  

HTH
0
 
jburgaardConnect With a Mentor Commented:
Does it automatically recognise the interfaces which are CONNECTED? exactly
I do not have a 3500yl-24G, but a some of other procurves.
What I have seen on these is If I have a config for one switch with fiber-GBIC's that I copy to an other switch where the GBIC's are not yet in place, then the vlan-tagging witch I felt was in place can disapear (revert to untagged vlan1) when the fiber-GBIC's  are seated.
0
 
bigfooterAuthor Commented:
Hi Thanks for your post.

I am testing today with a spare identical switch and that has helped. I have noticed the CLI does not accept orphaning interfaces and puts them back in the default VLAN.

I am going to Trunk on interfaces 21-24 and test the uplink with the GBIC modules to our core switch, give the vlan an IP address and test. Hopefully it should recognise I am using SX fiber and be in business.

Cheers
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
bigfooterAuthor Commented:
Just an update.

I put a gigabit transceiver into one of the spare interfaces and connected but for some reason it did not recognise as anything being connected... Just flashed for a while and then nothing.

I set the 21-24 as a trunk same as the trunk on the core switch.

If I set all four ports as a trunk do they all have to be connected?

Not sure what I am doing wrong here.

Thanks
0
 
jburgaardConnect With a Mentor Commented:
If I set all four ports as a trunk do they all have to be connected? no, they do not
What is in the log?
0
 
jburgaardCommented:
Some notes of operation are to be found in the manual at page 12-4 in http://cdn.procurve.com/training/Manuals/3500-5400-6200-6600-8200-MCG-Mar10-12-PortTrunk.pdf
fx you cannot mix cu-links and fiber-links to make a trunk.
In short both ends must match
-also in regard to vlan-tagging of the trunk (not individual ports)
0
 
bigfooterAuthor Commented:
Thanks for the posts and link. I can only connect to the switch with a console cable at them moment so will do some reading and see how I go on Monday. Will also grab the log output.

Makes sense about the uplinks matching and can confirm they do.

Interestingly, when I used an Patch Cable and configured the Trunk with the appropriate ports it worked fine.

I wonder why there is no reference to the GBIC / Fiber interfaces in the config.

Cheers
0
 
bigfooterAuthor Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.