cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1427
Views
0
Helpful
4
Replies

Deterministic WCCP assignment of buckets to WAEs

mvijay025
Level 1
Level 1

I have a scenario where there are 3 WAE devices used in a site. We are using MASK of 0x3F (6 bits) on source IP address for distribution to achieve as fair a bucket distribution to the devices as possible - 21 buckets, 21 buckets and 22 buckets. I understand it doesnt translate to equal load distribution as some buckets tend to have more flows. However, my question is regarding the determinism in the order of assignment. One may expect the following assignment to start with:

0 to 20 buckets - wae1

21 to 41 buckets - wae2

42 to 63 buckets - wae3

However, I see a different assignment in our deployment.

wae1: 1-10 and 32-41 buckets

wae2: 11-31 buckets

wae3: 42-63 buckets

Can I force the assignment a certain way? Does the assignment remain constant across reloads of devices?

CCP Client information:

    WCCP Client ID:          10.240.163.148

    Protocol Version:        2.0

    State:                   Usable

    Redirection:             L2

    Packet Return:           GRE

    Packets Redirected:    61

    Connect Time:          18w4d

    Assignment:            MASK

    Mask  SrcAddr    DstAddr    SrcPort DstPort

    ----  -------    -------    ------- -------

    0000: 0x0000003F 0x00000000 0x0000  0x0000

    Value SrcAddr    DstAddr    SrcPort DstPort CE-IP

    ----- -------    -------    ------- ------- -----

    0042: 0x0000002A 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0043: 0x0000002B 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0044: 0x0000002C 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0045: 0x0000002D 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0046: 0x0000002E 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0047: 0x0000002F 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0048: 0x00000030 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0049: 0x00000031 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0050: 0x00000032 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0051: 0x00000033 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0052: 0x00000034 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0053: 0x00000035 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0054: 0x00000036 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0055: 0x00000037 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0056: 0x00000038 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0057: 0x00000039 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

        0058: 0x0000003A 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0059: 0x0000003B 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0060: 0x0000003C 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0061: 0x0000003D 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0062: 0x0000003E 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    0063: 0x0000003F 0x00000000 0x0000  0x0000  0x0AF0A394 (10.240.163.148)

    WCCP Client ID:          10.240.163.147

    Protocol Version:        2.0

    State:                   Usable

    Redirection:             L2

    Packet Return:           GRE

    Packets Redirected:    76

    Connect Time:          18w4d

    Assignment:            MASK

    Mask  SrcAddr    DstAddr    SrcPort DstPort

    ----  -------    -------    ------- -------

    0000: 0x0000003F 0x00000000 0x0000  0x0000

    Value SrcAddr    DstAddr    SrcPort DstPort CE-IP

    ----- -------    -------    ------- ------- -----

    0011: 0x0000000B 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

        0012: 0x0000000C 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0013: 0x0000000D 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0014: 0x0000000E 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0015: 0x0000000F 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0016: 0x00000010 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0017: 0x00000011 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0018: 0x00000012 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0019: 0x00000013 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0020: 0x00000014 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0021: 0x00000015 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0022: 0x00000016 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0023: 0x00000017 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0024: 0x00000018 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0025: 0x00000019 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0026: 0x0000001A 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0027: 0x0000001B 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0028: 0x0000001C 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0029: 0x0000001D 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0030: 0x0000001E 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    0031: 0x0000001F 0x00000000 0x0000  0x0000  0x0AF0A393 (10.240.163.147)

    WCCP Client ID:          10.240.163.146

    Protocol Version:        2.0

        State:                   Usable

    Redirection:             L2

    Packet Return:           GRE

    Packets Redirected:    10

    Connect Time:          15w1d

    Assignment:            MASK

    Mask  SrcAddr    DstAddr    SrcPort DstPort

    ----  -------    -------    ------- -------

    0000: 0x0000003F 0x00000000 0x0000  0x0000

    Value SrcAddr    DstAddr    SrcPort DstPort CE-IP

    ----- -------    -------    ------- ------- -----

    0000: 0x00000000 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0001: 0x00000001 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0002: 0x00000002 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0003: 0x00000003 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0004: 0x00000004 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0005: 0x00000005 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0006: 0x00000006 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0007: 0x00000007 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0008: 0x00000008 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0009: 0x00000009 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0010: 0x0000000A 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0032: 0x00000020 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0033: 0x00000021 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0034: 0x00000022 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0035: 0x00000023 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0036: 0x00000024 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0037: 0x00000025 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0038: 0x00000026 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0039: 0x00000027 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0040: 0x00000028 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

    0041: 0x00000029 0x00000000 0x0000  0x0000  0x0AF0A392 (10.240.163.146)

Thanks,

Vijay

1 Accepted Solution

Accepted Solutions

gaursin2
Level 1
Level 1

HI Vijay,

Few things i want to share from your output, the reason of this  assignemnt you are seeing is because your WAE

10.240.163.146 which has "out of order" assignement, is added later [see there connect time] So we can conlcude that intially you have only 2 wae's in your setup [or may be 3] and have linier bucket assignemt but after addition of third one [or reload of 3rd one] bucket got re-assigned to this 3rd WAE from other two.

in short this was your assignment befor addition of 3rd WAE,

wae2: 1-31 buckets

wae3: 32-63 buckets

when 3rd WAE added, half of buckets from each WAE got assigned. and result is what you are seeing.

Hope this explanation anserrwd your query.

View solution in original post

4 Replies 4

gaursin2
Level 1
Level 1

HI Vijay,

Few things i want to share from your output, the reason of this  assignemnt you are seeing is because your WAE

10.240.163.146 which has "out of order" assignement, is added later [see there connect time] So we can conlcude that intially you have only 2 wae's in your setup [or may be 3] and have linier bucket assignemt but after addition of third one [or reload of 3rd one] bucket got re-assigned to this 3rd WAE from other two.

in short this was your assignment befor addition of 3rd WAE,

wae2: 1-31 buckets

wae3: 32-63 buckets

when 3rd WAE added, half of buckets from each WAE got assigned. and result is what you are seeing.

Hope this explanation anserrwd your query.

Thanks Gaurav. I was suspecting that. However, that does not seem quite right to me. This makes the assignment non-deterministic and has unwanted effects as we are facing now. Though not frequent, a WAE in the cluster going down/coming up is not a totally unforeseen event. I understand that in this case, the emphasis is on optimal re-assignment (reassign as low number of buckets as possible to achieve the required distribution) rather than going back to previous assignment. In my opinion, it is desirable to have an additional knob to ask WCCP router to deterministically assign buckets to WAEs. Does any such configuration exist?

-Vijay

I am still confused with what kind of issue you are facing with this type of assignemnt.

but you can use feature like WCCP slow start, which will control the traffic load in case of bucket re-assignment.

I haven't found any knob to create a deterministic assignment of buckets to WAE devices in the cluster. However, after toggling WCCP on my router it restored the assigment to original one.

0 to 20 buckets - wae1

21 to 41 buckets - wae2

42 to 63 buckets - wae3