Configuration Issues
Con?¬?guration of the port is another possible reason the port may be experiencing
connectivity issues. Some of the common con?¬?guration issues are as follows:
?– The VLAN to which the port belongs has disappeared: Each port in a switch
belongs to a VLAN. If the VLAN is deleted, then the port becomes inactive.
The following set of code illustrates that the command show interface interface will
not reveal a problem when a port is con?¬?gured to be part of a VLAN that does not exist.
SwitchX# sshh iinntt ffaa00//22
FastEthernet0/2 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is 0017.596d.2a02 (bia 0017.596d.2a02)
Description: Interface to RouterA F0/0
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
However, the command show interface interface switchport does show that the port
is inactive and will not be functional until the missing VLAN is replaced.
SwitchX# sshh iinntt ffaa00//22 sswwiittcchhppoorrtt
Name: Fa0/2
Switchport: Enabled
Administrative Mode: static access
Operational Mode: static access
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 5 (Inactive)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Some switches show a steady orange light on each port for which the associated VLAN
has disappeared.
Pages:
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142