[c-nsp] Circuit provisioning between an ONS 15454 and anon-Cisco NE?

[Michael K. Smith - Adhost]

Hello Aaron:

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Aaron Daubman
> Sent: Friday, April 13, 2007 8:38 AM
> To: Phil Bedard
> Cc: cisco-nsp
> Subject: Re: [c-nsp] Circuit provisioning between an ONS 15454 and
> anon-Cisco NE?
> 
> Phil,
> 
> > If you do a search on "Ethernet Manual Cross-connects" you'll find
> > some information on manually connecting an Ethernet port to an
> outgoing
> > STS circuit.
> 
> Thanks for the tip.  Searching as you described seems to return
> results which all sum up to the following:
> 
> """
> ONS 15454s require end-to-end CTC visibility between nodes for normal
> provisioning of Ethernet circuits. When other vendors' equipment sits
> between ONS 15454s, OSI/TARP-based equipment does not allow tunneling
> of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous
> DCC, the Ethernet circuit must be manually cross connected to an STS
> channel using the non-ONS network. Manual cross-connects allows an
> Ethernet circuit to run from ONS node to ONS node while utilizing the
> non-ONS network. (See  Figure 13-13.)
> 
> Note In this chapter, "cross-connect" and "circuit" have the following
> meanings: Cross-connect refers to the connections that occur within a
> single ONS 15454 to allow a circuit to enter and exit an ONS 15454.
> Circuit refers to the series of connections from a traffic source
> (where traffic enters the ONS 15454 network) to the drop or
> destination (where traffic exits an ONS 15454 network).
> """
> 
> This describes what I want to do (basically, even though there will
> not be an ONS on the other side of the circuit).  Unfortunately,
> however, I could not find any documentation on performing the manual
> cross-connect.
> 
> Have you found this documented anywhere (we're using XC10Gs)?
> 
I think this just means you cannot auto-provision the circuit from end
to end.  So, you have to build the circuit from the ingress port to the
egress optical port and sts on the same chassis.  Then, you pick it up
the same way on the other side.

So, in this environment, you would have:

- Ingress Ethernet port
- STS-3 from ingress Ethernet port to egress OC-192 on STS x
- Non-cisco equipment has circuit built on ingress OC-192 on STS x
- Circuit is picked up on other side on ingress OC-192 on STS x
- STS-3 from ingress OC-192 is build to egress Ethernet port

I hope that helps.

Mike