Routing
Routing

Extended community with 4 byte AS

‎03-22-2019 08:26 AM

What am I missing?

 

This works OK:

members bandwidth:200001L:300
members bandwidth:65500:37500000

 

But:

members bandwidth:200001L:37500000 gives commit error....

 

[edit policy-options community Bandwidth-300]
'members bandwidth:200001L:37500000'
invalid Extended community value value at '37500000' not in range 0 to 65535
error: configuration check-out failed

 

(exact ASN changed to 200001 for privacy)

 

Regards,

Pawel 

3 REPLIES 3
Routing
Solution
Accepted by topic author pmazurkiewicz
‎04-01-2019 01:43 PM

Re: Extended community with 4 byte AS

‎03-22-2019 09:28 AM

Hi,

As far as I understand, you only have 6 bytes left in the extended community for specifying the number (2 bytes are used for the type). You can either split those 6 bytes as 2:4 or 4:2. If you specify 'L' after the number, it's treated as 32-bit long (i.e. takes 4 bytes).

In this case 'bandwidth:200001L:37500000' you don't need to specify 'L' for 200001 as it will take 4 bytes anyway (as it's bigger than 65535, the maximum value which can be represented by 2 bytes), so you are left with just 2 bytes for the second number.

 

Routing

Re: Extended community with 4 byte AS

‎03-22-2019 09:58 AM

Sorry, you actially need 'L' when the number is higher than 65535 (although it seems redundant to me)

Routing

Re: Extended community with 4 byte AS

‎03-22-2019 09:58 AM

Hi,

current implemention does support only 2 Byte AS for bw community, so you can apply or use left space and put some small BW which fits