Conference azur::mcc

3431.0. "token view plus + TCP/IP access module" by MLN08::MALACRIDA () Mon Jul 27 1992 07:54

 (cross-posted in MCC notes file)

 May be I'd better to keep away from this problem, but I'd like instead
 to have some advise from you.

 A customer has in place a token ring LAN wich is blue-based,i.e. cabling,
 cards, hub, PCI software: a mainframe is attached to that TR lan, and,
 via a 3172 channel attached box, tha mainframe get access to an ethernet
 lan too. 
 On the ethernet side, some VAXes and some workstation, wich speak to the 
 mainframe via TCP/IP: finally an 8209 bridge to connect TR and Ethernet.

 The customer is looking for a network management solution (no NETVIEW on 
 the mainframe side ... yet) wich should be able to monitor the ring,
 collect statistical info (global traffic, traffic by station, traffic by
 protocol type and so on), and have fault isolation capability: as the best
 of my little knowledge, the only think I see we can do is:

 - put a TokenView Plus station with an SNMP proxy agent on the ring

 - put a VAX/DECstation on the ethernet site and use the TCP/IP access module
   to get access to the TokenView plus (8209 in the middle shouldn't be a 
   problem)
 
 
 Do you think this configuration be proposable or is far, far better and 
 safe to let IBM solve the problem ???

 Thanks,

 giovanni wich is a lot concerned on what Proteon TokenView can really do 
          with IBM stuff