Establishing STP per VLAN basis instead of entire VLAN network, so one STP for one VLAN and this for the security purpose where Cisco extended its feature further naimg as PVSTP+,remember both are pvstp and pvstp+ are cisco proprietary and doesn't find use in other switches
you must ensure a loop free topology before disabling the spanning-tree protocol you must configure the same native VLAN on both ends of the trunk link
Vlan trunk Protocol
Configuring Standard STP Parameters STP is disabled by default on Routing Switches. By default, each port-based VLAN on an HP device runs a separate spanning tree (a separate instance of STP). An HP device has one port-based VLAN (VLAN 1) by default that contains all the device's ports.
The default value for network diameter on a STP configuration is 7 (seven). This value can be changed, using the command: Switch(config)#spanning-tree vlan 1 root primary diameter 5 This command changes the network diameter 50 5 (five) hops from end to end
designated and root
VLAN and PoE are used
A VLAN is a virtual LAN. In technical terms, a VLAN is a broadcast domain created by switches. Normally, it is a router creating that broadcast domain. With VLANs, a switch can create the broadcast domain. This works by, you, the administrator, putting some switch ports in a VLAN other than 1, the default VLAN. All ports in a single VLAN are in a single broadcast domain. Because switches can talk to each other, some ports on switch A can be in VLAN 10 and other ports on switch B can be in VLAN 10. Broadcasts between these devices will not be seen on any other port in any other VLAN, other than 10. However, these devices can all communicate because they are on the same VLAN. Without additional configuration, they would not be able to communicate with any other devices, not in their VLAN.
VLAN tagging using 802.1Q protocol.
Since VLAN's cannot communicate with other VLAN's directly, I believe you would have to set up a router to do that. I would check out how to set up a bridge between two VLAN's.
VLAN: How are packets distributed with respect to the different classifications?
The native VLAN is untagged. If the VLAN 99 traffic to the router is untagged (as it would be, because that is native on the switches), the router cannot interpret the data because there is no VLAN information in the header as expected. In turn, the router tags all VLAN 99 traffic outbound, and leaves VLAN 1 data untagged, so the switches are unable to correctly interpret either. VLAN traffic to the other VLANs should not be affected by the assignment of the native VLAN.
It is the VLAN that supports untagged traffic on an 802.1Q trunk