|
|
|
|
This command creates containers.
container.create "serviceName=<value>"
, "serviceType=<device|test>"
, "memberListMethod=<auto|manual>"
, {membership_parameters}
, {severity_parameters}
[, "parentNames=none|<value1,value2,...>"]
[, "actionName=none|<value>"]
[, "comment=<value>"]
[, "displayComment=<true|false>"]
[, "departmentName=<string>"]
The container name must be unique within the end user department or administrative group, and must not be case sensitive. The container name cannot be the same as a device in your Traverse environment. Containers cannot have the same name as an existing device.
When serviceType=device (default) and memberListMethod=manual (default), {membership_parameters} include the following:
, memberList=<regexp_1,regexp_2,...>.
If any comma-separated entry for the value of memberList begins with #, it indicates another container is nested below this new container. Administrator users can specify devices from end user departments by using the department name as a prefix with a dash (-) as a separator.
Examples:
container.create "serviceName=My Admin Container", "serviceType=device", "memberListMethod=manual", "memberList=Corporate - cisco*,#Another Admin
Container", "severityMethod=auto"
container.create "serviceName=All End User Containers", "serviceType=device", "memberListMethod=manual", "memberList=\* - #*"
Note the use of a wildcard for both the department and container names. If a matching department name is not found, use the entire entry as a device in the user's department.
When serviceType=device and memberListMethod=auto, {membership_parameters}include the following:
[, "ruleDeviceName=<value>"]
[, "ruleDeviceType=<value>"]
[, "ruleDeviceModel=<value>"]
[, "ruleDeviceVendor=<value>"]
[, "ruleDeviceTag1=<value>"]
[, "ruleDeviceTag2=<value>"]
[, "ruleDeviceTag3=<value>"]
[, "ruleDeviceTag4=<value>"]
[, "ruleDeviceTag5=<value>"]
You must specify at least one rule. You can specify each rule parameter only once. The value supports multiple regular expressions.
Example:
container.create "serviceName=San Jose Devices", "serviceType=device",
"memberListMethod=auto", "ruleDeviceName=*sjc*",
"ruleDeviceType=unix*", "actionName=HQ Failure", "displayComment=false"
When serviceType=test, memberListMethod is an optional parameter with manual as the only valid value. {membership_parameters} include the following:
, "testListMethod=<auto|manual>"
[, "testName=<regexp_1,regexp_2,...>"]
[, "testType=<type_subtype_pair_1,type_subtype_pair_2,...>"]
When serviceType=test and testListMethod=auto, testName and testType parameters are not required. Instead, you must include all current and future tests for the selected devices in the container.
Example:
container.create "serviceName=Router Tests", "serviceType=test",
"memberListMethod=manual", "memberList=cisco*", "testListMethod=auto",
"actionName=none"
When serviceType=test and testListMethod=manual, the testName parameter is required. testType is an optional parameter that you can use to further filter the list of tests.
Example:
container.create "serviceName=All RTT Tests", "serviceType=test",
"memberListMethod=manual", "memberList=*", "testListMethod=manual",
"testName=*", "testType=ping/rtt", "actionName=Slow Response",
"comment=Response Time to Remote Sites", "displayComment=true"
severity_parameters includes the following, where N = 1, 2, or 3:
[, "severityMethod=<auto|manual>"]
[, "ratioN=<value>"]
[, "memberSeverityN=<ok|unknown|warning|critical>"]
[, "serviceSeverityN=<ok|unknown|warning|critical>"]
If severityMethod=auto, the remaining parameters are not required. If severityMethod=manual, you must specify at least one set of parameters. A complete set includes all three parameters.You can use the parentNames parameter to nest the a newly created container under other existing containers. Because you can nest a container below multiple containers, the value can specify a comma-separated list of existing containers. However, you can only specify device container names. A value of none indicates that the container is a top level container.
Example:
container.create "serviceName=San Jose Devices", "serviceType=device",
"memberListMethod=auto", "ruleDeviceName=*sjc*",
"ruleDeviceType=unix*", "parentNames=Critical Servers,HQ"
An administrator can use the departmentName parameter to create a container in a specific department.