Abstract: A network element modifying the DHCP lease timer is described. According to one embodiment, an exemplary method includes maintaining, at a network element, DHCP lease time for one or more clients and in response to a DHCP renewal request from a client, on behalf of a DHCP server, providing DHCP renewal services to the client based on lease time information associated with the client without invoking the DHCP server.

Abstract: Methods and apparatuses for process a crossconnect switchover in a network element are described. According to one embodiment, an exemplary method includes synchronizing state information regarding broadband subscriber sessions of one or more circuits of a network element between one or more hub devices of an active control card and a standby control card of the network element, and in response to a crossconnect switchover, starting up one or more sessions associated with the one or more hub devices of the standby control card using the synchronized information, such that the one or more sessions are started up as if they are restarted. Other methods and apparatuses are also described.

Abstract: A network element modifying the DHCP lease timer is described. According to one embodiment, an exemplary method includes maintaining, at a network element, DHCP lease time for one or more clients and in response to a DHCP renewal request from a client, on behalf of a DHCP server, providing DHCP renewal services to the client based on lease time information associated with the client without invoking the DHCP server.

Abstract: A network element modifying the DHCP lease timer is described. According to one embodiment, an exemplary method includes maintaining, at a network element, DHCP lease time for one or more clients and in response to a DHCP renewal request from a client, on behalf of a DHCP server, providing DHCP renewal services to the client based on lease time information associated with the client without invoking the DHCP server.

Abstract: The use of IP address blocks with default interfaces in a router is described herein. According to one embodiment, an exemplary method includes in response to a request for a first IP address received from a first client at an interface of the network element, assigning the first client an IP address from a first block of IP addresses dynamically allocated from an IP address provider separated from a pool of statically preassigned IP addresses, if there is no IP address remained unassigned in the pool of statically preassigned IP addresses, and advertising reachability information in a network with respect to the first block of the IP addresses dynamically allocated from the IP address provider, such that other entities of the network are aware of the first block of the IP addresses. Other methods and apparatuses are also described.

Abstract: A method and apparatus for performing per-port Internet Protocol (IP) multicast pruning, proxying of IP multicast group membership reports, and generating pseudo membership queries for determining IP multicast group membership are provided. A switch may implement per-port IP multicast pruning by establishing a mapping of IP multicast groups to its ports. The mapping is based upon membership reports received from each end-station participating in an IP multicast group. Based upon the mapping, the switch forwards IP multicast packets only to those of the end-stations that are participating in the IP multicast group addressed. Once per-port IP multicast pruning is implemented, multicast routers must process membership reports from all end-stations participating in an IP multicast group. To reduce this burden, a switch may act as a proxy device. The switch receives a membership report identifying an IP multicast group.

Abstract: A method and apparatus for reducing the amount of control plane processing and flow detection required in a Multiprotocol Over ATM (MPOA) system are provided. According to one aspect of the present invention, flow detection processing may be altered based upon a packet's content. A first MPOA client (MPC) may include a plurality of flow detection mechanisms including standard MPOA processing and modified flow detection processing. For example, a flow may be determined to exist when the number of packets to a particular destination within a predetermined time interval exceeds a threshold value. Alternatively, a flow may be determined to exist immediately for certain types of traffic and detection of a flow may be suppressed for other types of traffic. Upon receipt at a first MPC, traffic may be classified based upon any information contained within a packet, including the header, the payload, or portions and/or combinations thereof.