Date: Tue, 19 Mar 2024 13:51:07 +0000 (UTC) Message-ID: <776986470.2756.1710856267925@skald.opmantek.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2755_314287349.1710856267925" ------=_Part_2755_314287349.1710856267925 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You will need to edit the configuration file /usr/local/opmantek/conf/Ma= ps.nmis and make some simple changes.
To do this you will need to:
opMaps needs to know where Open-AudIT is so it can collect data from it.=
Find the configuration option 'Open-AudIT_SERVER' =3D> 'http= ://localhost/open-audit',
This will need to be the same where your Open-AudIT server is runnin= g, if you are using a machine server.domain.com and to access Open-AudIT yo= u browse to http://server.domain.com/open-audit, this is = what you would enter 'Open-AudIT_SERVER' =3D> 'http://server.domain.= com/open-audit'
As at version 1.0.3 of Open-AudIT we have opMaps integration.
To enable opMaps in Open-AudIT, do the following as an Open-AudIT user w= ith Admin level access.
Click the menu item Admin -> Config and set the correct URL for opMap= s. This will enable a link on the opMaps icon in the header of the Open-Aud= IT pages.
Click the menu item Admin -> Locations -> Add Location. Adding Loc= ations for opMaps is very easy. Enter the location details and click the "G= et Lat / Long" button. You should see the latitude and longitude fields pop= ulated. These values are derived by submitting the location details to the = Google API for Maps. You can also enter the Lat / Long manually. If you wou= ld prefer a different Lat / Long to the actual address details, but don't k= now the actual Lat / Long, you can populate the GeoCode field and click the= "Get Lat / Long" button. This will populate the Lat / Long fields with the= GeoCode address, rather than the entered address details. If both GeoCode = and address details are populated, the "Get Lat/Long" button will use the G= eoCode as preferred.
If you select the "Activate Group" checkbox a Group will be created that= will auto update when any devices are assigned to the given location.
To assign a device to a location you can view the device details and go = to Summary -> Location / Contact on the left side menu. Clicking the blu= e dash (or text if already populated) in the Location Name field will chang= e it to a drop down box. You can then select the location you wish the devi= ce to be allocated to.
To assign multiple devices to a location (say for example a selected sub= net), you can view any Group list as an Open-AudIT Admin user and select th= e devices you need by the checkboxes on the right side of the report. Next = click the "Edit" button in the report table header. You can then edit any m= anual fields, but importantly you can change the location of all selected d= evices. Click the Submit button at the bottom of the form to enact the chan= ge.
Once you have locations created, devices assigned to them and the URL fo= r opMaps populated, you can click the opMaps icon in the header and be sent= to the opMaps web page. The page will show all your locations and when a l= ocation is clicked a summary of the number of each type of device in that l= ocation.
After installing opMaps, you will need to set up the GroupLocations.nmis= so opMaps can display a geographic map of your NMIS status.
To do this you will need to :
This script creates the Map Files based on the NMIS Node files.
Usage: ./configmaps.pl <NODES> <GroupLocations>
cd /usr/local/opm= antek/bin/ ./configmaps.pl /usr/local/nmis8/conf/Nodes.nmis /usr/local/opmantek/conf/G= roupLocations.nmis
After creating GroupLocations.nmis, you may edit the file in the directo= ry /usr/local/opmantek/conf/
vi /usr/local/opm= antek/conf/GroupLocations.nmis
The following text is an example of what a GroupLocations.nmis file migh= t look like
%hash =3D ( 'NMIS8' =3D> { 'Customer' =3D> 'Opmantek', 'Location' =3D> 'Bundall, Queensland', 'Group' =3D> 'NMIS8' } );
In this example 'NMIS8' represents a map entry.
'Customer' =3D> or 'Business' =3D> The name of the business/custom= er which is the name of the map.
'Location' =3D> The location of each of the business/customer (Geodat= a).
'Group' =3D> The NMIS group which relates to that business/customer.<= /p>
By editing these you could change the groups that display on different m= aps.
Lets take an example, like a network with four groups, which represents = a company with operations in Australia and the America's. The groups = we have in NMIS are MexicoCity, NewYorkCity, Brisbane, GoldCoast. We = want to end up with three maps, the "Default" map for all the locations and= a regional map for each region.
%hash =3D ( 'GoldCoast-Global' =3D> { 'Customer' =3D> 'Opmantek-Global', 'Location' =3D> 'Bundall, Queensland', 'Group' =3D> 'GoldCoast' }, 'Brisbane-Global' =3D> { 'Customer' =3D> 'Opmantek-Global', 'Location' =3D> 'Brisbane, Queensland', 'Group' =3D> 'Brisbane' }, 'MexicoCity-Global' =3D> { 'Customer' =3D> 'Opmantek-Global', 'Location' =3D> 'Mexico City, Mexico', 'Group' =3D> 'MexicoCity' }, 'NewYorkCity-Global' =3D> { 'Customer' =3D> 'Opmantek-Global', 'Location' =3D> 'New York City, New York', 'Group' =3D> 'NewYorkCity' }, 'GoldCoast-AU' =3D> { 'Customer' =3D> 'Opmantek-AU', 'Location' =3D> 'Bundall, Queensland', 'Group' =3D> 'GoldCoast' }, 'Brisbane-AU' =3D> { 'Customer' =3D> 'Opmantek-AU', 'Location' =3D> 'Brisbane, Queensland', 'Group' =3D> 'Brisbane' }, 'MexicoCity-NA' =3D> { 'Customer' =3D> 'Opmantek-NA', 'Location' =3D> 'Mexico City, Mexico', 'Group' =3D> 'MexicoCity' }, 'NewYorkCity-NA' =3D> { 'Customer' =3D> 'Opmantek-NA', 'Location' =3D> 'New York City, New York', 'Group' =3D> 'NewYorkCity' }, );
Then you need to tell opMaps which map is the default map to load when i= t starts, by default the default map name is "Default", but you can change = this by editing Maps.nmis
vi /usr/local/opm= antek/conf/Maps.nmis
Find the following line under 'mapview' =3D>
'defaultMap' =3D> 'Default'
Replace the defaultMap with the map you want loaded, in our case "O= pmantek-Global:.
eg: 'defaultMap' =3D> 'Opmantek-Global'
NMIS supports Links, it automatically looks at your network and determin= es the links it can see. It then generates the file /usr/local/nmis8/= conf/Links.nmis, you can add sections to this manually and NMIS will keep t= hem and add more (if it finds any).
You can configure opMaps to use the NMIS links to display links on your = maps. Have a look at the Links.nmis file.
cat ../nmis8/conf= /Links.nmis=20 %hash =3D ( '192.168.88.0' =3D> { 'link' =3D> 'LAN', 'depend' =3D> 'N/A', 'interface1' =3D> 'FastEthernet0/0', 'node2' =3D> 'localhost', 'ifSpeed' =3D> 100000000, 'node1' =3D> 'asgard', 'net' =3D> 'wan', 'interface2' =3D> 'eth0', 'ifIndex2' =3D> 2, 'subnet' =3D> '192.168.88.0', 'role' =3D> 'core', 'ifIndex1' =3D> 1, 'mask' =3D> '255.255.255.0', 'ifType' =3D> 'ethernetCsmacd' } );
We will use this link named "192.168.88.0" as a link in our maps. = We need to modify the MapLinks.nmis file to add links to the maps, the defa= ult MapLinks.nmis looks like the example below.
cat conf/MapLinks= .nmis=20 %hash =3D ( 'Link1' =3D> { 'Group1' =3D> 'WAN1', 'Group2' =3D> 'Sales1', 'Link' =3D> 'BobLan' }, 'Link2' =3D> { 'Group1' =3D> 'xAN1', 'Group2' =3D> 'DataCenter1', 'Link' =3D> 'IPTV' }, 'Link3' =3D> { 'Group1' =3D> 'Cloud', 'Group2' =3D> 'HQ', 'Link' =3D> 'WANEDGE' } );
The Group name is actually Map Entry name, from the example before it wo= uld be GoldCoast-AU for the GoldCoast group in the Map Opmantek-AU.
%hash =3D ( 'Link1' =3D> { 'Group1' =3D> 'GoldCoast-AU', 'Group2' =3D> 'Brisbane-AU', 'Link' =3D> '192.168.88.0' }, 'Link2' =3D> { 'Group1' =3D> 'NewYorkCity-NA', 'Group2' =3D> 'MexicoCity-NA', 'Link' =3D> '192.168.88.0' }, 'Link3' =3D> { 'Group1' =3D> 'GoldCoast-Global', 'Group2' =3D> 'Brisbane-Global', 'Link' =3D> '192.168.88.0' }, 'Link4' =3D> { 'Group1' =3D> 'NewYorkCity-Global', 'Group2' =3D> 'MexicoCity-Global', 'Link' =3D> '192.168.88.0' }, 'Link5' =3D> { 'Group1' =3D> 'NewYorkCity-Global', 'Group2' =3D> 'Brisbane-Global', 'Link' =3D> '192.168.88.0' }, );
This will create the links and use the status and interface utilisation = of the link to color code the map, if the interface goes down, the link wil= l change color.
By default opMaps will display a "TERRAIN" style map, to use an alternat= e map style, open the Maps.nmis file in /usr/local/opmantek/conf/
vi /usr/local/opm= antek/conf/Maps.nmis
Find the following line under 'mapview' =3D>
'mapTypeId' =3D> 'mapType'
Replace the mapType with the map type you want.
eg: 'mapTypeId' =3D> 'google.maps.MapTypeId.TERRAIN'
The Follow map types can be used
ROADMAP
displays the default road map viewSATELLITE
displays Google Earth satellite imagesHYBRID
displays a mixture of normal and satellite views
TERRAIN
displays a physical map based on terrain informati=
on.opMaps will automatically determine the correct map centre and zoom leve= l for your maps, but sometimes, it will calculate the wrong centre for a hu= man, to use an alternate map centre and zoom level you can follow the follo= wing instructions.
To configure the default centres and zoom levels, open the Maps.nm= is file in /usr/local/opmantek/conf/
vi /usr/local/opm= antek/conf/Maps.nmis
Find the following lines under 'mapview' =3D>
'mapCentre' =3D> 'X, Y',
'mapZoom' =3D> 'zoomLevel'
Replace the X,Y and zoomLevel with the value you want.
eg :
'mapCentre' =3D> '10, -180',
'mapZoom' =3D> '3',
To configure the default centres and zoom levels, open the Maps.nm= is file in /usr/local/opmantek/conf/
vi /usr/local/opm= antek/conf/Maps.nmis
Find the following lines under 'group' =3D>,
'mapCentre-groupName' =3D> 'X, Y',
'mapZoom-groupName' =3D> 'zoomLevel',
Replace the groupName with a group name replace the X,Y and zoomLevel wi= th the value you want.
eg:
'mapZoom-Opmantek-US' =3D> '5',
'mapCentre-Opmantek-EU' =3D> '50, 20',