1 of 1 people found this helpful
1. You have already launched multiple copies of output step so this should be fine. May be you can increase the number of copies?
Check the above document for more performance parameters.
2. Check what Velan has commented in the following discussion:
3. Have you heard of the checksum feature introduced in AI? ( Please check documentation and use it)
4. Check armonitor.conf/cfg file and increase the java heap size of AI Process. If you are running spoon locally then also you can do it by increasing the heap size in spoon.bat file.
1. In the lookup if you choose a Non Indexed Remedy field/attribute then performance would be slow.
2. Usually for classes like Computer System it is very easy to find a unique attribute. For e.g. Serial Number. You then include it in your lookup as it is also required for update operation. You have to find a unique attribute in your discovery data for LEP class and specify it over there.
Thanks for the tips, I will check them out.
The main underlying question I had though -- is what other people in the community are using as the Lookup field for the CMDBOUTPUT step in Spoon for MAC addresses.
I would love to use "Name" = MAC Address as the lookup -- but the problem is there are duplicate MAC Addresses , so you can't create 2x
00:00:00:00:00 , even though you need to.
So how do other people get around it?
I guess I could put the "<MAC> on <ComputerSystem>" variable into the Serial # field for LEP? And then do a lookup on that one so at least it's indexed?
Can you use combination of Name and SystemName? BMC_LanEndpoint relationships are weak relationships so when they are created the SystemName field is generated.
I thought about that too -- but I read another thread here where the SystemName appearing is kind of like "magic", and it might not be there at the time of importing just the Mac (Unless I forced the systemname into the field during the Transformation).
So that would work -- if when creating a new LEP CI I forced in "SystemName" as opposed to "letting the CMDB do its thing and populate the SystemName on its' own" ?
Keep in mind this is a straight LEP creation at this point in the Job. The Transformation that does the relationship comes later.
If it is a matter of overcoming the duplicate issue, then yes, if you have the ability to set another attribute like SystemName in your transformation, then I would do that and use the combination to determine uniqueness.
It doesn't seem to let me set the SystemName in the Transformation. I mean the option is there, but the value never seems to get set. And yes, "DNS" has value .
Goes back to what I was saying about "SystemName" being some magical field that gets set at some point via back-end magic.
If you try to set it manually through the User Tool , directly into the form, you get a:
"Setting lead class references values is not allowed. : One or more weak propagated attributes that were changed are reset to original db value. Check log for more details. (ARWARN 120046)"
I'm curious how ADDM does it, because I would mimic that "Transformation". I will look for documentation.
In the meantime it looks like I might be stuck with trying to make serialnumber = hostname/systemname/DNS. This should be sufficient to "trick" it into allowing me to create "duplicate" MAC addresses that are associated with multiple systems.
Will give it a shot.
So that seemed to do the trick for now (putting the hostname in the serial # field of the LanEndPoint)
Now the weird thing I'm seeing is that the relationship is hit or miss for the same device. Example: Server12345 has 5 different MAC addresses.
For some reason -- the job is able to successfully relate server123 with 3 out of 5 MAC addresses. I can't figure out why 2 out of the 5 aren't being established. There are no errors in the transformation logs. The "lookup" I'm doing for both Source ComputerSystem and Destination LANENDPOINT show no duplicates. It's just weird that 3 out of 5 work fine, and 2 out of 5, using the same lookup values, aren't establishing that relationship.
name serialnumber MACAddress systemname InstanceId RelLeadInstanceId RelLeadClassId CC:16:7E:BE:5D:B0 server123.mycompany.com CC167EBE5DB0 server123.mycompany.com OI-4fe4a5679dba47e59bfa4af7f75aaf80 OI-b7c0b8418d434ac2bdd6807b371983e0 BMC_COMPUTERSYSTEM CC:16:7E:BE:5D:B1 server123.mycompany.com CC167EBE5DB1 NULL OI-a48cdf649610427fa51b78ebf44d05a1 NULL NULL CC:16:7E:BE:5D:B2 server123.mycompany.com CC167EBE5DB2 server123.mycompany.com OI-426af6c992164581a3150e6a7159bdbf OI-b7c0b8418d434ac2bdd6807b371983e0 BMC_COMPUTERSYSTEM CC:16:7E:BE:5E:34 server123.mycompany.com CC167EBE5E34 NULL OI-587ac053ed3843dfa49ddf6e37bbf586 NULL NULL CC:16:7E:BE:5E:3F server123.mycompany.com CC167EBE5E3F server123.mycompany.com OI-8bef6a728cd945fcbbb63c7080af5560 OI-b7c0b8418d434ac2bdd6807b371983e0 BMC_COMPUTERSYSTEM
This is what the transformation looks like
This is the output logs. The only thing I can think of is the "No Op" steps and what that has to do with anything , why they are even there, and what they do. Those seem to be out of box steps generated when I created the job via Atrium Integrator.
Step name CopyNr Read Written Input Output Updated Rejected Errors Active Time Speed pr/in/out CMDBLookUp_LANrel_Source 0 3069 3069 3069 0 0 0 0 Finished 7 438.9 - No Op 0 1534 1534 0 0 0 0 0 Finished 7 219.3 - CMDBLookUp_LANrel_Dest 0 1535 1535 1535 0 0 0 0 Finished 7.7 199.6 - No Op 2 0 383 383 0 0 0 0 0 Finished 7.7 49.8 - CMDBOutput_LANrel 0 384 384 384 0 0 0 0 Finished 7.7 49.9 - CMDBOutput_LANrel 1 384 384 384 0 0 0 0 Finished 7.7 49.9 - CMDBOutput_LANrel 2 384 384 384 0 0 0 0 Finished 7.7 49.9 - Add constants 0 3069 3069 0 0 0 0 0 Finished 2.3 1315 - Formula 0 3069 3069 0 0 0 0 0 Finished 2.3 1313 - Error Logging 0 0 0 0 0 0 0 0 Finished 7.7 0 - Table Source 0 0 3069 3069 0 0 0 0 Finished 2.6 1198 - Calculator 0 3069 3069 0 0 0 0 0 Finished 2.3 1311 - Error Logging 2 0 0 0 0 0 0 0 0 Finished 7.7 0 - Error Logging 2 2 0 0 0 0 0 0 0 0 Finished 7 0 -
Other things I'm going to try are "Enable Cache" in the CMDBLookup Steps.
1 of 1 people found this helpful
Your relationship job seems to be ok
Can you output the source and destination instance ID in an excel out to verify the same?
Also since you have selected the option "Do not pass row if lookup fails" you wont be able to figure out if the lookup actually failed or not. Though it is a good thing you can uncheck this option and let the errors come to verify your output.
Good suggestions & ideas, thank you !
I will post back when I have time to play around with it.
I finally got a chance to play around with this the other day.
~I unchecked the "Do not pass row if lookup fails" option
~I set up error file outputs on both the CMDBLOOKUPs and the CMDBOUTPUT steps
The weird thing is -- I didn't see any errors on any of them.
Even though ...
the ComputerSystem CI is created.
the LANENDPOINT CI is created.
... the entry in BMC_CORE_BMC_BASERELATIONSHIP doesn't get created
I have the "# of copies to start" set at 3. My next test is going to be to bump this back down to 1. Perhaps something is getting out of sync because 3 'instances' of the step are trying to run at the same time? 3 copiesis usually the magic # that BMC uses when you create an AI job from the UI.
Anyways, thanks again for the tips !