Configures a host system to receive bulkstats information through
Trivial File Transfer Protocol (TFTP), File Transfer Protocol (FTP) or SSH File
Transfer Protocol (SFTP).
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Bulk Statistics Configuration
configure > bulkstats mode
Entering the above command sequence results in the following prompt:
[local]host_name(config-bulkstats)#
Syntax
receiver { mode { redundant | secondary-on-failure } | ip_address { primary | secondary } [ mechanism { { ftp login user_name [ encrypted ] password pwd } | sftp login user_name user_name { public-key | [ encrypted ] password pwd } | tftp } } ] }
no receiver ip_address
no
Removes the receiver specified from the list of receivers where data
files are sent.
mode { redundant | secondary-on-failure
}
Determines how bulkstats are delivered to the primary and secondary
receivers.
Default:
secondary-on-failure
redundant : Files are transferred to both the
primary and secondary receivers. If either transfer is not currently possible,
the file is transferred when possible. The system continues to hold in memory
as much data as possible until the data has been successfully transferred to
both receivers. Data is only discarded if the in-memory data reaches the
configured limit. Refer to the
limit command.
secondary-on-failure : Files are transferred
to the secondary receiver if the primary receiver fails. In-memory data is
erased once the data is transferred to either the primary or secondary
receiver. This is the default behavior.
ip_address
Specifies the IP address of the receiver of interest using IPv4
dotted-decimal notation.
primary | secondary
Primary and secondary are used to indicate the order in which
receivers are connected. The secondary is used when the primary is unreachable.
primary : indicates the receiver is the
primary receiver of data.
secondary : indicates the receiver is the
secondary receiver of data.
mechanism { { { ftp login user_name [ encrypted ] password pwd } | sftp login user_name user_name { public-key | [ encrypted ] password pwd } | tftp }
Specifies the method by which data is transferred to the receiver.
ftp login
user_name
[ encrypted ]
password
pwd : the FTP protocol shall
be used for data file transfer.
user_name specifies the user to provide for
remote system secure logins and must be an alphanumeric string of 1 through 31
characters. The password to use for remote system authentication is specified
as
pwd and must be from 1 to 31 characters or 1
to 64 characters if the
encrypted keyword is also specified.
sftp login user_name user_name { public-key | [ encrypted ] password pwd } : the SFTP protocol shall be used for data file transfer. user_name specifies the user to provide for remote system secure logins and must be an alphanumeric string of 1 through 31 characters.
The password to use for remote system authentication is specified as pwd and must be from 1 to 31 characters or 1 to 64 characters if the encrypted keyword is also specified. public-key specifies the public key used for SFTP public key authentication for bulkstats transfer.
tftp : the TFTP protocol is to be used to
transfer files.
The
encrypted keyword is intended only for use by
the system while saving configuration scripts. The system displays the
encrypted keyword in the configuration file
as a flag that the variable following the
password keyword is the encrypted version of
the plain text password. Only the encrypted password is saved as part of the
configuration file.
Usage Guidelines
Use TFTP methods to reduce transfer times if excessive system
resources are being used across the network for transfer of data.
FTP transfer method allows for login which then provides system
logging within the enabled FTP logs.
The initial connection is attempted to the primary receiver. If the
primary receiver is unreachable for any reason, the secondary receiver is used.
If the secondary receiver is also unreachable, the system retries after a delay
period where it again attempts to connect to the primary receiver followed by
the secondary receiver as necessary.
Important
|
For redundant receivers, configuration changes to the receivers are
applied to all existing and all subsequent data sets pending transfer. If no
receiver is configured, bulk statistics will be collected and stored on the
system until the maximum amount of memory is used; they will not be transferred
to the receiver(s). When the storage limit has been reached the oldest
information is overwritten. When a receiver is configured for the primary and
secondary target, this command will use both receivers as default if no
receiver is specified.
|
Example
receiver 10.2.3.4 primary mechanism tftp
receiver 10.2.3.5 secondary
no receiver 10.2.3.4
Feedback