3Com corebuilder 3500 Implementation Manual page 184

Hide thumbs Also See for corebuilder 3500:

Table of Contents

The VLAN topologies that GVRP learns are treated differently from

VLANs that are statically configured. GVRP's dynamic updates are not

saved in NVRAM, while static updates are saved in NVRAM. When

GVRP is disabled, the system deletes all VLAN interfaces that were

learned through GVRP and leaves unchanged all VLANs that were

configured through the Administration Console, SNMP, or the Web

Management software.

GVRP manages the active topology, not nontopological data such as

VLAN protocols. If you need to classify and analyze packets by VLAN

protocols, you manually configure protocol-based VLANs. But if the

system needs to know only how to reach a given VLAN, then GVRP

provides all necessary information.

A GVRP-created VLAN is useful in situations where only Layer 2

switching needs to be performed for that VLAN. (Routing between a

GVRP-created VLAN and another VLAN can be performed with an

external router.) Because GVRP-created VLANs are assigned the

unspecified protocol type, router interfaces cannot be assigned to

them. Therefore, all communication within a GVRP-created VLAN is

constrained to that VLAN in allClosed mode; in allOpen mode, only

unicast frames with a known destination address can be transmitted

to another VLAN.