I never thought about a NAT option, that is a viable way around it if there werent a better solution.
we can create a sitemonitor device type with no probes assigned and add them manually per device, but down the road if we edit that device type ot might pull them out real time data display is definetly and issue I havent poked into the oids too much, but im assuming they increment on each additional add on to the site monitor which means for the probes to function we have to define the probe on the index (ie syncstatusoid.1, syncstatusoid.2 ) This could get complicated On Mon, Oct 6, 2014 at 4:53 PM, Bill Prince via Af <[email protected]> wrote: > In cacti, we have one template for the SiteMonitor, and all the > subordinate devices are included in that template. So one IP per > SiteMonitor is perfect. > > bp > > On 10/6/2014 2:45 PM, Forrest Christian (List Account) via Af wrote: > > You can't set multiple IPs. NAT on a router in between your management > and the devices may have a similar effect. > > I'm not sure how people are monitoring in powercode. Are you saying > you can't have multiple probes destined toward the same IP address? How > do they handle graphing say a 24 port switch with only 3-4 ports in use? > > If you have to create a 'probe' for each monitored device which lists > everything to be monitored, I think you're stuck with the idea of a > different type for each arrangement you have. > > -forrest > > On Mon, Oct 6, 2014 at 2:27 PM, That One Guy via Af <[email protected]> wrote: > >> first - packetflux - your products rock, your documentation on the other >> hand..... >> >> we are testing these currently for montoing/managing APC UPS and >> providing cambium sync >> >> We use powercode >> >> First, is there a way to set multiple IP addresses on a sitemonitor >> base unit? If that were possible it would resolve the issue >> >> Second, powercode monitoring is limited in its configuration, we cant >> create our own real time tools and the long term probe graphing requires a >> separate probe for each graph, no categorization or packaging >> >> so if we put in a sitemonitor that has both the APC add on module as >> well ans the sync module, we dont have a clean way to create monitoring >> tools >> >> in this case to have versatility without having a bunch of unused >> probes on each device we would have to create 4 separate device types. >> Stand alone Site Monitor, Site Monitor with sync, site monitor with APC >> monitor, site monitor with both, and then if we have two sync modules that >> is another, etc. >> >> Has anyone found a successful way of monitoring these? I really want >> to use them, I have a pile of them to use, but I need to monitor them in >> powercode >> >> -- >> All parts should go together without forcing. You must remember that the >> parts you are reassembling were disassembled by you. Therefore, if you >> can't get them together again, there must be a reason. By all means, do not >> use a hammer. -- IBM maintenance manual, 1925 >> > > > -- All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use a hammer. -- IBM maintenance manual, 1925
