Hi Jakob, I mostly map physical interfaces, because I'm primarily concerned with what is plugged into where and whether it's up or not i.e. physical connectivity.
I do occasionally map VLANs, because sometimes I need to know about logical connectivity i.e. why can't device A see device B when all the physical connectivity is there? I agree with you - it's difficult to map them both. Unusually for me, I can't think of any suggestions for the IM crew :) -- Doug Weathers Information Technology Network Administrator Cascade Healthcare Community 2500 NE Neff Road Bend, OR 97701 http://www.scmc.org mailto:[EMAIL PROTECTED] Desk: 541-383-6846 Cell: 541-480-0919 >>> [EMAIL PROTECTED] 5/30/2005 3:13:35 AM >>> Hi All, Just a small query to the masters on the list, as to how you set up your IM maps.. Do you map VLAN's, physical interfaces or both? I'm asking because I'm thinking we have physical interfaces serving 1- n VLANs and currently there is no 'smart' way to 'sub-interface' VLAN's on the physical interfaces in InterMapper. It makes it hard to layout the physical wiring along with the virtual infrastucture. If you ask a Cisco switch via SNMP you can get the VLAN's active on a given physical interface, so would it make sence for InterMapper to automatically sub-interface VLANs active on a given physical interface this way? It would also move the IP networks to possible subinterfaces and spawn IP ranges on a VLAN to any physical interface where it's enabled. So, what's the thoughts from user and Dartware? Jakob Peterh�nsel "Tell me why, don't we try, not to break our hearts and make it so hard for our selfs" P.S.B. 1987 Email: [EMAIL PROTECTED] AIM: Marook Phone: +45 22684961 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
