Abstract:
A VLAN is implemented with a logical hub and spoke topology that obviates local switching. Member devices are connected to a hub device such as a router via intermediate devices such as Layer 2 switches that support individual IP subnets within the VLAN. The Layer 2 switch does not allow bridging, so there is no IP subnet broadcast domain. Further, the Layer 2 switch implements only a single logical broadcast uplink port which is connected to the router. The Layer 2 switch also implements only point-to-point downlink ports, i.e., to individual member devices. Consequently, all traffic is forced to flow through the router, e.g., broadcast traffic, multicast traffic and traffic of unknown destination received by the Layer 2 switch from a member device is only flooded to the router, and the router performs intra-subnet routing in addition to routing between subnets and between VLANs. The router subjects all traffic to security measures and provide services including packet inspection, firewall, policing, metering, accounting, anti-virus, marking, filtering and encryption, and thereby reduce or eliminate the drawbacks associated with local switching.
Abstract:
A distributed device architecture includes a master device and one or more member devices. A simple network management protocol (SNMP) agent of a master device receives an SNMP request from a managing device. Where the SNMP request pertains to a given member device, and where the SNMP request requires involvement of the given member device to fulfill the SNMP request, the master device generates a non-SNMP request corresponding to the SNMP request and transmits the non-SNMP request to the given member device. A non-SNMP agent of the given member device processes the non-SNMP request and transmits processing results back to the master device. The master device generates an SNMP response corresponding to the processing results, and the SNMP agent of the master device transmits the SNMP response back to the managing device.
Abstract:
A switch of a data network implements both a bridge and a virtual bridge. In response to receipt of a data frame by the switch from an external link, the switch performs a lookup in a data structure using a source media access control (SMAC) address specified by the data frame. The switch determines if the external link is configured in a link aggregation group (LAG) and if the SMAC address is newly learned. In response to a determination that the external link is configured in a LAG and the SMAC address is newly learned, the switch associates the SMAC with the virtual bridge and communicates the association to a plurality of bridges in the data network.
Abstract:
A diagnostic system provides identification of symptoms in a distributed network and an engine for providing recommended rectification of error sources that correspond to the symptoms. The distributed network may be accessed for current statistics. Symptoms may be identified that correspond to the current statistics. A recommended course of action for the distributed network may be provided based on a predetermined list of courses of actions that correspond to rectifying the performance in the error sources.
Abstract:
A distributed device architecture includes a master device and one or more member devices. A simple network management protocol (SNMP) agent of a master device receives an SNMP request from a managing device. Where the SNMP request pertains to a given member device, and where the SNMP request requires involvement of the given member device to fulfill the SNMP request, the master device generates a non-SNMP request corresponding to the SNMP request and transmits the non-SNMP request to the given member device. A non-SNMP agent of the given member device processes the non-SNMP request and transmits processing results back to the master device. The master device generates an SNMP response corresponding to the processing results, and the SNMP agent of the master device transmits the SNMP response back to the managing device.
Abstract:
In a switching network, each of a plurality of lower tier entities is coupled to each of multiple master switches at an upper tier by a respective one of multiple links. At each of the multiple master switches, a plurality of virtual ports each corresponding to a respective one of a plurality of remote physical interfaces (RPIs) at the lower tier are implemented on each of a plurality of ports. Each of the plurality of lower tier entities implements a respective egress port mapping indicating which of its plurality of RPIs transmits egress data traffic through each of its multiple links to the multiple master switches. In response to failure of one of the multiple links coupling a particular lower tier entity to a particular master switch, the particular lower tier entity updates its egress port mapping to redirect egress data traffic to another of the multiple master switches without packet dropping.
Abstract:
A switching network has a plurality of switches including at least a switch and a managing master switch. At the managing master switch, a first capability vector (CV) is received from the switch. The managing master switch determines whether the first CV is compatible with at least a second CV in a network membership data structure that records CVs of multiple switches in the switching network. In response to detecting an incompatibility, the managing master switch initiates an image update to an image of the switch. In response to a failure of the image update at the switch, the switch boots utilizing a mini-DC module that reestablishes communication between the switch with the managing master switch and retries the image update.
Abstract:
A switching network includes an upper tier having a master switch and a lower tier including a plurality of lower tier entities. The master switch, which has a plurality of ports each coupled to a respective lower tier entity, implements on each of the ports a plurality of virtual ports each corresponding to a respective one of a plurality of remote physical interfaces (RPIs) at the lower tier entity coupled to that port. Data traffic communicated between the master switch and RPIs is queued within virtual ports that correspond to the RPIs with which the data traffic is communicated. The master switch applies data handling to the data traffic in accordance with a control policy based at least upon the virtual port in which the data traffic is queued, such that the master switch applies different policies to data traffic queued to two virtual ports on the same port of the master switch.
Abstract:
A switching network includes an upper tier having a master switch and a lower tier including a plurality of lower tier entities. The master switch, which has a plurality of ports each coupled to a respective lower tier entity, implements on each of the ports a plurality of virtual ports each corresponding to a respective one of a plurality of remote physical interfaces (RPIs) at the lower tier entity coupled to that port. Data traffic communicated between the master switch and RPIs is queued within virtual ports that correspond to the RPIs with which the data traffic is communicated. The master switch applies data handling to the data traffic in accordance with a control policy based at least upon the virtual port in which the data traffic is queued, such that the master switch applies different policies to data traffic queued to two virtual ports on the same port of the master switch.
Abstract:
A VLAN is implemented with a logical hub and spoke topology that obviates local switching. Member devices are connected to a hub device such as a router via intermediate devices such as Layer 2 switches that support individual IP subnets within the VLAN. The Layer 2 switch does not allow bridging, so there is no IP subnet broadcast domain. Further, the Layer 2 switch implements only a single logical broadcast uplink port which is connected to the router. The Layer 2 switch also implements only point-to-point downlink ports, i.e., to individual member devices. Consequently, all traffic is forced to flow through the router, e.g., broadcast traffic, multicast traffic and traffic of unknown destination received by the Layer 2 switch from a member device is only flooded to the router, and the router performs intra-subnet routing in addition to routing between subnets and between VLANs. The router subjects all traffic to security measures and provide services including packet inspection, firewall, policing, metering, accounting, anti-virus, marking, filtering and encryption, and thereby reduce or eliminate the drawbacks associated with local switching.