Abstract: A network device may receive a timing control packet from a first client device. The network device may determine that the network device is in a synchronized state relative to a network grandmaster clock. The network device may modify a first field of a header of the timing control packet to indicate that the network device is in a synchronized state. The network device may modify a second field of the header of the timing control packet to indicate a time at which the network device received the timing control packet from the first client device. The network device may forward, via the network, the timing control packet toward a second client device.

Abstract: A network device may receive a timing control packet from a first client device. The network device may determine that the network device is in a synchronized state relative to a network grandmaster clock. The network device may modify a first field of a header of the timing control packet to indicate that the network device is in a synchronized state. The network device may modify a second field of the header of the timing control packet to indicate a time at which the network device received the timing control packet from the first client device. The network device may forward, via the network, the timing control packet toward a second client device.

Abstract: A network device may receive a timing control packet from a first client device. The network device may determine that the network device is in a synchronized state relative to a network grandmaster clock. The network device may modify a first field of a header of the timing control packet to indicate that the network device is in a synchronized state. The network device may modify a second field of the header of the timing control packet to indicate a time at which the network device received the timing control packet from the first client device. The network device may forward, via the network, the timing control packet toward a second client device.

Abstract: A network device may receive a timing control packet from a first client device. The network device may determine that the network device is in a synchronized state relative to a network grandmaster clock. The network device may modify a first field of a header of the timing control packet to indicate that the network device is in a synchronized state. The network device may modify a second field of the header of the timing control packet to indicate a time at which the network device received the timing control packet from the first client device. The network device may forward, via the network, the timing control packet toward a second client device.

Abstract: A device may include one or more processors. The device may receive an instruction identifying a set of objects to be generated by a kernel associated with the device. The kernel may generate the set of objects based on receiving information identifying a corresponding set of write operations. The device may provide a first message to cause the kernel to perform first operations corresponding to a first subset of objects of the set of objects. The device may receive one or more notifications indicating whether each operation, of the first operations, was successfully performed. The device may determine, based on whether each operation was successfully performed, a quantity of objects to include in a second subset of objects, of the set of objects. The device may provide a second message to cause the kernel to perform second operations corresponding to the second subset of objects.

Abstract: A network device may include a timing module and at least one interface. The timing module determines a local time of the network device indicating when the network device sends a synchronization start message. The at least one interface sends the synchronization start message to a time client device to set the current time of day on the time client device, receives a synchronization response message from the time client device indicating that the current time of day of the time client device was set, and sends a synchronization success message to the time client device indicating that the time client device has correctly set its current time of day.

Abstract: Techniques are described that facilitate performing accounting and billing separately for each customer of a service provider account registered to an owner of a shared customer device. An access router performs separate data usage accounting for each of the customers in sub-accounts of the registered service provider account based on customer virtual local area network (CVLAN) and service VLAN (SVLAN) tags included in data packets. A network operator may, therefore, generate a bill for the shared customer device that includes separate data usage charges for each customer. To facilitate the techniques, the access router may determine a CVLAN and SVLAN associated with a customer. The CVLAN and SVLAN tags are included in a service request toward a service provider, and copied into a service request reply toward the shared customer device. The shared customer device then includes the tags in data packets to identify the customer to the access router.

Abstract: An example network device includes a set of interfaces, a control unit, and a forwarding engine. The control unit includes an interface group information repository that stores data defining interface groups. Each interface group includes one or more interfaces. The forwarding engine includes a media access control (MAC) address repository that stores a mapping of a first interface to a source MAC address, and a MAC address management module that determines whether an interface group to which the first interface is assigned is the same interface group as the interface group to which a second interface is assigned. The control unit is configured to receive a layer two (L2) communication via the second interface, wherein the L2 communication includes the source MAC address. The forwarding engine dynamically updates the MAC address repository based on the determination of the MAC address management module.

Abstract: A network device may receive first qualification indicators, for a first signal, from all line cards of the network device. The network device may, in response to the first qualification indicators, transmit instructions to all of the line cards to use the first signal. The network device may further receive second qualification indicators, for a second signal, from all of the line cards. In response to the second qualification indicators, the network device may store information for the second signal in order to use the second signal as a backup signal.

Abstract: Methods, apparatus, and products are disclosed for forwarding frames in a computer network using shortest path bridging (‘SPB’). The network includes multiple bridges, and each edge bridge is assigned a unique service virtual local area network (‘VLAN’) identifier. One of the bridges receives a frame for transmission to a destination node. The received frame includes a service VLAN identifier for the ingress bridge through which the frame entered the network and a customer VLAN identifier. The one bridge identifies an SPB forwarding tree in dependence upon the service VLAN identifier. The SPB forwarding tree specifies a shortest route in the network from the ingress bridge through the one bridge to the other bridges in the network. The one bridge then forwards the received frame to the egress bridge without MAC-in-MAC encapsulation in dependence upon the SPB forwarding tree and the customer VLAN identifier.

Abstract: An example network device includes a set of interfaces, a control unit, and a forwarding engine. The control unit includes an interface group information repository that stores data defining interface groups. Each interface group includes one or more interfaces. The forwarding engine includes a media access control (MAC) address repository that stores a mapping of a first interface to a source MAC address, and a MAC address management module that determines whether an interface group to which the first interface is assigned is the same interface group as the interface group to which a second interface is assigned. The control unit is configured to receive a layer two (L2) communication via the second interface, wherein the L2 communication includes the source MAC address. The forwarding engine dynamically updates the MAC address repository based on the determination of the MAC address management module.

Abstract: A derived state value is calculated based on a plurality of component state values. As any of the plurality of component state values changes, the derived state value is recalculated. When sending information about a MAC address or other data between two components, the derived state value is included in the information sent. An object receiving a MAC address or other data from another object checks the validity of the received derived state value to determine whether to accept the new data and flush old data, to accept the new data, or to ignore the new data.

Abstract: A method may include receiving a packet including a destination address, identifying a destination address entry based on the destination address, the destination address entry including an address identifier, comparing the address identifier to an event identifier, determining whether an event occurred based on the comparison, and forwarding the packet on an alternate path if it is determined that the event occurred.

Abstract: Methods, apparatus, and products are disclosed for forwarding frames in a computer network using shortest path bridging (‘SPB’). The network includes multiple bridges, and each edge bridge is assigned a unique service virtual local area network (‘VLAN’) identifier. One of the bridges receives a frame for transmission to a destination node. The received frame includes a service VLAN identifier for the ingress bridge through which the frame entered the network and a customer VLAN identifier. The one bridge identifies an SPB forwarding tree in dependence upon the service VLAN identifier. The SPB forwarding tree specifies a shortest route in the network from the ingress bridge through the one bridge to the other bridges in the network. The one bridge then forwards the received frame to the egress bridge without MAC-in-MAC encapsulation in dependence upon the SPB forwarding tree and the customer VLAN identifier.

Abstract: A method may include receiving a packet including a destination address, identifying a destination address entry based on the destination address, the destination address entry including an address identifier, comparing the address identifier to an event identifier, determining whether an event occurred based on the comparison, and forwarding the packet on an alternate path if it is determined that the event occurred.

Abstract: A technique for managing traffic in a multiport network node involves establishing customer-specific VLANs within the multiport network node that are identified by a combination of a VLAN ID and a customer ID. Traffic received at the multiport network node is mapped to a customer-specific VLAN and then broadcast to ports that are included in the customer-specific VLAN. Because customer-specific VLANs are identified by a combination of a VLAN ID and customer ID, a service provider can establish and maintain private broadcast domains on a per-customer ID basis. This enables the service provider to expand the number of unique VLAN IDs within the Service Provider Edge Device beyond the 4,096 limitation set by the IEEE 802.1Q standard while maintaining interoperability with the IEEE 802.1Q standard for incoming and outgoing traffic.

Abstract: A technique for implementing VLANs across a service provider network involves establishing logical ports that have bindings to transport tunnels. The logical ports are then treated the same as physical ports in defining broadcast domains at particular service provider edge devices. Logical ports can be established for Layer 2 transport tunnels that use stacked VLAN tunneling and MPLS tunneling. Establishing a logical port that uses stacked VLAN tunneling involves binding a physical port and a stacked VLAN tunnel to the logical port. Establishing a logical port that uses MPLS tunneling involves binding an MPLS tunnel to a logical port. In one embodiment, the logical port is bound to a static MPLS tunnel and in another embodiment, the logical port is bound to a dynamic MPLS tunnel and the destination IP address of the destination service provider edge device.

Abstract: A technique for managing traffic in a multiport network node involves establishing customer-specific VLANs within the multiport network node that are identified by a combination of a VLAN ID and a customer ID. Traffic received at the multiport network node is mapped to a customer-specific VLAN and then broadcast to ports that are included in the customer-specific VLAN. Because customer-specific VLANs are identified by a combination of a VLAN ID and customer ID, a service provider can establish and maintain private broadcast domains on a per-customer ID basis. This enables the service provider to expand the number of unique VLAN IDs within the Service Provider Edge Device beyond the 4,096 limitation set by the IEEE 802.1Q standard while maintaining interoperability with the IEEE 802.1Q standard for incoming and outgoing traffic.

Abstract: A technique for implementing VLANs across a service provider network involves establishing logical ports that have bindings to transport tunnels. The logical ports are then treated the same as physical ports in defining broadcast domains at particular service provider edge devices. Logical ports can be established for Layer 2 transport tunnels that use stacked VLAN tunneling and MPLS tunneling. Establishing a logical port that uses stacked VLAN tunneling involves binding a physical port and a stacked VLAN tunnel to the logical port. Establishing a logical port that uses MPLS tunneling involves binding an MPLS tunnel to a logical port. In one embodiment, the logical port is bound to a static MPLS tunnel and in another embodiment, the logical port is bound to a dynamic MPLS tunnel and the destination IP address of the destination service provider edge device.