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

Restoring the next-startup configuration file from a TFTP server, Displaying and maintaining

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 104 highlights

You can delete the main, the backup, or both. If the main and backup next-startup configuration files are the same file, the system sets the attribute of the configuration file to NULL instead of deleting the file. You can permanently delete the file after its attribute changes to NULL. You may need to delete the next-startup configuration file for one of the following reasons: • After you upgrade system software, the file does not match the new system software. • The file has been corrupted or is not fully compatible with the device. After the file is deleted, the device uses factory defaults at the next startup. Perform the following task in user view: Task Delete the next-startup configuration file. Command reset saved-configuration [ backup | main ] Restoring the next-startup configuration file from a TFTP server To download a configuration file from a TFTP server to the root directory of each member' storage medium, and specify the file as the next-startup configuration file, perform the task in this section. This task restores only the main next-startup configuration file. Before restoring the next-startup configuration file, make sure the server is reachable, the server is enabled with TFTP service, and you have read and write permissions. To restore the next-startup configuration file from a TFTP server: Step Command 1. Restore the main next-startup configuration file from a TFTP server in user view. restore startup-configuration from src-addr src-filename 2. Verify that the specified configuration file has been set as the main next-startup display startup configuration file. Remarks Available in user view. Optional. Displaying and maintaining a configuration file Task Display information about configuration rollback. Command display archive configuration [ | { begin | exclude | include } regular-expression ] Remarks Available in any view. 98

  • 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
98
You can delete the main, the backup, or both. If the main and backup next-startup configuration files are
the same file, the system sets the attribute of the configuration file to NULL instead of deleting the file. You
can permanently delete the file after its attribute changes to NULL.
You may need to delete the next-startup configuration file for one of the following reasons:
•
After you upgrade system software, the file does not match the new system software.
•
The file has been corrupted or is not fully compatible with the device.
After the file is deleted, the device uses factory defaults at the next startup.
Perform the following task in user view:
Task
Command
Delete the next-startup
configuration file.
reset saved-configuration
[
backup
|
main
]
Restoring the next-startup configuration file from a
TFTP server
To download a configuration file from a TFTP server to the root directory of each member' storage
medium, and specify the file as the next-startup configuration file, perform the task in this section.
This task restores only the main next-startup configuration file.
Before restoring the next-startup configuration file, make sure the server is reachable, the server is
enabled with TFTP service, and you have read and write permissions.
To restore the next-startup configuration file from a TFTP server:
Step
Command
Remarks
1.
Restore the main next-startup
configuration file from a TFTP
server in user view.
restore startup-configuration
from
src-addr src-filename
Available in user view.
2.
Verify that the specified
configuration file has been set
as the main next-startup
configuration file.
display startup
Optional.
Displaying and maintaining a configuration file
Task
Command
Remarks
Display information about
configuration rollback.
display archive configuration
[
|
{
begin
|
exclude
|
include
}
regular-expression
]
Available in any view.