Cluster interconnect using listening port 8059 + 8060

Hello,
I have 4 tomcat instances running on a zone which are being redirected to an apache via jkmounts.
One of the tomcats is running on port 8050 and with a listener setup on 8059.
I was wondering why this was the only port Apache wasn't picking up. A tail-f of the catalina.out shows that port 8059 was busy, so it tries to connect the listener to 8060... also busy, so it finally binds to 8061.
Ports 8059 and 8060 are being used by the cluster interconnects as shown in netstat below:
*.* *.* 0 0 49152 0 IDLE
localhost.5999 *.* 0 0 49152 0 LISTEN
*.scqsd* . *0 0 49152 0 LISTEN*
.scqsd *.* 0 0 49152 0 LISTEN
**.8059* . *0 0 49152 0 LISTEN**
*.8060 *.* 0 0 49152 0 LISTEN*
*.* *.* 0 0 49152 0 IDLE
*.sunrpc* . *0 0 49152 0 LISTEN*
. . *0 0 49152 0 IDLE*
localhost.5987 . *0 0 49152 0 LISTEN*
localhost.898 . *0 0 49152 0 LISTEN*
localhost.32781 . *0 0 49152 0 LISTEN*
localhost.5988 . *0 0 49152 0 LISTEN*
localhost.32782 . *0 0 49152 0 LISTEN*
.ssh *.* 0 0 49152 0 LISTEN
*.32783* . *0 0 49152 0 LISTEN*
.32784 *.* 0 0 49152 0 LISTEN
*.sccheckd* . *0 0 49152 0 LISTEN*
.32785 *.* 0 0 49152 0 LISTEN
*.servicetag* . *0 0 49152 0 LISTEN*
localhost.smtp . *0 0 49152 0 LISTEN*
localhost.submission . *0 0 49152 0 LISTEN*
.32798 *.* 0 0 49152 0 LISTEN
*.pnmd* . *0 0 49152 0 LISTEN*
.32811 *.* 0 0 49152 0 BOUND
localhost.6788 *.* 0 0 49152 0 LISTEN
localhost.6789 *.* 0 0 49152 0 LISTEN
scmars.ssh 161.228.79.36.54693 65180 51 49640 0 ESTABLISHED
localhost.32793 *.* 0 0 49152 0 LISTEN
*172.16.1.1.35136 172.16.1.2.8059 49640 0 49640 0 ESTABLISHED*
*172.16.1.1.35137 172.16.1.2.8060 49640 0 49640 0 ESTABLISHED*
*172.16.1.1.35138 172.16.1.2.8060 49640 0 49640 0 ESTABLISHED*
*172.16.1.1.35139 172.16.1.2.8060 49640 0 49640 0 ESTABLISHED*
*172.16.1.1.35140 172.16.1.2.8060 49640 0 49640 0 ESTABLISHED*
*172.16.0.129.35141 172.16.0.130.8059 49640 0 49640 0 ESTABLISHED*
*172.16.0.129.35142 172.16.0.130.8060 49640 0 49640 0 ESTABLISHED*
*172.16.0.129.35143 172.16.0.130.8060 49640 0 49640 0 ESTABLISHED*
*172.16.0.129.35144 172.16.0.130.8060 49640 0 49640 0 ESTABLISHED*
*172.16.0.129.35145 172.16.0.130.8060 49640 0 49640 0 ESTABLISHED*
My question is, how can I modify the ports being used by the cluster interconnects as I would like to keep port 8059 as the tomcat listener port?
Any help is appreciated.
Thanks!

Hi,
unfortunately the ports used by Sun Cluster are hard wired, su you must cnge your Tomcat port.
Sorry for the bad news
Detlef

Similar Messages

Cluster Interconnect information

Hi,
We have a two node cluster (10.2.0.3) running on top of Solaris and Veritas SFRAC.
The cluster is working fine. I would like to get more information about the private cluster interconnect used by the Oracle Clusterware but the two places I could think of have shown nothing.
SQL> show parameter cluster_interconnects;
NAME TYPE VALUE
cluster_interconnects string
SQL> select * from GV$CLUSTER_INTERCONNECTS;
no rows selected
I wasn't expecting to see anything in the cluster_interconnects parameter but thought there would be something in the dictionary view.
I'd be grateful if anyone could shed some light on this.
Where can I get information about the currently configured private interconnect?
I've yet to check the OCR, does anyone know which key/values are relevant, if any?
Thanks
user234564

Try this:
1. $ORA_CRS_HOME/bin/oifcfg getif
eth0 1xx.xxx.x.0 global public
eth1 192.168.0.0 global cluster_interconnect
2. V$CONFIGURED_INTERCONNECTS;
3. X$KSXPIA;
HTH
Thanks
Chandra Pabba

RAC interconnect using UDP - default ports?

Is there a default port used by each cluster member to listen for connections over UDP? We use IPTABLES firewalls on our hosts, and I need to ensure the cluster heartbeat traffic gets through the firewall properly.
Thanks in advance.
Jeff

user2528460 wrote:
I understood the UPD ports that are going to be used on the interconnect (clearly without a firewall). Is there a set of default ports?I did a quick count (using <i>lsof</i> to list UDP ports opened on the Interconnect interface) that showed over 185 UDP ports in use.. E.g.
[root ~]# lsof -n -i | grep UDP | grep "10.0.1.1"
oracle     5577 oracle   10u IPv4   130938       UDP 10.0.1.1:22747
oracle     5577 oracle   15u IPv4   130941       UDP 10.0.1.1:64265
oracle     5579 oracle   10u IPv4   130948       UDP 10.0.1.1:39566
oracle     5579 oracle   15u IPv4   130951       UDP 10.0.1.1:55454
oracle     5579 oracle   21u IPv4   130970       UDP 10.0.1.1:27897
oracle     5581 oracle   10u IPv4   130973       UDP 10.0.1.1:14118
oracle     5581 oracle   15u IPv4   130976       UDP 10.0.1.1:13774
oracle     5583 oracle   10u IPv4   130983       UDP 10.0.1.1:33277
oracle     5583 oracle   15u IPv4   130986       UDP 10.0.1.1:6886
..snipped..I would not be concerned about what ports are in use. The important decisions are do you use bonding for the Interconnect, do you use jumbo or super-jumbo frames (MTU sizes), and so on. The actual ports being used has no real bearing as firewalling is not applicable.

Changing the listener port number in a cluster environment

Hello,
I have an Oracle 10g database on a Windows cluster environment with Oracle Fail safe. I am trying to change the default listener port number - these are the steps I have done to change the port number:
1) Take the listener offline via Oracle Fail safe
2) stop the original listener from the command line
3) change the port number in the listener.ora file & save
4) start the original listener
5) bring the listener online in Fail safe
6) register the listener in the database with ALTER SYSTEM SET LOCAL_LISTENER....
After all this, when i check the status of the listener via lsnrctl, i see that the new port number is used, however in the Fail safe administrator, I still see the default port 1521. How do I go about changing the port number so that Fail safe also registers the change?

I did troubleshooting to verify the group, but this just changed the port number back to the default in the listener.ora & tnsnames.ora.
So I did all the steps again to change the port number from the default to another - via lsnrctl status, i see that the new port number is being used, I can also log in to the database via Toad using the new port number, in v$parameter i see that the local_listener is registered on the new port number....only under the Fail Safe manager, the port number (under listener parameter) has not changed....it still shows the default port number. Anyone know how to change this???

Should The Cluster server have a diff. listening port.

          Hello,
          I have 2 managed servers and the main admin server, which routes the requests
          to one of the 2 Managed Server instances on the round-robin algo... Should the
          Admin server's have a diff. listening port like(7001 as per default) to that of
          the 2 Managed servers which r listening on 7005, why is this needed, is there
          a major advantage on doing this... Plz clarify... and can we call the Managed
          servers as Cluster instances...
          Thanx in Advance


You can run admin & managed servers on the same port number.
          and yes you can call managed servers which are part of cluster called as
          clustered instances/nodes etc...
          Kumar
          VenkatRahul wrote:
          > Hello,
          >
          > I have 2 managed servers and the main admin server, which routes the requests
          > to one of the 2 Managed Server instances on the round-robin algo... Should the
          > Admin server's have a diff. listening port like(7001 as per default) to that of
          > the 2 Managed servers which r listening on 7005, why is this needed, is there
          > a major advantage on doing this... Plz clarify... and can we call the Managed
          > servers as Cluster instances...
          >
          > Thanx in Advance
          >

Listen port of cluster server instances

          Hi,
          Is it required for the server instances in a cluster to have the
          same listen port. In such a case it will not possible to have
          more than a single server in one machine becoz only one server can be listening
          to a single port.
          Plz guid me..
          thanx in adv
          pradeep


[att1.html]

Why WebLogic Server uses '7001' as its default listen port ?

I have an interesting question about "Why WebLogic Server uses '7001' as its default listen port ?" .
Any historical consideration or just fun?
Regards,
wenpin

HI I updated my AMagent.properties file as CDSSO = enable, after doing this I entered user id password in access manager console, after that i am getting an error Access to resource is denied, its not updating any log file in Agent machine
Thanks
Saikumar T

Aggregates, VLAN's, Jumbo-Frames and cluster interconnect opinions

Hi All,
I'm reviewing my options for a new cluster configuration and would like the opinions of people with more expertise than myself out there.
What I have in mind as follows:
2 x X4170 servers with 8 x NIC's in each.
On each 4170 I was going to configure 2 aggregates with 3 nics in each aggregate as follows
igb0 device in aggr1
igb1 device in aggr1
igb2 device in aggr1
igb3 stand-alone device for iSCSI network
e1000g0 device in aggr2
e1000g1 device in aggr2
e1000g2 device in aggr3
e1000g3 stand-alone device of iSCSI network
Now, on top of these aggregates, I was planning on creating VLAN interfaces which will allow me to connect to our two "public" network segments and for the cluster heartbeat network.
I was then going to configure the vlan's in an IPMP group for failover. I know there are some questions around that configuration in the sense that IPMP will not detect a nic failure if a NIC goes offline in the aggregate, but I could monitor that in a different manner.
At this point, my questions are:
[1] Are vlan's, on top of aggregates, supported withing Solaris Cluster? I've not seen anything in the documentation to mention that it is, or is not for that matter. I see that vlan's are supported, inluding support for cluster interconnects over vlan's.
Now with the standalone interface I want to enable jumbo frames, but I've noticed that the igb.conf file has a global setting for all nic ports, whereas I can enable it for a single nic port in the e1000g.conf kernel driver. My questions are as follows:
[2] What is the general feeling with mixing mtu sizes on the same lan/vlan? Ive seen some comments that this is not a good idea, and some say that it doesnt cause a problem.
[3] If the underlying nic, igb0-2 (aggr1) for example, has 9k mtu enabled, I can force the mtu size (1500) for "normal" networks on the vlan interfaces pointing to my "public" network and cluster interconnect vlan. Does anyone have experience of this causing any issues?
Thanks in advance for all comments/suggestions.

For 1) the question is really "Do I need to enable Jumbo Frames if I don't want to use them (neither public nore private network)" - the answer is no.
For 2) each cluster needs to have its own seperate set of VLANs.
Greets
Thorsten

Changing the Listener Port Number

Hi RACers,
I need to change the TNS listener port number from the default of 1521 (don't ask!).
I'm on Solaris10/Oracle10g 10.2.0.3 using a 2 node cluster.
I've tried editing the relevant files, bouncing everything and re-starting CRS, but that doesn't work. I tried using Netca to delete the listener and re-create it with a different port number and that didn't work either. The instances did not re-register despite having their local_listener parameter changes.
Obviously I'm doing something wrong, but don't know what. Any ideas or do you know where a procedure to do this is documented?
Thanks in advance.

My posting was not aimed at the OP at all.. not his fault that Oracle insists on using a TCP port that's NOT registered for Oracle use.
It is all Oracle's fault that port 1521 is used instead of 1527.
As for what Oracle books say.. bahumbug. Means nothing ito playing by the same networking rules as everyone else.
Port 1527 is what is registered for and by Oracle as use for Oracle tcp traffic. Not fricken port 1521!
And why is this a problem?
If you're in the network business and deal with everything and anything from network analysis and management to rewriting ToS bytes for proper DiffServ application.. then it is very frustrating to find a major company like Oracle ignoring the networking rules.
I read that as Oracle telling us "screw you".

IPFC (ip over fc) cluster interconnect

Hello!
It a possible create cluster interconnect with IPFC (ip over fc) driver (for example - a reserve channel) ?
What problems may arise?

Hi,
technically Sun Cluster works fine with only a single interconnect, but it used to be not supported. The mandatory requirement to have 2 dedicated interconnects was lifted a couple of months ago. Although it is still a best practice and a recommendation to use 2 independent interconnects.
The possible consequences of only having one NIC port have been mentioned in the previous post.
Regards
Hartmut

LDOM SUN Cluster Interconnect failure

I am making a test SUN-Cluster on Solaris 10 in LDOM 1.3.
in my environment, i have T5120, i have setup two guest OS with some configurations, setup sun cluster software, when executed, scinstall, it failed.
node 2 come up, but node 1 throws following messgaes:
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args:
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: test1
Configuring devices.
Loading smf(5) service descriptions: 37/37
/usr/cluster/bin/scdidadm: Could not load DID instance list.
/usr/cluster/bin/scdidadm: Cannot open /etc/cluster/ccr/did_instances.
Booting as part of a cluster
NOTICE: CMM: Node test2 (nodeid = 1) with votecount = 1 added.
NOTICE: CMM: Node test1 (nodeid = 2) with votecount = 0 added.
NOTICE: clcomm: Adapter vnet2 constructed
NOTICE: clcomm: Adapter vnet1 constructed
NOTICE: CMM: Node test1: attempting to join cluster.
NOTICE: CMM: Cluster doesn't have operational quorum yet; waiting for quorum.
NOTICE: clcomm: Path test1:vnet1 - test2:vnet1 errors during initiation
NOTICE: clcomm: Path test1:vnet2 - test2:vnet2 errors during initiation
WARNING: Path test1:vnet1 - test2:vnet1 initiation encountered errors, errno = 62. Remote node may be down or unreachable through this path.
WARNING: Path test1:vnet2 - test2:vnet2 initiation encountered errors, errno = 62. Remote node may be down or unreachable through this path.
clcomm: Path test1:vnet2 - test2:vnet2 errors during initiation
CREATED VIRTUAL SWITCH AND VNETS ON PRIMARY DOMAIN LIKE:<>
532 ldm add-vsw mode=sc cluster-vsw0 primary
533 ldm add-vsw mode=sc cluster-vsw1 primary
535 ldm add-vnet vnet2 cluster-vsw0 test1
536 ldm add-vnet vnet3 cluster-vsw1 test1
540 ldm add-vnet vnet2 cluster-vsw0 test2
541 ldm add-vnet vnet3 cluster-vsw1 test2
Primary DOmain<>
bash-3.00# dladm show-dev
vsw0 link: up speed: 1000 Mbps duplex: full
vsw1 link: up speed: 0 Mbps duplex: unknown
vsw2 link: up speed: 0 Mbps duplex: unknown
e1000g0 link: up speed: 1000 Mbps duplex: full
e1000g1 link: down speed: 0 Mbps duplex: half
e1000g2 link: down speed: 0 Mbps duplex: half
e1000g3 link: up speed: 1000 Mbps duplex: full
bash-3.00# dladm show-link
vsw0 type: non-vlan mtu: 1500 device: vsw0
vsw1 type: non-vlan mtu: 1500 device: vsw1
vsw2 type: non-vlan mtu: 1500 device: vsw2
e1000g0 type: non-vlan mtu: 1500 device: e1000g0
e1000g1 type: non-vlan mtu: 1500 device: e1000g1
e1000g2 type: non-vlan mtu: 1500 device: e1000g2
e1000g3 type: non-vlan mtu: 1500 device: e1000g3
bash-3.00#
NOde1<>
-bash-3.00# dladm show-link
vnet0 type: non-vlan mtu: 1500 device: vnet0
vnet1 type: non-vlan mtu: 1500 device: vnet1
vnet2 type: non-vlan mtu: 1500 device: vnet2
-bash-3.00# dladm show-dev
vnet0 link: unknown speed: 0 Mbps duplex: unknown
vnet1 link: unknown speed: 0 Mbps duplex: unknown
vnet2 link: unknown speed: 0 Mbps duplex: unknown
-bash-3.00#
NODE2<>
-bash-3.00# dladm show-link
vnet0 type: non-vlan mtu: 1500 device: vnet0
vnet1 type: non-vlan mtu: 1500 device: vnet1
vnet2 type: non-vlan mtu: 1500 device: vnet2
-bash-3.00#
-bash-3.00#
-bash-3.00# dladm show-dev
vnet0 link: unknown speed: 0 Mbps duplex: unknown
vnet1 link: unknown speed: 0 Mbps duplex: unknown
vnet2 link: unknown speed: 0 Mbps duplex: unknown
-bash-3.00#
and this configuration i give while setting up scinstall
Cluster Transport Adapters and Cables <<<You must identify the two cluster transport adapters which attach
this node to the private cluster interconnect.
For node "test1",
What is the name of the first cluster transport adapter [vnet1]?
Will this be a dedicated cluster transport adapter (yes/no) [yes]?
All transport adapters support the "dlpi" transport type. Ethernet
and Infiniband adapters are supported only with the "dlpi" transport;
however, other adapter types may support other types of transport.
For node "test1",
Is "vnet1" an Ethernet adapter (yes/no) [yes]?
Is "vnet1" an Infiniband adapter (yes/no) [yes]? no
For node "test1",
What is the name of the second cluster transport adapter [vnet3]? vnet2
Will this be a dedicated cluster transport adapter (yes/no) [yes]?
For node "test1",
Name of the switch to which "vnet2" is connected [switch2]?
For node "test1",
Use the default port name for the "vnet2" connection (yes/no) [yes]?
For node "test2",
What is the name of the first cluster transport adapter [vnet1]?
Will this be a dedicated cluster transport adapter (yes/no) [yes]?
For node "test2",
Name of the switch to which "vnet1" is connected [switch1]?
For node "test2",
Use the default port name for the "vnet1" connection (yes/no) [yes]?
For node "test2",
What is the name of the second cluster transport adapter [vnet2]?
Will this be a dedicated cluster transport adapter (yes/no) [yes]?
For node "test2",
Name of the switch to which "vnet2" is connected [switch2]?
For node "test2",
Use the default port name for the "vnet2" connection (yes/no) [yes]?
i have setup the configurations like.
ldm list -l nodename
NODE1<>
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw0@primary 0 network@0 00:14:4f:f9:61:63 1 1500
vnet2 cluster-vsw0@primary 1 network@1 00:14:4f:f8:87:27 1 1500
vnet3 cluster-vsw1@primary 2 network@2 00:14:4f:f8:f0:db 1 1500
ldm list -l nodename
NODE2<>
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw0@primary 0 network@0 00:14:4f:f9:a1:68 1 1500
vnet2 cluster-vsw0@primary 1 network@1 00:14:4f:f9:3e:3d 1 1500
vnet3 cluster-vsw1@primary 2 network@2 00:14:4f:fb:03:83 1 1500
ldm list-services
VSW
NAME LDOM MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw0 primary 00:14:4f:f9:25:5e e1000g0 0 switch@0 1 1 1500 on
cluster-vsw0 primary 00:14:4f:fb:db:cb 1 switch@1 1 1 1500 sc on
cluster-vsw1 primary 00:14:4f:fa:c1:58 2 switch@2 1 1 1500 sc on
ldm list-bindings primary
VSW
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw0 00:14:4f:f9:25:5e e1000g0 0 switch@0 1 1 1500 on
PEER MAC PVID VID MTU LINKPROP INTERVNETLINK
vnet1@gitserver 00:14:4f:f8:c0:5f 1 1500
vnet1@racc2 00:14:4f:f8:2e:37 1 1500
vnet1@test1 00:14:4f:f9:61:63 1 1500
vnet1@test2 00:14:4f:f9:a1:68 1 1500
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
cluster-vsw0 00:14:4f:fb:db:cb 1 switch@1 1 1 1500 sc on
PEER MAC PVID VID MTU LINKPROP INTERVNETLINK
vnet2@test1 00:14:4f:f8:87:27 1 1500
vnet2@test2 00:14:4f:f9:3e:3d 1 1500
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
cluster-vsw1 00:14:4f:fa:c1:58 2 switch@2 1 1 1500 sc on
PEER MAC PVID VID MTU LINKPROP INTERVNETLINK
vnet3@test1 00:14:4f:f8:f0:db 1 1500
vnet3@test2 00:14:4f:fb:03:83 1 1500
Any Idea Team, i beleive the cluster interconnect adapters were not successfull.
I need any guidance/any clue, how to correct the private interconnect for clustering in two guest LDOMS.

You dont have to stick to default IP's or subnet . You can change to whatever IP's you need. Whatever subnet mask you need. Even change the private names.
You can do all this during install or even after install.
Read the cluster install doc at docs.sun.com

Cluster interconnect

We have a 3 node RAC cluster, 10.2.0.3 version. sys admin is gearing up to change
1g interconnect to 10g interconnect. just trying to find out, if anything we need to be prepared with from the database point of view/cluster point of view.
Thanks

riyaj wrote:
But, if the protocol is not RDS, then the path becomes udp -> ip -> IPoIB -> HCA. Clearly, there is an additional layer IPoIB. Considering that most latency is at the software layer level, not in the hardware layer, I am not sure, additional layer will improve the latency. Perhaps when one compares 10GigE with 10Gb IB... but that would be comparing new Ethernet technology with older IB technology. QDR (40Gb) is pretty much the standard (for some years now) for IB.
Originally we compared 1GigE with 10Gb IB, as 10GigE was not available. IPoIB was a lot faster on SDR IB than 1GigE.
When 10GigE was released, it was pretty expensive (not sure if this is still the case). A 10Gb Ethernet port was more than 1.5x the cost of 40Gb IB port.
IB also supports a direct socket (or something) for IP applications. As I understand, this simplifies the call interface and allows socket calls to be made with less latency (surpassing that of the socket interface of a standard IP stack on Ethernet). We never looked at this ourselves as our Interconnect using IB was pretty robust and performant using standard IPoIB.
Further, InfiniBand has data center implications. In huge companies, this is a problem: A separate infiniband architecture is needed to support infiniband network, which is not exactly a mundane task. With 10Gb NIC cards, existing network infrastructure can be used as long as the switch supports the 10Gb traffic. True... but I see that more as resistance to new technology and even the network vendor used (do not have to name names, do I?) that will specifically slam IB technology as they do not supply IB kit. A pure profit and territory issue.
All resistance I've ever seen and responded to with IB versus Ethernet have been pretty much unwarranted - to the extend of seing RACs being build using 100Mb Ethernet Interconnect as IB was a "foreign" technology and equated to evil/do not use/complex/unstable/etc.
Another issue to keep in mind is that IB is a fabric layer. SRP scales and performs better than using fibre channel technology and protocols. So IB is not only suited as Interconnect, but also as the storage fabric layer. (Exadata pretty much proved that point).
Some months ago OFED announced that the SRP specs have been made available to Ethernet vendors to implement (as there is nothing equivalent on Ethernet). Unfortunately, a 10Gig Ethernet SRP implementation will still lack in comparison with a QDR IB SRP implementation.
Third point, skill set in the system admin side needs further adjustment to support Infiniband hardware effectively. Important point. But it is not that difficult as sysadmin to acquire the basic set of skills to manage IB from an o/s perspective. Likewise not that difficult for a network engineer to acquire the basic skills for managing the switch and fabric layer.
The one issue that I think is the single biggest negative ito using IB is getting a stable OFED driver stack running in the kernel. Some of the older versions were not that stable. However, later versions have improved considerably and the current version seems pretty robust. Oh yeah - this is specifically using SRP. IPoIB and bonding and so on, have always worked pretty well. RDMA and SRP were not always that stable with the v1.3 drivers and earlier.

2 x Ironport C170s(In cluster) - rejecting connections on port 25

Hi,
Earlier this morning, both our C170's stopped accepting incoming connections on 25...Incoming mail has a public listener (port 25), interface is correct (data 2 / External)...any suggestions/ideas what could have caused both to stop accepting connections at the same time?
Thanks

Hi - Thanks for the reply....this is now resolved...the above steps were performed yesterday, and nothing was running on port 25 on both....listernerconfig revealed why: no listerners configured?
Cause - "Someone" had changed the clusterlevel config...cluster was configured with listerns, but someone had changed both C170's to manually override the cluster with machine level config....checking the logs (gui_log and cli_log), I can see "someone"(We only have 3 staff who login to these devices, but all with "admin" and all from the same nat IP), had edited the listeners 3 days ago, a commit was applied 2 days ago, and another commit was done yesterday morning...so it really doesn't add up..If the listeners were changed 3 days ago, and commit done 2 days ago, why didn't both boxes stop listening on port 25, 2 days ago....Is the logging on these devices not reliable, or doesn't log "everything".....It's now resolved (forced both 170's to use the cluster settings for listeners)...but Im still very interested in how to accurately audit when it was changed, and by who....as it's not something that is "easily/accidentally" done...

Select Listener Port Number from which_table?

I'm writing a SQL script that, among other things, disconnects from Oracle and then reconnects to the same instance as a different user. I'm able to query v$database and v$instance to get most of the information I need (host, service name, etc) for the reconnect part. The only part I'm missing is the listener port number. I could hard code it to 1521, but that isn't very flexible. Currently, I'm prompting the user (which is normally me) for the listener port number in the SQL script, but that just seems a little bit lame. So my question is this: is there a view or table somewhere in the sys schema that I could use to view the listener configuration? I'm mostly working with 10gR2+ databases.

cleavitt wrote:
That is possible, but it needs to be a standard Oracle configuration if the script is to remain generic and portable. The script is actually working fine as-is. I was just trying to go the extra mile and determine the port number automatically. I could also prompt for a TNSNames entry as suggested by others, but I don't always have an entry defined for all of the Oracle instances in my company on every workstation that I work from.
Here is the script for anyone that is interested. It started out as a script that I found online, but the original did not work with 11g case-sensitive passwords and it only worked for local connections on the server.
Description:
Allows a DBA user to impersonate another user (without knowing the user's password).
Similar in function to using the SU command in Unix/Linux.
Note:
This script temporarily changes the impersonated user's password and may cause other
connection attempts by that user to fail during the moment that the temporary password is in effect.
WHENEVER SQLERROR EXIT
SET VERIFY OFF
ACCEPT username CHAR PROMPT 'Enter the username: '
ACCEPT listenerport NUMBER DEFAULT 1521 PROMPT 'Enter the listener port [1521]: '
-- Define substitution variables and column mapping.
COLUMN username NEW_VALUE username
COLUMN password_hash NEW_VALUE password_hash
COLUMN host_name NEW_VALUE hostname
COLUMN instance_name NEW_VALUE servicename
-- Populate substitution variables.
SELECT
name AS username,
-- Get the user's password hash(s) and apply appropriate formatting for case-sensitive password if needed (11g+ passwords).
NVL2(spare4, spare4 || ';' || password /* 11g+ */, password /* pre-11g */) AS password_hash
FROM sys.user$
WHERE name = UPPER('&username');
SELECT host_name, instance_name
FROM v$instance;
-- Set the user's password to a temporary value.
ALTER USER &username IDENTIFIED BY TempPass;
-- Use the temporary password to connect to the database as the user.
CONNECT &username/TempPass@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=&hostname)(PORT=&listenerport))(CONNECT_DATA=(UR=A)(SID=&servicename)));
-- Reset the user's password to the original value using the original password hash(s).
ALTER USER &username IDENTIFIED BY VALUES '&password_hash';
SHOW USER
UNDEFINE username
UNDEFINE password_hash
UNDEFINE hostname
UNDEFINE servicename
UNDEFINE listenerport
WHENEVER SQLERROR CONTINUE
SET VERIFY ONAnd by so doing you just kicked the user's password expiration on down the road, negating the benefit of havng a password expiration.
Also, you locked out the legitimate user of this account, until such time as you reset it back to the original. And in the mean time, if this happens to be an account used by some automated process, that process doesn't know the new "temporary" password and runs a risk of locking the account from too many invalid connection attempts. Try to become SYSMAN or DBSNMP from this, and you will very quickly kill OEM.
This has "bad idea" written all over it. What problem is it supposed to be be solving?

RDP listening port needs to be changed on one client PC - can't connect via Anywhere Access

We have a setup with Server 2012 Essentials and 10 workstations. We have setup Anywhere Access and is working fine. We have one system (Windows 7 Pro) on the network running AADS Server (use to be called XP Unlimited). This allows several users to logon
to that PC remotely at once as well as someone local using it. This PC needs to be changed from the default 3389 port due to the new AADS Server version requiring it. When ever we change the listening port we cannot remote desktop into this PC. It is available
in Remote Web Access Portal but just sits trying to connect. We have allowed the new connection in the Windows Firewall and even turned the firewall off as a test with no luck.
My question is, can we change the default 3389 port connection that the Server redirects you to for one PC on the network? If not how do you change in the Server to look at another local port for RDP once in the portal?
Thanks, Jason

Hi Jboy,
Can you navigate to HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Control, Terminal Server, WinStations and RDP-Tcp. Right click on the PortNumber dword and select Modify. Change the base to Decimal and enter a new port between 1025 and 65535
that is not already in use. Finally click OK.
http://support.microsoft.com/kb/306759
Thanks,
Umesh.S.K

Cluster interconnect using listening port 8059 + 8060

Similar Messages

Maybe you are looking for