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