cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
52
Views
3
Helpful
9
Replies
Highlighted
Cisco Employee

cisco-iso NED info message being treated as Error

We are using NSO 4.1.2 and tried cisco-iso NED versions 4.1.2 and 4.2.0. Facing an issue with the following command

 

 

admin@ncs-vg-dm% commit

 

Aborted: Network Element Driver error ned_prepare_cli for device c1-f56a6b4702c145fe8aa7e92f39eadf54-cloudvpn-CSR-dev1-esc-device: platform hardware throughput level MB 10:

 

Wait for IIC event to get throughput higher than 100K

 

[error][2016-05-27 18:17:34]

 

 

The message - “Wait for IIC event to get throughput higher than 100K” is generated by the CSR1000v device itself and is an informational message. The NED is treating it as an Error and thus performing a rollback. I know we can possibly suppress the warning using -  ned-settings { cisco-iso-config-warning } but is not a good solution for our orchestrator.

 

 

In our VMS solution, devices are registered by our orchestrator and we will need some way to suppress this error globally.

 

 

Is there any quick way that we can filter this warning out in the NED itself ?

Everyone's tags (4)
9 REPLIES 9
Cisco Employee

Re: cisco-iso NED info message being treated as Error

If adding to the dynamic warning list (via the ned-settings mentioned below) is not an option, then we need to request the NED engineer to add it to the static warning list (maintained within the NED code) and release a new NED version. That is, we need to raise a ticket to get the NED code updated.

Cisco Employee

Re: cisco-iso NED info message being treated as Error

 

In my opinipm this is a VNF specific behavior that should be handle by the specific NED rather than building exception handling into the orchestrator which would become bloated with specific adaptations.

 

 

Do you have a reason why this info event should be converter to an error?

Cisco Employee

Re: cisco-iso NED info message being treated as Error

It is handled by the cisco-ios NED, it is a configuration value just for the cisco-ios NED. Have a look in the cisco-ios yang file.

 

What you are asking for is moving that NED specific configuration to be hidden in the NED code. Don’t you think its better to have it configurable than moving it down in to the java code?

Cisco Employee

Re: cisco-iso NED info message being treated as Error

I think we first need understand why this info message being treated as ERROR or warning.

 

 

To our knowledge the problem start sto show at 4..0.4 IOS ned with 4.1.2 NCS

 

Vm2.2 which using 4.0.3 IOS ned with 4.0.3 NCS doesn’t show the problem

Cisco Employee

Re: cisco-iso NED info message being treated as Error

Simple, every message received from the CLI that is not specifically set as warning is considered an ERROR.

 

As we do not know all warning messages for IOS, …you either set the warning yourself or you wait until it is validated by the BU.

Cisco Employee

Re: cisco-iso NED info message being treated as Error

Is this  changed recently? Since we didn’t’ see this behavior  in early release (for this particular scenario)? Can you confirm that?

 

every message received from the CLI that is not specifically set as warning is considered an ERROR. “

 

 

If so I think the assumption is kind of too broad?

Cisco Employee

Re: cisco-iso NED info message being treated as Error

 

Not changed and it is equal in every NED. If we see something we do not understand, we abort the transaction.

The only “recent” change was that now you can configure warning exceptions from the user interface as Bilal mentioned in his first reply.

 

Cisco Employee

Re: cisco-iso NED info message being treated as Error

every message received from the CLI that is not specifically set as warning is considered an ERROR. “

 

If so I think the assumption is kind of too broad?

 

Feel free to give us a list of all return messages from cisco ios and then classify them by severity. This would be immensely helpful and Ill promise you more than one beer (or soft drink of your house if you don't like beer :).

 

We have to make assumptions as cisco ios doesn’t have any kind of consistency when an a return message ment the config was accepted and when not etc.

 

Its not like we can check if it exited with 0 for OK and 1 for not OK.

 

But back to the problem at hand, just add it to the ned-settings { cisco-iso-config-warning } setting. That will get rid of the problem will it not?

Cisco Employee

Re: cisco-iso NED info message being treated as Error

And in this case (NED) its better to fail early, imagine if it would let an error through (just because it didn’t actually say error in the return message), it would be much harder to find why the config didn’t work even though NSO thought the config went through OK. In this case it failed and you actually got to know why and could take appropriate measures.

 

 

 

every message received from the CLI that is not specifically set as warning is considered an ERROR. “

 

If so I think the assumption is kind of too broad?

 

Feel free to give us a list of all return messages from cisco ios and then classify them by severity. This would be immensely helpful and Ill promise you more than one beer (or soft drink of your house if you don't like beer :).

 

We have to make assumptions as cisco ios doesn’t have any kind of consistency when an a return message ment the config was accepted and when not etc.

 

Its not like we can check if it exited with 0 for OK and 1 for not OK.

 

But back to the problem at hand, just add it to the ned-settings { cisco-iso-config-warning } setting. That will get rid of the problem will it not?

Content for Community-Ad
August's Community Spotlight Awards