Abstract: Providing network access is disclosed. Use of a provider equipment port via which network access is provided to two or more downstream nodes, each having one or more classes of network traffic associated with it, is scheduled on a per class basis, across the downstream nodes. The respective network traffic sent to each of at least a subset of the two or more downstream nodes is limited, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.

Abstract: Providing gateway redundancy is disclosed. On each of a master and a standby gateway a single IP routing redundancy protocol instance is associated with a plurality of subscriber subnets. On each gateway, the respective single IP routing redundancy protocol instance is used to provide gateway redundancy for the plurality of subscriber subnets.

Abstract: Providing network access is disclosed. Use of a provider equipment port via which network access is provided to two or more downstream nodes, each having one or more classes of network traffic associated with it, is scheduled on a per class basis, across the downstream nodes. The respective network traffic sent to each of at least a subset of the two or more downstream nodes is limited, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.

Abstract: Providing network access is disclosed. Use of a provider equipment port via which network access is provided to two or more downstream nodes, each having one or more classes of network traffic associated with it, is scheduled on a per class basis, across the downstream nodes. The respective network traffic sent to each of at least a subset of the two or more downstream nodes is limited, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.

Abstract: Providing gateway redundancy is disclosed. On each of a master and a standby gateway a single IP routing redundancy protocol instance is associated with a plurality of subscriber subnets. On each gateway, the respective single IP routing redundancy protocol instance is used to provide gateway redundancy for the plurality of subscriber subnets.

Abstract: Providing gateway redundancy is disclosed. On each of a master and a standby gateway a single IP routing redundancy protocol instance is associated with a plurality of subscriber subnets. On each gateway, the respective single IP routing redundancy protocol instance is used to provide gateway redundancy for the plurality of subscriber subnets.

Abstract: Associating hosts with subscriber and service based requirements is disclosed. An identifier is extracted from a DHCP or other network address lease communication associated with a subscriber host. The identifier is used to associate the subscriber host with a requirement that is subscriber based, service based, or both subscriber and service based. The subscriber host is included in a set of one or more subscriber hosts associated with the subscriber, the service, or both, as applicable to the requirement, and the requirement is required to be enforced collectively to the one or more subscriber hosts comprising the set.

Abstract: Providing network access is disclosed. Use of a provider equipment port via which network access is provided to two or more downstream nodes, each having one or more classes of network traffic associated with it, is scheduled on a per class basis, across the downstream nodes. The respective network traffic sent to each of at least a subset of the two or more downstream nodes is limited, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.

Abstract: Providing network access is disclosed. Use of a provider equipment port via which network access is provided to two or more downstream nodes, each having one or more classes of network traffic associated with it, is scheduled on a per class basis, across the downstream nodes. The respective network traffic sent to each of at least a subset of the two or more downstream nodes is limited, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.

Abstract: Managing subscriber host information is disclosed. A new or updated information about a subscriber host is received. It is determined whether the subscriber host is associated with a multi-chassis peering. If it is determined that the subscriber host is associated with a multi-chassis peering, the new or updated information is propagated to a peer chassis associated with the multi-chassis peering.

Abstract: Verifying subscriber host connectivity is disclosed. In some embodiments, a unicast address resolution protocol (ARP) request is sent to a subscriber host, and based at least in part on whether a response to the request is received from the subscriber host, it is determined whether the subscriber host remains connected to a network.

Abstract: Managing a network resource is disclosed. An indication that a resource assigned to a subscriber host by a resource allocating node is no longer to be used by the subscriber host is received at a node other than the subscriber host or the resource allocating node. A resource release communication is sent to the resource allocating node from said node other than the subscriber host or the resource allocating node. The resource release communication appears to the resource allocating node to originate from the subscriber host and indicates to the resource allocating node that the resource is no longer to be used by the subscriber host.

Abstract: Ethernet VLL spoke termination at an IP interface is disclosed. A packet including an address associated with a remote host is received at an interface. A routing next hop information required to route the packet to the remote host at a far end of a pseudo-wire via which connectivity to the remote host is provided and an intermediate next hop information required to send the packet to the far end via the pseudo-wire are determined in a single forwarding stage, based at least in part on the interface and the address.

Abstract: Aggregating links across multiple chassis is disclosed. An indication that one or more local links are to be aggregated with one or more links on another chassis is received. Coordination with the other chassis is performed, via an inter-chassis control path, to present to a downstream equipment as an aggregated group of links the one or more local links and the one or more links on the other chassis.

Abstract: Providing gateway redundancy is disclosed. On each of a master and a standby gateway a single IP routing redundancy protocol instance is associated with a plurality of subscriber subnets. On each gateway, the respective single IP routing redundancy protocol instance is used to provide gateway redundancy for the plurality of subscriber subnets.

Abstract: Managing subscriber host information is disclosed. A new or updated information about a subscriber host is received. It is determined whether the subscriber host is associated with a multi-chassis peering. If it is determined that the subscriber host is associated with a multi-chassis peering, the new or updated information is propagated to a peer chassis associated with the multi-chassis peering.

Abstract: A multilink trunk from a client device in a communication network is split between two aggregation devices such that each aggregation device is connected to at least one link of the multilink trunk. The aggregation devices work in conjunction to appear to the client device as a single device connected to the client device over the multilink trunk. The aggregation devices transmit identical bridge protocol data units to the client device over their respective links of the multilink trunk. The aggregation devices exchange operational information and data packets over inter-device communication ports. A failure of the split multilink trunk at one aggregation device is restored through the other aggregation device.

Abstract: A method and apparatus for providing a Virtual Private Network (VPN) over a connectionless network connecting a plurality of Local Area Networks (LANs), such as an Ethernet network, is disclosed. The method and apparatus comprises associated each VPN with a unique identifier and each LAN of the VPN with a interface device connecting the LAN to the connectionless network, which may be for example, a Synchronous Optical Network (SONET). The interface device may service a plurality of LANs. Accordingly, each LAN is associated with a User-Network Interface that forms part of the interface device. Each data packet destined for a second LAN, such Ethernet frames, received by the interface device for a first LAN is encapsulated with, if known, a Media Access Control (MAC) address of the interface device connected to the second LAN, the VPN's unique identifier, and the port on the interface device connected to the second LAN.

Abstract: A multilink trunk from a client device in a communication network is split between two aggregation devices such that each aggregation device is connected to at least one link of the multilink trunk. The aggregation devices work in conjunction to appear to the client device as a single device connected to the client device over the multilink trunk. The aggregation devices transmit identical bridge protocol data units to the client device over their respective links of the multilink trunk. The aggregation devices exchange operational information and data packets over inter-device communication ports. A failure of the split multilink trunk at one aggregation device is restored through the other aggregation device.