OSPF with ipsec VTI interface goes down before dead timer.

I have a strange issue that OSPF will initially start working, hellos are exchanged both ways but then after about 3 – 6 hellos one of the sides stops getting them and the ipsec VTI tunnel drops on router A even before the dead timer reaches 0. Is this default behavior, when OSPF is over a VTI interface if it doesn’t receive hellos is drops the tunnel?
I’m at a loss as to what is going on since it looks like only one neighbor stops receiving hellos, router A, for a brief period of time. This VTI tunnel is going over another provider’s FW and they have assured me the tunnel destination/source ips are wide open they also sent me the ACL and I can verify this. The weird thing is if I enable EIGRP it works great with no issues. On router B I am using the same source/ip unnumbered  interface on multiple VTI tunnels to to other destinations but this shouldn’t cause any issues I don’t think. I have never had an issue like this and from what I can tell the router A just stops briefly getting hellos after 3 – 6 initial hellos and drops the protocol on the VTI interface. If I set the dead timer on router A long enough it will stop receiving hellos but stay up and then after a while you get “LOADING to FULL” as the hellos start coming in again.  Again the tunnel goes over a cisco 800 which I have no control over it and a potential FW before that but I saw the ACL and ip is being allowed. I was thinking this could be a trolling issue on the FW but it doesn’t explain why EIGRP works.  FYI I was having a recursive routing issue before but I have since fixed that and the issue still continues.
********  it turns out that i was using the same source ip on multiple tunnels. IPsec would get confused with packets coming in and would deliver packets to the wrong tunnel interface. This was solved but using the key command with a different key number on each set of tunnels with the shared profile command
"If more than one mGRE tunnel is configured on a router that use the same tunnel source address, the shared keyword must be added to the tunnel protection command on all such tunnel interfaces. Each mGRE tunnel interface still requires a unique tunnel key, NHRP network-ID, and IP subnet address. This is common on a branch router when a dual DMVPN cloud topology is deployed. "
Router A:
router ospf 1
router-id 10.213.22.2
passive-interface default
network x.x.97.26 0.0.0.0 area 0
interface Tunnel1
ip unnumbered GigabitEthernet0/1
ip virtual-reassembly in
ip tcp adjust-mss 1398
ip ospf network point-to-point
load-interval 30
tunnel source GigabitEthernet0/1
tunnel mode ipsec ipv4
tunnel destination x.x.173.109
tunnel path-mtu-discovery
tunnel protection ipsec profile VTI-to-NB
router B:
router ospf 1
router-id 172.17.2.6
priority 1
redistribute static subnets route-map Lan-static-RM
passive-interface default
no passive-interface Tunnel1
no passive-interface Tunnel4
no passive-interface Tunnel5
network x.x.173.109 0.0.0.0 area 0
network 172.17.2.6 0.0.0.0 area 0
network 192.168.1.47 0.0.0.0 area 0
interface Tunnel4
ip unnumbered GigabitEthernet0/2
ip virtual-reassembly in
ip tcp adjust-mss 1398
ip ospf network point-to-point
load-interval 30
tunnel source GigabitEthernet0/2
tunnel mode ipsec ipv4
tunnel destination x.x.97.26
tunnel path-mtu-discovery
tunnel protection ipsec profile VTI_NB_to_dorrance_prv
end
thanks P

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
I haven't studied your config, but I can tell you I have production environment using OSPF across VTI  (and GRE, and GRE/IPSec and DMVPN) tunnels without issue.  I.e. so OSPF can be okay with VTI tunnels.

Similar Messages

  • Interface goes down with mds9140

    Hi
    I've a problem with both MDS 9140. The fc interface goes down and don't go up when I reboot a device connected to them with a fiber. To solved the problem I need to remove the gbic and plug it back again. I use the following version of software
    Software
    BIOS: version 1.0.8
    loader: version 1.1(2)
    kickstart: version 1.2(1a)
    system: version 1.2(1a)
    Fabrice

    It is probably a software defect where if a port is up for over 248 days, Once link is lost, it will not come back w/o a shut/no shut or manual intervention as you describe. This issue is resolved in the 1.3.4b and above code. For a 91xx, this would be a disruptive upgrade. Or, simply issue a shut/no shut on an affected port and you'll be good for another 248 days.

  • RIP redistribution in to OSPF breaks when 1OSPF path goes down

    Hi All,
    I'm failing to understand why the RIP redistribution is breaking when I shutdown interface 0/0 on the mpls-usa router (mpls is just a naming convention). When 0/0 is up RIP is redistributed by when it is down I get nothing. See diagram below:
    The topology:
    Show ip route on mpls-2 and mpls-3 when interface 0/0 is down on mpls-usa
    show ip route on mpls-2 and mpls-3 with eth 0/0 down
    And this is my config on MPLS-USA

    Hi,
    First of all , please mention interfaces in your topology. Second in all routing table snapshot you cut the router hostname that also creates confusion.
    Now in the last output, i am not sure that output is from MPLS-2 or MPLS-3 and where E0/1 is connected to. Regarding your question related to number of routes, i guess you would have only one route in routing table because in OSPF external routes other than route metric, metric to ASBR also comes in to picture.
    When you shut one interface, route should not get disappeared. You can shut interface between MPLS-2 and MPLS-USA and share ospf lsa database output from MPLS-USA and MPLS-3. Also "show ip ospf nei" on MPLS-USA router.

  • HSRP both become active once tracked interface goes down

    Hi team,
    I was doing a fail-over testing for several sites for a customer.(dual CE router setup)
    I have two routers 08R & 09R with following HSRP config.
    with this configuration 08R is active & 09R is secondary.. all good
    but when I shutdown the Serial link on active router(08R). both become active and standby unknown
    they can ping each other, checked ARP table, all good.
    also removed track statement on backup router (09R) but no joy...
    put the debug on
    Please advise.
    08R#sh run int f0/0
    ip address 10.58.0.29 255.255.255.0
    standby 1 ip 10.58.0.30  <---hsrp ip
    standby 1 priority 105<------------------- when s0/0/0 down, becomes 95
    standby 1 preempt
    standby 1 track Serial0/0/0.100
    09R#sh run int f0/0
    ip address 10.58.0.31 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 priority 101  <-------
    standby 1 preempt
    standby 1 track Serial0/1/0:0.100<-----------also tracking its own serial interface (removed this as its not required but still not working)
    Debug on 08R
    Jun 25 08:51:33.554 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30  <---sending hellos with lower priority 95, no in pkts
    Jun 25 08:51:36.554 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:51:37.978 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Debug on 09R
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  in  10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Coup   out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  in  10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Coup   out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30

    Try this:
    Router 08R Configuration
    track 100 interface Serial0/0/0.100 ip routing
    interface FastEthernet0/0
    ip address 10.58.0.29 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 preempt
    standby 1 priority 105
    standby 1 track 100 decrement 10
    Router 09R Configuration
    track 100 interface Serial0/1/0:0.100 ip routing
    interface FastEthernet0/0
    ip address 10.58.0.31 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 preempt
    standby 1 priority 101
    standby 1 track 100 decrement 10
    Ref.: CCO
    /André

  • Redundacy Not happening after interface goes down.

    Dear All,
    I have the set up which I have attached. To brief, I have 2 CSS 11501 in two different locations connected each other via fibre and running redundnacy protocol on the link as heartbeat.
    The problem I am facing is if the interface through which the services are running fails the redundancy is not happening the master remains the master and the standby is standby and we have a services unavailable.
    the configuration is given below
    CSS_ACTIVE# sh run
    !Generated on 03/07/2010 22:26:21
    !Active version: sg0810106
    configure
    !*************************** GLOBAL ***************************
      username admin des-password lcof1eugqece2afd superuser
      bridge spanning-tree disabled
      arp timeout 1400
      no restrict web-mgmt
      ip redundancy master
      app
      app session 10.90.1.2
      ip route 10.50.3.0 255.255.255.0 10.50.9.1 1
    !************************* INTERFACE *************************
    interface e1
      trunk
      vlan 11
        default-vlan
      vlan 20
      vlan 21
    interface e9
      description "REDUNDANCY - CSS-STANDBY PORT 9"
      bridge vlan 23
    !************************** CIRCUIT **************************
    circuit VLAN11
      description "MANAGEMENT IP ADDRESS"
      ip address 10.7.10.20 255.255.255.0
    circuit VLAN20
      description "CSS_SERVER_VLAN"
      redundancy
      ip address 10.50.7.4 255.255.255.0
    circuit VLAN21
      description "CSS_CLIENT_VLAN"
      redundancy
      ip address 10.50.9.7 255.255.255.0
    circuit VLAN23
      description "REDUNDANT LINK TO CSS-STANDBY"
      ip address 10.90.1.1 255.255.255.0
        redundancy-protocol
    !************************** SERVICE **************************
    service Web1
      ip address 10.50.7.5
      active
    service Web2
      ip address 10.50.7.6
      active
    !*************************** OWNER ***************************
    owner KIM
      content web
        add service Web1
        add service Web2
        vip address 10.50.9.2
        advanced-balance sticky-srcip
        active
    CSS_ACTIVE#  
    CSS_STANDBY# sh run
    !Generated on 03/07/2010 22:31:42
    !Active version: sg0810106
    configure
    !*************************** GLOBAL ***************************
      ip redundancy
      bridge spanning-tree disabled
      arp timeout 1400
      no restrict web-mgmt
      app
      app session 10.90.1.1
      ip route 10.50.3.0 255.255.255.0 10.50.9.1 1
    !************************* INTERFACE *************************
    interface e1
      description "TRUNK "
      trunk
      vlan 11
        default-vlan
      vlan 20
      vlan 21
    interface e9
      description "REDUNDANCY - CSS-STANDY PORT 9"
      bridge vlan 23
    interface Ethernet-Mgmt
      phy 10Mbits-FD
      admin-shutdown
    !************************** CIRCUIT **************************
    circuit VLAN11
      description "MANAGEMENT IP ADDRESS"
      ip address 10.7.10.21 255.255.255.0
    circuit VLAN20
      description "CSS_SERVER_VLAN"
      redundancy
      ip address 10.50.7.4 255.255.255.0
    circuit VLAN21
      description "CSS_CLIENT_VLAN"
      redundancy
      ip address 10.50.9.7 255.255.255.0
    circuit VLAN23
      description "REDUNDANT LINK TO CSS-STANDBY"
      ip address 10.90.1.2 255.255.255.0
        redundancy-protocol
    !************************** SERVICE **************************
    service Web1
      ip address 10.50.7.5
      active
    service Web2
      ip address 10.50.7.6
      active
    !*************************** OWNER ***************************
    owner KIM
      content web
        add service Web1
        add service Web2
        vip address 10.50.9.2
        advanced-balance sticky-srcip
        active
    CSS_STANDBY#
    If the interface e1 fails on active the redundancy is not shifting to standby.

    You have setup box-to-box redundancy.
    This mechanism is very basic and only detects a box failure.  So, as long as the master can send heartbeat through the 'redundancy protocol' interface it will stay master.
    You should use interface/vip redundancy.
    A little bit more complex to configure but much more robust and with more features including interface failure detection.
    http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v8.20_v8.10/configuration/redundancy/guide/VIPRedun.html
    Gilles.

  • The accu of my MACBook Air goes down half the time as before I installed the new Mountain Lion OS. Any help or suggestions?

    After installiong the OS Mountain Lion the power of my Apple Airbook (2012) went down twice faster than before. Does anybody knows why?
    As well I lost my backup HD. After installation of Mountain Lion the HD was not anymore available!
    Any solution?
    Rgs Thomas

    It is likely not working from the same coffee spill. You can use Apple's hardware tests to see if any errors show up on sensors (voltage or current sensors) that might indicate the problem (see here for info on the tests: http://reviews.cnet.com/8301-13727_7-57352461-263/how-to-invoke-and-interpret-th e-apple-hardware-tests/). While you can try using dionized water to gently wash the port and spray it out (open the system to do this from the inside), it's not a guaranteed fix and could potentially harm other aspects of the system; however, since you recovered it from a similar spill and got it cheaply it may be worth a shot.

  • Network ce0 interface goes down when reboots  or does not come up

    Hi,
    Have a V440 and on reboot the main ip ce0 is not up. I have to manually go in and ifconfig 192.168.1.3 up
    My hostname.ce0
    192.168.1.3
    # wc /etc/hostname.ce0
    2 1 13 /etc/hostname.ce0
    # ifconfig -a
    lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    inet 127.0.0.1 netmask ff000000
    ce0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.3 netmask ffffff00 broadcast 192.168.1.255
    ether 0:3:ba:d5:ba:2b
    ce0:1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.76 netmask ffffff00 broadcast 192.168.1.255
    ce0:4: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.72 netmask ffffff00 broadcast 192.168.1.255
    ce0:5: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.66 netmask ffffff00 broadcast 192.168.1.255
    ce0:6: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.47 netmask ffffff00 broadcast 192.168.1.255
    ce0:7: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.42 netmask ffffff00 broadcast 192.168.1.255
    ce0:8: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.69 netmask ffffff00 broadcast 192.168.1.255
    ce0:9: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.88 netmask ffffff00 broadcast 192.168.1.255
    ce0:10: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.45 netmask ffffff00 broadcast 192.168.1.255
    ce0:11: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.90 netmask ffffff00 broadcast 192.168.1.255
    ce0:12: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.98 netmask ffffff00 broadcast 192.168.1.255
    ce0:13: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.73 netmask ffffff00 broadcast 192.168.1.255
    ce0:14: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.87 netmask ffffff00 broadcast 192.168.1.255
    ce0:15: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.48 netmask ffffff00 broadcast 192.168.1.255
    ce0:16: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.103 netmask ffffff00 broadcast 192.168.1.255
    ce0:17: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.44 netmask ffffff00 broadcast 192.168.1.255
    ce0:18: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.78 netmask ffffff00 broadcast 192.168.1.255
    ce0:19: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.46 netmask ffffff00 broadcast 192.168.1.255
    ce0:21: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.56 netmask ffffff00 broadcast 192.168.1.255
    ce0:22: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.77 netmask ffffff00 broadcast 192.168.1.255
    ce0:23: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.80 netmask ffffff00 broadcast 192.168.1.255
    ce0:24: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.83 netmask ffffff00 broadcast 192.168.1.255
    ce0:25: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.84 netmask ffffff00 broadcast 192.168.1.255
    ce0:26: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.67 netmask ffffff00 broadcast 192.168.1.255
    ce0:28: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.41 netmask ffffff00 broadcast 192.168.1.255
    ce0:29: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.64 netmask ffffff00 broadcast 192.168.1.255
    ce0:30: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.57 netmask ffffff00 broadcast 192.168.1.255
    ce0:31: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.71 netmask ffffff00 broadcast 192.168.1.255
    ce0:32: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.86 netmask ffffff00 broadcast 192.168.1.255
    ce0:33: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.59 netmask ffffff00 broadcast 192.168.1.255
    ce0:34: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.65 netmask ffffff00 broadcast 192.168.1.255
    ce0:35: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.104 netmask ffffff00 broadcast 192.168.1.255
    ce0:36: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.97 netmask ffffff00 broadcast 192.168.1.255
    ce0:37: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.70 netmask ffffff00 broadcast 192.168.1.255
    ce0:38: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.74 netmask ffffff00 broadcast 192.168.1.255
    ce0:39: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.79 netmask ffffff00 broadcast 192.168.1.255
    ce0:41: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.68 netmask ffffff00 broadcast 192.168.1.255
    ce0:42: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.43 netmask ffffff00 broadcast 192.168.1.255
    ce0:43: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.85 netmask ffffff00 broadcast 192.168.1.255
    ce0:44: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.105 netmask ffffff00 broadcast 192.168.1.255
    ce0:45: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.60 netmask ffffff00 broadcast 192.168.1.255
    ce0:46: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.82 netmask ffffff00 broadcast 192.168.1.255
    ce0:47: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.96 netmask ffffff00 broadcast 192.168.1.255
    ce0:48: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.94 netmask ffffff00 broadcast 192.168.1.255
    ce0:49: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.81 netmask ffffff00 broadcast 192.168.1.255
    ce0:50: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.106 netmask ffffff00 broadcast 192.168.1.255
    ce0:51: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.53 netmask ffffff00 broadcast 192.168.1.255
    ce0:52: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.91 netmask ffffff00 broadcast 192.168.1.255
    ce0:53: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.49 netmask ffffff00 broadcast 192.168.1.255
    ce0:54: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.63 netmask ffffff00 broadcast 192.168.1.255
    ce0:55: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.102 netmask ffffff00 broadcast 192.168.1.255
    ce0:56: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.62 netmask ffffff00 broadcast 192.168.1.255
    ce0:57: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.107 netmask ffffff00 broadcast 192.168.1.255
    ce0:58: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.130 netmask ffffff00 broadcast 192.168.1.255
    ce0:59: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.131 netmask ffffff00 broadcast 192.168.1.255
    ce0:60: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.132 netmask ffffff00 broadcast 192.168.1.255
    ce0:61: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.134 netmask ffffff00 broadcast 192.168.1.255
    ce0:62: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.135 netmask ffffff00 broadcast 192.168.1.255
    ce0:63: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.136 netmask ffffff00 broadcast 192.168.1.255
    ce0:64: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.138 netmask ffffff00 broadcast 192.168.1.255
    ce0:65: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.139 netmask ffffff00 broadcast 192.168.1.255
    ce0:66: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.140 netmask ffffff00 broadcast 192.168.1.255
    ce0:67: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.141 netmask ffffff00 broadcast 192.168.1.255
    ce0:68: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.142 netmask ffffff00 broadcast 192.168.1.255
    ce0:69: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.143 netmask ffffff00 broadcast 192.168.1.255
    ce0:70: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.145 netmask ffffff00 broadcast 192.168.1.255
    ce0:71: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.146 netmask ffffff00 broadcast 192.168.1.255
    ce0:72: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.147 netmask ffffff00 broadcast 192.168.1.255
    ce0:73: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.151 netmask ffffff00 broadcast 192.168.1.255
    ce0:74: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.152 netmask ffffff00 broadcast 192.168.1.255
    ce0:75: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.153 netmask ffffff00 broadcast 192.168.1.255
    ce0:76: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.154 netmask ffffff00 broadcast 192.168.1.255
    ce0:77: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.155 netmask ffffff00 broadcast 192.168.1.255
    ce0:78: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.156 netmask ffffff00 broadcast 192.168.1.255
    ce0:79: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.157 netmask ffffff00 broadcast 192.168.1.255
    ce0:80: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.158 netmask ffffff00 broadcast 192.168.1.255
    ce0:81: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.189 netmask ffffff00 broadcast 192.168.1.255
    ce0:82: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.211 netmask ffffff00 broadcast 192.168.1.255
    ce0:83: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.212 netmask ffffff00 broadcast 192.168.1.255
    ce0:84: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.213 netmask ffffff00 broadcast 192.168.1.255
    ce0:85: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.214 netmask ffffff00 broadcast 192.168.1.255
    ce0:86: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.215 netmask ffffff00 broadcast 192.168.1.255
    ce0:87: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.216 netmask ffffff00 broadcast 192.168.1.255
    ce0:88: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.217 netmask ffffff00 broadcast 192.168.1.255
    ce0:89: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.218 netmask ffffff00 broadcast 192.168.1.255
    ce0:90: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.219 netmask ffffff00 broadcast 192.168.1.255
    lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
    inet6 ::1/128
    Any help would be great!
    Thanks
    Marc

    msglobal3 wrote:
    Hi,
    Have a V440 and on reboot the main ip ce0 is not up. I have to manually go in and ifconfig 192.168.1.3 up
    My hostname.ce0
    192.168.1.3
    # wc /etc/hostname.ce0
    2 1 13 /etc/hostname.ce0The 'wc' output shows that you have a blank line in the file.
    Remove that line (so that 'wc' reports only 1 line present) and the interface will be brought up at boot time.
    Darren

  • Oracle RAC with QFS shared storage going down when one disk fails

    Hello,
    I have an oracle RAC on my testing environment. The configuration follows
    nodes: V210
    Shared Storage: A5200
    #clrg status
    Group Name Node Name Suspended Status
    rac-framework-rg host1 No Online
    host2 No Online
    scal-racdg-rg host1 No Online
    host2 No Online
    scal-racfs-rg host1 No Online
    host2 No Online
    qfs-meta-rg host1 No Online
    host2 No Offline
    rac_server_proxy-rg host1 No Online
    host2 No Online
    #metastat -s racdg
    racdg/d200: Concat/Stripe
    Size: 143237376 blocks (68 GB)
    Stripe 0:
    Device Start Block Dbase Reloc
    d3s0 0 No No
    racdg/d100: Concat/Stripe
    Size: 143237376 blocks (68 GB)
    Stripe 0:
    Device Start Block Dbase Reloc
    d2s0 0 No No
    #more /etc/opt/SUNWsamfs/mcf
    racfs 10 ma racfs - shared
    /dev/md/racdg/dsk/d100 11 mm racfs -
    /dev/md/racdg/dsk/d200 12 mr racfs -
    When the disk /dev/did/dsk/d2 failed (I have failed it by removing from the array), the oracle RAC went offline on both nodes, and then both nodes paniced and rebooted. Now the #clrg status shows below output.
    Group Name Node Name Suspended Status
    rac-framework-rg host1 No Pending online blocked
    host2 No Pending online blocked
    scal-racdg-rg host1 No Online
    host2 No Online
    scal-racfs-rg host1 No Online
    host2 No Pending online blocked
    qfs-meta-rg host1 No Offline
    host2 No Offline
    rac_server_proxy-rg host1 No Pending online blocked
    host2 No Pending online blocked
    crs is not started in any of the nodes. I would like to know if anybody faced this kind of a problem when using QFS on diskgroup. When one disk is failed, the oracle is not supposed to go offline as the other disk is working, and also my qfs configuration is to mirror these two disks !!!!!!!!!!!!!!
    Many thanks in advance
    Ushas Symon

    I'm not sure why you say QFS is mirroring these disks!?!? Shared QFS has no inherent mirroring capability. It relies on the underlying volume manager (VM) or array to do that for it. If you need to mirror you storage, you do it at the VM level by creating a mirrored metadevice.
    Tim
    ---

  • Oracle 10G Db Starts-up After Server Reboot, BUT Goes DOWN After Some Time

    Hi All,
    I am really puzzled over this one. I have couple of servers running DB on them and I have used scripts to auto-enable them when server(s) reboot.
    But there is one server where I see this funny behavior.
    The DB comes-up after server reboot.
    I can verify that in the startup logs and some more logs that I created.
    I can see that LISTENER is able to communicate also.
    But after a while, the DB shuts-down....!!
    I have checked all the places I could. I have also tried to see the difference between this server and others (I did not install this one), but can not see any difference.
    Is there anyway to find out (log) what is shutting down the DB??
    Any help will be much appreciated as I am at my wits end.
    Following is snap-shot from my logs:
    Fri Mar 16 20:42:29 EDT 2007
    Running dbstart.
    Done with starting all, let's check status...
    Fri Mar 16 20:42:42 EDT 2007
    LSNRCTL for Solaris: Version 10.2.0.1.0 - Production on 16-MAR-2007 20:42:42
    Copyright (c) 1991, 2005, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Solaris: Version 10.2.0.1.0 - Production
    Start Date 16-MAR-2007 00:46:56
    Uptime 0 days 19 hr. 55 min. 46 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /oracle/product/10.2.0/Db_1/network/admin/listener.ora
    Listener Log File /oracle/product/10.2.0/Db_1/network/log/listener.log
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.103.253.50)(PORT=1521)))
    Services Summary...
    Service "orcl" has 2 instance(s).
    Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
    Instance "orcl", status READY, has 1 handler(s) for this service...
    Service "orclXDB" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    Service "orcl_XPT" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    The command completed successfully
    Current Status:
    # date
    Fri Mar 16 21:30:40 EDT 2007
    # su - oracle -c "lsnrctl status"
    Sun Microsystems Inc. SunOS 5.10 Generic January 2005
    LSNRCTL for Solaris: Version 10.2.0.1.0 - Production on 16-MAR-2007 21:30:53
    Copyright (c) 1991, 2005, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    Solaris Error: 146: Connection refused
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.103.253.50)(PORT=1521)))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    Solaris Error: 146: Connection refused

    I was just looking at that.. Thanks for the tip.
    Following is what I see. But not sure what does it tell me?? Please help......
    From alert_orcl.log:
    <snip>
    db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Fri Mar 16 20:42:41 2007
    Errors in file /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-12663: Services required by client not available on the server
    ORA-36961: Oracle OLAP is not available.
    ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
    ORA-06512: at line 15
    Fri Mar 16 20:42:42 2007
    Completed: ALTER DATABASE OPEN
    From /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
    # cat /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
    /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
    Oracle Database 10g Release 10.2.0.1.0 - 64bit Production
    ORACLE_HOME = /oracle/product/10.2.0/Db_1
    System name: SunOS
    Node name: gcars0j6
    Release: 5.10
    Version: Generic_118833-24
    Machine: sun4u
    Instance name: orcl
    Redo thread mounted by this instance: 1
    Oracle process number: 15
    Unix process pid: 7700, image: oracle@gcars0j6 (TNS V1-V3)
    *** SERVICE NAME:() 2007-03-16 20:42:37.548
    *** SESSION ID:(159.3) 2007-03-16 20:42:37.548
    Thread 1 checkpoint: logseq 255, block 2, scn 8602014
    cache-low rba: logseq 255, block 3
    on-disk rba: logseq 255, block 767, scn 8602399
    start recovery at logseq 255, block 3, scn 0
    ----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 382Kb in 0.16s => 2.33 Mb/sec
    Total physical reads: 4096Kb
    Longest record: 3Kb, moves: 0/1066 (0%)
    Change moves: 1/8 (12%), moved: 0Mb
    Longest LWN: 308Kb, moves: 0/29 (0%), moved: 0Mb
    Last redo scn: 0x0000.0083431e (8602398)
    ----- Recovery Hash Table Statistics ---------
    Hash table buckets = 32768
    Longest hash chain = 1
    Average hash chain = 149/149 = 1.0
    Max compares per lookup = 1
    Avg compares per lookup = 1925/2083 = 0.9
    *** 2007-03-16 20:42:37.702
    KCRA: start recovery claims for 149 data blocks
    *** 2007-03-16 20:42:37.705
    KCRA: blocks processed = 149/149, claimed = 149, eliminated = 0
    *** 2007-03-16 20:42:37.706
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 255 Reading mem 0
    ----- Recovery Hash Table Statistics ---------
    Hash table buckets = 32768
    Longest hash chain = 1
    Average hash chain = 149/149 = 1.0
    Max compares per lookup = 1
    Avg compares per lookup = 2054/2074 = 1.0
    Error in executing triggers on database startup
    *** 2007-03-16 20:42:41.963
    ksedmp: internal or fatal error
    ORA-00604: error occurred at recursive SQL level 1
    ORA-12663: Services required by client not available on the server
    ORA-36961: Oracle OLAP is not available.
    ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
    ORA-06512: at line 15

  • Internet goes down at certain times

    My Interenet has been going out at the same time every night around 11pm -12am. I also have phone service through comcast which also obviously goes out. It does not come back on for hours. I work from home and teach classes on the internet. This is REALLY a problem. I have called numerous times in the past months and had a tech come out with no solution. I try to send a refresh and it ALWAYS fails. It has even failed when the Customer Service Rep assists. I am thinking about replacing the box. If this does not help I will change my service. I have had Comcast in a different city in the past and never had these issues. FYI: My Cable TV always works fine.

    Please give us more information:
    1) Please connect your computer directly to the modem via Ethernet ( no router, no wireless, no USB )
    2) Run ShaperProbe and post your results. (It works with Win 7)
    3) Post your upstream and downstream signal levels (click the link.) We are interested in your power levels (dBmV) and your Signal to Noise Ratio (SNR).
    4) Let us know to what speed tier you subscribe.
    5) Post the make a model of your modem.
    6) Post your modem's error logs.
     

  • Javax.management.InstanceNotFoundException --- and the admin goes down

    we are running on WLS 8.1 ,
    and from past two weeks we are facing issues with the admin frequebntly going down,
    i see this errros every time this goes down
    javax.management.InstanceNotFoundException: mydomain:Name=ms1,Server=ms1,Type=Log (admin server:true)
    at weblogic.management.internal.MBeanHomeImpl.getMBean_helper(MBeanHomeImpl.java:145)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:130)
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:263)
    at weblogic.management.internal.AdminMBeanHomeImpl.registerConfigMBeansForAdminChanges(AdminMBeanHomeImpl.java:1014)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    how ever the ms1 nolonger existis in the domain....

    Can you tell more about your domain configuration, and about ms1, was it configured as part of a cluster ? Since when is it not available. Were all the servers restarted after ms1 was down.. Does your config.xml still contain reference to ms1 ? if you remove it.
    The file running-managed-servers.xml also keeps track of the active managed servers, ensure that ms1 is not listed in it, and if it is there, remove the entry from this file, or delete this file before starting the admin server.

  • L2TP script to initiate a router reload when tunnel goes down - working

    Hi,
         Just thought I would post a working EEM script on doing a router reload when the L2TP tunnel goes down....
    I am using a 3825 router to initiate a site-to-site tunnel with a 3rd party vpn service - StrongVPN.  On the odd occasion when the tunnel goes down, the l2tp tunnel state goes to "no session left" and the virtual-ppp1 interface - which is tied to the l2tp vpn - goes down.  Unfortunately, because I have no control on the far end router, the only way to bring it back up is thru a router reload....
    Here you go:
    event manager applet L2TP-DOWN
    event syslog pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-PPP1, changed state to down"
    action 1.0 syslog msg "The L2TP VPN is down"
    action 1.1 cli command "enable"
    action 1.2 cli command "reload in 10" pattern "confirm"
    action 1.3 cli command ""
    action 1.4 syslog msg "EEM scheduled reload in 10 minutes"
    event manager applet L2TP-UP
    event syslog pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-PPP1, changed state to up"
    action 1.0 syslog msg "The L2TP VPN is up"
    action 1.1 cli command "enable"
    action 1.2 cli command "reload cancel"
    Jason

    Hi Arie,
         So, here is the script I am using....
    When the L2TP tunnel goes to "no sessions left", the virtual-ppp1 interface goes down.  That's the typical message I get when it goes down.  So, when I reboot the router, the script shows the message that the virtual-ppp1 interface is up when the L2TP tunnel comes up.  I checked the debugs and that is the behaviour when the tunnel goes up / down...
    Here you go:
    event manager applet L2TP-DOWN
    event syslog pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-PPP1, changed state to down"
    action 1.0 syslog msg "The L2TP VPN is down"
    action 1.1 cli command "enable"
    action 1.2 cli command "reload in 10" pattern "confirm"
    action 1.3 cli command ""
    action 1.4 syslog msg "EEM scheduled reload in 10 minutes"
    event manager applet L2TP-UP
    event syslog pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-PPP1, changed state to up"
    action 1.0 syslog msg "The L2TP VPN is up"
    action 1.1 cli command "enable"
    action 1.2 cli command "reload cancel"
    Thanks.

  • Server instance is going down very frequently

    Hi,
    Please help me solving one problem. The details are as follows:
    Two web applications built on struts framework are running on one server. The server is SAPJ2EE 6.20 server which is running on SUSE LINUX.
    I have SAPJ2EE 6.20 client interface using which I deploy these applications. Now once the applications are deployed, it runs perfect but after some time the instance of SAPJ2EE 6.20 application server goes down in linux and it remove these two application.
    To make these two applications avaliable to the users I have to restart the instance of application server on linux and again deploy the applications. The behaviour of the same is very dynamic. Sometime it goes down 2 - 3 times in a day, sometime once in a day,
    sometime once in 3 - 4 days and sometime once in a week.
    On server I checked the logs but I didn't get any clue. The logs contains normal java exceptions like NULLPointerException, ExhaustResultSetException, IOException etc.
    I guess the application is throwing some error because of which the server instance is going down and these errors are not showing in logs.( By error I don't mean exceptions, I mean errors like MemoryError etc.)
    Am I thinking correct or is their any other issue? How to verify what is going wrong?
    Please please please guide me on this as this is very important for me.
    thanks and regards

    Hi,
    I would suggest to have look at the application server console. Do you see any OutOfMemory or any sort of Exception over there
    Please paste it here
    regards
    Vivek Nidhi.

  • Nokia 5530 xpress music: The volume goes down when...

    Hi All
    I hope all of you are fine
    Nokia 5530 xpress music: when I play the music without Nokia headset the volume seems great but when I play the same song with headset the volume goes down.
    is the problem from Nokia Headset or from the mobile itself?
    Thanks in advance

    I think this is Normal.
    Otherwise It wouldn't do your hearing much good if you set the volume to maximum and then plugged in your headset
    If this Post is helpful. A click on the White Kudos star is always Appreciated
    Last Nokia: Nokia Lumia 800
    Current Phone: A Non Nokia Device
    Previous Phones:Don't Ask ;-)

  • 10g using ASM on AIX going down Intermittently

    I have the below setup
    Oracle10g(10.2.0.3.0) single instance database on AIX 5.3 ML 06 using ASM
    The database along with asm instance is going down intermittently with the below errors,
    database alert log contents as below:-
    Errors in file /oracle/admin/orcl/bdump/orcl_asmb_45396.trc:
    ORA-15064: communication failure with ASM instance
    ORA-03113: end-of-file on communication channel
    Tue Dec 11 10:18:42 2007
    ASMB: terminating instance due to error 15064
    Instance terminated by ASMB, pid = 45396
    asmb trace files contents as below:-
    error 15064 detected in background process
    ORA-15064: communication failure with ASM instance
    ORA-03113: end-of-file on communication channel
    asm alert log contents as below:-
    Tue Dec 11 10:09:20 2007
    NOTE: ASMB process exiting due to lack of ASM file activity
    Tue Dec 11 10:18:42 2007
    Errors in file /oracle/admin/+ASM/bdump/+asm_gmon_172048.trc:
    ORA-29702: error occurred in Cluster Group Service operation
    ORA-29702: error occurred in Cluster Group Service operation
    Tue Dec 11 10:18:42 2007
    GMON: terminating instance due to error 29702
    Instance terminated by GMON, pid = 172048
    gmon trace file contents as below:-
    Tue Dec 11 10:09:20 2007
    NOTE: ASMB process exiting due to lack of ASM file activity
    Tue Dec 11 10:18:42 2007
    Errors in file /oracle/admin/+ASM/bdump/+asm_gmon_172048.trc:
    ORA-29702: error occurred in Cluster Group Service operation
    ORA-29702: error occurred in Cluster Group Service operation
    Tue Dec 11 10:18:42 2007
    GMON: terminating instance due to error 29702
    Instance terminated by GMON, pid = 172048
    Thanks
    Message was edited by:
    user556141

    Hi,
    The metalink documents :
    ASM Crashes When Rebooting a Server With ORA-29702 Error.
    Note:467354.1
    RAC Survival Kit: ORA-29702
    Note:209850.1
    might help.
    Thanks
    Arnab

Maybe you are looking for

  • Database connection to MS SQL 2005 (URGENT Help Needed)

    Hi all, Does anyone know how to connect my adobe form to MS SQL 2005? I have this code: try {      InitialContext initialContext = new InitialContext ();      DataSource dataSource = (DataSource) initialContext.lookup ("jdbc/MyAlias");       java.sql

  • Location services no longer working after 4.3.3 update.

    I have a 3rd Gen 32GB touch, and after updating the software today, my location services no longer work. My device fails to find my location for the maps app, as well as other 3rd party apps. There was no problem with finding my location prior to thi

  • HT1386 Syncing problems with iPhone/MacBook

    Hi! I wan´t the iphone to be the source of notes, calendars and so on. When I sync the iPhone now, it reinstalls older calendar versions from the computer, erases new notes on the iphone and so on. I can´t find how to let the iphone conduct the proce

  • SELECT OPTIONS use in select statement

    hi, I have defined my selection screen in the main program. selection-screen begin of screen 0101 as subscreen. selection-screen begin of block b1. select-options:  S_KUNNR for  KNA1-KUNNR, selection-screen end of block b1. selection-screen end of sc

  • Need assistance calibratin​g a NI 9214 module.

    I am attempting to perform a calibration of a NI 9214 module, as per the instructions in the NI 9214 Calibration Procedure.  All calibration equipment is as per recommendation, with the exception of the calibrator, which is a Fluke 5700A (Fluke 5520A