HP 6125G HP 6125G & 6125G/XG Blade Switches Fundamentals Configuration - Page 102

Manually archiving running configuration, Performing configuration rollback, result in a valid

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 102 highlights

Manually archiving running configuration To save system resources, disable automatic configuration archiving and manually archive configuration if the configuration will not be changed very often. You can also manually archive configuration before performing complicated configuration tasks so you can use the archive for configuration recovery after the configuration attempt fails. Make sure you have set an archive path and file name prefix before performing this task. Perform the following task in user view: Task Manually archive the running configuration. Command archive configuration Performing configuration rollback To avoid rollback failure, follow these guidelines: • Do not reboot member devices while the system is executing the configuration replace file command. • Make sure the replacement configuration file is created by using the configuration archive function or the save command on the current device. • If the configuration file is not created on the current device, make sure the configuration file content format is fully compatible with the current device. • The replacement configuration file is not encrypted. To perform a configuration rollback: Step 1. Enter system view. 2. Perform configuration rollback. Command system-view configuration replace file filename The configuration rollback function might fail to reconfigure some commands in the running configuration for one of the following reasons: • A command cannot be undone, because prefixing the undo keyword to the command does not result in a valid undo command. For example, if the undo form designed for the A [B] C command is undo A C, the configuration rollback function cannot undo the A B C command, because the system does not recognize the undo A B C command. • A command (for example, a hardware-dependent command) cannot be deleted, overwritten, or undone due to system restrictions. • The commands in different views are dependent on each other. • Commands or command settings that the device does not support cannot be added to the running configuration. 96

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
96
Manually archiving running configuration
To save system resources, disable automatic configuration archiving and manually archive configuration
if the configuration will not be changed very often. You can also manually archive configuration before
performing complicated configuration tasks so you can use the archive for configuration recovery after
the configuration attempt fails.
Make sure you have set an archive path and file name prefix before performing this task.
Perform the following task in user view:
Task
Command
Manually archive the running configuration.
archive configuration
Performing configuration rollback
To avoid rollback failure, follow these guidelines:
•
Do not reboot member devices while the system is executing the
configuration replace file
command.
•
Make sure the replacement configuration file is created by using the configuration archive function
or the
save
command on the current device.
•
If the configuration file is not created on the current device, make sure the configuration file content
format is fully compatible with the current device.
•
The replacement configuration file is not encrypted.
To perform a configuration rollback:
Step
Command
1.
Enter system view.
system-view
2.
Perform configuration rollback.
configuration replace file
filename
The configuration rollback function might fail to reconfigure some commands in the running configuration
for one of the following reasons:
•
A command cannot be undone, because prefixing the
undo
keyword to the command does not
result in a valid
undo
command. For example, if the
undo
form designed for the
A
[
B
]
C
command
is
undo A C
, the configuration rollback function cannot undo the
A
B
C
command, because the
system does not recognize the
undo A B C
command.
•
A command (for example, a hardware-dependent command) cannot be deleted, overwritten, or
undone due to system restrictions.
•
The commands in different views are dependent on each other.
•
Commands or command settings that the device does not support cannot be added to the running
configuration.