Abstract: A method and network device for network traffic flooding. Specifically, the method and network device disclosed herein implement the mitigation of the lack of data-link layer (or L2) addressing resolutions, usually learned by or programmed manually into the network device, through the flooding of affected network traffic across identified network broadcast domains. Flooding of the network traffic in the aforementioned manner may ensure that at least the destination(s) of the network traffic receives the network traffic at least in scenarios where which it is unknown out of which particular physical network interface(s) should the network traffic be transmitted to reach the destination(s).

Abstract: A method and network device for network traffic flooding. Specifically, the method and network device disclosed herein implement the mitigation of the lack of data-link layer (or L2 ) addressing resolutions, usually learned by or programmed manually into the network device, through the flooding of affected network traffic across identified network broadcast domains. Flooding of the network traffic in the aforementioned manner may ensure that at least the destination(s) of the network traffic receives the network traffic at least in scenarios where which it is unknown out of which particular physical network interface(s) should the network traffic be transmitted to reach the destination(s).

Abstract: A method and network device for network traffic flooding. Specifically, the method and network device disclosed herein implement the mitigation of the lack of data-link layer (or L2) addressing resolutions, usually learned by or programmed manually into the network device, through the flooding of affected network traffic across identified network broadcast domains. Flooding of the network traffic in the aforementioned manner may ensure that at least the destination(s) of the network traffic receives the network traffic at least in scenarios where which it is unknown out of which particular physical network interface(s) should the network traffic be transmitted to reach the destination(s).

Abstract: A method and network device for network traffic flooding. Specifically, the method and network device disclosed herein implement the mitigation of the lack of data-link layer (or L2) addressing resolutions, usually learned by or programmed manually into the network device, through the flooding of affected network traffic across identified network broadcast domains. Flooding of the network traffic in the aforementioned manner may ensure that at least the destination(s) of the network traffic receives the network traffic at least in scenarios where which it is unknown out of which particular physical network interface(s) should the network traffic be transmitted to reach the destination(s).

Abstract: Methods, systems, and computer readable mediums for hitless repair. Hitless repair may include making a first determination, by a system control device (SCD) agent of a network device, that a SCD of the network device has experienced an error and/or is to be updated; making a second determination, by the SCD agent, that the SCD and the network device support the hitless repair; performing, by the SCD agent, a pre-hitless repair action set; and performing, by the SCD agent and after completing the pre-hitless repair action set, a post-hitless repair action set, including a hitless reset of the SCD.

Abstract: Methods, systems, and computer readable mediums for hitless repair. Hitless repair may include making a first determination, by a system control device (SCD) agent of a network device, that a SCD of the network device has experienced an error and/or is to be updated; making a second determination, by the SCD agent, that the SCD and the network device support the hitless repair; performing, by the SCD agent, a pre-hitless repair action set; and performing, by the SCD agent and after completing the pre-hitless repair action set, a post-hitless repair action set, including a hitless reset of the SCD.

Abstract: A method and apparatus of a network element that updates an interface list of a multi-link group of a network element is described. In an exemplary embodiment, a network element receives an indication that the interface list for the multi-link group on a network element is to change. In addition, the interface list includes a first set of interfaces. The network element further includes an address table having a plurality of address entries, where each of the plurality of address entries includes an address, a multi-link nexthop, and a tag group reference. The tag group reference references an entry in a tag group table, where a tag group entry includes a tag group identifier and a tag group set of interfaces. The network element further receives a second set of interfaces. The network element additionally updates the interface list for the tag group entry to include a second set of interfaces. Furthermore, the network element transmits data with the multi-link group using the second set of interfaces.

Abstract: A method and apparatus of a network element that updates an interface list of a multi-link group of a network element is described. In an exemplary embodiment, a network element receives an indication that the interface list for the multi-link group on a network element is to change. In addition, the interface list includes a first set of interfaces. The network element further includes an address table having a plurality of address entries, where each of the plurality of address entries includes an address, a multi-link nexthop, and a tag group reference. The tag group reference references an entry in a tag group table, where a tag group entry includes a tag group identifier and a tag group set of interfaces. The network element further receives a second set of interfaces. The network element additionally updates the interface list for the tag group entry to include a second set of interfaces. Furthermore, the network element transmits data with the multi-link group using the second set of interfaces.

Abstract: Systems and methods for providing service virtualization endpoint (SVE) redundancy in a two-node, active-standby form. An active-standby pair of SVEs register with a cloud-centric-network control point (CCN-CP) as a single service node (SN) using a virtual IP address for both a control-plane and a data-plane. At any given time, only the active SVE is a host for the control-plane and the data-plane. When a failover happens, the hosting operation is taken over by the standby SVE, therefore the failover will be transparent to CCN-CP and the SN.

Abstract: Systems and methods for providing service virtualization endpoint (SVE) redundancy in a two-node, active-standby form. An active-standby pair of SVEs register with a cloud-centric-network control point (CCN-CP) as a single service node (SN) using a virtual IP address for both a control-plane and a data-plane. At any given time, only the active SVE is a host for the control-plane and the data-plane. When a failover happens, the hosting operation is taken over by the standby SVE, therefore the failover will be transparent to CCN-CP and the SN.

Abstract: A plurality of SMP modules and an IOP module communicate storage traffic via respective corresponding I/O controllers coupled to respective physical ports of a switch fabric by addressing cells to physical port addresses corresponding to the physical ports. One of the SMPs executes initiator software to partially manage the storage traffic and the IOP executes target software to partially manage the storage traffic. Storage controllers are coupled to the IOP, enabling communication with storage devices, such as disk drives, tape drives, and/or networks of same. Respective network identification registers are included in each of the I/O controller corresponding to the SMP executing the initiator software and the I/O controller corresponding to the IOP. Transport of the storage traffic in accordance with a particular VLAN is enabled by writing a same particular value into each of the network identification registers.

Abstract: A plurality of SMP modules and an IOP module communicate storage traffic via respective corresponding I/O controllers coupled to respective physical ports of a switch fabric by addressing cells to physical port addresses corresponding to the physical ports. One of the SMPs executes initiator software to partially manage the storage traffic and the IOP executes target software to partially manage the storage traffic. Storage controllers are coupled to the IOP, enabling communication with storage devices, such as disk drives, tape drives, and/or networks of same. Respective network identification registers are included in each of the I/O controller corresponding to the SMP executing the initiator software and the I/O controller corresponding to the IOP. Transport of the storage traffic in accordance with a particular VLAN is enabled by writing a same particular value into each of the network identification registers.

Abstract: Systems and methods for providing service virtualization endpoint (SVE) redundancy in a two-node, active-standby form. An active-standby pair of SVEs register with a cloud-centric-network control point (CCN-CP) as a single service node (SN) using a virtual IP address for both a control-plane and a data-plane. At any given time, only the active SVE is a host for the control-plane and the data-plane. When a failover happens, the hosting operation is taken over by the standby SVE, therefore the failover will be transparent to CCN-CP and the SN.

Abstract: In one aspect, initial storage system control information is received, and in response a configuration of a storage interface is determined in accordance with the initial storage system control information. Then final storage system control information is accessed via the storage interface and the storage interface is reconfigured in accordance with the final storage system control information. In another aspect, one of a plurality of physical partitions of a physically partitionable symmetric multiprocessor executes a storage control process to control storage traffic, and another one of the physical partitions executes a program to process the storage traffic. The physical partitions are enabled to communicate the storage traffic at least in part via respective input/output controllers coupled to a switch fabric.

Abstract: Storage gateway provisioning, configuration, and management functions provide mechanisms to specify and manage parameters and operations associated with storage gateways. The parameters may include any combination of VLAN topology, zoning behavior, LUN masking, bandwidth, and priority. The parameters may also include path information describing initiator to target associations, enabling load-balancing aggregations and multipathing redundancy. Parameters may be specified at relatively low-levels, describing specific HW elements, or may be specified at relatively high-levels, describing desired bandwidth and redundancy requirements, with SW determining low-level HW assignments. Configuration and management functions enable dynamic modification of storage gateway parameters (such as bandwidth between selected initiator and target pairs). Management functions also enable dynamic switchover from a primary path to a secondary path with respect to a storage device.

Abstract: Storage gateway remote and local access to storage devices is provided in part via a target implementing bandwidth-controlled access to the devices. The target may be iSCSI-compatible, and may also optionally implement protection, security, and performance features. The protection and security features include any combination of VLANs, zoning, Logical Unit Number (LUN) masking, and encryption. The performance features include any combination of HW-accelerated Remote Direct Memory Access (RDMA), prioritized I/O operations, and service priority (such as strict priority and straight or weighted round-robin priorities). An initiator may be implemented in a Processor Memory Module (PMM) coupled to a switch fabric that is in turn coupled to a target implemented in a Fibre Channel Module (FCM).

Abstract: Storage gateway remote and local access to storage devices is provided in part via an initiator implementing bandwidth-controlled access to the devices. The initiator may be iSCSI-compatible, and may also optionally implement protection, security, and performance features. The protection and security features include any combination of VLANs, zoning, Logical Unit Number (LUN) masking, and encryption. The performance features include any combination of HW-accelerated Remote Direct Memory Access (RDMA), prioritized I/O operations, and service priority (such as strict priority and straight or weighted round-robin priorities). An initiator may be implemented in a Processor Memory Module (PMM) coupled to a switch fabric that is in turn coupled to a target implemented in a Fibre Channel Module (FCM).