This just came up in my environment. I just received the list of 
Context's from the Network staff, so I'll be looking to do exactly this 
very soon.

Thanks for posting.

-Rob


On 12/6/2011 3:39 AM, De Munter, Erwin wrote:
>
> Hi.
>
> Maybe there is a better way.  But this is my approach for ACE,  and 
> also for other clustered, virtual environments
>
> I discover both load balancers on their managenet phy address.  Then I 
> create pingables for all virtual addresses, instances, an put them in 
> a nice picture
>
> I import all relevant mibs  via Event configuration (combine mix tools 
> with CLI event files)  to have them in, and can manage them easily in 
>  my /custom/Events eventdisp and alertmap files.
>
> Then SNMP traps send by the virtual addresses are also mapped on 
> pingable models.
>
> The DUPLICATE MAC WITH DIFFERENT IP DETECTED  alarm is disabled in 
> general  at event level  (other option is to add them to your alarm 
> filters)
>
> To verify duplicate mac issues,  I have a policy to get them listed in 
> a global collection.
>
> Regards   Erwin
>
> *From:*GATTY Markus [mailto:[email protected]]
> *Sent:* maandag 5 december 2011 15:57
> *To:* spectrum
> *Subject:* [spectrum] Model a Cisco ACE
>
> Hi list,
>
> does anybody has experience in modelling a CISCO ACE (load balancer) 
> and all of its contexts. The problem is that the Cisco Ace is using 
> some kind of virtualisation. That means an Ace has its own admin 
> context and a context for each load balancing environment. Each of 
> these contexts has its own ip address.
>
> So I'm able to model the admin context and each of the load balancing 
> contexts - but Spectrum has no association between them. So during 
> modelling the different contexts spectrum raises an "DUPLICATE MAC 
> WITH DIFFERENT IP DETECTED" alarm on all contexts on the same box. And 
> if the box will fail, there would be several "DEVICE HAS STOPPED 
> RESPONDING TO POLLS" alarms.
>
> But for modelling the whole environment it is necessary to model all 
> the contexts because each of the contexts has its own interfaces.
>
> The environment has a similar behaviour like a VMWare ESX Server and 
> its virtual hosts!
>
>


---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to