z.archive.Transportpce-dev@lists.opendaylight.org | HoneyNode tests in TransportPCE

Home Messages Hashtags Subgroups

This group is locked. No changes can be made to the group while it is locked.

Date Date 1 - 3 of 3

HoneyNode tests in TransportPCE

javier.errea_moreno@... #130 Hi everyone, My name is Javier and I am new in the community and into transportPCE project. I hope you can help me solve the issues I face :) I am trying to run the test scenario End2End. As written in the script, I first create 2 instances of ROADMs and make sure the corresponding link of the type "ROADM-TO-ROADM" is created. Then, I add to the topology 2 instances of Xponders and configure the links with the corresponding ROADM instance. Now, when I try to create the service from 1 Xponder to the other, I get the following error from the controller. I am following the tutorial in the developer guide of transportPCE and I am getting the content from the samples there. I have verified that the content of the message has all the required fields with respect to the YANG model. I am using model versions 1.2.1. Thanks in advance!!! Javier "errors": { "error": [ { "error-type": "protocol", "error-tag": "malformed-message", "error-message": "Error parsing input: String 'org.opendaylight.yangtools.yang.model.util.type.ResolvedLengthConstraint@1882f7dc' does not match allowed length constraint %s", "error-info": "String 'org.opendaylight.yangtools.yang.model.util.type.ResolvedLengthConstraint@1882f7dc' does not match allowed length constraint %s" } ] } Here is the content of the request to create a service. I have modified the fields that correspond to my "node-id" and "clli". {"input": { "sdnc-request-header": { "request-id": "e3028bae-a90f-4ddd-a83f-cf224eba0e58", "rpc-action": "service-create", "request-system-id": "appname", "notification-url": "http://localhost:8585/NotificationServer/notify" }, "service-name": "service1", "common-id": "ASATT1234567", "connection-type": "service", "service-a-end": { "service-rate": "100", "node-id": "XPDRA", "service-format": "Ethernet", "clli": "NodeA", "tx-direction": { "port": { "port-device-name": "ROUTER_SNJSCAMCJP8_000000.00_00", "port-type": "router", "port-name": "Gigabit Ethernet_Tx.ge-5/0/0.0", "port-rack": "000000.00", "port-shelf": "00" }, "lgx": { "lgx-device-name": "LGX Panel_SNJSCAMCJP8_000000.00_00", "lgx-port-name": "LGX Back.3", "lgx-port-rack": "000000.00", "lgx-port-shelf": "00" } }, "rx-direction": { "port": { "port-device-name": "ROUTER_SNJSCAMCJP8_000000.00_00", "port-type": "router", "port-name": "Gigabit Ethernet_Rx.ge-5/0/0.0", "port-rack": "000000.00", "port-shelf": "00" }, "lgx": { "lgx-device-name": "LGX Panel_SNJSCAMCJP8_000000.00_00", "lgx-port-name": "LGX Back.4", "lgx-port-rack": "000000.00", "lgx-port-shelf": "00" } }, "optic-type": "gray" }, "service-z-end": { "service-rate": "100", "node-id": "XPDRC", "service-format": "Ethernet", "clli": "NodeC", "tx-direction": { "port": { "port-device-name": "ROUTER_SNJSCAMCJT4_000000.00_00", "port-type": "router", "port-name": "Gigabit Ethernet_Tx.ge-1/0/0.0", "port-rack": "000000.00", "port-shelf": "00" }, "lgx": { "lgx-device-name": "LGX Panel_SNJSCAMCJT4_000000.00_00", "lgx-port-name": "LGX Back.29", "lgx-port-rack": "000000.00", "lgx-port-shelf": "00" } }, "rx-direction": { "port": { "port-device-name": "ROUTER_SNJSCAMCJT4_000000.00_00", "port-type": "router", "port-name": "Gigabit Ethernet_Rx.ge-1/0/0.0", "port-rack": "000000.00", "port-shelf": "00" }, "lgx": { "lgx-device-name": "LGX Panel_SNJSCAMCJT4_000000.00_00", "lgx-port-name": "LGX Back.30", "lgx-port-rack": "000000.00", "lgx-port-shelf": "00" } }, "optic-type": "gray" }, "due-date": "2016-11-28T00:00:01Z", "operator-contact": "pw1234" } }

Gilles Thouenon #131 Hi Javier, Happy to know you are testing TransportPCE with Honeynode. I think your issue is simply due to the fact that the “node-id” value you are using in your rpc is “XPDRA” and does not match the node-id type required by the yang model. typedef node-id-type { type string { length "7..63"; pattern '([a-zA-Z][a-zA-Z0-9-]{5,61}[a-zA-Z0-9])' { error-message "A node-id must be 7 to 63 characters in length. A node-id can contain letters, numbers, and hyphens. The first character must be a letter. The last character must be a letter or number."; } } description "Globally unique identifier for a device."; } In our config, we use “XPDRA01” to match the model. Be sure also that the node-id value you use in the rpc to connect TransportPCE to the node is the same as the node-id inside the device configuration (org-openroadm-device/info/node-id). Hope it will help you. Gilles Thouenon De : Transportpce-dev@... [mailto:Transportpce-dev@...] De la part de javier.errea_moreno@... Envoyé : mardi 10 mars 2020 12:24 À : Transportpce-dev@... Objet : [Transportpce-dev] HoneyNode tests in TransportPCE Hi everyone, My name is Javier and I am new in the community and into transportPCE project. I hope you can help me solve the issues I face :) I am trying to run the test scenario End2End. As written in the script, I first create 2 instances of ROADMs and make sure the corresponding link of the type "ROADM-TO-ROADM" is created. Then, I add to the topology 2 instances of Xponders and configure the links with the corresponding ROADM instance. Now, when I try to create the service from 1 Xponder to the other, I get the following error from the controller. I am following the tutorial in the developer guide of transportPCE and I am getting the content from the samples there. I have verified that the content of the message has all the required fields with respect to the YANG model. I am using model versions 1.2.1. Thanks in advance!!! Javier "errors": { "error": [ { "error-type": "protocol", "error-tag": "malformed-message", "error-message": "Error parsing input: String 'org.opendaylight.yangtools.yang.model.util.type.ResolvedLengthConstraint@1882f7dc' does not match allowed length constraint %s", "error-info": "String 'org.opendaylight.yangtools.yang.model.util.type.ResolvedLengthConstraint@1882f7dc' does not match allowed length constraint %s" } ] } Here is the content of the request to create a service. I have modified the fields that correspond to my "node-id" and "clli". {"input": { "sdnc-request-header": { "request-id": "e3028bae-a90f-4ddd-a83f-cf224eba0e58", "rpc-action": "service-create", "request-system-id": "appname", "notification-url": "http://localhost:8585/NotificationServer/notify" }, "service-name": "service1", "common-id": "ASATT1234567", "connection-type": "service", "service-a-end": { "service-rate": "100", "node-id": "XPDRA", "service-format": "Ethernet", "clli": "NodeA", "tx-direction": { "port": { "port-device-name": "ROUTER_SNJSCAMCJP8_000000.00_00", "port-type": "router", "port-name": "Gigabit Ethernet_Tx.ge-5/0/0.0", "port-rack": "000000.00", "port-shelf": "00" }, "lgx": { "lgx-device-name": "LGX Panel_SNJSCAMCJP8_000000.00_00", "lgx-port-name": "LGX Back.3", "lgx-port-rack": "000000.00", "lgx-port-shelf": "00" } }, "rx-direction": { "port": { "port-device-name": "ROUTER_SNJSCAMCJP8_000000.00_00", "port-type": "router", "port-name": "Gigabit Ethernet_Rx.ge-5/0/0.0", "port-rack": "000000.00", "port-shelf": "00" }, "lgx": { "lgx-device-name": "LGX Panel_SNJSCAMCJP8_000000.00_00", "lgx-port-name": "LGX Back.4", "lgx-port-rack": "000000.00", "lgx-port-shelf": "00" } }, "optic-type": "gray" }, "service-z-end": { "service-rate": "100", "node-id": "XPDRC", "service-format": "Ethernet", "clli": "NodeC", "tx-direction": { "port": { "port-device-name": "ROUTER_SNJSCAMCJT4_000000.00_00", "port-type": "router", "port-name": "Gigabit Ethernet_Tx.ge-1/0/0.0", "port-rack": "000000.00", "port-shelf": "00" }, "lgx": { "lgx-device-name": "LGX Panel_SNJSCAMCJT4_000000.00_00", "lgx-port-name": "LGX Back.29", "lgx-port-rack": "000000.00", "lgx-port-shelf": "00" } }, "rx-direction": { "port": { "port-device-name": "ROUTER_SNJSCAMCJT4_000000.00_00", "port-type": "router", "port-name": "Gigabit Ethernet_Rx.ge-1/0/0.0", "port-rack": "000000.00", "port-shelf": "00" }, "lgx": { "lgx-device-name": "LGX Panel_SNJSCAMCJT4_000000.00_00", "lgx-port-name": "LGX Back.30", "lgx-port-rack": "000000.00", "lgx-port-shelf": "00" } }, "optic-type": "gray" }, "due-date": "2016-11-28T00:00:01Z", "operator-contact": "pw1234" } } _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

javier.errea_moreno@... #132 Thanks a lot!! Solved the issue. My bad....

1 - 3 of 3

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms