Veritas NetBackup™ OpsCenter Administrator's Guide
- Overview of NetBackup OpsCenter
- About OpsCenter
- About OpsCenter components
- About starting the OpsCenter console
- About OpsCenter console components
- About the View pane
- Sizing the Content pane
- About using tables
- Installing OpsCenter
- About planning an OpsCenter installation
- About the OpsCenter licensing model
- Managed NetBackup master server considerations
- About designing your OpsCenter Server
- About planning an OpsCenter Agent deployment
- Installing OpsCenter on Windows and UNIX
- About OpsCenter upgrade on Windows and UNIX
- About post-installation tasks
- About uninstalling OpsCenter on Windows and UNIX
- About clustering OpsCenter
- About planning an OpsCenter installation
- Getting started with OpsCenter
- Administering OpsCenter
- About the services and processes used by OpsCenter
- OpsCenter server scripts on Windows and UNIX
- About OpsCenter database administration
- About backup and restore of OpsCenter and OpsCenter Analytics
- About communication ports and firewall considerations in OpsCenter
- About OpsCenter log files
- Understanding OpsCenter settings
- Setting user preferences
- About managing licenses
- Configuring the data purge period on the OpsCenter Server
- Configuring SMTP server settings for OpsCenter
- Adding host aliases in OpsCenter
- Merging objects (hosts) in OpsCenter
- Modifying tape library information in OpsCenter
- Copying a user profile in OpsCenter
- Setting report export location in OpsCenter
- About managing Object Types in OpsCenter
- About managing OpsCenter users
- About adding AD / LDAP user groups in OpsCenter
- About managing recipients in OpsCenter
- About managing cost analysis and chargeback for OpsCenter Analytics
- Understanding data collection
- About data collection in OpsCenter
- About managing OpsCenter Agents
- About managing OpsCenter Data Collectors
- About configuring data collection for NetBackup
- About the Breakup Jobs option
- Viewing master server details and data collection status
- Collecting data from PureDisk
- Managing OpsCenter views
- About OpsCenter views
- About managing OpsCenter views
- View filters in OpsCenter
- Monitoring NetBackup using OpsCenter
- Controlling the scope of Monitor views
- About monitoring NetBackup using the Overview tab
- About monitoring NetBackup jobs
- Monitor > Services view
- About monitoring Audit Trails
- Managing NetBackup using OpsCenter
- About managing alert policies
- About creating (or changing) an alert policy
- About managing NetBackup storage
- About managing NetBackup devices
- About Operational Restore and Guided Recovery operations
- About Operational Restores from OpsCenter
- About OpsCenter Guided Recovery
- Troubleshooting Guided Recovery
- About managing NetBackup Hosts
- About managing NetBackup Deployment Analysis
- Data compilation for the Capacity License report
- Generating a Capacity Licensing report
- Supporting Replication Director in OpsCenter
- Understanding and configuring OpsCenter alerts
- About using SNMP
- About using SNMP
- Reporting in OpsCenter
- About OpsCenter reports
- Report Templates in OpsCenter
- About managing reports in OpsCenter
- Creating a custom report in OpsCenter
- About managing My Reports
- About managing My Dashboard
- About managing reports folders in OpsCenter
- About managing report schedules in OpsCenter
- About managing time schedules in OpsCenter
- Appendix A. Additional information on PureDisk data collection
- Appendix B. Attributes of NetBackup data
- Appendix C. Man pages for CLIs
- Appendix D. Creating views using CSV, TSV, and XML files
- Appendix E. Error messages in OpsCenter
SNMP traps
This section explains the content of an SNMP trap that is sent from Veritas NetBackup OpsCenter.
Each OpsCenter trap contains 2 standard object identifiers and 12 OpsCenter-specific object identifiers. An object identifier (or OID) is a numeric string that is used to uniquely identify an object.
The following table shows the contents of a trap that is sent from OpsCenter. A total of 14 bindings (or 14 name-value pairs) are present in each trap that is sent from OpsCenter. Each binding associates a particular Management Information Base (MIB) object instance with its current value.
Table: OpsCenter trap binding shows the name-value pairs that the traps pass to the SNMP manager.
Table: OpsCenter trap binding
Name | Value |
---|---|
1.3.6.1.2.1.1.3.0 | This field is the time (in hundredths of a second) between when OpsCenter server service starts and the OpsCenter trap is sent. See Request for Comment (RFC) 1905 and 2576 for a detailed definition. http://www.ietf.org/rfc/rfc1905.txt http://www.ietf.org/rfc/rfc2576.txt Example: 1173792454 |
1.3.6.1.6.3.1.1.4.1.0 | This field is the unique identifier for this trap. See RFC 1905 and RFC 2576 for a detailed definition. http://www.ietf.org/rfc/rfc1905.txt http://www.ietf.org/rfc/rfc2576.txt Example: 1.3.6.1.4.1.1302.3.12.10.2.0.4 |
1.3.6.1.4.1.1302.3.12.10.1.1 (iso.org.dod.internet.private.enterprises.p roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.alertRecipients) | This field is the alert recipient name. Example: Nancy Nieters |
1.3.6.1.4.1.1302.3.12.10.1.2 (iso.org.dod.internet.private.enterprises.p roducts.veritascc.ccTrapDefinitionsBranc h.ccTrapVarsBranch.alertSummary) | This value specifies the alert ID, alert status, and alert summary in the following format: Alert ID (Alert Status) Alert Summary Example: 100 (Active) Job Completed with Exit Status 0 |
1.3.6.1.4.1.1302.3.12.10.1.3 (iso.org.dod.internet.private.enterprises.p roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.alertDescription) | This field is the alert description. Examples for each alert condition are available. |
1.3.6.1.4.1.1302.3.12.10.1.4 (iso.org.dod.internet.private.enterprises.p roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.policyName) | This field is the alert policy name. |
1.3.6.1.4.1.1302.3.12.10.1.5 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.objectType) | This field is blank and not used. |
1.3.6.1.4.1.1302.3.12.10.1.6 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.collectorNam e) | This field is blank and not used. |
1.3.6.1.4.1.1302.3.12.10.1.7 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.ccHost) | This field is the IP address of the OpsCenter server. Example: 10.212.12.148 |
1.3.6.1.4.1.1302.3.12.10.1.8 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.sourceId) | This field is blank and not used. |
1.3.6.1.4.1.1302.3.12.10.1.9 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.ccObject) | This field is blank and not used. |
1.3.6.1.4.1.1302.3.12.10.1.10 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.sampleData) | This field is blank and not used. |
1.3.6.1.4.1.1302.3.12.10.1.11 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.ccAlertSeveri ty) | This field shows the alert severity level. Example: Informational |
1.3.6.1.4.1.1302.3.12.10.1.12 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.ccAlertTime) | This field shows the time when the alert gets cleared. Example: 13-10-2008 06:57:34 00 |
The first two OIDs listed in the table are standard SNMP OIDs. The other OIDs starting from 1.3.6.1.4.1.1302.3.12.10.1.1 to 1.3.6.1.4.1.1302.3.12.10.1.12 are OpsCenter OIDs. As per SNMPv2c trap definition, the two standard SNMP OIDs must be present as part of every trap.
All the 12 OpsCenter OIDs are defined in the OpsCenter MIB files. However, the two standard OIDs are not defined in the OpsCenter MIB files.