User's Manual

Fortress ES-Series CLI Guide: System Options, Maintenance and Licensing
183
Hop 1 00:14:8c:32:41:40 (FD00:0:8895:8895:214:8CFF:FE32:4140 - Car2-MAC-4140-IP-20) 1072ms cost=7407 (MESH2)
Hop 2 00:14:8c:31:be:40 (FD00:0:8895:8895:214:8CFF:FE31:BE40 - Car1-MAC-BE40-IP-10) 4167ms cost=7407 (MESH2)
Hop 3 00:10:60:17:53:bc (*) 4168ms cost=0 (Ethernet2)
Total cost = 14814Total cost = 3400
NOTE: The Mesh
Path trace tool is
intended for use only
when FastPath Mesh is
enabled on the Mesh
Point.
The results are similar to traceroute, except that traceroute
uses OSI Layer 3, and meshpath uses OSI Layer 2. The
meshpath results display the total end-to-end cost to reach a
particular node in a FastPath Mesh network, along with each
hop and its associated cost.
You must be logged on to an
administrator -level or a
maintenance-level account to execute meshpath (refer to
Section 2.2).
5.10 Copying Running Configurations
CAUTION: You
must only use
copy running-config to
copy configurations to a
Mesh Point of the same
model from which the
configuration file was
created.
Once a Mesh Point has been configured, you can use that
Mesh Point’s configuration to set up other Mesh Points in the
network using
copy running-config .
This command creates a text file that contains all of the
configuration information for the current Mesh Point, and
copies it to the specified SCP (Secure Copy) server using
SSH2 (Secure Shell 2) for in-transit encryption and
authentication. You can then
use this file to configure additional
network Mesh Points.
Sensitive information in the configuration file is protected by
use of an encryption key. Generate a configuration file with
copy running-config:
# copy running-config -from
<local> -to <remote-url> -encKey <keyText> -host <hostname>
-user
<username> -password <password> -excludenetworkconf
The -from <local> parameter indicates that the configuration
file will be created from the currently running local
configuration. The file is generated on the local Mesh Point,
and also transferred to the location specified by the
-to
<remote-url> parameter. The remote URL can be either a fully
qualified domain name (FQDN), or an IP address.
You must specify an encryption key (
-encKey), a text string of
8–32 characters used to encrypt the sensitive information in
the file.
Enter the hostname (
-host) of the target node (the Mesh Point
where the file will be copied), and the username (
-user) and
-password required by the SCP server.
If you include the
-excludenetworkconf switch, basic network
parameters (hostname, IP addresses, etc.) will be omitted from
the configuration file, allowing the file to be installed on a