- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Cluster interconnect and priorisation
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 03:50 AM
тАО12-13-2007 03:50 AM
I've got a cluster with 3 nodes (Alpha, OpenVMS 7.3-2) and I want to know, how I can see on what connection is the cluster interconnect (I want to have it on a special device). And if the cluster IC is on the wrong device, how can I change this or priorise this.
Regards,
Kirsten
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 04:08 AM
тАО12-13-2007 04:08 AM
Re: Cluster interconnect and priorisation
You can use the SCACP program
$MCR SCACP
SHOW vc
SHOW circ
SHOW channel
You can also set priorities on the various interconnects via the
SET CHANNEL/PRIO
Fekko
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 04:10 AM
тАО12-13-2007 04:10 AM
Re: Cluster interconnect and priorisation
you could do following:
HPS1:SYSTEM> mc scacp sho lan
SMHPS1 PEA0 Device Summary 13-DEC-2007 13:06:26.67:
Device Errors + Mgt Buffer MgtMax Line Total Current
Device Type Events Status Priority Size BufSiz Speed Pkts(S+R) LAN Address
------ ---- ------ ------ -------- ---- ------ ----- --------- -----------
LCL 0 Run Online Local Restart 0 1426 0 N/A 399498 00-00-00-00-00-00
EWC 0 Run Online Restart 0 1426 0 1000 2320236 00-1A-4B-AC-B1-40
EWD 0 Run Online Restart 0 1426 0 1000 2237576 00-1A-4B-AC-B1-41
EWA 0 Not in use by SCA 0 0 0 1000 0 00-00-00-00-00-00
EWB 0 Not in use by SCA 0 0 0 1000 0 00-00-00-00-00-00
It will show you interconnects used for Cluster.
In scacp you can set things for devices. in your systartup_vms.com add for instance:
$ IF F$GETDVI("EIC0","EXISTS") THEN MC SCACP SET LAN/PRIO=100 EIC
$ IF F$GETDVI("EID0","EXISTS") THEN MC SCACP SET LAN/PRIO=100 EID
$ IF F$GETDVI("EWA0","EXISTS") THEN MC SCACP STOP LAN EWA
$ IF F$GETDVI("EWB0","EXISTS") THEN MC SCACP STOP LAN EWB
This will disable two devices and give others higher priority.
gr,
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 04:11 AM
тАО12-13-2007 04:11 AM
SolutionMC SCACP is your friend ;-)
MC SCACP SHOW CHANNEL (use SET TERM/WID=132) will show you the channels, i.e. all cluster communication pathes formed between all visible LAN interfaces of all nodes within the cluster. There can be multiple channels between any 2 nodes in the cluster, it depends on the HW and network configuration.
Between each pair of nodes in the cluster then exists the VC (Virtual Circuit), which carries the SCS traffic. This virtual circuit may be multiplexed over all available channels between that pair of nodes.
You can use various SCACP> SET {CHANNEL|CIRCUIT|PORT|LAN_DEVICE} /PRIO=n commands to manually try to distribute the load over the various communication pathes.
You could also stop SCS communication over individual LAN interfaces (MC SCACP STOP LAN EWA)
If you want to reduce SCS traffic on a specific LAN segment, you could use MC SCACP SET LAN_DEVICE EWA/PRIO=-10
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 04:26 AM
тАО12-13-2007 04:26 AM
Re: Cluster interconnect and priorisation
Robert wrote:
>>>$
IF F$GETDVI("EWA0","EXISTS") THEN MC SCACP STOP LAN EWA
$ IF F$GETDVI("EWB0","EXISTS") THEN MC SCACP STOP LAN EWB
This will disable two devices and give others higher priority.
<<<
While this is true, you should VERY SERIOUSLY think whether this is what you want/need!
See Volker's answer about LOWERING priority. SHOULD anything unwelcome happen then, then the LOW priority interconnect will keep your cluster alive, but DISABLED does what it says: they will simply NOT function. And if there is NO (enabled) interconnect, there is NO cluster... It will hang, then crash.
Usually a low-performing cluster is WAY preferable, and upon return of the desired interconnect, full function is IMMEDIATELY, AUTOMATICALLY restored.
hth
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 09:58 AM
тАО12-13-2007 09:58 AM
Re: Cluster interconnect and priorisation
If so, IMO, it is reasonable to disable SCA on certain network interfaces, such as the interface you might use for TCP/IP external internet traffic for security reasons.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 01:16 PM
тАО12-13-2007 01:16 PM
Re: Cluster interconnect and priorisation
>>> if the cluster IC is on the wrong device, how can I change this or priorise this.
There should be no "wrong device" as a cluster interconnect. To use multiple network interfaces as cluster interconnect, simply connect the cables and make sure speed/duplex are properly configured. If you have multiple interfaces, ideally you'd want to use redundant switching for a 3 node cluster, otherwise the loss of a switch can cause the cluster to fail.
The SCACP utility will allow you to set priorities and monitor traffic. Assuming two networks, if you configure one for users and the second for cluster traffic, if you ever have a failure of the cluster network segment, your cluster fails. If you accept the default behavior however, your cluster would continue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2007 04:02 AM
тАО12-15-2007 04:02 AM
Re: Cluster interconnect and priorisation
Thank you very much.
Kirsten