Abstract:
A network element includes one or more hardware memory resources of fixed storage capacity for storing data used to configure a plurality of networking features of the network element. A utilization management process runs on the network element to perform operations including obtaining utilization data representing utilization of the one or more hardware memory resources, and analyzing the utilization data of the one or more hardware memory resources to produce summarized utilization data.
Abstract:
A method is provided in one example embodiment and includes calculating a packet metric for a first one of a plurality of links connected to a network element, wherein the packet metric is equal to a packet count over a period of time T divided by a maximum throughput of the first one of the links; and determining based on the packet metric whether traffic on the one of the links should be switched to another one of the plurality of links to optimize power usage. If a determination is made that the traffic on the first one of the links should be switched to another one of the plurality of links, the method further includes selecting a second link from a subset of the plurality of links; assigning the traffic to the selected second link; and applying a cost saving measure at an interface of the network element to which the first link is connected.
Abstract:
In accordance with one example embodiment, there is provided a method for configuring a virtual IP address (“VIP”) at a network element, wherein the configuring includes identifying at least one ingress interface of the network element for receiving traffic destined for the VIP and wherein the VIP is associated with a plurality of servers; determining whether the configuring indicates that the VIP is to be advertised; and advertising the configured VIP address to at least one neighboring network node if the configuring indicates that the VIP is to be advertised.
Abstract:
In an example, there is disclosed a network switch or other computing apparatus comprising: an ingress interface; a plurality of egress interfaces; and one or more logic elements, including at least a content addressable memory (CAM), comprising a channel selection engine to provide persistent channel selection comprising: receive a packet on the ingress interface; inspect a layer 2 (L2) attribute of the packet; lookup the L2 attribute in the CAM; and assign the packet to an egress interface communicatively coupled to a network service.
Abstract:
A method is provided in one example and includes receiving a data stream that includes IPv6 traffic, communicating the IPv6 traffic to a network element that does not support IPv6 probing, and probing the network element using IPv4.
Abstract:
The present disclosure relates to providing shared resources to virtual devices on a network switch. In one example, a switch comprises a plurality of virtual device contexts (VDCs) and a default virtual device context (DVDC). The DVDC stores configuration data that identifies a network resource. The DVDC transmits a reference to the configuration data to each of the plurality of VDCs. Each of plurality of VDCs receives the reference from the DVDC. When the DVDC receive, from the at least one of the plurality of VDCs, a request to access the configuration data via the reference, the DVDC transmits at least a portion of the configuration data to the at least one of the plurality of VDCs. The at least the portion of the configuration data is operable to initiate a connection between the at least one of the plurality of VDCs and the network resource.
Abstract:
An example method for zero touch configuration and synchronization of a service appliance in a network environment includes receiving, at an appliance port on a service appliance, an indication that a switch port on a switch changed from an inactive status to an active status, the appliance port being connected over a network to the switch port, starting a bootstrap protocol, including by receiving at the service appliance from the switch, a bootstrap message from a service executing in the switch, creating, by the service appliance, an empty port channel at the service appliance, adding, by the service appliance, the appliance port to the port channel, and associating, by the service appliance, the service to the port channel in a cache.
Abstract:
In an example, a network switch is configured to natively act as a high-speed load balancer. Numerous load-balancing techniques may be used, including one that bases the traffic “bucket” on a source IP address of an incoming packet. This particular technique provides a network administrator a powerful tool for shaping network traffic. For example, by assigning certain classes of computers on the network particular IP addresses, the network administrator can ensure that the traffic is load balanced in a desirable fashion. To further increase flexibility, the network administrator may apply a bit mask to the IP address, and expose only a portion, selected from a desired octet of the address.
Abstract:
In one embodiment, load balancing criteria and an indication of a plurality of network nodes is received. A plurality of forwarding entries are created based on the load balancing criteria and the indication of the plurality of nodes. A content addressable memory of a network element is programmed with the plurality of forwarding entries. The network element selectively load balances network traffic by applying the plurality of forwarding entries to the network traffic, wherein network traffic meeting the load balancing criteria is load balanced among the plurality of network nodes.
Abstract:
Systems, methods, and computer-readable media for creating service chains for inter-cloud traffic. In some examples, a system receives domain name system (DNS) queries associated with cloud domains and collects DNS information associated the cloud domains. The system spoofs DNS entries defining a subset of IPs for each cloud domain. Based on the spoofed DNS entries, the system creates IP-to-domain mappings associating each cloud domain with a respective IP from the subset of IPs. Based on the IP-to-domain mappings, the system programs different service chains for traffic between a private network and respective cloud domains. The system routes, through the respective service chain, traffic having a source associated with the private network and a destination matching the IP in the respective IP-to-domain mapping.