Hello Jobin, There are three Qos Model in MPLS network: Uniform mode: DiffServ Tunneling Uniform Mode has only one layer of QoS, which reaches end-to-end. The ingress PE router  copies the DSCP from the incoming IP packet into the MPLS EXP bits of the imposed labels. As the EXP bits travel through the core, they may or may not be modified by intermediate P routers. In this example, P router P1 modifies the EXP bits of the top label. At the egress P router  we copy the EXP bits to the EXP bits of the newly exposed label after the PHP (Penultimate-Hop-Pop).Finally at the egress PE router  we then copy the EXP bits to the DSCP bits of the newly exposed IP packet. Long Pipe: Diffserv Tunneling Pipe Mode uses two layers of QoS: An underlying QoS for the data, which remains unchanged when traversing the core. A per-core QoS, which is separate from that of the underlying IP packets. This per-core QoS PHB remains transparent to end users. When a packet reaches the edge of the MPLS core, the egress PE router  classifies the newly exposed IP packets for outbound queuing based on the MPLS PHB from the EXP bits of the recently removed label. Short Pipe: Diffserv Tunneling Short-pipe Mode uses the same rules and techniques across the core. The difference is at the egress PE router —you classify the newly exposed IP packets for outbound queuing based on the IP PHB from the DSCP value of this IP packet. If you manage the MPLS network than the uniform mode is the appropriate mode for you. have a look at this for the configuration:  http://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-... hope this helps ... View more

Hello Jobin, There are three Qos Model in MPLS network: Uniform mode: DiffServ Tunneling Uniform Mode has only one layer of QoS, which reaches end-to-end. The ingress PE router  copies the DSCP from the incoming IP packet into the MPLS EXP bits of the imposed labels. As the EXP bits travel through the core, they may or may not be modified by intermediate P routers. In this example, P router P1 modifies the EXP bits of the top label. At the egress P router  we copy the EXP bits to the EXP bits of the newly exposed label after the PHP (Penultimate-Hop-Pop).Finally at the egress PE router  we then copy the EXP bits to the DSCP bits of the newly exposed IP packet. Long Pipe: Diffserv Tunneling Pipe Mode uses two layers of QoS: An underlying QoS for the data, which remains unchanged when traversing the core. A per-core QoS, which is separate from that of the underlying IP packets. This per-core QoS PHB remains transparent to end users. When a packet reaches the edge of the MPLS core, the egress PE router  classifies the newly exposed IP packets for outbound queuing based on the MPLS PHB from the EXP bits of the recently removed label. Short Pipe: Diffserv Tunneling Short-pipe Mode uses the same rules and techniques across the core. The difference is at the egress PE router —you classify the newly exposed IP packets for outbound queuing based on the IP PHB from the DSCP value of this IP packet. If you manage the MPLS network than the uniform mode is the appropriate mode for you. have a look at this for the configuration:  http://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/mpls/47815-diffserv-tunnel.html#uniform hope this helps ... View more

Hello,   An MPLS network consists of edge devices known as PE (Provider Edge) and core router known as P (Provider). The basic roles of PE router are:    At the ingress side: encapsulate(push) a label and forward the packet toward the egress PE    At the egress side: decapsulate (pop) the label and forward the packet to final destination (if PHP is not activated) The P router reads the incoming label and identify to which egress interface must be sent (swap label). Back to your questions: you can configure a single router to be a P and PE router? the answer is Yes. what are the disadvantages of a single router doing both? it depends. How large is your MPLS network, what are the performances of your routers ..etc what is the main reason for separating the two routers on networks? There are many reasons for that: Scalability reason by offloading the role of label swapping to the P router and let the PEs focuses only for the Push and the PoP operations Simplifying the design of your MPLS networks  The answer for why i need a core layer in enterprise network design? could be applied as an answer for why i need a P router in MPLS design    Hope this helps  ... View more

Yes you can go and configure only the eth port 17 without touching the port 18 ... View more

Hello -Ypsilon The  interface breakout module 1 port 17,18 map 10g-4x will create  subinterfaces under parent Ethernet interfaces 17 and 18 and will not delete any  previous configs when you enter "show interface status you will get something like this: Eth 1/17/1 Eth 1/17/2 Eth 1/17/3 Eth 1/17/4 Eth 1/18/1 Eth 1/18/2 Eth 1/18/3 Eth 1/18/4 Hope this helps !!! ... View more