[Entmib] FW: [psg.com #332] AutoReply: More Standby State/Status Issues

["Sharon Chisholm" <[e-mail]>]

The following is the proposed resolution to entstate-332. The issue 
will be considered closed pending the proposed edit being done.

[Note that this text may be affected by the resolution of other issues]

In the description of StandybyStatus add


"             A value 
              'providingSharedService' means the entity
              is providing service that is summed with the service
              provided by other entities."

And add the following enumeration:
"
               providingSharedService (5)
"

In the description to entStateStandby replace

"              If this entity cannot operate in a standby role,
                the value of this object will always be
               'providingService'."

Sharon
-----Original Message-----
From: [e-mail] [mailto:[e-mail]] 
Sent: Friday, February 13, 2004 12:13 PM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Subject: [psg.com #332] AutoReply: More Standby State/Status Issues
<clip>

-------------------------------------------------------------------------
David T. Perkins [[e-mail]]

""Standby status" items should be renamed to "standby state" to be 
consistent with the other naming of other items in the MIB module. 
(Items are "state" when value is an enumerated int, and "status" when 
the value is a bit string.)

There is one important value missing from the enums for standby. It is 
the one that means that the service output is combined with other 
entities. This is commonly found with power supplies where the output 
is "summed". 

Section 2.2 is incorrect. It implies that by reading the value of 
entStandbyStatus for all entities, then entities can be classified as 
redundant (or protected). This is not true. Say that there are two 
entities that are identical and provide a "protected" service. At any 
time, only one is providing service, and the other is standing by 
protecting the other. A "protection switch" causes the roles to change 
(that is the one providing service will switch to standing by, and the 
one standing by will start to providing service).

In general, this MIB module does not provide enough information to 
determine 1) which entities are protected, 2) the relationship between 
the entities that are protected and the entities providing protection. "

David T. Perkins [[e-mail]]

"Here is a replacement for TC StandbyStatus:
  StandbyState  ::=  TEXTUAL-
CONVENTION                                                              
        
    STATUS         current                                          
    DESCRIPTION                                                     
         " Represents the possible values of standby state.
        
           The value 'notAvailable(1)' means that
           no information is available on the standby state
           for the entity.        
           The value 'hotStandby(2)' means the entity is not        
           providing service, and will be immediately able to 
           start providing service for the entity being backed up       
           without the need for initialization activity, and will   
           contain the same information as the entity being       
           backed up.
           The value 'coldStandy(3)' means the entity is not
           providing service, and will be able to start providing
           service for an entity (possibly one from a set) being
           backed up, and will require some initialization
           activity.      
           The value 'providingService(4)' means the        
           entity is providing service.
           The value 'providingSharedService(5)' means the entity
           is providing service that is summed with the service
           provided by other entities."                          
    REFERENCE                                                       
          "ITU Recommendation X.731, 'Information Technology - Open 
              Systems Interconnection - System Management: State    
              Management Function', 1992"                           
          SYNTAX         INTEGER                                    
            {                                                       
            notAvailable(1),                                       
            hotStandby(2),                                          
            coldStandby(3),                                         
            providingService(4),
            providingSharedService
(5)                                    
            }                                                       

And a replacement for entStateStandby:
 entStateStandby OBJECT-TYPE                                    
        SYNTAX StandbyStatus                                    
        MAX-ACCESS read-only                                    
        STATUS current                                          
        DESCRIPTION                                             
             "The standby state for this entity. A value of    
             'notAvailable' means that this entity is unable to 
             determine standby state.                              
                                                                
             Some entities will exhibit only a subset of the    
             remaining standby state values. If this entity
             cannot operate in a standby role, then the value
             with always 
be 'providingService'."                               
   ::= { entStateEntry 6 }                                      
"

_______________________________________________
Entmib mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/entmib