HP T9576G06, Management Manual

Page: 170 / 778

SCF Commands for the SNMP Agent
SNMP Configuration and Management Manual — 424777-006
5 -2
Configuration Restrictions: Attribute Conflicts
SCF commands for controlling your SCF session, such as the ASSUME and ENV
commands, are not documented in this section. The
SCF Reference Manual for G-
Series Releases provides information about general SCF commands.
In the following syntax diagrams, remember that if you set a default PROCESS with
the ASSUME PROCESS command, you can omit the NonStop agent process name
and period and just specify
#object-name
. For example:
-> ASSUME PROCESS $ZSNMP
-> INFO ENDPOINT #END1
-> STATUS ENDPOINT #END1
Configuration Restrictions: Attribute Conflicts
The NonStop agent does not allow conflicting object definitions to coexist in the same
operations environment. All defined objects must be capable of being started
concurrently. If you want to add new objects or alter existing objects, you must first
stop and delete or stop and alter any other current object definitions whose attribute
values conflict with the values of the object you are creating.
Attribute Conflicts Within a NonStop Agent Configuration
Object definitions not allowed within a NonStop agent configuration:
•
Two ENDPOINT objects cannot use the same TCP/IP Internet address (same
NETWORK attribute and same or overlapping HOSTADDR attribute values).
•
Two PROFILE objects cannot be defined with the same community (same
COMMUNITY attribute value).
When you try to add the conflicting object definition within a NonStop agent
configuration with the SCF ADD command, SCF returns an “Attribute Conflict” error
See
Appendix B, SCF Error Messages for the NonStop Agent .
Attribute Conflicts Between NonStop Agent Configurations
Attribute conflicts between NonStop agent configurations refer to operations
environments in which more than one NonStop agent process is being run, either on
the same node or on different nodes in a network.
Two NonStop agents cannot be defined with ENDPOINT objects that use the same
TCP/IP Internet address or that use an address that is a member of a currently started
full wildcard (“0.0.0.0”) address set.
Attribute conflicts between NonStop agent configurations manifest themselves when
you try to activate the conflicting object definition with the SCF START command. SCF
returns a “Resource Not Available” error.