DSCP field not tagged by GD
Posted: 03 Jan 2011 10:05
Hi,
First of all i whish you an happy new year.
I'm facing a weird behavior.
The installation is on G1.503.35, using multiple WAN to connect MG with GD-2 on branches offices.
All are using the same IP Quality of service Category and so the same diffServDSCP field.
On all GDs it' working fine, IP Packets are tagged using the DiffServ value except one GD.
In base configuration we select the value and the GD learn it from the OXE and apply this configuration.
We try to capture the input/output traffic using tcpdump on two GD (the first is working and the second not).
So on the first GD everything is tag using the diffserv from mgr.
The second GD isn't taging the diffserv at all.
We can see that the OXE is tagging his traffic to the GD (same thing, tcpdump from the OXE) but it's not tagged anymore when the GD receive it (maybe changed on the network).
I tried to switch the GD from IP Domain / Ip Quality to uncheck and check configuration but nothing changed.
So i think it was a network issue but sometime i'm quite sure you face this problem too, we have to point the issue on the network to the network team ...
Everything point to a network problem but the fact is that the GD isn't tagging his traffic to the OXE and she's supposed to, i don't know why and it's little disturbing.
So i'm searching how the GD learn that she need to use a diffserv value ?
Thank for reading me.
First of all i whish you an happy new year.
I'm facing a weird behavior.
The installation is on G1.503.35, using multiple WAN to connect MG with GD-2 on branches offices.
All are using the same IP Quality of service Category and so the same diffServDSCP field.
On all GDs it' working fine, IP Packets are tagged using the DiffServ value except one GD.
In base configuration we select the value and the GD learn it from the OXE and apply this configuration.
We try to capture the input/output traffic using tcpdump on two GD (the first is working and the second not).
So on the first GD everything is tag using the diffserv from mgr.
The second GD isn't taging the diffserv at all.
We can see that the OXE is tagging his traffic to the GD (same thing, tcpdump from the OXE) but it's not tagged anymore when the GD receive it (maybe changed on the network).
I tried to switch the GD from IP Domain / Ip Quality to uncheck and check configuration but nothing changed.
So i think it was a network issue but sometime i'm quite sure you face this problem too, we have to point the issue on the network to the network team ...
Everything point to a network problem but the fact is that the GD isn't tagging his traffic to the OXE and she's supposed to, i don't know why and it's little disturbing.
So i'm searching how the GD learn that she need to use a diffserv value ?
Thank for reading me.