08-22-2014 11:01 AM - edited 03-07-2019 08:29 PM
Hi, I've been asked to configure a switchport to match the one next to it. easy enough right, except there seem to be some commands required that are not in the config. Can you help? Here are the 2 ports:
SWITCHA#sh run int fa5/10
Building configuration...
Current configuration : 290 bytes
!
interface FastEthernet5/10
description Port 106
switchport access vlan 111
switchport voice vlan 107
service-policy output autoqos-voip-policy
qos trust cos
no snmp trap link-status
auto qos voip trust
tx-queue 3
bandwidth percent 33
priority high
shape percent 33
end
SWITCHA#sh run int fa5/11
Building configuration...
Current configuration : 290 bytes
!
interface FastEthernet5/11
description Port 107
switchport access vlan 111
switchport voice vlan 107
service-policy output autoqos-voip-policy
qos trust cos
no snmp trap link-status
auto qos voip trust
tx-queue 3
bandwidth percent 33
priority high
shape percent 33
end
SWITCHA#sh int fa5/10 trunk
Port Mode Encapsulation Status Native vlan
Fa5/10 auto negotiate other 1
Port Vlans allowed on trunk
Fa5/10 none
Port Vlans allowed and active in management domain
Fa5/10 none
Port Vlans in spanning tree forwarding state and not pruned
Fa5/10 none
SWITCHA#sh int fa5/11 trunk
Port Mode Encapsulation Status Native vlan
Fa5/11 auto negotiate not-trunking 1
Port Vlans allowed on trunk
Fa5/11 107,111
Port Vlans allowed and active in management domain
Fa5/11 107,111
Port Vlans in spanning tree forwarding state and not pruned
Fa5/11 107,111
DON'T KNOW IF IT MAKES A DIFFERENCE, BUT ONE PORT IS UP AND THE OTHER IS NOT PLUGGED IN YET:
Fa5/10 down down Port 106
Fa5/11 up up Port 107
08-22-2014 02:20 PM
I am puzzled about this question. In the beginning you say that you need to configure a port like another port on the switch but that some commands appear to be missing. But as I look at the two ports that you show they seem to be quite the same. What did I miss? What is not the same? What do you think is missing?
HTH
Rick
08-25-2014 09:24 AM
Hi, Thanks for taking a look. I guess my concern is that when I run this command:
SWITCHA#sh int fa5/10 trunk
on each interface, I get different results. One says 2 VLANs are allowed. the other says none. So I would say they do not match in terms of functionality. The question is: what else do I need to do to get the ports to match?
08-25-2014 10:22 AM
This does shed a different light on the question. In the original post and in my original response I focused on the configuration that was shown. And that shows interfaces that appear to be configured as access ports - and the configuration is quite the same. Your follow up post focuses on the fact that negotiation for trunking is enabled on the switch and your question is really about the trunking aspect, which is not explicitly configured.
My guess at the explanation of the difference is that FA5/11 is up and has negotiated and has learned that two vlans are allowed while FA5/10 is not up, and so has not negotiated and has not yet learned what vlans are permitted on the trunk.
So my guess at what you need to do to get the ports to match would be that you need to connect FA5/10 similar to the connection of FA5/11.
HTH
Rick
08-26-2014 01:52 AM
Agree with Rick.
Kindly check what is connected to that port.
Do show int f5/10 >> does this shows as down down or up/up
And as Rick said remove the connected to port F5/11 and connect the same to F5/10 and see if the link comes up or not?
If link comes up then you dont have any issue with this box the other box which was connected to F5/10 is the culprit.
Regards
Inayath
08-23-2014 01:17 PM
I agree with Richard, other than the description they look pretty much the same.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide