Does anyone know why the JUNOS interface "bandwidth" command (for setting informational data about the capacity of an interface, e.g. for detection via snmp), as documented here:
http://www.juniper.net/techpubs/software/junos/junos94/swconfig-network-interfaces/interfaces-configuring-the-interface-bandwidth.html Doesn't support aggregated interfaces? It says as much in the last sentence of the above documentation, but I'm kinda surprised that nobody ever asked for this to be fixed. It seems like subints on an aggregate interface would be the single most useful place to configure this. For example, say you have a 40G ae trunking down to a switch, where one subint vlan maps to a 1GE port, another maps to a 2xGE link-agg, another maps to a 10GE, etc, etc. This is the kind of thing that you might want to know about via SNMP, but as it stands today it always reports the capacity of the ae on the subint even if you manually configure a bandwidth value. Basically I'm hoping this is just some silly oversight from long long ago, and someone can be prompted to fix it. :) -- Richard A Steenbergen <r...@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp