50 likes | 247 Views
MEGACO MIB. Matt Holdrege – matt@ipverse.com Ilya Akramovich – iakramov@lucent.com. MG. MGC-1. Link ID LinkName LinkState MG-ID MGC-ID Element IP addresses Protocol and transport label (binary or text, etc.). Link. MGC-2. MIB Issues. Structure of MG/MGC mixed?
E N D
MEGACO MIB Matt Holdrege – matt@ipverse.com Ilya Akramovich – iakramov@lucent.com
MG MGC-1 Link ID LinkName LinkState MG-ID MGC-ID Element IP addresses Protocol and transport label (binary or text, etc.) Link MGC-2
MIB Issues • Structure of MG/MGC mixed? • How to define capabilities? • Do we mean associations when we say connnections? • How to represent events? • Deprecate Context • How to define the termination table. Do we have enough already? • How to associate terminations with MG’s. Do we worry about failover from the MIB standpoint? • Remove duplicate objects
More MIB issues • Should we have both messages and commands counters? • Do we care about tracking transport issues (SCTP or UDP or TCP issues?) • Should we have statistics per link/association? If so, we need to groups the stats under each linkname. • Do not allow resetStatistics • What is the point of LinkIdTable and TerminationIdTable? Walking tables can be very costly on large systems
Issues cont. • Long list of traps to be added • ATM SDP stats and objects to be added • Deprecate undefined objects • What is connection type? PTP or MTP? • Continuity test types? IP Continuity tests? Stats? • Package ID’s? More with packages? • VPN Grouping? • Conformance issues