Chapter 9: shared network card

Chapter 9: shared network cardObjectives:
Application Service Overview
Share NICs between service groups
VCs agent
Use proxy Resources
Application Agent
Use parallel service groups and network resources Share Network Interfaces between service groups
If multiple service groups in a cluster have a unique Nic resource and a unique name for each service group, because for interfaces, each service group has its own Nic resource, every time VCs monitors the same interface, it does not need to increase overhead and network traffic. Use proxy resources to replace network configurations
You can use a proxy resource to allow multiple service groups to view the same network interface, which reduces the network traffic generated by multiple Nic resources monitoring the same interface in different service groups. Proxy resources type
Add the main. cf file:
Proxy appproxy (
Critical = 0
Targetresname = demonic
Proxy resources mirrors the status of another resource in different service groups. Required attribute, targetresname. The resource names are reflected by the proxy resource.
Optional attributes
Targetresname specifies the names of the systems whose target resource status is monitored. If no system is specified, the local system will be used as the target system. Use parallel service groups and network resources
You can further streamline your configurations to provide only network interfaces by creating a service group for multiple service groups in the same network. This service group is configured as the parallel service group because Nic resources are permanently and online in multiple systems. With this configuration, all other service groups are configured with a proxy for Nic resources on their local system.
This configuration type can easily monitor an operation workbench, because the status of the parallel service group can be used to indicate the status of the network interface on each system.
Determines the service group status
Services cannot include any Onoff resources as members and are not reported as online, even if their member resources are online, because none and ononly resources do not consider the status when VCs reports whether a service group is online. Use phantom resources to complete configuration
The phantom resource is used to report the actual status of a Service Group composed of only permanent resources. A Service Group is only online when all non-permanent resources are online. Therefore, if a service group only has permanent resources, VCs considers the group to be offline, even if the permanent resources are running properly, by adding a phantom resource, the status of the Service Group is displayed as online.
Note: Only use phantom Resources in the parallel service group. Phantom Resource Type
The phantom resource enables VCs to determine the status of the non-Onoff Resource Service Group.
1. A service group without any Onoff resources cannot be online unless they contain a phantom Resource
2. The Phantom resource is only used for the parallel service group. Configure a parallel service group
You cannot change an existing failover Service Group to include resources of a parallel service group in addition to the offline configuration process.
Create a parallel service group
1. Use any GUI or CLI to create
2. Set the parallel attribute to 1 (true)
3. Add resources
After setting the critical attribute, You need to verify that the service groups are online on all systems in the system list.
Note: If you have a service group that already contains resources, you must set the parallel attribute to restart VCs by modifying the main. cf file and using the modified configuration file. Localizing Resources)
Locate resource attributes
The value of this attribute is applied globally in all systems. The value of this attribute is applied to each system as a local scope. By default, all attributes are global, and some attributes can be localized, so that you can specify different values for different systems.
After you create a resource, you can set it as a property value. By using the hares command, Gui, or offline configuration method, use the CLI as follows:
Hares-local netnic Device
Hares-Modify netnic device qfe0-sys S1
Hares-Modify netnic device hme0-sys S2
Any attribute can be localized. network resources are a common example of localization attributes. From: http://hi.baidu.com/nitar/blog/item/eadb814e53f2e53aafc3abab.html