Start a Conversation

Unsolved

This post is more than 5 years old

B

30873

June 19th, 2013 12:00

6224 Stack with SFPs

We have a stack with (2) 6224s. On port 2/g24 we have a 1000-LX SFP. It seems with that installed and operating ALL the other copper ports (1/g21-1/g24 and 1/g21-1/g23) no longer work. I can get link lights, but VLAN assignments appear to be ignored etc and no traffic is passing on the copper ports. Is this by design? Or am I majorly missing something. I really hate to lose 7 ports. 

5 Practitioner

 • 

274.2K Posts

June 19th, 2013 13:00

Combo ports have a combined input and output to and from the PHY chip. Only the optical port or the RJ-45 port cab be used singly, but not at the same time. Whichever cable is connected first will have use of the port PHY.

5 Practitioner

 • 

274.2K Posts

June 19th, 2013 14:00

Sorry i misread your post, i thought you were talking about the combo ports being used. Can you show us the config on the stack, including those ports that are not working. Also, what devices are being plugged into those ports and how are they configured?

Thanks

June 19th, 2013 14:00

So yo are saying if I have an SFP on 2/g24 with 1000-LX operating, 1/g21-g24 and 2/g21-g23 should still work normally for copper? We are not seeing that behavior at all.

June 19th, 2013 15:00

!Current Configuration:

!System Description "PowerConnect 6224, 3.3.5.5, VxWorks 6.5"

!System Software Version 3.3.5.5

!Cut-through mode is configured as disabled

!

configure

vlan database

vlan 15,30,75,90,120,135,1000

exit

ip telnet server disable

sntp unicast client enable

sntp client poll timer 1024

sntp server 64.90.182.55

clock summer-time recurring USA

clock timezone -5 minutes 0

stack

member 1 1

member 2 1

exit

ip address 192.168.60.7 255.255.255.0

ip default-gateway 192.168.60.1

ip https server

no ip http server

username "admin" password 5f4dcc3b5aa765d61d8327deb882cf99 level 15 encrypted

aaa authentication login "RadiusList" radius local

ip https authentication radius local

radius-server host auth 192.168.30.30

name "Default-RADIUS-Server"

timeout 5

key "XCI587gk6O1287g"

exit

line ssh

login authentication RadiusList

exit

ip ssh server

!

interface ethernet 1/g1

channel-group 1 mode auto

mtu 9216

exit

!

interface ethernet 1/g2

channel-group 1 mode auto

mtu 9216

exit

!

interface ethernet 1/g3

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g4

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g5

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g6

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g7

mtu 9216

switchport mode trunk

switchport trunk allowed vlan add 15,30,135

exit

!

interface ethernet 1/g8

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 1/g9

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 1/g10

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 1/g11

spanning-tree portfast

mtu 9216

switchport mode trunk

switchport trunk allowed vlan add 120

exit

!

interface ethernet 1/g12

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 1/g13

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 1/g14

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 1/g15

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 1/g16

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 1/g17

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 1/g18

spanning-tree portfast

mtu 9216

switchport access vlan 15

exit

!

interface ethernet 1/g19

channel-group 2 mode auto

mtu 9216

exit

!

interface ethernet 1/g20

channel-group 2 mode auto

mtu 9216                    

exit

!

interface ethernet 1/g21

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g22

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g23

mtu 9216

exit

!

interface ethernet 1/g24

mtu 9216

exit

!

interface ethernet 1/xg1

mtu 9216

exit

!

interface ethernet 1/xg2

mtu 9216

exit

!

interface ethernet 1/xg3

mtu 9216

exit

!

interface ethernet 1/xg4

mtu 9216

exit

!

interface ethernet 2/g1

channel-group 1 mode auto

mtu 9216

exit

!

interface ethernet 2/g2

channel-group 1 mode auto

mtu 9216

exit

!

interface ethernet 2/g3

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/g4

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/g5

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 2/g6

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 2/g7

mtu 9216

switchport mode trunk

switchport trunk allowed vlan add 15,30,135

exit

!

interface ethernet 2/g8

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 2/g9

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 2/g10

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 2/g11

spanning-tree portfast

mtu 9216

switchport access vlan 30

exit

!

interface ethernet 2/g12

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 2/g13

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 2/g14

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 2/g15

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 2/g16

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 2/g17

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 2/g18

spanning-tree portfast

mtu 9216

switchport access vlan 90

exit

!

interface ethernet 2/g19

channel-group 2 mode auto

mtu 9216

exit

!

interface ethernet 2/g20

channel-group 2 mode auto

mtu 9216

exit

!

interface ethernet 2/g21

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/g22

mtu 9216

exit

!

interface ethernet 2/g23

mtu 9216

exit

!

interface ethernet 2/g24

negotiation 1000f

traffic-shape 100000 kbps

spanning-tree portfast

mtu 9216

switchport access vlan 15

exit

!

interface ethernet 2/xg1

mtu 9216

exit

!

interface ethernet 2/xg2

mtu 9216

exit

!

interface ethernet 2/xg3

mtu 9216

exit

!

interface ethernet 2/xg4

mtu 9216

exit

!

interface port-channel 1

switchport mode trunk

switchport trunk allowed vlan add 1,15,30,75,90,120,135

mtu 9216

exit

!

interface port-channel 2

switchport mode trunk

switchport trunk allowed vlan add 1,15,30,75,90,120,135

mtu 9216

exit

snmp-server community Inn0va ro ipaddress 192.168.30.164

exit

That is the current configuration. However it was previously set to

interface ethernet 1/g22

mtu 9216

switchport access vlan15

exit

No matter what we did the copper on 1/g22 would not communicate on VLAN 15. So through trial and error we realized that the copper combo ports simply were acting strangely. I figured well, maybe if you use one SFP port, ALL combo ports only work via fiber.

June 19th, 2013 15:00

I forgot to mention configuration.

2/g24 has the 1000-LX SFP and goes to a fiber private line providing layer 2 to our office from our data center.

The remaining ports (1/g21-g24, 2/g21-23) were being used as copper ports to channel-group 2 or for an uplink to our firewall on VLAN 15.

5 Practitioner

 • 

274.2K Posts

June 20th, 2013 11:00

The combo ports work independent from each other. So if 2/g24 is using the SFP port, you cannot use the 2/g24 copper port. But all the other copper ports should still work.

I would like to get some more confirmation on whether this is related to the SFP port or not. I suggest scheduling a time when you can plug two clients into the copper side of the combo ports, so for example  2/g22 and 2/g23. Place those ports in access mode for VLAN 15, assign the clients static IP addresses suitable for the VLAN, and try to ping from one client to the other. Observe and record the outcome.

Then temporarily unplug the 2/g24 sfp connection and then test again, see If there is a change in behavior.

On a side note, the latest firmware for the 6200 switches has just came out.

 

I would suggest updating this also, as it can help with operability.

Thanks

No Events found!

Top