text:
Perl Policy
- 1 Introduction
- 2 Perl Versions
- 3 Module Paths
- 4 Documents
- 5 Site
- 6 Vendor
- 7 Core
- 8 Perl6
This document is currently a proposal for standards regarding to the perl package, related perl packages, creating perl module packages (both in binary form and in the form of PKGBUILDs). Portions are derived from the Debian Perl Policy document, and from various portions of the perl man pages.
Current Caveats
It does not reflect the current ArchLinux perl package(s) layout. Please do not use this document as a template for creating new perl module packages... yet... This policy, if implemented - represents a major change in way Arch handles perl.
Current (apparent) problems with perl packages include:
- The current ArchLinux default perl installation installs site and vendor packages into the same directory tree, which frequently causes conflicts if the end user installs and upgrades bot archlinux perl (vendor) packages on top of site packages.
- A symlink-farm is created in /usr/lib/perl5/ and /usr/lib/perl5/site_perl.
- A number of standard modules seem to be missing, or were neglected to be added as provides in the perl package itself, causing confusion and redundant entries in AUR for perl modules as users try and fix the problem themselves.
- Current perl-module PKGBUILD's could be simplifed and standardized quite a bit.
This policy would eliminate all these problems (features!).
Current (apparent) downsides to adopting a policy such as this one:
- An update of every perl module PKGBUILD so that it installs into the correct (vendor) directory tree. It remains somewhat backwards-compatible with the old structure, in that old PKGBUILD's would technically work, however local (site) installs could conflict with vendor installs in un-upgraded packages.
- Introduces changes into the perl package, which lives in [current], and proposes a new perl-modules package, which would live in [extra].
Perl Versions
At any given time, the package perl should represent the current stable upstream version of Perl revision 5. (see Perl 6).
Only one package may contain the /usr/bin/perl binary and that package must either be perl or a dependency of that package. In order to provide a minimal installation of Perl for use by applications without requiring the whole of Perl to be installed, the perl package contains the binary and a basic set of modules.
Module Paths
Perl searches three different locations for modules, referred to in this document as core in which modules distributed with Perl are installed, vendor for packaged modules and site for modules installed by the local administrator.
The module search path (@INC) in the Archlinux packages has been ordered to include these locations in the following order:
- site
Modules installed by the local administrator for the current version of Perl. Typically, these modules are installed using the cpan tool, or are downloaded in source form and installed via make.
- /usr/lib/perl5/site_perl/version
- /usr/share/perl5/site_perl/version
- vendor
Packaged modules, installed via the pacman tool from current/extra or community, or built into proper archlinux packages from ABS/AUR PKGBUILDS.
- /usr/lib/perl5/vendor_perl
- /usr/share/perl5/vendor_perl
- core
Modules included in the core Perl distribution. Also modules included in the perl-modules package. See core-perl-modules.
- /usr/lib/perl5/version
- /usr/share/perl5/version
- obsolete
Obsolete is the pathname to modules installed prior to the establishment of this document. This path will be removed from the perl package at some point in the future.
- /usr/lib/perl5/site_perl/current/arch
- /usr/lib/perl5/site_perl/current/
In each of the directory pairs above, the lib component is for binary, architecture dependant(XS) modules, and share for architecture-independent (pure-perl) modules. Under no circumstances should current be used as a replacement for version. Core and site modules really do depend on the perl version for which they were installed.
The POD files and manual pages which do not refer to programs may be split out into a separate perl-doc packages, which is normal for most archlinux packages in general. This is optional however.
Manual pages distributed with Perl packages must be installed into the standard directories:
Manual pages for programs and scripts are installed into /usr/share/man/man1 with the extension .1.
Manual pages for modules are installed into /usr/share/man/man3 with the extension .3perl.
Site Modules are perl modules installed by the local administrator for the current version of Perl. Typically, these modules are installed using the cpan tool, or are downloaded in source form and installed via make.
Site Directories
The Perl packages must provide a mechanism for the local administrator to install modules under /usr/lib/perl5/site_perl but must not create or remove those directories.
Modules should be installed to the directories described above in Module Path site, programs to /usr/local/bin and manual pages under /usr/local/man.
Site Installation
The following commands should be sufficient in the majority of cases for the local administrator to install modules and must create directories as required:
perl Makefile.PL make install
cpan Foo::Bar
Vendor modules are packaged modules, installed via the pacman tool which grabs pre-compiled modules from a repository, or modules which have been built into proper archlinux packages from a PKGBUILD.
Vendor Directories
The installation directory for Archlinux modules must be different from that for site modules. Some guidelines include:
- The current Perl packaging uses the vendor directories for this purpose, which are at present as described in above as vendor.
- No version subdirectory exists on these directories as the dependencies for packaged modules should ensure that all work with the current perl package.
- The Perl distribution includes many modules available separately from CPAN, which may have a newer version. The intent of the @INC ordering (described above) is to allow such modules to be packaged to vendor which take precedence over the version in core. A packaged module which shadows a core module in this way must be a newer version.
- Module packages must install manual pages into the standard directories using the extensions .1p and .3pm to ensure that no conflict arises where a packaged module duplicates a core module.
- .packlist (used for module uninstalls) and perllocal.pod (used to record local/site installations) files should not be installed, and should be removed from the package if found.
- Empty directories should be pruned.
Module Package Names
Perl module packages should be named for the primary module provided. The naming convention for module Foo::Bar is perl-foo-bar. Packages which include multiple modules may additionally include provides for those modules using the same convention.
Vendor Installation
A module should use the following lines in the PKGBUILD build target.
perl Makefile.PL INSTALLDIRS=vendor MAN1EXT=1p MAN3EXT=3pm
and this one to install the results into the temporary tree...
make install DESTDIR=$startdir/pkg install || return 1
A makedepends on perl (>= 5.8.8-6) is required in order ensure that the module is correctly installed into the new @INC path.
Sample Vendor PKGBUILD
# Maintainer: Harry Hacker <firstname.lastname@example.com> pkgname=perl-html-template pkgver=2.9 pkgrel=2 pkgdesc="Perl/CPAN Module HTML::Template : a simple HTML templating system" arch=('i686' 'x86_64') url="http://search.cpan.org/SAMTREGAR/HTML-Template" license=('GPL' 'Artistic') makedepends=("perl>=5.8.8-6") source=("http://www.cpan.org/authors/id/S/SA/SAMTREGAR/HTML-Template-${pkgver}.tar.gz") md5sums=("cbf88a486b36284be55765ac7357c187") options=(!emptydirs) build() { cd $startdir/src/HTML-Template-2.9 /usr/bin/perl Makefile.PL INSTALLDIRS=vendor MAN1EXT=1p MAN3EXT=3pm || return 1 make || return 1 make DESTDIR=$startdir/pkg install || return 1 /usr/bin/find $startdir/pkg -name '.packlist' -exec rm '{}' \; /usr/bin/find $startdir/pkg -name 'perllocal.pod' -exec rm '{}' \; }
Architecture-Independent Modules
Architecture-independent modules which require core modules from the perl package must specify a dependency on that package.
Modules which contain explicit require version or use version statements must specify a dependency on perl with the minimum required version, or more simply the current version.
In the absence of an explicit requirement, architecture-independent modules must depend on a minimum perl version of 5.8.8-6 due to the changes in @INC introduced by that version.
Binary Modules
Binary modules must specify a dependency on either perl with a minimum version of the perl package used to build the module, and must additionally depend on the expansion of perlapi-$Config{version} using the Config module.
Core modules are perl modules "typically" included in the core Perl distribution. It also includes in the perl-modules package.
Core Directories
- Modules included in the core Perl distribution should be installed into /usr/lib/perl5 and /usr/share/perl5.
- Only modules contained in the perl or perl-modules package should be installed into this directory tree.
- No version subdirectory exists in these paths as the dependencies for packaged modules should ensure that all work with the current perl package.
Core perl packages
The perl package should contain the /usr/bin/perl binary, and a minimal set of modules needed in order for simple perl scripts to run and for a base system to operate. It should be maintained in the [current] repository.
Sample perl PKGBUILD
The perl-modules package should contain all the extra modules provided in the perl package, as well as all of the the pragmatic and standard modules listed by executing perldoc perlmodlib. This package should provide modules which are expected to be present on any standard perl installation; such as Data::Dumper, CGI, and Encode. In addition, this package must includes provides for the archlinux packagenames for each of the modules contained.
This package is complex, and it should be updated only when the perl package is.
Because perl-modules must not be required for the basic operation of a Archlinux computer, perl-modules should be located in the [extra] repository and not in the [current] repository.
Users requiring a newer modules than what is provided in perl-modules are advised to install a site package until the next version of the perl package is released.
The current stable upstream version at the time of this writing is 5.8.8. There is currently work in progress on the next major revision, although the specifications have yet to be finalised.
It is anticipated that when Perl 6 is released it will initially be packaged as perl6, install the binary as /usr/bin/perl6 and use different directories for packaged modules to perl:
- /usr/lib/perl6
- /usr/share/perl6
This will allow Perl 5 and 6 packages and modules (which should be packaged as perl6-foo-bar), to co-exist for as long as required.
At some stage in the future when Perl 6 is sufficiently mature, the package naming may be reversed such that the perl package contains Perl 6 and the current package becomes perl5.


text:
Randy Moss, 49ers wide receiver
Randy Moss missed football so much that he gave up retirement to continue his career. As he reflected on Lewis' career, Moss said the most impressive thing about the linebacker might have been his ability to become a vocal leader for an entire team. "For him to take a franchise and put it on his back, it's very rarely that you see a defensive player do that," Moss said. "The focus is usually on a running back, a receiver and predominantly a quarterback, and for him to be able to take a franchise and put it on his back and bring them up to be a powerhouse, that's a credit to Ray, his people and the Baltimore Ravens' organization." -- Monique Jones
Copyright © 2019, Daily Press

subset: commoncrawl


text:
With real xxx videos uploaded from our most active and sexiest members to their profilesWith thousands of sexy videos to download absolutely free!
Visit our video Gallery and see what our members have been up to.Search millions of profile for Videos, voice intro's and see web cams from real members.Continue...
18 U.S.C. 2257 Declaração de Isenção


text:
Have an account?
Need an account?Create an account
Table Of Contents
Release Notes for Cisco ONS 15600 Release 5.0.4
Maintenance and Administration
Resolved Caveats for Release 5.0.4
Maintenance and Administration
Common Control and Cross Connect Cards
New Features and Functionality
Additional Support for In Service Topology Upgrades
State Verification Scan Before Activation
SONET J1 Path Trace Automatic Mode
Timing Synchronization Enhancements
High Level Functional Differences
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Release Notes for Cisco ONS 15600 Release 5.0.4
Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
September 2007
Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15600. For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to Release 5.0 of the Cisco ONS 15600 Procedure Guide, Cisco ONS 15600 Reference Manual, Cisco ONS SONET TL1 Command Guide, and Cisco ONS 15600 Troubleshooting Guide. For the most current version of the Release Notes for Cisco ONS 15600 Release 5.0.4, visit the following URL:
Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, visit the following URL:
Resolved Caveats for Release 5.0.4
New Features and Functionality
Obtaining Technical Assistance
Changes to the Release Notes
This section documents supplemental changes that have been added to the Release Notes for Cisco ONS 15600 Release 5.0.4 since the production of the Cisco ONS 15600 System Software CD for Release 5.0.4.
The following changes have been added to the release notes for Release 5.0.4.
Changes to Resolved Caveats
The following resolved caveats have been added.
Review the notes listed below before deploying the ONS 15600. Caveats with DDTS tracking numbers are known system limitations that are scheduled to be addressed in a subsequent release. Caveats without DDTS tracking numbers are provided to point out procedural or situational considerations when deploying the product.
DDTS # CSCeg34361
Revert fails if the internal subnet differs from that in the revert database. This issue is seen in a revert from a 5.0.x release to Release 5.0. This issue is not seen in reverts from Release 5.0.x to 1.x. This issue will be resolved in Release 6.0.
DDTS # CSCeh16339
Clicking the Cancel button from the CTC network view, Software tab during a software download does not stop the download, but gives the appearance in the network view, Software tab that it has. This symptom only occurs if you click the Cancel button after the software has been copied to the node, and during the "Copying to Standby TSC" phase of the software download. To avoid this issue, cancel the software download from the node view, Software tab instead of from the network view, Software tab when canceling during the "Copying to Standby TSC" phase of the software download. This issue will be resolved in a future release.
DDTS # CSCee60276
Some circuits might be displayed as PARTIAL after one or more ONS 15600 nodes is upgraded to Release 5.0.x. This can occur when the ONS 15600 interoperates with ONS 15454, 15327, or 15310 nodes in the same network, and there exist circuits with their source on the ONS 15454/15327/15310 nodes and drops on the ONS 15600 nodes. If this occurs, run "Circuit Reconfigure" on the affected PARTIAL circuits. For further documentation of this circumstance, see the Upgrading Cisco ONS 15600 Release 1.x to 5.0 document.
Maintenance and Administration
Caution VxWorks is intended for qualified Cisco personnel only. Customer use of VxWorks is not recommended, nor is it supported by Cisco's Technical Assistance Center. Inappropriate use of VxWorks commands can have a negative and service affecting impact on your network. Please consult the troubleshooting guide for your release and platform for appropriate troubleshooting procedures. To exit without logging in, enter a Control-D (hold down the Control and D keys at the same time) at the Username prompt. To exit after logging in, type "logout" at the VxWorks shell prompt.
DDTS # CSCeg57163
ONS platforms support only a single OSPF virtual link. This issue will be resolved in a future release.
DDTS # CSCdy58342
Network connectivity could be lost if a backbone area becomes segmented into multiple GNEs. This occurs only if multiple ONS 15600 nodes and routers are connected to the same LAN in OSPF area 0. If a link between two routers breaks, the CTC session connected to Router 1 will not be able to communicate with the ONS 15600 connected to Router 2. To resolve, you must repair the link between the routers or provide another form of redundancy in the network. This is as designed.
DDTS # CSCdz07098
If OSPF on LAN is enabled with an area ID that is the same as the area ID of any of the DCC Links, CTC will not be able to discover any of the DCC Connected Nodes. To avoid this issue, set the OSPF on LAN area ID to an area other than any of those already occupied by a DCC link. This is as designed.
DDTS # CSCdy25142
Equipment alarms are always reported based on the activity of the particular card, without taking card redundancy into consideration. Thus, an equipment alarm such as CTNEQPT-PB-0 may be raised against a line card as CR(SA) even though the traffic is protected. This issue will be resolved in a future release.
DDTS # CSCeb49407
Choosing certain qualities of RES settings in the CTC Provisioning tab, Timing subtab, may trigger a reference failure. Specifically, this can occur if you select the quality of RES level such that any of the following are true.
When you then input an actual reference signal lower than ST3E quality, the failure is triggered. This issue will be resolved in a future release.
DDTS # CSCdy14265
The manual bridge and roll feature allows you to perform the END command once the roll operation transitions from a ROLL PENDING to ROLL condition, even if the roll to port has an invalid signal. To avoid traffic impact, ensure that the roll-to line is alarm-free. If an alarm exists, you can choose to do nothing and wait for the alarm to clear, to delete the roll, or to proceed in spite of the alarm. This issue will not be resolved.
Control Cards
DDTS # CSCeg16339
Performing a TSC soft reset on an ONS 15600 with a large BLSR and circuit configuration sometimes causes subordinate I/O cards to soft reset. This issue will be resolved in a future release.
Data IO Cards
DDTS # CSCef20813
No graphical representations of LEDs for ASAP ports are displayed in the CTC card view. SD and SF LED representations are also absent from the CTC node view for some legacy OCn cards. There are no plans to resolve this issue.
DDTS # CSCeg12963
On an OC-48 port of an ASAP card, use of the ED-STS9c TL1 command to create a dual TAP port is only accepted for STS-x-y-z-4/16/28, and is incorrectly denied for the first, and the rest of all the STSs. To work around this issue, when creating an STS-9c dual tap on an OC-48 ASAP port, start the tap on the STS 4, STS 16, or STS 28 boundary. This issue will be resolved in a future release.
BLSR Functionality
DDTS # CSCeh49665
Connections might still exist after circuit deletions on BLSR DRI rings for which the primary node is isolated. For BLSR DRI rings with several types of DRI circuits, if you isolate the primary node by deleting the database, reseat the I/O cards, then delete all BLSR DRI circuits, the SSXCs still show connections. To avoid this issue, do not delete or create BLSR DRI circuits when a node on the BLSR DRI ring is isolated. This issue will be resolved in a future release.
DDTS # CSCeh35448
Rarely, a line card might reboot after multiple times creating and deleting a BLSR with circuits provisioned for PCA and DRI. If you have a BLSR with circuits provisioned for PCA and DRI, and you then delete the circuits, delete the BLSR, and reenter the same ring ID and facilities (as the BLSR you just deleted), it is possible to see a line card reboot. This issue will be resolved in a future release.
DDTS # CSCeh11972
Soft resetting both SSXC cards at the same time while the BLSR is in wait to restore results in a one-second hit. This also causes an out of sync condition where the ring appears switched on the GUI interface and CID-MISMATCH alarms are possibly declared. This issue can occur on a ring that is still switched and for which wait to restore period is active. Avoid soft resetting both SSXC cards at the same time when a wait to restore is active. Soft resets should only be performed when rings are in a steady state (switched or idle). If this out of sync condition occurs, a manual or forced switch on the affected rings will be required to resynchronize the system. This issue will be resolved in a future release.
DDTS # CSCeb56502
A circuit remains in the roll_pending state after a roll attempt is cancelled on a path roll in a two-fiber BLSR, where the path has an active protection switch at the circuit destination node. To recover from this situation, restart CTC. This issue will be resolved in the future release.
Path Protection Functionality
DDTS # CSCec15064
A path protection/SNCP circuit with a defect signal present (for example, AIS-P or AIS-V) on the protect path will produce RDI-P or RDI-V upstream of the detection point, but these signals will not be detected or indicated. This issue will be resolved in a future release.
DDTS # CSCdx61916
If, using CTC, you attempt to create a protected VT1.5 circuit that originates on one ONS 15327/454 that is connected to the ONS 15600 via path protection to another ONS 15327/454 that is connected to the ONS 15600 via 1+1 or BLSR, the circuit creation request will be denied because of mixed protection domains. CTC is currently incapable of routing VT circuits across the ONS 15600 when mixed protection schemes are involved. VT traffic can be routed across the ONS 15600 when mixed protection schemes are involved by performing the following:
Step 1 On the ONS 15600, create an STS level cross connect with the requisite path selectors.
Step 2 Use CTC to create a VT circuit from the source node to the trunk ports that interface to the 15600.
Step 3 Use CTC to create a VT circuit between the destination node and the trunk ports that interface with the 15600.
Note While this workaround provides the ability to route VT traffic across the ONS 15600 when mixed protection domains exist, the traffic must be managed as three separate circuits instead of one single end-to-end circuit.
This issue will be resolved in a future release.
DDTS # CSCdy68110
When you attempt to configure VT circuits on a test configuration consisting of two ONS 15454 nodes and one ONS 15600 node, when both ONS 15454s are connected to the ONS 15600 node using a dual path protection connection configuration, and when the ONS 15600 node serves as an intermediate node between the two ONS 15454 nodes, you may be unable to create a VT circuit from one ONS 15454 to the ONS 15600 and then to the other ONS 15454. VT Tunnels are created, but the VT circuit is not created. A mixed protection domain error message is raised when this occurs. To avoid this issue, create the VT tunnels manually, so that the two tunnels do not create a topology where the working and protect tunnels share the same I/O card. After the tunnels have been created, the VT circuit can be successfully added. This issue will be resolved in future release.
DDTS # CSCdx94969
Physical PM parameters can not be retrieved through the SNMP interface. MIBs released with the ONS 15600 do not have entries for the following physical PM parameters.
The standard SONET Generic MIB does not have entries for these. To work around this issue, use CTC to retrieve the values. SNMP support for these parameters may be considered for a future release.
DDTS # CSCdy54737
The following PM parameters can not be retrieved through SNMP.
•Protection groups:
•Far End counts for line and path
•1-Day PM counts
To retrieve these counts, use CTC. SNMP support for these parameters may be considered for a future release.
DDTS # CSCeg14663
The response from the TL1 command, RTRV-NE-IPMAP, contains two rows (one duplicate) of information for each DCC connected port that has provisioned BLSR protection. This issue will be resolved in a future release.
DDTS # CSCeg15770
The TL1 command RTRV-INV::ALL does not return inventory information for all cards present in the node when a preprovisioned PIM exists on a ASAP card. To use this command you must first delete the preprovisioned PIM. This issue will be resolved in a future release.
DDTS # CSCeb46234
A TL1 user cannot preprovision IO cards when a filler card is in the slot. Removal of the filler card will clear the slot and allow the TL1 user to preprovision the IO card. This is by design.
Resolved Caveats for Release 5.0.4
The following caveats were resolved in Release 5.0.x.
DDTS # CSCeh07574
Do not install an ASAP card in a system running Release 5.0. During normal testing at 50 deg C temperature the ASAP card can experience a silent failure that at times can be service affecting. Traffic might take errors when you run a fully loaded node with ASAP cards at 50 deg C temperature. Bit errors can occur on some ports. This issue is resolved in Release 5.0.2.
Maintenance and Administration
DDTS # CSCei03232
You cannot tunnel OSI over a DCC overhead circuit with foreign nodes that use a minimum (HDLC) frame size less then 6 bytes. This issue is resolved in Releases 5.0.4, 5.0.5, and 6.0.
DDTS # CSCeh94857
If a 1+1 is added after an SDCC tunnel is created, the tunnel is not protected. After conversion of an unprotected OC-N link provisioned with an SDCC tunnel to a protected 1+1, subsequent Manual or automatic protection switching operations will drop the SDCC Tunnel. Switching back to the Working Path will restore the SDCC Tunnel. To avoid this, create the 1+1 first and then create the SDCC Tunnel. This issue is resolved in Releases 5.0.4, 5.0.5, and 6.0.
DDTS # CSCeg60310
Issuing ampersand ranging to manage a full line card's worth of STSs, while at the same time issuing CTC commands against STSs on the same line card, might cause the TSC to reset. This issue is resolved in Release 5.0.2.
DDTS # CSCea78286
In a network topology where ONS 15600 A and ONS 15600 B are connected to the same LAN, with OSPF turned on, both Nodes A and B in the same non-backbone area, and a virtual link created from Node A to a backbone router, if another virtual link to the backbone is created on Node B, a TSC switch may occur. To avoid this situation, do not design a network in the aforementioned configuration; specifically, do not create the second virtual link. This issue is resolved in Release 5.0.
DDTS # CSCdy43268
When the OSPF DCC Metric or the OSPF LAN Metric is modified via CTC, there is no change to the routing of traffic. If a link is broken anywhere in the network, or if the TSC is soft reset the traffic will then be routed appropriately. This issue is resolved in Release 5.0.
DDTS # CSCea47483
If you initiate a roll from the circuits tab, then switch to the rolls subtab of the circuits tab, select the circuit and press the finish button multiple times (for example, if you accidentally double-click the finish button) to complete the roll, then multiple circuits will be displayed on the circuits tab, only one of which is complete (the rest are incomplete). When completing a roll from the rolls subtab of the circuits tab, only press the finish button a single time for each circuit that you wish to roll. This issue is resolved in Release 5.0.
DDTS # CSCea82511
The WTR condition is not displayed after rebooting the working port in an OC-48 1+1 bidirectional revertive configuration. This issue is resolved in Release 5.0.
Common Control and Cross Connect Cards
DDTS # CSCin90573
The TSC might reset when performing an SNMP walk on the entityMIB. This issue is resolved in Releases 5.0.4, 5.0.5, and 6.0.
DDTS # CSCei34480
The TSC might display messages indicating low resource conditions during restoration of databases containing large numbers of circuits, especially path protection-path protection circuits. If this occurs, shut down attached management sessions (especially CTC/CTM) until the updates are complete. This issue is resolved in Releases 5.0.4, 5.0.5, and 6.0.
DDTS # CSCei16460
A common control card reset can occur under the following three conditions.
1. The node has OSPF enabled on the LAN and the DCC area comes up before the LAN area.
2. In the DCC area, there is at least one other node running OSPF in the same LAN area and this node is up in both the LAN and DCC area.
3. There is either a router with static routes configured and advertised by OSPF; or there is a node with LAN a connection, but OSPF is disabled.
This issue has been only seen in Release 5.0.2. To avoid this issue, disable OSPF on the LAN. This issue is resolved in Releases 5.0.4 and 5.0.5.
Data IO Cards
DDTS # CSCeg32936
When you remove an ASAP PPM or PIM, the current PM interval is marked invalid. However, when the current 15min time period expires, the first historical PM interval (Prev in CTC) is incorrectly updated to valid. The invalid PM intervals should last for the duration of the PPM/PIM absence. To recover from this you must reinsert the PPM/PIM. This issue is resolved in Release 5.0.2.
BLSR Functionality
DDTS # CSCeg47868
Opposite side BLSR IDRI circuits do not recover after segmenting both BLSR DRI rings. If you create opposite side I-DRI circuits, service on working and secondary on RIP, segment both BLSR DRI rings using force switches so that termination nodes are on one segment, primary and secondary nodes on the other segment, then release the force switches in the order that they were performed, some circuits will drop traffic. To avoid this issue, segment one BLSR DRI ring at a time with force switches and release force switches before segmenting the second rings. This issue is resolved in Release 5.0.2.
DDTS # CSCeg72819
In a BLSR/MS-SPRing DRI configuration, if you add an intermediate node to the BLSR/MS-SPRing on the path between the primary and the secondary handoff, node isolation on the DRI can cause a loss of traffic. To correct this, delete and recreate the circuit in CTC. You can avoid the issue by creating the cross connect using TL1 instead of performing a network view right-click on the node and executing "Update Circuits With New Node." This issue is resolved in Release 5.0.2.
DDTS # CSCdz19797
On an ONS 15600, SNMP alarms that have an alarm state of "notAlarmed" show up as "administrative" when retrieved from the MIB browser.
Alarms retrieved from CTC and via the TL1 interface do not have this issue, and so, can be used to verify any alarm states that are incorrectly displayed from the SNMP interface. This issue is resolved in Release 5.0.
TL1 Functionality
DDTS # CSCeg18208
The TL1 command OPR-LPBK-<STS_PATH> gives an "Invalid Path" when using a VFAC AID, even though using the same VFAC AID in a RTRV-CRS command shows the AID is actually involved in a cross connect, so the path should be valid for the OPR-LPBK-<STS_PATH> command. This can occur when the VFAC AID used in the OPR-LPBK-<STS_PATH> command refers to a port on an ASAP-4 card that has been configured for the GIGE payload, where the PIM and PPM layers on the ASAP card are already present or provisioned, and where there is a cross connect provisioned on the node for which the VFAC AID is one of the endpoints, with cross connect and ports in the proper maintenance state such that provisioning a loopback should be allowed. To work around this issue, use CTC instead of TL1 to create the loopback. This issue is resolved in Release 5.0.2.
DDTS # CSCeg87471
Do not set the TID for an ENE to more than 19 characters. Setting the TID for an ENE to 20 characters or more and then issuing a TL1 command on the GNE to execute on the ENE will result in TL1 agent connectivity issues on the ENE. Specifically, if you set the TID on the ENE to 20 characters, reboot the TCC, then try to connect to that ENE from a GNE this will result in a loss of TL1 connectivity to the GNE. This issue is resolved in Release 5.0.2.
DDTS # CSCeb58786
When a node is provisioned for external timing and SSM Message Set configured for Generation 1, if SONET Minimum Clock (SMC) or Stratum 4 is received, the TL1 RTRV-SYNCN command will display DUS (an incorrect message). CTC, however, shows the correct SSM message being received, and all other Generation 1 messages are displayed correctly.
This can also be seen with the Generation 2 Message Set. Whenever Stratum 3, SMC, or Stratum 4 are received, the RTRV-SYNCN command displays DUS. CTC consistently displays the correct SSM messages being received. Use CTC to retrieve the SSM information. This issue is resolved in Release 5.0.
New Features and Functionality
This section highlights new features and functionality for Release 5.0.x. For detailed documentation of each feature, consult the user documentation.
New Hardware
SSXC Card
The single shelf cross-connect card (SSXC) is the central element for ONS 15600 switching. The SSXC card establishes connections and performs time division switching (TDS) at STS-1 and STS-Nc levels between ONS 15600 traffic cards.
The SSXC card works with the TSC card to maintain connections and set up cross-connects within the ONS 15600. You establish cross-connect and provisioning information using CTC or TL1. The TSC card stores the proper internal cross-connect information and relays the setup information to the SSXC card.
SSXC Switch Matrix
The switch matrix on each SSXC card consists of 6,144 STS-1 ports, with a maximum of 6,144 STS-1 cross-connections. When creating bidirectional STS-1 cross-connects, each bidirectional cross-connect uses two STS-1 ports, so the result is that the SSXC supports 3,072 bidirectional STS-1 cross-connects. Any STS-1 on any port can be connected to any other port, meaning that the STS cross-connections are non blocking. Non-blocking connections allow network operators to connect any STS1, STS3, STS12, STS24, STS48, or STS192 payload that is received on an OC-48 or OC-192 interface (or any STS6 or STS9 payload that is received on an ASAP interface) to any other interface capable of supporting the bandwidth.
The SSXC card has 128 input ports and 128 output ports capable of STS-48. An STS-1 on any of the input ports can be mapped to an STS-1 output port, thus providing full STS-1 time slot assignments (TSAs).
SSXC Slots and Connectors
Install an SSXC card in Slot 6 and a second SSXC card in Slot 8 for redundancy. (Slots 7 and 9 are also occupied by the SSXC faceplate.) The SSXC card has no external interfaces. All SSXC card interfaces are provided on the ONS 15600 backplane. For SSXC card level indicators consult the Cisco ONS 15600 Reference Manual.
Any Service Any Port Card
The Any-Service, Any-Port (ASAP) card provides up to 16 Telcordia-compliant, GR-253 SONET OC-3, OC-12, OC-48, or Gigabit Ethernet ports per card in any combination of line rates. The ports operate at up to 2488.320 Mbps over a single-mode fiber. The ASAP card has sixteen physical connector adapters with two fibers per connector adapter (Tx and Rx). The card supports STS-1 payloads and concatenated payloads at STS-3c, STS-6c, STS-9c, STS-12c, STS-24c, or STS-48c signal levels. It is fully interoperable with the ONS 15454 G-Series Ethernet cards.
The ASAP card consists of the ASAP carrier modules, the 4-port I/O module (4PIO), and the Pluggable Port Module (PPM, also known as a Small Form-Factor Pluggable [SFP]). The ASAP carrier module has 4 slots available for the 4PIOs, totaling 16 ports. The ports can each be provisioned as either OC-3, OC-12, OC-48, or Gigabit Ethernet.
You can install ASAP carrier modules in Slots 1 through 4 and 11 through 14. Each 4PIO module can accommodate up to four SFPs, and each SFP has a female LC connector. For card level indicators, port level indicators, and port numbering consult the Cisco ONS 15600 Reference Manual.
ASAP Card Application
The ASAP Carrier Card plugs into any of the eight available I/O slots for the ONS 15600. Each ASAP carrier card has four slots available for up to and including four ASAP Pluggable Input/output Modules (PIMs). There are four slots available on each PIM for Pluggable Port Modules (PPMs), which are Small Form-factor Pluggable (SFP) optics. Four PPMs per ASAP PIM are allowed, which means that there can be as many as 16 PPM optical network interfaces for each ASAP carrier card. Each PPM port can support any of the following SFP optics modules:
•ONS-SI-155-L2 single rate optics module, supporting the OC-3 LR-2 rate
•ONS-SI-622-L2 single rate optics module, supporting the OC-12 LR-2 rate
•ONS-SE-2G-L2 single rate optics module, supporting the OC-48 LR-2 rate
•ONS-SE-Z1 multi-rate optics module, supporting the following rates:
Each ASAP 4port I/O (ASAP_4PIO) PIM is hot-pluggable while other ports on other PIMs are functional. Each SFP is also hot-pluggable.
Layer 1 Ethernet transport is implemented for Gigabit Ethernet (GE) interfaces. GE traffic is generic framing procedure (GFP), ITU X.86, or Cisco high-level data link control/LAN extension (HDLC/LEX) encapsulated and mapped into a SONET payload.
The data path processing consists of:
•Optical-to-electrical conversion (O/E) and electrical to optical (E/O) on the ASAP_4PIO PIM
•Gigabit Ethernet to Ethernet over SONET (EoS) mapping (for the GE ports only)
Note For a single flow of Gigabit Ethernet, traffic can be mapped to an STS-48c. This choice limits maximum usable Ethernet ports to eight when all are mapped to STS-48c. Any time an STS-48c is used for an Ethernet connection, one-eighth of the total card bandwidth is consumed on the EoS mapper. If you want to use all 16 ports for Gigabit Ethernet, each port should be mapped to STS-24c or less bandwidth.
Ethernet facilities on the ASAP card include:
•Ethernet ports can be provisioned on a mutli-ate PPM.
•Encapsulation methods allowed for the Ethernet ports are:
–Cisco HDLC/LEX
For specifics on Ethernet operation, framing, mapping, etc. using the ASAP card refer to the Cisco ONS 15600 Reference Manual.
New Software Features
GFP-F Framing
Generic Framing Procedure (GFP) defines a standard-based mapping for different types of services onto SONET/SDH. With Release 5.0.x the ASAP card supports frame-mapped GFP (GFP-F), the PDU-oriented client signal adaptation mode for GFP. GFP-F maps one variable length data packet onto one GFP packet. GFP defines common functions and payload specific functions. Common functions are those shared by all payloads. Payload-specific functions differ depending on the payload type. The GFP standard is detailed in ITU recommendation G.7041.
Provisionable Framing Mode
Release 5.0.x provides a method to provision framing mode in the card view, Provisioning > Card tab, which displays the framing mode selections for the card in a drop-down list, and allows you to change the framing mechanism to either HDLC or GFP-F. You can also preprovision the framing mode prior to installing the card, and the card will boot up in the pre-provisioned mode. For details on framing mode provisioning consult to user documentation.
Pluggable Port Module Support
Release 5.0.x supports four small form-factor pluggables (SFPs), also known as Pluggable Port Modules (PPMs), for the ONS 15600 ASAP card.
Table 1 lists the available SFPs for the Cisco ONS 15600.
Table 1 Supported SFPs
Card Supported Compatible SFP
(Cisco Product ID)
Cisco Top Assembly Number (TAN)
For SFP applications with the ASAP card refer to the Cisco ONS 15600 Reference Manual. For information on the particular SFPs and their installation, consult the document, Installing GBIC, SFP and XFP Optical Modules in Cisco ONS 15454, 15327, 15600, and 15310 Platforms.
Enhanced State Model
Release 5.0.x introduces new administrative and service states for Cisco ONS 15600 cards, ports, and cross-connects. Administrative and service states are based on the generic state model defined in Telcordia GR-1093 Core, Issue 2 and ITU-T X.731 and are available for all support management interfaces. The following state types and state transition types are defined for Release 5.0.x. Consult the Cisco ONS 15600 Reference Manual for specific states and their applications.
Service States
Service states include a Primary State (PST), a Primary State Qualifier (PSTQ), and one or more Secondary States (SST).
Administrative States
Administrative states are used to manage service states. Administrative states consist of a PST and an SST. A change in the administrative state of an entity does not change the service state of supporting or supported entities.
Service State Transitions
The possible transitions from one service state to the next state for cards, ports, and cross-connects. A service state transition is based on the action performed on the entity and any autonomous activity.
Card Service State Transitions
The service state transitions for cards.
Port and Cross-Connect Service State Transitions
Port states do not impact cross-connect states with one exception. A cross-connect in the OOS-AU,AINS service state cannot transition autonomously into the IS-NR service state until the parent port is IS-NR.
Circuit State Model
Release 5.0.x adds support for circuit service and administrative states in CTC. For more information consult the user documentation.
32 Ring Two-fiber BLSR
With Release 5.0.x The ONS 15600 can support 32 concurrent two-fiber bidirectional line switched rings (BLSRs). Each BLSR can support up to 24 ONS 15600s. Because the working and protect bandwidths must be equal, you can create only OC-48 or OC-192 BLSRs.
In-Service Topology Upgrades
In Release 5.0.x in-service topology upgrades are supported for unprotected to path protection, and terminal to linear (add a node to a 1+1). Release 5.0.x provides both manual methods and CTC wizards for completing these upgrades.
Note Traffic hits resulting from an in service topology upgrade are less than 50 ms; however, traffic might not be protected during certain upgrades: in the case where you are upgrading from unprotected to path protection, with unidirectional routing, traffic hits might be greater than 50 ms. Cisco recommends waiting for a maintenance window to perform the topology upgrade in this case.
CTC Topology Upgrade Wizards
The following CTC topology upgrade wizards have been added for Release 5.0.x to support in service topology upgrades.
Terminal to Linear—Add a Node to 1+1
The wizard for this feature is invoked by right-clicking on a 1+1 link and then selecting the "terminal to linear" option. The option adds a node between a two nodes connected by a 1+1.
Additional Support for In Service Topology Upgrades
Circuit Routing
With Release 5.0.x you can choose between manually or automatically routing path protection circuits for a topology upgrade.
The following circuit types are supported for topology upgrades.
•Synchronous transport signal (STS)
•Unidirectional and bidirectional
•Automatically routed and manually routed
•CTC-created and TL1-created
•Ethernet (unstitched)
•Multiple source and destination (both sources should be on one node and both drops on one node)
Circuit Merge and Reconfigure
The circuit merge and reconfigure features enable you to merge selected CTC or TL1 circuits into one or more discovered CTC circuits based on the alignment of the circuit cross-connects, rather than the circuit ID.
Circuit Merge merges m circuits into one circuit. This feature takes one master circuit and merges aligned circuits with the master.
Circuit Reconfigure merges m circuits into n circuits. This feature takes m circuits and reconfigures them based on cross-connect alignment. To merge circuits choose the Merge subtab of the Edit Circuits tab in CTC. To merge circuits choose the Merge subtab of the Edit Circuits tab in CTC. To reconfigure circuits, choose the CTC Tools > Circuits tab, and select "Reconfigure Circuits..."
Dual-ring Interconnect
Dual-ring interconnect (DRI) topology provides an extra level of path protection for circuits on interconnected rings. DRI allows users to interconnect BLSRs, path protection configurations, or a path protection with a BLSR, with additional protection provided at the transition nodes. In a DRI topology, ring interconnections occur at two or four nodes.
DRI Features
The following list provides supported BLSR DRI features at a glance.
•BLSR two fiber configurations
•BLSR with path protection supported at the STS level (VT level not supported)
•Traditional DRI and integrated (IDRI)
•Traditional four node interconnect
•Integrated two node interconnect
•BLSR path level protection
•Drop and continue included
•Circuit routing, both manual and automatic
•Same side, or opposite side interconnect
•Ring interconnect on protect (RIP)
•Interconnection with mixed OCn
•Open ended DRI (supported for multi-vendor)
Note Interconnection links do not support 1+1, 1:1, or 1:n.
Note Dual transmit is not supported for Release 5.0.x BLSR DRI.
Unlike BLSR automatic protection switching (APS) protocol, BLSR DRI is a path-level protection protocol at the circuit level. Drop-and-continue BLSR-DRI requires a service selector in the primary node for each circuit routing to the other ring. Service selectors monitor signal conditions from dual feed sources and select the one that has the best signal quality. Same-side routing drops the traffic at primary nodes set up on the same side of the connected rings, and opposite-side routing drops the traffic at primary nodes set up on the opposite sides of the connected rings. For BLSR DRI, primary and secondary nodes cannot be the circuit source or destination.
A DRI circuit cannot be created if an intermediate node exists on the interconnecting link. However, an intermediate node can be added on the interconnecting link after the DRI circuit is created.
DRI protection circuits act as protection channel access (PCA) circuits. In CTC, you set up DRI protection circuits by selecting the PCA option when setting up primary and secondary nodes during DRI circuit creation.
Path Protection to BLSR DRI Handoff Configurations
Path protection configurations and BLSRs can also be interconnected. In path protection to BLSR DRI handoff configurations, primary and secondary nodes can be the circuit source or destination, which is useful when non-DCC optical interconnecting links are present.
Open GNE
Release 5.0.x supports open GNE configurations, through which the ONS 15600 can communicate with non-ONS nodes that do not support point-to-point protocol (PPP) vendor extensions or OSPF type 10 opaque link-state advertisements (LSA), both of which are necessary for automatic node and link discovery. An open GNE configuration allows the DCC-based network to function as an IP network for non-ONS nodes. To support open GNE Release 5.0.x provides provisionable foreign DCC terminations, provisionable proxy server tunnels, and provisionable firewall tunnels.
Foreign DCC termination
To configure an open GNE network, you can provision SDCC, LDCC, and GCC terminations to include a far-end, non-ONS node using either the default IP address of 0.0.0.0 or a specified IP address. You provision a far-end, non-ONS node by checking the "Far End is Foreign" check box during SDCC, LDCC, and GCC creation. The default 0.0.0.0 IP address allows the far-end, non-ONS node to provide the IP address; if you set an IP address other than 0.0.0.0, a link is established only if the far-end node identifies itself with that IP address, providing an extra level of security.
Proxy Server Tunnels and Firewall Tunnels
By default, the SOCKS proxy server only allows connections to discovered ONS peers, and the firewall blocks all IP traffic between the DCC network and LAN. You can, however, provision proxy tunnels to allow up to 12 additional destinations for SOCKS version 5 connections to non-ONS nodes. You can also provision firewall tunnels to allow up to 12 additional destinations for direct IP connectivity between the DCC network and LAN. Proxy and firewall tunnels include both a source and destination subnet. The connection must originate within the source subnet and terminate within the destination subnet before either the SOCKS connection or IP packet flow is allowed.
To set up proxy and firewall subnets in CTC, use the Provisioning > Network > Proxy and Firewalls subtabs. The availability of proxy and/or firewall tunnels depends on the network access settings of the node. See the user documentation for further details.
State Verification Scan Before Activation
Before allowing a software activation or reversion to proceed, Release 5.0.x nodes verify that their current state meets required activation criteria. Activation criteria must be met in order to avoid traffic hits. For ONS 15454, ONS 15454 SDH, ONS 15327, and ONS 15310 nodes, all BLSR spans on the node must be locked-out, and no 1:1, 1:N, 1+1 or Y-Cable protection switches can be in progress. For ONS 15600 nodes, all BLSR spans on the node must be locked-out.
Admin SSM
Synchronization status messaging (SSM) is a protocol that communicates information about the quality of the timing source. SSM messages enable nodes to automatically select the highest quality timing reference and to avoid timing loops. With Release 5.0.x you can configure an SSM value for a timing source (either BITS-IN or Optical Line) by selecting from the "ADMIN. SSM" selection box in the BITS Facilities subtab of the node view, Provisioning > Timing tabs. This feature is useful when the selected external timing source has no SSM information. When you select the Admin SSM value, all switching decisions are subsequently made based on your selection. The same SSM value is transmitted out of the interface configured for BITS Out, and in transmit Optical S1. The DS1 BITS type with framing type SF(D4) only supports Admin SSM. The 64KHz+8KHz clock (ONS 15454 SONET) also only supports Admin SSM. ESF Framing must have Sync Messaging turned off (uncheck the check box) in order to enable Admin SSM selection. SONET nodes use the SSM Generation II message set, as defined in Table 4 of ANSI T1.101-1999. SDH nodes support SDH generation 1 SSM and STU. SONET nodes support only SONET SSM (GR-253).
STS Around Ring
Release 5.0.x supports manual provisioning of contiguous concatenation (CCAT) STS circuits around the ring (traffic travels around the ring, starting and ending at the same node). In previous releases, if you selected the circuit source and destination as starting and ending on different I/O ports of the same node, the result would be an intra-node circuit only. With Release 5.0.x, you can manually route this type of circuit all the way around the ring. STS around the ring is supported for an unprotected path, in an unprotected ring, unless the underlying topology is line protected, in which case the around the ring circuit will also be line protected. STS around the ring is supported for all circuit sizes, starting with STS1 (SONET), or STM1 (SDH), and for all supported management interfaces.
Provisionable Patchcords
A provisionable patchcord is a user-provisioned link that is advertised by OSPF throughout the network. Provisionable patchcords, also called virtual links, are needed if an ONS 15600 optical port is connected to an ONS 15454 transponder or muxponder client port provisioned in transparent mode. Provisionable patchcords are required on both ends of a physical link. The provisioning at each end includes a local patchcord ID, slot and port information, remote IP address, and remote patchcord ID. Patchcords appear as dashed lines in CTC network view.
For supported combinations for ONS 15600 optical cards and the ONS 15454 transponder/muxponder cards used in a provisionable patchcord, refer to the Cisco ONS 15600 Reference Manual. For more information about the ONS 15454 transponder and muxponder cards, refer to the Cisco ONS 15454 Reference Manual.
Optical ports have the following requirements when used in a provisionable patchcord:
•An optical port connected to an ONS 15454 transponder or muxponder port requires an SDCC or LDCC termination.
•If the optical port is the protection port in a 1+1 group, the working port must have an SDCC or LDCC termination provisioned.
•If a remote end (ONS 15454) of a provisionable patchcord is Y-cable protected, an optical port requires two patchcords.
SONET J1 Path Trace Automatic Mode
With Release 5.0.x the ONS 15600 supports J1 path trace automatic mode through both CTC and TL1.
You can enable the SONET J1 Path Trace byte to monitor interruptions or changes to circuit traffic provisioned on the following ONS 15600 cards.
•OC48/STM16 SR/SH 16 Port 1310—Receive only
•OC48/STM16 LR/LH 16 Port 1550—Receive only
•OC192/STM64 SR/SH 4 Port 1310—Receive only
•OC192/STM64 LR/LH 4 Port 1550—Receive only
•ASAP OC-N PPMs—Receive only
•ASAP Ethernet PPMs—Receive and transmit
The J1 byte transmits a repeated, 64-byte, fixed-length string. If the string received at a circuit drop port does not match the string the port expects to receive, an alarm is raised. In automatic mode, the receiving port assumes the first J1 string it receives is the baseline J1 string.
Note The ONS 15600 does not support J1/IPPM for BLSR.
Timing Synchronization Enhancements
Support for additional timing synchronization enhancements is added for the Release 5.0.x ONS 15600. The following additional timing enhancements are supported by both CTC and TL1.
•Mixed mode timing references (external BITS, Line and Internal)
•BITS Out
•Forced switching of reference sources
For full details of timing synchronization support, refer to the Cisco ONS 15600 Reference Manual.
CTC Enhancements
SSH Shell Access Option
With Release 5.0.x an ONS 15600 Superuser can select secure shell (SSH) as an alternative to Telnet at the CTC Provisioning > Security > Access tabs. SSH is a terminal-remote host Internet protocol that uses encrypted links. It provides authentication and secure communication over unsecure channels. Port 22 is the default port and cannot be changed.
CTC Circuits State Default
The Release 5.0.x circuit creation wizard uses the new node default value, Node.circuits.State, as the default circuit state when creating a circuit. This default can be set in the NE Defaults window, and will not be overridden by the "user preferences" command feature, which caused the default value to be abandoned when using the wizard in previous releases.
Shell Login Challenge
Release 5.0.x supports the requirement of a specific shell password, set initially by the first shell user and then required of subsequent shell users at login. When this feature is enabled, the password is required of all shell users (rather than each user having a separate account) from the time it is set or changed. In the CTC node view, Provisioning > Security> Access tabs, check the "Enable Shell Password" check box to enable the shell password feature. The password can then be set or changed in a telnet or SSH shell session using the "passwd" command.
Note The password should be 8 characters or less to avoid possible conflicts with certain FTP clients.
Date Format Selection
Release 5.0.x adds a date format option to CTC, enabling you to choose between U.S. (MM/DD/YY) and European (DD/MM/YY) date formats. To choose the date format, click the Edit menu and choose Preferences. Select the desired date format (the default is MM/DD/YY) and click OK. The name/value pair ("ctc.dateFormat=DD/MM/YY" or "ctc.dateFormat=MM/DD/YY") will be updated in the ctc.ini (Windows), or .ctcrc (UNIX) file, where preferences are stored. Subsequently, the date format used in all tables, dialogs, and tabs will be changed to the format you selected in the Preferences dialog.
Provisionable Patchcord Tab
Provisionable patchcords, also called virtual links, are needed if an ONS 15600 optical port is connected to an ONS 15454 transponder or muxponder client port provisioned in transparent mode. Release 5.0.x features a Provisionable Patchcord subtab in CTC that displays physical links and their associated protection types, so that, when a control channel cannot be terminated on either end of a physical link, and as a result, the physical link cannot be automatically discovered by OSPF, you can still view the physical link and its protection type in the management software interface. You can view the physical links and their terminations from the CTC network view > Provisioning > Provisionable Patchcords tabs; or from the CTC node view > Provisioning > Comm Channels > Provisionable Patchcords tabs. To provision the patchcord, you select the Node Name, Slot, Port, and ID for both ends of the physical link. The ID is a unique 16-bit number used to identify a virtual link on a node. IDs are only unique for the particular node.
TL1-CTC Circuit Unification
In Release 5.0.x CTC fully supports TL1-created circuits and TL1 fully supports CTC-created circuits. Release 5.0.x circuit behavior and appearance is unified across both management interfaces, and you can easily alternate between the two. It is also no longer necessary to upgrade a TL1 circuit for CTC, or to downgrade a CTC circuit for TL1. The following circuit unification enhancements are supported with Release 5.0.x.
•Release 5.0.x cross-connects can be given names via TL1 using ENT-CRS and ED-CRS (use the "CKTID" parameter).
•CTC-created circuits can now be fully deleted if all cross-connects are deleted via TL1. (Deleting a source node cross-connect automatically deletes the CTC "circuitInfo" database object.)
•TL1 circuits now have names (like CTC circuits).
•You can use TL1 to change the name of any circuit, TL1-created or CTC-created.
•Low order (LO) tunnels and LO aggregation point circuits created via TL1 are now recognized and displayed in CTC.
•You can use TL1 to add cross-connects to a CTC-created circuit.
•You can edit TL1 circuits using CTC. (No need for upgrading the circuit first.)
•Circuit "upgrade" and "downgrade" functions have been removed.
•You can merge two or more CTC circuits into a single CTC circuit. (Circuit Merge and Circuit Reconfigure.)
•"ACTIVE" circuits are now called "DISCOVERED."
•"INCOMPLETE" circuits are now called "PARTIAL."
•"UPGRADABLE" circuits are now called "DISCOVERED_TL1."
•"INCOMPLETE_UPGRADABLE circuits are now called "PARTIAL_TL1."
Software Upgrade
Software upgrades from Release 1.x to 5.0.x are supported.
Cisco Transport Manager
Cisco Transport Manager (CTM) Release 5.0 supports the ONS 15600 Release 5.0.
High Level Functional Differences
The following high level support is added for Release 5.0.x.
Enhanced State Model Support
In Release 5.0.x, equipment, ports and circuits support additional Primary and Secondary states. Messages of the form REPT^DBCHG^MSG contain new Enhanced State Model (ESM) states in Release 5.0.x. The following are the new SONET states in ESM, as defined for TL1.
Table 2 describes each service state of the entity described by the Primary State (PST) and a Primary State Qualifier (PSTQ).
Table 2 Primary States
PST_PSTQ Values Description
In Service - Normal
Out of Service - Autonomous
Out of Service - Autonomous and Management
Out of Service - Management
Table 3 describes the Secondary States (SST). This parameter provides additional information pertaining to PST and PSTQ.
Table 3 Secondary States
SST Values Description
Mismatch of Equipment Alarm
Software Download
Remote Monitoring
TL1 support for Remote Monitoring (RMON) is added in Release 5.0.x for GIGE ports on the ASAP card.
Additional Functional Support
The following additional high level features add functional support in Release 5.0.x TL1.
•TL1 BLSR DRI support is added in Release 5.0.x.
•The TL1 Circuit Name feature is added in Release 5.0.x.
•DLT-CRS-PATH commands support a new parameter `CMDMDE' (Command Mode)
•TL1 support for SNMP configuration is added in Release 5.0.x.
•Port naming support is added in Release 5.0.x.
•TL1 support for static routes is added in Release 5.0.x.
•Fractional ATAG support added to Alarms/Events.
•TL1 PCA support added n Release 5.0.x.
•Support for Embedded Spaces in trace strings is added for the ONS 15600 in Release 5.0.x.
•Setting of revertive time regardless of revertiverness behavior is added in Release 5.0.x.
•Mixed timing mode support is added (combining both BITS and Line Timing Source).
•In addition to BITS-OUT functionality, SYNC-BITS1 and SYNT-BITS support are added for Release 5.0.x.
•Release 5.0.x TL1 adds an ADD/RMOVE parameter to the ED-CRS-STS command.
•"Free form" strings support is added: nested quoted strings can be part of a RTRV command response.
TL1 Command Changes
New Commands
The following commands were added in Release 5.0.x
Command Syntax Changes
The syntax of the following commands is changed in Release 5.0.x.
ALW-MSG-ALL syntax:
Is changed to:
DLT-CRS-<PATH> syntax:
Is changed to:
ED-CRS-<PATH> syntax:
Is changed to:
ED-<OCN_TYPE> syntax:
Is changed to:
ED-<OCN_TYPE>:[<TID>]:<aid>:<CTAG>:: :[DCC=<dcc>,][AREA=<area>,][SYNCMSG=<syncmsg>,][SENDDUS=<senddus>,][SFBER=<sfber>,][SDBER=<sdber>,][MODE=<mode>,][MUX=<mux>,][SOAK=<soak>,][OSPF=<ospf>,][LDCC=<ldcc>,][NAME=<name>,][CMDMDE=<cmdmde>,][EXPTRC=<exptrc>,][TRC=<trc>,][TRCMODE=<trcmode>,][TRCFROMAT=<trcfromat>,][ADMSSM=<admssm>,][SENDDUSFF=<senddusff>]:<pst>,[<sst>];
ED-BITS syntax:
ED-BITS:[<TID>]:<aid>:<CTAG>:::[LINECDE=<linecde>,][FMT=<fmt>,] [SYNCMSG=<syncmsg>,] [:<pst>];
Is changed to:
ED-CRS-STS-PATH syntax:
Is changed to:
ED-<MOD_PATH> syntax:
Is changed to:
ENT-CRS-<STS_PATH> syntax:
Is changed to:
ENT-EQPT syntax:
Is changed to:
EX-SW-<OCN_BLSR> syntax:
Is changed to:
RTRV-CRS syntax:
Is changed to:
TL1 Response Changes
The following TL1 responses have changed in Release 5.0.x.
RTRV-BITS response:
Is changed to:
RTRV-CRS response:
Is changed to:
RTRV-CRS-<PATH> response:
Is changed to:
RTRV-FFP-<OCN_TYPE> reponse:
Is changed to:
RTRV-INV reponse:
Is changed to:
RTRV-EQPT response:
Is changed to:
RTRV-OCN-TYPE response:
Is changed to:
Autonomous Message Changes
The following autonomous message syntax has changed.
REPT^DBCHG syntax:
Is changed to:
TL1 ENUM Changes
The following section, including Table 4 through Table 29, highlights ENUM items changed (added or removed) for Release 5.0.x, by ENUM type.
BITS_FAC is used in the following commands:
CCT is used in the following commands:
Table 6 CRS_TYPE enum items added in Release 5.0.x
Enum Name Enum Value
CRS_TYPE is used in the following commands:
Table 7 DETECTION_GUARD_TIMER enum items added in Release 5.0.x
Enum Name Enum Value
DETECTION_GUARD_TIMER is used in the following commands:
Table 8 DRINODE enum items added in Release 5.0.x
Enum Name Enum Value
DRINODE is used in the following commands:
Table 9 DRITYPE enum items added in Release 5.0.x
Enum Name Enum Value
DRITYPE is used in the following commands:
Table 10 ENCAP enum items added in Release 5.0.x
Enum Name Enum Value
ENCAP is used in the following commands:
Table 11 EQPT_TYPE enum items added in Release 5.0.x
Enum Name Enum Value
EQPT_TYPE is used in the following commands:
Table 12 CONST_MODE enum used instead of ENV_CRTL_MODE
Enum Name Enum Value
Table 13 FCS enum items added in Release 5.0.x
Enum Name Enum Value
FCS is used in the following commands:
Table 14 MOD1PAYLOAD enum items added in Release 5.0.x
Enum Name Enum Value
MOD1PAYLOAD is used in the following commands:
Table 15 MOD2 enum items added in Release 5.0.x
Enum Name Enum Value
MOD2 is used in the following commands:
Table 16 MOD2RMON enum items added in Release 5.0.x
Enum Name Enum Value
MOD2RMON is used in the following commands:
Table 17 MOD_PATH enum items added in Release 5.0.x
Enum Name Enum Value
MOD_PATH is used in the following commands:
Table 18 NE_SECU_MODE enum items added in Release 5.0.x
Enum Name Enum Value
NE_SECU_MODE is used in the following commands:
Table 19 PAYLOAD enum items added in Release 5.0.x
Enum Name Enum Value
PAYLOAD is used in the following commands:
Table 20 PRODUCT_TYPE enum items added in Release 5.0.x
Enum Name Enum Value
PRODUCT_TYPE is used in the following commands:
Table 21 PST_PSTQ enum items added in Release 5.0.x
Enum Name Enum Value
PST_PSTQ is used in the following commands:
Table 22 RECOVERY_GUARD_TIMER enum items added in Release 5.0.x
Enum Name Enum Value
RECOVERY_GUARD_TIMER is used in the following commands:
Table 23 SAMPLE_TYPE enum items added in Release 5.0.x
Enum Name Enum Value
SAMPLE_TYPE is used in the following commands:
Table 24 SNMP_VERSION enum items added in Release 5.0.x
Enum Name Enum Value
SNMP_VERSION is used in the following commands:
Table 25 SST enum items added in Release 5.0.x
Enum Name Enum Value
SST is used in the following commands:
Table 26 STARTUP_TYPE enum items added in Release 5.0.x
Enum Name Enum Value
STARTUP_TYPE is used in the following commands:
Table 27 TMPER enum items added in Release 5.0.x
Enum Name Enum Value
TMPER is used in the following commands:
VALIDITY is used in the following commands:
Table 29 VERIFICATION_GUARD_TIMER enum items added in Release 5.0.x
Enum Name Enum Value
VERIFICATION_GUARD_TIMER is used in the following commands:
Related Documentation
Release-Specific Documents
•Release Notes for the Cisco ONS 15600, Release 5.0.2
•Release Notes for the Cisco ONS 15454 SDH, Release 5.0.4
•Release Notes for the Cisco ONS 15327, Release 5.0.4
•Release Notes for the Cisco ONS 15454, Release 5.0.4
•Release Notes for the Cisco ONS 15310-CL, Release 5.0.4
•Cisco ONS 15600 Software Upgrade Guide, Release 5.0.2
Platform-Specific Documents
•Cisco ONS 15600 Procedure Guide
Provides installation, turn up, test, and maintenance procedures
•Cisco ONS 15600 Reference Manual
Provides technical reference information for SONET/SDH cards, nodes, and networks
•Cisco ONS 15600 Troubleshooting Guide
Provides a list of SONET alarms and troubleshooting procedures, general troubleshooting information, and hardware replacement procedures
•Cisco ONS SONET TL1 Command Guide
Provides a comprehensive list of TL1 commands
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to firstname.lastname@example.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
Contacting TAC by Telephone
If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
P1 and P2 level problems are defined as follows:
•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2007, Cisco Systems, Inc.
All rights reserved.


text:
The Turkish minister of foreign trade welcomed a small group of people to Istanbul.
Elsa of ELLE Belgium having a drink at the Vogue party.
Nesli of Styleseeking Zurich waiting on Istiklal Avenue.
Beautiful apartment building called Galatan Dogan.
Gizem who is an intern at ELLE Turkey and was kind of our helpdesk during our stay.
Adorable Seda from ELLE Turkey and Pelayo from katelovesme.
From second left to right: lovely Isin Gormus, Isik Simsek and Melis Agazat from ELLE Turkey.
Natalia and her brother Pelayo
Seda taking a picture of me with her lomo camera.
Elif and Irem, two sisters who spent my last day in Istanbul with me.


text:
Every few weeks, the wife and I like to have someone else break the eggs. Breakfast out may not be as glamorous as dinner reservations, but it's a lot cheaper, and the slice of humanity is always more interesting.
During a recent omelet pilgrimage before the last arctic cold front came in, I noticed a little old lady by herself in one of the booths. She had on a winter sweater, jeans that had neatly ironed creases, and a pair of what we used to call "deck shoes" — blue sneakers with white eyelets and laces.
She had brought her book with her. People can make themselves look harried and self-important if they have a newspaper in front of them at a diner. But somebody that goes to the trouble of bringing along a book is a reader, not a poser.
She was having her breakfast and morning coffee. She sipped with two slightly palsied hands wrapped around the mug. She had placed her spoon across the book to keep it open so she could read uninterrupted.
You never know what you will learn from a book. For reasons I can't quite figure out, I became entranced recently with "Shakespeare's Pub" by Peter Brown (St. Martin's Press, $26.99). It's a history of London as seen through the story of one of its oldest pubs, the George Inn. Or the Saint George Inn before the pub was re-named during one of England's anti-Catholic rants, something the Brits have to do every few decades since Henry VIII. The most recent outbreak was during the visit of Pope Benedict XVI in September 2010.
"Shakespeare's Pub" was interesting stuff, especially in that the author is quite certain that Shakespeare never had anything to do with the place. But it makes a good book title.
One of my favorite stories in the book is when Brown recalls the time a body was discovered near the pub. It was the year 1817, and the body was of a beggar in his mid-60s. He had no identification, and the authorities were unable to determine any possible cause of death.
So it was officially recorded: "died by the visitation of God."
Try to write that down today on a government document and the American Civil Liberties Union — the Westboro Baptist Church of the secular arm — will have a rant as good as any in merry olde England.
Brown writes that "at the start of the Industrial Revolution the way we regarded time itself had changed from something cyclical and constantly renewed to a straight line marked by numbers, timetables and schedules."
It reminded me of time as it is still taught by the liturgical year, the seasons moving one to the other, matched in Faith and matched in nature. It is striking how much the faith reflects the world as it is, rather than the artificial constructs man has tried to dump on the world to understand it.
Faith builds on nature and never contradicts it. That's part of the mystery of the Incarnation. And "died by the visitation of God" makes more and more sense when a person thinks about it.
We survived the arctic blast that recently visited the Midwest from Canada. An old Hoosier forecast is if the sun shines bright in the Midwest on a January day, the world will freeze solid in the evening. Hoosiers know that because they know that you learn the weather not by a timeline, but by living it season to season.
Just as a person learns the Faith.
It was time to finish that omelet and head home. I asked the waitress for the old woman's check, and we paid for her breakfast. We left before she could find out.
Going by those creased jeans and deck shoes, she might have gotten mad at us.
But it's the least we could do for a reader.
Robert P. Lockwood writes from Pennsylvania.
Copyright © 1996-2019 Our Sunday Visitor, Inc.


text:
CAMBRIDGE, Mass. - MIT's Wyatt Ubellacker has had quite the impressive year: the senior helped lead the men's swimming and diving team to its fifth consecutive New England Women's and Men's Athletic Conference (NEWMAC) title, while also being named the NEWMAC Swimmer of the Year for his five first place finishes, three of which were individual, and four conference records.
A month later, he was named the Swimmer of the Year at the 2013 NCAA Division III Swimming and Diving Championships after claiming two national titles and a national record, leading the Engineers to a third place finish, the highest they have ever placed in the team rankings before. And this past summer, he became the first MIT swimmer to compete in the U.S. Olympic Trials, finishing in 21st place in the 50-meter freestyle. All while maintaining a 4.9 GPA.
As MIT, the NEWMAC and its member institutions participate in the second annual Division III Week, which concludes on Sunday, April 14, Ubellacker reflected upon his decision to attend MIT and be a Division III student-athlete.
He said it was an easy choice when it came to picking a college. "I knew I wanted to swim in college and I knew MIT had a really good academic reputation," he said. "It wasn't that tough of a decision, to be honest. I applied early and got in early and once I got in, I was dead set."
When asked what it means to be a Division III student-athlete, Ubellacker said that it "gives me a good break to unwind from school work, and have something to focus on besides problem sets. I find that I am much more productive after working out, and I can't imagine my college experience without athletics and swimming."
For Ubellacker, who will be graduating in June with a degree in mechanical engineering and starting a job with robotics company Vecna the following month, his favorite memory was watching the underclassmen learn and grow. "When I came in as a freshman, I really looked up to the seniors and, every year, it is great to see how enthused each class are and how much talent they have. It is great to see what I feel is a reflection of what I was like as a freshman."
Acting head coach Samantha Pitter, who has been working with the team for the past five years, said that she was blown away by Ubellacker's performance at NCAAs, attributing his achievements to a new-found confidence. "I think all of his hard work over the four years finally paid off," she said. "Trials gave Wyatt a taste of that next level and when he saw it and was part of it, he wanted more. It gave him the drive to do well this year and that experience is really what is behind all of his success."
At last year's NCAA Championships, Ubellacker walked away with two thirds and one seventh place finish. When asked if he had trained differently to achieve the level of success this year, he said a number of factors had been changed.
"Starting last summer, I did less heavy lifting and focused more on reps than weight," he said. "In the water, we worked more on technique, starts and turns and underwaters. I went in every morning to work on that. It is hard to tell what really made the biggest difference. I feel like everything contributed a little and added up."
Pitter said that she had changed practices for everyone this season, not just Ubellacker. "We tried something different for Olympic Trials that really seemed to work so we brought it to the season," she said. "We changed the cycles of training and did more aerobic-based stuff, which gave him endurance for the fly which was missing before."
Going into NCAAs this year, the Georgetown, Ky. native had one simple goal: to get best times in all of his events, which he achieved. Being the national champion in two of his events was just icing on top of the cake.
"I definitely thought I had a good chance of winning, but I just wanted to focus on my events," he said.
Pitter said that her first goal was for the team to get third. "My agenda from day one was to take down the top teams," she said. "My goals for Wyatt individually were to get best times, which he did. I knew it was possible that he could win ... I knew as soon as I saw his morning swim in the 50 free that no one was going to be able to touch him ... it was pretty clear he was the man to beat in the pool."
In the 50 free on the first day of competition at NCAAs, Ubellacker was seeded third with his time of 20.01 from NEWMACs. In the preliminary session that morning, he raced to a 19.51, breaking the 20 second mark for the first time in his career, placing him in first going into finals. That evening, he held on to his first place seeding with a time of 19.81.
The next day, Ubellacker moved up from seventh to first in prelims of the 100-yard butterfly with his time of 47.34, breaking the 13-year-old national record of 47.43. At finals, he won his second national title after touching first in 47.41. On the final day, he touched second in the 100-yard freestyle in 44.01 after going 43.92 that morning. Throughout the week, Ubellacker was also part of the 200-yard medley relay that finished first and the 200-yard freestyle relay that placed second.
With the season officially over, Pitter said she was incredibly proud of all Ubellacker had accomplished throughout his time at MIT. "The biggest thing for me has been watching him grow, not only as a swimmer but as a student-athlete, and really become a leader for the team and someone for them to look up to," she said. "He has been a true backbone of this program for the past four years."
So what is next for Ubellacker? He isn't going to walk away from the pool and hang up his goggles just yet.
"I'm not ready to be done," he said. "I feel like I haven't reached my peak and I'm not quite ready to stop until I reach my full potential. So I'm going to keep training. I am going to compete in the World Championship Trials at the end of June (in Indianapolis) ... it kind of hit me all of a sudden at the end of the meet that, from now on, I'm going to be swimming by myself. Training with a team is a whole different experience. I'm really going to miss that."


text:
I am wild crazy over chandeliers. One of the happiest days in my own home design history was when this chandelier was installed in my living room. I love this style of chandelier – it's one of my favorites.
Another good day was when I bought this chandelier from a friend who was redesigning her house – taking it from English to totally Swedish. This was in her bedroom and this Italian style light fixture didn't mix with her new Swedish design. Good thing for me! This style is another favorite of mine and has gained greatly in popularity these past few years.
There are few makers of chandeliers who get it right – consistently - and Julie Neill is one of them. Her designs are based on the classics, yet she adds a youthful twist to each fixture. I would have trouble picking one favorite – I love so many of her chandeliers! She designs and crafts all her light fixtures from start to finish in her own New Orleans workshop. Everything is customized to the job. In fact, all the designs in her portfolio started life as a custom commission. Julie is so creative – she began her career as a painter, then moved on to painting things for the home instead of canvases, next she tried interior design which lead her to this very successful career in 2000. Her retail shop is on Magazine Street – one of America's best streets for antiquing. If you've never gone antiquing on Magazine Street – you should include it on your Bucket List.
Besides designing chandeliers, Julie also creates sconces, furniture, and accessories. New Orleans heavily influences her designs – a crown is an oft used element in her romantic and decidedly feminine creations. Julie's stamina and creativity is boundless. Not only does she run her own successful retail store and workshop, she has employees and two children to watch over, and she maintains a charming 1800s shotgun house. I first met Julie on the blogs – of course – where she writes The Bayou Contessa, a beautiful glimpse into New Orleans design. If you are planning a trip to NOLA, a stop at Julie Neill is a must. If you are in the market for a chandelier, give Julie a call. She works with each client to create the exact fixture they desire.
Julie has just redesigned her web site and it's gorgeous! Here is a small sampling of her product. Each fixture can be customized to any specification. Her range is from traditional to contemporary. All the finishes are hand applied and painted.
Here is the glamorous Cinderella chandelier in a dining room.
This bedroom's chandelier is a more contemporary design mixed with traditional elements. Leontine Linens.
Julie designed this lantern with matching sconces for Tobi Fairley's Richmond Symphony Designer House. I love this room!!!! The red of the chandelier is picked up in the trim of the table.
Seen in this month's Elle Décor magazine – this fixture is one of the many Italian styled chandeliers that Julie makes. Shown is the entry hall of Jane Scott Hodges' house in Kentucky. Jane Scott is the founder of the fabulous Leontine Linens Note: the pillows are by BVIZ. Just beautiful!
The Sheldon Chandelier is reflected in this trumeau.
One of her most popular designs is the graceful and romantic Elizabeth chandelier. Named after this client, the chandelier is great for lower ceilings – as it is more horizontal than vertical. This couple commissioned several chandeliers from Julie and an article on their house appeared in the New Orleans Home magazine. Shown here.
For their dining room, Julie created the Denise chandelier. I love the combination of the chairs and the bench around the square table.
The Ingrid fixture is another popular design – more contemporary than Julie's crystal chandeliers. Room designed by Jeffery McCollough for the Acadiana Symphony Decorator Showhouse.
These charming Beatrice hanging fixtures and Beatrice sconces designed by Julie made the cover of House and Home.
Julie Neill's shop on Magazine Street is filled with her creations – chandeliers and sconces - along with the pieces of furniture from her line.
Here's a close up of two chandeliers from the shop, one French and one Italian! The trumeau and the cabinet under it are also in Julie's line.
Julie's team hard at work – the chandeliers have to first be constructed, then hand finished, before they are able to be installed on the sales floor. Each fixture goes through a long and laborious process to be ready for sale.
o, you ask – what is the giveaway?!??!?!? I have been bursting at the seams keeping this a secret for the past month or two. One day Julie emailed me asking if I would like to host a giveaway of her product. What a silly question – of course I would love to!!!! I thought maybe she would be donating a sconce, or a small accessory from her shop. You can imagine how my mouth dropped to the floor when she so generously offered a CHANDELIER for a giveaway!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Yes!!! An original, Julie Neill Chandelier will be given away to one lucky winner!!! Oh My Gosh!!!!! Unreal. Seriously, y'all, I am SO excited about this. It's the biggest giveaway ever here on Cote de Texas and we've had some great giveaways in the past. Read on for the deets (details to those of you over 30.)
The winner will have their choice of either a traditional or contemporary fixture. The ELIZABETH Chandelier is the traditional choice. I was so excited about this choice because this fixture is one of my all time favorites of Julie's. Can you believe this giveaway? Seriously!!!!!! You can win this!!!!! Retail value is $3,800.00
Or, if you are a more contemporary person, the Ingrid Chandelier will be the second choice for the winner. The mirror and table are also from Julie Neill. Retail value for this chandelier is $3,495.00
Are you an Elizabeth or an Ingrid Person????
Go right now to the Julie Neill Design web site www.julieneill.com and look under the Chandelier, Sconces, or Lanterns sections. Pick out your favorite item that is for sale. Come back here and leave me a comment on what your favorite item is and explain why you like it so much. That's it!!!!
You have until Saturday night at 11:59 p.m. The contest closes at that time. One person will win either the Elizabeth or Ingrid chandelier – their choice. BE SURE TO LEAVE YOUR EMAIL ADDRESS IF YOU POST ANONYMOUSLY!! And please, only one comment per person!!!
Your choice: The Elizabeth
Or the Ingrid!!! Good luck to everyone!!!
And finally - a huge, huge thank you, kiss and hug to Julie Neill for her generous giveaway. From the bottom of my heart, thank you Julie!!!!!
Becky Vizard and Ann Connelly at Watkins Culver this Thursday and Friday!!
NOTE: Houstonians – I wanted to let you know that BVIZ and Ann Connelly Fine Art are back in town at Watkins Culver this Thursday and Friday. Becky Vizard has the most wonderful pillows – many of which have been featured on the pages of the best design magazines (including the Elle Décor picture previously shown!!) Her good friend, Ann, has a wonderful art gallery in New Orleans. To read all about these two talented ladies from Louisiana, go HERE. For details on when and where, call 713-529-0597.


text:
Pets, Pets, Pets
by Joanne Anderson
Get out your October calendar. Next month is packed with interesting pet events; many adoption fairs or fund raisers for worthy animal organizations. Here is just a sampling:
"Barktoberfest" dog/cat adoption event at the shelter- 300 Horseblock Rd., Brookhaven. A low-cost vaccine clinic for Town residents' pets will also take place between 1 and 3 p.m. During "Barktoberfest", there will be a petting zoo, face painting for kids, and demos by the Suffolk County Police K-9 Unit. From 2 to 3 p.m., participants can enter their own dogs in contests including World Class Wagging, Musical Sit and more. An adoption bonus will be given for any dog or cat adopted this day. For more info, call 631-286- 4940 or visit www.brookhaven.org/ animalshelter.
Neuter Clinic at Basic Pet Care, Rt. 109, Lindenhurst. It's really free. At the first clinic in March with the help of 7 vets and many volunteers, we altered over 80 cats in one day. Call the numbers above or 631-664-5481 to reserve a spot for one or more ferals in your care.
Oyster Bay Town Shelter
677-5784) Miller Pl. Syosset has a selection of dogs and cats, especially young kittens, seeking loving homes. "Ivory" #794 the young yellow Lab mix has the typical exuberance of her breed. She needs someone to guide her with training. Meanwhile this orange longhaired kitten #823 is doing his feline impression of the painting "The Scream". Can't you just hear him meowing "Take Me Home"? See more photos on the shelter's Petfinder site.


text:
Rumored $250 Quad-core phone from TCL
With the upcoming MT6589 phones, and TCL as confirmed to be one of the first adopters of the said chip; we can expect that by December 15, a new quad-core phone from TCL will say hi to us.
Rumored price, just at $256 and for the full specs; read on.
TCL will start using the MT6589 quad-core chip with this one. TCL has been famous for its SHARK series, those waterproof dual-core Android phones such as the TCL S600 and TCL S800.
Geeks from China expects a 4 to 4.5-inches quad-core baby from TCL that will have a 720p display in resolution. Android 4.1 JellyBean has been sounding as well, in line with that to boast is a fully pledged 2GB of RAM.
With this in the know, it is expected that other companies will start with that setting point in terms of pricing and specs.


text:
Cross Country Hosts Alumni; Football Scrimmagesby Jim Amidon • August 26, 2006 Share:
The largest alumni turnout in history made the 2006 Charlie Finch Memorial Alumni Cross Country Meet a huge success. The Finch Memorial marks the start of the season for the Red Pack — a Wabash cross country team with high hopes for a much improved season.
Click here to see photos from the event, now available as high resolution downloads.
The Wabash football team dodged rain showers on a hot and humid day for the annual Red vs. White Scrimmage. Click here to see photos from the scrimmage.
President Pat White was the ceremonial starter for the 2006 Charlie Finch Memorial event that included nearly 60 competitors, among them Dean of Admissions Steve Klein and professors Greg Redding and Brian Tucker. Deans Gary Phillips and Tom Bambrey were also on hand to cheer the Little Giants and returning alumni, who were honored at a picnic following the meet.
Former All-Conference performer Adam White '98 was easily the most impressive competitor. White, who helped Wabash to a third place finish at the 1995 national championships, ran away from his former teammate Roger Busch to win the four-mile run.
"It's hard to run when you're crying," said White after the race as he remembered another former teammate, Jeremy Wright '96, an Army Ranger killed in Afghanistan two years ago. The death of his own parents in a plane crash and Wright's tragic death inspired White to take up competitive racing again. The results of his training showed at the finish of the race when he clearly had enough energy to repeat the four-mile run.
Busch, assistant director of annual giving at Wabash and volunteer assistant cross country coach, ran to second place and finished about 100 meters behind White.
After Busch crossed the line, a sea of current Little Giants finished impressively, led by senior Dennis Frazee and Dustin Beck. Sam Compton-Craig, Geoff Lambert, Matt Maher, and Ben Bly all finished in strong fashion, in spite of what they called "a brutal workout Thursday."
The Red Pack's season continues next Saturday, September 2, when the Little Giants host the Wabash Hokum Karem at 10:30 a.m.


text:
HARTSVILLE, S.C.- The Cobra men's tennis team lost a tough match to a Top 50 team in the nation on Friday, West Alabama (No. 45) in men's collegiate tennis action. Coker dropped the match 5-4.
The Cobras had three solid victories from the No. 2, No. 3 and No. 4 spots in singles play. James Corfield (New Zealand) picked up a hard fought three set match at No. 2 singles with scores of 6-4, 3-6, 6-4, while Manel Estruga (Spain) and Guillermo Aylon (Spain) picked up straight set wins at No. 3 and No. 4 with scores of 6-3, 6-2 and 7-6, 6-4 respectively.
The Cobras other victory of the match came at No. 1 doubles where Corfield and Aylon won 8-5.
Coker is back on the courts on Saturday when they travel to Misenheimer, N.C. to take on Conference Carolinas foe Pfeiffer University starting at 1:00 p.m.
Coker (4) lost to West Alabama (5) (#45 National ITA ranking, #12 ITA South Region)
#1 Leonardo Lima (CC) lost to Santiago Lopez (WA) 6-2, 3-6, 6-4
#2 James Corfield (CC) def. Juan Tellez (WA) 6-4, 3-6, 6-4
#3 Manel Estruga (CC) def. Lucas Nunez (WA) 6-3, 6-2
#4 Guillermo Aylon (CC) def. Wade Covington (WA) 7-6, 6-4
#5 Juan Vallejo (CC) lost to Lucas Cruz (WA) 6-4, 6-4
#6 Evan Schreiner (CC) lost to Kike Ruiz (WA) 6-2, 6-0
#1 Corfield/Aylon (CC) def. Nunes/Ruiz (WA) 8-5
#2 Lima/Lamberigts (CC) lost to Tellez/Cruz (WA) 8-4
#3 Estruga/Vallejo (CC) lost to Lopez/Covington (WA) 8-5


text:
carlbobBudding Enthusiast
Content Count16
Last visited
About carlbob
Profile Information
Ford Model
UK/Ireland Location
You lucky people the cars are looking fantastic
They were just like that with me. In the end i showed them the price i could get it online and told them to beat it. Suprisingly they did, but the service i have had has been awful and now i still dont know if im or when i am getting the car. Goid mind to cancel it and go elsewhere.
Rang Allen Ford earlier to enquire about my car as i have heard nothing. Got told that they dont have any details of my order!!! They are gonna get back to me tomorrow. P**sed off is a mild understatement.
[quote name=jmbrown91' timestamp='13 1813846' post='238863] Takes around 1-2 weeks to get from the factory to dealer, then a couple of days to PDI (which takes no time at all in reality) and tax the car... Which dealer did you get your fiesta from carlbob? Allen ford at riverside. Not greatly impressed with them so far.
Thanks, will be ringing them tomorrow, really hope it's Friday as I booked the day off work.
I'm waiting for my candy blue titanium x 125 with 17's. They told me it was in stock when I ordered it, then last week told me it was being built on the 7th feb. will be very very annoyed if it ain't there on Friday. Anyone know how long it should take to get to the dealers. Again it's my first ever new car and I wanted it on release day, just one of the things on my To Do list.
carlbob started following 17" Rims On Fiesta 2013, What Tyre Size ? and 2013 Fiesta Arriving 1St March!
I agree that makes no sense, I have noticed on the e-brochure it says the kit is available as individual pieces.
Sounds like my dealer, just interested in selling. They tried offering me a fully dressed titanium, but I like the half leather heated seats and keyless entry amongst other things. Will find out soon what I end up with.
Images 9 and 10 on this link is what I was talking about in previous post http://www.autoexpress.co.uk/ford/fiesta
Also read the last paragraph of this review http://www.autoexpress.co.uk/ford/fiesta
The annoying thing is the dealers don't even know why it's not available on tit x. If it wasn't for the decent discount they offered I would have not ordered that model. I'm hoping that I can get the dress up kit at a later date. Having scoured the Internet I see a candy blue fiesta with the 17's and the sill parts of the bodykit, I think it was on autocar.co.uk, this would be great if I could just get this on my car.
17" Rims On Fiesta 2013, What Tyre Size ?
carlbob replied to NQbbe's topic in Wheels & TyresI have upgraded my titanium x to 17's , the order confirmation says 205/40/17. Think 35 would be too harsh ride for this model but maybe good for zetec s.
I have to say the titsnium x is highly spec'd ad standard, i have also gone gor the 17's and driver assistance pack. Not bothered with satnav and prefer the half leather. But i did want the dress up kit. Seems odd you cant choose it on ford website either, but i have noticed picture doesnt change if you choose titanium or titanium x, where i know the wheels are different.
Yes they did try to sell me a fully dressed titanium but i wanted the x. I have looked at lots of pics on the internet and some seem to show a sill kit without front and rear spoilers, doesnt state that this is the titanium x spec though.
Newbie - Titanium X Question ?
carlbob posted a topic in Ford Fiesta ClubHi everybody, I have ordered a 1.0 125ps titanium x in candy blue, the dealer is telling me that the full dress up kit is not available on this model. Is this because there is already a bodykit on the sills? The dealer is not sure why and I havent found one on sale yet to see it.


text:
Woman at Trump rally gives reporter kind note
Woman at Trump rally gives reporter kind note
(Hearst) —
A CNN reporter tweeted a photograph of a note he received from a woman at a Trump rally in Tallahassee on Tuesday.
The woman addressed the note to "media covering Trump." In it, she said she was horrified at the hostility shown to journalists covering Trump rallies.
A gift for reporters at Trump's rally in Tallahassee from a very kind lady: pic.twitter.com/YkPteKu3Qv
— Jeremy Diamond (@JDiamond1) October 25, 2016
The unidentified woman finished by thanking journalists and producers for doing their jobs with "professionalism and courage."
"A free, open, functioning press is essential to our democracy," she said.