Devices flowing from Smarts Manager into Network Configuration Manager have a network as their destination. This is functional, but sometimes it is necessary to specify not just the network, but the Device server to which the devices should map.
If mapping from Smarts Manager to Network Configuration Manager is configured in the Adapter and if more than one Device server exists, the network created will require one or more Device servers added to the Network Configuration Manager system administration console.
Take the previous example for NetworkA, and further assume there are two Device servers, DS1 and DS2. In this case, you may want to specify the specific Device server to which the device should be managed. The mapping rules handle this case by optionally taking a DS (Device server) filter and DS (Device server) destination.
Examine the following rule, which states that a device named myrouter.* coming from InChargeAM1 should go into NetworkA and be managed by Device server DS1:
InChargeAM1 None NetworkA Name myrouter.* DS1
There are actually two filters in this statement but in this case, the first filter is a no-op filter that passes everything. Note that the first filter must pass for it to reach the second filter. For example, a router named myrouter1 with an IP address of 172.x.x.x, would not cause the following rule to fire:
InChargeAM1 IP 192.168.1.1-192.168.1.255 NetworkA Name myrouter.* DS1
The first filter fails on the check of the IP address range, so the rest of the rule is ignored. With this rule structure, it is possible to route a device into exactly the desired destination by getting very specific with the rule set. The granularity of rules can be as fine or as coarse as needed to achieve a desired result.
In addition to being able to route a device into a specific Device server in Network Configuration Manager, there is a round robin (RR) option. The round robin option is applicable only to Network Configuration Manager Device servers. When specified, the round robin option balances incoming devices onto the set of Device servers for a network. Taking the previous example, say we wanted all devices in the 172 network from IP-AM InChargeAM1 to be distributed evenly across Device servers in NetworkA. That can be specified as follows:
InChargeAM1 IP 172.1.1.1-172.255.255.255 NetworkA RR
If there are 100 devices in the InChargeAM1 domain manager in the 172 network, then 50 of them will be managed by Device server DS1, and 50 will be managed by Device server DS2 in NetworkA. The following table contains additional examples of mapping rules from Smarts Manager to Network Configuration Manager.
| Origin (AM name) |
Filter type |
Filter value |
Destination (network name) |
DS Filter Type |
DS filter value |
DS destination (DS name) |
|---|---|---|---|---|---|---|
| Example 1 |
||||||
| .* |
IP |
192.168.1.1-192.168.1.255 |
Cust1 |
RR |
||
| .* |
IP |
10.1.1.1-11.1.1.1 |
Cust2 |
RR |
||
| Example 2 |
||||||
| InCharge-AM |
None |
Cust1 |
IP |
192.168.1.1-192.168.1.100 |
DeviceServer1 |
|
| InCharge-AM-PM |
None |
Cust1 |
IP |
192.168.1.101-192.168.1.255 |
DeviceServer2 |
|
| Example 3 |
||||||
| In.*-MSP |
Name |
abc.*23 |
Network5 |
IP |
10.1.1.1-10.255.255.255 |
DS1 |
| In.*-MSP |
Name |
bbc.*23 |
Network5 |
IP |
172.1.1.1-172.255.255.255 |
DS2 |
| In.*-AM.* |
None |
Network6 |
RR |
|||
| Incharge-AM |
Device Type |
Switch |
Network7 |
Name |
Dallas.* |
DS3 |
| Incharge-AM |
Device Type |
Router |
Network8 |
RR |
||
As previously noted, the rule structure is syntactically the same, whether the mapping is from Network Configuration Manager to Smarts Manager, or vice-versa. The following table lists the full structure of rules, including all the filter options available.
Note that the Device Type filter is only applicable to devices flowing from Smarts Manager to Network Configuration Manager, and refer to the device types in Smarts Manager. The main purpose of this filter type is to eliminate non-network devices, such as servers, from ending up in the Network Configuration Manager discovery jobs. However, it can also be used to separate device types, such as routers and switches, if desired.
| Origin IP-Am ornetworkname |
Filter type |
Filter value |
Destination IP-AM or networkname |
DS filter type |
DS filter value |
DS Device server name |
|---|---|---|---|---|---|---|
| RegEx Value |
IP |
IP Range |
*No RegEx here |
IP |
IP Range |
*No RegEx here |
| Name |
RegEx |
Name |
RegEx |
|||
| Device Type |
(Smarts Types) Router | Switch | Host, etc. |
Device Type |
Smarts Types |
|||
| None |
N/A |
None |
N/A |
|||
| RR (Round Robin) |
N/A |
