Configuring VN Communication
Context
In the virtualization solution for large- and medium-sized campus networks, VNs cannot communicate with each other by default. If VNs need to communicate and the security requirement is not high, you can configure the border node to allow inter-VN communication. Partial VN communication can be configured by using the IP address prefix.
In this document, assume that wired and wireless employees in the R&D and marketing departments need to communicate with each other. You need to configure partial inter-subnet communication between RD_VN and Market_VN.
- The default VN cannot be used to configure VN communication.
- Inter-VN communication cannot be transferred. For example, VN1-to-VN2 communication and VN2-to-VN3 communication have been configured, but VN1 and VN3 cannot communicate. Thus, you need to configure VN1-to-VN3 communication independently.
- In the centralized gateway solution, wireless traffic enters a specified VN and is then forwarded out if the recommended tunnel forwarding mode is used on the WLAN and the border node functions as the native WAC and wireless subnet gateway. Wireless user subnets are configured to connect to VNs using commands. In this case, to allow wireless user subnet communication between VNs, you can run commands to configure reachable wireless user subnet routes between VN instances.
Configuration Tasks
Description |
Operation Procedure |
---|---|
Configuring VN communication |
|