HPE D6020 Maintenance And Service Manual page 206

Hide thumbs Also See for HPE D6020:
Table of Contents

Advertisement

This command downloads the configuration file to the root directory of the default storage medium on
each member device and specifies the file as the main next-startup configuration file. If the default
storage medium has been partitioned, the configuration file is saved on the first partition.
Make sure all IRF members use the same type of default storage medium. If a subordinate device
uses a different type of default storage medium than the master device, the command cannot
propagate the configuration file to the subordinate device. For example, the subordinate device uses
a CF card, but the master device uses a flash memory. In this situation, you must manually restore
the main next-startup configuration file on the subordinate device.
Distributed devices in standalone or IRF mode:
This command downloads the configuration file to the root directory of the default storage medium on
each MPU and specifies the file as the main next-startup configuration file. If the default storage
medium has been partitioned, the configuration file is saved on the first partition.
Make sure all MPUs use the same type of default storage medium. If a standby MPU uses a different
type of default storage medium than the active MPU, the command cannot propagate the
configuration file to the standby MPU. For example, the standby MPU uses a CF card, but the active
MPU uses a flash memory. In this situation, you must manually restore the main next-startup
configuration file on the standby MPU.
Examples
# (Centralized devices in standalone mode.) Download the configuration file test.cfg from the IPv4
TFTP server at 2.2.2.2 in the public network, and specify the file as the main next-startup
configuration file.
<Sysname> restore startup-configuration from 2.2.2.2 test.cfg
Restoring the next startup-configuration file from 2.2.2.2...
Done.
# (Centralized devices in standalone mode.) Download the configuration file test.cfg from the IPv4
TFTP server at 2.2.2.2 in the MPLS L3VPN instance VPN1, and specify the file as the main
next-startup configuration file.
<Sysname> restore startup-configuration from 2.2.2.2 test.cfg vpn-instance VPN1
Restoring the next startup-configuration file from 2.2.2.2 in VPN VPN1...
Done.
# (Centralized devices in standalone mode.) Download the configuration file test.cfg from the IPv6
TFTP server at 2001::2 in the public network, and specify the file as the main next-startup
configuration file.
<Sysname> restore startup-configuration from ipv6 2001::2 test.cfg
Restoring the next startup-configuration file from 2001::2...
Done.
# (Distributed devices in standalone mode.) Download the configuration file config.cfg from the IPv4
TFTP server at 2.2.2.2 in the public network, and specify the file as the main next-startup
configuration file.
<Sysname> restore startup-configuration from 2.2.2.2 config.cfg
Restoring the next startup-configuration file from 2.2.2.2...
Done.
# (Distributed devices in standalone mode.) Download the configuration file test.cfg from the IPv4
TFTP server at 2.2.2.2 in the MPLS L3VPN instance VPN1, and specify the file as the main
next-startup configuration file.
<Sysname> restore startup-configuration from 2.2.2.2 test.cfg vpn-instance VPN1
Restoring the next startup-configuration file from 2.2.2.2. in VPN VPN1...
Done.
198

Advertisement

Table of Contents
loading

Table of Contents