The NIM feature enables NIM to model networks consisting of different
data-link protocol segments.
Networks consisting of different data-link protocol segments use bridges
to connect two segments that have different data link protocols. A network
consisting of a Token-Ring and an Ethernet segment can be connected to form
a single logical network, as shown in the following figure. Figure 1. Heterogeneous
Network. This illustration shows a single IP network in which the master server uses its
token-ring connection and a bridge to communicate with its client on an Ethernet segment.
Because a single NIM network object is used to represent one network, the other_net_type attribute
is reserved for a different type of interface that can exist in a network.
The other_net_type attribute can be added to the definition of a network
object. When present in a network definition, the other_net_type attribute
tells NIM that this logical network uses a bridge to connect the other network
type to the network type that was specified when the object was defined.
When you define a machine object to be connected to
a network object, NIM checks to see if the network has any other_net_type attributes.
If so, NIM requires that the fourth field, which is usually optional, in the if attribute,
be specified. This field specifies the logical name of the client's network
adapter. The following example defines a network object that has a bridge
joining a Token-Ring and an Ethernet segment:
nim -o define -t tok -a net_addr=129.35.129.0 \
-a snm=255.255.240.0 -a other_net_type1=ent b905net
lsnim -l b905net
class = network
type = tok
net_addr = 129.35.128.0
snm = 255.255.240.0
other_net_type1 = ent
Nstate = ready for use
prev_state = information is missing from this object's def>
The other_net_type attribute requires a sequence
number because a network could be composed of all three types of interfaces
linked by bridges.
When you define a client's interface that is physically
connected to an Ethernet segment joined with a Token-Ring network using a
bridge (with master being on the Token-Ring side), you must supply the fourth
field:
nim -o define -t standalone -a if1='find_net mymac 08005ac9430c \
ent' -a cable_type1=bnc mymac
