# US 11,113,072 B2 · Boot personality for network device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,113,072 B2 - Document ID: US11113072B2 - Status: Granted - Kind: B2 - Application number: 16/530,882 - Filed: 2019-08-02 - Published: 2021-02-04 - Granted: 2021-09-07 - Earliest claimed: 2019-08-02 - Assignees: Arista Networks, Inc. - Applicants: Arista Networks, Inc. - Inventors: Fakherdin Kalla; Gil Adrian Torres - Web page: https://patentgrep.com/patent/US11113072B2 ## CPC - G06F 9/4416: {Network booting; Remote initial program loading [RIPL]} - G06F 8/61: Installation - G06F 9/4405: {Initialisation of multiprocessor systems} - G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Embodiments described herein may relate to methods, systems, and/or instructions stored on non-transitory computer readable mediums for managing a boot personality of a network device. Managing a boot personality may include, while executing a first operating system on a network device in a first boot personality using a first processor, executing a command to modify a configuration of a hardware component of the network device to cause the network device to be configured in a second boot personality. The method may also include rebooting the network device; initializing, based on the configuration of the hardware component, a second processor before the first processor; and executing, after the initialization, a second operating system while the network device is in the second boot personality. ## Claims ### Claim 1 A method for managing a boot personality, the method comprising: while executing a first operating system on a network device in a first boot personality using a first processor, executing a first command to modify a configuration of a hardware component of the network device to cause the network device to be configured in a second boot personality; performing a first reboot of the network device after executing the first command; initializing, based on the configuration of the hardware component and during the first reboot, a second processor before the first processor; and executing, after the initialization, a second operating system while the network device is in the second boot personality; while executing the second operating system in the second boot personality, executing a second command to modify the configuration of the hardware component of the network device to cause the network device to be configured in the first boot personality; performing a second reboot of the network device after executing the second command; initializing, based on the configuration of the hardware component and during the second reboot, the first processor; and executing, after the initialization, the first operating system on the first processor while the network device is in the first boot personality. ### Claim 2 (depends on 1) The method of claim 1, wherein, before executing the command, the first operating system performs a health check on the second processor. ### Claim 3 (depends on 1) The method of claim 1, further comprising: installing, before the first reboot a new firmware on the second processor. ### Claim 4 (depends on 3) The method of claim 3, further comprising: performing a health check on the second processor after installing the new firmware and before the first reboot. ### Claim 5 (depends on 1) The method of claim 1, further comprising: verifying, after executing the first command, that the network device is configured for the second boot personality before the first reboot. ### Claim 6 (depends on 1) The method of claim 1, further comprising: configuring, after initializing the second processor, a bootloader to obtain the second operating system and store the second operating system on the network device. ### Claim 7 (depends on 6) The method of claim 6, wherein the second operating system is obtained by the bootloader via a network. ### Claim 8 (depends on 6) The method of claim 6, wherein the second operating system is obtained by the bootloader from a storage location on the network device. ### Claim 9 (depends on 1) The method of claim 1, wherein initializing the second processor comprises: configuring a plurality of network device components to be operatively connected to the second processor instead of the first processor. ### Claim 10 A non-transitory computer readable medium comprising instructions that, when executed by a processor, perform a method for managing a boot personality, the method comprising: while executing a first operating system on a network device in a first boot personality using a first processor, executing a first command to modify a configuration of a hardware component of the network device to cause the network device to be configured in a second boot personality; performing a first reboot of the network device after executing the first command; initializing, based on the configuration of the hardware component and during the first reboot, a second processor before the first processor; and executing, after the initialization, a second operating system while the network device is in the second boot personality; while executing the second operating system in the second boot personality, executing a second command to modify the configuration of the hardware component of the network device to cause the network device to be configured in the first boot personality; performing a second reboot of the network device after executing the second command; initializing, based on the configuration of the hardware component and during the second reboot, the first processor; and executing, after the initialization, the first operating system on the first processor while the network device is in the first boot personality. ### Claim 11 (depends on 10) The non-transitory computer readable medium of claim 10, wherein, before executing the command, the first operating system performs a health check on the second processor. ### Claim 12 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the method performed by executing the instructions further comprises: installing, before the first reboot a new firmware on the second processor. ### Claim 13 (depends on 12) The non-transitory computer readable medium of claim 12, wherein the method performed by executing the instructions further comprises: performing a health check on the second processor after installing the new firmware and before the first reboot. ### Claim 14 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the method performed by executing the instructions further comprises: verifying, after executing the first command, that the network device is configured for the second boot personality before the first reboot. ### Claim 15 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the method performed by executing the instructions further comprises: configuring, after initializing the second processor, a bootloader to obtain the second operating system and store the second operating system on the network device. ### Claim 16 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the second operating system is obtained by the bootloader via a network. ### Claim 17 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the second operating system is obtained by the bootloader from a storage location on the network device. ### Claim 18 (depends on 10) The non-transitory computer readable medium of claim 10, wherein initializing the second processor comprises: configuring a plurality of network device components to be operatively connected to the second processor instead of the first processor.