collect counters
303
Media Flow Controller Administrator’s Guide
Media Flow Controller CLI Commands
Notes:
•
client
—Configure CMC client rendezvous options.
•
auth
—Specify the authentication method to use to log into the server to rendezvous.
•
authtype
—Configure the type of authentication to use. The no variant resets the
authtype to its default, which is none.
−
password
(default)—Use the configured cmc client server auth password.
−
ssh-dsa2
or
ssh-rsa2 identity
and
username
—Select to use the cmc
client server auth ssh-dsa2 or ssh-rsa2 settings. The rendezvous client
username is cmcrendv (cannot be changed), and the identities for DSA2 and
RSA2 auth are configured on that user account.
•
password password [<password>]
—If no password is given, the user is
prompted for the password. Entries made at this prompt echo the asterisk (*)
character, and the user must enter the same string twice.
•
auto
—Enable or disable (default) automatic rendezvous attempts from a CMC client;
optionally, configure the wait, in seconds between automatic rendezvous attempts.
•
initial-delay
— Wait this long (default is 30 seconds) before initial attempt.
•
interval-long
—Wait this long (default is 86400 seconds) after successful
announcement but no connection (for example, the server lost our information).
•
interval-short
—Wait this long (default is 300) after unsuccessful announcement.
•
force
—Force a CMC client to attempt discovery and rendezvous with a server now,
regardless of whether automatic rendezvous is enabled, or how long it has been since
the last attempt. If being a CMC client is disabled, this produces an error and no action
is taken. If this attempt fails, the client does not automatically retry.
•
server-addr
—Set or clear the address (hostname or IP address) of the server with
which the client attempts rendezvous. Default is cmc.
•
service-name
—Set or clear the service name which is used for CMC rendezvous.
show cmc rendezvous
List all current configuration and state of CMC rendezvous, whether the system is a server or
a client. On a server, this includes listing the clients that have attempted rendezvous but not
yet been accepted. On a client, this involves showing our rendezvous status, and whether or
not we are currently under management.
collect counters
This command is for debugging use and requires the assistance of Customer Support.
collect counters detail <name> frequency <seconds> duration <seconds>
The collect counters detail <name> value will be supplied by Customer Support to help
pinpoint an issue, see
“Requesting Technical Support” on page 34
. The allowable names are
available only through Customer Support except the all counter detail name, which is - (dash).
The frequency value determines how often the collection is run and the duration value
determines how long the collection is run.
The collect counter command creates a file, counters-<mfd-name>-<date-time>.txt, in the
directory /var/opt/tms/sysdumps.
Example:
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...
