Patent Description:
<CIT> provides methods for zero loss and nonstop packet processing during system software upgrades.

Some implementations described herein relate to a network device.

Some implementations described herein relate to a computer-readable medium that comprises a set of instructions for a network device.

Some implementations described herein relate to a method.

A network device includes configuration functionalities (e.g., features, processes, applications, or services, among other examples) that the network device utilizes to facilitate routing of traffic through the network. When the network device is to be upgraded, the network device may perform an in-service software upgrade (ISSU) procedure to update the network device (e.g., without taking the network device offline). However, in some cases, some of the configuration functionalities are not compatible with performance of the ISSU procedure. Accordingly, performance of the ISSU procedure may detrimentally impact an operational performance of these configuration functionalities. For example, performance of the ISSU procedure may cause a configuration functionality to misbehave (e.g., cause unexpected errors) or to stop executing. This results in using computing resources (e.g., processing resources, memory resources, communication resources, and/or power resources, among other examples) of the network device and/or one or more other devices to attempt to fix the configuration functionality and/or to address any issues (e.g., misrouting issues, blackholing issues, or other issues) associated with the impacted operational performance of the configuration functionality.

In some cases, an administrator of the network device may run customized scripts to deactivate incompatible configuration functionalities prior to performance of the ISSU procedure on the network device and may run other customized scripts to activate the incompatible configuration functionalities after performance of the ISSU procedure. However, in many cases, such as due to continually changing configurations of the network device, the scripts do not deactivate and/or activate all of the incompatible configuration functionalities, which results in similar performance issues to those described above for the incompatible configuration functionalities not addressed by the scripts. In other cases, the scripts needlessly deactivate and/or activate configuration functionalities that are compatible with the ISSU procedure, which results in unnecessary operational performance issues of these configuration functionalities (e.g., due to the configuration functionalities not being active during performance of the ISSU procedure).

Some implementations described herein provide a network device that includes a first configuration data structure. The network device obtains a data package associated with an ISSU procedure (e.g., that the network device is to execute to cause performance of the ISSU procedure to update the network device). The data package includes a second configuration data structure. In some implementations, the first configuration data structure and the second configuration data structure identify one or more configuration functionalities of the network device that are incompatible with performance of the ISSU procedure, and the network device processes (e.g., parses) the first configuration data structure and the second data structure to identify the one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure. Accordingly, the network device causes the one or more configuration functionalities of the network device to be deactivated, and thereby causes the ISSU procedure to be performed (e.g., based on the data package). After causing the ISSU procedure to be performed, the network device causes the one or more configuration functionalities to be activated.

In this way, the network device automatically deactivates and activates the one or more configuration functionalities of the network device that are incompatible with performance of the ISSU procedure. The network device therefore causes the ISSU procedure to be performed when the one or more configuration functionalities are deactivated and causes the one or more configuration functionalities to be activated after the ISSU procedure has been performed. This enables the network device to be updated (e.g., based on performance of the ISSU procedure) without detrimentally impacting a performance of the one or more configuration functionalities of the network device (e.g., because the one or more configuration functionalities were not active during performance of the ISSU procedure). Accordingly, a likelihood that the one or more configuration functionalities misbehave (e.g. cause unexpected errors) or stop executing is reduced, which minimizes a use of computing resources (e.g., processing resources, memory resources, communication resources, and/or power resources, among other examples) of the network device and/or one or more other devices to attempt to fix the one or more configuration functionalities and/or to address any issues (e.g., misrouting issues, blackholing issues, or other issues) associated with an impacted performance of the one or more configuration functionalities. Further, some implementations eliminate a need for an administrator to generate and run customized scripts associated with performance of the ISSU procedure, which further reduces a likelihood of performance issues resulting from incompatible configuration functionalities not being correctly deactivated and activated for performance of the ISSU procedure and/or compatible configuration functionalities being unnecessarily deactivated and/or activated for performance of the ISSU procedure.

<FIG> are diagrams of one or more example implementations <NUM> described herein. Example implementation(s) <NUM> may include a network device, a client device, and/or a server device, which are described in more detail below in connection with <FIG>. The one or more network devices and/or the monitoring device may be configured to communicate with each other via a network.

The network device may include a plurality of configuration functionalities (e.g., a plurality of features, processes, applications, or services, among other examples) that the network device provides to facilitate routing of traffic through the network. In some implementations, one or more configuration functionalities, of the plurality of configuration functionalities, are incompatible with performance of an ISSU procedure (e.g., by the network device). For example, performing the ISSU procedure while the one or more configuration functionalities are active on the network device may detrimentally impact a performance of the one or more configuration functionalities during performance of the ISSU procedure and/or after performance of the ISSU procedure. Some implementations described herein enable the network device to automatically deactivate and/or activate the one or more configuration functionalities as part of performance of an ISSU procedure.

As shown in <FIG>, and by reference number <NUM>, the network device may receive a command, such as from the client device. For example, a user of the client device may interact with a user interface provided by the network device (e.g., a command line interface (CLI), a graphical user interface (GUI), or another interface) to enter the command, and the client device may send the command to the network device. The command may indicate that the network device is to be updated via performance of an ISSU procedure. For example, the command may include an instruction to communicate with the server device to obtain a data package that is associated with the ISSU procedure (e.g., a software installation package that includes an updated network device image and/or other upgrade information associated with the ISSU procedure) and to cause the ISSU procedure to be performed (e.g., based on the data package). The command may indicate that the network device has permission to deactivate and/or activate configuration functionalities of the network device (e.g., to facilitate performance of the ISSU procedure). For example, the command may include an indication (e.g., a command line option, such as indicated by a string prefixed by a dash ("-") when the command is entered via the CLI) that the network device has permission to deactivate and/or activate configuration functionalities of the network device to facilitate performance of the ISSU procedure.

As shown by reference number <NUM>, the network device may obtain the data package from the server device (e.g., based on the command received from the client device). For example, the network device may send (e.g., based on the command) a request (e.g., for the data package that is associated with the ISSU procedure) to the server device, and the server device may send (e.g., based on the request) the data package to the network device. Accordingly, the network device may receive the data package and may therefore perform one or more additional steps related to performance of the ISSU procedure, as described herein.

As shown in <FIG>, the network device may identify one or more configuration data structures (e.g., databases, electronic files, or other data structures) associated with the network device. For example, as shown by reference number <NUM>, the network device may identify a first configuration data structure included in the network device (e.g., that is stored and/or maintained by the network device). As another example, as shown by reference number <NUM>, the network device may identify a second configuration data structure included in the data package. The network device may process (e.g., parse) the data package to identify the second configuration data structure. At least one of the first configuration data structure or the second configuration data structure may indicate, for a particular configuration functionality, of the one or more configuration functionalities of the network device, that the particular configuration functionality is to not be active during performance of the ISSU procedure. For example, the first configuration data structure may indicate one or more configuration functionalities of the network device that are to not be active during performance of a general ISSU procedure, and the second configuration data structure may indicate one or more configuration functionalities of the network device that are to not be active during performance of the specific ISSU procedure associated with the data package (e.g., the first configuration data structure and the second configuration data structure may identify some or all of the same configuration functionalities and/or different configuration functionalities).

As shown in <FIG>, a configuration data structure (e.g., at least one of the first configuration data structure or the second configuration data structure) may include one or more data structure elements. Each data structure element may identify a configuration functionality of the one or more configuration functionalities of the network device that are incompatible with performance of the ISSU procedure. Moreover, the data structure element may indicate that the configuration functionality is not compatible with the ISSU procedure and/or that the configuration functionality is to not be active during performance of the ISSU procedure. For example, as shown in <FIG>, a first data structure identifies a first configuration functionality (e.g., a "chassis synchronization network-option" configuration functionality) and includes ISSU information (e.g., indicated by an "action" label) that indicates that (<NUM>) the first configuration functionality is not compatible with the ISSU procedure (e.g., via a "warn-message" label, "ISSU is not supported for Clock Synchronization (SyncE)") and that (<NUM>) the first configuration functionality is to not be active during performance of the ISSU procedure (e.g., via an "override" label). As another example, as further shown in <FIG>, a second data structure identifies a second configuration functionality (e.g., a "protocols ptp" configuration functionality) and includes ISSU information (e.g., indicated by an "action" label) that indicates that (<NUM>) the second configuration functionality is not compatible with the ISSU procedure (e.g., via a "warn-message" label, "ISSU is not supported for Clock Synchronization (PTP/Hybrid)") and that (<NUM>) the second configuration functionality is to not be active during performance of the ISSU procedure (e.g., via an "override" label).

As shown in <FIG>, and by reference number <NUM>, the network device may identify the one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure. For example, the network device may process (e.g., search, such as by using a processing tool configured to search configuration data structures) the first configuration data structure and/or the second configuration data structure to identify one or more data structure elements, and may process (e.g., parse, such as by using the process tool) the one or more data structure elements to identify the one or more configuration functionalities of the network device (e.g., that are identified by the one or more data structure elements). In some implementations, when the first configuration data structure and the second configuration data structure identify a same configuration functionality (and both indicate that the configuration functionality is to not be active during performance of the ISSU procedure), the network device may include the configuration functionality in the one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure. In some implementations, when the first configuration data structure and the second configuration data structure identify a same configuration functionality (but do not both indicate that the configuration functionality is to not be active during performance of the ISSU procedure), the network device may compare a first data structure element of the first configuration data structure and a second data structure element of the second configuration data structure that both identify the configuration functionality. The network device may thereby select, based on the comparison and from the first data structure element and the second data structure element, a particular data structure element (e.g., select a particular data structure element that has a higher priority, a more recent modification date, or another more preferential characteristic or parameter than the other data structure element). Accordingly, when the selected data structure element indicates that the configuration functionality is to not be active during performance of the ISSU procedure, the network device may include the configuration functionality in the one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure.

Additionally, or alternatively, when the first configuration data structure identifies a configuration functionality that is not identified by the second configuration data structure, the network device may not include the configuration functionality in the one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure (e.g., when the first configuration data structure indicates that the configuration functionality is to not be active during performance of the ISSU procedure). Additionally, or alternatively, when the second configuration data structure identifies a configuration functionality that is not identified by the first configuration data structure, the network device may include the configuration functionality in the one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure (e.g., when the second configuration data structure indicates that the configuration functionality is to not be active during performance of the ISSU procedure). Some additional implementations contemplate other processes for identifying the one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure (e.g., based on the first configuration data structure and/or the second configuration data structure, or not based on the first configuration data structure and the second configuration data structure).

In some implementations, the network device may store information identifying the one or more configuration functionalities of the network device in another data structure (e.g., a database, an electronic file, or another data structure) that is distinct from the first configuration data structure and the second configuration data structure. This may facilitate one or more processing steps associated with deactivating and/or activating the one or more configuration functionalities of the network device, as further described herein (e.g., because the network device does not need to reprocess the first configuration data structure and/or the second configuration data structure to identify the one or more configuration functionalities of the network device).

As shown in <FIG>, and by reference number <NUM>, the network device may cause the one or more configuration functionalities of the network device to be deactivated. For example, the network device may cause one or more deactivation actions associated with the one or more configuration functionalities of the network device to be performed. The one or more deactivation actions may include, for example, the network device generating one or more commands to deactivate the one or more configuration functionalities and executing the one or more commands (e.g., causing the one or more commands to be executed by the network device). In some implementations, the network device may obtain the information identifying the one or more configuration functionalities of the network device from the other data structure and may cause, based on the information, the one or more configuration functionalities of the network device to be deactivated.

As shown in <FIG>, and by reference number <NUM>, the network device may cause the ISSU procedure to be performed (e.g., after causing the one or more configuration functionalities of the network device to be deactivated). The network device may cause the ISSU procedure to be performed based on the data package (e.g., that the network device received from the server device). For example, the network device may process (e.g., execute) the data package to cause the network device to perform the ISSU procedure. In this way, the network device may cause one or more parameters (e.g., one or more settings) of at least one other configuration functionality of the network device (e.g., that is not included in the one or more configuration functionalities of the network device that are incompatible with performance of the ISSU procedure) to be modified (e.g., cause the one or more parameters to be updated based on performance of the ISSU procedure).

As shown in <FIG>, and by reference number <NUM>, the network device may cause the one or more configuration functionalities of the network device to be activated (e.g., after causing the ISSU procedure to be performed). For example, the network device may cause one or more activation actions associated with the one or more configuration functionalities of the network device to be performed. The one or more deactivation actions may include, for example, the network device generating one or more commands to activate the one or more configuration functionalities and executing the one or more commands (e.g., causing the one or more commands to be executed by the network device). In some implementations, the network device may obtain the information identifying the one or more configuration functionalities of the network device from the other data structure and may cause, based on the information, the one or more configuration functionalities of the network device to be activated.

For example, a network device, of the one or more network devices, may perform one or more functions described as being performed by the monitoring device, or vice versa.

<FIG> is a diagram of an example environment <NUM> in which systems and/or methods described herein may be implemented. As shown in <FIG>, environment <NUM> may include a network device <NUM>, a network <NUM>, a server device <NUM>, and/or a client device <NUM>. Devices and/or elements of environment <NUM> may interconnect via wired connections and/or wireless connections.

Network device <NUM> includes one or more devices capable of receiving, processing, storing, routing, and/or providing information related to automatic deactivation and activation of configuration functionalities of the network device <NUM> that are incompatible with performance of an ISSU procedure, as described elsewhere herein. For example, network device <NUM> may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router or a provider core router), a virtual router, or another type of router. Additionally, or alternatively, network device <NUM> may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, or a data center server), a load balancer, and/or a similar device. In some implementations, network device <NUM> may be a physical device implemented within a housing, such as a chassis. In some implementations, network device <NUM> may be a virtual device implemented by one or more computer devices of a cloud computing environment or a data center. In some implementations, a group of network devices <NUM> may be a group of data center nodes that are used to route traffic flow through network <NUM>.

Network <NUM> includes one or more wired and/or wireless networks. For example, network <NUM> may include a cellular network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a private network, the Internet, and/or a combination of these or other types of networks. The network <NUM> enables communication among the devices of environment <NUM>.

Server device <NUM> includes one or more devices capable of receiving, generating, storing, processing, providing, and/or routing information related to a data package associated with an ISSU procedure, as described elsewhere herein. Server device <NUM> may include a communication device and/or a computing device. For example, server device <NUM> may include a server, such as an application server, a client server, a web server, a database server, a host server, a proxy server, a virtual server (e.g., executing on computing hardware), or a server in a cloud computing system. In some implementations, server device <NUM> includes computing hardware used in a cloud computing environment.

Client device <NUM> includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with providing a command indicating that the network device <NUM> is to be updated via performance of an ISSU procedure, as described elsewhere herein. Client device <NUM> may include a communication device and/or a computing device. For example, client device <NUM> may include a wireless communication device, a mobile phone, a user equipment, a laptop computer, a tablet computer, a desktop computer, a gaming console, a set-top box, a wearable communication device (e.g., a smart wristwatch, a pair of smart eyeglasses, a head mounted display, or a virtual reality headset), or a similar type of device.

<FIG> is a diagram of example components of a device <NUM>, which may correspond to network device <NUM>, server device <NUM>, and/or client device <NUM>. In some implementations, network device <NUM>, server device <NUM>, and/or client device <NUM> include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include a bus <NUM>, a processor <NUM>, a memory <NUM>, an input component <NUM>, an output component <NUM>, and a communication component <NUM>.

Bus <NUM> includes one or more components that enable wired and/or wireless communication among the components of device <NUM>. Bus <NUM> may couple together two or more components of <FIG>, such as via operative coupling, communicative coupling, electronic coupling, and/or electric coupling. Processor <NUM> includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field-programmable gate array, an application-specific integrated circuit, and/or another type of processing component. Processor <NUM> is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor <NUM> includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

Memory <NUM> includes volatile and/or nonvolatile memory. For example, memory <NUM> may include random access memory (RAM), read only memory (ROM), a hard disk drive, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory). Memory <NUM> may include internal memory (e.g., RAM, ROM, or a hard disk drive) and/or removable memory (e.g., removable via a universal serial bus connection). Memory <NUM> may be a non-transitory computer-readable medium. Memory <NUM> stores information, instructions, and/or software (e.g., one or more software applications) related to the operation of device <NUM>. In some implementations, memory <NUM> includes one or more memories that are coupled to one or more processors (e.g., processor <NUM>), such as via bus <NUM>.

Input component <NUM> enables device <NUM> to receive input, such as user input and/or sensed input. For example, input component <NUM> may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and/or an actuator. Output component <NUM> enables device <NUM> to provide output, such as via a display, a speaker, and/or a light-emitting diode. Communication component <NUM> enables device <NUM> to communicate with other devices via a wired connection and/or a wireless connection. For example, communication component <NUM> may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.

Device <NUM> may perform one or more operations or processes described herein. In some examples, instructions for execution by the processor may be provided by way of a computer-readable medium. For example, a non-transitory computer-readable medium (e.g., memory <NUM>) may store a set of instructions (e.g., one or more instructions or code) for execution by processor <NUM>. Such instructions may for example be received via a computer-readable transmission medium, which may be received via the communication component <NUM>. Such a transmission medium may also include communication of instructions over the bus <NUM>. Processor <NUM> may execute the set of instructions to perform one or more operations or processes described herein. In some implementations, execution of the set of instructions, by one or more processors <NUM>, causes the one or more processors <NUM> and/or the device <NUM> to perform one or more operations or processes described herein. In some implementations, hardwired circuitry is used instead of or in combination with the instructions to perform one or more operations or processes described herein. Additionally, or alternatively, processor <NUM> may be configured to perform one or more operations or processes described herein.

<FIG> is a diagram of example components of a device <NUM>. Device <NUM> may correspond to network device <NUM>, server device <NUM>, and/or client device <NUM>. In some implementations, network device <NUM>, server device <NUM>, and/or client device <NUM> may include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include one or more input components <NUM>-<NUM> through <NUM>-B (B ≥ <NUM>) (hereinafter referred to collectively as input components <NUM>, and individually as input component <NUM>), a switching component <NUM>, one or more output components <NUM>-<NUM> through <NUM>-C (C ≥ <NUM>) (hereinafter referred to collectively as output components <NUM>, and individually as output component <NUM>), and a controller <NUM>.

Controller <NUM> may perform one or more processes described herein. Controller <NUM> may perform these processes in response to executing software instructions stored by and/or received via a computer-readable medium. A computer-readable storage medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

<FIG> is a flowchart of an example process <NUM> associated with automatic deactivation and activation of configuration functionalities of a network device that are incompatible with performance of an in-service software upgrade procedure. In some implementations, one or more process blocks of <FIG> are performed by the network device (e.g., network device <NUM>). In some implementations, one or more process blocks of <FIG> are performed by another device or a group of devices separate from or including the network device, such as a server device (e.g., server device <NUM>) and/or a client device (e.g., client device <NUM>). Additionally, or alternatively, one or more process blocks of <FIG> may be performed by one or more components of device <NUM>, such as processor <NUM>, memory <NUM>, input component <NUM>, output component <NUM>, and/or communication component <NUM>; one or more components of device <NUM>, such as input component <NUM>-<NUM>, switching component <NUM>, output component <NUM>, and/or controller <NUM>; and/or one or more components of another device.

As shown in <FIG>, process <NUM> may include identifying a first configuration data structure included in the network device (block <NUM>). For example, the network device may identify a first configuration data structure included in the network device, as described above.

As further shown in <FIG>, process <NUM> may include obtaining a data package associated with an ISSU procedure that includes a second configuration data structure (block <NUM>). For example, the network device may obtain a data package associated with an ISSU procedure that includes a second configuration data structure, as described above.

As further shown in <FIG>, process <NUM> may include identifying one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure (block <NUM>). For example, the network device may identify, based on at least one of the first configuration data structure or the second configuration data structure, one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure, as described above.

As further shown in <FIG>, process <NUM> may include causing the one or more configuration functionalities of the network device to be deactivated (block <NUM>). For example, the network device may cause the one or more configuration functionalities of the network device to be deactivated, as described above.

As further shown in <FIG>, process <NUM> may include causing, based on the data package, the ISSU procedure to be performed (block <NUM>). For example, the network device may cause, after causing the one or more configuration functionalities of the network device to be deactivated and based on the data package, the ISSU procedure to be performed, as described above.

As further shown in <FIG>, process <NUM> may include causing the one or more configuration functionalities of the network device to be activated (block <NUM>). For example, the network device may cause, after causing the ISSU procedure to be performed, the one or more configuration functionalities of the network device to be activated, as described above.

In a first implementation, obtaining the data package includes receiving, from a client device, a command indicating that the network device is to be updated via performance of the ISSU procedure, sending, to a server device and based on the command, a request for the data package, and receiving, based on sending the request, the data package.

In a second implementation, alone or in combination with the first implementation, the command indicates that the network device has permission to deactivate and activate configuration functionalities of the network device to facilitate performance of the ISSU procedure.

In a third implementation, alone or in combination with one or more of the first and second implementations, identifying the one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure includes processing the first configuration data structure and the second configuration data structure to identify one or more data structure elements, wherein each data structure element, of the one or more data structure elements, identifies a configuration functionality of the one or more configuration functionalities of the network device, wherein the data structure element indicates that the configuration functionality is not compatible with the ISSU procedure, and the data structure element indicates that the configuration functionality is to not be active during performance of the ISSU procedure; and processing the one or more data structure elements to identify the one or more configuration functionalities of the network device.

In a fourth implementation, alone or in combination with one or more of the first through third implementations, process <NUM> includes storing information identifying the one or more configuration functionalities of the network device in another data structure, and causing, based on the information stored in the other data structure, one or more deactivation actions associated with the one or more configuration functionalities of the network device to be performed.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, process <NUM> includes causing, based on the information stored in the other data structure, one or more activation actions associated with the one or more configuration functionalities of the network device to be performed.

In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, causing the ISSU procedure to be performed is to cause one or more parameters of at least one other configuration functionality of the network device to be modified.

Although <FIG> shows example blocks of process <NUM>, in some implementations, process <NUM> includes additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in <FIG>.

Therefore, from one perspective, there has been described a network device configured to identify a first configuration data structure included in the network device and may be configured to obtain a data package associated with an ISSU procedure that includes a second configuration data structure. The network device may be configured to identify, based on the first configuration data structure and the second configuration data structure, one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure. The network device may be configured to cause the one or more configuration functionalities of the network device to be deactivated and to thereafter cause the ISSU procedure to be performed. The network device may be configured to cause, after causing the ISSU procedure to be performed, the one or more configuration functionalities of the network device to be activated.

As used herein, traffic or content may include a set of packets. A packet may refer to a communication structure for communicating information, such as a protocol data unit (PDU), a service data unit (SDU), a network packet, a datagram, a segment, a message, a block, a frame (e.g., an Ethernet frame), a portion of any of the above, and/or another type of formatted or unformatted unit of data capable of being transmitted via a network.

As an example, "at least one of: a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiple of the same item.

Claim 1:
A network device, comprising:
one or more memories; and
one or more processors to:
identify a first configuration data structure included in the network device;
obtain a data package associated with an in-service software upgrade, ISSU, procedure that includes a second configuration data structure;
identify, based on the first configuration data structure and the second configuration data structure, one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure by;
processing the first configuration data structure and the second configuration data structure to identify one or more data structure elements,
wherein each data structure element, of the one or more data structure elements, identifies a configuration functionality of the one or more configuration functionalities of the network device, wherein:
the data structure element indicates that the configuration functionality is not compatible with the ISSU procedure, and
the data structure element indicates that the configuration functionality is to not be active during performance of the ISSU procedure; and
processing the one or more data structure elements to identify the one or more configuration functionalities of the network device;
cause the one or more configuration functionalities of the network device to be deactivated;
cause, after causing the one or more configuration functionalities of the network device to be deactivated and based on the data package, the ISSU procedure to be performed; and
cause, after causing the ISSU procedure to be performed, the one or more configuration functionalities of the network device to be activated.