Sponsored Content
Operating Systems AIX Setting up NIM for different networks Post 303024755 by trifo75 on Tuesday 16th of October 2018 10:06:45 AM
Old 10-16-2018
I have got the solution eventually: there were 2 routing entry in my network (ent) object. routing1 was the default, which were added when the ent object was created. routing2 were added later by me. I had to remove routing1 by issuing

Code:
nim -o change -a routing1='' my-remote-network

Now it is working.

--Trifo

Moderator's Comments:
Mod Comment edit by bakunin: thanks for sharing your solution, but PLEASE use CODE-tags when posting code, commands, terminal output and the like. Thank you.

Last edited by bakunin; 10-16-2018 at 11:31 AM..
This User Gave Thanks to trifo75 For This Post:
 

9 More Discussions You Might Find Interesting

1. AIX

AIX versus Networks

HI folks, Actually i have a network engineer having 2 and 1/2 years of experience in cisco having CCNA certification also. Now my company offering me to move to AIX field. I am new to AIX and do not know more about that field. So i want a suggestion from you peoples, that I have to join AIX or... (5 Replies)
Discussion started by: rawatmohinder
5 Replies

2. AIX

migrate NIM server through NIM installation

I try to migrate a NIM server from one server to another. I try to do a mksysb on NIM server restore the NIM server's mksysb to a client through NIM installation shutdown NIM server start newly installed client as NIM server Does anyone do this before? who can give me some suggestion? (1 Reply)
Discussion started by: yanzhang
1 Replies

3. AIX

Back up a client NIM from nim master

Hello everyone Im trying to backup a nim client from nim master but I got this message COMMAND STATUS Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. 0042-001 nim:... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies

4. What is on Your Mind?

Networks alternative to Internet

I've read about BITNET, CompuServe... CompuServe was probably not a network but an online service. Are (were) there any other networks alternative to Internet? Does anyone have experience with them? Do they still exist, is it possible to access them over Internet? There seems not to be another way... (13 Replies)
Discussion started by: Action
13 Replies

5. Solaris

Multiple networks on same server

If I have 2 interfaces in a server on the same subnet/network does Solaris automatically choose to route packets destined for this network out the first interface. I.e if ce0 and ce1 were on same network ce0 would be chosen as it's first interface? (5 Replies)
Discussion started by: Actuator
5 Replies

6. Solaris

solaris routing between two networks

ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2 inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255 ether 0:14:4f:55:82:9 ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3 inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
3 Replies

7. AIX

NIM : remove nim client info from the client

Hi. I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ? Tks (2 Replies)
Discussion started by: stephnane
2 Replies

8. AIX

Problem in communication nim client with nim master

Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client... (0 Replies)
Discussion started by: omonoiatis9
0 Replies

9. AIX

How to know NIM name from NIM client?

Friend's, I was playing around with NIM in my environment & had a quick question in mind which I didn't/couldn't find answer to, which is -- how to find the name of the NIM server sitting on the NIM client? All leads to the answer would be much appreciated, many thanks! -- Souvik (2 Replies)
Discussion started by: thisissouvik
2 Replies
smcroute(8)						      System Manager's Manual						       smcroute(8)

NAME
SMCRoute - Static Multicast Router (-Interface) - Version 0.95 SYNOPSIS
smcroute < options > < commands > options -d - start daemon -v - verbose output -D - enable debug logging commands - common -h - print help -k - kill daemon commands - multicast routing related -a <InputIntf> <OriginIpAdr> <McGroupAdr> <OutputIntf> [<OutputIntf>] ... - add route -r <InputIntf> <OriginIpAdr> <McGroupAdr> - remove route commands - multicast signaling related -j <InputIntf> <McGroupAdr> - join MC group -l <InputIntf> <McGroupAdr> - leave MC group DESCRIPTION
SMCRoute is a command line tool to manipulate the multicast routes of the Linux kernel. It supports both IPv4 and IPv6 multicast routing. SMCRoute can be used as an alternative to dynamic multicast routers like 'mrouted' in situations where static multicast routes should be maintained and/or no proper IGMP or MLD signaling exists. Generally multicast routes exists in the kernel only as long as smcroute or another multicast routing daemon is running. Only one multicast routing daemon can be active at a time, so it's impossible to run smcroute and e.g. 'mrouted' at the same time. The -d option smcroute is used to start the smcroute daemon. Otherwise, smcroute searches for an already running smcroute daemon and passes the commands to it. The -k option will terminate a running daemon. Multicast routes can be added with the -a command and removed with the -r command. A multicast route is defined by an input interface (<IntputIntf>), a unicast IP origin address (<OriginIpAdr>), a multicast group (<McGroupAdr>) and a list of output interfaces (<OutputIntf> ...). The origin and multicast group addresses must both be IPv4 addresses or IPv6 addresses. If IPv4 addresses are specified then SMCRoute will operate on the IPv4 multicast routes. If IPv6 addresses are specified then SMCRoute will operate on the IPv6 multicast routes. The output interfaces must not be given with the -r as the first three parameter are sufficient to identify the route to remove. The intention of SMCRoute is to help in situation where dynamic multicast routing does not work properly, but dynamic multicast routing is in nearly all cases the preferred solution. SMCRoute supports dynamic multicast routing with the multicast group 'join' -j and 'leave' -l commands. For both commands the input interface on which the multicast sessions should be received (<InputIntf>) and the multicast group address <McGroupAdr> must be given. The <McGroupAdr> may be an IPv4 or IPv6 address. Superuser rights are necessary to start the smcroute daemon or to communicate with the daemon. OPTIONS
-d Starts the smcroute daemon before any of the optional following commands are executed. -v Gives verbose output in some error situations (don't expect too much, check syslog instead). -D Gives additional debug messages in normal use (don't expect too much, see syslog instead). COMMANDS
-a <InputIntf> <OriginIpAdr> <McGroupAdr> <OutputIntf> [<OutputIntf>] ... The command is passed to the daemon that adds the given multicast route to the kernel's routing table. <InputIntf> can be any net- work interface as listed by 'ifconfig' or 'ip link list' (incl. tunnel interfaces), but not the loopback interface. <OriginIpAdr> is the source IP address of the multicast packets that will be routed by this entry. It is a unicast IPv4 or IPv6 address and not a multicast IP address. <McGroupAdr> is the IPv4 or IPv6 address of the multicast group that will be forwarded. <OutputIntf> [<Out- putIntf>] ... is a list of one or more network interfaces to which the multicast packets will be forwarded. The same rules for the selection of output interfaces applies as for the input interface. Warning, by using multiple output interfaces (traffic multiplication), using the input interface also as output interface (direct loop) or constructing some other forms of indirect loop you can flood you network. -r <InputIntf> <OriginIpAdr> <McGroupAdr> The command is passed to the daemon that removes a multicast route previously added with the -a command. The parameters are identi- cal except to the omitted list of <OutputIntf>. -j <InputIntf> <McGroupAdr> The command is passed to the daemon that passes it to the kernel. The kernel then tries to join the multicast group <McGroupAdr> on interface <InputIntf> by starting IGMP (or MLD if <McGroupAdr> is an IPv6 address) signaling on <InputIntf>. This signaling may be received by routers connected to <InputIntf>'s network that support IGMP/MLD multicast signaling and then hopfuly start forwarding of the requested multicast session to <InputIntf>'s network. With this command smcroute allows the integration of nodes that needs static multicast routing into dynamic multicast routing net- works. -l <InputIntf> <McGroupAdr> The command is passed via the daemon to the kernel that initiate a 'leave' for a previously 'joined' multicast group. LIMITS
The current version compiles and runs fine with the Linux kernel version 2.4. The known limits are: Multicast routes: more then 200 Multicast group membership: max. 20 FILES
/proc/net/ip_mr_cache - contains the active IPv4 multicast routes /proc/net/ip_mr_vif - contains the IPv4 'virtual' interfaces used by the active multicast routing daemon /proc/net/ip6_mr_cache - contains the active IPv6 multicast routes /proc/net/ip6_mr_vif - contains the IPv6 'virtual' interfaces used by the active multicast routing daemon /var/run/smcroute - IPC socket created by the smcroute daemon SEE ALSO
mrouted BUGS
The English wording of this man page. AUTHORS
smcroute was originally written by Carsten Schill <carsten@cschill.de>, support for IPv6 was added by Todd Hayton <todd.hayton@gmail.com>, support for FreeBSD was added by Micha Lenk <micha@debian.org>. The source code is now maintained by Todd Hayton <todd.hayton@gmail.com>, Micha Lenk <micha@debian.org> and Julien BLACHE <jblache@debian.org>. The current version is available at: http://alioth.debian.org/projects/smcroute TIPS
A lot of extra information is sent under the daemon facility and the debug priority to the syslog daemon. August 08, 2011 smcroute(8)
All times are GMT -4. The time now is 12:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy