Abstract: A tool for packet transmission and delivery in a distributed system. The tool determines one or more packets is classified as a L3 packet. The tool determines translation of the one or more packets classified as L3 packets to one or more corresponding net devices. The tool sends the one or more packets classified as a non L3 packet to a user space packet dispatcher service.

Abstract: A business rule framework may be used to provide a vendor agnostic interface to allow one or more business users to design, deploy, test and/or monitor an operation of one or more business rules using a common user interface. The business rule framework may allow a user access to a business rule management system (BRMS) using a common interface, regardless of a vendor or version of BRMS being used by a business organization. The business rule framework may include a business rule governance interface allowing the business user with the common user interface to the BRMS, regardless of the version or vendor of the BRMS product being used. The business rule framework may also include a BRMS interface capable of communicating with different BRMS products.

Abstract: In one embodiment, a method for providing virtual link aggregation (vLAG) in a transparent interconnection of lots of links (TRILL)-enabled network, includes creating a virtual routing bridge logically connected to a first physical routing bridge and a second physical routing bridge to form a vLAG group at an edge of the TRILL-enabled network; determining a first distribution tree linking the first physical routing bridge to every other routing bridge in the TRILL-enabled network in a non-repeating fashion, ending with the second physical routing bridge; determining a second distribution tree linking the second physical routing bridge to every other routing bridge in the TRILL-enabled network in a non-repeating fashion, ending with the first physical routing bridge; receiving a multicast packet at the virtual routing bridge from one of the physical routing bridges; and distributing the multicast packet according to either the first or the second distribution tree thereby preventing looping.

Abstract: A tool for forwarding plane support in a distributed system. The tool receives, by one or more computer processors, one or more messages. The tool determines, by one or more computer processors, a distribution scope for the one or more messages. The tool determines, by one or more computer processors, a destination endpoint ID for the one or more messages. The tool sends, by one or more computer processors, the one or more messages to one or more forwarding plane agents.

Abstract: A networking system, and more particularly an interface management subsystem, offers logical interface abstraction for networking system software. The networking system generally transmits data via a hardware interface. All software components in the control and forwarding plane use a Logical Interface (LIF) that is a logical representation of the hardware interface. A mapping occurs between the LIF and hardware interface used to transmit the data. Each LIF is represented by an LIF identifier used to store and retrieve logical interface records to and from shared memory accessible to all protocols and applications in the control and forwarding plane. The efficient storage and retrieval of such logical interface records allows for a global unique view of network interfaces, avoidance of data replication in each networking system software application's memory space, etc.

Abstract: A tool for packet transmission and delivery in a distributed system. The tool determines one or more packets is classified as a L3 packet. The tool determines translation of the one or more packets classified as L3 packets to one or more corresponding net devices. The tool sends the one or more packets classified as a non L3 packet to a user space packet dispatcher service.

Abstract: A tool for assigning virtual port channels to one or more logical switch routers in a distributed system. The tool receives, by one or more computer processors, a request to assign a virtual port channel to a second logical switch router. The tool sends, by one or more computer processors, a request to negotiate a link-down on the channel on a first logical switch router to a universal fiber port on the first logical switch router for processing. The tool sends, by one or more computer processors, a request to create the channel on the second logical switch router to a second interface manager on the second logical switch router for processing. The tool sends, by one or more computer processors, a request to negotiate a link up on the channel on the second logical switch router to the universal fiber port on the first logical switch router for processing.

Abstract: A tool for partitioning a switch into one or more logical switches in a distributed system. The tool creates, by one or more computer processors, one or more logical switch routers, based, at least in part, on a user configuration. The tool assigns, by one or more computer processors, based, at least in part, on a user configuration, one or more ports to the one or more logical switch routers. The tool manages, by one or more computer processors, the one or more logical switch routers.

Abstract: In one embodiment, a system includes a TRILL-enabled network that includes a first physical routing bridge (RB) and a second physical RB, logic adapted for creating a virtual RB logically connected to the first and second physical RBs to form a vLAG group at an edge of the network, logic adapted for determining a first distribution tree linking the first physical RB to every other RB in the network in a non-repeating fashion, ending with the second physical RB, and logic adapted for determining a second distribution tree linking the second physical RB to every other RB in the network in a non-repeating fashion, ending with the first physical RB, wherein when a multicast packet is received by the virtual RB from one of the physical RBs, the multicast packet is distributed according to either the first or the second distribution tree thereby preventing looping.

Abstract: A method and system for static routing in a TRILL network is disclosed. Routing bridges in the TRILL network use LLDP discovery to identify their next hop routing bridges. A data packet, with an inner header specifying a MAC address of a destination host, is sent by a source host and received by an ingress routing bridge. The ingress routing bridge encapsulates the data packet with a TRILL header and an outer header and sends the data packet to a next hop routing bridge on path to the destination host. The next hop routing bridge determines it is not the egress routing bridge for the data packet and sends the data packet onward to the egress routing bridge. The egress routing bridge decapsulates the data packet and forwards the data packet to the destination host specified in the inner header.

Abstract: A method for maintaining a bridging network communication path table is presented and includes determining a failed communication link between a first bridge computer and a second bridge computer in the bridging network; identifying, in the communication path table, a first path that includes the failed communication link; and indicating that the first path is not active.

Abstract: In one embodiment, a method for providing virtual link aggregation (vLAG) in a transparent interconnection of lots of links (TRILL)-enabled network, includes creating a virtual routing bridge logically connected to a first physical routing bridge and a second physical routing bridge to form a vLAG group at an edge of the TRILL-enabled network; determining a first distribution tree linking the first physical routing bridge to every other routing bridge in the TRILL-enabled network in a non-repeating fashion, ending with the second physical routing bridge; determining a second distribution tree linking the second physical routing bridge to every other routing bridge in the TRILL-enabled network in a non-repeating fashion, ending with the first physical routing bridge; receiving a multicast packet at the virtual routing bridge from one of the physical routing bridges; and distributing the multicast packet according to either the first or the second distribution tree thereby preventing looping.

Abstract: In one embodiment, a system includes a TRILL-enabled network that includes a first physical routing bridge (RB) and a second physical RB, logic adapted for creating a virtual RB logically connected to the first and second physical RBs to form a vLAG group at an edge of the network, logic adapted for determining a first distribution tree linking the first physical RB to every other RB in the network in a non-repeating fashion, ending with the second physical RB, and logic adapted for determining a second distribution tree linking the second physical RB to every other RB in the network in a non-repeating fashion, ending with the first physical RB, wherein when a multicast packet is received by the virtual RB from one of the physical RBs, the multicast packet is distributed according to either the first or the second distribution tree thereby preventing looping.

Abstract: A method and system for static routing in a TRILL network is disclosed. Routing bridges in the TRILL network use LLDP discovery to identify their next hop routing bridges. A data packet, with an inner header specifying a MAC address of a destination host, is sent by a source host and received by an ingress routing bridge. The ingress routing bridge encapsulates the data packet with a TRILL header and an outer header and sends the data packet to a next hop routing bridge on path to the destination host. The next hop routing bridge determines it is not the egress routing bridge for the data packet and sends the data packet onward to the egress routing bridge. The egress routing bridge decapsulates the data packet and forwards the data packet to the destination host specified in the inner header.

Abstract: An optical cross connect with simultaneous correction of multiple mirror angles to achieve desired output power. In one embodiment beam offset and pointing angle are changed and output power is measured to determine changes to mirror angles.

Abstract: Portions of code containing critical code routines are identified and labeled, then compiled into Dynamic Link Libraries (“DLLs”) and linked such that the critical code routines are optimally loaded into a reserved address space in the DLL memory space. If supported, cache locking may be enabled for the reserved address space. The portions of source code containing portions of critical code for which execution performance is to be improved are labeled, and the source code is scanned prior to compilation to locate the labeled portions of critical code. A linker is configured to store all the labeled portions of critical code into an Executable and Linking Format (“ELF”) section header, which is relocated at run-time into a memory space reserved for the portions of critical code.

Abstract: An optical cross connect with simultaneous correction of multiple mirror angles to achieve desired output power. In one embodiment beam offset and pointing angle are changed and output power is measured to determine changes to mirror angles.

Abstract: A system including a method and apparatus are provided for controlling fault conditions in a computer controlled device such as a data communications device. The invention can preferably be provided in a process restarter mechanism within an operation system. In operation, the process restarter system detects improper execution (i.e., detects a processing failure) of a set of instructions and initiates execution of the set of instructions in response to the operation of detecting. The system then repeats the operation of detecting and initiating according to a first restart sequence and then repeats the operation of detecting and initiating according to a second restart sequence. The second restart sequence initiates execution of the set of instructions in a different sequence than the first restart sequence.