VLAN中继线在单端口机之间切换

Question

我有这个设置，这有点低端，因为我没有测试服务器来测试，所以我只是做我能做的，以达到目标设置。通常我会使用刀片或机架式服务器。

因此，我通常在机架式服务器中设置一个4以太网端口，但在桌面型计算机上只有1，所以我所做的是将其设置为VLAN，(eth1.100，eth2.100等)，并将其连接到2950 cisco交换机。我将连接到机器的端口配置为主干，这样所有的VLANS都会通过它。至于我为什么需要这些vlan是因为我需要4个端口，这是对台式计算机的限制(购买是NIC 4端口不是一个选项，所以我将坚持这个设置)。

现在，我的问题是，即使我已经将这些端口配置为主干，但我不能在PC0中将1.1.1.1 ping为1.1.1.2在PC1中。请参见下面的图片，以获得更易于理解的设置。此外，我还读到过，当您配置VLAN /sub时，物理端口将自动进入主干模式。

我做错什么了？

顺便说一句，作为一个补充信息，我测试了这个到一个正常的开关(不是管理，只是一个正常的家庭开关，我得到了成功的平)

让每个人都知道，我不能在数据包跟踪器上测试我的设置，因为我不能在PC机上配置数据包跟踪器中的VLAN (子接口)，上面的图片只是让每个人都对我的设置有一个清晰的视图。日志、安装、配置由于其隔离而不可用。

最新情况：

sw1#show interfaces trunk 
Port        Mode         Encapsulation  Status        Native vlan
Fa0/1       on           802.1q         trunking      1
Fa0/2       on           802.1q         trunking      1

Port        Vlans allowed on trunk
Fa0/1       1-1005
Fa0/2       1-1005

Port        Vlans allowed and active in management domain
Fa0/1       1,100
Fa0/2       1,100

Port        Vlans in spanning tree forwarding state and not pruned
Fa0/1       1,100
Fa0/2       1,100

sw1#

sw1#show interfaces fa0/1
FastEthernet0/1 is up, line protocol is up (connected)
  Hardware is Lance, address is 0030.a311.5301 (bia 0030.a311.5301)
 BW 100000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s
  input flow-control is off, output flow-control is off
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:08, output 00:00:05, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue :0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     956 packets input, 193351 bytes, 0 no buffer
     Received 956 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     2357 packets output, 263570 bytes, 0 underruns
     0 output errors, 0 collisions, 10 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
sw1#show interfaces fa0/2
FastEthernet0/2 is up, line protocol is up (connected)
  Hardware is Lance, address is 0030.a311.5302 (bia 0030.a311.5302)
 BW 100000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s
  input flow-control is off, output flow-control is off
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:08, output 00:00:05, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue :0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     956 packets input, 193351 bytes, 0 no buffer
     Received 956 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     2357 packets output, 263570 bytes, 0 underruns
     0 output errors, 0 collisions, 10 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
sw1#

sw1#show interfaces switchport 
Name: Fa0/1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: All
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Appliance trust: none

Name: Fa0/2
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: All
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Appliance trust: none

Answer 1

首先，在不同的VLANS中拥有一个具有子接口的端口与拥有四个端口并不是一回事。在不同的VLAN中拥有这么多NIC的机器通常是个坏主意。作为一个网络用户，我不相信服务器知道它应该发送什么接口。在您的场景中，您能确定最初的ping请求来自哪个NIC吗？如果不是每次都是eth1.100，ping就会失败。如果它退出eth1.100，并且当PC1接收到它时，它也可能失败，该机器发送除eth1.100以外的任何接口的回复。

您可以使用机器上的wireshark捕获来查找数据包的来龙去脉。

在交换机上做一个show mac address-table，看看哪个VLAN正在显示。虽然，与您的配置，这可能会改变的个人电脑的意愿。

从您的输出，只有VLAN 100实际上是集群到两台PC。所以你少了200,300和400。验证那些VLAN是用show vlan在交换机上创建的。