Relative to the discussion about adding ifAlias functionality, does it
make sense to create a separate table in the PF database for switch
metadata? This would allow for easier additions to PF for additional
OIDs to be added. It also makes sense to me that a config file directive
should be added to tell PF which SNMP OID to display for the port data.
At first I figured the table would contain the ifIndex, per-switch key
and the ifAlias so that the ifIndex and switch information from other
functions in the product could be used to lookup the ifAlias...but I am
not familiar enough with the code yet, and the switch config entries
appear to be stored as the flat file in the database rather than as a
table with individual entries.
Would it make sense to create a switch entity table the stores switches
(and the rest of the data in switches.conf) as rows in a DB table, each
with a unique key that could then be used to reference a second table of
metadata such as ifAlias, ifLocation, etc. A separate perl script could
then be created to maintain the data (as mentioned on the users
listserv.) With such granular setup of data, the perl script could poll
different switches at different intervals even.
Out of curiosity, why was the whole switches.conf file stuck in the
database versus individual rows for each switch? Regardless of this, is
the setup I mention seem like the a feasible approach? If so, I can
start some of the design and coding. This could open some interesting
functionalities on a management level for PF.
Nicholas
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Packetfence-devel mailing list
Packetfence-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
