Creating VDC Interworking

27

Resources, such as cloud hosts, of different virtual data centers (VDCs) are isolated and cannot communicate with each other.
When you need two cloud hosts of different VDCs in the same cloud resource pool to communicate with each other, you can create VDC interworking. After the creation, the cloud hosts of different VDCs can communicate with each other on routed networks.

For details,seeCreating VDC Interworking,The applicable version is 3.0.8 or 3.0.9.

Other related questions:
Creating VPC Interworking
A virtual private cloud (VPC) can provide a secure, isolated network for virtual data centers (VDCs). Resources, such as cloud hosts, of different VPCs are isolated and cannot communicate with each other. When you need two cloud hosts of different VPCs to communicate with each other, create VPC interworking. After the creation, the cloud hosts of different VPCs can communicate with each other on routed networks. For details,seeCreating VPC Interworking, The applicable version is 3.0.8 or 3.0.9.

How Do I Create Private Specifications and Associate Them with VDCs
Public specifications are created on FusionSphere OpenStack OM and are visible to all VDCs. To select private specifications in VDCs, you need to create private specifications on FusionSphere OpenStack and associate them with the VDCs. Private specifications associated with VDCs are visible to only the VDCs. This section instructs system super administrators to create private specifications and associate them with VDCs. For details,seeHow Do I Create Private Specifications and Associate Them with VDCs,The applicable version is 3.0.9.

The System Prompts That the Number of CSHA Instances Exceeds the Remaining Quota in the Organization When Users Create a VDC or Modify VDC Quotas on ServiceCenter
【Product�? ServiceCenter 【Version�? 3.0.8, 3.0.8 SPC1, and 3.0.9 【Fault Type�? Resource management fault 【Symptom�? VDC creation is normal in a new organization with limited or unlimited quotas. After you create an organization with unlimited quotas and change it into one with limited quotas, the system reports "The VDC quota exceeded the available quota of the target organization." when you create or modify a VDC in the organization. 【Fault Locating�? Check ServiceCenter and database logs. The CSHA quota is �? in the organization. 【Root Cause�? When you change the organization with unlimited quotas to limited quotas, CSHA is not enabled. However, you have not changed the CSHA quota. When you try to create or modify a VDC, the system checks that the CSHA quota is �? in the organization and reports "The VDC quota exceeded the available quota of the target organization." 【Solution�? Upgrade ServiceCenter to 3.0.9 SPC1. 【Suggestions and Summary�? Before the upgrade, create an organization with unlimited quotas and do not change it into an organization with limited quotas immediately. If you have already changed the organization into one with limited quotas and the organization has other important data, change it back to unlimited quotas. ---End

Precautions for STP interworking on an S series switch
S (except the S1700) series switches adopt the standard STP/RSTP/MSTP algorithm. When a Huawei switch that runs STP interworks with a non-Huawei device, pay attention to the following: 1. If the non-Huawei device runs the standard STP algorithm, the Huawei switch can interwork properly with the device. 2. If the non-Huawei device runs a non-standard STP protocol except the Cisco Per VLAN Spanning Tree (PVST) protocol, the Huawei switch can transparently transmit STP packets from the device after the stp disable and bpdu enable commands are executed on the interface of the Huawei device connected to the non-Huawei device. 3. If the non-Huawei device is a Cisco device that runs PVST, the Huawei switch cannot negotiate with the device, but can transparently transmit packets from the device. 4. Check whether the configurations (such as the mode, root priority, and path cost) between the non-Huawei device and Huawei switch are consistent with each other. 5. Check the Proposal/Agreement mechanism. In enhanced mode, the current interface calculates the root interface when calculating the synchronization flag bit. In common mode, the interface ignores the root interface when calculating the synchronization flag bit. You can run the stp no-agreement-check command to configure the common fast transition mechanism on an interface. By default, the enhanced fast transition mechanism is configured on an interface. 6. There are two formats of MSTP BPDUs. One is dot1s, the format regulated in IEEE802.1s; the other is legacy, a private BPDU format. If the format of MSTP BDPUs is set to dotls on one interface and legacy on the peer interface, the negotiation fails. You can run the stp compliance { auto | dot1s | legacy } command to configure the specified STP BDPU format. The auto mode is set to allow an interface to automatically use the format of MSTP BDPUs sent from the remote interface. In this manner, the two interfaces use the same MSTP BDPU format. By default, MSTP BDPUs use the auto mode. 7. When a Huawei device is connected to a non-Huawei device, if the region name, revision level, and VLAN-to-instance mapping configured on the two devices are the same but the BPDU keys are different, the two devices cannot communicate with each other. To address this problem, run the stp config-digest-snoop command to enable the digest snooping function so that the BPDU keys on Huawei and non-Huawei devices are consistent.

Can the AR router interwork with a PBX
A PBX often provides E1 (DB9) and FXO (RJ11) interfaces. E1 and FXO interfaces can connect to the AR.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top