NIM Less known features : HANIM, nimsh over ssl, DSMThe Network Installation Manager server is one of the most important host in an environment. New machines installations, machines backups, backups restorations,software (filesets), third party products installations, in some cases volume group backups are made from the NIM server. A Sysadmin's Unixersal Translator (ROSETTA STONE) OR What do they call that in this world? Contributions and corrections gratefully accepted. An executive guide to IBM’s strategy and roadmap for the AIX operating system on Power Systems. Download the white paper (740KB). Some best practices have to be respected. I’ll give you in this post a few tricks for NIM. First off all a NIM server has to be in your disaster recovery plan because it the first server needed when you have to re- build a crashed machine : my solution HANIM. It has to be secured (nimsh, and nimsh authentication over ssl), and it has to be flexible and automated (DSM). NIM High Availability : HANIMFinding documentation and information about NIM High Availability is not so easy. I recommend you to check the NIM from a to Z Redbook, it’s one of the only viable source for HANIM. HANIM simple to setup and simple to use, but there are a few things to know and to understand about it : HANIM Overview. It's the beginning of the end for the Patch Tuesday era. Microsoft announced this week at its Ignite event that beginning with the forthcoming Windows 10 operating. Businesses are more comfortable with the cloud and have increased their security spending, but still face a shortage of skilled cybersecurity workers. Products from a very wide variety of vendors may be affected. See Vendor Information for details from vendors who have provided feedback for this advisory. The alternate NIM master is a backup. NIM build from the NIM master. Takeover operations from master to alternate are manuals. Power. HA can be used to run these takeover operations but my advice is not to use it. Takeover can be performed even if the NIM master is down. HANIM does not perform any heartbeat. HANIM only provides a method for replicating NIM database and resources. Resources can be replicated from master to alternate : NIM database AND resources data can be replicated (replicate=yes option). My advice is to run every NIM operation from the master (even if it is possible to run a NIM operation from the alternate). Disks are not shared between the master and the alternate, when a sync operation is done, missing resources are copied over NFS form the master to the alternate, or from the alternate to the master. HANIM does not provides a filesystem takeover. A takeover operation modify all the nimclient’s /etc/niminfo files. NIM master and alternate NIM master must be one the same AIX version . Subsystem PID is 9. For the purpose of this post some resources (spot, lpp. If you check on the NIM from a to Z, page 1. At the time of writing, only rsh/rshd communication is supported for NIM synchronization.”. THIS STATEMENT IS FALSE : I’m using nimsh for the synchronization, and I recommend to use it. We are in 2. 01. 3, do not use rsh anymore. Subsystem PID is 1. Subsystem PID is 5. Here are some points you can verify : On the NIM master, the attribute is. Remember : HANIM only provides a method for replicating NIM database and resources. You can - if you want- synchronize the NIM database only or the NIM database and its resources (data included). Remember : never perform a NIM synchronization from the alternate NIM master. Database synchronization only. The database synchronization is useful, when objects are modified, for example when you are modifying a subnet mask for a network object. It also can be useful when objects “without files” are created ; for instance a machine. On the other hand if your are trying to synchronize the database if an object “with a file” exists such as an lpp. Much much easier, just add replicate=yes attribute to the nim command, it works like a charm . On clients /etc/niminfo file is modified (NIM. Most of the time a NIM synchronization is not enough and you’ll need to synchronize others file in my case, my root . For this need I’m using a little script based over rsync which synchronize my master to my alternate everyday . Alternate NIM master is also a client of the NIM master, its client has to be configured . Received 2. 76. 3 Bytes in 0. Seconds. 0. 51. 3- 0. The nimsh Subsystem was requested to stop. Subsystem PID is 9. This communication is not encrypted. For any communication initiated from the NIM master (push operations), the NIM master communicates with the NIM client using the NIMSH daemon. This allows an encrypted handshake dialog during authentication. IBM Systems Magazine - Avoiding Those 'Segmentation Fault' Failure Messages on AIXHave you ever wondered what causes the mysterious ? Even with more applications being written as native 6. The problem is that memory is handled in 2. MB . 3. 2- bit code uses 1. GB of address space. Segments identify the different types of uses of memory, and then pages provide a means of manipulating smaller pieces of memory within these segments. The segmentation mechanism used in AIX is similar to that plaguing the early days of PCs, except the segments were 6. K in PCs and are 2. MB in AIX. Whilst 2. MB seemed a huge amount when the segmentation mechanism was first designed, it isn't large by today's standards. In particular, it isn't large when one segment is put to multiple uses, with the Private Data segment (2) fitting the stack, heap and some shared objects into that 2. MB, with the stack and the heap moving towards each other. As heap usage and the size of shared objects have both increased, so has the occurrence of problems with segments - particularly in segment 2. This is best shown with a diagram (Figure 1). So, what can be done to get around this problem? When problems first started to be seen with the memory model in AIX, the standard approach was to patch the executable with . Soon, the compiler and linker could create these large model executables directly. However, IBM wanted something considerably more flexible, so introduced the LDR. On each recursion a further 1 MB is allocated from the heap. Let's call this program . When we execute it we will eventually get a core dump we can examine with dbx (See Code Sample 1). To understand what this program is to highlight, we have to understand what is happening in the Private Data segment. The information can be found in the header files provided with every copy of AIX in the bos. If this is installed the seg. Basically, memory in this segment looks like the following diagram (Figure 2). This is a static picture (Figure 3), but what goes on as a program executes highlights where the problems occur. The stack and the heap are increasing towards each other, but the starting point of the heap will vary with size of any shared objects loaded into the segment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2019
Categories |