Sofware-Defined Networking

Reply
Highlighted
Contributor
Posts: 20
Registered: ‎01-18-2012

ODL netconf-connector for MLXe

I'm trying to establish a netconf-connector between ODL (Boron SR3) and one of our MLXe's. I've got these yang files (which I've added the date to the name per ODL naming requirements):

 

common-defs@2011-04-20.yang
interface-config@2011-04-20.yang
interface-statedata@2011-04-20.yang
mpls-config@2011-04-20.yang
mpls-statedata@2011-04-20.yang
netiron-config@2011-04-20.yang
netiron-statedata@2011-04-20.yang
version-statedata@2011-04-20.yang
vlan-config@2011-04-20.yang
vlan-statedata@2011-04-20.yang

 

Now I'm trying to get the connector to establish a connection over port 830 with the MLX.

 

I've enabled netconf on the device (netconf server) and have confirmed ODL can actually communcate with the Router via said port.

 

Just wondering if someone has either the xml formatting for Postman for registering establishing a netconf connection or, even better, a Postman collection for the various things I can modify using netconf on the MLX's?

 

Here's my current netconf connector format, which ISN'T working:

 

<module xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:config">
<type xmlnsSmiley Tonguerefix="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">prefix:sal-netconf-connector</type>
<name>mlx-01</name>
<address xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">10.10.10.10</address>
<port xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">830</port>
<username xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">admin</username>
<password xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">password</password>
<default-request-timeout-millis xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">30000</default-request-timeout-millis>
<!--keepalive-delay xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">1000</keepalive-delay-->
<yang-module-capabilities xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">urn:ietfSmiley Tonguearams:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&amp;revision=2010-09-24</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">urn:ietfSmiley Tonguearams:xml:ns:yang:ietf-yang-types?module=ietf-yang-types&amp;revision=2010-09-24</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/common-defs?module=common-defs&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/interface-config?module=interface-config&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/interface-statedata?module=interface-statedata&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/mpls-config?module=mpls-config&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/mpls-statedata?module=mpls-statedata&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/netiron-config?module=netiron-config&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/netiron-statedata?module=netiron-statedata&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/version-statedata?module=version-statedata&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/vlan-config?module=vlan-config&amp;revision=2011-04-20</capability>
<capability xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">http://brocade.com/ns/netconf/config/netiron-config/vlan-statedata?module=vlan-statedata&amp;revision=2011-04-20</capability>
</yang-module-capabilities>
<tcp-only xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">false</tcp-only>
<event-executor xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlnsSmiley Tonguerefix="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:netty">prefix:netty-event-executor</type>
<name>global-event-executor</name>
</event-executor>
<binding-registry xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlnsSmiley Tonguerefix="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:binding">prefix:binding-broker-osgi-registry</type>
<name>binding-osgi-broker</name>
</binding-registry>
<dom-registry xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlnsSmiley Tonguerefix="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:dom">prefix:dom-broker-osgi-registry</type>
<name>dom-broker</name>
</dom-registry>
<client-dispatcher xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlnsSmiley Tonguerefix="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:config:netconf">prefix:netconf-client-dispatcher</type>
<name>global-netconf-dispatcher</name>
</client-dispatcher>
<processing-executor xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlnsSmiley Tonguerefix="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:threadpool">prefix:threadpool</type>
<name>global-netconf-processing-executor</name>
</processing-executor>
<keepalive-executor xmlns="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlnsSmiley Tonguerefix="urnSmiley SurprisedpendaylightSmiley Tonguearams:xml:ns:yang:controller:threadpool">prefix:scheduled-threadpool</type>
<name>global-netconf-ssh-scheduled-executor</name>
</keepalive-executor>
</module>

 

Any help would be GREATLY apprecaited!

 

Thanks,

 

Steve

TAC Mod
Posts: 103
Registered: ‎04-07-2011

Re: ODL netconf-connector for MLXe

Hello @Schmeg,

 

Welcome to the Community!

While we still encourage the Community to assist with your post, I wanted to let you know that I have passed your questions on to our TAC Engagement Team. They will be reaching out to you shortly to gather more information regarding your configuration, so we can get you routed to the correct group.

Once your case is closed, if appropriate, we will post the resolution to this thread to help others within the Community; or, if you'd prefer, please come back and post the resolution yourself.

Please let us know if there is anything else we can do to help faciliate your case resolution.

You can find out more about the TAC Engaged Program by clicking on the link below.

Thank you!

Denise K.
Brocade Community Team
@DeniseK

 

TAC Engaged Program

TAC Engaged Program

TAC Mod
Posts: 103
Registered: ‎04-07-2011

Re: ODL netconf-connector for MLXe

Hello @Schmeg

 

Unfortunately, the case I proactively opened for you has been closed, as you were unreachable via the contact information we had on file for you.

 

If you could update your contact information via your Community profile, we could open a new case with TAC and try to help you resolve your issue.

 

Thank you!

 

Denise

 

 

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.