Fault Symptom
A VLANIF interface goes Down.
Common Causes and Solutions
Table 1 describes common causes and solutions.
Table 1 Common causes and solutions for the VLANIF interface going down
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 [ step step-number [ increased | decreased ] ] 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.
|
A VLANIF interface only goes Up when at least one interface in the VLAN is Up.
|
No IP address is assigned to the VLANIF interface.
|
Run the ip address command in the VLANIF interface view to assign an IP address to the VLANIF interface.
|
The VLANIF interface is shut down.
|
Run the undo shutdown command in the VLANIF interface view to start the VLANIF interface.
|