Cisco Technology, Inc.

William Beebee

Hemant Singh

Madhu Sudan

Chad Mikkelson

Ralph Droms

Ole Troan

Tong Liu

Joshua B Littlefield

Pawel Piotr Sowinski

Yie-Fong Dan

Bernard Ernst Volz

In one embodiment, methods are described for recovering lost customer premises equipment (CPE) information on a cable modem termination system (CMTS) in the presence of only Dynamic Host Control Protocol Version 6 (DHCPv6) CONFIRM. A CMTS purges routing information for an Internet Protocol Version 6 (IPv6) node, such as a CPE router, in response to detecting an interface reset for the IPv6 node. IPv6 addresses and prefixes information for the IPv6 node is gleaned from a DHCPv6 CONFIRM message received from the IPv6 node. By sending portions of the IPv6 addresses and prefixes information within a DHCPv6 LEASEQUERY message, a DHCPv6 CONFIRM message with an embedded DHCPv6 LEASEQUERY message, or a DHCPv6 CONFIRM message with an Interface-ID option, a reply message can be received that contains the purged routing information for the IPv6 node.

Recovering lost device information in cable networks

A method is provided in one example and includes determining that an access concentrator has lost customer premise equipment information. The method also includes obtaining the customer premise equipment information that is lost by evaluating Neighbor Discovery data and dynamic host configuration protocol version six (DHCPv6) query data. In more specific implementations, the method may include communicating a Bulk Leasequery message; receiving a response to the Bulk Leasequery message; and filtering out cable modem identifiers from the response to the Bulk Leasequery message.

System and method for recovery of customer premise equipment information on an access concentrator

A network processing device is configured to receive a configuration message from a host device and forward the configuration message to a server. The configuration message can be configured to request the server assign an Internet Protocol (IP) address to the host device. The network processing device can be configured to send at least one probe message to the host device responsive to receiving the configuration message. The network processing device can be configured to determine whether the host device intends to continue utilizing a previously assigned IP address in addition to the IP address requested by the configuration message based, at least in part, on any responses to the at least one probe message received from the host device.

Detection and support of a dual-stack capable host

Techniques for automatically identifying an edge-facing router in a network are provided. In one technique, a DHCP message is obtained at a router of a subscriber network. An options field of the DHCP message is identified. The options field of the DHCP message is analyzed to determine whether data in the options field indicates that first router is SP-facing. If it is determined that the router is an SP-facing router, then identification data that identifies the router as an SP-facing router is stored.

Automatically identifying an edge-facing router

Techniques are provided herein for receiving synchronization messages at a second network device that is in a hot standby configuration from a first network device that is maintaining Internet Protocol version 6 (IPv6) state machines for one or more neighbor devices. The synchronization messages are configured to indicate an IPv6 state for each state machine maintained in the first network device. An IPv6 state for corresponding state machines is updated in the second network device based on the synchronization messages such that the IPv6 states in the second network device allows the second network device to actively process IPv6 traffic for the one or more neighbor devices upon traffic switchover from the first network device to the second network device without restarting the corresponding IPv6 state machine associated with each of the one or more neighbor devices in the second network device. The roles of the first and second device with respect to active and standby state are reversed after a switchover.

Hot standby neighbor discovery protocol for internet protocol version 6

A system includes a forwarding engine to schedule when replicas of a received multicast packet are forwarded towards one or more multicast recipients. The system also includes an egress interface device to replicate the multicast packet and forward the multicast packet replica towards the one or more multicast recipients when prompted by the forwarding engine based on the scheduling.

Distributed multicast packet replication with centralized quality of service

Techniques for automatically identifying an edge-facing router in a network are provided. In one technique, data is obtained at a first router of a subscriber network. The data may be included in a DHCP message or a NDP RA message. The first router determines, based on the data, whether the first router is a service provider (SP)-facing router, which is a router that is coupled to a SP router and no other router in the subscriber network is logically between the SP-facing router and the SP router. If it is determined that the first router is an SP-facing router, then the first router stores identification data that identifies the first router as an SP-facing router. Otherwise, the first router stores identification data that identifies the first router as a non-SP-facing router.

A network device is to receive traffic including neighbor discovery messages from requesting customer devices, and can detect the neighbor discovery messages within the traffic according to a distributed inspection scheme that includes the network device and a remote component. The network device is to then examine the neighbor discovery messages to determine if the neighbor discovery message should be forwarded to other of the customer devices, and respond to the requesting customer devices.

Growing community of inventors

Lowell, MA, United States of America

William Beebee