Abstract: Presented herein are techniques to receive configuration instructions for elements of a network topology to be simulated and tested. In response to receiving and in accordance with the configuration instructions, a plurality of software images (for a plurality of virtual network elements of the network topology) are configured via an Application Programming Interface (API). The plurality of software images run in a cloud host. In response to receiving and in accordance with the configuration instructions, data is configured via the API, which represents one or more connections between the virtual network elements. A plurality of software images for the plurality of virtual network elements is then executed in accordance with the data representing the connections, for development and testing of the network topology.

Abstract: Presented herein are techniques to receive configuration instructions for elements of a network topology to be simulated and tested. In response to receiving and in accordance with the configuration instructions, a plurality of software images (for a plurality of virtual network elements of the network topology) are configured via an Application Programming Interface (API). The plurality of software images run in a cloud host. In response to receiving and in accordance with the configuration instructions, data is configured via the API, which represents one or more connections between the virtual network elements. A plurality of software images for the plurality of virtual network elements is then executed in accordance with the data representing the connections, for development and testing of the network topology.

Abstract: Presented herein are techniques to receive configuration instructions for elements of a network topology to be simulated and tested. In response to receiving and in accordance with the configuration instructions, a plurality of software images (for a plurality of virtual network elements of the network topology) are configured via an Application Programming Interface (API). The plurality of software images run in a cloud host. In response to receiving and in accordance with the configuration instructions, data is configured via the API, which represents one or more connections between the virtual network elements. A plurality of software images for the plurality of virtual network elements is then executed in accordance with the data representing the connections, for development and testing of the network topology.

Abstract: A method is provided in one example embodiment and includes determining a location of a location detection device using a wireless link; determining an identity of a fixed port to which the location detection device is connected, where the location of the location detection device is proximate to the fixed port; and communicating a location of the fixed port to a location anchor. In more specific examples, the location of the fixed port is linked to a point of attachment in order to configure the fixed port. Additionally, the location of the fixed port can be presented to a server for application to a point of attachment via an application program interface (API).

Abstract: Techniques are provided for delegating authority over licenses to use computer products in a disconnected network. In one example, a collector device receives a delegation of authority from a license manager device to manage entitlements for a plurality of computer products installed in a network infrastructure. The collector device receives an identifier from each computer product. The collector device receives a configuration state of each computer product, wherein each configuration state includes a set of features that are enabled on the first computer product. The collector device sends to the license manager device a report that includes each identifier and each configuration state.

Abstract: Presented herein are techniques to receive configuration instructions for elements of a network topology to be simulated and tested. In response to receiving and in accordance with the configuration instructions, a plurality of software images (for a plurality of virtual network elements of the network topology) are configured via an Application Programming Interface (API). The plurality of software images run in a cloud host. In response to receiving and in accordance with the configuration instructions, data is configured via the API, which represents one or more connections between the virtual network elements. A plurality of software images for the plurality of virtual network elements is then executed in accordance with the data representing the connections, for development and testing of the network topology.

Abstract: Techniques are provided for auditing and managing licenses for use of computer products. A license manager of a vendor receives an identifier of a computer product and a report of a set of licensed features enabled on the computer product. The license manager identifies a customer account associated with the identifier. The customer account includes a pool of entitlements acquired by the customer. The license manager compares the report with the entitlements in the pool, and with the customer's use of other computer products which draw entitlements from that pool, to generate a comparison result. An authorization decision of “in compliance” or “out of compliance” may be returned to the requesting computer product.

Abstract: Techniques are provided for delegating authority over licenses to use computer products in a disconnected network. In one example, a collector device receives a delegation of authority from a license manager device to manage entitlements for a plurality of computer products installed in a network infrastructure. The collector device receives an identifier from each computer product. The collector device receives a configuration state of each computer product, wherein each configuration state includes a set of features that are enabled on the first computer product. The collector device sends to the license manager device a report that includes each identifier and each configuration state.

Abstract: A method is provided in one example embodiment and includes determining a location of a location detection device using a wireless link; determining an identity of a fixed port to which the location detection device is connected, where the location of the location detection device is proximate to the fixed port; and communicating a location of the fixed port to a location anchor. In more specific examples, the location of the fixed port is linked to a point of attachment in order to configure the fixed port. Additionally, the location of the fixed port can be presented to a server for application to a point of attachment via an application program interface (API).

Abstract: An improved technique for processing a DHCP request from a DHCP client device is performed in a data communications device of a network (e.g., performed in a router). The technique involves receiving the DHCP request from the DHCP client device, evaluating a set of rules in response to the DHCP request to obtain a rule-based classification result, and outputting a DHCP response in response to the rule-based classification result. In some arrangements, a policy manager which is external to the data communications device plays a role in the classification process (e.g., dynamic updating of the set of rules, responding to individual queries from the data communications device when generating the rule-based classification result, etc.). Such improvements over conventional DHCP approaches enables improved flexibility and coordination of the DHCP process.

Abstract: Techniques for providing remote access to a service provider network include exchanging multiple Dynamic Host Configuration Protocol (DHCP) formatted messages instead of any Point to Point Protocol (PPP) message to provide all PPP functions for accessing a service provider network from a customer node. The service provider network is on provider premises and the customer node is on customer premises different from the provider premises. The DHCP format is used to exchange authentication messages, user profile data on Authentication, Authorization and Accounting (AAA) servers, or session keep-alive echo messages, alone or in some combination. When all are message types are combined, these techniques provide a remote access server (RAS) with the capability to perform all functions presently provided by PPP processes. In some combinations, these techniques allow a modified DHCP server to replace a legacy AAA server.

Abstract: Techniques for supporting subscriber sessions for access to an IP network include receiving from a first node at a different second node, a Dynamic Host Configuration Protocol (DHCP) formatted echo-request message. The echo-request message includes a DHCP option field that holds data that indicates an echo-request type. In response to receiving the echo-request message, the second node sends to the first node a DHCP formatted echo-reply message that corresponds to the echo-request message. The echo-reply message includes a DHCP option field that holds data that indicates an echo-reply type. When received by the first node, the echo-response message causes the first node to determine a connected state with the second node. Point to Point Protocol (PPP) keep-alive messages between a customer premises node and a remote access server gateway to an IP network may be replaced by these DHCP echo-request and echo-reply messages.

Abstract: Techniques for providing remote access to a service provider network include exchanging multiple Dynamic Host Configuration Protocol (DHCP) formatted messages instead of any Point to Point Protocol (PPP) message to provide all PPP functions for accessing a service provider network from a customer node. The service provider network is on provider premises and the customer node is on customer premises different from the provider premises. The DHCP format is used to exchange authentication messages, user profile data on Authentication, Authorization and Accounting (AAA) servers, or session keep-alive echo messages, alone or in some combination. When all are message types are combined, these techniques provide a remote access server (RAS) with the capability to perform all functions presently provided by PPP processes. In some combinations, these techniques allow a modified DHCP server to replace a legacy AAA server.

Abstract: Techniques for supporting subscriber sessions for access to an IP network include receiving from a first node at a different second node, a Dynamic Host Configuration Protocol (DHCP) formatted echo-request message. The echo-request message includes a DHCP option field that holds data that indicates an echo-request type. In response to receiving the echo-request message, the second node sends to the first node a DHCP formatted echo-reply message that corresponds to the echo-request message. The echo-reply message includes a DHCP option field that holds data that indicates an echo-reply type. When received by the first node, the echo-response message causes the first node to determine a connected state with the second node. Point to Point Protocol (PPP) keep-alive messages between a customer premises node and a remote access server gateway to an IP network may be replaced by these DHCP echo-request and echo-reply messages.

Abstract: A provider edge (PE) device provides subscribers with access to an Internet Service Provider (ISP) network. The subscribers are connected to the PE device via a broadband aggregation device. The PE device includes a processor operable to snoop control plane traffic for a logical identifier that allows subscriber traffic having varying data plane information to be treated as a session group. The processor is further operable to instantiate the session group based on the logical identifier. A unit of the PE device applies a QOS policy to traffic flow associated with the session group. It is emphasized that this abstract is provided to comply with the rules requiring an abstract that will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. 37 CFR 1.72(b).

Abstract: An improved technique for processing a DHCP request from a DHCP client device is performed in a data communications device of a network (e.g., performed in a router). The technique involves receiving the DHCP request from the DHCP client device, evaluating a set of rules in response to the DHCP request to obtain a rule-based classification result, and outputting a DHCP response in response to the rule-based classification result. In some arrangements, a policy manager which is external to the data communications device plays a role in the classification process (e.g., dynamic updating of the set of rules, responding to individual queries from the data communications device when generating the rule-based classification result, etc.). Such improvements over conventional DHCP approaches enables improved flexibility and coordination of the DHCP process.