Question #808

This CCNA lab question focuses on fundamental switching concepts: VLANs, trunking, native VLANs, and EtherChannel (link aggregation). The goal is to configure the switches to ensure proper connectivity, VLAN segregation, and bandwidth optimization. Let's break down the lab and analyze each task in detail. ## **Overall Lab Context** The lab presents a network topology with four Cisco switches (SW-1, SW-2, SW-3, SW-4) connected in a square. The objective is to configure these switches to manage VLAN traffic and utilize EtherChannel for efficient link aggregation. All physical cabling is verified, and all ports are pre-configured as 802.1q trunks. **Key Technical Terms Explained:** * **VLAN (Virtual Local Area Network):** A logical grouping of devices on one or more LANs that behave as if they are on the same physical segment, even if they are located on different network switches. VLANs help segment networks, improve security, and manage broadcast domains. * **Trunk Port:** A switch port configured to carry traffic for multiple VLANs over a single physical link. This is essential for inter-switch communication where data from different VLANs needs to be forwarded. * **802.1q (Dot1q):** The industry-standard protocol for VLAN tagging on trunk links. When a frame (network data packet) belonging to a specific VLAN traverses a trunk port, an 802.1q header is added to the frame. This header contains the VLAN ID, allowing the receiving switch to identify which VLAN the frame belongs to. * **Tagged Traffic:** Network frames that have an 802.1q header added, indicating their VLAN ID. * **Untagged Traffic:** Network frames that do *not* have an 802.1q header. On a trunk link, untagged traffic is associated with the **Native VLAN**. * **Native VLAN:** On an 802.1q trunk link, the Native VLAN is the VLAN to which all untagged traffic belongs. It's crucial that the native VLAN configured on both ends of a trunk link matches; otherwise, connectivity issues can arise. * **EtherChannel (Link Aggregation):** A technology that bundles multiple physical Ethernet links into a single logical link. This provides increased bandwidth, load balancing across the bundled links, and redundancy (if one physical link fails, traffic is automatically rerouted over the remaining links). * **Port-Channel Interface:** The logical interface created when you bundle physical interfaces into an EtherChannel. Configuration applied to the Port-Channel interface affects all physical interfaces within that bundle. * **LACP (Link Aggregation Control Protocol):** An industry-standard protocol (IEEE 802.3ad) used to automatically negotiate and manage EtherChannel bundles between compatible switches. * **`mode active`:** The interface actively initiates LACP negotiation. It sends LACP BPDUs (Bridge Protocol Data Units) to the other switch. * **`mode passive`:** The interface responds to LACP BPDUs from the other switch but does not initiate negotiation. * **`mode on`:** The interface forms an EtherChannel unconditionally, without LACP negotiation. Both sides must be configured with `mode on` for this to work, and it lacks the dynamic negotiation benefits of LACP. "Immediately negotiate the link aggregation" often points to `active` mode for LACP. ## **Topology and VLAN Information** * **SW-1 <-> SW-2:** Connected via e0/1 on both switches. * **SW-1 <-> SW-3:** Connected via e0/2 on SW-1 and e0/2 on SW-3. * **SW-2 <-> SW-4:** Connected via e0/2 on SW-2 and e0/2 on SW-4. * **SW-3 <-> SW-4:** Connected via e0/0 and e0/1 on both switches. This is where EtherChannel (Po34) will be formed. **VLAN IDs:** * **56 and 77:** Allowed (These are *tagged* VLANs that should be permitted on trunks). * **99:** Untagged (This will be the *Native VLAN* on specific links). ## **Detailed Analysis of Each Task** ### **Task 1: Configure both SW-1 and SW-2 ports e0/1 and e0/2 to permit only the allowed VLANs** **Objective:** Restrict the VLANs that can traverse the trunk links connected to SW-1 and SW-2. By default, trunk ports usually allow all VLANs. Limiting them to only necessary VLANs (56 and 77) improves security, reduces unnecessary broadcast traffic, and optimizes switch resource usage. **Commands Used and Explanation:** ``` SW-1# configure terminal SW-1(config)# interface range e0/1-2 SW-1(config-if-range)# switchport trunk allowed vlan 56,77 SW-1(config-if-range)# end SW-1# write memory SW-2# configure terminal SW-2(config)# interface range e0/1-2 SW-2(config-if-range)# switchport trunk allowed vlan 56,77 SW-2(config-if-range)# end SW-2# write memory ``` * `configure terminal`: Enters global configuration mode. * `interface range e0/1-2`: Allows you to configure multiple interfaces (e0/1 and e0/2) simultaneously, saving time and ensuring consistent configuration. * `switchport trunk allowed vlan 56,77`: This command is applied to trunk interfaces. It specifies that only VLANs 56 and 77 are permitted to send and receive traffic over these trunks. Any other VLAN traffic will be dropped. * `end`: Exits configuration mode and returns to privileged EXEC mode. * `write memory` (or `copy running-config startup-config`): Saves the running configuration (current active settings) to NVRAM (Non-Volatile RAM) so that the configuration persists after a device reboot. ### **Task 2: Configure both SW-3 and SW-4 ports e0/2 to permit only the allowed VLANs** **Objective:** Similar to Task 1, this task restricts VLANs on the specific trunk links connecting SW-1 to SW-3 (via e0/2) and SW-2 to SW-4 (via e0/2). **Commands Used and Explanation:** ``` SW-3# configure terminal SW-3(config)# interface e0/2 SW-3(config-if)# switchport trunk allowed vlan 56,77 SW-3(config-if)# end SW-3# write memory SW-4# configure terminal SW-4(config)# interface e0/2 SW-4(config-if)# switchport trunk allowed vlan 56,77 SW-4(config-if)# end SW-4# write memory ``` * The commands are identical in function to Task 1, but they are applied to single interfaces (e0/2 on SW-3 and SW-4) rather than a range, as only one interface needs configuration on each switch for this task. ### **Task 3: Configure both SW-1 and SW-2 e0/1 ports to send and receive untagged traffic over VLAN 99** **Objective:** Designate VLAN 99 as the Native VLAN for the trunk link between SW-1 e0/1 and SW-2 e0/1. This means any untagged frames received on these ports will be assigned to VLAN 99, and any frames sent from VLAN 99 on these ports will be sent untagged. It's critical that the native VLAN matches on both ends of the trunk for proper communication. **Commands Used and Explanation:** ``` SW-1# configure terminal SW-1(config)# interface e0/1 SW-1(config-if)# switchport trunk native vlan 99 SW-1(config-if)# end SW-1# write memory SW-2# configure terminal SW-2(config)# interface e0/1 SW-2(config-if)# switchport trunk native vlan 99 SW-2(config-if)# end SW-2# write memory ``` * `interface e0/1`: Selects the specific interface to configure. * `switchport trunk native vlan 99`: Configures VLAN 99 as the native VLAN for this 802.1q trunk port. ### **Task 4: Configure both SW-3 and SW-4 ports e0/0 and e0/1 for link aggregation using the industry standard protocol. All ports must immediately negotiate the link aggregation** **Objective:** Create an EtherChannel bundle between SW-3 and SW-4 using the two physical links (e0/0 and e0/1). The "industry standard protocol" refers to LACP (Link Aggregation Control Protocol), and "immediately negotiate" points to using the `active` LACP mode. This will create a logical Port-Channel interface, increasing bandwidth and providing redundancy between SW-3 and SW-4. **Commands Used and Explanation:** ``` SW-3# configure terminal SW-3(config)# interface range e0/0-1 SW-3(config-if-range)# channel-group 34 mode active SW-3(config-if-range)# end SW-3# write memory SW-4# configure terminal SW-4(config)# interface range e0/0-1 SW-4(config-if-range)# channel-group 34 mode active SW-4(config-if-range)# end SW-4# write memory ``` * `interface range e0/0-1`: Selects the physical interfaces that will be part of the EtherChannel. * `channel-group 34 mode active`: This is the core command for creating an EtherChannel. * `channel-group 34`: Specifies that these interfaces should be bundled into Port-Channel interface 34. The number (34 in this case) is locally significant on each switch but usually chosen to match for clarity (Po34 as indicated in the topology). * `mode active`: Configures the interfaces to actively send LACP packets, attempting to form an EtherChannel. For a successful LACP EtherChannel, at least one side must be `active`. Using `active` on both sides ensures immediate negotiation and robust setup. ### **Task 5: Permit only the allowed VLANs on the new link** **Objective:** Apply the VLAN filtering (allowing only VLANs 56 and 77) to the newly created logical Port-Channel interface (Po34). Remember, configurations for EtherChannel functions (like trunking, allowed VLANs, native VLAN) should be applied to the *Port-Channel interface* rather than the individual physical member interfaces. **Commands Used and Explanation:** ``` SW-3# configure terminal SW-3(config)# interface port-channel 34 SW-3(config-if)# switchport trunk encapsulation dot1q SW-3(config-if)# switchport mode trunk SW-3(config-if)# switchport trunk allowed vlan 56,77 SW-3(config-if)# end SW-3# write memory SW-4# configure terminal SW-4(config)# interface port-channel 34 SW-4(config-if)# switchport trunk encapsulation dot1q SW-4(config-if)# switchport mode trunk SW-4(config-if)# switchport trunk allowed vlan 56,77 SW-4(config-if)# end SW-4# write memory ``` * `interface port-channel 34`: Enters configuration mode for the logical Port-Channel interface that was created in Task 4. * `switchport trunk encapsulation dot1q`: Explicitly sets the trunk encapsulation method to 802.1q. While physical ports were pre-configured, a newly created logical interface might need this explicitly set, or it's good practice to ensure consistency. * `switchport mode trunk`: Configures the Port-Channel interface as a trunk port. This is necessary for it to carry traffic from multiple VLANs. Even though physical ports were pre-configured as trunks, the logical interface is new and needs to be configured as a trunk itself. * `switchport trunk allowed vlan 56,77`: Applies the VLAN filtering, allowing only VLANs 56 and 77 to pass over this EtherChannel trunk link. ## **Conclusion and Key Takeaways** This lab demonstrates essential Cisco IOS commands for configuring VLANs, trunking, native VLANs, and EtherChannel. **Important points to remember:** * **Consistency is Key:** For trunks and EtherChannels to function correctly, configurations (like native VLAN, LACP mode, allowed VLANs) must match on both ends of the link. * **Logical vs. Physical:** When configuring EtherChannel, apply trunking and VLAN-related commands to the *Port-Channel interface*, not the individual physical member interfaces. * **Security and Efficiency:** Restricting allowed VLANs on trunk links is a best practice for security and network performance. * **Saving Configuration:** Always use `write memory` or `copy running-config startup-config` to save your configurations, especially in a lab environment, to ensure they persist after a reboot. * **LACP Modes:** Understand the difference between `active`, `passive`, and `on` modes for EtherChannel negotiation. `Active` is often preferred for dynamic negotiation.

Cisco試験におけるこのラボ問題は、**VLANトランキングの最適化（VLAN Pruning）**、**ネイティブVLANの設定**、および**LACP（Link Aggregation Control Protocol）**の構成能力を問う実機操作問題です。 以下に、各タスクの技術的解説と、推奨される設定コマンドをまとめます。 --- # 📝 試験問題解析：VLANトランキングとLACPの構成 ## 1. タスク概要と技術ポイント ### タスク 1 & 2: VLAN Allowed List の設定 * **目的**: トランクリンクを通過できるVLANを制限し、不要なブロードキャストトラフィックを遮断して帯域を節約します。 * **技術点**: `switchport trunk allowed vlan` コマンドを使用します。試験では指定されたVLAN ID（例: 10, 20, 30など）を正確に入力する必要があります。 ### タスク 3: ネイティブVLANの設定 * **目的**: タグなし（Untagged）トラフィックを特定のVLAN（VLAN 99）として処理するように設定します。 * **技術点**: 両端のスイッチで一致させる必要があります。一致しない場合、ネイティブVLANミスマッチのログが表示されます。 ### タスク 4: LACP（業界標準プロトコル）によるリンク集約 * **目的**: 複数の物理リンクを1つの論理リンク（EtherChannel）にまとめ、帯域幅の拡大と冗長性を確保します。 * **技術点**: 「業界標準（Industry Standard）」は **LACP (802.3ad)** を指します（PAgPはCisco独自）。「即座にネゴシエーション（Immediately negotiate）」という指示があるため、モードは **`active`** を選択します。 ### タスク 5: Port-Channel上でのVLAN制限 * **目的**: 作成した論理インターフェース（Port-Channel）に対しても、物理ポートと同様にVLAN制限を適用します。 --- ## 2. 推奨設定コマンド（CLI） ※試験環境で指定されているVLAN IDを `` と表記します。 ### SW-1 / SW-2 の設定 ```ios ! Task 1 & 3: e0/1 の設定 interface Ethernet0/1 switchport trunk allowed vlan switchport trunk native vlan 99 exit ! Task 1: e0/2 の設定 interface Ethernet0/2 switchport trunk allowed vlan exit ``` ### SW-3 / SW-4 の設定 ```ios ! Task 4: LACPの設定 (e0/0, e0/1) interface range Ethernet0/0 - 1 channel-group 1 mode active exit ! Task 2 & 5: e0/2 および Port-Channel の設定 interface Ethernet0/2 switchport trunk allowed vlan exit interface port-channel 1 switchport mode trunk switchport trunk allowed vlan exit ``` --- ## 3. 実装の重要ポイント（エキスパートのアドバイス） 1. **LACPモードの選択**: * `active`: 自らLACPパケットを送信し、積極的にネゴシエーションを行います（今回の指示「immediately negotiate」に合致）。 * `passive`: 相手からLACPパケットが届いた場合のみ応答します。 * `desirable / auto`: これらはCisco独自の **PAgP** 用であり、今回使用してはいけません。 2. **トランク設定の順序**: * EtherChannelを構成する場合、物理ポートに設定を入れる前に `channel-group` を作成するか、作成した後の `interface port-channel` に対して設定を適用するのがベストプラクティスです。これにより、メンバーポート間での設定の不一致（Suspended状態）を防げます。 3. **VLAN 99 の作成**: * タスクには明記されていませんが、ネイティブVLANとして機能させるために、各スイッチで `vlan 99` が作成されているか確認してください（通常、事前設定されていますが、念のため `show vlan brief` で確認を推奨します）。 4. **保存の忘れ厳禁**: * 指示にある通り、次の問題に進む前に必ず `copy running-config startup-config` または `write` を実行してください。これを忘れると、ラボのスコアが加算されない場合があります。 ## 4. 検証コマンド 設定後、以下のコマンドで状態を確認してください。 * `show interfaces trunk`: 指定したVLANのみが Allowed になっているか、Native VLANが99かを確認。 * `show etherchannel summary`: 状態が `P` (Bundled in port-channel) になっているかを確認。 * `show ip interface brief`: インターフェースが Up/Up であることを確認。 以上が、このラボ問題の専門的な解析と解答指針です。

這是一份針對 Cisco 認證考試（如 CCNA/CCNP）中常見的實作題（Lab Item）進行的專業解析。本題主要考察 **VLAN Trunking（802.1Q）**、**Native VLAN 設定** 以及 **LACP 鏈路聚合（EtherChannel）** 的配置能力。 --- # 📝 考題專業解析：VLAN 與 EtherChannel 配置實作 ## 1. 考題重點分析 (Exam Topics Analysis) 本實驗題涵蓋了交換網路（Switching Network）中四個核心知識點： * **VLAN Trunking 限制 (VLAN Pruning/Allowed List)：** 透過手動配置允許的 VLAN ID 來增強網路安全性與減少廣播風暴。 * **Native VLAN 設定：** 變更預設的 Untagged VLAN（預設為 VLAN 1）以符合安全性最佳實踐。 * **LACP (Link Aggregation Control Protocol)：** 使用業界標準協議（IEEE 802.3ad）進行鏈路聚合。 * **Port-channel 介面管理：** 確保物理介面與邏輯介面（Port-channel）的配置一致性。 --- ## 2. 任務分解與指令實作 (Task Breakdown & CLI) ### 任務 1 & 2：限制 Trunk 允許的 VLAN **要求：** 在 SW-1、SW-2、SW-3、SW-4 的指定連接埠上僅允許特定的 VLAN 通過。 *注意：題目中未明示具體 VLAN ID，實務考試時請參照 Topology 或 Task 說明中的 VLAN 列表（假設為 VLAN 10, 20, 30）。* **配置範例 (以 SW-1 為例)：** ```ios SW-1(config)# interface range e0/1 - 2 SW-1(config-if-range)# switchport trunk allowed vlan 10,20,30 ``` *(SW-2, SW-3, SW-4 需根據題目要求的介面進行相同邏輯的操作)* --- ### 任務 3：配置 Native VLAN **要求：** SW-1 與 SW-2 的 e0/1 埠需將 VLAN 99 設為 Untagged 流量所屬 VLAN。 **配置範例：** ```ios SW-1(config)# interface e0/1 SW-1(config-if)# switchport trunk native vlan 99 SW-2(config)# interface e0/1 SW-2(config-if)# switchport trunk native vlan 99 ``` * **專家提示：** 兩端的 Native VLAN 必須一致，否則會觸發 CDP 的 `Native VLAN mismatch` 警告，導致生成樹（STP）不一致。 --- ### 任務 4：配置 LACP 鏈路聚合 **要求：** SW-3 與 SW-4 的 e0/0, e0/1 進行聚合，使用「業界標準協議」且「立即協商」。 * **業界標準：** 指的是 **LACP** (Link Aggregation Control Protocol)。 * **立即協商：** 模式必須設定為 **`active`** (主動發起協商)。 **配置範例 (以 SW-3 為例)：** ```ios SW-3(config)# interface range e0/0 - 1 SW-3(config-if-range)# channel-group 1 mode active ``` --- ### 任務 5：Port-channel 上的 VLAN 限制 **要求：** 在新建立的 EtherChannel (Port-channel) 上僅允許特定 VLAN。 **配置範例 (以 SW-3 為例)：** ```ios SW-3(config)# interface port-channel 1 SW-3(config-if)# switchport mode trunk SW-3(config-if)# switchport trunk allowed vlan 10,20,30 ``` * **專家提示：** 最佳實踐是在 `interface port-channel` 下進行配置，系統會自動同步至所屬的物理成員埠（e0/0, e0/1）。 --- ## 3. 完整配置參考清單 (Final Checklist) ### SW-1 ```ios interface e0/1 switchport trunk native vlan 99 switchport trunk allowed vlan interface e0/2 switchport trunk allowed vlan ``` ### SW-2 ```ios interface e0/1 switchport trunk native vlan 99 switchport trunk allowed vlan interface e0/2 switchport trunk allowed vlan ``` ### SW-3 & SW-4 ```ios interface range e0/0 - 1 channel-group 1 mode active ! interface port-channel 1 switchport mode trunk switchport trunk allowed vlan ! interface e0/2 switchport trunk allowed vlan ``` --- ## 4. 關鍵注意事項 (Critical Success Factors) 1. **存檔 (Save Configuration)：** 題目特別要求「Save your configurations to NVRAM」，在完成所有配置後，務必在每台 Switch 執行： * `SW-1# copy running-config startup-config` 或 `write`。 2. **LACP 模式選擇：** * `active`：主動協商 (符合題目要求的 "immediately negotiate")。 * `passive`：被動等待 (不符合本題要求)。 * `desirable/auto`：這是 Cisco 私有的 PAgP 協議，不符合題目要求的 "industry standard"。 3. **封裝協議：** 題目提到 "All ports are pre-configured as 802.1q trunks"，但在某些舊版設備上，可能需要手動輸入 `switchport trunk encapsulation dot1q`。 4. **禁止修改：** 切勿更改主機名 (hostname) 或 enable 密碼，否則系統自動評分可能會失敗。 --- **解析專家：** Cisco Certified Technical Expert **建議：** 實作題最重細節，配置完畢後建議使用 `show interfaces trunk` 與 `show etherchannel summary` 進行最終驗證。

这是一份针对思科认证考试（如 CCNA 或 CCNP）中典型实验题的深度解析。本题主要考察 **VLAN Trunking（中继）**、**Native VLAN（本征 VLAN）** 以及 **EtherChannel（链路聚合/LACP）** 的配置。 --- # 📝 考题专业解析：交换网络综合配置实验 ## 1. 考题要点概览 (Key Objectives) 本实验要求在四台交换机（SW-1, SW-2, SW-3, SW-4）之间建立稳定的二层连接。核心技术点包括： * **Trunk 允许列表控制**：限制 Trunk 链路上通行的 VLAN，增强安全性。 * **Native VLAN 配置**：修改本征 VLAN 以匹配管理或特定流量需求。 * **LACP 链路聚合**：使用行业标准协议（IEEE 802.3ad）增加带宽并提供冗余。 * **配置持久化**：要求保存至 NVRAM。 --- ## 2. 任务分解与配置步骤 (Step-by-Step Configuration) ### 任务 1 & 2：配置允许的 VLAN 列表 **要求**：在指定端口上仅允许特定的 VLAN 通过。 > **注意**：题目中未给出具体的 VLAN ID 列表。在实际考试中，请务必查看“Tasks”选项卡或拓扑说明中的具体数字（例如 `10,20,99`）。以下示例假设允许的 VLAN 为 `10,20,99`。 * **SW-1 & SW-2**: ```ios SW-1(config)# interface range e0/1 - 2 SW-1(config-if-range)# switchport trunk allowed vlan 10,20,99 ``` * **SW-3 & SW-4**: ```ios SW-3(config)# interface e0/2 SW-3(config-if)# switchport trunk allowed vlan 10,20,99 ``` ### 任务 3：配置 Native VLAN (本征 VLAN) **要求**：在 SW-1 和 SW-2 的 e0/1 端口上设置 VLAN 99 为 Native VLAN。 > **原理**：Native VLAN 上的流量在 Trunk 链路上是不打标签（Untagged）的。链路两端的 Native VLAN 必须一致，否则会触发 CDP 报错。 * **SW-1 & SW-2**: ```ios SW-1(config)# interface e0/1 SW-1(config-if)# switchport trunk native vlan 99 ``` ### 任务 4：配置 LACP 链路聚合 **要求**：在 SW-3 和 SW-4 之间，将 e0/0 和 e0/1 聚合。使用“行业标准协议”（即 **LACP**），且要求“立即协商”（即 **Active** 模式）。 * **SW-3 & SW-4**: ```ios SW-3(config)# interface range e0/0 - 1 SW-3(config-if-range)# channel-group 1 mode active ``` ### 任务 5：在 Port-channel 上配置允许的 VLAN **要求**：确保新创建的聚合链路（Port-channel）也应用了 VLAN 允许列表。 * **SW-3 & SW-4**: ```ios SW-3(config)# interface port-channel 1 SW-3(config-if)# switchport mode trunk SW-3(config-if)# switchport trunk allowed vlan 10,20,99 ``` --- ## 3. 完整配置脚本参考 (以 SW-3 为例) 为了确保考试不丢分，建议按照以下逻辑顺序操作： ```ios ! 进入全局配置模式 conf t ! 任务 2: 配置 e0/2 的允许 VLAN interface e0/2 switchport trunk allowed vlan 10,20,99 ! 任务 4: 配置 LACP 聚合 interface range e0/0 - 1 channel-group 1 mode active ! 任务 5: 配置 Port-channel 属性 interface port-channel 1 switchport mode trunk switchport trunk allowed vlan 10,20,99 ! 任务 6: 保存配置 (极其重要) end copy running-config startup-config ``` --- ## 4. 关键考点与易错点提示 (Expert Tips) 1. **LACP 协议模式选择**： * 题目要求“Industry standard protocol”（行业标准协议），必须使用 **LACP**。 * 题目要求“Immediately negotiate”（立即协商），必须使用 **`mode active`**。如果使用 `mode desirable`，那是思科私有的 PAgP 协议，不符合题意。 2. **Native VLAN 一致性**： * 在 SW-1 和 SW-2 互联的链路上，两端都必须配置 `switchport trunk native vlan 99`。如果只配一端，会导致生成树（STP）环路风险或通信中断。 3. **Port-channel 继承性**： * **最佳实践**：先创建 `channel-group`，然后进入 `interface port-channel X` 进行 `switchport` 相关配置。这样配置会自动同步到成员物理接口（e0/0, e0/1）上，避免成员接口配置不一致导致聚合失败（Suspended 状态）。 4. **保存配置**： * 实验题最后一步必须执行 `copy run start` 或 `write`。思科自动评分系统通常会检查 NVRAM 中的 `startup-config`。 5. **验证命令** (建议在提交前执行)： * `show interface trunk`：确认各端口的 Allowed VLAN 和 Native VLAN。 * `show etherchannel summary`：确认 Port-channel 状态是否为 **SU** (S=Switched, U=In use)，协议是否为 **LACP**。 --- **💡 总结**：本题难度中等，关键在于对 LACP 模式的理解以及对 Trunk 允许列表的精确配置。务必仔细阅读题目要求的 VLAN 范围，确保不遗漏任何一个接口。