No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R010C00 Configuration Guide - Ethernet Switching

This document describes the configuration of Ethernet services, including configuring link aggregation, VLANs, Voice VLAN, VLAN mapping, QinQ, GVRP, MAC table, STP/RSTP/MSTP, SEP, and so on.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
How Is the Inter-VLAN Communication Fault Rectified?

How Is the Inter-VLAN Communication Fault Rectified?

The possible causes for the fault of inter-VLAN communication through the VLANIF interface are as follows:
  1. The VLANIF interface is not Up.

    Run the display interface vlanif vlan-id to check the current state and Line protocol current state fields.

    <HUAWEI> display interface vlanif 2
    Vlanif2 current state : UP
    Line protocol current state : UP
    Last line protocol up time : 2014-12-26 11:09:08 UTC-08:00
    Description:
    Route Port,The Maximum Transmit Unit is 1500
    Internet Address is 10.1.1.2/24
    IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 4c1f-cc41-3a64
    Current system time: 2014-12-26 11:09:12-08:00
        Input bandwidth utilization  : --
        Output bandwidth utilization : --
    
    If the value of any one of the two fields is DOWN, the VLANIF interface is Down. Rectify this fault according to Table 4-11.
    Table 4-11  Common causes and solutions to the VLANIF interface Down event

    Common Cause

    Solution

    The VLAN corresponding to the VLANIF interface is not created.

    Run the vlan vlan-id command to create a VLAN corresponding to the VLANIF interface.

    The interface is not added to the VLAN.

    NOTE:
    • The port trunk pvid vlan vlan-id command only configures the PVID on a trunk interface, but does not add a trunk interface to a VLAN.
    • The port hybrid pvid vlan vlan-id command only configures the PVID on a hybrid interface, but does not add a hybrid interface to a VLAN.
    Run the following commands as required.
    • Run the port default vlan vlan-id command in the interface view to add an access interface to a VLAN.
    • Run the port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } command in the interface view to add a trunk interface to a VLAN.
    • You can add a hybrid interface to a VLAN in tagged or untagged mode. Run the port hybrid tagged vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } command to add a hybrid interface to a VLAN in tagged mode, or run the port hybrid untagged vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } command to add a hybrid interface to a VLAN in untagged mode.

    The physical status of all interfaces added to the VLAN is Down.

    Rectify this fault. A VLANIF interface goes Up as long as one interface in the VLAN is Up.

    No IP address is assigned to the VLANIF interface.

    Run the ip address ip-address { mask | mask-length } command to configure an IP address for the VLANIF interface.

    The VLANIF interface is shut down. That is, the value of current state is Administratively DOWN.

    Run the undo shutdown command in the VLANIF interface view to start the VLANIF interface.

  2. No corresponding routing entry is generated.

    When inter-VLAN communication is implemented across Layer 3 switches, the routing entries must exist on the switches. As shown in Figure 4-39, the routing entry with destination IP address 10.2.1.0/24 and next hop address 10.1.4.2 must exist on Switch1, and the routing entry with destination IP address 10.1.1.0/24 and next hop address 10.1.4.1 must exist on Switch2.

    Figure 4-39  Inter-VLAN communication across switches
    If routing entries do not exist, run the ip route-static command to configure a static route.
    • Switch1: ip route-static 10.1.2.0 255.255.255.0 10.1.4.2
    • Switch2: ip route-static 10.1.1.0 255.255.255.0 10.1.4.1
Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142081

Views: 258471

Downloads: 408

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next