CactiEZ v0.7 and Weathermaps 0.97a
Moderators: Developers, Moderators
CactiEZ v0.7 and Weathermaps 0.97a
I have installed CactiEZ v0.7 on VMware Workstation v9.0:
Plugin Management (Cacti Version: 0.8.8a, Plugin Architecture Version: 3.1) and Weathermaps 0.97a
I work with Weathermaps to monitor network connection status.
I draw map and config Weathermaps: if the connection is up the link would be green and if the connection is down the link would be red.
"Poller Interval" and "Cron Interval" are " Every minute"
I also use "Monitor" and "Thold" to get warning email.
If a device shutdown, I get email warning after 2 minutes and Weathermaps change (link on the map) to red after 12 minutes
If the device up after shutdown, I get email warning after 3 minutes and Weathermaps change (link on the map) to green after 3 minutes
So it is OK if device up after shutdown. Its not good when device shutdown, it take too long time to change link status.
Have you got the same problem ?
I see Weathermaps 0.97c now, I try to upgrade Weathermaps by use them command " yum update" in console
but I dont see change int Weathermaps plugin, it seem upgrade OS.
How can I upgrade Weathermaps 0.97c plugin from Weathermaps 0.97a?
thank you
Sorry for my English
Plugin Management (Cacti Version: 0.8.8a, Plugin Architecture Version: 3.1) and Weathermaps 0.97a
I work with Weathermaps to monitor network connection status.
I draw map and config Weathermaps: if the connection is up the link would be green and if the connection is down the link would be red.
"Poller Interval" and "Cron Interval" are " Every minute"
I also use "Monitor" and "Thold" to get warning email.
If a device shutdown, I get email warning after 2 minutes and Weathermaps change (link on the map) to red after 12 minutes
If the device up after shutdown, I get email warning after 3 minutes and Weathermaps change (link on the map) to green after 3 minutes
So it is OK if device up after shutdown. Its not good when device shutdown, it take too long time to change link status.
Have you got the same problem ?
I see Weathermaps 0.97c now, I try to upgrade Weathermaps by use them command " yum update" in console
but I dont see change int Weathermaps plugin, it seem upgrade OS.
How can I upgrade Weathermaps 0.97c plugin from Weathermaps 0.97a?
thank you
Sorry for my English
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Re: CactiEZ v0.7 and Weathermaps 0.97a
How did you configure weathermap to detect links being down? Please paste the config for a link.
To upgrade, unzip the new version over the top of the old version, in cacti/plugins/weathermap (I don't know where that folder is on CactiEZ)
To upgrade, unzip the new version over the top of the old version, in cacti/plugins/weathermap (I don't know where that folder is on CactiEZ)
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Re: CactiEZ v0.7 and Weathermaps 0.97a
@Howie:
The config for a link ( link include two interface, if device up -> interface up -> green and vice verses)
LINK node02318-node02287
INFOURL /graph.php?rra_id=all&local_graph_id=153
OVERLIBGRAPH /graph_image.php?local_graph_id=153&rra_id=0&graph_nolegend=true&graph_height=100&graph_width=300
TARGET /var/www/html/rra/pop11_traffic_in_112.rrd /var/www/html/rra/pop10_traffic_in_158.rrd
NODES node02318 node02287
and the color for link:
KEYPOS DEFAULT 1755 96 Traffic Load
KEYTEXTCOLOR 0 0 0
KEYOUTLINECOLOR 0 0 0
KEYBGCOLOR 255 255 255
BGCOLOR 255 255 255
TITLECOLOR 0 0 0
TIMECOLOR 0 0 0
SCALE DEFAULT 0 0 255 0 0
SCALE DEFAULT 0 100 0 240 0
About upgrade, I upgrade it by using Winscp: delete weathermap folder, copy new one, copy editor.php from old one, change folder permission. When I done, I can see map but I cant edit map
I get error like this:
Warning: require_once(Weathermap.class.php): failed to open stream: No such file or directory
in /var/www/html/plugins/weathermap/editor.php on line 4 Fatal error: require_once(): Failed opening
required 'Weathermap.class.php' (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/html/plugins/weathermap/editor.php on line 4
Thank you
The config for a link ( link include two interface, if device up -> interface up -> green and vice verses)
LINK node02318-node02287
INFOURL /graph.php?rra_id=all&local_graph_id=153
OVERLIBGRAPH /graph_image.php?local_graph_id=153&rra_id=0&graph_nolegend=true&graph_height=100&graph_width=300
TARGET /var/www/html/rra/pop11_traffic_in_112.rrd /var/www/html/rra/pop10_traffic_in_158.rrd
NODES node02318 node02287
and the color for link:
KEYPOS DEFAULT 1755 96 Traffic Load
KEYTEXTCOLOR 0 0 0
KEYOUTLINECOLOR 0 0 0
KEYBGCOLOR 255 255 255
BGCOLOR 255 255 255
TITLECOLOR 0 0 0
TIMECOLOR 0 0 0
SCALE DEFAULT 0 0 255 0 0
SCALE DEFAULT 0 100 0 240 0
About upgrade, I upgrade it by using Winscp: delete weathermap folder, copy new one, copy editor.php from old one, change folder permission. When I done, I can see map but I cant edit map
I get error like this:
Warning: require_once(Weathermap.class.php): failed to open stream: No such file or directory
in /var/www/html/plugins/weathermap/editor.php on line 4 Fatal error: require_once(): Failed opening
required 'Weathermap.class.php' (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/html/plugins/weathermap/editor.php on line 4
Thank you
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Re: CactiEZ v0.7 and Weathermaps 0.97a
why did you copy editor.php from the old install? You can't use part of one version and part of another...
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Re: CactiEZ v0.7 and Weathermaps 0.97a
When I use all new file, I got some errors, I read somewhere to recommand use the old one.Howie wrote:why did you copy editor.php from the old install? You can't use part of one version and part of another...
have you got idea about the time of link ?
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Re: CactiEZ v0.7 and Weathermaps 0.97a
Yes, it sounds like RRDtool averaging.
Cacti doesn't look at the data on the link to decide if a device is down. Weathermap is looking at the traffic on the link. RRDtool works by averaging over time, so it will take at least 2 poller cycle to show exactly zero - the first one will be "half full" so not zero.
Did you start with 1 minute polling, or did you change later? If you changed after the graphs were created, then the graphs would still have 5 minute average values inside them.
Those two things together explain the 'lag'.
If you just want to have a link go red when the device is down in Cacti, use the cactihost: TARGET instead. Then Weathermap and Cacti will behave the same.
Cacti doesn't look at the data on the link to decide if a device is down. Weathermap is looking at the traffic on the link. RRDtool works by averaging over time, so it will take at least 2 poller cycle to show exactly zero - the first one will be "half full" so not zero.
Did you start with 1 minute polling, or did you change later? If you changed after the graphs were created, then the graphs would still have 5 minute average values inside them.
Those two things together explain the 'lag'.
If you just want to have a link go red when the device is down in Cacti, use the cactihost: TARGET instead. Then Weathermap and Cacti will behave the same.
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Re: CactiEZ v0.7 and Weathermaps 0.97a
@Howie
I start with Poller 1 minute and cron 1 minutes
It get lag only when device changes from up to down
I start with Poller 1 minute and cron 1 minutes
It get lag only when device changes from up to down
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Re: CactiEZ v0.7 and Weathermaps 0.97a
You will still get better results using the cactihost target.
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Re: CactiEZ v0.7 and Weathermaps 0.97a
thank for quick reply,
If I change TARGET as cactihost ( Ping - Advance of device), I will lost link status as red or green.
If I change TARGET as cactihost ( Ping - Advance of device), I will lost link status as red or green.
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Re: CactiEZ v0.7 and Weathermaps 0.97a
I thought you wanted to monitor the HOST status?
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Re: CactiEZ v0.7 and Weathermaps 0.97a
If I only want to monitor host status, I will use "monitor" plugin.Howie wrote:I thought you wanted to monitor the HOST status?
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Re: CactiEZ v0.7 and Weathermaps 0.97a
Then you should probably look at monitoring ifOperStatus for the interface, rather than traffic. This is the actual up/down state of the interface on the router.
If you use the snmp target in Weathermap, then this is queried directly from the router. For example:
You will need to get the snmp interface number from 'verbose query' in the Cacti device menu.
Then 1=up, 2=down and 0=unknown/failure
If you use the snmp target in Weathermap, then this is queried directly from the router. For example:
Code: Select all
SET community public
LINK connection1
SET ip 10.1.1.2
SET interface 23
TARGET snmp:{map:community}:{link:this:ip}:.1.3.6.1.2.1.2.2.1.8.{link:this:interface}:-
Then 1=up, 2=down and 0=unknown/failure
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
-
- Cacti User
- Posts: 118
- Joined: Wed Oct 03, 2012 5:51 pm
Re: CactiEZ v0.7 and Weathermaps 0.97a
Hi Howie,Howie wrote:Then you should probably look at monitoring ifOperStatus for the interface, rather than traffic. This is the actual up/down state of the interface on the router.
If you use the snmp target in Weathermap, then this is queried directly from the router. For example:
You will need to get the snmp interface number from 'verbose query' in the Cacti device menu.Code: Select all
SET community public LINK connection1 SET ip 10.1.1.2 SET interface 23 TARGET snmp:{map:community}:{link:this:ip}:.1.3.6.1.2.1.2.2.1.8.{link:this:interface}:-
Then 1=up, 2=down and 0=unknown/failure
I am new to Cacti and Weathermap (experience wise). What you have described here is EXACTLY what I am looking for. However, I don't really understand how to write this into a config.
Below I have copied and pasted a part of a live config on our network (from the links section not the nodes section).
Code: Select all
LINK V100R1-27kswitch
INFOURL /graph.php?rra_id=all&local_graph_id=217
OVERLIBGRAPH /graph_image.php?local_graph_id=217&rra_id=0&graph_nolegend=true&graph_height=100&graph_width=300
TARGET /var/www/html/rra/draytek_v100_r1_traffic_in_219.rrd
NODES V100R1 27kswitch
"V100R1-27kswitch" as is, as this simply represents the name
Then delete all the rest and replace as follows
SET ip "IP of switch"
SET interface "port on switch"
TARGET (I don't understand how to build this line)
Assuming everything here looks correct. Could you explain how to correctly write the TARGET line. What info I should enter here and where I need to get that from.
Thanks in advance for any assistance you can give.
-
- Cacti User
- Posts: 118
- Joined: Wed Oct 03, 2012 5:51 pm
Re: CactiEZ v0.7 and Weathermaps 0.97a
Hi Guys,
I am trying to figure out how to monitor the status of links on our network. I have created a test map with only one link in it.
The idea as suggested above is to monitor the "ifOperStatus" of the ethernet port on the switches.
Currently, the best I can get is that it always says the link is down.
Below is the code I have used for the map and below that is an SNMP walk of the switch in question. The port im interested in on this example is port 4.
Thanks for any help anyone can provide.
I am trying to figure out how to monitor the status of links on our network. I have created a test map with only one link in it.
The idea as suggested above is to monitor the "ifOperStatus" of the ethernet port on the switches.
Currently, the best I can get is that it always says the link is down.
Below is the code I have used for the map and below that is an SNMP walk of the switch in question. The port im interested in on this example is port 4.
Thanks for any help anyone can provide.
Code: Select all
KEYPOS DEFAULT 1755 96 Traffic Load
KEYTEXTCOLOR 0 0 0
KEYOUTLINECOLOR 0 0 0
KEYBGCOLOR 255 255 255
BGCOLOR 255 255 255
TITLECOLOR 0 0 0
TIMECOLOR 0 0 0
SCALE DEFAULT 0 0 255 0 0
SCALE DEFAULT 0 100 0 240 0
SET key_hidezero_DEFAULT 1
# End of global section
# TEMPLATE-only NODEs:
NODE DEFAULT
MAXVALUE 100
# TEMPLATE-only LINKs:
LINK DEFAULT
BANDWIDTH 100M
# regular NODEs:
NODE mcswitch
LABEL MC Switch
ICON images/aaaSwitchSmall.png
POSITION 191 198
NODE trswitch
LABEL TR Switch
ICON images/aaaSwitchSmall.png
POSITION 547 198
# regular LINKs:
LINK mcswitch-trswitch
SET ip 172.16.172.89
SET interface 4
TARGET snmp:{map:community}:{link:this:172.16.172.89}:.1.3.6.1.2.1.2.2.1.8{link:this:interface 4}:-
NODES mcswitch trswitch
Code: Select all
+ Running data query [3].
+ Found type = '3' [SNMP Query].
+ Found data query XML file at '/var/www/html/resource/snmp_queries/interface.xml'
+ XML file parsed ok.
+ Executing SNMP get for num of indexes @ '.1.3.6.1.2.1.2.1.0' Index Count: 10
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.2.1.2.2.1.1' Index Count: 10
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.1' value: '1'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.2' value: '2'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.3' value: '3'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.4' value: '4'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.5' value: '5'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.6' value: '6'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.7' value: '7'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.8' value: '8'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.9' value: '9'
+ Index found at OID: '1.3.6.1.2.1.2.2.1.1.10' value: '10'
+ Located input field 'ifIndex' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.2.2.1.1'
+ Found item [ifIndex='1'] index: 1 [from value]
+ Found item [ifIndex='2'] index: 2 [from value]
+ Found item [ifIndex='3'] index: 3 [from value]
+ Found item [ifIndex='4'] index: 4 [from value]
+ Found item [ifIndex='5'] index: 5 [from value]
+ Found item [ifIndex='6'] index: 6 [from value]
+ Found item [ifIndex='7'] index: 7 [from value]
+ Found item [ifIndex='8'] index: 8 [from value]
+ Found item [ifIndex='9'] index: 9 [from value]
+ Found item [ifIndex='10'] index: 10 [from value]
+ Located input field 'ifOperStatus' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.2.2.1.8'
+ Found item [ifOperStatus='Up'] index: 1 [from value]
+ Found item [ifOperStatus='Up'] index: 2 [from value]
+ Found item [ifOperStatus='Up'] index: 3 [from value]
+ Found item [ifOperStatus='Up'] index: 4 [from value]
+ Found item [ifOperStatus='Up'] index: 5 [from value]
+ Found item [ifOperStatus='Down'] index: 6 [from value]
+ Found item [ifOperStatus='Down'] index: 7 [from value]
+ Found item [ifOperStatus='Up'] index: 8 [from value]
+ Found item [ifOperStatus='Down'] index: 9 [from value]
+ Found item [ifOperStatus='Down'] index: 10 [from value]
+ Located input field 'ifDescr' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.2.2.1.2'
+ Found item [ifDescr='port 1: Gigabit Copper'] index: 1 [from value]
+ Found item [ifDescr='port 2: Gigabit Copper'] index: 2 [from value]
+ Found item [ifDescr='port 3: Gigabit Copper'] index: 3 [from value]
+ Found item [ifDescr='port 4: Gigabit Copper'] index: 4 [from value]
+ Found item [ifDescr='port 5: Gigabit Copper'] index: 5 [from value]
+ Found item [ifDescr='port 6: Gigabit Copper'] index: 6 [from value]
+ Found item [ifDescr='port 7: Gigabit Copper'] index: 7 [from value]
+ Found item [ifDescr='port 8: Gigabit Copper'] index: 8 [from value]
+ Found item [ifDescr='Fiber'] index: 9 [from value]
+ Found item [ifDescr='Fiber'] index: 10 [from value]
+ Located input field 'ifName' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.31.1.1.1.1'
+ Found item [ifName='port 1: Gigabit Copper'] index: 1 [from value]
+ Found item [ifName='port 2: Gigabit Copper'] index: 2 [from value]
+ Found item [ifName='port 3: Gigabit Copper'] index: 3 [from value]
+ Found item [ifName='port 4: Gigabit Copper'] index: 4 [from value]
+ Found item [ifName='port 5: Gigabit Copper'] index: 5 [from value]
+ Found item [ifName='port 6: Gigabit Copper'] index: 6 [from value]
+ Found item [ifName='port 7: Gigabit Copper'] index: 7 [from value]
+ Found item [ifName='port 8: Gigabit Copper'] index: 8 [from value]
+ Found item [ifName='port 9: Gigabit Copper'] index: 9 [from value]
+ Found item [ifName='port 10: Gigabit Copper'] index: 10 [from value]
+ Located input field 'ifAlias' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.31.1.1.1.18'
+ Found item [ifAlias=''] index: 1 [from value]
+ Found item [ifAlias=''] index: 2 [from value]
+ Found item [ifAlias=''] index: 3 [from value]
+ Found item [ifAlias=''] index: 4 [from value]
+ Found item [ifAlias=''] index: 5 [from value]
+ Found item [ifAlias=''] index: 6 [from value]
+ Found item [ifAlias=''] index: 7 [from value]
+ Found item [ifAlias=''] index: 8 [from value]
+ Found item [ifAlias=''] index: 9 [from value]
+ Found item [ifAlias=''] index: 10 [from value]
+ Located input field 'ifType' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.2.2.1.3'
+ Found item [ifType='ethernetCsmacd(6)'] index: 1 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 2 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 3 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 4 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 5 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 6 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 7 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 8 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 9 [from value]
+ Found item [ifType='ethernetCsmacd(6)'] index: 10 [from value]
+ Located input field 'ifSpeed' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.2.2.1.5'
+ Found item [ifSpeed='100000000'] index: 1 [from value]
+ Found item [ifSpeed='100000000'] index: 2 [from value]
+ Found item [ifSpeed='100000000'] index: 3 [from value]
+ Found item [ifSpeed='100000000'] index: 4 [from value]
+ Found item [ifSpeed='100000000'] index: 5 [from value]
+ Found item [ifSpeed='0'] index: 6 [from value]
+ Found item [ifSpeed='0'] index: 7 [from value]
+ Found item [ifSpeed='100000000'] index: 8 [from value]
+ Found item [ifSpeed='0'] index: 9 [from value]
+ Found item [ifSpeed='0'] index: 10 [from value]
+ Located input field 'ifHwAddr' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.2.2.1.6'
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 1 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 2 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 3 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 4 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 5 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 6 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 7 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 8 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 9 [from value]
+ Found item [ifHwAddr='B0:48:7A:B3:27:57'] index: 10 [from value]
+ Located input field 'ifIP' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.4.20.1.2'
+ Found item [ifIP='0.0.0.0'] index: 2 [from regexp oid parse]
+ Found item [ifIP='127.0.0.1'] index: 1 [from regexp oid parse]
+ Found item [ifIP='172.16.172.89'] index: 2 [from regexp oid parse]
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Re: CactiEZ v0.7 and Weathermaps 0.97a
The line in my example was correct The whole point is that it pulls the details from those SET lines, so you don't have to change the TARGET for each port.
You also missed the "SET community...." line which belongs in the top section of the file, before any nodes or links.
You also missed the "SET community...." line which belongs in the top section of the file, before any nodes or links.
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Who is online
Users browsing this forum: No registered users and 3 guests