FSP_1.3.6.1.4.1.2011.5.25.183.1.22.49 hwPhyStackVlanConflict

Description

FSP/3/VLAN_CONFLICT: OID [OID] [octet] conflicts with the stack reserved VLAN. (VlanId=[integer])

The service VLAN conflicts with the stack reserved VLAN.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.183.1.22.49	Minor	environmentalAlarm(6)

Parameters

Name	Meaning
OID	Indicates the MIB object ID of the alarm.
[octet]	Indicates the services or protocols that conflict with the stack reserved VLAN.
[integer]	Indicates the stack reserved VLAN ID.

Impact on the System

The stack reserved VLAN has been used by other service modules. As a result, other devices cannot join the stack.

Possible Causes

When a master/standby switchover occurs in the stack or member switches in the stack restart, and the master switch becomes a standalone switch, the VLAN manually created by users or automatically created by protocols such as VCMP and GVRP is the same as the stack reserved VLAN ID.

Procedure

Run the display stack command to check the stack reserved VLAN ID.
Run the display vlan summary command to check the created VLANs. Determine whether the stack reserved VLAN has been created on the switch.
- If so, go to step 3.
- If not, collect alarm information and configuration information, and then contact technical support personnel.
Check whether the stack reserved VLAN ID can be changed to another VLAN ID.
- If so, run the stack reserved-vlan vlan-id command to change the stack reserved VLAN ID.
- If not, go to step 4.
Delete the created stack reserved VLAN ID.
- If the created stack reserved VLAN is Static VLAN, run the undo vlan vlan-id command to delete it.
- If the created stack reserved VLAN is Dynamic VLAN, run the undo gvrp command to disable the GVRP function.
- If the created stack reserved VLAN is Rrpp reserved, run the control-vlan command to change the control VLAN of RRPP.
- If the created stack reserved VLAN is Sep reserved, run the control-vlan (SEP segment view) command to change the control VLAN of SEP.