MPLS TE tunnel mounted from another equipment vendor with affinity 0x0 / 0xffff

We use traffic engineering with dynamic tunnels, with a condition on the bandwidth on the following topology:

We want to mount a tunnel from the ASR9000 to the ASR1000-2, so through the Huawei switch. However, the tunnel does not rise.

Our bandwidths are properly defined. The default affinity is 0x0 / 0xffff on the ASR9000 tunnel.

However, when we assemble a tunnel from the ASR1000-1 to the ASR1000-2, the tunnel goes up well.

When we change the affinity value of the ASR9000 tunnel to "0x0 mask 0x0", the tunnel rises through the Huawei.

Why is the Huawei switch not passable with a tunnel mounted from an ASR9000 with affinity 0x0 / 0xffff?

By analyzing the messages on the ASR9000, we encounter the following message: Info: No path to destination, 128.x.x.x (bw or affinity)

First I have checked the documentation to see what is the default affinity on the MPLS TE configuration:

Since the traffic is only passing the Huawei device and no MPLS TE tunnel is created on it, traffic should be transparent.

Next plan: We ask customer to do a packet capture in order to see what is happening when the tunnel it goes UP and when it doesn't

By changing the tunnel configuration on the ASR9000 to 0x0 / 0x0, you can see that the tunnel goes up by filtering the RSVP messages (messages 91 and 92 in the capture)

From message 209, the tunnel is shutdown, the 0x0 / 0x0 command is removed (and therefore no fault goes to 0x0 / 0xFFFF), then "no shutdown". Subsequently, the tunnel did not ascend.

It seems that we need to change the value of the administrative-group attribute for an interface, so the Huawei device can pass traffic with the same affinity as the tunnel is set.

The mpls te link administrative group command sets the value of the administrative-group attribute for an interface.

Parameters

Views

VLANIF interface view, GE interface view, XGE interface view, 40GE interface view, Eth-trunk interface view

Usage Guidelines

After being advertised globally, interface attributes can work as a standard for the ingress of a tunnel to select a path.

The modification on the administrative-group attributes takes effect only on the LSPs created after the modification and does not affect the established LSPs.

The mpls te link administrative group command can be run on the outgoing interface of the link through which a TE tunnel passes.

Example

# Set the administrative-group attribute to 0x0101 on interface VLANIF100.

<HUAWEI> system-view

[HUAWEI] interface vlanif 100

[HUAWEI-Vlanif100] mpls

[HUAWEI-Vlanif100] mpls te

[HUAWEI-Vlanif100] mpls te link administrative group 101

# Set the administrative-group attribute to 0x0101 on interface GE0/0/1.

<HUAWEI> system-view

[HUAWEI] interface gigabitethernet 0/0/1

[HUAWEI-GigabitEthernet0/0/1] undo portswitch

[HUAWEI-GigabitEthernet0/0/1] mpls

[HUAWEI-GigabitEthernet0/0/1] mpls te

[HUAWEI-GigabitEthernet0/0/1] mpls te link administrative group 101