Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."
Today's Topics:
1. Re: 1.0.2 and Backbone cable documentation
(Schroeder, AJ (GE Healthcare, consultant))
2. Re: 1.0.2 and Backbone cable documentation (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Thu, 6 Dec 2012 20:28:40 +0000
From: "Schroeder, AJ (GE Healthcare, consultant)"
<[email protected]>
Subject: Re: [Netdot-users] 1.0.2 and Backbone cable documentation
To: Carlos Vicente <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hello Carlos,
What I mean by " splicing the strands together to signify" is to take backbone
A-B, strands 27-28 and splicing them with backbone B-C, strands 9-10 and
forming a path for the circuit. I was able to get it to work by manually
selecting the circuit for each individual strand, but I was not able to pick
the strand sequence when I tried to add the circuit initially.
Also, due to us being in a co-lo, we have our circuits delivered to a telco
room that is not ours, and then extended up to us - which is what we are
attempting to document. Is there a way to have backbones assigned to two
separate circuits, one for the "last mile" and one for the long haul?
Thank you,
AJ
-----Original Message-----
From: Carlos Vicente [mailto:[email protected]]
Sent: Thursday, December 06, 2012 1:42 PM
To: Schroeder, AJ (GE Healthcare, consultant)
Cc: [email protected]
Subject: Re: [Netdot-users] 1.0.2 and Backbone cable documentation
Hello AJ,
On 12/6/12 1:19 PM, Schroeder, AJ (GE Healthcare, consultant) wrote:
> Hello list,
>
>
>
> I have netdot 1.0.2 installed and I am trying to document some of our
> fiber connections with it. One of our datacenters is in a co-lo
> facility and we need to document how the fiber is extended to our
> equipment. The way I understand things from the documentation is that
> we need to create a hierarchy something like this to begin to create backbone
> cables:
>
>
>
> Site
>
> ->Floor
>
> -->Room
>
> --->Closet (in our case, racks)
>
>
>
> From there we can create backbone cables from closet (rack) in site A,
> to closet (rack) in site B. After that is created, we can "splice"
> fiber strands together to signify which ports on the patch panels we are on.
This is the part that I'm not sure about. What exactly do you mean by "splicing
the strands together to signify..."?
The way we thought of this was to splice strands in backbone A-B with strands
in backbone B-C.
It is also possible to assign a circuit to strands from backbone A-B alone (no
splicing).
> Also, since we are in a co-lo, the lack of being able to create racks
> and patch panels as "entities" doesn't allow us accurately describe
> the physical layout of the fiber. I can enter in a feature request,
> but I see there are a couple out there dealing with cable plant so I
> don't want to create duplicates.
Yes, this is a known limitation. Our goal for a future release is to change
this structure into something more flexible, like a nested location record
which can be pretty much anything (site, building, floor, room, rack, etc)
cv
------------------------------
Message: 2
Date: Fri, 07 Dec 2012 08:41:12 -0500
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] 1.0.2 and Backbone cable documentation
To: "Schroeder, AJ (GE Healthcare, consultant)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 12/6/12 3:28 PM, Schroeder, AJ (GE Healthcare, consultant) wrote:
> Hello Carlos,
>
> What I mean by " splicing the strands together to signify" is to take
> backbone A-B, strands 27-28 and splicing them with backbone B-C,
> strands 9-10 and forming a path for the circuit. I was able to get it
> to work by manually selecting the circuit for each individual strand,
> but I was not able to pick the strand sequence when I tried to add
> the circuit initially.
That should definitely work. From the circuit page, if you go to Strand
Sequences -> [add] -> Backbones from Site A to Site C
you should see a pair of sequences to select.
> Also, due to us being in a co-lo, we have our circuits delivered to a
> telco room that is not ours, and then extended up to us - which is
> what we are attempting to document. Is there a way to have backbones
> assigned to two separate circuits, one for the "last mile" and one
> for the long haul?
A strand or sequence of strands can only be associated with one circuit.
cv
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 49, Issue 3
*******************************************
