[psnmp-commits] CVS: rapports/maintainer_manual datafetch.tex,1.5,1.6

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Update of /cvsroot/psnmp/rapports/maintainer_manual
In directory sc8-pr-cvs1:/tmp/cvs-serv20302

Modified Files:
	datafetch.tex 
Log Message:
toto


Index: datafetch.tex
===================================================================
RCS file: /cvsroot/psnmp/rapports/maintainer_manual/datafetch.tex,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6

--- datafetch.tex	23 May 2003 15:01:56 -0000	1.5
+++ datafetch.tex	23 May 2003 15:50:31 -0000	1.6
@@ -29,11 +29,11 @@
 
 The list of VLANs is available at the following OIDs:
 \begin{itemize} 
-\item {\tt {dot1qVlan}
+\item {\tt dot1qVlan}
 {\tt .1.3.6.1.2.1.17.7.1.4.3.1.1.NNN}
 {\tt iso. org. dot. internet. mgmt. mib-2. dot1dBridge. qBridgeMIB. qBridgeMIBObjects. dot1qVlan. dot1qVlanStaticTable. dot1qVlanStaticEntry. dot1qVlanStaticName. NNN}
 {\tt NNN} is a VLAN's number. The OID value is the VLAN's description.
-\item {\tt {a3VlanGM}
+\item {\tt a3VlanGM}
 {\tt .1.3.6.1.4.1.43.10.1.14.1.1.1.2.NNN}
 {\tt iso. org. dot. internet. private. enterprises. a3Com. generic. genExperimental. genVirtual. a3ComVlanGroup. a3ComVlanGlobalMappingTable. a3ComVlanGlobalMappingEntry. a3ComVlanGlobalMappingIfIndex. NNN}
 {\tt NNN} is a VLAN's number. The OID value is the number of an virtual
@@ -46,11 +46,11 @@
 The table of interfaces and VLANs assocations (i.e. for each port, the list
 of VLANs it is part of) is available at the following OIDs:
 \begin{itemize} 
-\item {\tt {dot1qEgress}
+\item {\tt dot1qEgress}
 {\tt .1.3.6.1.2.1.17.7.1.4.3.1.2.NNN}
 {\tt iso. org. dot. internet. mgmt. mib-2. dot1dBridge. qBridgeMIB. qBridgeMIBObjects. dot1qVlan. dot1qVlanStaticTable. dot1qVlanStaticEntry. dot1qStaticEgressPort. NNN}
 {\tt NNN} is a VLAN's number. The OID value is a bits' mask"; this mask (seen as a boolean list) coding if the VLAN is on a port (1) or not (0); the port 1 is the first bit, port 2 the second, etc.
-\item {\tt {ifStack}
+\item {\tt ifStack}
 {\tt .1.3.6.1.2.1.31.1.2.1.3.MMM.NNN}
 {\tt iso. org. dot. internet. mgmt. mib-2. ifMIB. ifMIBObjects. ifStackTable. ifStackEntry. ifStackStatus. MMM. NNN}
 {\tt MMM} is a ifStackHigher value and {\tt NNN} a ifStackLower value; they
@@ -60,8 +60,7 @@
 roots, and ports belonging to this VLAN are the leaves. The OID value
 is 1(active).
 
-@example
-@group
+
 An example of a VLAN configuration and all
 ifStackHigher/ifStackLower defined to code this
 configuration:
@@ -93,8 +92,7 @@
     11               6
     11               7
     11               8
-@end group
-@end example
+
 
 A stack that contains a VLAN, encapsulation and a port interface, specifies:
 \begin{itemize} 
@@ -116,12 +114,12 @@
 is described in the following OIDs:
 
 \begin{itemize} 
-\item {\tt {dot1qPvid}
+\item {\tt dot1qPvid}
 {\tt .1.3.6.1.2.1.17.7.1.4.5.1.1.NNN}
 {\tt iso. org. dot. internet. mgmt. mib-2. dot1dBridge. qBridgeMIB. qBridgeMIBObjects. dot1qVlan. dot1qPortVlanTable. dot1qPortVlanEntry. dot1qPvid. NNN}
 {\tt NNN} is a interface's number and refers to the ifIndex. The OID value is a VLAN's number find in
 dot1qVlanStaticName and is the VLAN on which the interface tags.
-\item {\tt {a3VlanE}
+\item {\tt a3VlanE}
 {\tt .1.3.6.1.4.1.43.10.1.14.4.1.1.3.NNN}
 {\tt iso. org. dot. internet. private. enterprises. a3Com. generic. genExperimental. genVirtual. a3ComEncapsulationGroup. a3ComVlanEncapsIfTable. a3ComVlanEncapsIfEntry. a3ComVlanEncapsIfTag. NNN}
 {\tt NNN} refers to the
@@ -216,7 +214,7 @@
 In order to fetch data , we use three modules~: 
 One in charge of retrieving back the forwarding tables of each switch, one in charge of retrieving the bandwidth of each port of each switch, and one in charge of keeping up to date a historic of the current flows registered on each port of each switch. All interrogation is performed with SNM protocol. 
 
-\subection{The \textit{maxFlows} module~:}
+\subsection{The \textit{maxFlows} module~:}
 
 This module gets the bandwidth of each port of each switch. The result
 is either put in a file or in the database directly.\\
@@ -564,8 +562,8 @@
 Interrogating NIS servers, creating a file roughly identical to the size of the net we are working on. The function called to do it is~:
 \textit{get\_all\_nis\_info(char *emptyFile)}
 And emptyFile will be filled with two columns, the first with MAC adresses, the second with the host names matching. 
-Description of the function : 
-
+\par
+The fonction {\tt get\_all\_nis\_info} is called by the main progam and uses {\tt yp\_all} wich allows us to specify a fonction applied to each entry of the specified NIS database (here : ethers.byname). The result of this fonction is written in a file in text mode and contains the list of machines on the network and their MAC address. Only machines which respond to {\tt gethostbynames} will be in the list.
 
 
 \item
@@ -581,16 +579,16 @@
 Once the file filled, the second part of the Datafetchmodule can be launched. 
 \textit{ethers()} parse the file 
 Once the file filled, the second part of the Datafetchmodule can be launched. 
-\textit{ethers()} parse the file in question and launch with suited options \textit{search_host_text()} which asks hosts then. \\
+\textit{ethers()} parse the file in question and launch with suited options \textit{search\_host\_text()} which asks hosts then. \\
 
 
 \par
 Retrieving forwarding tables is made by SNMP interrogation. 
-The result can be store either in a databse, or in a file. By the case, we need to connect to the database with the appropriate options the user gave in an extern file, or we immediately launch \textit{search_host_text()} function which will ask in SNMP each switch to retrieve the forwarding tables. \\
+The result can be store either in a databse, or in a file. By the case, we need to connect to the database with the appropriate options the user gave in an extern file, or we immediately launch \textit{search\_host\_text()} function which will ask in SNMP each switch to retrieve the forwarding tables. \\
 
 
 \par
-The output structure of \textit{search_host_text()} in file, and so the final output, must be~:
+The output structure of \textit{search\_host\_text()} in file, and so the final output, must be~:
 \verb+<vlan_number>:<host1>:<port_number>:<host2>+
 in order to suit the topology unit input which treat these datas. \\
 When we store in database, we have to create 2 tables~:
@@ -598,10 +596,10 @@
 \begin{itemize}
 
 \item
-\textit{APPLIANCES_TABLE}, which contains a name and a number identifying each host, plus (comparing to file storing) a type number (switch, router, printer, station ...) and a switch number used by topology unit. 
+\textit{APPLIANCES\_TABLE}, which contains a name and a number identifying each host, plus (comparing to file storing) a type number (switch, router, printer, station ...) and a switch number used by topology unit. 
 
 \item
-\textit{LINKS_DATA_TABLE} contains the same datas as when we work with file in output, what means~:
+\textit{LINKS\_DATA\_TABLE} contains the same datas as when we work with file in output, what means~:
 \verb+(vlan, host1, port1, host2)+
 
 \end{itemize}



