On Wed, Feb 18, 2009 at 5:58 PM, Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de> wrote:
On Wed, Feb 18, 2009 at 11:26:16AM -0500, Tim Durack wrote:
> Thanks to all who produced scli - it's a rather useful tool.
Nice to hear that your find it useful.
> Is it possible to incorporate "friendly" port-names in some of the output?
> For example:
[...]
> Egress Ports: 0-23,30-46,72-75,96-113,116-143
[...]
> Egress Ports: A1-A24,B7-B23,D1-D4,E1-E18,E21-F24
What is your definition of "friendly" port-name? How do you convert a
port index into a "name"? Is your idea to map the port number to on
ifIndex and then take the ifName if present? Whether this leads to
something useful clearly depends on the device since the content of
ifName is not very consistent across implementations as far as I can
tell.
Yup, ifIndex->ifName is what I'm looking for.
I need to run some automation scripts that enable certain port-level functions based on VLAN membership. Right now I have to harvest configs and parse out the necessary ports. scli would make this a little easier.
> Would also be useful to have Tagged Ports listed in the output. I know
> that's not in the mib, so it would have to be parsed out.
This should be fairly easy to do and I believe it is useful. I just
prototyped the necessary code and now I get:
Vlan Id: 1234
Vlan Name: planetlab
Egress Ports: 7-8,19-21,23
Forbidden Ports:
Untagged Ports: 7-8,19-20
Tagged Ports: 21,23
Status: active
Cool. Did you commit this?
It would also be nice to have a command that returns the information
sorted by port rather vlan; I sometimes wonder what the set of VLANs
is running over a given port...
Agreed. Glad to see scli is alive and kicking! (the mailing list has been quiet.)
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>