Dell PowerConnect 2748 User's Guide - Page 54

Managing System Files, Startup Configuration File, Image files

Page 54 highlights

Managing System Files Use the File Management section to manage switch software, the image file, and the configuration files. Files can be downloaded or uploaded via a TFTP server. This applies to the PowerConnect 2748 switch configuration only. The configuration file structure consists of the following configuration files: • Startup Configuration File - Contains the commands required to reconfigure the device to the same settings as when the device is powered down or rebooted. The Startup file is created by copying the configuration commands from the Running Configuration file or the Backup Configuration file. • Running Configuration File - Contains all Startup file commands, as well as all commands entered during the current session. After the device is powered down or rebooted, all commands stored in the Running Configuration file are lost. During the startup process, all commands in the Startup file are copied to the Running Configuration File and applied to the device. During the session, all new commands entered are added to the commands existing in the Running Configuration file. Commands are not overwritten. To update the Startup file, before powering down the device, the Running Configuration file must be copied to the Startup Configuration file. The next time the device is restarted, the commands are copied back into the Running Configuration file from the Startup Configuration file. • Image files - System file images are saved in two Flash Files called images (Image 1 and Image 2). The active image stores the active copy, while the other image stores a second copy. The device boots and runs from the active image. If the active image is corrupted, the system automatically boots from the non-active image. This is a safety feature for faults occurring during the Software Upgrade process. 54

  • 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

54
Managing System Files
Use the File Management section to manage switch software, the image file, and the configuration
files. Files can be downloaded or uploaded via a TFTP server.
This applies to the PowerConnect
2748 switch configuration only.
The configuration file structure consists of the following configuration files:
Startup Configuration File
— Contains the commands required to reconfigure the device to
the same settings as when the device is powered down or rebooted. The Startup file is created
by copying the configuration commands from the Running Configuration file or the Backup
Configuration file.
Running Configuration File
— Contains all Startup file commands, as well as all commands
entered during the current session. After the device is powered down or rebooted, all
commands stored in the Running Configuration file are lost. During the startup process, all
commands in the Startup file are copied to the Running Configuration File and applied to
the device. During the session, all new commands entered are added to the commands
existing in the Running Configuration file. Commands are not overwritten. To update the
Startup file, before powering down the device, the Running Configuration file must be copied
to the Startup Configuration file. The next time the device is restarted, the commands are
copied back into the Running Configuration file from the Startup Configuration file.
Image files
— System file images are saved in two Flash Files called images (Image 1 and
Image 2). The active image
stores the active copy, while the other image stores a second copy.
The device boots and runs from the active
image. If the active image is corrupted, the system
automatically boots from the non-active image. This is a safety feature for faults occurring
during the Software Upgrade process.