• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 825
  • Last Modified:

Cisco 6513 port type unkown

When I perform a 'sh port' on our main switch I'm getting the following:

sh port
Port  Name                 Status          Vlan       Duplex Speed       Type
----- -------------------- ----------      ---------- ------ ----------- ------------
1/22                             not connect 1            full        1000    No Connector
1/23 Trunk-4948-ESX  connected   trunk      full        1000    Unknown
1/24                               connected  trunk      full        1000   1000BaseSX

Should I be conserned about the 'unknown'?

This is a newly created trunk that will handle a lot of vm traffic and I want  to be sure it is sound
before loading her up. Should I relace the gbic module?
  • 3
  • 3
1 Solution
Don JohnstonInstructorCommented:
Two questions:
Is a Cisco GBIC installed in the port?  Or is it a non-Cisco GBIC?
Is it working correctly?

If it's a non-Cisco GBIC, then that could be the reason.

And if it's working correctly anyway, then... I guess that's all that matters. :-)
Istvan KalmarHead of IT Security Division Commented:
If you use 3'rd party SFP you need:

service unsupported-transceiver
no errdisable detect cause gbic-invalid
cp361Author Commented:
@donjohnston:: Yeah it seems to be working OK just an Odd message.

@ikalmar: "service unsupported-transceiver
                   no errdisable detect cause gbic-invalid"

is this a statement (info)  or cli  to do?
We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

Don JohnstonInstructorCommented:
Don't worry about the commands. ikalmar doesn't understand that you're running CatOS.

Are the GBICs Cisco or not?
cp361Author Commented:

I will have to wait until I return to work on Monday  (PDT)  to confirm.... I was just sitting here worrying about a potential problem down the road when the ESX server we have built is fully loaded with mission critical VMS on the other end of the trunked port with a bad gbic... lol

I will report back when I find out.
cp361Author Commented:
Ok I swapped out the gbic and now the infomartion is being displayed as tp "type". The gbic I removed was indeed a cisco so this may have become a problem who knows and I replaced it with a cisco.
Don JohnstonInstructorCommented:
Probably a fault in the GBIC that interfered with the supervisor not recognizing the type of GBIC but still allowed traffic flow.
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.

Join & Write a Comment

Featured Post

WEBINAR: GDPR Implemented - Tips & Lessons Learned

Join the WatchGuard team on Thursday, March 29th as we recount some valuable lessons learned in weighing the needs of a business against the new regulatory environment, look ahead at the two months left before implementation, and help you understand the steps you can take today!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now