Skip to main content
Start a Conversation

Solved!

Go to Solution

NoOneOfConsequence

1 Rookie

 • 

28 Posts

2769

April 25th, 2021 08:00

Meaning of primary/secondary/default boot images? [S3048-ON OS9]

I'm a software (Linux, virt, etc.) guy, not a networking guy. For my sins, I also manage my team's small lab, which uses a stack of Dell S3048-ON switches running FTOS 9. We'll be expanding the stack from 2 to 4 switches in a couple of weeks, and I'm taking the opportunity presented by having the new switches sitting around to research the details of how these things work and write some internal documentation.

Right now I'm working on the OS9 upgrade process. I've reached the point that I've got the updated OS written to the B: partition of both switches.

Dell#show boot system stack-unit all

Current system image information in the system:
===============================================

Type          Boot Type       A                                  B
----------------------------------------------------------------------------------------------
stack-unit 1  FLASH BOOT      9.10(0.1P8)[boot]                  9.14(2.9)
stack-unit 2  FLASH BOOT      9.10(0.1P8)[boot]                  9.14(2.9)
stack-unit 3 is not present.
stack-unit 4 is not present.
stack-unit 5 is not present.
stack-unit 6 is not present.

I'm pretty sure that the next step is to use the boot system command to set both switches to boot from their B: partition, i.e.:

boot system stack-unit {1|2} {default|primary|secondary} system://B

I've been unable to figure out the meaning of default/primary/secondary in this context. Having a default would make sense; having a primary and a secondary would make sense. The combination, however, doesn't seem to make any sense at all, and I've not been able to find anything that explains what these terms really mean.

Anyone know?

DELL-Erman O

Moderator

 • 

2.8K Posts

April 26th, 2021 06:00

Hi, system first attempts to load the image from the primary path. If boot fails, system will attempt to load the image from the secondary path (such as redundant), and finally, if that fails too, the system will load the default image. Unfortunately, I couldn't find a more descriptive document to share with you.

 

Hope this will helps!

DELL-Joey C

Moderator

 • 

3.9K Posts

April 25th, 2021 23:00

Hi,

 

That's great to know a person who is in Linux, probably on another time we may need you help on other Linux enquiries for opinions. 

 

I'm not a network person too, but I'll try to help.

 

I came across the S3048_ON RN: https://dell.to/3aWFFqT that might help you out on completing the update, page 14 and 15. 

 

In your case, that would be #(conf)boot system stack-unit 1 primary system: b:. Then follow the rest of the steps till rebooting the switching. 

 

Also don't forget to check page 6, you may need to update BIOS, GRUB and CPLD if, the versions displayed are not matched. 

NoOneOfConsequence

1 Rookie

 • 

28 Posts

April 26th, 2021 06:00

Yes, I've seen the release notes, and I've determined through experimentation that the primary boot image is what I need to set.  That doesn't answer the question though.

Primary/secondary vs. default(/non-default).  To me they're two different ways of saying the same thing, or they're completely unrelated.

The meaning of having a primary, secondary, and default boot images isn't apparent to me, and it isn't explained anywhere (AFAICT).

NoOneOfConsequence

1 Rookie

 • 

28 Posts

April 26th, 2021 07:00

@Dell-ErmanO wrote:

Hi, system first attempts to load the image from the primary path. If boot fails, system will attempt to load the image from the secondary path (such as redundant), and finally, if that fails too, the system will load the default image. Unfortunately, I couldn't find a more descriptive document to share with you.

 

Hope this will helps!

That is the information that I was looking for.  Is it actually in the documentation anywhere?

Frankly, it sounds like the "default" image should be called "tertiary" or maybe "failsafe."

jessieobioma

1 Rookie

 • 

49 Posts

August 4th, 2021 23:00

Hello,
I am new to DELL switches and I have an S3048 in my environment.
Apologies if this is not the right thread for my questions.
Questions;

1. Is it possible to backup the OS image on my Dell EMC S3048-ON switch. If yes, which directory houses the image and what is the procedure?
2. Is it possible to have two different version of the OS installed in the same switch? 
3．Is there a vlan.dat file as is in cisco switches? if yes, which directory houses this file?

Thank you.

DELL-Erman O

Moderator

 • 

2.8K Posts

August 5th, 2021 04:00

Hello,

Welcome to the community. As I know there is no taking backup whole OS on S-series. But you can take to save running configurations as below;

refer the link https://www.dell.com/support/manuals/en-us/dell-emc-os-9/s3048-on-9.14.2.6-config-pub/save-the-running-configuration?guid=guid-30740b60-fdc7-4980-b20e-06e195bbaf13&lang=en-us 

Save the Running-Configuration

The running-configuration contains the current system configuration. Dell EMC Networking recommends coping your running-configuration to the startup-configuration.

The commands in this section follow the same format as those commands in the  Copy Files to and from the System section but use the filenames startup-configuration and running-configuration. These commands assume that current directory is the internal flash, which is the system default.
  • Save the running-configuration to the startup-configuration on the internal flash of the primary RPM.
    EXEC Privilege mode
    copy running-config startup-config
  • Save the running-configuration to an FTP server.
    EXEC Privilege mode
    copy running-config ftp: // username:password@{hostip | hostname}/filepath/ filename
  • Save the running-configuration to a TFTP server.
    EXEC Privilege mode
    copy running-config tftp: //{hostip | hostname}/ filepath/filename
  • Save the running-configuration to an SCP server.
    EXEC Privilege mode
    copy running-config scp: //{hostip | hostname}/ filepath/filename
    NOTE When copying to a server, a host name can only be used if a DNS server is configured.
NOTE When you load the startup configuration or a configuration file from a network server such as TFTP to the running configuration, the configuration is added to the running configuration. This does not replace the existing running configuration. Commands in the configuration file has precedence over commands in the running configuration.
 
If you want, you can enable OS verification.

Dell EMC Networking OS Image Verification

Dell EMC Networking OS comes with the OS image verification and the startup configuration verification features. When enabled, these features check the integrity of The OS image and the startup configuration that the system uses while the system reboots and loads only if they are intact.

Important Points to Remember

  • The OS image verification feature is disabled by default on the Dell EMC Networking OS.
  • The OS image verification feature is supported for images stored in the local system only.
  • The OS image verification feature is not supported when the fastboot or the warmboot features are enabled on the system.
  • If OS image verification fails after a reload, the system does not load the startup configuration. The System displays an appropriate error message until the no verified boot command is used on the system.
  • After you enable The OS image verification feature, the system prompts you to enter The OS image hash when you upgrade the Dell EMC Networking OS to a later version. The system checks if your hash matches with The OS image hash only after reloading.
  • After enabling The OS image verification feature, use the verified boot hash command to verify and store the hash value. If you don’t store the hash value, you cannot reboot the device until you verify The OS image hash.
 
 
I have not come across a switch that can run two OSes at the same time. I did some research and digging when you write, but I couldn't find a similar example in the sources I've reviewed. Regarding this and I think the vlan.dat file is stored in NVRAM, but I couldn't find a command about how to access the file directory. Maybe with the "vtp file" command like in cisco, I searched for this command because the name of the existing VLAN database can be changed, but I couldn't find it.
 
Hope this will help! 
 

Was this post helpful?

View All

No Events found!

Top