Marc,
To complete Steve and Diego's answers, do not forget sub-interfaces... :-)
DLCI will inherit map-class in this order :
1) DLCI specific
2) Sub-interface
3) Physical interface
map-class frame-relay Phys
frame-relay cir 64000
map-class frame-relay SubInt
frame-relay cir 48000
map-class frame-relay DLCI
frame-relay cir 32000
!
interface Serial1/0
no ip address
encapsulation frame-relay
no fair-queue
serial restart-delay 0
frame-relay class Phys
frame-relay traffic-shaping
frame-relay interface-dlci 789
!
interface Serial1/0.1 multipoint
frame-relay class SubInt
frame-relay interface-dlci 123
class DLCI
frame-relay interface-dlci 456
!
interface Serial1/0.2 multipoint
frame-relay interface-dlci 124
R1(config-subif)#do sh traf
Interface Se1/0
Access Target Byte Sustain Excess Interval Increment Adapt
VC List Rate Limit bits/int bits/int (ms) (bytes) Active
789 64000 1000 64000 0 125 1000
- <--------- From Physical interface
Interface Se1/0.1
Access Target Byte Sustain Excess Interval Increment Adapt
VC List Rate Limit bits/int bits/int (ms) (bytes) Active
456 48000 750 48000 0 125 750
- <--------- From Sub-interface
123 32000 500 32000 0 125 500
- <--------- From DLCI
Interface Se1/0.2
Access Target Byte Sustain Excess Interval Increment Adapt
VC List Rate Limit bits/int bits/int (ms) (bytes) Active
124 64000 1000 64000 0 125 1000
- <--------- From Physical interface
Christophe
On Tue, Jun 28, 2011 at 7:58 AM, Diego Gonzalez <[email protected]> wrote:
> I agree with you.
>
> Is your choice to apply the map-class to a specific DLCI or every DLCI
> active in the physical interface.
>
> A good example of a mix of both methods is when you want to shape for
> instance at 128kbps traffic out to DLCI and at 192kbps traffic out to any
> other DLCI of the same interface:
>
> map-class frame-relay DLCI_SPECIFIC
> frame-relay cir 128000
> frame-relay bc 1280
> !
> map-class frame-relay DLCI_OTHERS
> frame-relay cir 192000
> frame-relay bc 24000
> !
> interface Serial0/0
> frame-relay traffic-shaping
> frame-relay class DLCI_OTHERS
> frame-relay interface-dlci 201
> class DLCI_SPECIFIC
> !
> !
>
> Cheers
> Diego.
>
>
> 2011/6/28 marc abel <[email protected]>
>
>> Can anyone explain the logic or give some advice around when to apply
>> frame-relay map-class under the interface or under the dlci?
>>
>> For instance this would be under the DLCI:
>>
>> interface Serial0/0/0
>> bandwidth 64
>> ip address 150.100.24.4 255.255.255.0
>> encapsulation frame-relay
>> ip ospf network point-to-point
>> frame-relay traffic-shaping
>> frame-relay map ip 150.100.24.2 402 broadcast
>> frame-relay interface-dlci 402
>> class QOS
>> no frame-relay inverse-arp
>> frame-relay lmi-type cisco
>> end
>>
>> Under the interface:
>>
>> interface Serial0/0/0
>> bandwidth 64
>> ip address 150.100.24.4 255.255.255.0
>> encapsulation frame-relay
>> ip ospf network point-to-point
>> frame-relay class QOS
>> frame-relay traffic-shaping
>> frame-relay map ip 150.100.24.2 402 broadcast
>> no frame-relay inverse-arp
>> frame-relay lmi-type cisco
>> end
>>
>>
>> The first seems to shape just the DLCI in question per policy and all
>> others get a default policy, the second shapes all the DLCI's the
>> same.
>>
>> Thank you,
>>
>> Marc
>> _______________________________________________
>> For more information regarding industry leading CCIE Lab training, please
>> visit www.ipexpert.com
>>
>> Are you a CCNP or CCIE and looking for a job? Check out
>> www.PlatinumPlacement.com
>>
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out
www.PlatinumPlacement.com
