8 Replies Latest reply: Jan 29, 2013 11:16 AM by Sebastian Solbach -Dba Community-Oracle RSS

    local listener status showing local virtual ip, but not local ip

    SaikatBanerjee
      Hi,

      SNRCTL> stat LISTENER
      Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
      STATUS of the LISTENER
      ------------------------
      Alias LISTENER
      Version TNSLSNR for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
      Start Date 19-JAN-2013 00:50:10
      Uptime 0 days 0 hr. 29 min. 51 sec
      Trace Level off
      Security ON: Local OS Authentication
      SNMP ON
      Listener Parameter File /grid/app/11.2.0/grid/network/admin/listener.ora
      Listener Log File listener.log
      Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.9.50.231)(PORT=1521)))
      Services Summary...


      In every oracle documentation for e.g:11.2 Scan and Node TNS Listener Setup Examples [ID 1070607.1] we found the local listener status showing both local-ip and vip. Why is not showing in our case? What to do?

      Please suggest.

      Regards,
      Saikat
        • 1. Re: local listener status showing local virtual ip, but not local ip
          damorgan
          What's going on? Doesn't anyone posting today believe in patching? Large sums of money invested in high availability but no patching? I don't get it.

          In a RAC cluster the listener should be started and stopped as part of the grid infrastructure. Without knowing specifically how you are logged on, and what you are looking at, it would not be advisable to try to guess at what you are doing.
          • 2. Re: local listener status showing local virtual ip, but not local ip
            SaikatBanerjee
            Hi,

            I am logged in as grid user.
            Went to grid_home/bin

            then fired the above command. But in the output it showed only local-vip(10.9.50.231) but not the local-host-ip.why??Please help me know the reason.


            Is it necessery to local-host-ip to be shown up in local listener status, since local listener listens only on local vip, but not local-host ip?

            But all oracle documentation shows that local listener status shows both the ips...local vip+local-host-ip. Please help.



            Regards,
            Saikat
            • 3. Re: local listener status showing local virtual ip, but not local ip
              8398219
              Did you create the Node Listener using netca ?

              Were you setting the env variables for the Grid Home When creating the node listener using netca and checking the status ?
              The lsnrctl binary you run should be from GI_HOME/bin
              • 4. Re: local listener status showing local virtual ip, but not local ip
                Billy~Verreynne
                Saikat Banerjee wrote:

                Listener Parameter File /grid/app/11.2.0/grid/network/admin/listener.ora
                Contents of this file?

                A TCP end point (listener port) can be bound by
                - telling the socket API to bind it to all IPs (existing now and that may be created in future) on that platform
                - giving the socket API a specific IP address to bind to only

                For an Oracle Listener, this behaviour is determined by the HOST and IP parameters.
                • 5. Re: local listener status showing local virtual ip, but not local ip
                  SaikatBanerjee
                  Hi,

                  Will update the listener file shortly. You said..

                  A TCP end point (listener port) can be bound by
                  - telling the socket API to bind it to all IPs (existing now and that may be created in future) on that platform
                  - giving the socket API a specific IP address to bind to only

                  But, are they(TCP endpoint) must be bound by both ips? Is there any problem in future if local-host-ip is not shown in local-listener status?



                  In production the listener.ora file contains only HOST=local-vip..but listener status showing host=local-vip+ host=local-host-ip.
                  In DR, we were getting only local-vip in lsnrctl status. Then we added local-host ip using netmanager and now both the ips are showing .




                  But, are they(TCP endpoint) must be bound by both ips? Is there any problem in future if local-host-ip is not shown in local-listener status?
                  • 6. Re: local listener status showing local virtual ip, but not local ip
                    Billy~Verreynne
                    Saikat Banerjee wrote:

                    Will update the listener file shortly. You said..

                    A TCP end point (listener port) can be bound by
                    - telling the socket API to bind it to all IPs (existing now and that may be created in future) on that platform
                    - giving the socket API a specific IP address to bind to only

                    But, are they(TCP endpoint) must be bound by both ips? Is there any problem in future if local-host-ip is not shown in local-listener status?
                    It depends on how the Listener is configured.

                    A socket bind() call is used to bind an IP address, or IP addresses, and a port, to a specified socket (created via the socket() call). The listen() is then used to listen for client connect() calls to the socket/listening endpoint.

                    The bind() call supports the INADDR_ANY flag as IP address. This tells the socket layer to bind that socket to all IP addresses of that platform. It also automatically supports any new IP addresses that may be created subsequently on that platform. The bind() parameters also support a single specific IP address - binding only that IP and port to the socket.

                    As I mentioned, the HOST and IP parameters in listener.ora tells the listener how to bind - what parameters to use. And this determines on which IP addresses of that platform, the listener opens tcp listening endpoints. The listener does not arbitrarily decide which IPs to use and not use. It does as the configuration states.
                    • 7. Re: local listener status showing local virtual ip, but not local ip
                      SaikatBanerjee
                      Hi,

                      Thanks a lot for your valubale answers.

                      *1)In 11gR2 RAC I found that listener.ora is used from grid_home and there is no i/p, port no etc. Just key is present . But the status o/p shows ips,hots,ports. Does the oraagent process picks up those information from crs?*


                      [grid@VM-PAGRAC3 admin]$ more listener.ora
                      LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER))))
                      # line added by Agent
                      LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_S
                      CAN1)))) # line added by Agent
                      ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON # line added by
                      Agent
                      ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent
                      [grid@VM-PAGRAC3 admin]$




                      LSNRCTL> stat
                      Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
                      STATUS of the LISTENER
                      ------------------------
                      Alias LISTENER
                      Version TNSLSNR for Linux: Version 11.2.0.3.0 - Production
                      Start Date 25-JAN-2013 10:53:17
                      Uptime 4 days 9 hr. 13 min. 0 sec
                      Trace Level off
                      Security ON: Local OS Authentication
                      SNMP OFF
                      Listener Parameter File /oracle/11.2.0/grid/network/admin/listener.ora
                      Listener Log File /oracle/app/oracle/diag/tnslsnr/VM-PAGRAC3/listener/alert/log.xml
                      Listening Endpoints Summary...
                      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
                      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.17.0.129)(PORT=1521)))
                      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.17.0.133)(PORT=1521)))
                      Services Summary...
                      Service "+ASM" has 1 instance(s).
                      Instance "+ASM1", status READY, has 1 handler(s) for this service...
                      Service "PAGRAC" has 1 instance(s).
                      Instance "PAGRAC1", status READY, has 1 handler(s) for this service...
                      Service "PAGRACXDB" has 1 instance(s).
                      Instance "PAGRAC1", status READY, has 1 handler(s) for this service...
                      The command completed successfully
                      LSNRCTL>

                      2.What is the purpose of endpoint_listener.ora?

                      [grid@VM-PAGRAC3 admin]$ cat endpoints_listener.ora
                      LISTENER_VM-PAGRAC3=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=VM-PAGRAC3-vip)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=10.17.0.129)(PORT=1521)(IP=FIRST)))) # line added by Agent
                      [grid@VM-PAGRAC3 admin]$



                      It seems lots of changes have beeen done in 11gR2 related to listener. If you kindly help me regarding this I willl be grateful.




                      Thanks a lot!
                      Saikat
                      • 8. Re: local listener status showing local virtual ip, but not local ip
                        Sebastian Solbach -Dba Community-Oracle
                        Hi,

                        in 11gR2 all information about the listeners is kept in the OCR and the listener processes read the information out of that (I believe via. oraagent over crs and not directly, but that detail should not be an issue).
                        However there are some usecases where the listener.ora is still needed (e.g. for setting up Data Guard or ExtProc).

                        Also there are some older programs (can't remember which), which rely on the entries in listener.ora. For backward compatibility these information is written by the oraagent to the endpointlistener.ora file.

                        Regards
                        Sebastian