[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

5212.0. "Cannot set characteristics of Circuit AM circuit" by CSOADM::ROTH (Light fuse and retire quickly) Wed Jun 16 1993 22:49

SSB V1.3, VMS V5.5
3100/76, 32Mb

Trying to add some CIRCUIT AM circuits between SNMP boxes via iconic
interface.

For aEndpointName and zEndpointName I am putting in the information
like this:

        SNMP <name> INTERFACE <number>

But, alas, I get an error:

The requested operation cannot be completed

        Entity Existance Info: Entity Existance cannot be determined
        MCC Routine Error:     %MCC-E-INVPARAM, Invalid parameter passed



Since no documentation shows an example of SNMP Circuit AM stuff, I
decided to try it on a couple of registered NODE4's that I have,
following the example in the Circuit AM book that I have. No dice, same
result as above. Are there fields REQUIRED other than the endpoints?

I scanned some of the notes in here that have Circuit AM questions and
they appear mostly to go unanswered... does anyone know anything about
the Circuit AM?

Thanks,

Lee Roth (ready to give up on DECmcc and watch Barney reruns on TV all
day long.)

T.RTitleUserPersonal
Name
DateLines
5212.1FCL method, same problemCSOADM::ROTHLight fuse and retire quicklyThu Jun 17 1993 09:3068
Same crapola when trying via FCL...

MCC> set circuit test3 aEndPointName=(instance=snmp bbsoc1 interface 3)

Circuit LOCAL_NS:.test3
AT 17-JUN-1993 08:06:18 Characteristics

The requested operation cannot be completed
                  Entity Existence Info = Entity Existence Cannot Be Determined,
                      MCC Routine Error = %MCC-E-INVPARAM,  invalid parameter
                                          passed

MCC> set circuit test3 zEndPointName=(instance=snmp bbrho1 interface 3)

Circuit LOCAL_NS:.test3
AT 17-JUN-1993 08:06:19 Characteristics

The requested operation cannot be completed
                  Entity Existence Info = Entity Existence Cannot Be Determined,
                      MCC Routine Error = %MCC-E-INVPARAM,  invalid parameter
                                          passed

MCC> show circuit test3 all attr

Circuit LOCAL_NS:.test3 
AT 17-JUN-1993 08:08:22 All Attributes

                              circuitID = LOCAL_NS:.test3
Circuit LOCAL_NS:.test3  does not have any endpoints 
                                circAES = Circuit LOCAL_NS:.test3 
                          aEndpointName = (
                                 instance = Circuit LOCAL_NS:.not_set_yet ,
                                 objectid = %X303030,
                               objectname = "" )
                    administrativeState = Unknown
                       circuitBandwidth = (
                              azBandwidth = -1,
                              zaBandwidth = -1 )
                            circuitType = (
                                     Mode = Unknown,
                                     type = unspecified )
                         componentNames = (
                                     type = null,
                               components = (  ) )
                  compositeCircuitNames = {  }
                  transmissionDirection = Unknown
                          zEndpointName = (
                                 instance = Circuit LOCAL_NS:.not_set_yet ,
                                 objectid = %X303030,
                               objectname = "" )
                    ComponentDomainName = LOCAL_NS:.soc
                               Location = -- Attribute Not Available
                    Implementation Desc = -- Attribute Not Available
                     Responsible Person = -- Attribute Not Available
                           Phone Number = -- Attribute Not Available
                           MAIL Account = -- Attribute Not Available
                                Remarks = -- Attribute Not Available
                              Text File = -- Attribute Not Available
                           contactNames = -- Attribute Not Available
                          customerNames = -- Attribute Not Available
                          facilityNames = -- Attribute Not Available
                           networkNames = -- Attribute Not Available
                          providerNames = -- Attribute Not Available
                           serviceNames = -- Attribute Not Available
                               typeText = -- Attribute Not Available
                             userLabels = -- Attribute Not Available
                           User1Defined = -- Attribute Not Available
                           User2Defined = -- Attribute Not Available
5212.2QAR 00269CSOADM::ROTHLight fuse and retire quicklyThu Jun 17 1993 17:240
5212.3Good choiceTOOK::MINTZErik MintzThu Jun 17 1993 20:194
Since all of the developers who worked on the circuit AM have left the
group responsible for supporting it, there may be some delay in answering
the QAR.

5212.4Quick throw me a circuit!GLDOA::BREIMAYERFri Jul 02 1993 11:4823
    Lee,
    
    I have been having similiar problems.  I also tested the Circuit AM on
    two NODE4 machines with SVA-0 interfaces.  What I have found is that
    object name must have Circuit.mp:.not_set_yet instead of "" for both
    the A and Z endpoints.  Every field after circuitBandwidth up to
    Zendpoint needs to be blank.  Once I did this then the circuit
    registered the endpoints fine.  I am currently trying to define
    endpoints for proteon P4100's and I know of a customer that registered
    circuits for Wellfleet routers interface 1 successfully.
    
    Some problems I have seen with alarming is that alarms cannot be
    written for the A or Z endpoint counters under the circuit entity.  The
    nmfoperationalState stays enabled if one of the endpoints becomes
    unreachable (sucks) so alarms on status are no good.  In a nutshell, I
    will be forced to write alarms for the endpoints instead of circuits
    which to me defeats the purpose of alarming on WAN circuits.  Customers
    want the circuit to display severity levels in the map, not the
    domains with the endpoints.
    
    I hope this helps some.  Call me if I can be of more help.
    
    Ted
5212.5CSOADM::ROTHLight fuse and retire quicklyTue Jul 06 1993 10:455
Thanks for the tip! Sounds like the iconic interface should substitute
the the text you mentioned when the users leaves the field blank.
Certainly a bug!!

Lee
5212.6VERNA::V_GILBERTTue Jul 06 1993 11:467
Re .5

What you are suggesting is not very generic.  The only time the Iconic Map
enters text where the user leaves a field blank is if an field is required,
it has a default value, and the user leaves it blank.

Verna
5212.7just so long as it worksCSOADM::ROTHLight fuse and retire quicklyWed Jul 07 1993 16:247
Re: .6

Okay, I'll buy that... anything but the current behavior. Just becuase I
leave a field blank I should not get the message that I received as I
noted in the basenote.

Lee