RE: [Hubmib] POWER-ETHERNET-MIB query: Enabled but disabled?

["Romascanu, Dan (Dan)" <dromasca at avaya.com>]

It looks to me that you are dealing with a faulty or non-standard
implementation of the state machine. I would suspect one of the two -
either there is an extra non-standard switch that activates the
detection mechanism on the port (maybe a left-over from a pre-standard
implementation) and which prevents the state machine to work although
pethPsePortAdminEnable=true or the implementation is buggy and while
searching it returns the initial pethPsePortDetectionStatus=disabled
value instead of the searching(2) value that should be returned for any
'state other than those listed above'.  

Dan

 

> -----Original Message-----
> From: Bill Fenner [mailto:fenner at research.att.com] 
> Sent: Monday, October 15, 2007 11:25 PM
> To: hubmib at ietf.org
> Subject: [Hubmib] POWER-ETHERNET-MIB query: Enabled but disabled?
> 
> 
> I'm seeing a device where, on some ports, it reports 
> pethPsePortAdminEnable=true but pethPsePortDetectionStatus=disabled .
> As far as I can tell, this combination of states isn't 
> allowed by the state diagram in figure 33-6 of 802.1af-2003 - 
> it's only permitted to be in the DISABLED state when 
> mr_pse_enable is "disabled".  Assuming that 
> pethPsePortAdminEnable reflects the "disable/enable" states 
> of mr_pse_enable, this means that it's both disabled and not disabled.
> 
> Since this isn't the Hitchhiker's Guide to the Galaxy, any 
> wisdom as to how a management station should interpret this 
> combination of values?  Should I just ignore the value of 
> AdminEnable and pretend that these ports were 
> administratively disabled too?
> 
> Thanks,
>   Bill
> 
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib at ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 


_______________________________________________
Hubmib mailing list
Hubmib at ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib