Nexus 7010 No route to host

Hi,
I needed to add vlans on the bladecenter, So added to ports on the bladecenter and then to the main trunk port of BC as well as i created the vlan on BC.
This BC connects to two main NEXUS 7010 core switch, I added to trunk port of these switches as well and vlan was already created in the nexus core switch.
but i was unable to ping the subnet gateway from the nexus core switch and gets the error as "no route to host"
Is this something there is no routing define for this subnet. As OSPF is running on the core switch.
Thanks
Sagar

Thanks Alex
VLAN was allowed on the trunk, everything related vlan is fine.
but there was no static route defined on the switch as the routing for the subnet was done on the firewall
so what i thought is to give a static route for network with next hop as firewall interface and guess what it started to work
Thanks
Sagar

Similar Messages

  • Nexus 7010 - redistribute host routes in to OSPF

    In my Nexus 7010 infrastructure, I have a requirement to redistribute host routes in to OSPF so that the other connected sites receive the host routes through OSPF.
    These hosts are part of the connected network (192.168.100.0/24) on Nexus, I dont want this network to be advertised in to OSPF but I want the hosts inside this subnet (192.168.100.11 and 192.168.100.12) to be advertised.
    I tried to create a prefix list with these two hosts and added them to a route-map and then using the "redistribute direct" command called this route-map in to OSPF, but this is not working.
    However, if I add the entire subnet (the connected network) in to this route-map, it shows up in OSPF.
    Is there a way I could have only the hosts to be part of the OSPF database?

    Hello, There is no need for VDC or VRF I think. are we missing a trick here. I also just tested for my own sanity. (Or am I completely under-thinking this)
    N7K-1 has vlan 24 and the host route will be to 172.25.24.20
    N7K-1 Config:
    conf t
    ip route 172.25.24.20/32 Vlan24
    ip prefix-list TEST seq 5 permit 172.25.24.20/32
    route-map STATIC_TO_OSPF permit 10
      match ip address prefix-list TEST
    router ospf 1
      bfd
      router-id 192.168.101.1
      redistribute static route-map STATIC_TO_OSPF
    here is what I see on its neighbour N7K2:
    DC1-N7K2# show ip route 172.25.24.20
    IP Route Table for VRF "default"
    '*' denotes best ucast next-hop
    '**' denotes best mcast next-hop
    '[x/y]' denotes [preference/metric]
    '%<string>' in via output denotes VRF <string>
    172.25.24.20/32, ubest/mbest: 1/0
        *via 192.168.102.5, Eth8/1, [110/20], 00:00:07, ospf-1, type-2
    DC1-N7K2#
                    Type-5 AS External Link States
    Link ID         ADV Router      Age        Seq#       Checksum Tag
    172.25.24.20    192.168.101.1   479        0x80000002 0x0eed    0
    So in essence point the host routes statically to the directly connected interface.
    hth.
    Bilal

  • How to do routing on N7K-F248XP-25E (Nexus 7010) ?

                       Hi all,
         Please educate me the following scenario : I have Nexus 7010 with 2 L3 modules, N7K-M132XP-12L and N7K-M148GT-11L. Now to increase more ports for end devices, I add in the module N7K-F248XP-25E and believe it's for Layer 2 switching only. Is there a way to do routing on these L2 modules without having to go to the L3 modules ? Thanks for all help.

    Is there a way to do routing on these L2 modules without having to go to the L3 modules ?
    No.  If you have an M1/M2 card and routing is enabled, the F2E card will "step down" and do Layer 2 work.  All Layer 3 work will be done by the M1/M2 card.

  • Nexus 7010 and ESX Host

    Hi,
    We are currently seeing issues on a ESX Host using 10G Fibre dual connectivity to a pair of Nexus 7010's using vPC for the port channel to this ESX host which was working fine , up to this weekend. No changes had been made on the Nexus or ESX host.
    We have changed the hardware path for the believed fault on a vmnic which when part of the virtual switch cause VM's on the Host to stop pinging, although we still see a CDP neighborship with the ESX from the Nexus, but changing fibre and Nexus ports has not worked.
    As part of the testing , the vmware guy was removing this 'faulty' vmnic from the Virtual switch , which is part of an ether channel bundle his end. My first question is, how does the Nexus detect a link leaving the bundle for the ESX host , when the actual physical link is still up , and all they have done is software removed it from on the ESX, as the Nexus will still attempt to push traffic across both bundled links. I know there is the Cisco 1000V software , which can be used at an extra price, but is this the only option.
    Any help will be gladly welcome.

    Hi
    How the switch detects a link 'moving out' of the Etherchannel would depend on how you have configured it...
    If you have used 'channel-group x mode on' under the physical ports in the channel, then it will not detect the change, and you will get problems. The solution is to ensure the config of the channel on both ends (server/switch) is consistent in this case. An inconsistent config will cause you connectivity issues.
    If the switch automatically negotiates the Etherchannel (i.e. you are using LACP, and the server supports LACP) then it should detect the change.
    Regards
    Aaron
    Please rate helpful posts...

  • In reviewing the Cisco Licensing Guide, there is a license part number for MPLS on the Nexus 7010. Part Number is N7K-MPLS1K9.

    In reviewing the Cisco Licensing Guide, there is a license part number for MPLS on the Nexus 7010.  Part Number is N7K-MPLS1K9.  Is there a corresponding part number for the Nexus 7710?

    For the benefit of others, here is what we found. The N7K was hitting the bug CSCtg95381.
    Symptom
    Nexus 7000 may punt traffic to CPU; so that the traffic may experience random delay or drop.
    Further looking, ARP is learned and FIB adjacency is in FIB adjacency table.
    Conditions
    The problem is caused by race condition. Some hosts have not responded to the ARP refresh sent by
    N7k which in turn  trigger to delete  ARP entry  due to expiry. As a result   the route delete notification is
    sent   to URIB from the process. However there is still traffic coming to   given IP address as a result  the next packet that hit glean resulting   in triggering ARP and  hope ARP is learnt from the host this time.
    Workaround
    (s):
    Clear ip route < host>.
    Not  totally explains why it was working for certain client-server  combination but yet the workaround is holding well for end-points when  implemented.
    There  would be no host route for the destination server in the adjacency  manager on N7K-01. The only thing thats there is the subnet route  pointing towards the vlan gateway address. Implementing the work-around,  a new /32 route can now be seen in the adjacency manager for the  server.
    The bug is fixed in releases starting 5.1(5). Planning to upgrade to 5.2(3a).
    Regards, Rashid.

  • Nexus 7010 bgp state change alert not triggered to NNM

    Hi ,
    BGP state change alert not triggered  to NNM on  Nexus -7010 for Monitoring.
    Details of the Device:
    Nexus 7010 :     
    Software
      BIOS:      version 3.22.0
      kickstart: version 5.1(3)
      system:    version 5.1(3)
    BGP neighbor status :
    Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
    172.16.1.2      4 65505 5089234 5194515    51359    0    0     6w2d 391
    172.16.1.3      4 65505 5044293 5146859    51359    0    0    30w4d 378
    172.31.11.3     4 15404  120744  114811    51359    0    0     1w6d 1
    172.31.42.3     4 65501 5261796 5264413    51359    0    0    2d06h 0
    Snmp trap enabled:
    snmp-server user admin network-admin auth md5 0x690c4ede8a88ba7f2de791dbe7a77f0a
    priv 0x690c4ede8a88ba7f2de791dbe7a77f0a localizedkey
    snmp-server host 172.30.0.55 traps version 2c xxxx
    snmp-server enable traps bgp
    Downloaded cisco-bgp4-mib version, bgp4-mib tried and performed snmpwalk  as given below
    nnmsnmpwalk.ovpl -c xxx 172.31.15.130 .1.3.6.1.4.1.9.9.187.0.6
    Error : No MIB objects contained under subtree
    nnmsnmpwalk.ovpl -v 2 -c xxx 172.31.15.130 .1.3.6.1.2.1.15.3.
    No MIB objects contained under subtree
    Kindly advise to resolve the issue
    Regards
    Hari

    You can set an alert for Warning State. This is feasible.
    Juke Chou
    TechNet Community Support

  • Private-VLAN using Nexus 7010 and 2248TP FEX

    I have a Nexus 7010 with several 2248TP FEX modules.
    I am trying to configure a Private VLAN on one of the FEX host ports.
    I see in the documentation you can't do promiscous but I can't even get the host only configuration to take.
    Software
      BIOS:      version 3.22.0
      kickstart: version 6.0(2)
      system:    version 6.0(2)
    sho run | inc private
    feature private-vlan
    vlan 11
      name PVLAN_Primary
      private-vlan primary
      private-vlan association 12
    vlan 12
      name PVLAN_Secondary
      private-vlan isolated
    7010(config)# int e101/1/48
    7010(config-if)#
    7010(config-if)# switchport mode ?
      access        Port mode access
      dot1q-tunnel  Port mode dot1q tunnel
      fex-fabric    Port mode FEX fabric
      trunk         Port mode trunk
    Switchport mode private-vlan doesn't even show up!!!!!!
    If I try this command it says its not allowed on the FEX port.
    7010(config-if)# switchport private-vlan host-association 11 12
    ERROR: Requested config not allowed on fex port
    What am I doing wrong?????
    Todd

    Have you found a solution to this?
    -Jeremy

  • Port-channel L2 problem with Fabric Interconnect and Nexus 7010

    Hi,
    i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
    but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
    I was trying :
    1. I using non dedicated port in Nexus 7010.
          - rate-mode share
          - channel-group 1 mode active
          - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    2. I using non dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode on
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
    3. I using dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    4. I using dedicated port in Nexus 7010
         - rate-mode dedicated
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up and running well.
    but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
    is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
    i attach the topology of N7K with Fabric interconnect.
    regards,
    Berwin H

    Hi Manish,
    the issue was solved, i was fix it last week.
    the solution is:
    i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2)  so i allocate the interface on all module
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
    i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
    So here the result of my port-channel :
    SVRN7KFARM-HO-01# show port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
    Group Port-       Type     Protocol  Member Ports
          Channel
    1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                         Eth1/4(P)    Eth1/25(P)  
    2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                         Eth1/12(P)   Eth1/26(P)  
    3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)  
    4     Po4(SU)     Eth      NONE      Eth10/32(P)  Eth10/34(P)  Eth10/35(P)
                                         Eth10/36(P)
    Thanks.
    Berwin H

  • External services moved, but SOA suite still gives "no route to host"

    We have a SOA Suite integrating towards external services. The external service provider moved the services to a different server, and updated dns entries to reflect this move. But our SOA Suite gave "no route to host" errors when this move was performed, clearly not reloading the changes done in DNS, but still using the old address.
    How and where can the SOA Suite be configured to actually time out domain name resolutions, when external services are moved this way. Can we ask it to use hostname instead of ip address.
    Bouncing the servers is of course working, but there must be a configuraiton way around this.
    bouncing production servers is the final resort.
    Details of error message
    <MSG_TEXT>BusinessEvent diapatch failed for {ESBDomain.Service.publish} with error An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: No route to host: connect

    also check for firewalls on the server - a good test would be to an attempt to telnet into webservice hostname and portnumber from the SOA Server.
    Regards,
    Shanmu.

  • No route to host:connect -- error in the struts-config.xml file

    hi all,
    acutally am doing a struts application in that i have written everything properly
    but getting this kinda no route to host:connect error
    my struts-config.xml file is like this...
    <struts-config>
    <form-beans>
    <form-bean name="myForm" type="MyForm">
    </form-beans>
    <action-mappings>
    <action path="/action"
                   name="myForm"
                   type="MyAction"
                   scope="request"
                   validate="true" >
                   <forward name="success" path="/success.jsp" />
                   <forward name="failure" path="/failure.jsp" />
         </action>
    </action-mappings>
    </struts-config>
    sikandar 

    Hi Lee,
    I am working on Oracle ADF 10.1.2 and getting the same problem. The lines in my struts-config.xml are as below:
    <action path="/unitsView" className="oracle.adf.controller.struts.actions.DataActionMapping" type="view.UnitsViewAction" name="DataForm" parameter="/unitsView.uix" unknown="false">
    <set-property property="modelReference" value="unitsViewUIModel"/>
    <forward name="unitsEditLink" path="/unitsEdit.do"/>
    </action>
    <action path="/unitsView" className="oracle.adf.controller.struts.actions.DataActionMapping" type="view.UnitsViewAction" name="DataForm" parameter="/unitsView.uix" unknown="false">
    <set-property property="modelReference" value="unitsViewUIModel"/>
    <forward name="unitsCreateLink" path="/unitsCreate.do"/>
    </action>
    I have two lines with [action path="/unitsView"]. The reason why is that I want the user to go to the form create screen for the create button and form edit screen for the edit button. If this does not work, it seems to mean that only a single screen can be used for create/edit functions. However, the ADF editor diagram looks perfectly to point to create.uix and edit.uix respectively.
    Please shed some light.
    Thanks,
    Regards,
    Michael

  • FTP receiver channel error: No route to host

    Hello,
    I am using a ftp receiver channel and got the following error:
    java.lang.Exception: ftp access error: java.net.NoRouteToHostException: No route to host.
    The following steps are processed right:
    - Connection to FTP-Server "XXXX", Folder "/public_html/external/eh/"
    - Write to FTP-Server "XXXX", Folder "/public_html/external/eh/", file "xyz.xml"
    - Sending: Modus "TXT", Size XXX, Codepage UTF-8
    And then the error occurs.
    It seems that the channel could connect to the server and start sending the data, but then the error occurs.
    Did anybody know this problem?
    Thank you very much
    Thomas

    Hi Thomas -
    Is your FTP server configured for active or passive data connections?  If active, you need SP15.  Before SP15, only passive data connections are supported.
    Regards,
    Jin

  • Critical Alarm for Nexus 7010 device

    Hi Team,
    We are getting Critical Alarm for the Data center device Nexus 7010 continuously from 28-Oct.
    error (device hde1) in start_transaction: Journal has aborted - kernel
    2012 Oct 29 10:00:18.227 DC-Core-Switch2 29 10:00:18 %KERN-2-SYSTEM_MSG: EXT3-fs
    error (device hde1) in start_transaction: Journal has aborted - kernel
    2012 Oct 29 10:28:37.497 DC-Core-Switch2 29 10:28:37 %KERN-2-SYSTEM_MSG: EXT3-fs
    error (device hde1) in start_transaction: Journal has aborted - kernel
    2012 Oct 29 10:28:42.398 DC-Core-Switch2 29 10:28:42 %KERN-2-SYSTEM_MSG: EXT3-fs
    Also attaching the complete logs collected for this device and suggest if there is any Hardware related issue or some Software related issue.
    Regards,
    Ashutosh

    Hello
    hde1 is the logflash device. Looks like there were IO errors and the kernel mounted the fs read-only. You can try to reload the device and if logflash will come back up fine after the reload, its a transient issue; if the issue comes back, the logflash device most likely is damaged bad and needs to be replaced. You will need to open a service request with TAC to get it replaced.
    HTH,
    Alex

  • Nexus 7010 fabric extender timing out

    Hello -
    We have a Nexus 7010 and we are testing out using the fabric extenders for a need.  We have a demo 2224 unit and have it connected to our M132XP-12 10G blade in the 7K but the FEX won't come online.  I would have figured a possible software incompatability but looking at the supported list for that as well as hardware everything seems to be in order.  This is what the status shows after it spends about 15 mins in the image download state.
    FEX: 111 Description: FEX0111   state: Offline
      FEX version: 4.2(1)N2(1a) [Switch version: 5.1(2)]
      FEX Interim version: 4.2(1)N2(1a)
      Switch Interim version: 5.1(2)
      Module Sw Gen: 21  [Switch Sw Gen: 21]
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth2/20
      Fabric interface state:
        Po11 - Interface Up. State: Active
        Eth2/20 - Interface Up. State: Active
      Fex Port        State  Fabric Port  Primary Fabric
    This is looped in the log details until it times out:
    04/25/2011 15:31:41.986978: Module register received
    04/25/2011 15:31:41.987713: Registration response sent
    04/25/2011 15:31:41.987889: Requesting satellite to download image
    04/25/2011 15:32:00.105031: Module register received
    04/25/2011 15:32:00.105779: Registration response sent
    04/25/2011 15:32:00.105956: Requesting satellite to download image
    04/25/2011 15:32:20.191181: Module register received
    04/25/2011 15:32:20.191957: Registration response sent
    04/25/2011 15:32:20.192144: Requesting satellite to download image
    We ran a debug during this and these entries are displayed when looking for errors.
    2011 Apr 25 15:30:31.443745 fex: Reg resp: Failed to get card info for swcardid 132
    2011 Apr 25 15:30:35.472721 fex: Cardinfo: Unknown card id to get (132)
    2011 Apr 25 15:30:35.472753 fex: Reg resp: Failed to get card info for swcardid 132
    2011 Apr 25 15:30:41.495302 fex: Cardinfo: Unknown card id to get (132)
    I'm still doing some more searching which so far hasn't turned up much, wanted to see if anyone has some other insight??
    Thanks!

    Hi Jack -
    Thanks for the response.  Unfortunately, yes that is already complete.  I was hoping that would be an easy fix.  When we upgraded to 5.1(2) we did the 5.1 EPLD.  I ran the install all impact command noted below for the 5.1 EPLD just to make sure it didn't report anything else as needing upgrade.
    sho install all impact epld bootflash:n7000-s1-epld.5.1.1.img
    Compatibility check:
    Module  Type  Upgradable        Impact   Reason
         1    LC         Yes    disruptive   Module Upgradable
         2    LC         Yes    disruptive   Module Upgradable
         5   SUP         Yes    disruptive   Module Upgradable
         1  Xbar         Yes    disruptive   Module Upgradable
         2  Xbar         Yes    disruptive   Module Upgradable
         3  Xbar         Yes    disruptive   Module Upgradable
         1   FAN         Yes    disruptive   Module Upgradable
         2   FAN         Yes    disruptive   Module Upgradable
         3   FAN         Yes    disruptive   Module Upgradable
         4   FAN         Yes    disruptive   Module Upgradable
    Copy complete, now saving to disk (please wait)...
    Retrieving EPLD versions... Please wait.
    Images will be upgraded according to following table:
    Module  Type           EPLD      Running-Version   New-Version  Upg-Required
         1    LC  Power Manager              4.008       4.008           No
         1    LC  IO                         1.006       1.006           No
         1    LC  Forwarding Engine          1.006       1.006           No
         1    LC  SFP                        1.004       1.004           No
         2    LC  Power Manager              4.008       4.008           No
         2    LC  IO                         1.016       1.016           No
         2    LC  Forwarding Engine          1.006       1.006           No
         2    LC  FE Bridge(1)              186.006      186.006           No
         2    LC  FE Bridge(2)              186.006      186.006           No
         2    LC  Linksec Engine(1)          2.006       2.006           No
         2    LC  Linksec Engine(2)          2.006       2.006           No
         2    LC  Linksec Engine(3)          2.006       2.006           No
         2    LC  Linksec Engine(4)          2.006       2.006           No
         2    LC  Linksec Engine(5)          2.006       2.006           No
         2    LC  Linksec Engine(6)          2.006       2.006           No
         2    LC  Linksec Engine(7)          2.006       2.006           No
         2    LC  Linksec Engine(8)          2.006       2.006           No
         5   SUP  Power Manager              3.009       3.009           No
         5   SUP  IO                         3.028       3.028           No
         5   SUP  Inband                     1.008       1.008           No
         5   SUP  Local Bus CPLD             3.000       3.000           No
         5   SUP  CMP CPLD                   6.000       6.000           No
         1  Xbar  Power Manager              2.010       2.010           No
         2  Xbar  Power Manager              2.010       2.010           No
         3  Xbar  Power Manager              2.010       2.010           No
         1   FAN  Fan Controller (1)         0.007       0.007           No
         1   FAN  Fan Controller (2)         0.007       0.007           No
         2   FAN  Fan Controller (1)         0.007       0.007           No
         2   FAN  Fan Controller (2)         0.007       0.007           No
         3   FAN  Fan Controller (1)         0.007       0.007           No
         3   FAN  Fan Controller (2)        0.007       0.007           No
         4   FAN  Fan Controller (1)         0.007       0.007           No
         4   FAN  Fan Controller (2)         0.007       0.007           No

  • Nexus 7010 upgrade path

    We currently have two Nexus 7010 with 5.0(2a) as system images.
    We would need to know the correct upgrade path to 6.1(1). On the release notes it reads the path is from 4.2(8), 5.0(5) or 5.1(6) to 5.2(5) then to 6.1(1).
    Also if ISSU is possible or, because we may need to upgrade EPLD, if there is no upgrade path to do a non-disruptive upgrade.

    You probably need to dig a little deeper to get a definitive answer (sup1 or 2, type of cards, etc..) but here is a diagram in the release notes for 6.1 found here:
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/61_nx-os_release_note.html
    If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

  • Java.lang.RuntimeException: No route to host in Work Flow

    Dear All,
    Workflow containers are not starting up due to follwing errorin log file.
    "{oracle.apps.fnd.profiles.ExtendedProfileStore@1a80aea}],mUniqueId=SVC-GSM-WFMLRSVC-2201985,mLevel=4
    }, oracle.jdbc.driver.T4CConnection@1e2670b, 10006, STOPPED_ERROR, Could not handle the control
    event -> java.lang.RuntimeException: No route to host) "
    Checked Metalink and google but could't find the troubles hooting steps.
    Request anybody to guide me to troubleshoot above issue.
    Regards,
    Sunil.

    Sunil,
    Please see these docs.
    Workflow Service Component is System Deactivated with Error Details : Could not handle the control event -> java.lang.OutOfMemoryError: unable to create new native thread [ID 842968.1]
    Unable To Start Workflow Notification Mailer [ID 418329.1]
    Java Mailer wont start OPEN_MAIL_FYI=The requested template does not exist [ID 331358.1]
    Thanks,
    Hussein

Maybe you are looking for