HI Alex:<br><br>Thanks for the reply.<br><br>But do you mean the UDP Age? Any good values to set for the time-out?<br><br>Thanks.<br><br><br>-- <br>Regards,<br><br>Emmanuel Muncal, ECE<br><a href="http://framesofanemn.blogspot.com">http://framesofanemn.blogspot.com</a><br>
<br><br>-----BEGIN
GEEK CODE BLOCK-----<br>Version: 3.12<br>GE d- s: a28- C++++ UL++ P L++
E--- W++<br>N+ o-- K- w O+ M- V-- PS+ PE+ Y PGP- t 5+<br>X+ R* tv+ b+
DI++ D- G e++ h---- r+++ y+++<br>------END GEEK CODE BLOCK------<br><br><div class="gmail_quote">On Sun, Aug 1, 2010 at 8:22 PM, alex sharaz <span dir="ltr"><<a href="mailto:alexsharaz@me.com">alexsharaz@me.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div bgcolor="#FFFFFF"><div>Hi</div><div>Sounds familiar</div><div>I found thar I had to enable normal timeouts on DNS. The serveriron does strange things to timeouts for radius and DNS</div>
<div>Do a port dns ? To find the command.</div><div>Alex<br><br>Sent from my iPhone, easier than windows mobile</div><div><br>On 1 Aug 2010, at 01:56, Emmanuel Muncal <<a href="mailto:graemann@gmail.com" target="_blank">graemann@gmail.com</a>> wrote:<br>
<br></div><div></div><blockquote type="cite"><div>
<p><font size="2">Hi all,<br>
<br>
Anyone having intermittency problems with dns slb specially with dig<br>
and nslookup on the vip?<br>
<br>
While on real server there is no problem.<br>
<br>
My healthcheck:<br>
-no L3<br>
-i got dns_query turned on querying for <a href="http://www.google.com" target="_blank"></a><a href="http://www.google.com" target="_blank">www.google.com</a><br>
<br>
Any ideas?<br>
<br>
Thanks.<br>
<br>
Emmanuel<br>
<br>
<br>
On 8/1/10, <a href="mailto:foundry-nsp-request@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp-request@puck.nether.net" target="_blank">foundry-nsp-request@puck.nether.net</a><br>
<<a href="mailto:foundry-nsp-request@puck.nether.net" target="_blank">foundry-nsp-request@puck.nether.net</a>> wrote:<br>
> Send foundry-nsp mailing list submissions to<br>
> <a href="mailto:foundry-nsp@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank"></a><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:foundry-nsp-request@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp-request@puck.nether.net" target="_blank">foundry-nsp-request@puck.nether.net</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:foundry-nsp-owner@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp-owner@puck.nether.net" target="_blank">foundry-nsp-owner@puck.nether.net</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of foundry-nsp digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: traffic-policy reporting (Nick Morrison)<br>
> 2. ACLs and BI-RX (Chuck Ufarley)<br>
> 3. Dual-Mode vlan id (Gary H)<br>
> 4. Re: Dual-Mode vlan id (Sujith)<br>
> 5. Re: Dual-Mode vlan id (Raoul Bhatia [IPAX])<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Fri, 30 Jul 2010 16:38:37 +0000<br>
> From: Nick Morrison <<a href="mailto:nick@nick.on.net" target="_blank">nick@nick.on.net</a>><br>
> To: Peter Kranz <<a href="mailto:pkranz@unwiredltd.com" target="_blank">pkranz@unwiredltd.com</a>><br>
> Cc: <a href="mailto:foundry-nsp@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> Subject: Re: [f-nsp] traffic-policy reporting<br>
> Message-ID: <<a href="mailto:20100730163837.GA13290@nick.on.net" target="_blank">20100730163837.GA13290@nick.on.net</a>><br>
> Content-Type: text/plain; charset=us-ascii<br>
><br>
> On Wed, Jul 28, 2010 at 12:12:39PM -0700, Peter Kranz said:<br>
>> I would like to be able to graph the traffic handled by a named<br>
>> traffic policy; i.e. I can't really get much useful data out of the<br>
>> show stat traffic-policy report since it does not provide packet per<br>
>> second level data, only total bytes..<br>
><br>
> You could use munin. Grab that output every 5 minutes and munin will<br>
> graph it easily. You can use rancid to run the command without having<br>
> to write an Expect script.<br>
><br>
> There is probably also an SNMP OID you can query.. check the SNMP MIB<br>
> reference for your switch.<br>
><br>
> Good luck!<br>
><br>
> Nick<br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Fri, 30 Jul 2010 13:51:17 -0700<br>
> From: Chuck Ufarley <<a href="mailto:markentime@gmail.com" target="_blank">markentime@gmail.com</a>><br>
> To: <a href="mailto:foundry-nsp@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> Subject: [f-nsp] ACLs and BI-RX<br>
> Message-ID:<br>
> <<a href="mailto:AANLkTikpZpRr1eqEA61qrgmm5WR4O9R=k5LMNOOrv8HL@mail.gmail.com" target="_blank">AANLkTikpZpRr1eqEA61qrgmm5WR4O9R=k5LMNOOrv8HL@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
> Hey all--<br>
> I'm get this error message when I load an ACL on multiple ports of a card on<br>
> a BI-RX:<br>
><br>
> Dynamic Log Buffer (1000 lines):<br>
> Jul 29 14:42:36:I:Failed to allocate Traffic Conditioner resource<br>
> Jul 29 14:42:36:I:Failed to allocate Traffic Conditioner resource<br>
> Jul 29 14:42:36:I:Failed to allocate Traffic Conditioner resource<br>
> Jul 29 14:42:36:I:Failed to allocate Traffic Conditioner resource<br>
><br>
> When I put an ACL on one port, no problem. Applying another ACL to a port<br>
> on the same line card, and I get the above. Can anyone give me some advice<br>
> on what may be the cause of this?<br>
><br>
> Thanks much.<br>
><br>
> --Chuck<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="https://puck.nether.net/pipermail/foundry-nsp/attachments/20100730/bf09d38c/attachment-0001.html" target="_blank"></a><a href="https://puck.nether.net/pipermail/foundry-nsp/attachments/20100730/bf09d38c/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/foundry-nsp/attachments/20100730/bf09d38c/attachment-0001.html</a>><br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Fri, 30 Jul 2010 20:09:14 -0400<br>
> From: Gary H <<a href="mailto:ciscovoiper@gmail.com" target="_blank">ciscovoiper@gmail.com</a>><br>
> To: <a href="mailto:foundry-nsp@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> Subject: [f-nsp] Dual-Mode vlan id<br>
> Message-ID:<br>
> <<a href="mailto:AANLkTikp_ynrjqfS9Xtwejbi7Ss539vEZq4FMznqYXZj@mail.gmail.com" target="_blank">AANLkTikp_ynrjqfS9Xtwejbi7Ss539vEZq4FMznqYXZj@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
> I'm using Dual-Mode on user interfaces and I didn't assign a vlan id so it<br>
> is using the DEFAULT-VLAN.<br>
><br>
> I have voice traffic assigned with voice-vlan ##.<br>
><br>
> My trunk carries the voice traffic but the data get stuck somewhere. Does<br>
> the Dual-Mode need to be assigned a vlan id so that it can be a tagged trunk<br>
> port member because DEFAULT-VLAN no longer has the port available once it<br>
> gets added to the voice vlan as a tagged port.<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="https://puck.nether.net/pipermail/foundry-nsp/attachments/20100730/d79a7f4a/attachment-0001.html" target="_blank"></a><a href="https://puck.nether.net/pipermail/foundry-nsp/attachments/20100730/d79a7f4a/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/foundry-nsp/attachments/20100730/d79a7f4a/attachment-0001.html</a>><br>
><br>
> ------------------------------<br>
><br>
> Message: 4<br>
> Date: Sat, 31 Jul 2010 09:47:15 +0530<br>
> From: Sujith <<a href="mailto:jith787@gmail.com" target="_blank">jith787@gmail.com</a>><br>
> To: Gary H <<a href="mailto:ciscovoiper@gmail.com" target="_blank">ciscovoiper@gmail.com</a>><br>
> Cc: <a href="mailto:foundry-nsp@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> Subject: Re: [f-nsp] Dual-Mode vlan id<br>
> Message-ID:<br>
> <<a href="mailto:AANLkTik=GNzG0Eib2gT3uNHjTECKoSj_OX7v15td-ou-@mail.gmail.com" target="_blank">AANLkTik=GNzG0Eib2gT3uNHjTECKoSj_OX7v15td-ou-@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
> On Sat, Jul 31, 2010 at 5:39 AM, Gary H <<a href="mailto:ciscovoiper@gmail.com" target="_blank">ciscovoiper@gmail.com</a>> wrote:<br>
><br>
>> I'm using Dual-Mode on user interfaces and I didn't assign a vlan id so it<br>
>> is using the DEFAULT-VLAN.<br>
>><br>
>> I have voice traffic assigned with voice-vlan ##.<br>
>><br>
>> My trunk carries the voice traffic but the data get stuck somewhere. Does<br>
>> the Dual-Mode need to be assigned a vlan id so that it can be a tagged<br>
>> trunk<br>
>> port member because DEFAULT-VLAN no longer has the port available once it<br>
>> gets added to the voice vlan as a tagged port.<br>
>><br>
><br>
> Yes you should. Are you doing any inter-Vlan routing? Configure some data<br>
> Vlan and trunk it to the interface and your problem will get resolved.<br>
><br>
> Thanks<br>
> -Sujith<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="https://puck.nether.net/pipermail/foundry-nsp/attachments/20100731/0e5a8f9b/attachment-0001.html" target="_blank"></a><a href="https://puck.nether.net/pipermail/foundry-nsp/attachments/20100731/0e5a8f9b/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/foundry-nsp/attachments/20100731/0e5a8f9b/attachment-0001.html</a>><br>
><br>
> ------------------------------<br>
><br>
> Message: 5<br>
> Date: Sat, 31 Jul 2010 10:37:43 +0200<br>
> From: "Raoul Bhatia [IPAX]" <<a href="mailto:r.bhatia@ipax.at" target="_blank">r.bhatia@ipax.at</a>><br>
> To: Gary H <<a href="mailto:ciscovoiper@gmail.com" target="_blank">ciscovoiper@gmail.com</a>><br>
> Cc: <a href="mailto:foundry-nsp@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> Subject: Re: [f-nsp] Dual-Mode vlan id<br>
> Message-ID: <<a href="mailto:4C53E0D7.5020604@ipax.at" target="_blank">4C53E0D7.5020604@ipax.at</a>><br>
> Content-Type: text/plain; charset=ISO-8859-1<br>
><br>
> On 07/31/2010 02:09 AM, Gary H wrote:<br>
>> I'm using Dual-Mode on user interfaces and I didn't assign a vlan id so<br>
>> it is using the DEFAULT-VLAN.<br>
>><br>
>> I have voice traffic assigned with voice-vlan ##.<br>
>><br>
>> My trunk carries the voice traffic but the data get stuck somewhere.<br>
>> Does the Dual-Mode need to be assigned a vlan id so that it can be a<br>
>> tagged trunk port member because DEFAULT-VLAN no longer has the port<br>
>> available once it gets added to the voice vlan as a tagged port.<br>
><br>
><br>
> what we do:<br>
><br>
> # assign the port to the vlans<br>
> vlan 123 name data<br>
> tag e 1<br>
><br>
> vlan 456 name voice<br>
> tag e 1<br>
><br>
> # allow untagged/dual mode for data vlan<br>
> int e 1<br>
> dual-mode 123<br>
><br>
><br>
> is that what you need?<br>
><br>
> cheers,<br>
> raoul<br>
> --<br>
> ____________________________________________________________________<br>
> DI (FH) Raoul Bhatia M.Sc. email. <a href="mailto:r.bhatia@ipax.at" target="_blank"></a><a href="mailto:r.bhatia@ipax.at" target="_blank">r.bhatia@ipax.at</a><br>
> Technischer Leiter<br>
><br>
> IPAX - Aloy Bhatia Hava OG web. <a href="http://www.ipax.at" target="_blank"></a><a href="http://www.ipax.at" target="_blank">http://www.ipax.at</a><br>
> Barawitzkagasse 10/2/2/11 email. <a href="mailto:office@ipax.at" target="_blank"></a><a href="mailto:office@ipax.at" target="_blank">office@ipax.at</a><br>
> 1190 Wien tel. +43 1 3670030<br>
> FN 277995t HG Wien fax. +43 1 3670030 15<br>
> ____________________________________________________________________<br>
><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> foundry-nsp mailing list<br>
> <a href="mailto:foundry-nsp@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank"></a><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
><br>
> End of foundry-nsp Digest, Vol 90, Issue 15<br>
> *******************************************<br>
><br>
<br>
--<br>
Sent from my mobile device<br>
<br>
Regards,<br>
<br>
Emmanuel Muncal, ECE<br>
<a href="http://framesofanemn.blogspot.com" target="_blank"></a><a href="http://framesofanemn.blogspot.com" target="_blank">http://framesofanemn.blogspot.com</a><br>
<br>
<br>
-----BEGIN GEEK CODE BLOCK-----<br>
Version: 3.12<br>
GE d- s: a28- C++++ UL++ P L++ E--- W++<br>
N+ o-- K- w O+ M- V-- PS+ PE+ Y PGP- t 5+<br>
X+ R* tv+ b+ DI++ D- G e++ h---- r+++ y+++<br>
------END GEEK CODE BLOCK------<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net" target="_blank"></a><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank"></a><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</font>
</p>
</div></blockquote></div>
</blockquote></div><br><br clear="all"><br>