Default static route and Null 0

Hi Everyone,
Need to clear some doubts  for below setup
Switch 3550A is connected to Internet Router and has OSPF nei relationship with it.
3550A#                      sh run int fa0/11
Building configuration...
Current configuration : 272 bytes
interface FastEthernet0/11
 description OSPF LAN Connection to 2691 Router Interface Fas 0/1
 no switchport
 ip address 192.168.5.2 255.255.255.254
sh ip route shows
3550A#sh ip route
Gateway of last resort is 192.168.5.3 to network 0.0.0.0
O*E2 0.0.0.0/0 [110/1] via 192.168.5.3, 20:39:56, FastEthernet0/11
3550A#
All is working fine.
For testing  purposes i config below static route on 3550A
ip default-network 192.168.1.0
ip route 192.168.1.0 255.255.255.0 Null0
After above change
3550A#           sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
S*   192.168.1.0/24 is directly connected, Null0
O*E2 0.0.0.0/0 [110/1] via 192.168.5.3, 20:38:38, FastEthernet0/11
Now i can not ping to internet as below
3550A#ping 4.2.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds:
Success rate is 0 percent (0/5)
When we ping from Switch then source IP is always the Outside interface IP right?
So in this case Switch is using which IP as source?
 Ping to internet is not working as default network is set to 192.168.1.0 and all request goes to this IP and then it goes to
Null interface right?
Extended ping works fine as below
3550A#ping
Protocol [ip]:
Target IP address: 4.2.2.2
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.5.2
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds:
Packet sent with a source address of 192.168.5.2
Success rate is 100 percent (5/5), round-trip min/avg/max = 76/79/80 ms
Second thing to confirm is this ping works because 192.168.5.2 is directly connected to Internet Router interface?
Regards
MAhesh

Hi Mahesh,
When we ping from Switch then source IP is always the Outside interface IP right?
That is correct.  By default it is always the outgoing interface on the device unless you specify it differently.
Ping to internet is not working as default network is set to 192.168.1.0 and all request goes to this IP and then it goes to
Null interface right?
That is correct. Null0 can't be used as next-hop.
Second thing to confirm is this ping works because 192.168.5.2 is directly connected to Internet Router interface?
No, that is because 192.168.5.0/30 is NATed. Remember 192.168.x.x address is a private segment and cannot access the Internet unless NAT is used.
HTH
Reza

Similar Messages

  • I´m doing a design for presale, where I will need a router what support PAT for 500 or a little more of users, it not need any more features only static routing and dhcp pool for 500 users, can you help me for know what router recommend?

    I´m doing a design for presale, where  I will  need a router what support PAT for 500 or a little more of users, it  not need any more features only static routing and dhcp pool for 500 users, can you help me for know what router recommend?

    What is your WAN speed currently and projected WAN speed in the next 3 years?

  • Rtadvd changes default IPv6 router (and breaks things)

    Hello,
    I have been testing IPv6 on my home network and I have decided to let my iMac act as a gateway, as it's the only machine that stays on most of the day. Everything works fine with the he.net tunnel, but a few seconds after I start rtadvd, the default v6 gateway is automatically set to the link-local (fe80::/16) address of the en0 interface, breaking v6 routing for my whole network. Manually deleting such route and readding the correct one (2001::/16) on the tunnel interface gif0 fixes it.
    The problem is that I'm ultimately planning on having a shell script do all of this on boot, and having the script wait a given number of seconds before deleting and readding the route doesn't seem very elegant, not to mention that I don't really know how much time passes before the default route is changed.
    This is what my gif0 and en0 interfaces look like:
    gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
    tunnel inet 192.168.0.6 --> 216.66.80.30
    inet6 fe80::217:f2ff:fed9:eb5e%gif0 prefixlen 64 scopeid 0x2
    inet6 2001:470:1f0b:1393::2 --> 2001:470:1f0a:1393::1 prefixlen 128
    en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    ether 00:17:f2:d9:eb:5e
    inet6 fe80::217:f2ff:fed9:eb5e%en0 prefixlen 64 scopeid 0x4
    inet 192.168.0.6 netmask 0xffffff00 broadcast 192.168.0.255
    media: autoselect (100baseTX <full-duplex,flow-control>)
    status: active
    This is the default gateway that I manually set (and works):
    Internet6:
    Destination Gateway Flags Netif Expire
    default 2001:470:1f0a:1393::1 UGSc gif0
    And this is what it gets reset to (and stops working):
    Internet6:
    Destination Gateway Flags Netif Expire
    default fe80::217:f2ff:fed9:eb5e%en0 UGc en0
    This happens a short while after starting rtadvd, but I can't find anything in the manual pages that refers to the default route. I have used the very same configuration on FreeBSD (by replacing en0 with the correct interface name) and it worked flawlessly, so I'm not sure what the problem is. I suspect that I should add something to rtadvd.conf, because right now I only have a reference to en0 and that may be why the route is redirected there, but I'm not sure how to do that.
    Here is my current rtadvd.conf:
    en0:\
    :addrs#1:addr="2001:470:1f0b:1393::":prefixlen#64:tc=ether:
    Any hints will be greatly appreciated.
    Thank you

    krbonne:
    Congratulations! I am glad you were able to resolve your issue. I'm not much of a hand at networking, hence my referring you to the other Forum.
    Sorry, no Dutch ancestors. Just a Bible name my father chose for me. Incidentally, many linguistic traditions seem to favor the name, Ukranians, Hispanic, Philipinos and now Dutch, and I'm others as well.
    Please do not hesistate to return to Discussions should you have further questions, or just to browse.
    [edited by host - see Terms of Use, section 4.2.2 ]
    Good luck.
    cornelius

  • ASA 5505:Static Routing and Deny TCP connection because of bad flag

    Hi Everybody,
    I have a problem. I made a VPN site-2-site with 2 ASA 5505. The VPN works great. And I create a redondant link if the VPN failed.
    In fact, I use Dual ISP with route tracking. If the VPN fails, the default route change to an ISDN router, situated on the inside interface.
    When I simulated a VPN fail, the ASAs routes switch automatically on backup ISDN routers. If I ping elements, it works great. But when i try TCP connection like telnet, the ASAs deny connections:
    %PIX|ASA-6-106015: Deny TCP (no connection) from 172.16.10.57/35066 to 172.16.18.1/23 flags tcp_flags on interface interface_name.
    the security appliance discarded a TCP packet that has no associated connection in the security appliance connection table. The security appliance looks for a SYN flag in the packet, which indicates a request to establish a new connection. If the SYN flag is not set, and there is not an existing connection, the security appliance discards the packet.
    thanks!
    EDIT: On the schema, The interface of the main asa is 172.16.18.148...

    Check if the xlate timer is set greater than or equal to what the conn timer, so as not to have connections waiting on xlates that no longer exist. To minimize the number of attempts, enable "service resetinbound" . The PIX will reset the connection and make it go away. Without service resetinbound, the PIX Firewall drops packets that are denied and generates a syslog message stating that the SYN was a denied connection.

  • Cisco UC560 Not Clearing Static Routes When VPN Connections Drop

    We have a Cisco UC560 (UC560-FXO-K9) running "Cisco IOS Software, UC500 Software (UC500-ADVIPSERVICESK9-M),
    Version 15.1(2)T2, RELEASE SOFTWARE (fc1)"  The issue is when we have end users connecting with the Cisco VPN Client to this device sometimes we are unable to connect to any devices on our LAN or sometimes we can't connect to the LAN on the other end of our site-to-site VPN.  The one symptom I've observed when this happens is that old VPN sessions that have disconnected appear to leave static routes from the user's outside IP at their home to an IP on our LAN to a Virtual-Access interface.  When this starts to happen, I restart the firewall to clear out the stale static routes and the problem is fixed, for a while at least.  Below is the current state where we have the site-to-site VPN connected to our branch office and 2 user's connected with Cisco VPN clients.  Below that is the static route table which has 5 total Virtual-Access interface routes (one is an extra route for a user currently connected so that their outside IP is in the static route table with 2 inside IP's associated.)  Is there a way to fix the cleanup of VPN connections when they terminate?
    #sh crypto isakmp peers
    Peer: <branch office outside IP> Port: 500 Local: <firewall's outside IP>
    Phase1 id: <branch office outside IP>
    Peer: <users's outside IP #1> Port: 50420 Local: <firewall's outside IP>
    Phase1 id: EZVPN_GRP_437
    Peer: <user's outside IP #2> Port: 49345 Local: <firewall's outside IP>
    Phase1 id: EZVPN_GRP_437
    Bugsy#sh ip ro st
    Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, * - candidate default, U - per-user static route
           o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
           + - replicated route, % - next hop override
    Gateway of last resort is <next hop of ISP for firewall> to network 0.0.0.0
    S*    0.0.0.0/0 [1/0] via <next hop of ISP for firewall>
          10.0.0.0/8 is variably subnetted, 12 subnets, 3 masks
    S        10.0.0.153/32 [1/0] via <non-connected IP of VPN user>, Virtual-Access2
    S        10.0.0.155/32 [1/0] via <non-connected IP of VPN user>, Virtual-Access2
    S        10.0.0.156/32 [1/0] via <user's outside IP #2>, Virtual-Access3
    S        10.0.0.158/32 [1/0] via <user's outside IP #1>, Virtual-Access3
    S        10.0.0.159/32 [1/0] via <user's outside IP #2 again>, Virtual-Access2
    S        10.1.10.1/32 is directly connected, Vlan90

    Hi Brian,
    This sounds like you are running into the following known issue:
      CSCtl03682 - EzVPN client: Several RRI routes  pointing to same virtual interface
    which is Dup'd to:
      CSCtf39056 - RRI routes not deleted
    This is fixed since 15.1(2)T4, so I would recommend upgrading to SWP 8.2 or higher.  The only other way to clean up the stuck routes is to reload the router.
    Thanks,
    Brandon

  • Configuring static routes at the network edge

    We have some Cisco 1750 routers at the edge of our network which are running RIP. We were advised to use static routes on the router, since there was only one route (across a WAN link) for traffic to go from the hub connected to the router, as RIP would only waste the limited bandwidth to the router. We posted this problem previously and got a response which stated :You could set up a default static route on your edge router, run RIP on your internal routers in order to propagate the default, but block the RIP to the outside.
    On your edge router, make a default route to your external link. Keep RIP running as before, but add the line redistribute static in your rip configuration. That will get the default route propagated.
    Now to stop the RIP on the external interface: If the link is on a different major IP network to your internal network, you can simply not include it in the network commands under rip. But if it is in the same network, then RIP will be enabled on the interface, so you will have to add passive-interface xxxxx, where xxxxx refers to the interface carrying your external link,
    Alternatively, you could define your default route using the ip default-network command. This will get propagated automatically into the RIP even without the redistribute command.
    We tried it, the problem is that the router is unreachable, via the serial or Ethernet, although if connected to the router via console port, with the configuration screen , you are able to ping external locations, and are able to telnet into the router, but he PC's on the Ethernet side of the router cant see the network.
    Assistance\Advice requested.
    attached you wll find , the actual reply , and a copy of some info from our work file.

    Ernie
    I have looked at the config that you posted and I see several issues. The serial interface on Salvage is 172.20.2.2. Your message indicates that it is connected via serial to a 3640 which your message seems to indicate is 172.20.1.4. But that makes the 3640 on a different subnet. Connections over a serial link should be in the same subnet on both ends. (The exception to that is when you are using the ip unnumbered feature - which you are not). I suspect that part of your problem is that the routers do not see themselves on a connected subnet. When you run RIP over the link it can compensate for that to some degree. But when you stop RIP the problem has impact.
    Also I see that you have a static default route as Kevin suggested. And in RIP you have redistribute static. But there is no default metric defined. To redistribute into RIP you need a default metric. Another aspect of the problem with the default route is that the next hop for the default route is 172.20.1.4, but without RIP running I believe that Salvage has no idea how to get to that address. You can confirm this by doing show ip route 172.20.1.4 on Salvage. I suspect that you will get an error about route not in table.
    Beyond these issues I believe that there is a larger problem of misunderstanding. When I look at your original post in this thread it talks about not running RIP over the serial link. And when I read Kevin's response the first paragraph is describing not running RIP over the serial interface when it says do static default on your edge router and run RIP on your internal router. If you are not running RIP over the serial interface then I see no reason to run RIP on Salvage at all. There is one piece of this that Kevin did not address. If you do not run RIP over the serial link then how does the 3640 know about the Ethernet subnet at Salvage. I believe that the answer is that the 3640 needs to configure a static route to 172.20.27.0 with the 1750 serial interface as the next hop. And if there are other routers that the 3640 communicates with via RIP then the 3640 needs to redistribute static into RIP (remembering to have a default metric).
    If you address these issues I believe that you will have connectivity from the central network to the remote subnet on Salvage.
    HTH
    Rick

  • How do you promote a static route over a directly connected?

    Hi all,
    I have a need for a static route to be used instead of a directly connected route. (Long story - involving firewalls and anti-spoofing.. but can go further if required)
    I am using a Cisco 3750 switch. I notice directly connected routes have a metric of 0, and the highest metric I can give a static route is 1.
    Therefore, how is it possible for me to make the switch use the static route and not the directly connected?
    Any help would be appreciated!
    Cheers,
    Ben

    Hi Rick,
    Thanks for your patience.
    Maybe I should start again.
    Initially we had 16 VLANs within the 10.0/16 address space. We have some Cisco 3750's connected by dark fibre accross a couple of kms and then lower access switches all hanging of these by some means. The network is flat.
    We have a checkpoint firewall hanging off one of the 3750s connected using a TRUNK port. The firewall has an IP address on all VLANs and is used to route traffic between VLANs based on its ruleset.
    So if I have a user in VLAN 10 who wants to talk to VLAN 20, they travel to the firewall, if a rule permits the access, the firewall routes the packet on to VLAN 2 and the switches deliver at Layer 2.
    The switches all have their default VLAN 1 disabled, and have an IP address on our management VLAN to allow us to manage the switches.
    Its quite important that this IP is on a secured management VLAN as we don't want just anyone being able to snoop switch logins etc..
    If we need to login to a switch, the firewall routes our traffic from whatever VLAN we are on to the Management VLAN.
    One of our VLANs (the Desktop VLAN) is quite large (approx 1300 hosts) and suffers a great deal from too much arp broadcast traffic.
    As we have a flat switched network across several kms, the cost of putting in routers to subnet this large VLAN is excessive.
    However, the 3750's we have are perfectly capable of routing between VLANs, so we decide to create a load of new VLANs instead of subnetting our large VLAN. We don't want to use the firewall to route between these new VLANs as thats just giving the firewall more to do, and previously all these hosts were on a single subnet, so we have no need for any strict security - at most we can use ACLs on the switches if we even need that!
    So far so good.
    With 1300 hosts, we obviously can't make sudden topology changes. Therefore we need to be able to route between the Desktop VLAN and the new VLANs.
    We therefore introduce the static routes between the firewall and the switches.
    So the firewall says:
    route 10.1.0.0/16 via Multilayer switch IP on 10.1.0.0/16
    The multilayer switch says:
    route 10.0.0.0/16 via Firewall IP on 10.1.0.0/16
    This allows routing perfectly between the Desktop VLAN and the new VLANs.
    However the moment we enable ip routing on the switches we break access between the desktop VLAN and the Management VLAN.
    A packet leaves the desktop VLAN through the default gateway on the firewall. This is then routed to the Management VLAN. The return packet doesn't use the Management VLAN default gateway (firewall), it follows the static route on the switch and ends up at the firewall on 10.1.0.0/16. This is subsequently dropped as the firewall knows the packet hasn't come from the 10.1.0.0/16 network, it originally came from the desktop VLAN on 10.0.0.0/16.
    It might seem we can define a route on the switch to say:
    route 10.0.50.0/24 (management VLAN) via 10.0.50.254 (firewall). However, this would result in all packets from 10.1.0.0/16 being dropped by the firewall.
    The other problem is that if we are on a new VLAN and want to talk to the management VLAN. The packet goes to its default gateway on the switch. The switch says - "I have an IP on the management VLAN, its directly connected" - therefore it ignores the static route, and passes the packet on its way. We have now bypassed the firewall, which is bad.
    Incidentally the return packets get routed through the firewall and dropped, as the original packet didn't come through the firewall, there is no entry in the state table for its return.
    I think if we turned off the management interface on the switch and managed it through the interface on 10.1.0.0/16, I assume everything would work. However, we don't want to do this for a whole load of other reasons I wont go into.
    Im sure there must be a fairly simple solution - I just don't have enough experience!
    Cheers,
    Ben

  • Recovering static routing setting 10.1.10.1 for CUE

    I'd like to recover connectivity with CUE.
    I deleted default static routing setting 10.1.10.1 for CUE by my mistake.
    I tried to configure like followings.
    UC520#configure terminal
    Enter configuration commands, one per line.  End with CNTL/Z.
    UC520(config)#interface Loopback0
    UC520(config-if)#description $FW_INSIDE$
    UC520(config-if)#ip address 10.1.10.2 255.255.255.252
    % 10.1.10.0 overlaps with Vlan101
    UC520(config-if)#ip access-group 101 in
    UC520(config-if)#ip nat inside
    UC520(config-if)#ip virtual-reassembly
    UC520(config-if)#interface Integrated-Service-Engine0/0
    UC520(config-if)#description cue is initialized with default IMAP group
    UC520(config-if)#ip unnumbered Loopback0
    UC520(config-if)#ip nat inside
    UC520(config-if)#ip virtual-reassembly
    UC520(config-if)#service-module ip address 10.1.10.1 255.255.255.252
    Need IP address to be configured on interface Integrated-Service-Engine0/0
    It seems like ip adress setting failed because of overlapping with Vlan101. Also CUE Connectivity Diagnostics says "IP address needs to be configured on interface Integrated-Service-Engine0/0"
    Use reset only to recover from shutdown or failed state
    Warning: May lose data on the the NVRAM, nonvolatile file system or unsaved configuration!
    Do you want to reset?[confirm]
    Trying to reload Service Module Integrated-Service-Engine0/0.
    UC520#service-module Integrated-Service-Engine 0/0 session
    IP address needs to be configured on interface Integrated-Service-Engine0/0
    UC520#
    I'm a beginer of IOS, Cisco products and also English. I can barely use CCA. Thank you.

    Check in flash there should be a default configuration file with basic settings.

  • Cisco RV180W Static Routing

    Hi folks.
    Just needing to find out how to implement static routing in my router.  I can't seem to get it to work.  
    I have an internal server that I want all of my requests to go to, and it has an internal IP of 192.168.1.7.  This router is 192.168.1.1, so it's pretty straight forward.  So I thought.  Also, can I break up various services to point to different machines?  Such as:
    Machine
    Ports
    192.168.1.21
    80, 443
    192.168.1.7
    25, 53, 110, 143, 995, 587
    Firmware is 1.0.5.4
    Any advice appreciated.  
    Cheers

    Hello,
    Thank you for the information and I'm sorry you are having issues with your device.
    I think your problem is related to the configuration you are using.
    First of all, go ahead and delete all the static routing and the port forwarding rules you have created as it will be better to start from zero.
    These are the requirements for this to work, make sure you met them:
    1- Check the WAN IP of the router and make sure it is the public IP address. If you don't have the public IP address then contact your ISP to get the modem on bridge mode.
    2- Make sure that the server you are trying to reach from the outside is using the IP address of the router as the default gateway
    3- Go to the firewall and then to access rules and create all the rules needed for your server (Check the attached screenshot). Here is a document showing how to create the rules:
    http://sbkb.cisco.com/CiscoSB/ukp.aspx?vw=1&docid=01ef2188693e42058388dbfe3311ea1f_Access_Rules_Configuration_on_Cisco_Small_Business_RV120W_Wi.xml&pid=2&respid=0&snid=7&dispid=0&cpage=search
    Keep in mind that this is everything that needs to be done to open the ports. When you create the access rules a matching port forwarding rule is created automatically.
    Please let us know if you have any questions

  • Policy routing and black hole filtering on 6500

    I have a 6500 with many SVIs configured and every one with multiple ip addresses. The users are accessing the network through these SVIs. For access control I use the black hole filtering method by dinamically injecting static routes to Null 0 for every user that is not authenticated.
    But I need these users to reach one server to authenticate.
    Is there a way to do this besides putting the server inside every VLAN ? Something like policy routing all the packets to the server to exit the server interface and the response packets to reach the user bypassing the global routing table ? Maybe using a vrf for the server only ?
    Thanx.

    Dave Northampton UK here.
    We seem to have different consumer laws to US it seems?
    Here the RETAILER is wholly responsible for the goods he sells. If such a case as this arose there would be NO time limit of 15 days, if the goods were found not to be of "merchantable quality" the time factor would not matter, certainly up to a year!
    Certainly a retailer can take matters up with their supplier/manfctr but the CUSTOMER must get a new, working product PDQ or a total refund..IN CASH or put on a card, no credit notes or any other such swaddling!
    Of course! Many shops wriggle and tell people porkies but in the end that is da law!
    Dave.

  • High CPU with error "%ADJ-3-RESOLVE_REQ:" in Catalyst 4500-X VSS after making L3 function (static routing)

    We have a VSS based on 2x WS-C4500X-16., The VSS is used as Layer 2 Switch for diffrents Vlan in our DC.
    After making the VSS as a Layer 3 gateway for our production VLAN and added 2 routes for routing purposes, we encountered a network down time with high CPU in the VSS and  a huges log messages : 
    .May 14 12:11:25.947: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.22 Vlan100
    .May 14 12:11:34.516: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.22 Vlan100
    .May 14 12:11:40.072: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
    .May 14 12:11:49.682: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
    .May 14 12:11:55.079: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
    .May 14 12:12:00.926: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
    .May 14 12:12:06.701: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.8.32 Vlan100
    .May 14 12:12:12.624: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
    .May 14 12:12:21.627: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
    .May 14 12:12:32.261: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.8.32 Vlan100
    .May 14 12:12:41.801: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.2.105 Vlan100
    .May 14 12:12:49.633: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
    .May 14 12:12:54.831: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
    .May 14 12:12:59.960: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
    .May 14 12:13:08.745: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
    .May 14 12:13:16.138: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
    .May 14 12:13:22.393: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
    .May 14 12:13:31.415: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.141 Vlan100
    .May 14 12:13:38.944: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.2.215 Vlan100
    .May 14 12:13:45.972: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
    Bellow are the show version of our VSS, 
    Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), Version 03.04.00.SG RELEASE SOFTWARE (fc3)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Wed 05-Dec-12 04:38 by prod_rel_team
    ROM: 15.0(1r)SG10
    S_C4500X_01 uptime is 33 weeks, 1 day, 14 minutes
    Uptime for this control processor is 33 weeks, 1 day, 16 minutes
    System returned to ROM by power-on
    System restarted at 11:59:10 UTC Tue Sep 24 2013
    Running default software
    Jawa Revision 2, Winter Revision 0x0.0x40
    Last reload reason: power-on
    License Information for 'WS-C4500X-16'
        License Level: ipbase   Type: Permanent
        Next reboot license Level: ipbase
    cisco WS-C4500X-16 (MPC8572) processor (revision 9) with 4194304K/20480K bytes of memory.
    Processor board ID JAE173303CF
    MPC8572 CPU at 1.5GHz, Cisco Catalyst 4500X
    Last reset from PowerUp
    4 Virtual Ethernet interfaces
    32 Ten Gigabit Ethernet interfaces
    511K bytes of non-volatile configuration memory.
    Configuration register is 0x2101
    Can you help please, 

    Hi,
    thanks for your reply, but there is no hsrp configured, just an interface vlan. with 2 static routes and the problem was there for more than an hour before we decided to rollback.
    Is there a BugId with this problem in Cisco DataBase.
    here is a show ip route 
    S_C4500X_01#      show ip route
    Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area 
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, * - candidate default, U - per-user static route
           o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
           + - replicated route, % - next hop override
    Gateway of last resort is 10.2.1.253 to network 0.0.0.0
    S*    0.0.0.0/0 [1/0] via 10.2.1.253
          10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
    C        10.0.0.0/8 is directly connected, Vlan100
    L        10.1.1.250/32 is directly connected, Vlan100
          172.31.0.0/16 is variably subnetted, 2 subnets, 2 masks
    C        172.31.0.0/16 is directly connected, Vlan120
    L        172.31.0.1/32 is directly connected, Vlan120
    S     192.1.0.0/16 [1/0] via 10.1.1.254
    and the show ip cef: 
    _C4500X_01#        show ip cef 
    .May 14 12:13:57.859: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.158 Vlan100 f
    Prefix               Next Hop             Interface
    0.0.0.0/0            10.2.1.253           Vlan100
    0.0.0.0/8            drop
    0.0.0.0/32           receive              
    10.0.0.0/8           attached             Vlan100
    10.0.0.0/32          receive              Vlan100
    10.1.1.6/32          attached             Vlan100
    10.1.1.17/32         attached             Vlan100
    10.1.1.40/32         attached             Vlan100
    10.1.1.41/32         attached             Vlan100
    10.1.1.50/32         attached             Vlan100
    10.1.1.60/32         attached             Vlan100
    10.1.1.99/32         attached             Vlan100
    10.1.1.121/32        attached             Vlan100
    10.1.1.122/32        attached             Vlan100
    10.1.1.124/32        attached             Vlan100
    10.1.1.125/32        attached             Vlan100
    10.1.1.126/32        attached             Vlan100
    10.1.1.225/32        attached             Vlan100
    10.1.1.227/32        attached             Vlan100
    10.1.1.250/32        receive              Vlan100
    10.1.1.254/32        10.1.1.254           Vlan100
    10.2.1.3/32          attached             Vlan100
    10.2.1.4/32          attached             Vlan100
    10.2.1.6/32          attached             Vlan100
    10.2.1.8/32          attached             Vlan100
    10.2.1.9/32          attached             Vlan100
    10.2.1.18/32         attached             Vlan100
    10.2.1.23/32         attached             Vlan100
    10.2.1.24/32         attached             Vlan100
    Prefix               Next Hop             Interface
    10.2.1.26/32         attached             Vlan100
    10.2.1.28/32         attached             Vlan100
    10.2.1.29/32         attached             Vlan100
    10.2.1.31/32         attached             Vlan100
    10.2.1.103/32        attached             Vlan100
    10.2.1.108/32        attached             Vlan100
    10.2.1.109/32        attached             Vlan100
    10.2.1.124/32        attached             Vlan100
    10.2.1.129/32        attached             Vlan100
    10.2.1.137/32        attached             Vlan100
    10.2.1.139/32        attached             Vlan100
    10.2.1.143/32        attached             Vlan100
    10.2.1.144/32        attached             Vlan100
    10.2.1.159/32        attached             Vlan100
    10.2.1.167/32        attached             Vlan100
    10.2.1.174/32        attached             Vlan100
    10.2.1.175/32        attached             Vlan100
    10.2.1.176/32        attached             Vlan100
    10.2.1.181/32        attached             Vlan100
    10.2.4.38/32         attached             Vlan100
    10.2.4.39/32         attached             Vlan100
    10.2.4.43/32         attached             Vlan100
    10.2.4.47/32         attached             Vlan100
    10.2.4.51/32         attached             Vlan100
    10.2.4.63/32         attached             Vlan100
    10.2.4.65/32         attached             Vlan100
    10.2.4.69/32         attached             Vlan100
    10.2.4.71/32         attached             Vlan100
    10.2.4.73/32         attached             Vlan100
    10.2.4.102/32        attached             Vlan100
    10.2.4.106/32        attached             Vlan100
    10.2.4.107/32        attached             Vlan100
    10.2.4.113/32        attached             Vlan100
    10.2.4.116/32        attached             Vlan100
    10.2.4.119/32        attached             Vlan100
    10.2.4.120/32        attached             Vlan100
    10.2.4.122/32        attached             Vlan100
    10.2.4.141/32        attached             Vlan100
    10.2.4.148/32        attached             Vlan100
    10.2.6.7/32          attached             Vlan100
    Prefix               Next Hop             Interface
    10.2.6.16/32         attached             Vlan100
    10.2.6.31/32         attached             Vlan100
    10.2.7.14/32         attached             Vlan100
    10.2.7.22/32         attached             Vlan100
    10.2.7.24/32         attached             Vlan100
    10.2.7.34/32         attached             Vlan100
    10.2.7.37/32         attached             Vlan100
    10.2.7.41/32         attached             Vlan100
    10.2.7.48/32         attached             Vlan100
    10.2.8.18/32         attached             Vlan100
    10.2.8.32/32         attached             Vlan100
    10.2.8.59/32         attached             Vlan100
    10.2.8.70/32         attached             Vlan100
    10.2.8.85/32         attached             Vlan100
    10.2.8.88/32         attached             Vlan100
    10.2.8.104/32        attached             Vlan100
    10.2.8.135/32        attached             Vlan100
    10.2.99.10/32        attached             Vlan100
    10.2.99.54/32        attached             Vlan100
    10.255.255.255/32    receive              Vlan100
    127.0.0.0/8          drop
    172.31.0.0/16        attached             Vlan120
    172.31.0.0/32        receive              Vlan120
    172.31.0.1/32        receive              Vlan120
    172.31.0.5/32        attached             Vlan120
    172.31.0.29/32       attached             Vlan120
    172.31.255.255/32    receive              Vlan120
    192.1.0.0/16         10.1.1.254           Vlan100
    224.0.0.0/4          drop
    224.0.0.0/24         receive              
    Prefix               Next Hop             Interface
    240.0.0.0/4          drop
    and show ip arp 
    Protocol  Address          Age (min)  Hardware Addr   Type   Interface
    Internet  10.1.1.1                0   aa00.0400.c286  ARPA   Vlan100
    Internet  10.1.1.6                0   0050.5689.24b8  ARPA   Vlan100
    Internet  10.1.1.10               0   0050.5694.7d20  ARPA   Vlan100
    Internet  10.1.1.11               0   0050.5694.7d20  ARPA   Vlan100
    Internet  10.1.1.12               0   0050.5694.6ae7  ARPA   Vlan100
    Internet  10.1.1.13               0   0050.5694.6ae7  ARPA   Vlan100
    Internet  10.1.1.14               0   0050.568a.6321  ARPA   Vlan100
    Internet  10.1.1.16               0   0050.5694.0ab5  ARPA   Vlan100
    Internet  10.1.1.17               0   0050.5694.493d  ARPA   Vlan100
    Internet  10.1.1.40               0   0013.19b0.9c40  ARPA   Vlan100
    Internet  10.1.1.41               0   1c17.d35a.c840  ARPA   Vlan100
    Internet  10.1.1.50               0   0002.b9b4.a5c0  ARPA   Vlan100
    Internet  10.1.1.60               0   000a.410f.e500  ARPA   Vlan100
    Internet  10.1.1.71               -   0008.e3ff.fc28  ARPA   Vlan100
    Internet  10.1.1.96               0   e02f.6d12.4df3  ARPA   Vlan100
    Internet  10.1.1.98               0   0050.5696.6d86  ARPA   Vlan100
    Internet  10.1.1.99               0   0050.5696.6d88  ARPA   Vlan100
    Internet  10.1.1.121              0   e02f.6d12.4dea  ARPA   Vlan100
    Internet  10.1.1.122              0   e02f.6d12.4e61  ARPA   Vlan100
    Internet  10.1.1.123              0   e02f.6d5b.c10e  ARPA   Vlan100
    Internet  10.1.1.124              0   e02f.6d17.c869  ARPA   Vlan100
    Internet  10.1.1.125              0   e02f.6d5b.c217  ARPA   Vlan100
    Internet  10.1.1.126              0   e02f.6d17.c8ec  ARPA   Vlan100
    Internet  10.1.1.127              0   e02f.6d17.c876  ARPA   Vlan100
    Internet  10.1.1.128              0   e02f.6d5b.bef3  ARPA   Vlan100
    Internet  10.1.1.202              0   0000.85b7.9031  ARPA   Vlan100
    Internet  10.1.1.222              0   000f.f84d.2ca9  ARPA   Vlan100
    Internet  10.1.1.225              0   000f.f84d.3963  ARPA   Vlan100
    Internet  10.1.1.227              0   00c0.ee26.9367  ARPA   Vlan100
    Protocol  Address          Age (min)  Hardware Addr   Type   Interface
    Internet  10.1.1.250              -   0008.e3ff.fc28  ARPA   Vlan100
    Internet  10.1.1.254              0   0000.0c07.ac07  ARPA   Vlan100
    Internet  10.2.1.2                0   0011.4333.bcda  ARPA   Vlan100
    Internet  10.2.1.3                0   0050.5689.5d38  ARPA   Vlan100
    Internet  10.2.1.4                0   0050.5689.0404  ARPA   Vlan100
    Internet  10.2.1.6                0   0050.5689.6d3b  ARPA   Vlan100
    Internet  10.2.1.7                0   1cc1.def4.6940  ARPA   Vlan100
    Internet  10.2.1.8                0   0050.5689.330e  ARPA   Vlan100
    Internet  10.2.1.9                0   0012.793a.3ccc  ARPA   Vlan100
    Internet  10.2.1.10               0   0012.7990.e5d3  ARPA   Vlan100
    Internet  10.2.1.13               0   0050.568a.6dcf  ARPA   Vlan100
    Internet  10.2.1.15               0   0050.568a.60ff  ARPA   Vlan100
    Internet  10.2.1.18               0   0050.5689.091b  ARPA   Vlan100
    Internet  10.2.1.20               0   0050.5689.451c  ARPA   Vlan100
    Internet  10.2.1.21               0   0050.568a.0cf4  ARPA   Vlan100
    Internet  10.2.1.22               0   0050.5689.6c59  ARPA   Vlan100
    Internet  10.2.1.23               0   0050.5696.6d9e  ARPA   Vlan100
    Internet  10.2.1.24               0   0050.5689.76c4  ARPA   Vlan100
    Internet  10.2.1.26               0   0050.5689.2f4e  ARPA   Vlan100
    Internet  10.2.1.27               0   0050.5689.0632  ARPA   Vlan100
    Internet  10.2.1.28               0   0050.5689.1ce9  ARPA   Vlan100
    Internet  10.2.1.29               0   0050.5689.6aaa  ARPA   Vlan100
    Internet  10.2.1.31               0   0050.5689.0d1a  ARPA   Vlan100
    Internet  10.2.1.37               0   0050.5696.6d81  ARPA   Vlan100
    Internet  10.2.1.103              0   d4be.d9be.8eef  ARPA   Vlan100
    Internet  10.2.1.106              0   14fe.b5e1.c595  ARPA   Vlan100
    Internet  10.2.1.107              0   0023.ae7d.a966  ARPA   Vlan100
    Internet  10.2.1.108              0   d4be.d9c8.6770  ARPA   Vlan100
    Internet  10.2.1.109              0   14fe.b5e9.c5b5  ARPA   Vlan100
    Internet  10.2.1.110              0   14fe.b5ea.5f9d  ARPA   Vlan100
    Protocol  Address          Age (min)  Hardware Addr   Type   Interface
    Internet  10.2.1.111              0   001e.c959.d4f0  ARPA   Vlan100
    Internet  10.2.1.114              0   b8ac.6f48.4538  ARPA   Vlan100
    Internet  10.2.1.115              0   14fe.b5e1.ed89  ARPA   Vlan100
    Internet  10.2.1.116              0   7845.c409.1959  ARPA   Vlan100
    Thanks
    Lotfi

  • Need to default 2811 router

    Hi all,
    Please bear with me.  I noticed several topics along the lines of password recovery for a 2811 router and do not mean to ask a redundant question.  I've followed the .pdf instructions and the router will reboot as normal every time.  I manage to get to the rommon 1> and when I initially entered the confreg command as outlined in the password recovery steps it would not recognize the confreg command.  I ended up typing a ? and all the avaialble commands listed... after the commands listed, the CLI would allow me to type confreg 0x2142 which resulted in a message "need to reload or power cycle" (or something to that effect).  After typing the reset, the 2811 reloads, but reboots to normal condition.  I tried the confreg 0x102 method and got the same result.  After several attempts, it seems like the procedure is not working.  So how can I simply default the router and start from scratch if the recovery procedure fails?
    Thank you!

    Hello
    Can you try the below:-
    thanks
    please rate all useful information
    Shut down the router.
    Remove the compact flash that is at the back of the router.
    Power on the router.
    Once the Rommon1> prompt appears, enter this command:
    confreg 0x2142
    Insert the compact flash.
    Type reset.   /you forget to type reset/
    When you are prompted to enter the initial configuration, type No, and press Enter.
    At the Router> prompt, type enable.
    At the Router# prompt, enter the configure memory command, and press Enter in order to copy the startup configuration to the running configuration.
    Use the config t command in order to enter global configuration mode.
    Use this command in order to create a new user name and password:
    router(config)#username cisco privilege 15 password cisco
    Use this command in order to change the boot statement:
    config-register 0x2102
    Use this command in order to save the configuration:
    write memory
    Reload the router, and then use the new user name and password to log in to the router.

  • Static routing

    Hello,
    I set up a network (192.168.1.0), with a wrt160n router. I want to create a second network (192.168.2.0) and use the router to set up a static route between the two networks. Whenever I try to set up a static route and save the settings I get the error "invalid static route", although I think I use the correct data:
    destination lan ip: 192.168.2.0
    subnet mask: 255.255.255.0
    Gateway: 192.168.2.1 (static ip of the router in the second nw)
    interface: lan & wireless
    I already did an upgrade of the firmware but to no avail.
    Anybody any ideas?
    Best regards,
    Christophe

    Are you setting the first network with 192.168.1.0 or 192.168.0.1....?
    Make the first network at 192.168.0.1 and second at 192.168.0.2.Follow this link for Static Routing.

  • RV042 Static Routing Question

    I am currently using RV042 in the two-WAN backup mode. However, I tried the redundant option and am finding it to give me more bandwidth and better performance than only one of the WANs.
    My problem is that in the redundant mode, I am unable to use a few websites that I use on a regular basis. One of the sites is our internet hosted time sheet service and their site just goes crazy when I try to access it through the router set up in redundant mode. I am not even able to login to their site, and it is important for my daily work.
    My question is - can I set up static routes for certain sites so that the router knows to access them through only one of my WANs? For example, if my timesheet software site is 123.123.123.123, and my prefered WAN gateway is 68.68.68.68, can I tell the router to only access this site through the given gateway, even if the router is configured to use either WAN?
    I have tried static routes and it does not seem to work at all.
    For example:
    Site: 123.123.123.123
    SM: 255.255.255.0
    Gateway 68.68.68.68
    When I save this and run the tracert to 123.123.123.123, it goes through the other gateway, and not the one I specified here.
    Any hints are appreciated.
    Thanks,
    Alex P.

    If your using this in load balance mode, go to system management and scroll down to protocol binding.  Chances are your going to a secure site with both wans working and the site sees one connection with two ip addresses coming at it and breaks the connection.  You can do a protocol bind for all your https traffic to go out one wan for all the ip addresses in your network and this should fix the issue.  You can do this for mail and other protocols that would get messed up by the dual wan.  Hope this helps.

  • Check for Null in Mediator Static Routing filter

    Using Expression Builder for Mediator component how can I check the values for NULL in a particular XML element. In my case the XSD is
    <xs:complexType name="OdsCadDataSet">
    <xs:choice>
    <xs:element name="odsCadCase" type="OdsCadCase" minOccurs="0"
    maxOccurs="1"/>
    <xs:element name="odsCadEvent" type="OdsCadEvent" minOccurs="0"
    maxOccurs="1"/>
    <xs:element name="odsCadUnitStatus" type="OdsCadUnitStatus"
    minOccurs="0" maxOccurs="1"/>
    </xs:choice>
    </xs:complexType>
    I want to check in expression builder of mediator whether odsCase, odsCadEvent, odsCadUnitStatus is been processed. I have three static routing for each element and plan to put filter which checks is odsCadCase is null and so forth. How to have this use case.
    Thanks
    Edited by: user5108636 on 28/06/2010 00:15

    helo, i have same problem here...
    I have a xsd:choice on request like this:
    <message>
    <properties>
    <property name="tracking.compositeInstanceId" value="80003"/>
    <property name="tracking.ecid" value="0000J1MQVAZBDC^5lVg8yZ1DtZWJ000T5r"/>
    <property name="transport.http.remoteAddress" value="10.106.17.137"/>
    </properties>
    <parts>
    <part name="request">
    <ns1:parametrosConsultaGuia>
    <ns1:guiaCompensacaoRequest>
    <ns1:anoGuia>2011</ns1:anoGuia>
    <ns1:numeroGuia>314</ns1:numeroGuia>
    <ns1:codigoFatoGerador>6</ns1:codigoFatoGerador>
    <ns1:codigoPorte>77011</ns1:codigoPorte>
    </ns1:guiaCompensacaoRequest>
    <ns1:guiaComplementarRequest>
    <ns1:codigoEntidade/>
    <ns1:classeEmbarcacao/>
    <ns1:codigoPorte/>
    <ns1:codigoAssunto/>
    <ns1:fatoGerador/>
    <ns1:numeroTransacaoInternet/>
    </ns1:guiaComplementarRequest>
    <ns1:guiaDesarquivamentoRequest>
    <ns1:codigoAssunto/>
    <ns1:idPessoa/>
    </ns1:guiaDesarquivamentoRequest>
    <ns1:guiaDividaAtivaRequest>
    <ns1:numeroDebito/>
    <ns1:codigoUsuario/>
    </ns1:guiaDividaAtivaRequest>
    <ns1:guiaNormalRequest>
    <ns1:codigoEntidade/>
    <ns1:codigoAssunto/>
    <ns1:fatoGerador/>
    <ns1:numeroTransacaoInternet/>
    </ns1:guiaNormalRequest>
    <ns1:guiaReferenciaRequest>
    <ns1:numeroGuiaPai/>
    <ns1:anoGuiaPai/>
    <ns1:codigoEntidade/>
    <ns1:classeEmbarcacao/>
    <ns1:codigoAssunto/>
    </ns1:guiaReferenciaRequest>
    <ns1:guiaRemanescenteRequest>
    <ns1:numeroDebito/>
    <ns1:codigoUsuario/>
    </ns1:guiaRemanescenteRequest>
    <ns1:guiaMultaRequest>
    <ns1:codigoEntidade/>
    <ns1:dataVencimento/>
    <ns1:valorMulta/>
    <ns1:percentualDesconto/>
    <ns1:percentualAcrescimo/>
    </ns1:guiaMultaRequest>
    </ns1:parametrosConsultaGuia>
    </part>
    </parts>
    </message>
    I tried everything to check if some of the requests are filled but allways mediator returns null:
    03/06/2011 13:50:42MensagemEvaluation of xpath condition "string-length($in.request/guia:guiaRequest/guia:parametrosConsultaGuia/guia:guiaReferenciaRequest) > 0" resulted false
    <payload>
    Atividade03/06/2011 13:50:42MensagemonCase "GuiaCompensacao.getGuiaCompensacao"
    03/06/2011 13:50:42MensagemEvaluation of xpath condition "$in.request/guia:guiaRequest/guia:parametrosConsultaGuia/guia:guiaCompensacaoRequest != ''" resulted false
    <payload>
    Atividade03/06/2011 13:50:42MensagemonCase "GuiaRemanescenteService.getGuiaRemanescente"
    03/06/2011 13:50:42MensagemEvaluation of xpath condition "string-length($in.request/guia:guiaRequest/guia:parametrosConsultaGuia/guia:guiaRemanescenteRequest) > 0" resulted false
    <payload>
    Atividade03/06/2011 13:50:42MensagemonCase "GuiaMultaService.gerarBoleto"
    03/06/2011 13:50:42MensagemEvaluation of xpath condition "string-length($in.request/guia:guiaRequest/guia:parametrosConsultaGuia/guia:guiaMultaRequest) > 0" resulted false
    <payload>
    Atividade03/06/2011 13:50:42MensagemonCase "GuiaDividaAtiva.getGuiaDividaAtiva"
    03/06/2011 13:50:42MensagemEvaluation of xpath condition "string-length($in.request/guia:guiaRequest/guia:parametrosConsultaGuia/guia:guiaDividaAtivaRequest) > 0" resulted false
    <payload>
    Atividade03/06/2011 13:50:42MensagemonCase "GuiaDesarquivamento.getGuiaDesarquivamento"
    03/06/2011 13:50:42MensagemEvaluation of xpath condition "string-length($in.request/guia:guiaRequest/guia:parametrosConsultaGuia/guia:guiaDesarquivamentoRequest) > 0" resulted false
    <payload>
    Atividade03/06/2011 13:50:42MensagemonCase "GuiaComplementarService.gerarBoleto"
    03/06/2011 13:50:42MensagemEvaluation of xpath condition "string-length($in.request/guia:guiaRequest/guia:parametrosConsultaGuia/guia:guiaComplementarRequest) > 0" resulted false
    <payload>
    Atividade03/06/2011 13:50:42MensagemonCase "GuiaNormalService.gerarBoleto"
    03/06/2011 13:50:42MensagemEvaluation of xpath condition "string-length($in.request/guia:guiaRequest/guia:parametrosConsultaGuia/guia:guiaNormalRequest) > 0" resulted false
    <payload>

Maybe you are looking for