Abstract: Techniques are provided for managing, within a storage system, the sequence in which I/O requests are processed by the storage system based, at least in part, on a one or more logical characteristics of the I/O requests. The logical characteristics may include, for example, the identity of the user for whom the I/O request was submitted, the service that submitted the I/O request, the database targeted by the I/O request, an indication of a consumer group to which the I/O request maps, the reason why the I/O request was issued, a priority category of the I/O request, etc. Techniques are also provided for automatically establishing a scheduling policy within a storage system, and for dynamically changing the scheduling policy in response to changes in workload.

Abstract: Methods and systems for facilitating fault tolerance in a non-hot-standby configuration of a network routing system are provided. According to one embodiment, a failover method is provided. One or more processing engines of a network routing system are configured to function as active processing engines, each of which having one or more software contexts. A control blade is configured to monitor the active processing engines. One or more of the processing engines are identified to function as non-hot-standby processing engines, each of which having no pre-created software contexts corresponding to the software contexts of the active processing engines. The control blade monitors the active processing engines.

Abstract: Methods and systems for facilitating fault tolerance in a non-hot-standby configuration of a network routing system are provided. According to one embodiment, a failover method is provided. A fault manager executing on a control blade of multiple server blades of a network routing system actively monitors an active processing engine of multiple processing engines within the network routing system. Responsive to detecting a fault associated with the active processing engine, the active processing engine is dynamically replaced with a non-hot-standby processing engine of the multiple processing engines by (i) determining one or more software contexts that were associated with the active processing engine prior to detection of the fault, and (ii) creating one or more replacement software contexts within the non-hot-standby processing engine corresponding to the one or more software contexts.

Abstract: Methods and systems for facilitating fault tolerance in a non-hot-standby configuration of a network routing system are provided. According to one embodiment, a failover method is provided. A fault manager executing on a control blade of multiple server blades of a network routing system actively monitors an active processing engine of multiple processing engines within the network routing system. Responsive to detecting a fault associated with the active processing engine, the active processing engine is dynamically replaced with a non-hot-standby processing engine of the multiple processing engines by (i) determining one or more software contexts that were associated with the active processing engine prior to detection of the fault, and (ii) creating one or more replacement software contexts within the non-hot-standby processing engine corresponding to the one or more software contexts.

Abstract: Methods and systems for facilitating fault tolerance in a non-hot-standby configuration of a network routing system are provided. According to one embodiment, a method is provided for replacing an active processing engine with a non-hot-standby processing engine. Multiple processing engines within a network routing system are configured. The processing engines include an active processing engine having one or more software contexts, representative of a set of objects implementing a virtual router, for example, and a non-hot-standby processing engine having no pre-created software contexts corresponding to the one or more software contexts. Responsive to determining a fault associated with the active processing engine, the active processing engine is dynamically replaced with the non-hot-standby processing engine by creating replacement software contexts within the non-hot-standby processing engine corresponding to the one or more software contexts.

Abstract: Techniques are provided for managing, within a storage system, the sequence in which I/O requests are processed by the storage system based, at least in part, on a one or more logical characteristics of the I/O requests. The logical characteristics may include, for example, the identity of the user for whom the I/O request was submitted, the service that submitted the I/O request, the database targeted by the I/O request, an indication of a consumer group to which the I/O request maps, the reason why the I/O request was issued, a priority category of the I/O request, etc. Techniques are also provided for automatically establishing a scheduling policy within a storage system, and for dynamically changing the scheduling policy in response to changes in workload.

Abstract: Methods and systems for facilitating fault tolerance in a non-hot-standby configuration of a network routing system are provided. According to one embodiment, a method is provided for replacing an active processing engine with a non-hot-standby processing engine. Multiple processing engines within a network routing system are configured. The processing engines include an active processing engine having one or more software contexts, representative of a set of objects implementing a virtual router, for example, and a non-hot-standby processing engine having no pre-created software contexts corresponding to the one or more software contexts. Responsive to determining a fault associated with the active processing engine, the active processing engine is dynamically replaced with the non-hot-standby processing engine by creating replacement software contexts within the non-hot-standby processing engine corresponding to the one or more software contexts.

Abstract: Passive replication methods and systems to facilitate fault tolerance in a network routing system are provided. In one embodiment, a fault associated with a processing engine (PE) of a network routing system is detected by monitoring the health of the network routing system PEs. Responsive to detecting a fault (e.g., a link failure, a failure of a virtual router (VR) or a failure of the PE): VRs that were operating on the PE prior to detection of the fault are identified; configuration information (e.g., a set of command lines in a configuration file) associated with the identified VRs is identified; and the identified VRs are dynamically recreated on a new PE based on the configuration information. For example, a command line interface engine may replay the command line set with a new slot ID and a PE ID of the new PE to recreate the VRs on the new PE.

Abstract: Passive replication methods and systems to facilitate fault tolerance in a network routing system are provided. In one embodiment, a fault associated with a processing engine (PE) of a network routing system is detected by monitoring the health of the network routing system PEs. Responsive to detecting a fault (e.g., a link failure, a failure of a virtual router (VR) or a failure of the PE): VRs that were operating on the PE prior to detection of the fault are identified; configuration information (e.g., a set of command lines in a configuration file) associated with the identified VRs is identified; and the identified VRs are dynamically recreated on a new PE based on the configuration information. For example, a command line interface engine may replay the command line set with a new slot ID and a PE ID of the new PE to recreate the VRs on the new PE.

Abstract: In a network routing system,a control blade provides for redundancy and failover of virtual routers (VRs) instantiated by objects running on processing engines of the several virtual routing engines (VREs). When the control blade detects a failure of one processing engines, it may identify the virtual private networks (VPNs) and/or VRs operating on the failed processing engine. The control blade identifies a set of command lines corresponding with the identified VPNs and VRs, and replays the set of command lines with an identity of a new processing engine to recreate the identified VPNs and VRs on the new processing engine.

Abstract: In a network routing system,a control blade provides for redundancy and failover of virtual routers (VRs) instantiated by objects running on processing engines of the several virtual routing engines (VREs). When the control blade detects a failure of one processing engines, it may identify the virtual private networks (VPNs) and/or VRs operating on the failed processing engine. The control blade identifies a set of command lines corresponding with the identified VPNs and VRs, and replays the set of command lines with an identity of a new processing engine to recreate the identified VPNs and VRs on the new processing engine.

Abstract: In a network routing system, a control blade provides for redundancy and failover of virtual routers (VRs) instantiated by objects running on processing engines of the several virtual routing engines (VREs). When the control blade detects a failure of one processing engines, it may identify the virtual private networks (VPNs) and/or VRs operating on the failed processing engine. The control blade identifies a set of command lines corresponding with the identified VPNs and VRs, and replays the set of command lines with an identity of a new processing engine to recreate the identified VPNs and VRs on the new processing engine.

Abstract: In a network routing system, a control blade provides for redundancy and failover of virtual routers (VRs) instantiated by objects running on processing engines of the several virtual routing engines (VREs). When the control blade detects a failure of one processing engines, it may identify the virtual private networks (VPNs) and/or VRs operating on the failed processing engine. The control blade identifies a set of command lines corresponding with the identified VPNs and VRs, and replays the set of command lines with an identity of a new processing engine to recreate the identified VPNs and VRs on the new processing engine.