Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
Last Published:
2025-04-13
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: AIX,Linux,Solaris,Windows
- Introduction
- Agent entry point overview
- About agent entry points
- Agent entry points described
- About the action entry point
- About the info entry point
- Considerations for using C++ or script entry points
- About the agent information file
- About the ArgList and ArgListValues attributes
- Creating entry points in C++
- About creating entry points in C++
- Syntax for C++ entry points
- Agent framework primitives
- Agent Framework primitives for container support
- Creating entry points in scripts
- About creating entry points in scripts
- Syntax for script entry points
- Agent framework primitives
- VCSAG_GET_ATTR_VALUE
- Agent Framework primitives with container support
- Example script entry points
- Logging agent messages
- Building a custom agent
- Building a script based IMF-aware custom agent
- Creating XML file required for AMF plugins to do resource registration for online and offline state monitoring
- Testing agents
- Static type attributes
- About static attributes
- Static type attribute definitions
- AdvDbg
- ArgList
- State transition diagram
- Internationalized messages
- Troubleshooting VCS resource's unexpected behavior using First Failure Data Capture (FFDC)
- Appendix A. Using pre-5.0 VCS agents
Attribute scope across systems: global and local attributes
An attribute whose value is the same across all systems on which the service group is configured global in scope. An attribute whose value applies on a per-system basis is local in scope.
The at operator (@) indicates the system to which a local value applies.
In the following example of the MultiNICA resource type, attributes applying locally are indicated by "@system" following the attribute name:
MultiNICA mnic ( Device@sysa = { le0 = "166.98.16.103", qfe3 = "166.98.16.105" } Device@sysb = { le0 = "166.98.16.104", qfe3 = "166.98.16.106" } NetMask = "255.255.255.0" ArpDelay = 5 RouteOptions@sysa = "default 166.98.16.103 0" RouteOptions@sysb = "default 166.98.16.104 0" )
In the preceding example, the value of the NetMask attribute is "255.255.255.0" on all systems, whereas the values of the Device attribute and the RouteOptions attribute are different on sysa and sysb.