H3C Technologies H3C S12500-X Series Switches - Manual (Page 32)

26
Internet protocol processing: disabled
Tunnel source 1.1.3.1
Tunnel keepalive enabled, Period(20 s), Retries(2)
Network ID 1
Tunnel protocol/transport GRE_EVI/IP
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 drops
Output: 0 packets, 0 bytes, 0 drops
# Display information about EVI-Link interfaces on Switch C.
[SwitchC] display evi link interface tunnel 0
Interface Status Source Destination
EVI-Link0 UP 1.1.3.1 1.1.1.1
EVI-Link1 UP 1.1.3.1 1.1.2.1
# Display ENDC information.
[SwitchC] display evi neighbor-discovery client summary
Status: I-Init E-Establish P-Probe
Interface Local Address Server Address Network ID Reg Auth Status
Tunnel0 1.1.3.1 1.1.1.1 1 15 disabled E
# Display neighbor entries that Switch C has learned.
[SwitchC] display evi neighbor-discovery client member
Interface: Tunnel0 Network ID: 1
Local Address: 1.1.3.1
Server Address: 1.1.1.1
Neighbor System ID Created Time Expire Status
1.1.1.1 000F-0001-0001 2014/04/01 12:12:12 13 Up
1.1.2.1 000F-0000-0002 2014/04/01 12:12:12 13 Up
4. Verify that hosts in different sites can ping one another in the same extended VLAN.
Multiple-EVI-networks configuration example
Network requirements
Use EVI to connect the sites of the data center in Figure 7 . To isolate different types of traffic and extend
their VLANs to different sites, set up EVI networks as shown in Table 1 .
Table 1 EVI networks
Traffic type Network ID Extended VLANs Sites
Database 1 100, 101 2, 3, 4
Network management 2 4000 All sites
Web 3 50, 80 1, 4
In each EVI network, use the edge device at site 4 as an ENDS and all other edge devices as its ENDCs.