snmp-v3-add-trap-recipient
Usage
avcli snmp-v3-add-trap-recipient --recipient recipient --username username --security-level security_level [--authentication-type type] [--authentication-pass-phrase pass_phrase] [--encryption-type type] [--encryption-pass-phrase pass_phrase]
Description
The snmp-v3-add-trap-recipient command adds a recipient server (recipient) and a trap user (username) to the CallHomeInfo.xml file on the everRun system. The everRun system can then send SNMPv3 traps to the trap user, when the user exists on the recipient server.
Options
--recipient recipient | The server that is the recipient of SNMPv3 traps. Specify a domain name or an IPv4 address. |
--username username | The name of the trap user on the recipient server to whom the everRun system sends SNMPv3 traps. |
--security-level security-level |
The user's security level. Valid values are:
|
--authentication-type type |
The user's type of authentication. Valid values are:
|
--authentication-pass-phrase pass_phrase | The user's required pass phrase, which is used to generate the secret authentication key. The pass_phrase must be a minimum of eight characters. |
--encryption-type type |
The user's type of encryption. Valid values are:
|
--encryption-pass-phrase pass_phrase | The user's required pass phrase, which is used to generate the secret encryption key. The pass_phrase must be a minimum of eight characters. |
Examples
The examples below add recipient servers and trap users to the CallHomeInfo.xml file on the everRun system.
The following example adds the recipient server snmp1.my-domain.com and the trap user myTrapUser1. The trap messages that the system sends to myTrapUser1 will be authenticated and encrypted.
$ avcli snmp-v3-add-trap-recipient --recipient snmp1.my-domain.com --username myTrapUser1 --security-level priv --authentication-type MD5 --authentication-pass-phrase trapUser1AuthPassPhrase --encryption-type AES --encryption-pass-phrase trapUser1EncriptPassPhrase
The following example adds the recipient server snmp2.my-domain.com and the trap user myTrapUser2. The trap messages that the system sends to myTrapUser2 will be authenticated, but not encrypted.
$ avcli snmp-v3-add-trap-recipient --recipient snmp2.my-domain.com --username myTrapUser2 --security-level auth --authentication-type MD5 --authentication-pass-phrase trapUser2AuthPassPhrase
The following example adds the recipient server snmp3.my-domain.com and the trap user myTrapUser3. The trap messages that the system sends to myTrapUser3 will not be authenticated or encrypted.
$ avcli snmp-v3-add-trap-recipient --recipient snmp3.my-domain.com --username myTrapUser3 --security-level noauth