nnmconnedit.ovpl: one interface to many interfaces (716 Views)
Reply
Occasional Advisor
BastiBr
Posts: 20
Registered: ‎09-09-2011
Message 1 of 8 (716 Views)

nnmconnedit.ovpl: one interface to many interfaces

Hello,

I only found one thread to this topic and the answer wasn't really helpful.

Is it possible with nnmconnedit.ovpl to create connections between one interface and many other interfaces?

(one to many)

It looks like one cannot add more than one connection to a single interface...

 

#<connectionedits>
#    <connection>
#        <operation>add</operation>
#        <node>111.111.111.111</node>
#        <interface>Lo2</interface>       
#        <node>555.555.555.555</node>
#        <interface>Lo25</interface>
#    </connection>
#    <connection>
#        <operation>add</operation>
#        <node>222.222.222.222</node>
#        <interface>Lo2</interface>
#        <node>555.555.555.555</node>
#        <interface>Lo25</interface>
#    </connection>
#</connectionedits>

 

Only the last connection will always be added.

Has anyone an answer or an idea?

 

Thanks Bastian

Occasional Advisor
BastiBr
Posts: 20
Registered: ‎09-09-2011
Message 2 of 8 (706 Views)

Re: nnmconnedit.ovpl: one interface to many interfaces

Has really no one the same (nearly the same) problem, an idea or a comment?

 

Honored Contributor
David Campeau
Posts: 1,083
Registered: ‎04-12-2007
Message 3 of 8 (697 Views)

Re: nnmconnedit.ovpl: one interface to many interfaces

Yes, I've noticed the same thing. As I have other irons in the fire, I've been unable to follow up.

HP Expert
Darren Hammond
Posts: 530
Registered: ‎09-20-2000
Message 4 of 8 (679 Views)

Re: nnmconnedit.ovpl: one interface to many interfaces

Hi Bastian,

 

According to the NNMi reference page for nnmconnedit.ovpl,  an endpoint cannot exist for more than one connection element.   The example that you quoted contains multiple connection statements. 

 

--- excerpt from reference page ---

...

When adding a connection, each endpoint will be removed from any existing connection of which it may be
a member, then added to the new connection. If there are more than two endpoints specified in the
connection element, the connection will appear on maps as a shared-media connection symbol.

 

---

 

What kind of physical environment are you modeling?  Is it a WAN cloud?  If two independent network devices are connected to a single port on another device,  then NNMi will want to show this as a "shared media symbol"  (as it does for WANs clouds also),.   To illustrate such a connection,  the syntax of the connection element might be like this for your example:

 

#<connectionedits>
#    <connection>
#        <operation>add</operation>
#        <node>555.555.555.555</node>
#        <interface>Lo25</interface>
#        <node>111.111.111.111</node>
#        <interface>Lo2</interface>      
#        <node>222.222.222.222</node>
#        <interface>Lo2</interface>
#    </connection>
#</connectionedits>

 

I hope that this helps,

 

Best regards,

Darren

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Occasional Advisor
BastiBr
Posts: 20
Registered: ‎09-09-2011
Message 5 of 8 (666 Views)

Re: nnmconnedit.ovpl: one interface to many interfaces

Hello Darren,

 

thanks for your answer and support. It is a WAN cloud. I  tried your syntax and added the connections with nnmconnedit.ovpl. I looks fine that's what I wanted. Thanks a lot. So that's also a solution David can use.

Is it possible for documentation issues to add comments into the *.xml flie I added with nnmconnedit.ovpl?

Do I have to expect problems with such comments in the *.xml file?

 

#<connectionedits>
#    <connection>
#        <operation>add</operation>
#        <!-- site A -->
#        <node>555.555.555.555</node>
#        <interface>Lo25</interface>
#        <!-- site B -->
#        <node>111.111.111.111</node>
#        <interface>Lo2</interface> 
#        <!-- site C -->
#        <node>222.222.222.222</node>
#        <interface>Lo2</interface>
#    </connection>
#</connectionedits>

HP Expert
Darren Hammond
Posts: 530
Registered: ‎09-20-2000
Message 6 of 8 (662 Views)

Re: nnmconnedit.ovpl: one interface to many interfaces

Hello Bastian,

 

I'm pleased that you now have the behaviour that you were looking for.

 

On the subject of the comment fields,   I think those should be fine as they should be ignored by the xml parser. I ran a test on my local box,  and the comments that I added do not appear to interfere with the processing of the connection.

 

Hope this helps,

 

Best regards,

Darren

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Occasional Advisor
BastiBr
Posts: 20
Registered: ‎09-09-2011
Message 7 of 8 (640 Views)

Re: nnmconnedit.ovpl: one interface to many interfaces

Hello Darren,

 

thanks for your testing! So I will make comments into my file.

One question, why get all added connections blue coloured when only one of the added interfaces is not reacheable?

#<connectionedits>
#    <connection>
#        <operation>add</operation>
#        <!-- site A -->
#        <node>555.555.555.555</node>
#        <interface>Lo25</interface>
#        <!-- site B -->
#        <node>111.111.111.111</node>
#        <interface>Lo2</interface> 
#        <!-- site C -->
#        <node>222.222.222.222</node>  

#        <interface>Lo2</interface>    <<<--- for example this one
#    </connection>
#</connectionedits>

 

I thought  or hoped that only the connection to the interface which is not reacheable will get yellow/red...

and all the others will be untouched.

 

Best regards

Bastian

 

HP Expert
Darren Hammond
Posts: 530
Registered: ‎09-20-2000
Message 8 of 8 (635 Views)

Re: nnmconnedit.ovpl: one interface to many interfaces

Hello Bastian,

 

Hmm,  I think that might be normal behaviour for this type of connection.     A shared media connection is modeled as  a single connection with many end-points,  so I believe that the status calculation will follow that of a normal connection.

 

I do seem the same kind of behaviour on my machine.

 

As outlined in the online help:

 

+++++++++++++++++++

 

Network Connections Status Color
ColorMeaningDescription
Unknown Indicates that due to other network problems, the status of one interface cannot be determined at this time.


...

 

+++++++++++++++++++

 

 

The shared media connection would appear to follow this rule - if one interface is "unknown" then the entire connection is unknown.      For this type of connection,  it's quite difficult to know what kind of status should be applied to it,  because the other end of each connection into the shared media cloud is..... a cloud  :).    It would be nice perhaps if the connection was cut in half, with the end nearest the device reflecting the status of the interface on that end of the connection , but I guess you can tell this from the colour of the interface object.

 

Hope this helps,

 

Best regards,

Darren

 

 

 

 

 

 

 

 

 

 

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.