Re: Outgoing traffic problem on Citrix Netscaler Load Balancer
Hi Anil, Have you setup MBF? I've seen that as an issue before. If you don't have a default route set, than MBF might help you send the response out the interface on which it was received. Paul > On Mar 24, 2014, at 11:46 PM, Anil KARADAG wrote: > > Hi, > > I setup a netscaler load balancer for sip traffic on Amazon EC2. Clients > packets are arrived to the backend servers over to the load balancer but any > responses cannot be arrived to clients. I see the responses on the load > balancer. > > I think there is a config problem for that but I don't know and did not find > any solution for that. How can I fix the outbound traffic issue. > > thanks > Bu e-posta mesaj? ve ekleri g?nderildi?i ki?i ya da kuruma ?zeldir ve > gizlidir. Ayr?ca hukuken de gizli olabilir. Hi?bir ?ekilde ???nc? ki?ilere > a??klanamaz ve yay?nlanamaz. E?er mesaj?n g?nderildi?i al?c? de?ilseniz bu > elektronik postan?n i?eri?ini a??klaman?z, kopyalaman?z, y?nlendirmeniz ve > kullanman?z kesinlikle yasakt?r ve bu elektronik postay? ve eklerini derhal > silmeniz gerekmektedir. NETA? TELEKOM?N?KASYON A.?. bu mesaj?n i?erdi?i > bilgilerin do?rulu?u veya eksiksiz oldu?u konusunda herhangi bir garanti > vermemektedir. Bu nedenle bu bilgilerin ne ?ekilde olursa olsun i?eri?inden, > iletilmesinden, al?nmas?ndan, saklanmas?ndan ve kullan?lmas?ndan sorumlu > de?ildir. Bu mesajdaki g?r??ler g?nderen ki?iye ait olup, NETA? > TELEKOM?N?KASYON A.?.'nin g?r??lerini yans?tmayabilir. > --- > This e-mail and its attachments are private and confidential and intended for > the exclusive use of the individual or entity to whom it is addressed. It may > also be legally confidential. Any disclosure, distribution or other > dissemination of this message to any third party is strictly prohibited. If > you are not the intended recipient you are hereby notified that any > dissemination, forwarding, copying or use of any of the information is > strictly prohibited, and the e-mail should immediately be deleted. NETA? > TELEKOM?N?KASYON A.?. makes no warranty as to the accuracy or completeness of > any information contained in this message and hereby excludes any liability > of any kind for the information contained therein or for the transmission, > reception, storage or use of such information in any way whatsoever. The > opinions expressed in this message are those of the sender and may not > necessarily reflect the opinions of NETA? TELEKOM?N?KASYON A.?.
Re: Outgoing traffic problem on Citrix Netscaler Load Balancer
Hi Anil, The command is for the service or servicegroup and it is: set service -useproxyport (NO|YES) Paul > On Apr 1, 2014, at 1:38, Anil KARADAG wrote: > > My aim is forwarding all sip packages from netscaler snip:client port number > to backend server ip: backend server port. I tried the following scenarios; > > - “use source ip” is enabled, “use proxy port” is set no > o Result: we see client port as source port but no SNIP for source > ip-address > - In additional above configured also RNAT > o Result: we see SNIP ip address as source ip address but source port again > become random. > > Checked the citrix support link for rnat, but our sip packages include ‘via > header’ option with SNIP: client port number; > > Via: SIP/2.0/UDP SNIP:5060;received=192.168.184.13;branch=z9hZ4bb1ce74d0f-a161-43af-8f08-2d98cf702742_0efcfc5e_71732184846337 > From: Alex White-Robinson [mailto:ale...@gmail.com] > Sent: Tuesday, April 01, 2014 11:00 AM > To: Anil KARADAG > Cc: Pui Edylie; Paul Bertain; nanog@nanog.org > Subject: Re: Outgoing traffic problem on Citrix Netscaler Load Balancer > > Have you configured RNAT yet? Might tidy up your SIP problem. Do you need the > servers to see the client's source port, or is your issue that SIP response > traffic is not on the port the client expects? > > Give the guide to setting up RNAT here a try - > http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-1-map/ns-lb-commonprotocols-sip-con.html > > tl;dr though - > set rnat > set lb sipParameters -rnatSrcPort 5060 -rnatDstPort 5060 -retryDur 1000 > -addRportVip ENABLED -sip503RateThreshold 1000 > > > > On Tue, Apr 1, 2014 at 7:33 PM, Anil KARADAG wrote: > Hi again, > > > > I continue to work on fixing the problem, but no success so far. Is there any > way to use client port number without enabling "use source ip"?? > > > > -Original Message- > From: Anil KARADAG [mailto:akara...@netas.com.tr] > Sent: Monday, March 31, 2014 3:51 PM > To: Pui Edylie; Paul Bertain > Cc: nanog@nanog.org > Subject: RE: Outgoing traffic problem on Citrix Netscaler Load Balancer > > > > Hi,SIP source ports destination ports > SIP source ports destination ports > > > Thanks for solution but I cannot use it, because backend servers must know > netscaler snip ip for clients. So I need fixed proxy port to communication > with backend servers. > > > > -Original Message- > > From: Pui Edylie [mailto:em...@edylie.net] > > Sent: Monday, March 31, 2014 3:23 PM > > To: Anil KARADAG; Paul Bertain > > Cc: nanog@nanog.org > > Subject: Re: Outgoing traffic problem on Citrix Netscaler Load Balancer > > > > Hi Anil, > > > > Take a look at > > http://support.citrix.com/proddocs/topic/ns-system-10-1-map/ns-nw-ipaddrssng-enabling-use-src-ip-mode-tsk.html > > - use the client's port. > > > > We prefer F5 LTM much better than Netscaler :) > > > > Cheers, > > Edy > > > > On 3/31/2014 8:17 PM, Anil KARADAG wrote: > > > Hi Paul, > > > > > > Thanks for reply, it works :). But I have another problem; source port is > > altered by the virtual service. However, we need the source port to be the > > same on the destination servers. Is there a way to ensure this? > > > > > > Thanks > > > > > > -Original Message- > > > From: Paul Bertain [mailto:p...@bertain.net] > > > Sent: Tuesday, March 25, 2014 10:47 PM > > > To: Anil KARADAG > > > Cc: nanog@nanog.org > > > Subject: Re: Outgoing traffic problem on Citrix Netscaler Load Balancer > > > > > > Hi Anil, > > > > > > Have you setup MBF? I've seen that as an issue before. If you don't have a > > default route set, than MBF might help you send the response out the > > interface on which it was received. > > > > > > Paul > > > > > >> On Mar 24, 2014, at 11:46 PM, Anil KARADAG > >> mailto:akara...@netas.com.tr>> wrote: > > >> > > >> Hi, > > >> > > >> I setup a netscaler load balancer for sip traffic on Amazon EC2. Clients > >> packets are arrived to the backend servers over to the load balancer but > >> any responses cannot be arrived to clients. I see the responses on the > >> load balancer. > > >> > > >> I think there is a config problem for that but I don't know and did not > >> find any solutio
Re: updating & checking DNS zone files
For incrementing your zone's serial number, I usually include zsu to whatever editor I am using. It doesn't check the zone though. You can use the aforementioned named-checkzone, etc. for that. Paul On Jul 5, 2008, at 5:04 PM, [EMAIL PROTECTED] wrote: Quoting [EMAIL PROTECTED]: Apart from using Bernstein's tinydns, anyone have any scripts for looking for problems in zone files or for incrementing the serial number reliably? Check out BIND's named-checkzone and named-compilezone, depending on exactly what you are looking for. There are a number of command line parameters for fine tuning what you care about, and you can use the return value to determine if the zone is valid or not. As for the serial number, that is some simple scripting depending on what value you use for the serial number. -- Jason Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at [EMAIL PROTECTED], and delete the original message. Your cooperation is appreciated.
Re: ATT.net
Internap notified us that they were shutting down their peering with ATT (AS7018) at their Dallas facility and was asking them to investigate but there were no listed causes for it. At approximately 21:34 CDT on August 27th, 2008, we were notified that the link with ATT peer (AS 7018) in the DAL PNAP was experiencing loss. We have since shut down the peering and will asking ATT to investigate We will be following-up with ATT immediately to investigate this issue. This does not appear to be related to a hardware issue on the Internap side, so we will open a ticket to have ATT investigate their end immediately. I haven't seen anything over on the "outages" yet. Paul Aug 27, 2008, at 7:58 PM, [EMAIL PROTECTED] wrote: Any known issues across AT&T's network? Got a couple calls for some access issues, I'm seeing roughly 15% loss at a couple of paths at the AT&T network edge.
