Load Balancing on ACE Modules

hi,
Is it possible to load balance VIP hits on two ACE Modules in an active/active configuration. Or is it that only per FT group only single context could be active.
Regards.

You can have 1 context active on one ACE and the other context active on the other ACE.
If you have 2 Vip, you can have 1 vip belonging to one context and the other vip belonging to the other context.
Like this, you split the traffic between the 2 devices which allows you to handle more traffic than what 1 device could normally do.
If one device can handle all your traffic, I prefer to only have 1 active unit and 1 standby.
Easier to implement and troubleshoot.
Gilles.

Similar Messages

Debug commands for load-balancing on ACE

is possible to debug the load-balancing decision which is provided by ACE? For example: when the traffic comes to the VIP address I need to see which serverfarm is used for this traffic and which rserver was choosen for this traffic. Thank you.

no, you there is no debug to see the decision.
You could capture the queues infos and see what it contains but it is quite complicated.
A simple way is to capture a sniffer trace of front-end and backend simultaneously and you will be able to see where the traffic was loadbalanced.
You can also use the capture feature of the ACE module to get this info.
Gilles.

FTP Load Balancing on ACE 4710

Hi,
I have two ACEs working in ROUTED-MODE. In the servers there are HTTP content and FTP content.
- The load balancing is working in correct form.
Now, I have a problem: The client wants to performs a FTP request to server in Internet from server belong to server farm configured in the ACE.
In simple words, now the server belonging to the farm will be the client for the FTP server in Internet. The client can connect to the Internet FTP, he enter his username and password, but when he want to transfer data (command as ls, get, put) the connection is closed.
- When the client makes the FTP comes with the VIP address 200.29.72.226 to the intenet FTP.
- I have a capture when is performing the command "ls" and the connection was closed: The ACE stated:
12:42:11.079794 00:08:74:4e:d4:67 > 00:0b:fc:fe:1b:01, ethertype 802.1Q (0x8100), length 79: vlan 2, p 0, ethertype IPv4, IP (tos 0x0, ttl 128, id 28479, offset 0, flags [DF], length: 61) 10.3.2.1.1911 > 200.54.172.202.21: P [tcp sum ok] 37:58(21) ack 161 win 16400
12:42:11.079957 00:0b:fc:fe:1b:01 > 00:e0:b6:04:14:49, ethertype 802.1Q (0x8100), length 79: vlan 2, p 0, ethertype IPv4, IP (tos 0x0, ttl 128, id 28479, offset 0, flags [DF], length: 61, bad cksum a77 (->57b)!) 200.29.72.226.39292 > 200.54.172.202.21: P [bad tcp cksum 7d15 (->4ce)!] 37:58(21) ack 161 win 16400
12:42:11.080088 00:e0:b6:04:14:49 > 00:0b:fc:fe:1b:01, ethertype 802.1Q (0x8100), length 79: vlan 46, p 0, ethertype IPv4, IP (tos 0x0, ttl 128, id 28479, offset 0, flags [DF], length: 61) 200.54.172.202.21 > 200.29.72.226.39292: R [tcp sum ok] 161:182(21) ack 37 win 16400 [RST PORT 10,3,2,1,7,191\015\012]
12:42:11.079212 00:0b:fc:fe:1b:01 > 00:08:74:4e:d4:68, ethertype 802.1Q (0x8100), length 79: vlan 46, p 0, ethertype IPv4, IP (tos 0x0, ttl 128, id 28479, offset 0, flags [DF], length: 61, bad cksum 57b (->a77)!) 200.54.172.202.21 > 10.3.2.1.1911: R [bad tcp cksum 4d2 (->7d19)!] 161:182(21) ack 37 win 16400 [RST PORT 10,3,2,1,7,191\015\012]
I atached a diagram of situation and actual configuration.
I appreciate your help
Thanks and regards,
Jaime.

Thanks Gilles!
I applied the commands you told me. I performed laboratory tests and it worked fine.
Then I apply in the ACE of client and the results were positive.
Thanks you very much again.
Jaime.

Send Email issue using "Mail Server Load balancer" (Cisco ACE 20)

I have asked this question in SAP MII forum too but it appears issue could be in NetWeaver Mail API. Please let me know if someone have experienced this kind of issue or any suggestions.
The send email action was working file in MII with smtp mail server on port 25. Recently basis did a change in mail server ip address and they installed a new Load Balancer . The Load balancer is between SMTP and MII. After this change MII does not send email (unknown source error). now MII send email action has ip address or qualified path of Load balancer in MII send email configuration instead of direct ip address of SMTP server. Below is the error message in Net Weaver logs.
MII still sends email if direct ip address of email server provided instead of Email Load balancer but not through Load balancer .
Any suggestions ?
Could not authenticate mail account (Unknown Source)
[EXCEPTION]
javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:319)
at javax.mail.Service.connect(Service.java:169)
at javax.mail.Service.connect(Service.java:118)
at com.sap.xmii.storage.connections.MailConnection.sendMail(MailConnection.java:202)
at com.sap.xmii.bls.executables.actions.mail.MailActions.send(MailActions.java:223)
at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Switch.doExecute(Switch.java:131)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)

Hi Ahmed,
I don't have experience with Blackberry, but, as the document mentions, the first thing to do would be making sure that the connection timeout is set to something high enough
You can find more details on how to modify this value at the link below:
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/security/guide/tcpipnrm.html#wp1074289
I hope this helps
Daniel

Two isp load balancing on ACE(load balancer)

hi
I don't know much about load balancer(ACE).
Is this is possible to load balance two isp's on load balancer (ACE). If so, how i can do so , any configuration example, or cisco document.

Wrong forum, post in "Datacenter". You can move your posting with the Actions panel on the right.

Setting up additional load balancing on ACE 4710

I recently deployed ACE 4710 to load balance traffic to a group of web servers. I would like to add additional server farm(s) with different applications on them to ACE 4710 for load balancing the traffic. How can I best achieve this goal? I currently use 3 interfaces out of 4 interfaces (Server Side interface, Client side interface, and Failover interface). Do I need to use my last interface to set up for the new VIP address for a new server farm? Is virtualized service a possible solution? Thank you in advance.

You can configure trunking so that multiple vlans can exist.
Also note that the vip ip address does not have to belong to a subnet.
You could configure a static route on the upstream router pointing the traffic for the new vip to the interface ip address.
Gilles.

TCP SYNSEEN with load balancing Cisco ACE 4710

I have a Cisco ACE 4710 load balancing the traffic to two proxy servers, the configuration is the same since December 2012, but yesterday it stated to show SYNSEEN in the show conn command, and the hosts cannot browse. I think that means that the three-way-handshake is not complete.
If I bypass the ACE the hosts can browse without problems.
I have tested with another ACE appliance and the same configuration but the behaviour is the same.
I need help as soon as possible,
thanks,
I've attached the Show conn, show conn detail and show run.

Hi Cesar,
Thank you for your answer,
The issue was solved,
We were running an A3 software version, it seems to have a Bug so it doesn't show the NAT commands in the "show run", so when we made the configuration backup we didn't noticed it.
The ACE reloaded because an electrical failure so it losted the NAT config.
We just upgraded to an A4 version and also added a NAT/PAT to enable the communication between the Clients and the Proxy.
Regards,

Remote server load balancing by ACE

Hi,
We have ACE 4710 inslatted in 1-Arm mode deployed in DC where it is load balancing DC servers properly. Now my management wants to load balance the DR servers as well using the DC ACE. Is this possible??

Hi Partha,
I think that by DR you mean Disaster Recovery. As far as I know normally a DR plan does not use just the ACE but a combination of GSS+ACE is used.
Also in my opinion if you want to use the ACE to handle the outage on one site you still have a single point of failure due to the physical location of the ACE.
I don't know the specifics for your situation but as I said normally the combination GSS+ACE is preferred; the GSS can redirect clients' requests to different ACE systems, located in different physical locations.
So as long as the DR serverfarm is reachable from the ACE, from the technical point of view you should not have any problem ; then you should check if your choice indeed meets the requirements for a DR solution.
If you have an account team better would be to speak with them they can advise on which solution suits better your needs and if what you have in mind is one of the solutions you can implement.
I hope this clarifies more
Alessandro

Email send issue using "Mail Server Load balancer" (Cisco ACE 20)

Please let me know if someone have experienced this kind of issue or any suggestions.
The send email action was working file in MII with smtp mail server on port 25. Recently basis did a change in mail server ip address and they installed a new Load Balancer . The Load balancer is between SMTP and MII. After this change MII does not send email (unknown source error). now MII send email action has ip address or qualified path of Load balancer in MII send email configuration instead of direct ip address of SMTP server. Below is the error message in Net Weaver logs.
MII still sends email if direct ip address of email server provided but not through email Load balancer .
Any suggestions ?
Could not authenticate mail account (Unknown Source)
[EXCEPTION]
javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:319)
at javax.mail.Service.connect(Service.java:169)
at javax.mail.Service.connect(Service.java:118)
at com.sap.xmii.storage.connections.MailConnection.sendMail(MailConnection.java:202)
at com.sap.xmii.bls.executables.actions.mail.MailActions.send(MailActions.java:223)
at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Switch.doExecute(Switch.java:131)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Repeater.doExecute(Repeater.java:113)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:158)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteRequestHandler.processQueryRequest(XacuteRequestHandler.java:342)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteRequestHandler.QueryRequest(XacuteRequestHandler.java:135)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteConnector.doProcessRequest(XacuteConnector.java:86)
at com.sap.xmii.Illuminator.connectors.AbstractConnector.processRequest(AbstractConnector.java:83)
at com.sap.xmii.Illuminator.server.QueryEngine.run(QueryEngine.java:41)
at com.sap.xmii.Illuminator.services.handlers.IlluminatorService.processRequest(IlluminatorService.java:68)
at com.sap.xmii.Illuminator.services.ServiceManager.run(ServiceManager.java:68)
at com.sap.xmii.servlet.Illuminator.service(Illuminator.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:80)
at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:44)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.processServletRequest(ReportParser.java:610)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parseServletTag(ReportParser.java:276)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parseFile(ReportParser.java:154)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parse(ReportParser.java:119)
at com.sap.xmii.servlet.ReportServlet.service(ReportServlet.java:90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
Date:
2014-03-25
Time:
14:04:06:176
Category:
com.sap.xmii.storage.connections.MailConnection
Location:
com.sap.xmii.storage.connections.MailConnection
Application:
sap.com/xapps~xmii~ear
Thread:
Thread[HTTP Worker [@629095796],5,Dedicated_Application_Thread]
Data Source:
j2ee\cluster\server0\log\defaultTrace_00.trc
Arguments:
DSR Transaction:

Have a look at this thread please:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f11f3079-b04a-4a8e-b89e-d56eb0532c42/the-mail-could-not-be-sent-to-the-recipients-because-of-the-mail-server-failure-sending-mail-using?forum=sqldatabaseengine
Saeid Hasani [sqldevelop]

Problem with load balancing on ACE 4710

Hello.
I'm setting ACE4710.
I'm using DSR (Direct server return).
The load balancing cannot be distributed now.
I append the network configuration.
Could someone please help out?
THANKS!

Hello.
My problem has not been to have load balancing to rserver.
Connection is http://192.168.11.100:9080/ → ＮＧ（Connection error)
Connection is http://192.168.11.101:9080/ → ＯＫ（rserver1)
Connection is http://192.168.11.102:9080/ → ＯＫ（rserver2)
Even if "predictor ROUNDROBIN" is changed, it is the same.
Why cannot load balancing be done?
It is displayed that State is OPERATIONAL as a result of doing 'show rserver'.
Is this a correct display?

Class-maps used for load balancing on ACE

I am from CCS background and am trying to understand how the VIPs could be configured on an ACE module (using class maps).
I am looking for specific information for the following :
1. Will each VIP have a corresponding Service-policy on the VLAN Interface or can we club many VIPs (through policy-maps) onto a single service-policy entry on teh interface?
2. I could not find any cisco doco with the configuration examples for more than one VIP address and would please like to know some examples, if possible or could some one direct me to a doco with many VIP entries ?
- Should each VIP have a seperate class-map or can list them together?

You will have to configure L3/L4 class-maps for corresponding VIPs. You just need a single policy with n class-maps for n VIPS.
I am writing a sample that will hopefully help you on this
class-map match-all app1-vip
match virtual-address 10.1.1.1 tcp eq 80
class-map match-any app2-vip
match virtual-address 10.1.1.2 tcp eq 443
policy-map type loadbalance first-match L7app1
class class-default
server-farm App1-farm
policy-map type loadbalance first-match L7app2
class class-default
server-farm App2-farm
policy-map multi-match All-vips
class app1-vip
loadbalance vip inservice
loadbalance policy L7app1
loadbalance vip icmp-reply active
class app2-vip
loadbalance vip inservice
loadbalance policy L7app2
loadbalance vip icmp-reply active
int vlan 100
ip address 10.10.10.101 255.255.255.0
service-policy input All-vips
Syed Iftekhar Ahmed

Load Balancing with ACE using HTTP Header information

Hello,
I am trying to setup a class-map using http loadbalance match-all.
What I want to do is check for the HTTP Host and if it doesnot match the http referer than go to server farm A. if it does match then go to server farm B.
My problem is the host can be serveral different values as well as the referer. Can you setup varibales in the ACE so I can store the value from http host and compare it against http referer?
Thanks
Mike C.

It should be like this (If you want to use separate class maps for referrer & Host).
class-map type http loadbalance match-any site1-HostHDR
2 match http header Host header-value ".*site1.com"
class-map type http loadbalance match-any site1-Referer
2 match http header Referer header-value "http://site1.*"
class-map type http loadbalance match-any site2-HostHDR
2 match http header Host header-value ".*site2.com"
class-map type http loadbalance match-any site2-Referer
2 match http header Referer header-value "http://site2.*"
class-map type http loadbalance match-all Site1-policy
2 match class-map site1-HostHDR
3 match class-map site1-Referer
class-map type http loadbalance match-all Site2-policy
2 match class-map site2-HostHDR
3 match class-map site2-Referer
policy-map type loadbalance http first-match Site1
class Site1-policy
serverfarm SFarm-A
class Site2-policy
serverfarm SFarm-A
class class-default
serverfarm SFARm-B
Syed Iftekhar Ahmed

ACE 4710 server load balancing on ACE with routed model.

Hi experts,
Pls help me...i need server laod balance on ACE4710 with routed model sample configuration or configuration guide....thanks in advance....

Here you go

Want to know about ACE module in 6509 : load-balancing concept

Hi,
I am quite new in this field , where i need to configure and understand the concept of load-balancing through ACE.
In my existing network set-up , i have some application servers as well as some other servers where i am looking for load-balancing.
I have gone through some of the site and cisco site as well and i came across ACE module which can be installed in 6509 switch.
I have 6509 switch as well but before going for installing the ACE module I am keen to understand below things:
1) what is difference between CSM or any other product load-balancer and ACE module :
Gone through site as well , but not getting proper answer or comparison.
1) I have some of the server configured with clustering and getting one virtual IP, In this case , will ACE work ?
2) If suppose i go for configuring different IP address with all server IP :
How do i achieve it ?
3) what is Virtual IP concept in ACE because i do not have and other ACE module then why do i need virtual IP ?
4) will the load-balancing happens based on destination based or session based ?
Please share the knowledge. It would be great help for me to go ahead with ACE and configure it and understand all the application ?

Hello,
1) what is difference between CSM or any other product load-balancer and ACE module :
There are several differences but to say simply, you get higher performance and more features with ACE module/appliance comparing others.
One big difference is that with ACE seriese, you can configure multiple contexts on one box (virtual load-balancers on one box) that makes us possible to provide a virtual load-balancer to a customer. In that way, the customer can access and makes changes on only the virtual box. You can split management domain for each customers. Also using contexts, you can assign certain resources available on the hardware for each contexts according to their service contract.
ACE serise has specific hardware chip for supporting SSL termination but some others do not.
For instance, you need a CSM-S, or a CSM and a SSL module to terminate SSL.
The other thing I should mention is that our most recent product is ACE serise that means it has longer product roadmap.
Let me try clarifying your other questions.
3) what is Virtual IP concept in ACE because i do not have and other ACE module then why do i need virtual IP ?
4) will the load-balancing happens based on destination based or session based ?
I think I'd better to put 3) and 4) first.
Virtual ip address (VIP) is the address to which client accesses.
VIP is tied with a serverfarm or serverfarms, in a serverfarm one or multiple rservers can be configured.
"serverfarm" is a group of "rservers".
"rserver" means real-server that has an ip address and processes transactions.
When a client accesses to the VIP, ACE picks up a rserver according to algorithm.
If you configure a VIP that is tied with a serverfarm where only one rsever is configured, client accesses to the virtual ip address are
all forwarded to the rserver.
If you configure a VIP that is tied with a serverfarm where multiple rsevers are configured, client accesses to the virtual ip address are
balanced among those rservers.
If you configure multiple VIPs, client accesses to those VIPs are forwareded to corresponding rservers according to configuration.
1) I have some of the server configured with clustering and getting one virtual IP, In this case , will ACE work ?
ACE load-balances connections to configured rservers.
If the clustered servers are sharing one virtual ip address and you configure the virtual ip address as a rserver, all connections are
sent to the virtual ip address. That is not "load-balancing" on ACE... You need multiple rservers to which ACE load-balances connections.
2) If suppose i go for configuring different IP address with all server IP :
How do i achieve it ?
You can configure those ip addresses as rserver ip address.
Multiple rservers are tied into a group, "serverfarm".
I'm not certain about your culstered servers but I guess you can configure each ip addresses in the culster as rservers.
Then put those rservers in a serverfarm.Client accesses to a virtual ip address configured on ACE for the serverfarm.
This way connections are load-balanced among those rservers depending on load-balancing algorithm you choose.
Above is just an overveiw. ACE gives you granular control not mentioned above.
I can provide more specific information if you tell me details of what you are trying to archive with ACE.
Regards,
Kimihito.

Regarding ACE load balancing

Hi,
I have one server application with two physical servers clustered with one virtual IP address . I have total six ip addresses for one server : details are given below
Cluster IP’s :
Node 1 :
NIC 1 : 10.10.x.x : physical IP address
NIC 2 : 172.16.x.x : heartbeat address used in between server
Node 2 :
NIC 1 : 10.10.x.x : physical ip address
NIC 2 : 172.16.x.x : heartbeat address used in between server
Cluster IP : 10.10.x.x : clustered IP address used to access server
SQL IP : 10.10.x.x : clustered IP address used to access SQL application .
now i want to achieve server load-balancing using ACE module. Please suggest to me fulfil this requirement. how to do this ?
whether i need to remove the virtual IP and directly bind two physical ip to ace virtual ip add.
How do i check ace server load-balancing configuration with live server .... do we have any tool to check the packet behaviour to confirm that load-balancing is happening properly in between two physical servers :
Please guide me and share the knowledge .....................

Hi Vinod,
You are correct. In order to achieve load-balancing with an ACE blade, you need to configure the addresses of the two severs separately. If you look at the documentation page on cisco.com for ACE (http://www.cisco.com/en/US/products/ps6906/tsd_products_support_model_home.html) you will find sample configuration for the most commont topologies.
As for how to verify if the load-balancing is working correctly, you can use the command "show serverfarm ", which will list you all the servers in a serverfarm, along with the current and total connection numbers for each of them.

Load Balancing on ACE Modules

Similar Messages

Maybe you are looking for