[mrtg] Re: OIDs for Xylan OmniSwitch

[Perkins, Larry]

> -----Original Message-----
> From: Minich, Matthias 
> Sent: Tuesday, April 25, 2000 5:22 AM
> To: MRTG (E-mail)
> Subject: [mrtg] OIDs for Xylan OmniSwitch
> 
> 
> Hello out there,
> it's me (again!!!)
> 
> Does anybody have the OIDs for the vlan-Interfaces of an OmniSwitch? If I
> run cfgmaker, it detects these virtual interfaces, but it doesn't get any
> values.
   I am a late-comer to this list, so please excuse me if I am "out of
synch"
  with your request, but I will answer the question which I "think" that you

  are asking :-)

   We have two OmniSwitches currently monitored with MRTG.  CFGMAKER 
  ran sucessfully against both.  It took a while to discover the precise
relationship 
  between what is established as a config and the "real" use of the various
ports.  
  What I determined was that the config, consisting of lines like 

             "Target[switch.ip.number]: 2005:snmpid at switch.ip.number"

  was pointing at physical ports in the following manner:  cardslot&port
number
  Thus "2005" was card2/port5.  In a similar manner, "8012" would be
card8/port12.

  As for the Virtual Ports, if you look at the output files created by MRTG
in the
  associate work directory, you should see files of the form:
   
      Omni.Swithc.IP.Number.1.html   and    Omni.Swithc.IP.Number.10.html
and
      Omni.Swithc.IP.Number.11.html   and   Omni.Swithc.IP.Number.XX.html
and
      so forth.    

  If you open these with your friendly neighborhood network browser, you
should 
  find port descriptions which include a line like: 

       Interface: vn253 (1) 


  That is the virtual name MRTG "extracts"  for the interface.

  Now log into your OMNI switch and execute the VIA command.  You should get
something
  similar to the following:


                   GROUP Interface Attachments For All Interfaces

GROUP:                                       Service/
Admin
Slot/Intf          Description               Instance        Protocol
Status
========== ================================ ============   ============
=======
    1.1 :* GROUP #1.0 IP router vport       Rtr     /  1   IP
Enabled
    1.10:* Grand Central Routing            Rtr     /  2   IP
Enabled
    1.12:* Academic VLan                    Rtr     /  3   IP
Enabled
    1.XX:* Staff VLan (1)                   Rtr     /  5   IP
Enabled


Note the Slot/Intf column.   The number after the dot (.) should coorespond
to the
"XX" in the "Omni.Swithc.IP.Number.XX.html" files created by MRTG.  Be
careful
if you add or delete any Auto Tracker (or other) VLans, because the
coorespondence
between the "vnXXX" port "name" and the ordinal position of the interface
may
change and cause MRTG to stop paying "attention" to that port.  If you do
any
extensive editing of the CFG file to match "meaningful" names with  the MRTG
output, then there will be even more "clean up" than usual from otherwise
"casual"
configuration changes on your OMNI switch.

I hope that this is helpful.

Later,
--LP--

********************************************  
  LARRY PERKINS, Network Supervisor    
********************************************  
 Snail Mail:  Gonzaga University/CCNSS   
              502 East Boone Avenue      
              Spokane, WA 99258-0001     
                                         
 EMail:       PERKINS at gonzaga.edu        
                                         
 VMail:       (509) 323-5961             
              (509) 328-4220 x5961       

********************************************  
**Note** This signature is used to impart
          contact information only; it does
          NOT indicate Gonzaga University's
          endorsement of opinions expressed 
          herein.

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org