||Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
|(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix|
The object dispatcher (oserv) service listens on TCP port 94. This is a well-known port, assigned to Tivoli by the Internet Assigned Numbers Authority (IANA). All inter-ORB and inter-TMR communications with the object dispatcher use this port as the destination. When a port range is specified in the TMR, the client port that connects to 94 will be created within the port range.
Tivoli has not established any other predefined ports with IANA as registered ports (those that fall in the range 1024 to 49151). The table below is a list of the predefined ports used by the Tivoli Framework.
Tivoli port range
Some object call requests cause the oserv to create TCP client connections (to the remote object dispatcher service) using ephemeral ports (short-lived TCP ports in the high port range, that is those above 1023). This will be true for DM monitors. The object-call induced client connections, the IOM channel server, and IOM ephemeral client connections can (optionally) locally bind to a port from a pre-selected port range.
Whenever a new socket needs to be opened, a call to a framework service is made. This service finds the next available port within the specified range and returns it to the caller. There are some differences in the port selection algorithm between Windows NT and UNIX. It is not important to understand the selection algorithm for implementing Tivoli across firewalls but we include it here as background information. The algorithm differences stem from having to get around some of the non-standard (X/OPEN non-compliance) features of the Winsock API. On UNIX, a port is considered IN USE if it is held in the TCP TIME-WAIT state and binds to these ports fail appropriately. On NT, subsequent binds to ports already in TIME-WAIT bind successfully, but fail during the connect() call.
On UNIX, when a managed node/gateway binds to a port from the range, Tivoli starts at the lowest number in the range and hunts for a port that will bind successfully. If bind() fails, the Tivoli communications moves to the next port in the port range and retries the bind. This bind attempt continues until the bind() finds an available port. It finally gives up the search when the upper bound in the range is reached.
On Windows NT, Tivoli always remembers the last port bound and connected successfully from this range. Subsequent bind attempts start from the next port. If the bind fails, the algorithm proceeds just like in the UNIX case, except that when the upper bound is reached, it wraps around and then continues until the start point is reached. This wraparound is needed because we may start at a port that is already near the upper bound, and by not wrapping, we do not give the bind a fair chance. This practice has been found to be more efficient than starting from the lower bound and heading up.
However, if the NT bind() succeeds but the connect() fails with the EADDRINUSE return code, the algorithm makes five more attempts
to bind and reconnect, each time bumping the port by one. When all five attempts fail to connect, it gives up. When the BDT service
is enabled the object-call induced client connections will always use BDT listening port on the server side. Note: Unfortunately, not
all services and applications completely respect a configured port range. During installation for instance, several ports will be opened
outside of the port range. This is partly to do with the implementation of the rexec service and partly because of some identified problems
within the installation process. In later chapters, we see which components do not respect the port range.
The port range can be set using the command odadmin set_port_range on the TMR server. This command sets the port range for all managed nodes within the TMR. Every framework-based connection will start to create connections that reside in this range. Existing (sustained) connections will not be affected by this change - there is no forced reconnection to use the new range.
odadmin set_port_range "range"
Restricts IOM channel communication ports and Tivoli communication between managed nodes to the specified port range. This option is especially helpful for firewall administrators who need to regulate the availability of ports. The oserv and gateway default ports are not affected by this option.
odadmin set_port_range 2500-3000
odadmin set_port_range 5900-5999,6010-6040,7001
odadmin set_port_range ""
The last example resets the range to no Tivoli-defined range. To enable or disable the single port BDT service use the following command:
odadmin single_port_bdt FALSE|TRUE [od...|clients|all ]
odadmin single_port_bdt TRUE 1
odadmin single_port_bdt TRUE clients
odadmin single_port_bdt FALSE all
To modify the port number used by the single port BDT service you can use the following command:
odadmin set_bdt_port port_number [od...|clients|all ]
odadmin set_bdt_port 12050 all
odadmin set_bdt_port 9401 all
The settings will take effect only after the MDist 2 services are restarted. Recommended way to start and stop the services is by
shutdown/start commands as opposed to odadmin reexec command. To view the current port range configuration, and single port BDT settings execute:
odadmin odinfo od
NOTE: The port range restriction will not necessarily be adhered to by every Tivoli product. The observance of port range restrictions may also vary by release level. Check product release notes for changes at each release. When setting the port range, it needs to be understood that for a Tivoli management gateway the range applies also for any downcalls to its assigned endpoints. Therefore, carefully set the range to avoid a managed node or gateway running out of available ports.The setting of the port range may involve some trial and error until ideal values can be found. If a standard Tivoli operation fails, especially with some form of communication error, such as an IOM error, then the port range should always be checked in relation to the activity that was taking place. The operating system may generate something like an "address in use" error that will usually result in a "general failure" in Tivoli.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to to buy a cup of coffee for authors of this site|
Last modified: March 12, 2019