Abstract:
A system for packet transmission over an MPLS tunnel may include a plurality of network devices. The network devices may include ingress and egress routers and intermediate routers. The system may be configured to use payload type indication labels and payload type headers to transmit packets from a plurality of user devices having different payload types and service instances over a single pseudo-wire service in a label switched path of the MPLS network.
Abstract:
Methods and systems for encapsulating and de-encapsulating a customer frame component of a Provider Backbone Bridging header are provided. The customer frame component includes a customer local area network identifier and a customer destination address. The customer frame component can be received at an ingress port of a network device for transmission. Header information can be determined from the customer local area network identifier and the customer destination address. A key can be set in the header information to a predefined value for a Provider Backbone Bridging protocol. A backbone service instance identifier can be determined from the customer local area network identifier. The header information and backbone service instance identifier can be concatenated with the customer frame component to form a frame. The frame can be provided to an egress port of the network device for transmission, where the egress port is determined from the header information.
Abstract:
Networks devices interconnected via link groups may implement micro operations administration and maintenance (micro-OAM) sessions. The micro-OAM sessions may be used to monitor the status of individual links within the link groups at small time scales. The micro-OAM session may be implemented on a non-internet protocol (non-IP) layer. In some cases, independent micro-OAM sessions may be used to monitor different links within a link group.
Abstract:
Methods and systems for encapsulating and de-encapsulating a customer frame component of a Provider Backbone Bridging header are provided. The customer frame component includes a customer local area network identifier and a customer destination address. The customer frame component can be received at an ingress port of a network device for transmission. Header information can be determined from the customer local area network identifier and the customer destination address. A key can be set in the header information to a predefined value for a Provider Backbone Bridging protocol. A backbone service instance identifier can be determined from the customer local area network identifier. The header information and backbone service instance identifier can be concatenated with the customer frame component to form a frame. The frame can be provided to an egress port of the network device for transmission, where the egress port is determined from the header information.