You're correct. An switch port connected to another switch port should not have an Link "up" and Protocol "down", status.
Is the question asking whether this state is possible?
This is not a possible state on an L2 port connected to an L2 port.
Could you type the question exactly as it is written.
Two switches are connected together as shown below:
SwitchA# show interfaces fa0/1
Fa0/1 is up, line protocol is down (notconnect)
Hardware is fastethernet, address is 0008.xxxx.xxxx
The interface status of switch A is shown below:
The network administrator has verified that a functioning cable connects Switch A and Switch B shown above.
From the output that is shown above, what two pieces of information below are true?
(Choose two) -
A.Using a source mac address of 0008.xxxx.xxxx switch B is sending frames to switch A
B. The status of fa0/2 should be checked on Switch B
C. The interface is functional at OSI layer 1
D. There is likely to be an IP address issue on switch A Fa0/1
C is right, A and D dont make much sense
Well my answers to this question would be "B" and "C". However, the question is wrong concerning the line "up" and protocol "down" status. I'm also not sure as to why they have IP addresses assigned to physical switchports. Normally, on switches an IP is assigned to the "virtual" (interface vlan x) for remote management purposes. I think this question is very poorly written.
Then, again because the topology doesn't show whether fa0/2 is the actual port on switch B maybe one shouldn't infer that, that is the interface referenced from switch B.
Therefore, maybe "D" is correct because an IP should not be set on an physical switchport. An IP address cannot be assigned to an physical port on an switch because we're at L2, and L2 uses MAC addresses.
I would say B and C would be the answers on that one. Basically having a direct Layer 2 connection between two switches you're operating with 2 layers that need to be up - the line and the protocols that run between the switches. Up/Down indicates that while the phsyical line is good - meaning you're seeing that there is a device connected at the other side - but it is not negotiating the link successfully.
This could be caused by a unidirectional link of some type, a hardware/software failure on the switch, or the other side could be err-disabled or shutdown on the other side. This could also be a problem if different protocols are used for trunking(ISL vs dot1q).
I'll defer to the experts but B and C seem like reasonable answers (assuming that the cable is indeed connected to Fa0/2 on the other side...) B because we don't know what's configured on the other side (encapsulation, speed, duplex, etc) and C because the physical connectivity is up and the cable has been verified.
I'm looking for more clarification.
Here are my concerns:
1.) I can buy the hardware/software failure.
2.) If the other side were err-disabled, or shutdown the link/line wouldn't be in an "up" state at all...correct?
3.) I can also buy the trunking encapsulation although that info wasn't given?
Revised: Actually, having considered it further: I also believe you could have mismatched trunking protocols; or even one side configured as trunk, and the other as access, and the link would still be up; you just wouldn't be able to pass traffic. Please correct me if I'm wrong.
Please understand I'm simply looking for clarification and I always appreciate your knowledge and assistance.
Yes, you're correct mismatched trunking protocols does mean that one side is configured for ISL and the other side to dot1q. However, an mismatched setting would simply prevent an trunk from forming, or the passing of data across the trunk. However, the MAC-layer protocol of 802.3 or Ethernet II, which are basically the same thing, would still be in an "up" state.
Also, if one side is set with: switchport mode access, and the other side set to switchport mode trunk; their Administrative and Operational Modes would be set to either static access or trunk, respectively. You're correct, they wouldn't be trunking and this is not an correct/viable configuration.