text:
Difference between revisions of "PSWEpisode632"
Wheat Loaf (talk | contribs)
Mike Shema (talk | contribs)
|Line 21:
|Line 21:
== Announcements ==
== Announcements ==
Welcome to our round table discussion on DevOps and Security Applications. Quick reminder for our listeners, every week we record Application Security Weekly, featuring Mike
Welcome to our round table discussion on DevOps and Security Applications. Quick reminder for our listeners, every week we record Application Security Weekly, featuring Mike , John Kinsella and Matt Alderman covering all of the latest application security news and research along with interviews with some of the best and brightest minds in appsec today. You can subscribe to Application Security Weekly, and all of our shows on the Security Weekly network by visiting securityweekly.com/subscribe.
== Description ==
== Description ==
Revision as of 06:35, 19 December 2019
Recorded December 19, 2019 at G-Unit Studios in Rhode Island!
- 1 Introduction
- 2 Segment 1: DevOps and Securing Applications
- 3 Segment 2: Security vs. Compliance
- 4 Segment 3: Security History - Lessons from the past
First up in this episode is our round table discussion on DevOps and Securing Applications where we'll cover how to navigate the wide variety of options for securing modern applications and the processes used to build and deploy software today. Next up we debate one of information security's long-standing debates: security versus compliance in what is sure to be a lively round table discussion. The final segment in this episode assembles a panel of experts to discuss the history of security and what we can learn from the past. Stay tuned for all that and more on this very special episode of Paul's Security Weekly.
Episode Audio
Segment 1: DevOps and Securing Applications
Welcome to our round table discussion on DevOps and Security Applications. Quick reminder for our listeners, every week we record Application Security Weekly, featuring Mike Shema, John Kinsella and Matt Alderman covering all of the latest application security news and research along with interviews with some of the best and brightest minds in appsec today. You can subscribe to Application Security Weekly, and all of our shows on the Security Weekly network by visiting securityweekly.com/subscribe.
- Given that DevOps is a process and its execution requires many different tools, how do we get started "doing DevOps"?
- What about DevOps allows us to produce more secure applications?
- What concepts inside of DevOps do most people lose site of?
- What are the major challenges involved in taking an application from traditional development to DevOps?
- What are some of the best approaches to making an application more resilient to threats, specifically:
- Static Code Analysis
- Software Compisition Analysis
- Software Testing
- Web Application Scanning
- To ORM or not to ORM?
- Which services do you implement yourself vs. using a cloud service?
- How do I choose the best secrets vault?
- What should I use an orchestrator for and what should I not use an orchestrator for?
- How do I build a secure API for my app?
- Thoughts on GraphQL vs. REST security implications?
✶Click Headshots for Full Bio✶
- Puma Scan (commercial) and open source (http://github.com/pumasecurity/puma-scan)
Segment 2: Security vs. Compliance
Welcome to our round table discussion on security versus compliance. Quick reminder for our listeners, every week we record Security and Compliance Weekly, featuring Jeff Man, Josh Marpet and Scott Lyons covering all of the latest compliance and security news along with interviews with folks close to challenges and success stories in compliance today. You can subscribe to Security and Compliance Weekly, and all of our shows on the Security Weekly network, by visiting securityweekly.com/subscribe.
It was once said that if Security and Compliance were in a relationship the status would be "It's Complicated". This discussion will aim to help you understand this relationship and how it can be beneficial or a mere distraction to an organization's overall security posture.
- Define "Secure" and "Compliant".
- Does compliance merely raise awareness about security shortcomings?
- What is the relationship between Security and Compliance?
- Being Secure and being Compliant are mere points in time, how can we best develop a process to ensure we are always striving to a secure and compliant state?
- How does Security impact and/or influence Compliance?
- How does Compliance impact and/or influence Security?
- How do you balance these extremes: "We will be Secure and ignore compliance" vs. "We will be compliant but ignore security"
✶Click Headshots for Full Bio✶
Segment 3: Security History - Lessons from the past
Welcome to our security history roundtable discussion. I'd like to remind our listeners to subscribe to the Security Weekly mailing list where you'll receive information about our upcoming webcasts, virtual training and Security Weekly appearances at conferences throughout the year. You can subscribe to our mailing list, and all of the podcasts on the Security Weekly network, by visiting securityweekly.com/subscribe.
The history of security can be traced back to a variety of different sources. The amount of articles on the topic is dizzying. Most will cite names of early phone phreaks, Kevin Mitnick, Kevin Poulsen, Steve Jobs, Steve Wozniak and quickly transition to many other more recent "hacks" or breaches. Our goal is to not review the history of hacking. This is the history of security. We've carefully chosen key events and research to discuss the very beginnings of security, and their impact and lessons for today's ever-evolving security landscape.
- 1903 - Nevil Maskelyne Hacked A Wireless Telegraph Demonstration - The second it became physically possible to hack into something, somebody did it. That somebody's name was Nevil Maskleyne, history's first hacker, and he was around a lot earlier than you might expect. He hacked into a live telegraph demonstration in 1903. - Dot-dash-diss: The gentleman hacker's 1903 lulz
- 1939-1940 - Breaking the Enigma cipher - BOMBE was the name of an electro-mechanical machine, developed during WWII by Alan Turing and Gordon Welchman, whilst working as codebreakers at Bletchley Park. It was used to help breaking the German Enigma codes and was (partly) based on the so-called BOMBA, an earlier machine developed by Polish mathematicians in 1938. From 1943 onwards, an improved version of the British BOMBE was built in the US by the US Navy and — independently — by the US Army.
- 1966 - The World's First Computer Password? It Was Useless Too - Fernando Corbató implements passwords on CTSS on an IBM 7090. CTSS may also have been the first system to experience a data breach. One day in 1966, a software bug jumbled up the system's welcome message and its master password file so that anyone who logged in was presented with the entire list of CTSS passwords. But that's not the good story. Twenty-five years after the fact, Allan Scherr, a Ph.D. researcher at MIT in the early '60s, came clean about the earliest documented case of password theft. In the spring of 1962, Scherr was looking for a way to bump up his usage time on CTSS. He had been allotted four hours per week, but it wasn't nearly enough time to run the detailed performance simulations he'd designed for the new computer system. So he simply printed out all of the passwords stored on the system.
- 1969 - RABBITS Was Probably The First Computer Virus: 1969 - The first computer virus in history may have been a program called RABBITS. Nobody knows who made it, and nobody knows why, but whoever it was brought the University of Washington Computer Center down. It was a tiny, inconspicuous program that made copies of itself—breeding, as its name suggested, like rabbits. In 1969, someone installed it onto a computer at the university and let it run. The program made two copies of itself, and then each of those copies made copies until the computer overloaded and stopped working.
- 1971 - Creeper and Reaper - Creeper was an experimental computer program written by Bob Thomas at BBN in 1971.[2] Its original iteration was designed to move between DEC PDP-10 mainframe computers running the TENEX operating system using the ARPANET, with a later version by Ray Tomlinson designed to copy itself between computers rather than simply move.[3] This self-replicating version of Creeper is generally accepted to be the first computer worm. The program was not actively malicious software as it caused no damage to data, the only effect being a message it output to the teletype reading "I'm the creeper: catch me if you can". Reaper (program) was a similar program created by Ray Tomlinson to move across the ARPANET and delete the self-replicating Creeper.
- 1973 - Oral History of Robert Metcalfe - What had happened was a couple of high school students hacked into the Arpanet through one of the early TIPs. A TIP [Terminal IMP] was a way to dial into a Telnet program so you could then log in to any of the computers on the Arpanet. Imagine that! And some high school students, as I recall they were probably in Los Angeles around UCLA, somewhere like that, managed to find out the phone number. No one was keeping it a secret. Acoustically coupled modems were the big thing in those days, and so these high school kids got into some of the computers and did some mischief. They caught my attention, so I wrote this 602 RFC saying "Look out! Trouble!"
- RFC 602 The Stockings Were Hung by the Chimney with Care - Individual sites, used to physical limitations on machine access, have not yet taken sufficient precautions toward securing their systems against unauthorized remote use. For example, many people still use passwords which are easy to guess: their fist names, their initials, their host name spelled backwards, a string of characters which are easy to type in sequence (e.g. ZXCVBNM).
- 1986 - A Brief History of Cyber Crime - In 1986 the systems administrator at the Lawrence Berkeley National Laboratory, Clifford Stoll, noted certain irregularities in accounting data. Inventing the first digital forensic techniques, he determined that an unauthorized user was hacking into his computer network. Stoll used what is called a "honey pot tactic," which lures a hacker back into a network until enough data can be collected to track the intrusion to its source. Stoll's effort paid off with the eventual arrest of Markus Hess and a number of others located in West Germany, who were stealing and selling military information, passwords and other data to the KGB.
- 1988 - THE HISTORY OF CYBERSECURITY - a man named Robert Morris had an idea: he wanted to gauge the size of the internet. To do this, he wrote a program designed to propagate across networks, infiltrate Unix terminals using a known bug, and then copy itself. This last instruction proved to be a mistake. The Morris worm replicated so aggressively that the early internet slowed to a crawl, causing untold damage. The worm had effects that lasted beyond an internet slowdown. For one thing, Robert Morris became the first person successfully charged under the Computer Fraud and Abuse Act (although this ended happily for him – he's currently a tenured professor at MIT). More importantly, this act also led to the formation of the Computer Emergency Response Team (the precursor to US-CERT), which functions as a nonprofit research center for systemic issues that might affect the internet as a whole. Morris Worm
- 1987 -History Of Antivirus - At the end of 1987 there was big movement in the antivirus industry, with the founding of the, now world famous, McAfee company (now owned by Intel) and the creation of first set of antivirus products. G Data Software was reportedly the first to market that year with 'Ultimate Virus Killer 2000', shortly followed by McAfee's 'Virus Scan'.
- 1984-1986 - The History and Evolution of Intrusion Detection - Between 1984 and 1986, Dorothy Denning and Peter Neumann researched and developed the first model of a real-time IDS. This prototype was named the Intrusion Detection Expert System (IDES). This IDES was initially a rule-based expert system trained to detect known malicious activity. This same system has been refined and enhanced to form what is known today as the Next-Generation Intrusion Detection Expert System (NIDES) (Further reading: https://www.symantec.com/connect/articles/evolution-intrusion-detection-systems and Is IPS a feature or a product?)
- 1980-1994 - Who Invented The Firewall? - William Cheswick and Steven Bellovin, who literally wrote the book on firewalls in 1994 while at AT&T Bell Labs, say they didn't invent the firewall, either -- they built a circuit-level gateway and packet filtering technology. Most security experts trace the firewall's roots, back to work done at Digital Equipment Corp. in the late 1980s by Jeff Mogul, Brian Reid, and Paul Vixie, starting with the gatekeeper.dec.com gateway, as well as to Mogul's "screend" technology. DEC SEAL, which was shipped in 1992, was the first commercial firewall and included proxies developed by Ranum. "DEC SEAL was interesting because it had a part number and a manual and a corporation behind it," Ranum says.
✶Click Headshots for Full Bio✶
Security is Not Deterministic. Tell Your CISO to get over it; Yeah, they want to know, "are we secure?" "Did that next gen $2M PoS help us get secure?" "I hear that new AI thing I don't understand will fix our security problems?"
No. The answer is no. There is no 'Yes' answer to security. Tell your CISO and the Board: No matter WTF you do, you will never be secure. Ain't gonna happen.
SANE PEOPLE: "Are you or your organization ever going to be 100% secure?" (Crazies need no respond.) of course not.
Simply, there is no such thing as secure (100% free of any threat or chance of violation) nor is there any chance of 0% security even if you have your computers turned off. Hard copy is still a threat.
So, what does Winn mean?
I want everyone to get over this binary concept of absolutism. There is no perfect security (100%) and there is no 100% absesses of security (0%).
Therefore, all security must be somewhere on the spectrum of >0 and < 100. Even you MBAs get that, eh? :)

subset: commoncrawl


text:
At stage 3 of the Prestashop Installation, I enter the DB details which I know to be correct, and I receive the error:
Database server was not found. Please verify the login, password, and database server name fields.
The server is localhost, and I have verified the database name and username. Why can Prestashop not find the server?
This occurs when choosing InnoDB and MyIsam.
If I change the server from localhost to the public hostname I receive the same error.


text:
Crater Holden and Uzboi Vallis
These images, taken by the High Resolution Stereo Camera (HRSC) on board ESA's Mars Express spacecraft, show the outlet channel of the Uzboi Vallis system into Crater Holden on Mars.
The HRSC obtained these images during orbit 511 with a ground resolution of approximately 45 metres per pixel. The scenes show the region of Noachis Terra, over an area centred at about 26º South and 325º East.
The valley of Uzboi Vallis begins in the region of Argyre Planitia and crosses the southern highlands in the direction of the northern lowlands. It connects several large impact craters, such as the 140 kilometre-wide Crater Holden seen in the main image.
Due to a layer of haze close to the base of Holden, the area within the crater appears lighter coloured and slightly less detailed than the surrounding area.
A small, dark dune-field can be seen in the eastern half of the crater floor. It indicates the role of wind in the morphological evolution of Crater Holden.
The terrain within Crater Holden is the result of a long and varied evolution. The numerous smaller craters inside Holden indicate that the crater is old.
Many smaller craters on the floor of Holden are covered with sediments, which were deposited after the formation of these craters and indicate that they are older than the unfilled small craters.
The central mount of Holden is partly hidden, because it has also been covered by sediments. The rim of the crater has been cut by gullies, which sometimes form small valley networks.
In the southern part of Crater Holden, well-preserved 'alluvial fans' (fan-shaped deposits of water-transported material) are visible at the end of some gullies (see close-up left).
In other parts of the crater rim, the alluvial fans are less distinct and partly covered by younger 'talus' cones (cone-shaped piles of debris from rock falls at the base of slopes).
Uzboi Vallis enters Crater Holden from the south-west. Two distinct phases of its development can be seen. In the first phase, a valley was formed up to 20 kilometres wide.
Later, a smaller channel was cut into the valley floor. The end of the small channel has been blocked by a landslide from the crater rim (see close-up 2).
The deepest parts of the valley floor are more than 1600 metres below the surrounding area. The numerous valleys at the flanks of Uzboi Vallis indicate that water probably played a major role in the formation and evolution of this region. Most of the valleys have been covered by younger sediments, indicating they have been inactive in recent geological time.
The colour images were processed using the HRSC nadir (vertical view) and three colour channels. The perspective views were calculated from the digital terrain model derived from the stereo channels.
The 3D anaglyph image was created from the nadir channel and one of the stereo channels. Stereoscopic glasses are needed to view the 3D image. Image resolution has been decreased for use on the internet.
For more information on Mars Express HRSC images, you might like to read our updated 'Frequently Asked Questions'.


text: In conjunction with This is the ENDD and at the invitation of event presenter Mathew Dryhurst, Aaron David Ross of Gatekeeper has compiled a mixtape exploring the vape aesthetic. The resulting work is available to stream and download below, along with a statement by ADR. The compilation will be given a public premier tomorrow at Beverly's (21 Essex St New York, NY 10002), following the conclusion of the conference, at 630pm.


text:
*This product is now available during lock down. Please note delivery may be delayed as courier companies are only using road freight at this time.
Add 50 superfoods plus a supreme mix of essential vitamins and minerals, probiotics and fibre into every day with the brand new Super Scoop Range.
Size: 360g tub (30 X 12g Servings)
Flavour: Cacao- Adult
Super Scoop has a concentration of high-quality phytonutrients in a convenient powder form, specially designed to help you lead a more plant-based lifestyle. It's low in sugar and calories but still super tasty, and dissolves easily in everything from yoghurt to cookie batter, milk or water. I designed Super Scoop to be your all-in-one, simple solution to taking in a pile of nutrients that we all need each day, without any harmful, synthetic additives, colourants or preservatives.
This is what you can expect from every Super Scoop serving:
✔ 50 superfoods
✔100% vegan-friendly
✔ 100 million CPU probiotic
✔ Gluten-free
✔ Fat-free
✔ High in fibre
✔ Dairy-free probiotic
✔ Non-GMO
✔ Low in calories
✔ Preservative-free
Shop everything you need to bounce with me at home! Get your rebounder, accessories, and workouts online.
Hey, new moms. Did you know you can bounce back after baby at home and regain your strength and fitness? It's simple with a Lisa Raleigh rebounder.
Sneak 50 superfoods into your and your kiddies' diets with my latest Super Scoop range.
Sign up to our newsletter and receive my latest deliciously healthy recipes, daily motivation, general fitspiration, plus keep up to date with our exciting monthly prizes & giveaways.


text:
Have an account?
Need an account?Create an account
Table Of Contents
Release Notes for Cisco ONS 15454 SDH Release 4.1
CWDM and DWDM GBIC Compatibility with G1000-4 Cards and G1K-4 Cards
Active Cross Connect or TCCi/2 Card Removal
SONET and SDH Card Compatibility
Maintenance and Administration
Changed Default Alarm Severities
DDTS # CSCdv10824: Netscape Plugins Directory
Database Restore on an MS-SPRing (or BLSR)
Active Cross Connect or TCCi/2 Card Removal
Resolved Caveats for Release 4.1
Maintenance and Administration
New Features and Functionality
New Software Features and Functionality
ML-Series Resilient Packet Ring
Protect Threshold Crossing Alarms
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Release Notes for Cisco ONS 15454 SDH Release 4.1
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.
October, 2007
Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15454 SDH multiplexer. For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to the "Release 4.1 and 4.5" version of the of the Cisco ONS 15454 SDH Installation and Operations Guide, and Cisco ONS 15454 SDH Troubleshooting and Reference Guide. For the most current version of the Release Notes for Cisco ONS 15454 SDH Release 4.1, 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 4.1
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 15454 SDH Release 4.1 since the production of the Cisco ONS 15454 SDH System Software CD for Release 4.1.
The following changes have been added to the release notes for Release 4.1
Changes to Caveats
The following caveat has been added to the release notes.
Review the notes listed below before deploying the ONS 15454 SDH. 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 # CSCsh41324
When running release 4.1.4, if a circuit is created within CTC and if that circuit is retrieved via TL1, all looks as expected. However, after the software is upgraded to release 6 and latter, the circuit retrive does not show the same value as was before. For example FAC-4-1 changes to FAC-4-0. Workaround is to delete and recreate the circuit within CTC.
CWDM and DWDM GBIC Compatibility with G1000-4 Cards and G1K-4 Cards
Existing G1000-4 cards are expected to support CWDM and DWDM GBICs, but final qualification testing was not complete at press time. The online version of the 4.1 user documentation and release notes will be updated to reflect the final qualification status of CWDM and DWDM GBICs on the G1000-4 card, when this information is available.
Existing G1K-4 cards do not support CWDM or DWDM GBICs.
G1K-4 cards with the CLEI code of WM5IRWPCAA (manufactured after August 2003) are expected to support CWDM and DWDM GBICs, but final qualification testing was not complete at press time. The online version of the 4.1 user documentation and release notes will be updated to reflect the final qualification status of CWDM and DWDM GBICs on the G1K-4 card with the CLEI code of WM5IRWPCAA, when this information is available.
Note Operating temperature of the DWDM GBICs is -5 degrees C to 40 degrees C.
DDTS # CSCdw92634
SDH DS3-i and E3 electrical cards only support a VC4 J1 trace string setting for all VC4s together. You cannot set the J1 byte for individual VC4s. This issue is a limitation of hardware.
Note VC3 J1 strings can be set individually, but the optical cards cannot monitor the VC3 J1 string.
DDTS # CSCdy00622
Very rarely, an Equipment Failure Alarm can occur on an externally timed TCC+ or TCC-I card after a reset. If this occurs, BITS will be displayed as good for one TCC, but bad for the other. If the issue occurs on the standby TCC, a second reset could clear the problem. If the issue occurs on the active TCC, the card must be replaced. This issue is closed, as it does not occur with TCC2, and is otherwise very rare.
DDTS # CSCdw14501
Interconnection Equipment failure alarms may be generated at 55 degrees C, and 72 volts. When the operating environment is at 55 degrees C and 72 volts, interconnection equipment failure alarms for the following cards can occur:
The alarms could potentially occur on any of these boards, as well: OC48AS, GigE, OC192 or OC192LR. This issue will be resolved in a future release.
DDTS # CSCdw50903
E1-14 boards with second source components can incur bit errors under extreme environmental conditions. When these boards operate under voltage and temperature stress conditions and a temperature ramp rate of 1 degree per minute, the boards could exhibit dribbling bit errors at high temperatures: BER = 5.5e-6. To avoid this, you must apply the temperature ramp rate at 0.5 degree per minute. This ramp rate complies with the NEBS standard; however, this issue will be revisited in a future release.
Line Cards
DDTS # CSCeb19055
On the subsequent 3 slots occupied by the protect FMEC, MEA is not set when a mismatched IO card is inserted. This issue will be resolved in a future release.
DDTS # CSCea52722
With DS3-I cards in a 1:2 protection group, when the protect card is active and in the WTR condition, removing another working card from the protection group clears the WTR condition. To work around this issue, remove the working card from the protection group when the protect card is in the standby state. This issue will be resolved in a future release.
DDTS # CSCea60715
In a 1+1 configuration, traffic may be lost upon reset of both working and protect STM64 cards. If you reset the protect card and then, before the protect card completes rebooting, reset the working card, the traffic does not switch to protect but remains on working. If the working card is removed during the time the protect is still coming up, the traffic does not switch to working and is lost. To avoid this issue, wait for the protect to fully come up before pulling the work card. This issue will be resolved in a future release.
DDTS # CSCeb39337
Very rarely, DS3i can lose traffic on an active XC-VXL pull. To avoid this issue, side switch the XC-VXL cards. This issue will be resolved in a future release.
DDTS # CSCeb34655
Very rarely, E1-42 takes greater than 2 second hits on an active XC-VXL pull. To avoid this issue, side switch the XC-VXL cards. This issue will be resolved in a future release.
DDTS # CSCeb43397
Rarely, E1-42 cards may incur a greater than 60 ms traffic disruption during protection switches. This can occur when you pull the active working E1-42 card. This issue will be resolved in a future release.
DDTS # CSCeb34326
Rarely, an E1-42 card can go into continual autoreset. This can occur after the E1-42 card is inserted, or following a node power cycle. Hard reset the E1-42 by removing and re-inserting it into the chassis to stop this cycle. This issue will be resolved in a future release.
Ethernet Polarity Detection
The TCC2 does not support Ethernet polarity detection. The TCC+ and TCCI both support this feature. If your Ethernet connection has the incorrect polarity (this can only occur with cables that have the receive wire pairs flipped), the TCC+/I will work, but the TCC2 will not. In this event, a standing condition, "LAN Connection Polarity Reverse Detected" (COND-LAN-POL-REV), will be raised (a notification will appear on the LCD, and there will be an alarm raised). This issue will most likely be seen during an upgrade or initial node deployment. To correct the situation, ensure that your Ethernet cable has the correct mapping of the wire wrap pins. For Ethernet pin mappings, consult the "DLP-A 21 Install LAN Wires on the Backplane" procedure in the user documentation.
Active Cross Connect or TCCi/2 Card Removal
Active cross connect or TCCi/2 cards should not be removed. If the active cross connect or TCCi/2 card must be removed, to minimize network interruption you can first perform an XC10G (or XCVXL) side switch and then remove the card once it is in standby, or you can perform a lockout on all circuits that originate from the node whose active cross connect or active TCCi/2 will be removed (performing a lockout on all spans will also accomplish the same goal). No lockout is necessary for switches initiated through CTC.
Caution If you mistakenly remove an active cross connect or TCCi/2 card and you subsequently lose traffic on some interface cards, you may need to physically reset these cards if they fail to regain traffic.
DDTS # CSCdz21738
A cross connect card switch can result in double traffic hits or a long hit for a E1-VC12 circuit. This issue is under investigation.
DDTS # CSCdy65482
On the AIC-i card, a volume adjustment on the receive value of a four-wire orderwire circuit will be displayed as the negative of its actual value. To work around this issue, enter the negative of the value you actually want for the receive value. For example, adjust the receive value on CTC to -2 dbm for a gain of 2 dbm. This issue will be resolved in a future release.
SONET and SDH Card Compatibility
Tables 1, 2, and 3 list the cards that are compatible for the ONS 15454 SONET and ONS 15454 SDH platforms. All other cards are platform specific.
Table 1 SDH Data Cards that are SONET Compatible
Product Name Description
4 port Gigabit Ethernet Module - need GBICs
12 port 10/100BT Ethernet Module
2 port Gigabit Ethernet Module - need GBICs
10/100 Mbps Ethernet card, 12 ports, RJ-45, L2/L3 switching, SDH/ETSI system, includes console cable
1000 Mbps Ethernet card, 2 SFP slots, L2/L3 switching, SDH/ETSI system
Table 2 SONET Data Cards that are SDH Compatible
Product Name Description
4 Port Gigabit Ethernet
10/100BT, 12 circuit, compatible w/ XC, XCVT and XC10G
Gigabit Ethernet, 2 circuit, GBIC - G
10/100 Mbps Ethernet card, 12 ports, RJ-45, L2/L3 switching, SONET/ANSI system, includes console cable
1000 Mbps Ethernet card, 2 SFP slots, L2/L3 switching, SONET/ANSI system
Table 3 Miscellaneous Compatible Products
Product Name Description
Empty slot Filler Panel
1000Base-LX, SM or MM, standardized for 15454/327
1000Base-SX, MM, standardized for 15454/327
Bag of 15 90 degree fiber retention boots
1000BASE, SX, short-reach, multimode, small form factor pluggable (SFP), LC connectors
1000BASE, LX, long-reach, single mode, SFP, LC connectors
Cable, console, ML-Series, RJ-11 plug to RJ-45 jack, 22Ý/55.9cm long, SONET/ANSI system
Cable, console, ML-Series, RJ-11 plug to RJ-45 jack, 22Ý/55.9cm long, SDH/ETSI system
DDTS # CSCdw44431
Cisco ONS 15454 optical cards are not provisioned for particular path labels (C2 bytes). Consequently, they cannot raise a PLM condition. However, the ONS 15454 electrical card that terminates traffic ensures that the C2 byte is correct for the type of traffic carried. If the C2 byte is incorrect, this card raises a PLM condition that is reported against the optical port of ingress. An optical card will not raise a PLM against traffic that passes through a node, though it will appear to raise a PLM against traffic with the wrong C2 byte that is terminated on an electrical card within the node. It is not known at this time when or if this issue will be resolved.
Note Optical cards do ensure that the C2 byte is nonzero (Equipped), and will raise a UNEQ condition if the C2 byte is 0 (Unequipped).
DDTS # CSCdw80652
When one traffic card in a DS3i 1:N protection group is reset, and then another card is reset, there will be a loss of traffic on the second card, after the first card completes its reset, lasting until the second card completes its reset. This only occurs when the protect card tries to handle the traffic of a card that is resetting, and that card is carrying traffic because when it reset the protect card was carrying traffic for another card. This loss of traffic occurs because the protect card attempts to set its relays to handle the traffic of the working card, but the relays on the working card are also set to carry the traffic, and since the card is resetting, no software is running to switch its relays. This issue most frequently presents itself when testing a double-failure scenario: resetting two cards in a protection group. Wait until the first card completes its reset sequence before resetting the second card to prevent this problem. Configuring cards in 1:1 instead of 1:N protection should also avoid the problem. This issue will not be resolved.
DDTS # CSCdw57215
In a configuration with STM16 Any Slot cards and an VC4-8c circuit, provisioned between G1000-4 cards with traffic going over the STM16 span, extracting the G1000-4 card at one end of the VC4-8c circuit before deleting the circuit can result in a traffic hit on all existing SDH circuits defined over that same span. There are no issues if the circuit is deleted prior to the removing the G1000-4 card.
XC10G Boot Process
If you install a new XC10G card to the node and it fails to boot, remove the card and reinsert it. If the card still fails to boot, return it using the RMA procedure. This issue will be resolved in future hardware.
Jitter Performance with XC10G
During testing with the XC10G, jitter generation above 0.10 UI p-p related to temperature gradient testing has been observed. This effect is not expected to be seen under standard operating conditions. Changes are being investigated to improve jitter performance in a subsequent version of the XC10G cross connect card. DDTS numbers related to this issue include CSCdv50357, CSCdv63567, CSCdv68418, CSCdv68441, CSCdv68389, CSCdv59621, and CSCdv73402.
E Series and G Series Cards
Do not use the repair circuit option with provisioned stitched Ethernet circuits. It is not known at this time when or if this issue will be resolved.
Single-card EtherSwitch
Each E100/E1000 card can be configured as a single-card EtherSwitch configuration to allow VC4-4c of bandwidth to be dropped at each card. The following scenarios for provisioning are available:
VC4-2c, VC4-2c
VC4-2c, VC4, VC4
When configuring scenario 3, the VC4-2c must be provisioned before either of the VC4 circuits.
Multicard EtherSwitch
When deleting and recreating Ethernet circuits that have different sizes, you must delete all VC4 circuits provisioned to the EtherSwitch before you create the new circuit scenario. (See the preceding "Single-card EtherSwitch" section on page 6 for details on the proper order of circuit creation.) Enable front ports so that the VLANs for the ports are carried by the largest circuit first. A safe approach is to enable the front port before you create any circuits and then retain the front port VLAN assignment afterwards. If you break the rules when creating a circuit, or if you have to delete circuits and recreate them again, delete all circuits and start over with the largest first.
DDTS # CSCeb56287
When an ML-series circuit's state is provisioned from In-Service (IS) to Out-of-Service (OOS), and then back to IS, data traffic does not recover. To avoid this issue, prior to changing the state from IS, set the POS port to shut down on the CLI. After the state is changed back to IS from OOS, set the POS port to "no shutdown." This issue will be resolved in Release 4.6.
DDTS # CSCeb25778
When a MAC-SA is seen for the first time, it is learned, but may age out in less than 5 minutes. If the same MAC-SA is seen again before the first ages out, the entry will age out after 5 minutes, as expected. This issue will not be resolved.
DDTS # CSCeb11930
The POS shutdown command will raise PLM-P on the far end for a VC3 circuit in an SDH node. This occurs on all ML-series cards in nodes running Release 4.0 or 4.1. This issue will be resolved in Release 4.6.
DDTS # CSCin43669
Timer expiration can cause a system crash when you attempt to remove 250 Shared Packet Ring (SPR) subinterfaces using the "no int spr1" command, while Cisco Discovery Protocol (CDP) is also enabled. To avoid this issue, either turn off CDP, issue the command, and then turn CDP back on; or remove the SPR subinterfaces explicitly. This issue will not be resolved.
DDTS # CSCea36829
The broadcast packet count is always 0 for the SPR interface. The ML100 and ML1000 hardware does not support counting broadcast packets. This issue will not be resolved.
DDTS # CSCeb21996
When the POS interface is removed from SPR due to a defect, while SPR is configured in immediate mode, the defect type may not be reported. This only occurs if the defect is set and clears in less then 50 ms.
DDTS # CSCdy31775
Packets discarded due to output queue congestion are not included in any discard count. This occurs under either of the following conditions:
•Traffic on ML-series cards between Ethernet and SDH ports, with oversubscription of available circuit bandwidth configured, leading to output queue congestion.
•Traffic from SDH to Ethernet, with oversubscription of the available Ethernet bandwidth.
This issue will be resolved in a future release.
DDTS # CSCdz49700
ML-series cards do not appear in the Cisco Discovery Protocol (CDP) adjacencies and do not participate in the Spanning-Tree Protocol. All packets are counted as multicast.
The ML-series cards always forward Dynamic Trunking protocol (DTP) packets between connected devices. If DTP is enabled on connected devices (which might be the default), DTP might negotiate parameters, such as ISL, that are not supported by the ML-series cards. All packets on a link negotiated to use ISL are always counted as multicast packets by the ML-series card, and STP and CDP packets are bridged between connected devices using ISL without being processed. To avoid this issue, disable DTP and ISL on connected devices. This functionality is as designed.
DDTS # CSCdz68649
Under certain conditions, the flow-control status may indicate that flow control is functioning, when it is not. Flow-control on the ML-series cards only functions when a port-level policer is configured. A port-level policer is a policer on the default and only class of an input policy-map. Flow-control also only functions to limit the source rate to the configured policer discard rate, it does not prevent packet discards due to output queue congestion.
Therefore, if a port-level policer is not configured, or if output queue congestion is occurring, policing does not function. However, it might still mistakenly display as enabled under these conditions. To avoid this issue, configure a port-level policer and prevent output queue congestion. This issue will be resolved in a future release.
DDTS # CSCdz69700
Issuing a shutdown/no shutdown command sequence on an ML1000 port clears the counters. This is a normal part of the startup process and there are no plans to change this functionality.
DDTS # CSCdz87944
Error messages indicating "Stuck Ucode" and "MDA_INTERNAL_ERROR" occur when routing 64-byte VLAN tagged frames at line rate. For VLANs, use bridging instead of routing. This issue will be resolved in a future release.
DDTS # CSCea01675
Packets without an 802.1q VLAN tag are classified as COS 0. This issue will be resolved in a future release.
DDTS # CSCea11742
When a circuit between two ML POS ports is provisioned OOS, one of the ports might erroneously report TPTFAIL. This issue exists for both ML100T-12 and ML1000-2 cards. If this occurs, open a console window to each ML card and configure the POS port to shutdown. This issue will be resolved in Release 5.0.
DDTS # CSCea20962
No warning is displayed when applying OOS to ML drop ports on the circuit provisioning window. This issue will be resolved in Release 5.0.
DDTS # CSCea26847
An unexpected card reload can occur when a card is configured to route IP-Multicast traffic and subsequently sends IP-Multicast frames larger than 1649 bytes. To prevent this, avoid routing IP-Multicast frames larger than 1649 bytes. This issue is under investigation.
DDTS # CSCin29274
When configuring the same static route over two or more interfaces, use the following command:
ip route a-prefix a-networkmask a.b.c.d
Where a.b.c.d is the address of the outgoing gateway, or, similarly, use the command:
ip route vrf vrf-name
Do not try to configure this type of static route using only the interface instead of the address of the outgoing gateway in Release 4.0. This issue will be resolved in a future release.
DDTS # CSCin32057
If no BGP session comes up when VRF is configured and all interfaces have VRF enabled ensure that at least one IP interface (without VRF) is configured and add an IP loopback interface on each node.
DDTS # CSCin35960
POS ingress classification based on IP precedence does not match the packets when inbound policy map classifying based on IP precedence is applied to the POS interface, which is configured for HDLC or PPP encapsulation. To avoid this issue, use LEX encapsulation (default) or, at the Ethernet ingress point, mark the COS based on an IP precedence classification, then classify based on the COS during POS ingress. This issue will be resolved in a future release.
DDTS # CSCdy55437
The maximum MAC Address Learn Rate for the ML-Series cards is 1300 MAC addresses per second. This number varies based on the ML-Series control and forwarding plane loads. If the forwarding and control planes are heavily loaded, the maximum MAC Address Learn Rate could be as low as 100 MAC addresses per second. To correct a situation where an ML-Series card has stopped learning MAC addresses, reduce the load on these cards. This load limit is by design.
DDTS # CSCdy47284
Oversize frames are not supported on ML100 Fast Ethernet ports. Oversize frames cause egress traffic to incur CRC, line, and fragment errors on these ports. To avoid this issue, do not send jumbo packets to ML far end ports. This is as designed.
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 # CSCeb63327
The High Temperature Alarm is raised at 50 degrees Celsius. This is, however, not optimal on an Itemp rated system, which can tolerate up to 65 degrees Celsius. To work around this issue, the alarm can be downgraded or suppressed, but note that this will result in no temperature alarm provided at all. Alternatively, Cisco TAC provides a method of retrieving the temperature from the node, which can thus be monitored periodically for temperature-related problems. This issue will be resolved in Release 4.6, and in a future maintenance release of Release 4.1.
DDTS # CSCeb39359
When changing NE timing from extern/mix to Line timing, a Transient IEF alarm may be reported against the standby XC10G. This issue will be resolved in a future release.
DDTS # CSCeb35648
A circuit in the AINS state on STM1-8/OC3-8 may transition to IS state even when signals in both directions have alarms. This issue will be resolved in a future release.
DDTS # CSCeb12032
When upgrading the software from Release 4.0 to Release 4.1, a TU-AIS will be reported on the span card for a one way VC12 E1-42 circuit. The alarm cannot be cleared once it is detected. This issue will be resolved in a future release.
DDTS # CSCeb09356
The CTC card level provisioning pane allows a different range of values for the PSC-W, PSC-S, and PSC-R thresholds from the range allowed in the defaults provisioning window. At the CTC card view for an OC-192 card, CTC will allow any values for the PSC-W, PSC-S, and PSC-R. When provisioning these same values using the CTC node view defaults pane, the range is restricted from 0 to 600. This issue will be resolved in Release 4.6.
DDTS # CSCeb24771
A static route may be lost if SOCKS proxy server mode is turned on and then off on the node. If the workstation was communicating with the NE using static routing it will lose connectivity to the NE. If this happens, re-enter the static route. This issue will be resolved in Release 6.0.
DDTS # CSCea93638
Path level alarms are displayed on the CTC conditions pane for deleted circuits. This issue may occur on any circuit deletion case. The conditions may be cleared by a TCC side switch. This issue will be resolved in Release 5.0.
Changed Default Alarm Severities
The following alarm severities have changed for Release 4.1.
Table 4 Changed Alarm Severities
Alarm New Severity
DDTS # CSCea81001
When a fault condition exists against a circuit or port that is in the OOS-MT or OOS-AINS state (or when you are using the "Suppress Alarms" check box on the CTC Alarm Behavior pane), the alarm condition is not assigned a reference number. If you were to place the circuit or port in service at this time, in the absence of the reference number, the CTC alarm pane would display the condition with a time stamp indicating an alleged, but incorrect, time that the autonomous notification was issued. Clicking the CTC alarm "Synchronize" button at this stage will correct the alarm time stamp. There is no way to remedy the lack of reference number. This issue will be resolved in Release 6.0.
DDTS # CSCea78364
Simultaneous failure of working and protect cards in 1:N protection groups may not be alarmed as service affecting. This can occur when the working card of the protection group has been removed from the chassis, and the protect card of the protection group is subsequently issued a Manual Reset. Since the working and protect facilities are impaired, the Improper removal alarm should clear and be reissued as a Critical and service affecting condition. This issue will be resolved in Release 6.0.
DDTS # CSCea61887
Terminal loopback is provisionable even if the card is in transponder mode.
To see this, in the provisioning tab for a G1000 or G1K-4 card pick a pair of ports and set them to transpond with each other. The condition also holds true by picking one port and setting it to transpond with itself (one-port unidirectional). Once the transponder setting is provisioned, go to the Maintenance tab and attempt to provision terminal loopback on any of the ports that were previously provisioned for transponder functionality. CTC allows terminal loopback to be provisioned even though the setting has no effect due to the fact that the ports are performing transponder functions. If terminal loopback is truly intended, you should remove the transponder settings. A warning stating that terminal loopback has no effect if transponders are present will be displayed in Release 4.6.
DDTS # CSCeb20996
While using the orderwire capability of the AIC-I, you must not input a station number with less than 4 digits. If you enter, for example, 123, CTC will display 0123; however, you will not be able to ring the node by dialing either *123, or *0123. This issue will be resolved in Release 4.6.
DDTS # CSCea13593
DRI configuration rules require limits on multiple drops. However, in an ONS 15454 SDH DRI topology, a unidirectional circuit can be created from one ring to another with two drops at the destination node. This issue will be resolved in Release 5.0.
DDTS # CSCdz90733
PCA traffic can remain down after restoring the incorrect database and then restoring the correct database to the node. To avoid this issue, exercise care in database restoration. If you accidentally restore the wrong database, first restore the correct database and check to see if all traffic has returned. If PCA traffic is still down, you may need to remove and reinsert a fiber or perform a cross connect card reset. This issue will be resolved in Release 5.0.
DDTS # CSCdz84149
If a user is logged into CTC as a superuser (or other higher level security type), and then another superuser changes the first user's security level to "retrieve" (or another lower level security type) without first logging the user out, the lower level user is then still able to perform some actions authorized only for the original login security level. For example, a "provisioning" level user demoted to "retrieve" level in this manner can still provision and edit MS-SPRings (BLSRs) while logged into the current session, though the same user may no longer provision DCCs. To ensure that a user's level is changed completely, the superuser must log the user out prior to changing the security level. This issue is under investigation.
DDTS # CSCdz90753
In the Maintenance > Cross Connect Resource Pane, the VT matrix port detail is inconsistent with the general VT matrix data. This can occur when a 1+1 protection scheme is in place. To avoid confusion, note that the VT matrix data counts the VTs for both the working and protect card, while the detail data counts the VTs only for the working card. This issue is under investigation.
DDTS # CSCdz62367
When replacing a failed working E1-42 card in a 1:1 or 1:N protection configuration with the protect card carrying the switched traffic, bit errors, less than 50ms in duration, are possible on the activated protection card. This issue is currently under investigation.
DDTS # CSCdy10030
CVs are not positively adjusted after exiting a UAS state. When a transition has been made from counting UAS, at least 10 seconds of non-SES must be counted to exit UAS. There are no plans to resolve this issue at this time.
DDTS # CSCdx35561
CTC is unable to communicate with an ONS 15454 SDH that is connected via an Ethernet craft port. CTC does, however, communicate over an SDCC link with an ONS 15454 SDH that is Ethernet connected, yielding a slow connection. This situation occurs when multiple nodes are on a single Ethernet segment and the nodes have different values for any of the following features:
•Enable OSPF on the LAN
•Enable Firewall
•Craft Access Only
When any of these features are enabled, the proxy ARP service on the node is also disabled. The ONS 15454 SDH proxy ARP service assumes that all nodes are participating in the service.
This situation can also occur immediately after the aforementioned features are enabled. Other hosts on the Ethernet segment (for example, the subnet router) may retain incorrect ARP settings for the ONS 15454 SDHs.
To avoid this issue, all nodes on the same Ethernet segment must have the same values for Enable OSPF on the LAN, Enable Firewall, and Craft Access Only. If any of these values have changed recently, it may be necessary to allow connected hosts (such as the subnet router) to expire their ARP entries.
You can avoid waiting for the ARP entries to expire on their own by removing the SDCC links from the affected ONS 15454 SDH nodes. This will disconnect them for the purposes of the proxy ARP service and the nodes should become directly accessible over the Ethernet. Network settings on the nodes can then be provisioned as desired, after which the SDCC can be restored.
This issue will not be resolved.
DDTS # CSCdy11012
When the topology host is connected to multiple OSPF areas, but CTC is launched on a node that is connected to fewer areas, the topology host appears in CTC, and all nodes appear in the network view, but some nodes remain disconnected. This can occur when the CTC host does not have routing information to connect to the disconnected nodes. (This can happen, for example, if automatic host detection was used to connect the CTC workstation to the initial node.)
CTC will be able to contact the topology host to learn about all the nodes in all the OSPF areas, but will be unable to contact any nodes that are not in the OSPF areas used by the launch node. Therefore, some nodes will remain disconnected in the CTC network view.
To work around this issue, if no firewall enabled, then the network configuration of the CTC host can be changed to allow CTC to see all nodes in the network. The launch node must be on its own subnet to prevent network partitioning, and craft access must not be enabled. The CTC host must be provisioned with an address on the same subnet as the initial node (but this address must not conflict with any other node in the network), and with the default gateway of the initial node. CTC will now be able to contact all nodes in the network.
If a firewall is enabled on any node in the network, then CTC will be unable to contact nodes outside of the initial OSPF areas. This issue will not be resolved.
DDTS # CSCdy57891
An LOP-P alarm can be inadvertently cleared by an LOS that is raised and cleared. On STM-N cards, when an LOP condition and an LOS condition are both present on the input, an LOS will be raised. However, upon clearing the LOS with the LOP still present, the LOP alarm is not raised. An AIS-P condition will be visible. This issue will be resolved in a future release.
DDTS # CSCdw38283
If a node has one good BITS reference and is running in a normal state, and you configure a second BITS reference, then reconfigure the second reference within 30 seconds of applying the first configuration, the node will enter FAST START SYNC mode. To avoid this problem, wait a minute before configuring the second reference a second time. This issue is a hardware limitation, and there are no current plans to resolve it.
DDTS # CSCdw23208
The following table summarizes B1, B2, and B3 error count reporting for SDH optical cards. Note that not all reporting is done according to ITU specifications. In particular, ITU specifies error counts for B1 and B3 as the number of blocks with errors (refer to ITU-T G.826 for paths and ITU-T G.829 for RS and MS).
Table 0-5 Error Count Reporting
ITU Specification
STM16 trunk
DDTS # CSCdw82689
After creating 509 VLANs and provisioning many Ethernet circuits, Ethernet circuit provisioning can become very slow, or possibly fail. Ethernet traffic may also incur an outage of a few minutes. To avoid this problem, delete any VLANs that are created but not used, and do not recreate them. There is no resolution planned for this issue.
DDTS # CSCdv10824: Netscape Plugins Directory
If you use CTC, JRE, and the Netscape browser with a Microsoft Windows platform, you must ensure that any new installation of Netscape uses the same Netscape directory as the previous installation did, if such an installation existed. If you install Netscape using a different path for the plugins directory, you will need to reinstall JRE so that it can detect the new directory.
"Are you sure" Prompts
Whenever a proposed change occurs, the "Are you sure" dialog box appears to warn the user that the action can change existing provisioning states or can cause traffic disruptions.
MS-SPRing Functionality
DDTS # CSCeb40296
IPPM counts for PCA (extra) traffic will not be displayed in CTC if the MS-SPRing switches back to working after a failure recovery. To see this issue, perform the following steps in a two-fiber or four-fiber MS-SPRing configuration.
Step 1 Create a PCA circuit.
Enable IPPM on all OCn cards for this PCA circuit.
Step 2 Issue a Forced Switch Ring (FS-R) in CTC on the add or drop node. The MS-SPRing switches.
Step 3 View the PCA path level counts shown in CTC.
Step 4 Clear the Forced Switch Ring in CTC. The MS-SPRing switches back to working; however, IPPM path level counts for PCA circuits are not shown.
To recover from this situation, lock out the ring by issuing the LockoutOfProtection (LK-S) command on both east and west for all nodes in the ring. Reboot the OCn card that is not showing PCA path level counts. This procedure needs to be performed whenever there is a switch in BLSR configuration. This issue will be resolved in Release 4.6.
DDTS # CSCea81000
In a two-fiber or four-fiber MS-SPRing, MS-RFI is not reported for an LOS or LOF with a ring lockout in place on a different span. This issue will be resolved in Release 6.0.
DDTS # CSCeb09217
Circuit states are not updated after a span update. If you update a four node OC-12 two-fiber MS-SPRing to a four node OC-192 two-fiber BLSR, the previous PCA circuits should be shown as two-fiber MS-SPRing protected, but they are shown as "UNKNOWN" protected. If you relaunch CTC this situation is corrected. This issue will be resolved in Release 5.0.
DDTS # CSCea02986
In MS-SPRing configurations multiple node deletions and additions on a ring in quick succession can cause PCA traffic to go down. If this occurs, apply a Force Ring switch on the effected nodes. This issue will be resolved in Release 5.0.
DDTS # CSCdz66275
When creating a MS-SPRing from the network view, the node default values for reversion are not initially used. To see this, starting with no preferences file, log into a node with CTC, and set the node default values for MS-SPRing reversion. Now, in Network view, use the MS-SPRing wizard to create a MS-SPRing. The node level default values are initially ignored while the wizard is still in operation. If you encounter this issue, you may need to change values as appropriate for your network while you are still using the MS-SPRing wizard. Once the wizard is finished, these values are saved to a preferences file and will be used henceforth. This issue will be resolved in a future release.
DDTS # CSCdz35479
Rarely, CTC Network view can freeze following the deletion or addition of a node from or to a BLSR/MS-SPRing. This can result in the CTC Network view no longer updating correctly. If this occurs, restart CTC. This issue will be resolved in Release 5.0.
DDTS # CSCdy63060
In a 4 node, two-fiber MS-SPRing configuration, the E100 unstitched circuit state can become stuck at OOS-AINS-PARTIAL, even if there are no alarms and conditions raised.
This issue has been seen under the following conditions:
Step 1 Set up a 4 node, two-fiber MS-SPRing.
Step 2 Provision an E100 point to point circuit starting with the OOS-AINS state and the longer
Step 3 path as the working path. The working path should have at least one pass-through node.
Step 4 Ensure that Ethernet ports and STM-N ports are all in service, no alarms or conditions are raised, and traffic is running clear.
If the state does not change automatically, use the Circuit Edit Window to explicitly set the circuit state to IS. This issue will be resolved in a future release.
DDTS # CSCdy56668
Ethernet circuits may appear in the CTC circuit table with an INCOMPLETE status after an MS-SPRing span is upgraded. The circuits, when this occurs, are not truly incomplete. They are unaffected and continue to carry traffic. To see the circuit status correctly, restart CTC. This issue is under investigation.
DDTS # CSCdy48872
Issuing a lockout span in one direction while a ring switch (SF-R) is active in the other direction may result in a failure to restore PCA circuits on the ring.
To see this issue, on a node participating in a two fiber MS-SPRing with PCA circuits terminating at the node over the two fiber MS-SPRing, cause an SF-R by failing the receive fiber in one direction (say, west). Then issue a lockout span in the other direction (in our example, east). Since the lockout span has higher priority than the SF-R, the ring switch should clear and PCA traffic should be restored on spans without a fiber fault. The ring switch does clear, but PCA traffic does not restore. To correct this issue, clear the fiber fault. All traffic restores properly. This issue will be resolved in a future release.
DDTS # CSCdw53481
Two MS-Rs are not allowed to coexist. If you execute a manual ring switch command on one side of an MS-SPRing node and apply another manual ring switch command on other side of the node, the second manual ring switch command is rejected. This works as designed. The implementation complies with Telcordia GR-1230, R6-102.
DDTS # CSCdx45851
On a four fiber MS-SPRing, restoring the database for all nodes at the same time could cause VC4-16c traffic to fail to switch. Do not restore the database for multiple nodes simultaneously. The proper procedure for restoring the database for multiple nodes is to restore one node at a time. This procedure is documented in the user documentation.
DDTS # CSCdx19598
A rare hardware failure on an STM16AS card transmitter can trigger SEF on the receiving STM16AS card in a four fiber MS-SPRing (or BLSR) configuration. The BER calculations are suspended when SEF is detected, so SD or SF is never raised. Likewise SEF is not considered a signal failure condition like LOS or LOF, so a protection switch will not occur. If this occurs, use the CTC GUI to force a protection switch on the MS-SPRing (or BLSR). This issue will not be resolved.
DDTS # CSCdv53427
In a two ring, two fiber MS-SPRing (or BLSR) configuration (or a two ring MS-SPRing or BLSR configuration with one two fiber and one four fiber ring) it is possible to provision a circuit that begins on one ring, crosses to a second ring, and returns to the original ring. Such a circuit can have protection vulnerabilities if one of the common nodes is isolated, or if a ring is segmented in such a way that two non-contiguous segments of the circuit on the same ring are each broken. There are two possible workarounds for this issue:
1. Manually route the circuit to avoid the "one circuit over two ring" routing scenario.
2. When routing the circuit automatically, select the Using Required Nodes/Spans option in the Circuit Routing Preference screen, then select the appropriate spans to avoid the "one circuit over two ring" routing scenario.
This issue will be resolved in a future release.
Database Restore on an MS-SPRing (or BLSR)
When restoring the database on an MS-SPRing (or BLSR), follow these steps:
Step 1 To isolate the failed node, issue a force switch toward the failure node from the adjacent east and west nodes.
Step 2 If more than one node has failed, restore the database one node at a time.
Step 3 After the TCCi has reset and booted up, release the force switch from each node.
SNCP Functionality
DDTS # CSCeb37707
With a VT SNCP circuit, if you inject signals with a thru-mode test set into one path of the circuit in a particular order, you may not see the appropriate alarms. This can occur when you first inject LOP-P, then clear, then inject LOP-V. This issue will be resolved in Release 6.0.
DDTS # CSCea23862
After you perform a force switch on one of the spans of a DRI or IDRI topology with SNCP DRI circuits present, if you then apply a clear on the same span, the state will not show up immediately in CTC. This issue is under investigation.
DDTS # CSCea23732
If you try to manually create a VC4 circuit over a three node, STM4 SNCP using automatic routing and a required node, but there is no protected path from the source to the destination excluding the required node, automatic routing will fail to find a path and will raise a "ComputeRouteInMixedDomains: No Route Found" exception. To avoid this issue, you can avoid selecting required nodes, or use manual routing. This issue will be resolved in Release 5.0.
Active Cross Connect or TCCi/2 Card Removal
As in MS-SPRing (or BLSR) and 1+1, you must perform a lockout on SNCP (or path protection) before removing an active cross connect or TCCi (or TCC2) card. The following rules apply to SNCP (or path protection).
Active cross connect cards should not be removed. If the active cross connect or TCCi/2 card must be removed, to minimize network interruption you can first perform an XC10G (or XCVXL) side switch and then remove the card once it is in standby, or you can perform a lockout on all circuits that originate from the node whose active cross connect or active TCCi/2 will be removed (performing a lockout on all spans will also accomplish the same goal). No lockout is necessary for switches initiated through CTC.
Performance Monitoring
DDTS # CSCea38791
In the CTC Performance > Statistics tab of the G1000-4 or G1000-2, there are no entries for Rx/Tx Multicast and Broadcast packets. This issue will be resolved in a future release.
The following two notes on page 5-30 of the Cisco ONS 15454 Reference Manual, R4.1 and R4.5 should be replaced.
Note G-Series cards manufactured before August 2003 do not support DWDM GBICs. G1000-4 cards compatible with DWDM GBICs have a CLEI code of SNP8KW0KAB. Compatible G1K-4 cards have a CLEI code of WM5IRWPCAA.
Note All versions of G1000-4 and G1K-4 cards support CWDM GBICs.
The replacement information is contained in CWDM and DWDM GBIC Compatibility with G1000-4 Cards and G1K-4 Cards.
Resolved Caveats for Release 4.1
The following items are resolved in Release 4.1
ML Series
DDTS # CSCin25238
If you configure Fast EtherChannel and POS-channel in the same bridge group, during system boot, the Fast EtherChannel or POS-channel configuration may be lost and following error message displayed:
Interface FastEthernet1 is attempting to join Port-channel1. But Port-channel1 belongs to bridge-group 1 which has another FE(C) member in it. FEC + FE(C) is not allowed in the same bridge group. Please change your configuration and retry.
This issue is resolved in Release 4.1.
DDTS # CSCea18623
To avoid possible ML-series card resets when adding interfaces to a bridge group, always configure the Spanning-Tree Protocol for the bridge group (using the bridge number protocol command) before performing any other configuration on the bridge group.
If you want to use a bridge group that does not run the Spanning-Tree Protocol, you must first configure the bridge group with the Spanning-Tree Protocol, and then disable the Spanning-Tree Protocol for that bridge group on every interface where it is used (using the bridge-group number spanning-disabled interface configuration command). This issue is resolved in Release 4.1.
Maintenance and Administration
DDTS # CSCea19297
For any STS or VT circuit that terminates on a node, an AIS (path level) that raises and clears on that circuit's path may result in an inability of other path alarms to be cleared. This can also occur when a line-level alarm occurs on the circuit path's line, causing the OC-N to send AIS-path downstream on each path within the line. This issue is resolved in Release 4.1.
DDTS # CSCea21686
Retrieving a diagnostic file may cause a Standby or Active TCC2 reset. This is not traffic affecting. This issue is resolved in Release 4.1.
MS-SPRing Functionality
DDTS # CSCdy65890
If you have PCA circuits over two-fiber or four-fiber MS-SPRing protect channels, an incorrect auto-inservice transition occurs after traffic preemption. You may place the circuit back into the OOS-AINS state after the BLSR has returned to the unswitched mode, using the Circuit Editing pane of the CTC. This issue is resolved in Release 4.1.
New Features and Functionality
This section highlights new features and functionality for Release 4.1. For detailed documentation of each of these features, consult the user documentation.
New Software Features and Functionality
ML-Series Resilient Packet Ring
RPR (Resilient Packet Ring) is a new protocol available on the ML-Series cards enabling you to use SDH bandwidth more efficiently, with 50 ms recovery times.
Basic Feature Description
RPR for the ML-Series line cards provides a set of enhancements to the performance of any such card running the Release 4.1. These improvements include:
RPR for the ML-Series line cards allows new deployment applications for all cards running Release 4.1. These improvements include:
•Better SDH bandwidth utilization compared to an STP controlled ring topology.
•Non-SDH fail-over mechanism with sub 50-millisecond convergence for fiber cuts, restores, node failures and inserting new nodes.
•Ability to perform ML-Series QOS (quality of service) features on all SDH traffic (pass-through, drop, and add).
•No hardware changes: Only requires ONS 15454 Release 4.1, which includes the new IOS configuration.
•Increased number of supportable VLANs and MAC addresses on the ring.
•A scalable, inter-ring protection mechanism for increased network resiliency.
•The addition of RPR does not remove any Release 4.0 functionality. RPR features are enabled via a new set of configuration commands.
For further details of RPR uses and features, consult the user documentation for Release 4.1.
Open Ended SNCP
In previous releases, you could create an end-to-end SNCP circuit on any Cisco ONS 15XXX network using A-Z provisioning of CTC/CTM. This feature requires you to specify one source node and one destination node of a SNCP circuit. CTC/CTM requires these nodes to be part of the network that is discovered by CTC/CTM.
With Release 4.1 you can create an open ended SNCP circuit in addition to a regular SNCP. An open ended SNCP circuit is a partial SNCP circuit. This feature helps you create end-to-end SNCP circuits where a part of the given SNCP circuit is on a Cisco 15XXX network, while the other part of the circuit is on another vendor's equipment. The circuit may consist of one source point and two end points. There are two paths from the source; one path is from the source to one end point and the other path is from the source to the other end point. The source has a bridge that sends the traffic on both paths. The end points do not have any selectors and may hand off the traffic to another vendor's equipment. For bidirectional circuits, the source also contains a selector for the reverse traffic from end points to source. Alternatively, open ended SNCP can be used to create a circuit with two sources and one destination. In the unidirectional case, the destination node has a selector, and the source nodes have one-way connections.
NE Defaults
The NE defaults pane user interface is changed in Release 4.1 as follows:
•The NE defaults pane now has a highlighted title at the top of the pane, indicating the last action taken by the user.
•If you import or export a file, the title shows the file name and the time of the action.
•If you load or apply a file to the node, the changes and the time of the action will be displayed.
User Privileges
As of Release 4.1, The following user privileges have changed:
•A Maintenance level user can back up the database and transfer a software package to the node.
•A Provisioning level user can delete and reset cards.
Protect Threshold Crossing Alarms
As of Release 4.1, BLSR/MS-SPR and path protection/SNCP protect thresholds at both the card and port level are inherited from the working card/port.
Gigabit Ethernet Transponder
The Gigabit Ethernet Transponder is a software enhancement to existing G-series Ethernet cards that allows these cards to support transponder functionality.
The following features support Gigabit Ethernet Transponder functionality for Release 4.1.
Note In this section, unless otherwise mentioned, all items apply equally to both G1000-4 cards and G1K-4 cards. Some capabilities also apply to G1000-2 cards for the ONS 15327.
CWDM GBICs
Note This applies only to the ONS 15454-based G-series cards (G1000-4 and G1K-4).
CWDM GBICs correspond to the eight wavelengths supported by the Cisco CWDM GBIC solution on the ONS 15454: CWDM-GBIC-1470, CWDM-GBIC-1490, CWDM-GBIC-1510, CWDM-GBIC-1530, CWDM-GBIC-1550, CWDM-GBIC-1550, CWDM-GBIC-1570, CWDM-GBIC-1590.
DWDM GBICs
This applies only to the latest revision of the ONS 15454-based G-series cards (G1000-4 and G1K-4).
DWDM GBICs correspond to the 32 different ITU-100GHz wavelengths supported on the ONS 15454: 1530.33, 1531.12, 1531.90, 1532.68, 1534.25, 1535.04, 1535.82, 1536.61, 1538.19, 1538.98, 1539.77, 1540.56, 1542.14, 1542.94, 1543.73, 1544.53, 1546.12, 1546.92, 1547.72, 1548.51, 1550.12, 1550.92, 1551.72, 1552.52, 1554.13, 1554.94, 1555.75, 1556.55, 1558.17, 1558.98, 1559.79, and 1560.61. The ONS 15454 version DWDM GBICs are the only officially supported DWDM GBICs for the G-Series Ethernet cards. These GBICs have wideband reception capability and can receive with adequate sensitivity across the 1260-1620 nm range (refer to GBIC specs in the user documentation for details). This capability can be exploited in some of the transponder applications.
GBIC Notes
New GBICs are supported for only those vendors/brands that are officially certified for use on the ONS 15454.
GBIC inventorying functions are not currently supported. However, the type of GBIC plugged in and the wavelength used are displayed to CTC and TL1 users (as well as CTM users when CTM support is added).
Performance monitoring of optical parameters such as DWDM power levels per wavelength are not supported in Release 4.1.
The GBIC security feature is not supported in Release 4.1.
Three Transponder Modes of Operation
Release 4.1 supports three transponder modes of operation:
Bidirectional 2-port transponder
Bidirectional 1-port transponder
Unidirectional 2-port transponder
This applies only to the ONS 15454-based G-series cards (G1000-4 and G1K-4). This feature also includes the ability of the cards to operate (when in transponder mode) independent of the cross connect cards and even operate without any cross connect cards in the shelf.
When at least one port is provisioned in a transponder mode, the entire card will be in transponder mode. When SONET/SDH circuits are provisioned on a card, the card is said to be in normal/SONET/SDH mode.
Hybrid mode of operation is not supported in Release 4.1. At any given time, a card can be either in transponder mode (with one or more ports being provisioned to provide transponder capabilities) or in normal SONET/SDH mode. A mixed or hybrid mode (in which only some ports are performing transponder functions while others are switching traffic into the SONET/SDH network) is not supported and you will be prevented from provisioning such a combination. In order to move a card from SONET/SDH mode to transponder mode you must first delete all SONET/SDH circuits terminating on the card, after which ports will become provisionable as transponders. Similarly you must first turn off transponder mode on all ports before a card can become eligible for SONET/SDH circuits again.
Facility Loopback
Facility Loopback is supported for Release 4.1 transponder functionality.
This applies to all G-series cards (G1000-4 and G1K-4 on the ONS 15454 and G1000-2 on the ONS 15327).
Provisionable Flow Control Watermarks
Provisionable flow control watermarks are supported for Release 4.1. This capability enables the user to tune the flow control mechanism on the G-Series cards for some network applications.
This applies to all G-series cards (G1000-4 and G1K-4 on the ONS 15454 and G1000-2 on the ONS 15327).
Changed Alarms
The following alarms have changed as of Release 4.1
SDH CRITICAL Alarms
LOC is added in Release 4.1
SDH MAJOR Alarms
SQUELCHED is MJ in Release 4.0 but changed to NA in Release 4.1
FEC-MISM is added in Release 4.1
SDH MINOR Alarms
LP-PLM is MN in Release 4.0 but changed to MJ in Release 4.1
LP-TIM is MN in Release 4.0 but changed to MJ in Release 4.1
SDH Conditions
BAT-A-HGH-VLT is in Release 4.0 and Release 4.1 but unused
BAT-A-LOW-VLT is in Release 4.0 and Release 4.1 but unused
BAT-B-HGH-VLT is in Release 4.0 and Release 4.1 but unused
BAT-B-LOW-VLT is in Release 4.0 and Release 4.1 but unused
INTRUSION-PSWD is added in Release 4.1
LPBKFACILITY (G-Series) is added in Release 4.1
Related Documentation
Release-Specific Documents
•Release Notes for Cisco ONS 15454 SDH Release 4.0
•Release Notes for Cisco ONS 15454 Release 4.1
•Release Notes for Cisco ONS 15327 Release 4.1
Platform-Specific Documents
•Cisco ONS 15454 SDH Installation and Operations Guide, Release 4.1 and 4.5
•Cisco ONS 15454 SDH Troubleshooting and Maintenance Guide, Release 4.1 and 4.5
•Cisco ONS 15454 SDH Product Overview, Release 4.1 and 4.5
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.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R)
Copyright © 2007, Cisco Systems, Inc.
All rights reserved.


text:
CALGARY - After 16 seasons, two Rocket Richard Trophies, one trip to the Stanley Cup final, two Olympic gold medals and countless forehead-crinkling smiles, Jarome Iginla is no longer a Calgary Flame.
Take some extra tissues to work this morning, Calgary. Take a deep breath and let the news sink in.
Jarome Iginla is a Pittsburgh Penguin (not a Boston Bruin, as was widely reported Wednesday night in a deal that might have fallen through at the last moment.)
Time for the grieving process - and the long-awaited rebuild of a floundering National Hockey League franchise – to officially begin.
"He's been such a presence on this team, for this city, this organization, for so long," a shell-shocked Michael Cammalleri was saying after the Flames defeated the Colorado Avalanche Wednesday night. "He's such a dominant player. A guy who is in the lineup all the time, not missing any games.
"It will be different, for sure, without him."
The Flames announced late Wednesday that Iginla is headed to Pittsburgh for forwards Kenneth Agostino and Ben Hankowski and Pittsburgh's 2013 first-round pick.
Clearly, this is a move designed, on Calgary's part, to start stocking a bare cupboard of prospects with eye to the future.
The long-term future.
The Penguins, on the other hand, are girding for another run at the Stanley Cup – the only item missing from Iginla's storied resume. They also just happen to be one of four teams reportedly on Iginla's list of approved destinations (he has a no-movement clause in a contract set to expire this summer.)
In spite of his age, Iginla was considered the prize catch on the trade market with the April 3 trade deadline fast approaching.
The Flames, meanwhile, sent out a press release nearly two hours before puck drop between Calgary and the Colorado Avalanche to announce Iginla would sit out as a healthy scratch.
"He texted me today after pre-game nap to say he wouldn't be here tonight and to wish us the best in the game tonight," Cammalleri said. "That was pretty much it."
In an emotional performance for the home team, the Flames reeled off their eighth straight win at the Dome (keeping in mind they've lost 10 straight on the road.)
Cammalleri led the way with two goals. Jiri Hudler and Steve Begin notched singles. Jamie McGinn Gabriel Landeskog, and Ryan O'Reilly replied for the Avalanche."
Just how weird of a night was it? Well, consider TSN kept replaying the footage of general manager Jay Feaster and assistant general manager John Weisbrod marching out of the press box at the end of the Bruins-Montreal Canadiens game, presumably en route to the executive offices.
Just how weird of a night was it? Well, TSN commentator Mike Johnson works between the benches, and said Flames players were peering over to ask him about the Iginla trade between whistles.
Just how weird of a night as it? Well, the only standing ovation went to former Flame killer Wayne Gretzky, shown on the big screen sitting in one of the Dome luxury boxes.
Just how weird of a night was it? Well, at 5:32 and 19:07 of the third period, the "Iggy, Iggy" chant erupted again with the finality of it all sinking in.
"A nice gesture by the fans," said defenceman Mark Giordano. "There's no doubt what he means to the fans, the organization, and the city. Obviously, a different kind of night. A little bit weird. But hopefully everything works out."
An announcement – or press conference – is expected as early as this morning.
"It's our captain," Giordano said. "One of the best players that's played the game. He's been here his whole career. I think it was a little bit surreal, different.
"But I thought we did a good job and played hard. That's all we were asking of each other. And, for Iggy, a friend and a good teammate for a long time."


text:
PET plastic cold drink cups are crystal clear and available in a wide range of sizes from 7 fl oz up to 32 fl oz. Many different lid formats are available to fit most sizes of disposable plastic cup - such as lids with straw slots or bubble dome lids.
+ Click on product to enlarge
Case Quantity900
DimensionsWidth: 102mm Length: 102mm Height: 45mm
© Copyright Celebration 2020 | Registered in England No. 1743179 | Privacy Statement | Terms & Conditions | Environmental Policy Statement | Cookies Policy | Site by Verto


text:
- Version
- Download 51379
- File Size 0.00 KB
- File Count 1
- Create Date August 30, 2018
- Last Updated August 30, 2018
Engineering Metrology Study Materials & Lecture Notes
Engineering Metrology Study Materials
Engineering Metrology Materials & Notes. Engineering Metrology Unit Wise Lecture Notes and Study Materials in pdf format for Engineering Students. Engineering Metrology Notes & Book has covered every single topic which is essential for B.Tech/ BE Students. Engineering Metrology Study Materials provided here is specifically prepared for JNTUH JNTUK JNTUA R13, R10, R09 Students but all other University students can also download it as it has covered every single important chapter. So all students seeking Engineering Metrology Engineering Text Book for JNTU Hyderabad, JNTU Kakinada, JNTU Anantapur, Guru Gobind Singh Indraprastha University, Anna University, PTU, UPTU, JMI, University of Mumbai, Osmania University, GGU, WBUT, LPU, SMU, Galgotia's and other universities can download Engineering Metrology Materials & Notes, Lecture Notes, Books and Class Notes from this page.
Engineering Metrology Lecture Notes
Students are advised to follow their Syllabus While Studying JNTUH JNTUK JNTUA Engineering Metrology Study Material and Text Book. As we have covered all topics but the topics provided in the notes are not tabulated according to latest prescribed syllabus. So all students are advised to follow their syllabus while reading Engineering Metrology Class Notes and Study Material or Text Book.
Don't forget to share this Lecture Note / Text Book of Engineering Metrology among all your friends and also on your social media pages. Feel free to get in touch with us regarding any issue. We are always there in your services and we will surely get back to you within minutes, if needed. So Scroll above and Download Engineering Metrology Materials & Notes or Text Book in pdf format.
If you find any issue while downloading this file, kindly report about it to us by leaving your comment below in the comments section and we are always there to rectify the issues and eliminate all the problem. So never hesitate to ask us anything in this regard or regarding anything on our website.


text:
Voting strictly along party lines, the GOP controlled New Hampshire Senate today voted 13 to 11 to reject the expansion of Medicaid under the terms of the Affordable Care Act (Obamacare). The vote sets up a conflict in a House-Senate Committee of Conference that could start as early as next week.
Expanded Medicaid would provide insurance coverage to an estimated 58,000 New Hampshire residents, paid for 100% by federal dollars for the first three years.
The Senate also approved a budget that makes $50 million in unspecified personnel cuts that could lead to hundreds of layoffs. This, too, could be altered by the conference committee.
On their way into today's session, the Senators had to wade through dozens of pro-worker and pro-Medicaid activists to get into their chamber. NH Voices for Health, which brings together health care providers and advocates, has been working hard to rally support for expanded Medicaid. The State Employees Association will lead efforts to stop the personnel cuts, which would not only hurt workers and their families but also reduce the quality of services offered to state residents.
The effort will escalate over the next few weeks as Representatives and Senators continue the budget debate, perhaps right up to the June 30 end of the fiscal year.


text:
You just surfed the best wave of your life, or completed an epic mountain bike ride. Naturally, you want to tell your friends about it. Recounting your adventures through words can recapture some of the excitement, but a video would be better, right?
Over the past two weeks, I've been testing two portable cameras that will do the trick: The Ion Air Pro WiFi and the GoPro HD Hero2 with the Wi-Fi BacPac and Remote. Unlike regular cameras or camcorders, these action cameras feature rugged designs for outdoor use, and allow you to capture video at unique angles from your surfboard, bike or other sports equipment. The option of Wi-Fi also lets you connect to your smartphone or tablet to instantly watch and share videos, and to use your devices as a remote control.
The $350 Ion Air Pro WiFi impresses with a streamlined design that makes it easy to start shooting right away. The GoPro is a bit more expensive: The camera alone costs $300, and if you want the WiFi BacPac, that's another $60; you can get a combo kit with a remote for $100. Setup also takes a bit longer. Even so, the GoPro is the better choice, because when it comes to the most important feature — video quality — it's the hands-down winner.
I attached both the GoPro and Ion to my bike's handlebar and also shot a video of myself skateboarding, with the GoPro mounted to the front of my board and the Ion attached to my helmet. Unfortunately, I wasn't able to do a full water test, but the Ion is waterproof in up to thirty feet of water, while the GoPro is waterproof in up to 197 feet of water using the included waterproof case. Both worked fine when submerged in a bathtub.
Video quality on the Ion is okay. Videos shot at full 1080p resolution weren't sharp, and colors were a bit dark. As a result, some of the finer details were lost. For example, when I did a side-by-side video comparison of the GoPro and the Ion, I was able to see such details as the leaves in the trees with the GoPro, but not so much on the Ion's video. Also, while I adjusted the handlebar mount as tight as I could, videos were slightly shaky and wind noise can be a problem on the Ion.
The Ion can capture photos at up to five megapixels, but pictures suffer from the same problems as video. I also found it annoying that I had to connect the Ion to my computer to change the camera's settings. Ion says a future update will allow you adjust the settings from the camera's smartphone app.
The Ion is otherwise easy to use. The tube-shaped camera features two large buttons on top: A power/camera key and a slider switch that stops/starts video recording. The camera vibrates briefly to confirm it's recording, which is nice.
The cool thing about the Ion camera is the company's "podz" system. This is a disc in the back of the camera that contains the Wi-Fi radio and twists off so you can access the camera's various ports. The company plans to offer other podz, such as one incorporating a bigger battery or a better microphone, so you can easily swap them out.
As for the Wi-Fi functionality, it's a nice option if you want to be able to view and share videos right after you're done. I downloaded the Ion Camera app to my iPhone (an Android version is coming) and connected to the camera. All my photos and videos appeared in the album section. You can share directly to Facebook, and you also get eight gigabytes of free cloud-based storage.
The GoPro HD Hero2 delivered excellent video quality. Videos shot at full 1080p resolution looked sharp and bright, with more accurate colors. It was better at image stabilization, and the waterproof housing helped block out wind noise. The camera also has a wider field of view than the Ion, so it was able to capture more of the scene.
The GoPro can take photos up to 11 megapixels and, unlike the Ion, you can change the settings right from the camera. Two buttons on the front and top of the small, rectangular camera help you navigate through the various menus, while a small LCD displays all your options.
I like the onscreen battery indicator. The Ion vibrates when low on battery, but I like a visual cue, too. Both cameras promise about 2.5 hours of battery life. In tests where I shot continuous 1080p video, both the GoPro and Ion delivered two hours and 40 minutes of battery life.
The GoPro requires housing in most instances, whereas the Ion works without one. The GoPro comes with a plastic case with two interchangeable back doors — one that's waterproof and another with vents to capture more sound. Installation is easy, but if you want to add the WiFi BacPac, which attaches to the back of the camera via connector, that requires another door. It's not a huge deal, but just know that the GoPro requires a little more planning and setup.
The WiFi Remote Control is a useful accessory. You can wear it on your wrist and take photos and video with the press of a button. It was great while skating, since I didn't have to bend over and press the button every time, and I can imagine using it while surfing.
GoPro's Wi-Fi app is due out in the fall for iOS and Android devices, but I got an early peek at the iPhone version. The interface looks simple, and provides a preview of the camera's angle. You can also access all of the camera settings, and you'll be able to view and share clips via social networks like the Ion app.
I had a lot of fun using both cameras, and though I like the Ion's design better, I'm willing to deal with the extra setup of the GoPro for better video quality, and would recommend it to other outdoor enthusiasts who want to capture all their adventures.


text:
Secretary-General Ban Ki-moon leaves New York today for a trip to Switzerland, Belgium and Luxembourg, where he will meet with United Nations, European Union and national government officials, his spokesperson announced today.
In Switzerland, Mr. Ban will chair a meeting of the UN System Chief Executives Board (CEB) at a retreat held outside Geneva. The Board, which meets twice a year, brings together the heads of the various UN specialized agencies and the chiefs of the World Bank and the International Monetary Fund (IMF), otherwise known as the Bretton Woods institutions.
Mr. Ban will then travel to Brussels, where he will attend the EU Summit on Sustainable Energy for All, and will also hold a series of meetings with European Commission officials, including President José Manuel Barroso.
The last stop of Mr. Ban's trip will be in Luxembourg, where he will meet the Henri the Grand Duke, Prime Minister Jean-Claude Juncker and other senior officials. He will also address the Luxembourg Parliament.
The Secretary-General will return to New York on 18 April.
Source: UN News Centre
The Brussels based United Nations Regional Information Centre for Western Europe - UNRIC provides information on UN activities to the countries of the region. It also provides liaison with institutions of the European Union in the field of information. Its outreach activities extend to all segments of society and joint campaigns, projects and events are organized with partners including the EU, governments, the media, NGOs, schools and local authorities.
United Nations Regional Information Centre for Western Europe (UNRIC Brussels)
Residence Palace, Rue de la Loi/Wetstraat 155, Block C2,7th and 8th floor, Brussels 1040, Belgium
Tel.: +32 2 788 8484 / Fax: 32 2 788 8485


text:
Rockit Now is a wordpress theme specially designed for Bands and music websites. This theme
is easy to modify and ready to be up and running out of the box. The PSD files included have
been customized to allow fast skinning.
Main Features
- Event Managment
- Gallery Managment
- Album + Track Managment
- Slider Managment
- Sidebar Managment
- Powerfull Theme Options + Page Builder
This template comes in 8 pre made color variations. But it will only take one minute to
create your desired color schemes by using theme options
Change Log: Older Versions
Dummy data import system is updated all slider files are centerlized now little styling issues resolved for Blog, Event and Album Description page View Albums URL is now dynamic Home page slider is fixed Even count down widget background image is dynamic PSDs are updated
For detailed log please check documentation
Change Log: Version 1.7
1 Theme option data lost issue on theme activation 2 RTL and Responsive 3 CSS and JS more improved. 4 Pretty photo css function removed and added for theme activation 5 Error Message added (like data not found etc) 6 Date format whole theme and wp format enabled 7 Theme made child theme enabled. 8 Added proper comment with all funtions 9 Added action and filter are placed in one function 10 Fixed undefined errors on fresh installation with isset or emtpy check 11 inline JS moved in function.js and made it fuction 12 Checked compatibility with latest wordpress version 13 W3C school validation 14 Default sidebar show on first time activation
Change Log: Version 1.8
1- update upcoming event widget 2- Fixed: footer menu issue.[file: style.css line#3292 replace height:69px with min-height:69px;]
Change Log: Version 1.9 (14 September 2014)
1: WordPress 4.0 compatibility 2: Event map issue on event detail page
Change Log: Version 2.0 (12 January 2015)
Added: Compatibility with WordPress version 4.4.2
Get the theme here !