Abstract: An adjunct network device includes several ports, an uplink interface, and an adjunct forwarding engine coupled to the ports and the uplink interface. A first port is configured to receive a packet, which includes a destination address. The adjunct forwarding engine is configured to send the packet to the uplink interface if the destination address is not associated with any of the ports. The packet is sent to one of the ports if the destination address is associated with the one of the ports.

Abstract: A virtual network device includes several different virtual network device sub-units, which collectively operate as a single logical network device. An interface bundle includes interfaces in more than one of the different virtual network device sub-units included in the virtual network device. The interface bundle is coupled to a virtual link bundle, which connects the virtual network device to another device. The interface bundle is managed as a single logical interface.

Abstract: A blade router for increased interface scalability is provided. The blade router may address interface scalability by having each of the linecards manage its interfaces locally and may use the concept of virtual and local interfaces for intelligent forwarding. The blade router may appear as a single router from the customer perspective during configuration. For some embodiments, two virtual interfaces may be used, one for regular interface traffic and another for Network Address Translation (NAT)-enabled interface traffic.

Abstract: An adjunct network device includes several ports, an uplink interface, and an adjunct forwarding engine coupled to the ports and the uplink interface. A first port is configured to receive a packet, which includes a destination address. The adjunct forwarding engine is configured to send the packet to the uplink interface if the destination address is not associated with any of the ports. The packet is sent to one of the ports if the destination address is associated with the one of the ports.

Abstract: A blade switch for increased interface scalability is provided. The blade switch may address interface scalability by having each of the switch linecards manage its interfaces locally and may use the concept of virtual and local interfaces for intelligent forwarding. The blade switch may appear as a single network switch having a single bridge ID from the network perspective during operation and from the customer perspective during configuration.

Abstract: A an example method includes building a dictionary between an exporter and a collector by encoding a first data record of a flow according to a dictionary template and exporting the first data record to the collector via a network communication. The method can also include compressing a second data record of the flow using the dictionary, where the compressing comprises encoding the second data record according to an encoding template; and exporting the second data record to the collector to be decompressed using the dictionary.

Abstract: A method may involve: receiving a packet (e.g., via a port or uplink interface in a satellite switch) and conveying the packet between one or more ports and one of several uplink interfaces. The one or more ports and the uplink interface are associated with each other. The association can be independent of VLAN (Virtual Local Area Network). As an example, such a method can involve: receiving a first packet via a first port; conveying the first packet to a distribution-layer via a first uplink interface; receiving a second packet via a second port; and conveying the second packet to the distribution-layer via a second uplink interface, where the first uplink interface is associated with the first port and the second uplink interface is associated with the second port. In some embodiments, ports and uplink interfaces are associated by being assigned to the same virtual linecard.

Abstract: An adjunct network device includes several ports, an uplink interface, and an adjunct forwarding engine coupled to the ports and the uplink interface. A first port is configured to receive a packet, which includes a destination address. The adjunct forwarding engine is configured to send the packet to the uplink interface if the destination address is not associated with any of the ports. The packet is sent to one of the ports if the destination address is associated with the one of the ports.

Abstract: An adjunct network device includes several ports, an uplink interface, and an adjunct forwarding engine coupled to the ports and the uplink interface. A first port is configured to receive a packet, which includes a destination address. The adjunct forwarding engine is configured to send the packet to the uplink interface if the destination address is not associated with any of the ports. The packet is sent to one of the ports if the destination address is associated with the one of the ports.

Abstract: Method and system for providing access layer satellite architecture in a data network including receiving a data packet from an access layer network device, the data packet including a Virtual Local Area Network (VLAN) identifier associated with a port on the access layer network device, performing a route lookup procedure based on the received data packet to determine a destination of the data packet, updating an ARP table with a Media Access Control (MAC) address associated with the VLAN identifier and the port of the received data packet, and transmitting the data packet to a destination network device, is disclosed.

Abstract: Method and devices are provided to form virtual switches for data networks. As noted above, the term “switch” as used herein will apply to switches, routers and similar network devices. Each virtual switch acts as a single logical unit, while encompassing at least two physical chassis. Accordingly, each virtual switch may be treated as a single point of management. Each virtual switch includes a master chassis and at least one slave chassis. The master chassis is configured to control the slave chassis. The master chassis includes at least one master supervisor card and the slave chassis includes at least one slave supervisor card. The master chassis and the slave chassis communicate via a virtual switch link according to a virtual switch link protocol.

Abstract: A blade router for increased interface scalability is provided. The blade router may address interface scalability by having each of the linecards manage its interfaces locally and may use the concept of virtual and local interfaces for intelligent forwarding. The blade router may appear as a single router from the customer perspective during configuration. For some embodiments, two virtual interfaces may be used, one for regular interface traffic and another for Network Address Translation (NAT)-enabled interface traffic.

Abstract: A blade switch for increased interface scalability is provided. The blade switch may address interface scalability by having each of the switch linecards manage its interfaces locally and may use the concept of virtual and local interfaces for intelligent forwarding. The blade switch may appear as a single network switch having a single bridge ID from the network perspective during operation and from the customer perspective during configuration.

Abstract: Method and system for providing access layer satellite architecture in a data network including receiving a data packet from an access layer network device, the data packet including a Virtual Local Area Network (VLAN) identifier associated with a port on the access layer network device, performing a route lookup procedure based on the received data packet to determine a destination of the data packet, updating an ARP table with a Media Access Control (MAC) address associated with the VLAN identifier and the port of the received data packet, and transmitting the data packet to a destination network device, is disclosed.