Abstract: A device can receive information associated with an application identifier of an application that is to be implemented by a cluster. The device can provide information associated with an instance identifier of the device. The device can receive information associated with a first set of instance identifiers associated with the first set of devices. The device can configure, using the information associated with the first set of instance identifiers, the device to implement the application as part of the cluster. The device can receive information associated with a second set of instance identifiers associated with a second set of devices of the cluster. The device can compare the information associated with the first set of instance identifiers and the information associated with the second set of instance identifiers. The device can selectively configure the device to implement the application as part of the cluster based on the comparison.

Abstract: A device can receive information associated with an application identifier of an application that is to be implemented by a cluster. The device can provide information associated with an instance identifier of the device. The device can receive information associated with a first set of instance identifiers associated with the first set of devices. The device can configure, using the information associated with the first set of instance identifiers, the device to implement the application as part of the cluster. The device can receive information associated with a second set of instance identifiers associated with a second set of devices of the cluster. The device can compare the information associated with the first set of instance identifiers and the information associated with the second set of instance identifiers. The device can selectively configure the device to implement the application as part of the cluster based on the comparison.

Abstract: A network system for an expandable distributed core architecture (“DCA”) includes multiple spine switches, multiple leaf switches coupled thereto, and a plurality of interconnections coupling each of the spine switches to each of the leaf switches. Servers, storage, and other system items and resources can be coupled to the leafs via downlinks and uplinks. Each of the plurality of spine switches includes at least one unused spine port that is reserved for a future expansion of the DCA in order to accommodate the addition of at least one other separate leaf switch to the at least one unused spine port. Additional ports can be unused and reserved for future expansion additions of more leafs and/or more spines. Also, a computing system assists in the design of the specific number and configuration of spines, leafs and interconnections based upon user inputs regarding current and future system needs.

Abstract: A network system for an expandable distributed core architecture (“DCA”) includes multiple spine switches, multiple leaf switches coupled thereto, and a plurality of interconnections coupling each of the spine switches to each of the leaf switches. Servers, storage, and other system items and resources can be coupled to the leafs via downlinks and uplinks. Each of the plurality of spine switches includes at least one unused spine port that is reserved for a future expansion of the DCA in order to accommodate the addition of at least one other separate leaf switch to the at least one unused spine port. Additional ports can be unused and reserved for future expansion additions of more leafs and/or more spines. Also, a computing system assists in the design of the specific number and configuration of spines, leafs and interconnections based upon user inputs regarding current and future system needs.

Abstract: A network system for an expandable distributed core architecture (“DCA”) includes multiple spine switches, multiple leaf switches coupled thereto, and a plurality of interconnections coupling each of the spine switches to each of the leaf switches. Servers, storage, and other system items and resources can be coupled to the leafs via downlinks and uplinks. Each of the plurality of spine switches includes at least one unused spine port that is reserved for a future expansion of the DCA in order to accommodate the addition of at least one other separate leaf switch to the at least one unused spine port. Additional ports can be unused and reserved for future expansion additions of more leafs and/or more spines. Also, a computing system assists in the design of the specific number and configuration of spines, leafs and interconnections based upon user inputs regarding current and future system needs.

Abstract: A system and method for a symmetric switching fabric includes a first switching tier that includes a plurality of leaf switches, a second switching tier that includes one or more spine switches, and a plurality of interlinks for coupling the leaf switches to the spine switches. Each of the leaf switches includes one or more first ports configured to couple each of the leaf switches to other network devices outside the switching fabric and one or more second ports for coupling each of the leaf switches to each of the spine switches. A ratio of a number of first ports and a number of second ports is selected based on an oversubscription ratio. For each pair of a first switch selected from the leaf switches and a second switch selected from the spine switches, a same number of first interlinks selected from the plurality of interlinks couple the first switch to the second switch.

Abstract: A network system for an expandable distributed core architecture (“DCA”) includes multiple spine switches, multiple leaf switches coupled thereto, and a plurality of interconnections coupling each of the spine switches to each of the leaf switches. Servers, storage, and other system items and resources can be coupled to the leafs via downlinks and uplinks. Each of the plurality of spine switches includes at least one unused spine port that is reserved for a future expansion of the DCA in order to accommodate the addition of at least one other separate leaf switch to the at least one unused spine port. Additional ports can be unused and reserved for future expansion additions of more leafs and/or more spines. Also, a computing system assists in the design of the specific number and configuration of spines, leafs and interconnections based upon user inputs regarding current and future system needs.

Abstract: A network system for an expandable distributed core architecture (“DCA”) includes multiple spine switches, multiple leaf switches coupled thereto, and a plurality of interconnections coupling each of the spine switches to each of the leaf switches. Servers, storage, and other system items and resources can be coupled to the leafs via downlinks and uplinks. Each of the plurality of spine switches includes at least one unused spine port that is reserved for a future expansion of the DCA in order to accommodate the addition of at least one other separate leaf switch to the at least one unused spine port. Additional ports can be unused and reserved for future expansion additions of more leafs and/or more spines. Also, a computing system assists in the design of the specific number and configuration of spines, leafs and interconnections based upon user inputs regarding current and future system needs.

Abstract: A system and method for a symmetric switching fabric includes a first switching tier that includes a plurality of leaf switches, a second switching tier that includes one or more spine switches, and a plurality of interlinks for coupling the leaf switches to the spine switches. Each of the leaf switches includes one or more first ports configured to couple each of the leaf switches to other network devices outside the switching fabric and one or more second ports for coupling each of the leaf switches to each of the spine switches. A ratio of a number of first ports and a number of second ports is selected based on an oversubscription ratio. For each pair of a first switch selected from the leaf switches and a second switch selected from the spine switches, a same number of first interlinks selected from the plurality of interlinks couple the first switch to the second switch.

Abstract: A system and method for a symmetric switching fabric includes a first switching tier that includes a plurality of leaf switches, a second switching tier that includes one or more spine switches, and a plurality of interlinks for coupling the leaf switches to the spine switches. Each of the leaf switches includes one or more first ports configured to couple each of the leaf switches to other network devices outside the switching fabric and one or more second ports for coupling each of the leaf switches to each of the spine switches. A ratio of a number of first ports and a number of second ports is selected based on an oversubscription ratio. For each pair of a first switch selected from the leaf switches and a second switch selected from the spine switches, a same number of first interlinks selected from the plurality of interlinks couple the first switch to the second switch.

Abstract: A system and method for a symmetric switching fabric includes a first switching tier that includes a plurality of leaf switches, a second switching tier that includes one or more spine switches, and a plurality of interlinks for coupling the leaf switches to the spine switches. Each of the leaf switches includes one or more first ports configured to couple each of the leaf switches to other network devices outside the switching fabric and one or more second ports for coupling each of the leaf switches to each of the spine switches. A ratio of a number of first ports and a number of second ports is selected based on an oversubscription ratio. For each pair of a first switch selected from the leaf switches and a second switch selected from the spine switches, a same number of first interlinks selected from the plurality of interlinks couple the first switch to the second switch.

Abstract: A network system for an expandable distributed core architecture (“DCA”) includes multiple spine switches, multiple leaf switches coupled thereto, and a plurality of interconnections coupling each of the spine switches to each of the leaf switches. Servers, storage, and other system items and resources can be coupled to the leafs via downlinks and uplinks. Each of the plurality of spine switches includes at least one unused spine port that is reserved for a future expansion of the DCA in order to accommodate the addition of at least one other separate leaf switch to the at least one unused spine port. Additional ports can be unused and reserved for future expansion additions of more leafs and/or more spines. Also, a computing system assists in the design of the specific number and configuration of spines, leafs and interconnections based upon user inputs regarding current and future system needs.

Abstract: A method and apparatus for automating the configuration of network entities with a network management system. More particularly, a graphical user interface incorporates a template to allow administrators to configure attributes of network entities. The graphical user interface and template reduce the number of blocks required to configure network entities and also minimize user errors. The graphical user interface also allows an administrator to add and manage templates for future use. The method and apparatus are also for monitoring the progress of configuring network entities and generating an operation log.

Abstract: A method for reporting events relating to objects of a network element manageable by a network management device, using a network management protocol, and devices, a network, and computer-readable storage medium storing control logic, that operate in accordance with the method. Events for each object are detected, event information is generated for detected events, generated event information for multiple events is packaged into a trap message for each object type, the trap message is communicated from the network element to the network management device, and the event information from the communicated trap message is unpacked at the network management device. In this manner, network congestion and processor overload at the network management device can be reduced.

Abstract: A method and apparatus for automating the configuration of network entities with a network management system. More particularly, a graphical user interface incorporates a template to allow administrators to configure attributes of network entities. The graphical user interface and template reduce the number of blocks required to configure network entities and also minimize user errors. The graphical user interface also allows an administrator to add and manage templates for future use. The method and apparatus are also for monitoring the progress of configuring network entities and generating an operation log.

Abstract: A method for reporting events relating to objects of a network element manageable by a network management device, using a network management protocol, and devices, a network, and computer-readable storage medium storing control logic, that operate in accordance with the method. Events for each object are detected, event information is generated for detected events, generated event information for multiple events is packaged into a trap message for each object type, the trap message is communicated from the network element to the network management device, and the event information from the communicated trap message is unpacked at the network management device. In this manner, network congestion and processor overload at the network management device can be reduced.