Reference Guide

348 | Force10 Service Agent
www.dell.com | support.dell.com
Encrypt FTSA Messages
Encrypting FTSA message to a recipient other than the default is supported only on platforms: c e
Per-recipient, you have a choice of sending FTSA E-mails in clear text or with PGP5 encryption. Messages
to the default recipient are configured for encryption using a public encryption key, as shown in the
example in Add Additional Recipients of FTSA E-mails.
Create a PGP5 encryption key
Provide Administrator Contact Information
Dell Force10 recommends that you provide administrator contact information so that it can be included in
Type 3 or greater E-mails.
Step Task Command Command Mode
1 Copy the encryption key file to the internal
flash. The key Force10DefaultPublicKey for
the default recipient is packed with FTOS, so
enable encryption for it, proceed to Step 3.
copy source-path/file
flash://keyfilename
EXEC Privilege
2 Specify the key with which E-mails to the
recipient will be encrypted.
keyadd keyfilename CALLHOME<SERVER-LABEL>
3 Encrypt E-mails to the recipient. encrypt CALLHOME<SERVER-LABEL>
Step Task
1 Use a PGP5-compatible program such as PGP or GnuPG to generate the public or private key. The user name that
you choose in the program will be the one that you use in the server command.
2 Export the public key to a file.
Task Command Command Mode
Provide the postal service mailing address at which the network administrator
can be contacted.
contact-address CALLHOME
Provide the E-mail address at which the network administrator can be
contacted.
contact-email CALLHOME
Provide the name of the network administrator to be contacted upon an FTSA
trigger event.
contact-name CALLHOME
Include a memo in FTSA messages.
contact-notes CALLHOME
Provide the phone number of the network administrator to be contacted upon
an FTSA trigger event.
contact-phone CALLHOME
Note: The contact fields may contain any character, however, be aware that FTSA generates all messages are XML format,
for example <contact-name> </contact-name>, so non-alphanumeric characters might create XML errors.