Cisco Ceasing Development Of Load-Balancer Products

      Has anybody heard of Cisco's ceasing on developing the ACEs past ACE30?
Thanks.

All-
At this current point in time, the ACE30 and ACE4710 will continue to be developed through A5(3.X) code as part of the planned lifecycle of those products.  Any of the other future products including vACE, RISE, Nexus based Modules, appliances, etc. currently have no ETA, nor has any lifecycle ever been defined as they are not released products.  There is also no official Cisco response at this point in time to the rumors of cancellation, holds, etc. despite the hinting of certain articles to "confirmed by Cisco resources" based comments. 
Your best avenue for information is to talk with your local Cisco sales representative or account manager.  They may have more specific information pertaining to questions at a per-product/per-scenario level. As well, they will have the ability to help you plan your future deployments and designs queries accordingly.
Regards,
Chris Higgins
Cisco ANS Escalation Team

Similar Messages

  • Cisco CSS 11503 Arrowpoint/Load Balance question

    I am troubleshooting an issue with my 11503.  I am running version 07.40.0.04. I have it configured as follows:
      content upcadtoa-rule
        add service cadtoa-wls1-e0
        add service cadtoa-wls1-e1
        add service cadtoa-wls2-e0
        add service cadtoa-wls2-e1
        add service cadtoa-wls3-e0
        add service cadtoa-wls3-e1
        add service cadtoa-wls4-e0
        add service cadtoa-wls4-e1
        add service cadtoa-wls5-e0
        add service cadtoa-wls5-e1
        add service cadtoa-wls6-e0
        add service cadtoa-wls6-e1
        arrowpoint-cookie expiration 00:00:15:00
        protocol tcp
        port 8001
        advanced-balance arrowpoint-cookie
        redundant-index 2
        vip address 172.30.194.195 range 2
        arrowpoint-cookie name TOA
        active
    However, the load-balancing across the servers does not seem to be doing much balancing.  One of those servers is getting hit with 5 times as much traffic as another and another server is lucky to get a connection at all.  With the cookie expiration set, one would think that this would all balance out over time.
    I just came across this information from Cisco and I am wondering if it is relevant:
    If you configure a balance or advanced-balance method on a content rule that requires the TCP protocol for Layer 5 (L5) spoofing, you should configure a default URL string, such as url "/*". The addition of the URL string forces the content rule to become an L5 rule and ensures L5 load balancing or stickiness. If you do not configure a default URL string, unexpected results can occur.
    In the following configuration example, if you configure a Layer 3 (L3) content rule with an L5 balance method, the CSS performs L5 load balancing, but will reject UDP packets.
    content testing
    vip address 192.168.128.131
    add service s1
    balance url
    active
    The balance url method is an L5 load-balancing method in which the CSS must spoof the connection and examine the HTTP GET content request to perform load balancing. The CSS rejects the UDP packet sent to this rule because a UDP connection cannot be L5. Though the CSS allows this rule configuration, its expected behavior would be more clear if you promote the rule to L5 by configuring the url "/*" command.
    In the next example, if you configure an L3 content rule with an L5 advanced-balance method, L5 stickiness will not work as expected.
    content testing
    vip address 192.168.128.131
    add service s1
    advanced-balance arrowpoint-cookie
    active
    The advanced-balance arrowpoint-cookie method causes the CSS to spoof the connection, however, the CSS still marks it as an L3 rule. Thus, the CSS does not insert the generated cookie and the rule defaults to L3 stickiness (sticky-srcip). You must configure a URL like url "/*" to promote this rule to L5, ensuring that L5 stickiness works as expected.
    Thanks in advance for any help you can give.  The thing is not down, it is just balancing strangely causing application performance issues.
    James

    Hey James,
    You will need to suspend the content rule in order to add the url statement.  This will cause a quick downtime until the content rule is activated again.  I have shown below the commands to add the statement.  Perhaps you can create your commands in a Notepad file, then paste them all in so they execute quickly to minimize your downtime:
      content MY-SITE
        vip address 10.201.130.140
        port 80
        protocol tcp
        add service MY-SERVER
        active
    CSS11503# config t
    CSS11503(config)# owner TEST
    CSS11503(config-owner[TEST])# content MY-SITE
    CSS11503(config-owner-content[TEST-MY-SITE])# url "/*"
    %% Attribute may not be modified on active rule
    CSS11503(config-owner-content[TEST-MY-SITE])# suspend
    CSS11503(config-owner-content[TEST-MY-SITE])# url "/*"
    CSS11503(config-owner-content[TEST-MY-SITE])# active
    CSS11503(config-owner-content[TEST-MY-SITE])# exit
    CSS11503(config-owner[TEST])# exit
    CSS11503(config)# exit
    CSS11503# show run
      content MY-SITE
        vip address 10.201.130.140
        add service MY-SERVER
        port 80
        protocol tcp
       url "/*"       <--------
        active
    Hope this helps,
    Sean

  • Cisco 1921 Dual ADSL Load Balancing/Failover?

    Hello,
    We have purchased a Cisco 1921 with twin ADSL after advice from a Cisco sales rep. However I am having trouble working out the load balancing/fail over config for the device.
    I would like traffic to balance over both ADSL lines and if one goes down not to interrupt connectivity.
    I had a look at ppp multilink but I am unsure our ISP (BT) support this?
    This is my current config which I think only one ADSL line is being used. Some input would be appreciated
    Robbie
    ! Last configuration change at 13:18:34 UTC Tue Mar 29 2011
    version 15.0
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname xxxxxx
    boot-start-marker
    boot-end-marker
    no logging buffered
    enable secret 5 xxxxx
    enable password xxxx
    no aaa new-model
    no ipv6 cef
    ip source-route
    ip cef
    ip name-server 194.74.65.68
    ip name-server 194.72.0.114
    multilink bundle-name authenticated
    crypto pki trustpoint TP-self-signed-xxxxxx
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-xxxxx0
    revocation-check none
    rsakeypair TP-self-signed-xxxxx!
    crypto pki certificate chain TP-self-signed-xxxxxx
    certificate self-signed 02 nvram:IOS-Self-Sig#4.cer
    license udi pid CISCO1921/K9 xxxxx
    username admin privilege 15 secret 5 xxxxxxxxxx/
    interface GigabitEthernet0/0
    description lan$ETH-LAN$
    ip address 10.0.8.1 255.255.248.0
    ip nat inside
    ip virtual-reassembly
    duplex auto
    speed auto
    interface GigabitEthernet0/1
    no ip address
    shutdown
    duplex auto
    speed auto
    interface ATM0/0/0
    no ip address
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    no atm ilmi-keepalive
    dsl operating-mode adsl2
    interface ATM0/0/0.1 point-to-point
    description $ES_WAN$$FW_OUTSIDE$
    ip flow ingress
    pvc 0/38
      encapsulation aal5mux ppp dialer
      dialer pool-member 1
    interface ATM0/1/0
    no ip address
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    no atm ilmi-keepalive
    dsl operating-mode adsl2
    interface ATM0/1/0.1 point-to-point
    description $ES_WAN$$FW_OUTSIDE$
    ip flow ingress
    pvc 0/38
      encapsulation aal5mux ppp dialer
      dialer pool-member 1
    interface Dialer0
    mtu 1483
    ip address negotiated
    ip access-group spalding in
    ip access-group spalding out
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    ip nat outside
    ip virtual-reassembly
    encapsulation ppp
    dialer pool 1
    dialer-group 1
    ppp authentication chap callin
    ppp chap hostname xxxxx
    ppp chap password 0 xxxxx
    ppp multilink
    ppp multilink links minimum 2
    ppp multilink fragment disable
    ppp timeout multilink link add 2
    no cdp enable
    interface Dialer1
    mtu 1483
    ip address negotiated
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    ip nat outside
    ip virtual-reassembly
    encapsulation ppp
    dialer pool 1
    dialer-group 1
    ppp authentication chap callin
    ppp chap hostname xxxxx
    ppp chap password 0 xxxxx
    ppp link reorders
    ppp multilink
    ppp multilink links minimum 2
    ppp multilink fragment disable
    ppp timeout multilink link add 2
    no cdp enable
    ip forward-protocol nd
    no ip http server
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip nat inside source list 1 interface Dialer0 overload
    ip nat inside source static tcp 10.0.15.201 3389 interface Dialer0 3389
    ip nat outside source static tcp 195.194.75.218 3389 10.0.15.200 3389 extendable
    ip route 0.0.0.0 0.0.0.0 Dialer0
    access-list 1 remark INSIDE_IF=GigabitEthernet0/0
    access-list 1 permit 10.0.0.0 0.254.255.255
    dialer-list 1 protocol ip permit
    control-plane
    line con 0
    line aux 0
    line vty 0 4
    privilege level 15
    login local
    transport input telnet ssh
    line vty 5 15
    privilege level 15
    login local
    transport input telnet ssh
    scheduler allocate 20000 1000
    end

    Hi,
    Can anyone help me with this config?  not very reliable.
    Building configuration...
    Current configuration : 17349 bytes
    ! Last configuration change at 06:08:06 UTC Sun Apr 5 2015 by Shawn
    version 15.4
    no service pad
    service tcp-keepalives-in
    service tcp-keepalives-out
    service timestamps debug datetime msec localtime show-timezone
    service timestamps log datetime msec localtime show-timezone
    service password-encryption
    service sequence-numbers
    hostname Router
    boot-start-marker
    boot system flash0:c2900-universalk9-mz.SPA.154-3.M2.bin
    boot-end-marker
    security authentication failure rate 3 log
    security passwords min-length 6
    logging buffered 51200
    logging console critical
    enable secret 5 $1$sNeA$GB6.SMrcsxPf51tK2Eo9Z.
    aaa new-model
    aaa authentication login local_authen local
    aaa authorization exec local_author local
    aaa session-id common
    no ip source-route
    ip port-map user-protocol--8 port udp 3392
    ip port-map user-protocol--9 port tcp 3397
    ip port-map user-protocol--2 port udp 3391
    ip port-map user-protocol--3 port tcp 14000
    ip port-map user-protocol--1 port tcp 3391
    ip port-map user-protocol--6 port udp 3394
    ip port-map user-protocol--7 port tcp 3392
    ip port-map user-protocol--4 port udp 14100
    ip port-map user-protocol--5 port tcp 3394
    ip port-map user-protocol--10 port udp 3397
    ip dhcp excluded-address 192.168.1.1 192.168.1.49
    ip dhcp excluded-address 192.168.10.1 192.168.10.49
    ip dhcp pool DHCP_POOL1
     import all
     network 192.168.1.0 255.255.255.0
     dns-server 139.130.4.4 203.50.2.71
     default-router 192.168.1.1
     lease infinite
    ip dhcp pool ccp-pool1
     import all
     network 192.168.10.0 255.255.255.0
     dns-server 139.130.4.4 203.50.2.71
     default-router 192.168.10.1
     lease infinite
    no ip bootp server
    ip host SHAWN-PC 192.168.1.10
    ip host DIAG 192.168.1.5
    ip host MSERV 192.168.1.13
    ip name-server 139.130.4.4
    ip name-server 203.50.2.71
    ip cef
    ip cef load-sharing algorithm include-ports source destination
    no ipv6 cef
    multilink bundle-name authenticated
    cts logging verbose
    crypto pki trustpoint TP-self-signed-1982477479
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-1982477479
     revocation-check none
     rsakeypair TP-self-signed-1982477479
    license udi pid 
    license boot module c2900 technology-package securityk9
    license boot module c2900 technology-package datak9
    redundancy
    controller VDSL 0/0/0
     operating mode adsl2+
    controller VDSL 0/1/0
     operating mode adsl2+
    no cdp run
    track timer interface 5
    track 1 interface Dialer0 ip routing
     delay down 15 up 10
    track 2 interface Dialer1 ip routing
     delay down 15 up 10
    ip tcp synwait-time 10
    ip ssh time-out 60
    ip ssh authentication-retries 2
    class-map type inspect match-all sdm-nat-user-protocol--7-1
     match access-group 104
     match protocol user-protocol--7
     match access-group 102
    class-map type inspect match-all sdm-nat-user-protocol--4-2
     match access-group 101
     match protocol user-protocol--4
    class-map type inspect match-all sdm-nat-user-protocol--6-1
     match access-group 103
     match protocol user-protocol--6
    class-map type inspect match-all sdm-nat-user-protocol--5-1
     match access-group 103
     match protocol user-protocol--5
    class-map type inspect match-all sdm-nat-user-protocol--4-1
     match access-group 102
     match protocol user-protocol--4
    class-map type inspect match-all sdm-nat-user-protocol--7-2
     match access-group 101
     match protocol user-protocol--7
    class-map type inspect match-all sdm-nat-user-protocol--3-1
     match access-group 102
     match protocol user-protocol--3
    class-map type inspect match-all sdm-nat-user-protocol--2-1
     match access-group 101
     match protocol user-protocol--2
    class-map type inspect match-all sdm-nat-user-protocol--1-2
     match access-group 102
     match protocol user-protocol--1
    class-map type inspect match-all sdm-nat-user-protocol--1-1
     match access-group 101
     match protocol user-protocol--1
    class-map type inspect match-all sdm-nat-user-protocol--2-2
     match access-group 102
     match protocol user-protocol--2
    class-map type inspect match-all sdm-nat-user-protocol--3-2
     match access-group 101
     match protocol user-protocol--3
    class-map type inspect match-all sdm-nat-user-protocol--8-2
     match access-group 101
     match protocol user-protocol--8
    class-map type inspect match-all sdm-nat-user-protocol--9-2
     match access-group 104
     match protocol user-protocol--9
    class-map type inspect match-any ccp-skinny-inspect
     match protocol skinny
    class-map type inspect match-all sdm-nat-user-protocol--9-1
     match access-group 101
     match protocol user-protocol--9
     match access-group 104
    class-map type inspect match-all sdm-nat-user-protocol--8-1
     match access-group 104
     match protocol user-protocol--8
     match access-group 102
    class-map type inspect match-any ccp-h323nxg-inspect
     match protocol h323-nxg
    class-map type inspect match-any ccp-cls-icmp-access
     match protocol icmp
     match protocol tcp
     match protocol udp
    class-map type inspect match-all sdm-nat-user-protocol--10-2
     match access-group 104
     match protocol user-protocol--10
    class-map type inspect match-all sdm-nat-user-protocol--10-1
     match access-group 101
     match protocol user-protocol--10
     match access-group 104
    class-map type inspect match-any ccp-h225ras-inspect
     match protocol h225ras
    class-map type inspect match-any ccp-h323annexe-inspect
     match protocol h323-annexe
    class-map type inspect match-any ccp-cls-insp-traffic
     match protocol pptp
     match protocol dns
     match protocol ftp
     match protocol https
     match protocol icmp
     match protocol imap
     match protocol pop3
     match protocol netshow
     match protocol shell
     match protocol realmedia
     match protocol rtsp
     match protocol smtp
     match protocol sql-net
     match protocol streamworks
     match protocol tftp
     match protocol vdolive
     match protocol tcp
     match protocol udp
    class-map type inspect match-all SDM_GRE
     match access-group name SDM_GRE
    class-map type inspect match-any ccp-h323-inspect
     match protocol h323
    class-map type inspect match-all ccp-invalid-src
     match access-group 100
    class-map type inspect match-any ccp-sip-inspect
     match protocol sip
    class-map type inspect match-all ccp-protocol-http
     match protocol http
    class-map type inspect match-any CCP_PPTP
     match class-map SDM_GRE
    class-map type inspect match-all ccp-insp-traffic
     match class-map ccp-cls-insp-traffic
    class-map type inspect match-all ccp-icmp-access
     match class-map ccp-cls-icmp-access
    policy-map type inspect ccp-inspect
     class type inspect ccp-invalid-src
      drop log
     class type inspect ccp-protocol-http
      inspect
     class type inspect ccp-insp-traffic
      inspect
     class type inspect ccp-sip-inspect
      inspect
     class type inspect ccp-h323-inspect
      inspect
     class type inspect ccp-h323annexe-inspect
      inspect
     class type inspect ccp-h225ras-inspect
      inspect
     class type inspect ccp-h323nxg-inspect
      inspect
     class type inspect ccp-skinny-inspect
      inspect
     class class-default
      drop
    policy-map type inspect sdm-pol-NATOutsideToInside-1
     class type inspect sdm-nat-user-protocol--1-1
      inspect
     class type inspect sdm-nat-user-protocol--2-1
      inspect
     class type inspect sdm-nat-user-protocol--3-1
      inspect
     class type inspect sdm-nat-user-protocol--4-1
      inspect
     class type inspect sdm-nat-user-protocol--5-1
      inspect
     class type inspect sdm-nat-user-protocol--6-1
      inspect
     class type inspect sdm-nat-user-protocol--7-1
      inspect
     class type inspect sdm-nat-user-protocol--8-1
      inspect
     class type inspect sdm-nat-user-protocol--9-1
      inspect
     class type inspect sdm-nat-user-protocol--10-1
      inspect
     class type inspect CCP_PPTP
      pass
     class type inspect sdm-nat-user-protocol--7-2
      inspect
     class type inspect sdm-nat-user-protocol--8-2
      inspect
     class type inspect sdm-nat-user-protocol--1-2
      inspect
     class type inspect sdm-nat-user-protocol--2-2
      inspect
     class type inspect sdm-nat-user-protocol--9-2
      inspect
     class type inspect sdm-nat-user-protocol--10-2
      inspect
     class type inspect sdm-nat-user-protocol--3-2
      inspect
     class type inspect sdm-nat-user-protocol--4-2
      inspect
     class class-default
      drop log
    policy-map type inspect ccp-permit
     class class-default
      drop
    policy-map type inspect ccp-permit-icmpreply
     class type inspect ccp-icmp-access
      inspect
     class class-default
      pass
    zone security in-zone
    zone security out-zone
    zone-pair security ccp-zp-self-out source self destination out-zone
     service-policy type inspect ccp-permit-icmpreply
    zone-pair security ccp-zp-in-out source in-zone destination out-zone
     service-policy type inspect ccp-inspect
    zone-pair security ccp-zp-out-self source out-zone destination self
     service-policy type inspect ccp-permit
    zone-pair security sdm-zp-NATOutsideToInside-1 source out-zone destination in-zone
     service-policy type inspect sdm-pol-NATOutsideToInside-1
    interface Null0
     no ip unreachables
    interface Embedded-Service-Engine0/0
     no ip address
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     shutdown
    interface GigabitEthernet0/0
     description $ETH-LAN$
     ip address 192.168.10.1 255.255.255.0
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     duplex auto
     speed auto
     no mop enabled
    interface GigabitEthernet0/1
     no ip address
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     shutdown
     duplex auto
     speed auto
     no mop enabled
    interface ATM0/0/0
     no ip address
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     no atm ilmi-keepalive
    interface ATM0/0/0.1 point-to-point
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     pvc 8/35
      encapsulation aal5mux ppp dialer
      dialer pool-member 1
    interface ATM0/0/0.2 point-to-point
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
    interface Ethernet0/0/0
     no ip address
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     shutdown
     no mop enabled
    interface ATM0/1/0
     no ip address
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     no atm ilmi-keepalive
    interface ATM0/1/0.1 point-to-point
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     pvc 8/35
      encapsulation aal5mux ppp dialer
      dialer pool-member 2
    interface Ethernet0/1/0
     no ip address
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip flow ingress
     shutdown
     no mop enabled
    interface GigabitEthernet0/3/0
     no ip address
    interface GigabitEthernet0/3/1
     no ip address
    interface GigabitEthernet0/3/2
     no ip address
    interface GigabitEthernet0/3/3
     no ip address
    interface GigabitEthernet0/3/4
     no ip address
    interface GigabitEthernet0/3/5
     no ip address
    interface GigabitEthernet0/3/6
     no ip address
    interface GigabitEthernet0/3/7
     no ip address
    interface Vlan1
     description $FW_INSIDE$
     ip address 192.168.1.1 255.255.255.0
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip nbar protocol-discovery
     ip flow ingress
     ip nat inside
     ip virtual-reassembly in
     zone-member security in-zone
    interface Dialer0
     description $FW_OUTSIDE$
     ip address negotiated
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip nbar protocol-discovery
     ip flow ingress
     ip nat outside
     ip virtual-reassembly in
     zone-member security out-zone
     encapsulation ppp
     dialer pool 1
     dialer-group 1
     ppp authentication chap pap callin
     ppp chap hostname [email protected]
     ppp chap password 7 1444405858557A
     ppp pap sent-username [email protected] password 7 135645415F5D54
     ppp multilink
    interface Dialer1
     description $FW_OUTSIDE$
     ip address negotiated
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip nbar protocol-discovery
     ip flow ingress
     ip nat outside
     ip virtual-reassembly in
     zone-member security out-zone
     encapsulation ppp
     dialer pool 2
     dialer-group 2
     ppp authentication chap pap callin
     ppp chap hostname [email protected]
     ppp chap password 7 01475E540E5D55
     ppp pap sent-username [email protected] password 7 055F5E5F741A1D
     ppp multilink
    router eigrp as#
    router eigrp 10
     network 192.168.1.1 0.0.0.0
    router rip
     version 2
     network 192.168.1.0
     no auto-summary
    ip forward-protocol nd
    ip http server
    ip http access-class 3
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip dns server
    ip nat inside source static tcp 192.168.1.10 3392 interface Dialer1 3392
    ip nat inside source static udp 192.168.1.10 3392 interface Dialer1 3392
    ip nat inside source static tcp 192.168.1.35 3391 interface Dialer0 3391
    ip nat inside source static udp 192.168.1.35 3391 interface Dialer0 3391
    ip nat inside source static tcp 192.168.1.5 3394 interface Dialer0 3394
    ip nat inside source static udp 192.168.1.5 3394 interface Dialer0 3394
    ip nat inside source static tcp 192.168.1.17 3397 interface Dialer0 3397
    ip nat inside source static udp 192.168.1.17 3397 interface Dialer0 3397
    ip nat inside source static tcp 192.168.1.10 14000 interface Dialer0 14000
    ip nat inside source static udp 192.168.1.10 14100 interface Dialer0 14100
    ip nat inside source route-map ADSL0 interface Dialer0 overload
    ip nat inside source route-map ADSL1 interface Dialer1 overload
    ip route 0.0.0.0 0.0.0.0 Dialer0 track 1
    ip route 0.0.0.0 0.0.0.0 Dialer1 track 2
    ip access-list extended NAT
     remark CCP_ACL Category=18
     permit ip 192.0.0.0 0.255.255.255 any
    ip access-list extended SDM_GRE
     remark CCP_ACL Category=1
     permit gre any any
     remark CCP_ACL Category=1
    ip access-list extended STATIC-NAT-SERVICES
     permit ip host 192.168.1.35 any
     permit ip host 192.168.1.5 any
     permit ip host 192.168.1.10 any
     permit ip host 192.168.1.17 any
    dialer-list 1 protocol ip permit
    dialer-list 2 protocol ip permit
    route-map ADSL0 permit 10
     match ip address NAT
     match interface Dialer0
    route-map ADSL1 permit 10
     match ip address NAT
     match interface Dialer1
    access-list 1 remark INSIDE_IF=Vlan1
    access-list 1 remark CCP_ACL Category=2
    access-list 1 permit 192.168.1.0 0.0.0.255
    access-list 2 remark HTTP Access-class list
    access-list 2 remark CCP_ACL Category=1
    access-list 2 permit 192.168.1.0 0.0.0.255
    access-list 2 deny   any
    access-list 2 remark HTTP Access-class list
    access-list 2 remark CCP_ACL Category=1
    access-list 3 remark HTTP Access-class list
    access-list 3 remark CCP_ACL Category=1
    access-list 3 permit 192.168.1.0 0.0.0.255
    access-list 3 deny   any
    access-list 10 remark INSIDE_IF=NAT
    access-list 10 remark CCP_ACL Category=2
    access-list 10 permit 192.168.1.0 0.0.0.255
    access-list 100 remark CCP_ACL Category=128
    access-list 100 permit ip host 255.255.255.255 any
    access-list 100 permit ip 127.0.0.0 0.255.255.255 any
    access-list 100 permit ip 139.130.227.0 0.0.0.255 any
    access-list 100 permit ip 203.45.106.0 0.0.0.255 any
    access-list 101 remark CCP_ACL Category=0
    access-list 101 permit ip any host 192.168.1.10
    access-list 101 remark CCP_ACL Category=0
    access-list 101 permit ip any host 192.168.1.35
    access-list 101 permit tcp any any eq www
    access-list 102 remark CCP_ACL Category=0
    access-list 102 permit ip any host 192.168.1.35
    access-list 102 remark CCP_ACL Category=0
    access-list 102 permit ip any host 192.168.1.10
    access-list 103 remark CCP_ACL Category=0
    access-list 103 permit ip any host 192.168.1.5
    access-list 104 remark CCP_ACL Category=0
    access-list 104 permit ip any host 192.168.1.17
    control-plane
    banner login ^CCE-Rescue Systems^C
    line con 0
     login authentication local_authen
     transport output telnet
    line aux 0
     login authentication local_authen
     transport output telnet
    line 2
     no activation-character
     no exec
     transport preferred none
     transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
     stopbits 1
    line vty 0 4
     authorization exec local_author
     login authentication local_authen
     transport input telnet ssh
    line vty 5 15
     authorization exec local_author
     login authentication local_authen
     transport input telnet ssh
    scheduler allocate 20000 1000
    end
    Thanks
    Shawn

  • Cisco RV042 - Dual Wan Load Balancing - Secure Site (HTTPS) Trouble

    PID VID :
    RV042 V03
    Firmware Version :
    v4.0.0.07-tm (Aug 19 2010 19:19:50)
    Ever since I setup my RV042 with load balancing using the Dual Wan system I have had trouble staying connected to some secure sites. After doing some searching I found that the potential issue is the IP change mid session.
    "http://www.broadbandreports.com/forum/r25537589-Cisco-RV042-can-not-use-load-balancing-for-some-web-sites"
    Although my interface is significantly different I was able to find the same area in my RV042 admin area however, it doesn't seem to work.
    System Management
    > Dual Wan
    In Wan 1 & Wan 2 I have HTTPS and HTTPS Secondary all forwarded to use Wan 2 under Protocol Binding
    This however has not managed to do anything at all for my network and every computer conneceted experiences the same HTTPS irregularities at some websites.
    I'm sure I must be doing something wrong, but I don't know what it is.
    Both incoming connections are from the same service provider although the plans are different.
    Any help with this would greatly help me stop losing my mind trying to fight with my website control panel for 10 minutes to just login and get something done.
    Thanks

    Any ideas or advice from anyone?

  • Cisco MDS Port channel load balancing

    A customer recently asked an interesting question about exchange based load balancing on an FC port channel. The platform is UCS with an 8 and 16 port channel per fabric interconnect on two separate UCS domains. The application is Oracles data warehousing which has been known to saturate 4 x 8gb fc links. Since the balancing method is exchange based what constitutes the start and end of an exchange? We are trying to avoid a condition where and intense read write conversation locks to a single link in the port channel and not spread across 8/16 links. Where can I find more information about exchange based routing protocol or how should I go about managing extreme io in a converged infrastructure.

    The default loadbalance method on FI and MDS is src-dst-ox-id based. Note that loadbalancing is done by a device on *outgoing traffic*. FI and MDS do not have to negotiate anything here. Technically, one device can do src-dst-id based while the other can use src-dst-ox-id. However, in your case there is no reason for such a change.
    As I wrote before, If all of the links in the port-channel are touching the max capacity, you should recommend your customer to increase links in the bundle (max 16) or upgrade to 16G links. If few of the links are heavily utilized while other links in the same port-channel are under utilized, you may want to check the application or HBA for capability of breaking down the large reads/writes under smaller exchanges. If no traffic is going on few of the links at all, then I would suspect UCS to FI pinning as well.

  • Cisco switches and virtual ip address(load balancing address) on xenapp portals

    Hi I am quite new in configuring cisco switches and stumble across an issue after installing xenapp7.6 with load balanced portal to the ddc`s
    It seems i only can ping or get access to portal if using real ip address behind cisco switch from other subnets in my network.
    I can ping ddc01 and ddc02 and connect to the portal with http without problem. However when i triy to access the load balancing address of the ddc`s
    it wont answer to ping or http
    In same subnett it is no problem connecting to the load balancing address of the ddc`s, but in loactions on other subnets i only can access real server ip
    eks
    dd01   192.168.1.4    ok ping and access behind cisco switch from subnets
    ddc02 192.168.1.5   ok to ping  access behind cisco switch from subnets
    load balancing for both ddc 192.168.1.6 not able to get answer og access from subnets, only in same subnett
    Is there any way to configure switch to access the load balancing address of the ddc`s ?
    Regards
    Pål Arne Røberg

    Wrong forum. This forum is dedicated to feedback related to CSC framework itself. You should not wish for response here.
    Moved by moderator, no longer apply.

  • Load Balancing b/w two cisco router

    Hello Friends,
    Please advise me,We are using two Cisco Routers with F5 Load balancer,
    Router A (Cisco 2811) has one ISP configured
    Router B (Cisco 3825) has the other ISP configured
    ISP on Router A has 5 Mbps Bandwidth
    ISP on Router B has 10 Mbps Bandwidth
    My Doubt is if the load balancer is down,how to utilize the ISP (or) How to divert the connection ?
    Here i have attached my N/w diagram for ur reference..........
    Can someone solve my question.............please
    Thank you.

    Hi Mohamed,
    With default routing in use you can just configure one default route on each router   But it would only do load sharing not load balancing.
    PFR(performance routing) is a better solution but have never tried with two diffferent router series. Also need to validate if the router series you are using supports PFR.
    Regards,
    Sathvik K V

  • Difference between Clustering and Load balancing

              What is the difference between Clustering and Load balancing?
              For example, We use Cisco Arrowpoint to do load balancing and it works fine for 3
              Sun solaris boxes/WebLogic 6.1 SP1.
              So what is the value addition to buy clustering license?
              Thanks
              Selvaraj
              

    Hi.
              Among other things, clustering allows you to share app data (such as http session
              data) across cluster members, allowing you to failover should one cluster member
              crash.
              If your app is stateless then this doesn't mean much - load balancing alone would
              probably be ok for you.
              Regards,
              Michael
              Selvaraji wrote:
              > What is the difference between Clustering and Load balancing?
              >
              > For example, We use Cisco Arrowpoint to do load balancing and it works fine for 3
              > Sun solaris boxes/WebLogic 6.1 SP1.
              >
              > So what is the value addition to buy clustering license?
              >
              > Thanks
              >
              > Selvaraj
              Michael Young
              Developer Relations Engineer
              BEA Support
              

  • Cluster/load balance weblogic using L4 switch like Alteon

    Can I install weblogic as a standalone server on 2 or more server and
              cluster/load balance weblogic using a hardware balancer like Alteon Layer4
              switch (of course I will use a centralised storage to maintain a single copy
              of data which will eliminate syncronizing problem among servers)?
              BTW, Alteon can support persistent binding. The reason to use a Layer 4
              switch is that it is very fast, and this will make the application server
              layer transparent to client, the client can think this is a single server
              (it don't need to know whether there are 5 weblogic servers or 20 weblogic
              servers behind switch), and hardware are more reliable, sacalable and fast.
              I am not sure whether the normal weblogic clustered servers need to
              share/exchange info on the running memory, if it does, this approach will
              fail.
              

    So My understanding is:
              Alteon with WL 6.0 can do load balancing for:
              entity bean
              stateless session bean
              but can't do load balancing for:
              stateful session bean (will persistent/sticky binding solve part of the
              problem except fail-over)
              in-memory replication
              am I right?
              Pao Wan
              "Don Ferguson" <[email protected]> wrote in message
              news:[email protected]...
              > It is possible to configure Alteon to understand the WebLogic 6.0 cookie
              format
              > and have a proxy-less cluster configuration that performs load balancing
              and
              > fail over of session state.
              >
              > It is also possible to configure Alteon's hardware-based SSL decryption
              for really
              > fast HTTPS processing.
              >
              > We are working on a white paper that describes how to configure Alteon for
              use
              > with WebLogic Server 6.0.
              >
              > -Don
              >
              >
              > Robert Patrick wrote:
              >
              > > Cameron,
              > >
              > > I believe that BEA tested their new proxy-less web clustering solution
              with
              > > load-balancing products from Alteon and several other vendors
              (Arrowpoint ?--
              > > which is now Cisco). However, it was my understanding that these
              products do
              > > not understand how to decrypt our cookies and extract IP addresses but
              rather
              > > these products are capable of doing sticky load balancing based on the
              Session
              > > ID contained in our cookie.
              > >
              > > If this is correct, then what this means is that when the primary server
              fails,
              > > the request will be routed to "some other server" in the cluster but not
              > > necessarily the one that holds the secondary copy of the user's session.
              The
              > > change in WLS 6.0 is that WLS will accept these misdirected requests and
              it will
              > > go out to the correct server and "migrate" the session to the server
              that
              > > received the request making that server the new primary (and
              regenerating the
              > > Session ID).
              > >
              > > I am sure if this is wrong that our product manager or one of our
              engineers will
              > > correct me (please?)...
              > >
              > > Hope this helps,
              > > Robert
              > >
              > > Cameron Purdy wrote:
              > >
              > > > Hi Robert,
              > > >
              > > > FWIW - There are several vendors (Primeon? Arrowpoint?) who claim to
              > > > understand WL cookies and parse the IPs out. (I haven't verified it
              myself
              > > > though.)
              > > >
              > > > --
              > > > Cameron Purdy
              > > > Tangosol, Inc.
              > > > http://www.tangosol.com
              > > > +1.617.623.5782
              > > > WebLogic Consulting Available
              > > >
              > > > "Robert Patrick" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > There are not any hardware vendors (yet) that can understand
              WebLogic's
              > > > session
              > > > > ID. While you might be able to use the load balancer without the
              proxy on
              > > > 5.1,
              > > > > you would not be able to take advantage of in-memory replication
              failover
              > > > unless
              > > > > you only had two machines in the cluster. Like you said, everything
              will
              > > > work
              > > > > with 6.0 regardless of how the load balancer works (though you
              really,
              > > > really
              > > > > want to minimize the number of times the requests come into the
              wrong
              > > > server by
              > > > > utilizing sticky load balancing).
              > > > >
              > > > > Hope this helps,
              > > > > Robert
              > > > >
              > > > > Cameron Purdy wrote:
              > > > >
              > > > > > Rajesh,
              > > > > >
              > > > > > I meant that it would work in lieu of a proxy (such as Apache or
              NES)
              > > > with
              > > > > > 5.1, but only if both the hw load balancer and WL were set up to
              use
              > > > > > cookies. Some hw load balancers rely on IP and that doesn't
              work -- AOL
              > > > > > connections for example can change the source IP on the fly.
              Others
              > > > produce
              > > > > > their own cookies, that will work. Some even can use WL cookies
              and
              > > > parse
              > > > > > them to determine where to go. According to what I've read, with
              6.0 if
              > > > the
              > > > > > WL primary dies or for some other reason the request shows up at
              the
              > > > "wrong"
              > > > > > server, it will be handled correctly. That means you are pretty
              safe
              > > > with
              > > > > > hw load balancers and 6.0, almost regardless of the sticky
              > > > implementation
              > > > > > that they use.
              > > > > >
              > > > > > --
              > > > > > Cameron Purdy
              > > > > > Tangosol, Inc.
              > > > > > http://www.tangosol.com
              > > > > > +1.617.623.5782
              > > > > > WebLogic Consulting Available
              > > > > >
              > > > > > "Rajesh" <[email protected]> wrote in message
              > > > > > news:[email protected]...
              > > > > > >
              > > > > > > Hi Cameron,
              > > > > > > Can you elaborate on how it would work with WL5.1 since no in
              memory
              > > > > > replication
              > > > > > > would happen if the servers are standalone.
              > > > > > >
              > > > > > > "Cameron Purdy" <[email protected]> wrote:
              > > > > > > >Yes, this will work fine with WL6. (WL5.1 will work fine as
              long as
              > > > > > cookies
              > > > > > > >are used by the load balancer.)
              > > > > > > >
              > > > > > > >--
              > > > > > > >Cameron Purdy
              > > > > > > >Tangosol, Inc.
              > > > > > > >http://www.tangosol.com
              > > > > > > >+1.617.623.5782
              > > > > > > >WebLogic Consulting Available
              > > > > > > >
              > > > > > > >
              > > > > > > >"paowan" <[email protected]> wrote in message
              > > > > > > >news:[email protected]...
              > > > > > > >> Can I install weblogic as a standalone server on 2 or more
              server
              > > > and
              > > > > > > >> cluster/load balance weblogic using a hardware balancer like
              Alteon
              > > > > > Layer4
              > > > > > > >> switch (of course I will use a centralised storage to
              maintain a
              > > > single
              > > > > > > >copy
              > > > > > > >> of data which will eliminate syncronizing problem among
              servers)?
              > > > > > > >>
              > > > > > > >> BTW, Alteon can support persistent binding. The reason to use
              a
              > > > Layer
              > > > > > > >4
              > > > > > > >> switch is that it is very fast, and this will make the
              application
              > > > > > server
              > > > > > > >> layer transparent to client, the client can think this is a
              single
              > > > > > server
              > > > > > > >> (it don't need to know whether there are 5 weblogic servers
              or 20
              > > > > > weblogic
              > > > > > > >> servers behind switch), and hardware are more reliable,
              sacalable
              > > > and
              > > > > > > >fast.
              > > > > > > >>
              > > > > > > >> I am not sure whether the normal weblogic clustered servers
              need to
              > > > > > > >> share/exchange info on the running memory, if it does, this
              > > > approach
              > > > > > will
              > > > > > > >> fail.
              > > > > > > >>
              > > > > > > >>
              > > > > > > >
              > > > > > > >
              > > > > > >
              > > > >
              >
              

  • Ise & vlan load balancing (user balancing)

    As far as I know anb based on some esperience in a test environment it seems that cisco ISE among two load balancing radius kind of attributes supports only vlan gropu assignment, this means that on the switches vlan group assignment is required.
    A second method of passing multiple vlans or vlan IDs by radius attributes is not allowed.
    Am I wrong?
    The issue I'm trying to overcome is the following
    Subnet1     /24
    Subnet2     /22
    Many, many switches
    (and the situation can't be changed)
    Assuming the vlan assignment is local to the switch and with a round robin method, once the IPs are exhausted on Subnet1 only half of the clients that authenticate will obtain an IP (on Subnet2) while the rest will get stuck on Subnet1 without an IP
    The same situation comes up when considering an odd number of authenticated clients on every switch and with two /24 subnets: it is likely possible that Subnet1 will be "full" before the second subnet does falling in the previous situation.
    is there any solution?
    thank you in advance

    Don,
    You are right. I should have said - Forte uses its own partitioning scheme
    not the default scheme you see when you open partition workshop.
    Nirmal
    From: Don Nelson <[email protected]>
    To: Nirmal P Uppalapati <[email protected]>
    Cc: [email protected]
    Subject: Re: Load Balancing, User Visible Service objects, Running man
    Date: Wednesday, October 22, 1997 10:45 PM
    Nirmal,
    One note on the "running man"...
    At 08:12 PM 10/22/97 -0500, Nirmal P Uppalapati wrote:
    3. Running Man
    When you run an application by clicking on the running man Forte uses
    its
    default partitioning scheme and runs the application. The partitionscheme
    that you made will be used only when you run the application distributedor
    from the partition workshop. This is the time you might encounter errorsif
    your partitioning is not right.
    Actually, clicking on the "running man" from the repository or project
    workshop will cause the application to be run VERY differently thanrunning
    it distributed.
    It's not technically correct to say that the default partitioning schemeis
    used with the running man.
    Forte consulting offers a deployment workshop that covers the finerpoints
    of this and other distributed issues.
    Don
    ============================================
    Don Nelson
    Regional Consulting Manager - Rocky Mountain Region
    Forte Software, Inc.
    Denver, CO
    Corporate voice mail: 510-986-3810
    aka: [email protected]
    ============================================
    "If you ask me, though, any game without push-ups, hits, burns or noogies
    is a sissy game." - Calvin

  • 3rd party distributed SW load balancing with In-Memory Replication

              Hi,
              Could someone please comment on the feasibility of the following setup?
              I've started testing replication with a software load balancing product. This
              product lets all nodes receive all packets and uses a kernel-level filter
              to let only one node at the time receive it. Since there's minimum 1 heartbeat
              between the nodes, there are several NICs in each node.
              At the moment it seems like it doesn't work: - I use the SessionServlet - with
              a 2-node cluster I first have the 2 nodes up and I access it with a single client:
              .the LB is configured to be sticky wrt. source IP address, so the same node gets
              all the traffic - when I stop the node receiving the traffic the other node takes
              over (I changed the colours of SessionServlet) . however, the counter restarts
              at zero
              From what I read of the in-memory replication documentation I thought that it
              might work also with a distributed software load balancing cluster. Any comments
              on the feasability of this?
              Is there a way to debug replication (in WLS6SP1)? I don't see any replication
              messages in the logs, so I'm not even sure that it works at all. - I do get a
              message about "Clustering Services startting" when I start the examples server
              on each node - is there anything tto look for in the console to make sure that
              things are working? - the evaluation license for WLS6SP1 on NT seems to support
              In-Memory Replication and Cluster. However, I've also seen a Cluster-II somewhere:
              is that needed?
              Thanks for your attention!
              Regards, Frank Olsen
              

    We are considering Resonate as one of the software load balancer. We haven't certified
              them yet. I have no idea how long its going to take.
              As a base rule if the SWLB can do the load balancing and maintain stickyness that is fine
              with us as long as it doesn't modify the cookie or the URL if URL rewriting is enabled.
              Having said that if you run into problems we won't be able to support you since it is not
              certified.
              -- Prasad
              Frank Olsen wrote:
              > Prasad Peddada <[email protected]> wrote:
              > >Frank Olsen wrote:
              > >
              > >> Hi,
              > >>
              > > We don't support any 3rd party software load balancers.
              >
              > Does that mean that there are technical reasones why it won't work, or just that
              > you haven't tested it?
              >
              > > As >I said before I am thinking your configuration is >incorrect if n-memory
              > replication is not working. I would >strongly suggest you look at webapp deployment
              > descriptor and >then the config.xml file.
              >
              > OK.
              >
              > >Also doing sticky based on source ip address is not good. You >should do it based
              > on passive cookie persistence or active >cookie persistence (with cookie insert,
              > a new one).
              > >
              >
              > I agree that various source-based sticky options (IP, port; network) are not the
              > best solution. In our current implementation we can't do this because the SW load
              > balancer is based on filtering IP packets on the driver level.
              >
              > Currently I'm more interested in understanding whether it can our SW load balancer
              > can work with your replication at all?
              >
              > What makes me think that it could work is that in WLS6.0 a session failed over
              > to any cluster node can recover the replicated session.
              >
              > Can there be a problem with the cookies?
              > - are the P/S for replication put in the cookie by the node itself or by the proxy/HW
              > load balancer?
              >
              > >
              > >The options are -Dweblogic.debug.DebugReplication=true and
              > >-Dweblogic.debug.DebugReplicationDetails=true
              > >
              >
              > Great, thanks!
              >
              > Regards,
              > Frank Olsen
              

  • JOLT JSL Load Balancing ?

    Hello
    Question: If I have hundreds of JOLT clients accessing Tux services behind a
    firewall, can/should I load balance across multiple JRLYs? Has anyone done
    this with a Cisco, F5 or other load balancer? Or have you instead just
    tinkered with the "appAddress" on the JOLT client.
    Here's why I ask:
    From the JOLT 1.2 documentation...
    - Under normal conditions, only one JRLY can communicate with one JRAD.
    - A JRAD can only point to one JSL.
    So given the constraints above, it would look something like...
    JRLYx ------||-------JRAD-------------JSL/JSH (Node X)
    FireW
    JRLYy ------||-------JRAD-------------JSL/JSH (Node Y)
    If all JOLT requests to go one JRLY, they will pound the JSL/JSH on one
    node. So load balancing would be preferred and I'd like to do something
    smarter than defining half the clients with appAddress=JRLYx and the other
    half with appAddress=JRLYy.
    Thanks for taking the time to read this. I would imagine I'm not the first
    to run into this.
    -Jon

    Jolt, by definition, requires a Tuxedo setup. By specifying multiple
              addresses in the appaddrlist, the Jolt connection pool will distribute
              the connections across the addresses supplied. So yes, the appaddrlist
              is only used to establish the physical connection. The JoltPoolManager
              will hand out the connections in such a way as to distribute the load
              across the existing connections.
              Hope this helps,
              Robert
              Laurent Nel wrote:
              > Robert Patrick <[email protected]> wrote:
              > >The Jolt connection pool can be configured to distribute
              > >its connections
              > >across multiple JSL on multiple machines (by specifying
              > >more than one
              > >address in the appaddrlist argument in the configuration
              > >of the pool).
              > >Obviously, once a request is sent from WLS to a specific
              > >JSH process,
              > >Tuxedo load-balancing is used to determine which Tuxedo
              > >server will
              > >process the request.
              >
              > So, does this requires a Tuxedo setup ?
              > I would like to know if it is possible to do load-balancing using
              > only the appaddrlist of the Jolt pool ?
              > My understanding of this list is that it is used only to determine
              > to which tuxedo server the jolt client is going to open a connection.
              > The online doc says that the server is choosen 'randomly' (I guess
              > that it means in a unpredictable way).
              >
              > Laurent
              

  • RX load balancing on SG200-18

    Hi guys,
    I put this question on Spiceworks and someone chimed in and said it wasn't possible due to the nature of how etherchanel balances, but I wanted to double check.  Here is my question:
    I have a cisco SG200-18 managed switch configured with LAG with LACP and a new Supermicro X9SCM-F motherboard that uses two Intel NICs (82579LM & 82574L).  The server is running Server 2012 r2 standard and I'm teaming the NICs via intel's driver.  The team type is set to IEEE 802.3ad Dynamic Link Aggregation.  From my understand that means that inbound and outbound packets should be able to utilize the increased bandwidth (thus the dynamic part).  So far in my testing coping files to and from the server from multiple PCs at the same time only files being copied from the server utilize the increased bandwidth. I can see in task manager on the server that the ethernet is using over 1 Gbps.  However, files going TO the server from multiple computers at the same time max out at 1Gbps.
    Any insight on why this would be?
    Edit: Also want to note that the switch is running the most recent version of the firmware.
    Attached you'll find some screen setups of the different windows on the server & the switch.  Thanks!

    Hello,
    This is a common question with LACP and LAGs in general.
    It all comes down to this.  Any single connection will only ever be able to use a single member of the LAG.  Meaning that whatever the maximum speed (1Gbps) of one physical link is, that is the limit of the transfer.
    It is because of how the load balancing algorithm works.  When a packet comes in, the switch hashes either the IP or MAC address of the source and destination, and comes up with a number.  If your LAG has 4 links, it is a number from 1-4.  That determines which link in the LAG gets used in that connection.  That connection will only ever use that LAG member, and cannot spill over, even if the link it is using gets full.
    The load balancing algorithm can be changed to better utilize the links, however the test of a single computer transferring to another computer will always give the results you saw.
    There are several enterprise level Cisco switches which can load balance based on source and destination port number, which could enable two computers to utilize multiple links, if they were transferring data on different TCP ports.  However the small business switches are only able to load balance by MAC/IP.  You can experiment with the load balancing setting to see which setting optimizes your link usage. You may also be able to tweak this setting on the server side, but that one is up to you.
    Hope that helps a bit, you've done some nice testing already, so I'm really just confirming what you've already seen.
    Thank you for choosing Cisco,
    Christopher Ebert
    Network Support Engineer - Cisco Small Business Support Center

  • Network load balancer for Agentry applications

    Hi Expert,
    I'm going to implement a SAP Mobile Platform solution that will use an agentry application and I need some clarification about the HA configuration and the usage of the network load balancer and relay server. Just for information I'm going to use SMP 2.3 SP4.
    My understanding is that Relay server is a reverse proxy and load balancer for SMP but It can't be used for the agentry applications. Is this correct?
    Based on the standard configuration in order to balance the load of the client devices in the SMP cluster I have to use a Network load balancer, therefore the technical architecture of my solution should be the following:
    |Agentry Client device|   ---->  | Network Load Balancer |  ----> | SMP and Agentry Cluster| -----> |Back end systems|
    Is this correct? I didn't find specifications about the Network load balancer.. Is there a list of the Network load balancer products supported from SAP for agentry application. Is there any best practice on the network load balancer?
    Thank you in advance for you collaboration.
    BR
    g.
    Tags edited by: Michael Appleby

    Because we don't test any directly with our QA we don't have have a preferred products.  Talking to our consulting group they normally just use what the customer already has installed in their network.   Both Software or hardware load balancers has been used.
    The key part needed for the load balancer for Agentry 6.0.x and SMP 2.3 (not SMP 3) that it is set to TCP Pass through.
    Stephen

  • Aggressive Load Balancing = unstable network

    Last week we upgraded 26 WLCs 4400 controllers from version 5.2.178 to version 6.0.188.0/6.0.196.0.
    Two days after the upgrade, IT-administrators had reported problems with 15 of the WLCs.
    The symptoms was:
    - Problems conntecting to SSIDs
    - Unstable network when connected
    - Clients didnt get a IP-adress
    - Unstable signal strength
    After some troubleshooting, it turned out "Aggressive load-balancing" was enabled on the WLCs having these problems.
    Output from one WLC:
    (Cisco Controller) >show load-balancing
    Aggressive Load Balancing........................ Enabled
    Aggressive Load Balancing Window................. 0 clients
    Aggressive Load Balancing Denial Count........... 3
                                                        Statistics
    Total Denied Count............................... 5873 clients
    Total Denial Sent................................ 14067 messages
    Exceeded Denial Max Limit Count.................. 2924 times
    None 5G Candidate Count.......................... 8215 times
    None 2.4G Candidate Count........................ 2331 times
    Yesterday we ran this command on these WLCs:
    config load-balancing aggressive disable
    ..and the problems now seem to have dissappeared.
    Aggressive load-balancing is disabled as default in the newest versions of WLC software, but we have upgraded since version 4.0.155.5 (where I think this was enabled as default), and I guess this setting was enabled because of that.
    Some info from cisco.com about aggressive load balancing:
    Aggressive load-balancing works at the association phase. If enabled and the conditions to load-balance are met, when a wireless client attempts to associate to a LAP, association response frames are sent to the client with an 802.11 response packet that includes status code 17. This code indicates that the AP is too busy to accept any more associations.
    It is the responsibility of the client to honor, process or discard that association response frame with reason code 17. Some clients ignore it, even though it is part of the 802.11 specification. The standard dictates that the client driver must look for another AP to connect to since it receives a "busy" message from the first AP it tries. Many clients do not do this and send the association request again. The client in question is allowed on to the wireless network upon subsequent attempts to associate.
    Just wanted to post this in case others are experiencing problems like we did

    Tweak your RF. You need to adjust the TX power and the data rates. The reason you have one AP with 9 clients is probably because that AP has the lowest TX power setting like 7-8. Make each AP the same TX power level, depending on how many AP's and how big the room is. You will need to play around with this and the data rates to achieve what you want.
    Here is a guide to look at too
    http://www.cisco.com/web/strategy/docs/education/cisco_wlan_design_guide.pdf
    Sent from Cisco Technical Support iPhone App

Maybe you are looking for

  • Installing gcc on solaris 10

    hi, i have a problem when trying to install gcc on solaris 10. my path: PATH=/usr/sbin:/usr/bin:/usr/sfw/bin:/usr/sfw/lib:/usr/sfw/libexec # gcc test.c gcc: installation problem, cannot exec `as': No such file or directory i don't know what the probl

  • Label printing issues in Sapscript

    We are struggling with building a new label for a finished good.  On previous labels we used barcode BC_CD39.  This new label requires a mix of same barcode and 2D barcode.  One of the issues is BC_CD39 is it is too big at 13mm.  So we want to use CD

  • Problem with advanced data Grid

    Hi, I am new to flex. I am designing the UI using flex. I need to that know tht using advanced datagrid when i click the add button the content in my textbox need to be displayed in my ADG, and also i need to know when i click the add button i should

  • Page is distorted on edit

    on normal view my website displays well but on edit the page is distorted that Iis the parts of the pages move away from there normal position.Its like the css is not implemented.

  • Unable to load .xmp files

    I'm having a difficult, okay, impossible time getting previously created .xmp side-cart files to load and I'm wondering if there's a compatibility issue going on here. Originally, the files were created from RAW files in LR 1.5 on a MAC. I've since u