text:
Table Of Contents
Release Notes for Cisco ONS 15310-CL
Release 6.0.1Maintenance and Administration
Resolved Caveats for Release 6.0.1
Maintenance and Administration
New Features and Functionality
New Software Features and Functionality
Cisco Service Assurance Agent ML-Series Support
Obtaining Optical Networking Information
Where to Find Safety and Warning Information
Cisco Optical Networking Product Documentation CD-ROM
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco ONS 15310-CL
Release 6.0.1
July 2008
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.
Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15310-CL. For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to Release 6.0 of the Cisco ONS 15310-CL Procedure Guide, Cisco ONS 15310-CL Reference Guide, Cisco ONS SONET TL1 Command Guide, and Cisco ONS 15310-CL Troubleshooting Guide. For the most current version of the Release Notes for Cisco ONS 15310-CL Release 6.0.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 6.0.1
New Features and Functionality
Obtaining Optical Networking Information
Where to Find Safety and Warning Information
Cisco Optical Networking Product Documentation CD-ROM
Obtaining Documentation and Submitting a Service Request
Changes to the Release Notes
This section documents supplemental changes that have been added to the Release Notes for Cisco ONS 15310-CL Release 6.0.1 since the production of the Cisco ONS 15310-CL System Software CD for Release 6.0.1.
No changes have been added to the release notes for Release 6.0.1.
Review the notes listed below before deploying the ONS 15310-CL. 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.
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.
A CTC client session can disconnect from an ONS node during simultaneous deletion of large numbers of VT level circuits (3000+). Connectivity to the node will recover without any user action. If the condition persists, restart the CTC session to reconnect. This issue is under investigation.
Data I/O Cards
In Asymmetric configuration, with autonegotiation enabled and flow control selected, an ML-series card might fail to synchronize with, or to recognize the asymmetric flow control. This issue is under investigation.
Path Protection Functionality
Traffic hits can occur in an unprotected to path protection topology upgrade in unidirectional routing. If you create an unprotected circuit, then upgrade the unprotected circuit to a path protection circuit using Unprotected to Path Protection wizard, selecting unidirectional routing in the wizard, the circuit will be upgraded to a path protection circuit. However, during the conversion, traffic hits on the order of 300 ms should be expected. This issue will not be resolved.
Bridge and Roll
When a rollTo leg is not receiving a good signal, and because of this the rollPending alarm is not cleared, there is no alarm indicating the reason that the RollPending alarm fails to clear. This issue is resolved in Release 7.0.
Note To be compatible with TL1 and DNS, all nodes must have valid names. Node names should contain alphanumeric characters or hyphens, but no special characters or spaces.
Resolved Caveats for Release 6.0.1
The following items are resolved in Release 6.0.1.
Maintenance and Administration
A 100 second outage on DS1 traffic that is physically looped back, and in IS-AINS state, can occur during a span switch. With a loopback on the DS1 traffic a span switch will induce errors that raise a signal degrade (SD) on the DS1. The system then injects AIS due to the SD to keep from transitioning to IS from IS-AINS. To prevent this issue avoid using a physical loopback. This issue is resolved Release 6.0.
Data I/O Cards
Loss of Ethernet signal on one of the front ports takes longer than expected to be propagated to the remote port. Link integrity operates slower than expected for Ethernet failures (though it works as expected for SONET failures). To see this, any condition that causes an Ethernet loss of signal (removal of a front port Ethernet cable, for example) will invoke the Ethernet integrity function. This issue is resolved in Release 6.0.
On ML-series in the ONS 15310-CL, when policing is enabled, the configured policed rate is not forwarded. This can occur when policing at a rate lower than 1 Mbps. The workaround is to set the policed rate higher than 1 Mbps, or to raise the configured policed rate until the desired rate is forwarded. This issue is resolved in Release 6.0.
Path Protection Functionality
A path protection/SNCP circuit with a defect signal present (for example, AIS-P or AIS-V) on the protect path will produce RDI-P or RDI-V upstream of the detection point, but these signals will not be detected or indicated. This issue is resolved in Release 6.0.
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 later, the circuit retrieve does not show the same value as before. For example FAC-4-1 changes to FAC-4-0. Workaround is to manually reset the active CTX after the upgrade.
New Features and Functionality
This section highlights new features and functionality for Release6.0.x. For complete documentation of each of the features of the ONS 15310-CL, consult the user documentation.
New Software Features and Functionality
Detectable Filler Card
As of Release 6.0, filler cards are detectable in CTC node view when installed in the ONS 15310-CL expansion slot. The filler card serves three functions: it prevents exposure to hazardous voltages and currents inside the ONS 15310-CL chassis, it eliminates electromagnetic interference (EMI) that might disrupt other equipment, and it directs the flow of cooling air through the chassis. If an expansion card (CE-100T-8 or ML-100T-8) is not plugged in, a filler card must be inserted in the expansion slot.
Bridge and Roll
Release 6.0.x introduces bridge and roll for the ONS 15310-CL. You can use the bridge and roll feature for maintenance functions such as card or facility replacement, or for load balancing. As of Release 6.0 you can perform bridge and roll operations using CTC or TL1 on all of the following ONS platforms: ONS 15454, ONS 15454 SDH, ONS 15600, ONS 15327, and ONS 15310-CL.
The CTC Bridge and Roll wizard reroutes live traffic without interrupting service. The bridge process takes traffic from a designated "roll from" facility and establishes a cross-connect to the designated "roll to" facility. When the bridged signal at the receiving end point is verified, the roll process creates a new cross-connect to receive the new signal. When the roll completes, the original cross-connects are released.
CTC Rolls Window
The CTC Rolls window provides access to information about a rolled circuit before the roll process is complete. To view the Rolls window, click the Circuits > Rolls tabs in either network or node view.
The Rolls window provides information on the following roll states and options. For descriptions of each state or option, consult the user documentation.
•Roll From Circuit
•Roll To Circuit
•Roll State
•Roll Valid Signal
•Roll Mode (automatic or manual)
•Roll Path
•Roll From Circuit
•Roll From Path
•Roll To Path
•Force Valid Signal
•Types of Rolls
TL1 Bulk Roll
Release 6.0.x TL1 bridge and roll features support for bulk rolling. Bulk rolling enables you to roll a subset of cross-connections from one port/facility to another port/facility.
The following TL1 commands specifically support bulk rolls. These commands support line-level rolling/bulk rolling and cannot be used for path-level rolling. For a complete list of TL1 commands supporting bridge and roll, as well as examples for each of the supported features, including bulk roll, consult the user documentation.
This command deletes an attempted rolling operation or completes an attempted rolling operation. The rolls that are created using the ENT-BULKROLL-<OCN_TYPE> command can be deleted using the DLT-BULKROLL-<OCN_TYPE> command.
This command edits information about rolling traffic from one end point to another without interrupting service. This command can use the CMDMDE option to force a valid signal. The only parameter that can be edited is CMDMDE. The time slots cannot be edited.
This command enters information about rolling traffic from one end-point to another without interrupting service.
This command retrieves roll data parameters.
Single and Dual Rolls
CTC supports two roll types. In a single roll operation you select only one roll point. This allows you to move either the source or destination of a circuit to a new end-point on the same node (similar to a TL1 single roll), or on a different node (rolling the original circuit onto another circuit).
In a dual roll, you select two roll points. This allows you to reroute a segment between the two roll points of a circuit. The new route for a dual roll can be a new link (no circuit is required), or it can be another circuit (created before or during the bridge and roll process).
For dual roll constraints, consult the user documentation.
Protected Circuits
CTC allows you to roll the working or protect path regardless of which path is active. You can upgrade an unprotected circuit to a fully protected circuit or downgrade a fully protected circuit to an unprotected circuit with the exception of a path protection circuit. When using bridge and roll on path protection circuits, you can roll the source or destination, or both path selectors in a dual roll, but not a single path selector.
Enhanced Security Features
Security Policy Enhancements
With Release 6.0.x the range of days over which you can enforce disabling of inactive users has increased. The previous range was 45 to 90 days. The new range is 1 to 99 days.
With Release 6.0.x enforced single concurrent user session applies to EMS, TL1, telnet, SSH, sftp, and ftp. This support applied only to EMS and TL1 in previous releases.
In Release 6.0.x you can set how many characters difference must exist between a user's old password and the next new password in a range of one to five characters.
Secure Shell Encryption and Node Access Security
In previous releases the ONS platforms supported SSH version 2 (SSHv2) as an alternative to the ability to telnet into a node (shell access). In Release 6.0.x SSH encrypts all traffic (including passwords) to effectively eliminate unwanted monitoring of node activity. SSHv2 also supports access to the line card shell via shelf controller (that is, via relay), and access to line cards via IOS CLI (for cards in L2/L3 mode).
In Release 6.0.x all HTTP access to a node (for example, database backup, bulk PM retrieval, or software download) allows the use of HTTPS.
In previous releases any service type supported by ONS software could access ONS nodes. In Release 6.0.x node access can be controlled by service type. Each service type from which you can access a node in Release 6.0.x is configurable to support a choice of access states. The available states are non-secure (the default), secure (via SSHv2), and disabled (deny access from this service type). The SSHv2 secure state is supported for shell and ftp (using sftp), TL1, and EMS access types. Only nonsecure and disabled modes are supported for SNMP access.
RADIUS Security
As of Release 6.0 users with Superuser security privileges can configure nodes to use Remote Authentication Dial In User Service (RADIUS) authentication. Cisco Systems uses a strategy known as authentication, authorization, and accounting (AAA) for verifying the identity of, granting access to, and tracking the actions of remote users.
RADIUS Authentication
RADIUS is a system of distributed security that secures remote access to networks and network services against unauthorized access. RADIUS comprises three components:
•A protocol with a frame format that makes use of User Datagram Protocol (UDP)/IP
•A server
The server runs on a central computer, while clients reside in the dial-up access servers and can be distributed throughout the network.
An ONS node operates as a client of RADIUS. The client is responsible for passing user information to designated RADIUS servers, and then acting on the response that is returned. RADIUS servers are responsible for receiving user connection requests, authenticating the user, and returning all configuration information necessary for the client to deliver service to the user. RADIUS servers can act as proxy clients to other kinds of authentication servers. Transactions between the client and RADIUS server are authenticated through the use of a shared secret, which is never sent over the network. User passwords are sent encrypted between the client and RADIUS server. This eliminates the possibility that someone illicitly monitoring an unsecured network might detect a user's password.
An ONS node acting as a RADIUS client can request authentication from up to ten hierarchically arranged RADIUS servers. RADIUS security provisioning features are located in the Provisioning > Security > RADIUS tabs. For further details and operation of RADIUS security features consult the user documentation.
RADIUS Session Time Limits
Release 6.0.x RADIUS supports RADIUS session time limits. This feature applies only when a RADIUS server is used for authentication. When RADIUS indicates that a session is to have a time limit, that session is terminated immediately after the time expires. There is no local database support for session time limits. Rather, when EMS users are forcibly logged out by the RADIUS server, they are presented with a notification dialog box indicating that they have been forcibly logged out due to session time expiration. Similarly, when a TL1 user is logged out, an autonomous REPT_EVT_SESSION is sent. After a TL1 user is logged out, the next command the user enters receives a DENY response with a reason code of PLNA (Login Not Active).
AAA Server Enable/Disable
In Release 6.0.x RADIUS a Superuser can turn AAA server authentication on or off. When AAA server authentication is turned off, the local security policy and settings are employed for user authentication. When AAA server authentication is enabled, it applies to all NE management services, overriding local settings where the two conflict.
Note The following security policy features are not available when AAA server authentication is used:
•Idle user timeout (RADIUS user session timeouts are employed instead)
•Single session per user
•Forced password change at first login (global policy)
•Forced password change at next login (individual user)
•Password change prevention
•Excess failed login attempt lockout
•Password reuse prevention
•Inactive account disable
•Password expiration
AAA server authentication can be set in the node view > Provisioning > Defaults tabs. The default for AAA server authentication is OFF.
Audit Trail Enhancements
The following features enhance your ability to monitor node and network activity through use of the audit trail in Release 6.0.x.
•Archival of the audit trail in TL1, with a supporting archival failure transient alarm, AUD-ARCHIVE-FAIL
•Audit trail initiation support for IOS-based data cards in the L2/L3 mode (available over the Syslog/IOS CLI)
•Tracking of all Release 6.0.x supported failed login types (incorrect password, disabled account, locked account, single login per user per node denial)
•Shell session login, logout, and activity trail
•Tracking of FTP/sftp logins and logouts
•Sustained audit trail for all logins and logouts whether or not an AAA server is used for user authentication
•Tracking of all user attempts to log in to the node
•When a login is denied, the audit trail records the reason (type of login failure)
CTC Enhanced Security Support
Note All of the security options and settings described in this section are available to Superuser level users. For specific security levels for any given feature, consult the user documentation.
CTC provides several user-configurable security features in the following subtabs under the The CTC node view Security tab.
•Active Logins
The Active Logins, Policy, Access, and RADIUS tabs support new features for Release 6.0.x, as described below.
Active Logins
The Active logins tab supports session management for Release 6.0.x. The Active Logins tab displays current login status information for the network. In previous releases the Active Logins tab displayed only which users were logged in, and the IP address from which each user was logged in. As of Release 6.0, in addition to user names and IP addresses, the Active Logins tab displays the specific node to which the user is logged in, the type of session used to log in, the date and time each user logged in, and the last date/time each user was active during the login. You can refresh the Last Activity Time by clicking the Retrieve Last Activity Time button. You also have the option to log out selected sessions. This feature logs out any selected sessions immediately, and interrupts any activities associated with those sessions. When you log out an active user session you have the option to lock the user out (from future sessions) prior to the logout.
In Release 6.0.x the following services are monitored in the Active Logins tab.
•telnet shell sessions (via serial port only; not the debug port)
•SSH shell sessions
The Policy tab supports user security policy options. The Policy tab provides security policy settings and options. In previous releases the Policy tab provided the following functionality, in five display areas, in which settings could be applied:
•Idle User Timeout—Sets the hours and minutes a user can remain idly logged in before a timeout will occur; settings are provided for each user level.
•User Lockout—Sets the number of times a user can fail an attempt to log in before a lockout will occur, with an option to enforce manual unlocking of the user name by a Superuser, or alternatively, to set the lockout duration in minutes and seconds. Login failure types include:
–Incorrect password
–Disabled account
–Locked account
–Single login per user per node denial
•Password Change—Sets the number of unique passwords that must be used before a single password can be reused. Sets the option to disable changing of passwords for a fixed, user-configurable number of days. Sets the option to require a password change on first login to a new account.
•Password Aging—Enables you to optionally set a fixed number of days for each user security level (after which time a warning will be issued to create a new password), and to set a fixed number of days after which the password will actually expire and the user will no longer be able to log in.
•Other—Sets the option to enforce a single concurrent session per user (EMS and TL1 only). Also sets the option to enforce disabling of inactive users for users inactive a specified number of days; for example, if this feature is checked, with 90 days selected, a user ID that has not logged in for 90 days or more will be unable to log in again.
With Release 6.0.x, in the "Other" area, enforced single concurrent user session applies to EMS, TL1, telnet, SSH, HTTP, sftp, and ftp, and also, the range of days over which you can enforce disabling of inactive users has increased. The new range is 1 to 99 days.
Release 6.0.x also adds a new Password Change configuration that sets how many characters difference must exist between the old password and the new password in a range of one to five characters.
Node Access
The Access tab supports node access options, including enhanced SSH secure connection support for Release 6.0.x. The Access tab provides settings and options for each type of access that can be used to reach the node. In previous releases, the Access tab included the following three areas for applying node access settings and options.
•LAN Access—Sets the option of None, Front only, Backplane only, or Front and Backplane. Also includes a "Restore Timeout" setting, configurable in minutes.
•Shell Access—Sets a choice between Telnet, with a configurable port number, and SSH, with a fixed port number.
•Other—Sets the PM clearing privilege as Provisioning or Superuser.
With Release 6.0.x the Access tab provides four new areas, plus functional changes to the Shell Access area, for a total of seven areas in which settings can be applied as follows.
•LAN Access—(Same as in previous releases.) Sets the option of None, Front only, Backplane only, or Front and Backplane. Also includes a "Restore Timeout" setting, configurable in minutes.
•Serial Craft Access—Sets the option to enable or disable the shelf controller serial craft port.
•Shell Access—Sets the Access security state for shell logins as Disable, Nonsecure, or Secure. Sets the configurable Telnet Port. Sets the option to Enable Shell Password.
•EMS Access—Sets the Access security state for EMS logins as Nonsecure or Secure. Sets the Corba IIOP Listener Port.
•TL1 Access—Sets the Access security state for TL1 logins as Disable, Nonsecure, or Secure.
•SNMP Access—Sets the Access security state for SNMP logins as Disable or Nonsecure.
•Other—(Same as in previous releases.) Sets the PM clearing privilege as Provisioning or Superuser.
The RADIUS tab is new for Release 6.0.x, and supports the new RADIUS security features, including RADIUS server management, authentication, accounting, and management of shared secrets. The RADIUS tab provides an area for setting the options to:
•Enable RADIUS Authentication
•Enable RADIUS Accounting
•Enable the given node as the final Authentication when no RADIUS server is reachable
The RADIUS tab also provides a display area for RADIUS servers, in order of authentication preference. This area displays the IP Address, Shared Secret, Authentication Port, and Accounting Port for each RADIUS server.
In the RADIUS tab you can create a RADIUS server by clicking the Create button. The RADIUS tab also provides the following additional actions, which can be performed upon selected server(s).
•Move up (in order of Authentication)
•Move down (in order of Authentication)
For information on using and configuring RADIUS features in Release 6.0.x consult the user documentation.
IOS Security Enhancements
With Release 6.0.x the ML-Series card includes several security features. Some of these features can operate independent of the ONS node where the ML-Series card is installed. Others are configured using CTC or TL1.
Security features configured with Cisco IOS include:
•Cisco IOS login enhancements
•Secure Shell connection
•AAA/RADIUS stand alone mode
•Cisco IOS basic password
Security features configured with CTC or TL1 include:
•Disabled console port
•AAA/RADIUS relay mode
Disabling the Console Port on the ML-Series Card
There are several ways to access the Cisco IOS running on the ML-Series card, including a direct connection to the console port, which is the RJ-11 serial port on the front of the card. As of Release 6.0, you can increase security by disabling this direct connection, which is enabled by default. This prevents console port input without preventing any console port output, such as Cisco IOS error messages.
You can disable console port access through CTC or TL1.
Secure Login on the ML-Series Card
The ML-Series card supports the Cisco IOS login enhancements integrated into Cisco IOS Release 12.2(25)S and introduced in Cisco IOS Release 12.3(4)T. The enhancements allow users to better secure the ML-Series card when creating a virtual connection, such as Telnet, Secure Shell (SSH), or HTTP. The secure login feature records successful and failed login attempts for vty sessions on the ML-Series card. These features are configured using the Cisco IOS command-line interface (CLI).
Secure Shell on the ML-Series Card
In previous releases the ML-Series card supported SSH version 1 (SSHv1) only. With Release 6.0.x the ML-Series card also supports SSH version 2 (SSHv2). SSHv2 offers security improvements over SSHv1 and is the default choice on the ML-Series card.
SSH has two applications, an SSH server and SSH client. The ML-Series card only supports the SSH server and does not support the SSH client. The SSH server in Cisco IOS software works with publicly and commercially available SSH clients.
The SSH server enables a connection into the ML-Series card, similar to an inbound Telnet connection, but with stronger security. Before SSH, security was limited to the native security in Telnet. SSH improves on this by allowing the use of Cisco IOS software authentication.
The ONS node also supports SSH. When SSH is enabled on the ONS node, the user must use SSH to connect to the ML-Series card for Cisco IOS CLI sessions. Telnet access to the ML-Series card is prevented when SSH is enabled on the ONS node except for connections through the console port of the ML-Series card. Disabling the console port on the ML-Series card will prevent this Telnet access.
RADIUS on the ML-Series Card
RADIUS is a distributed client/server system that secures networks against unauthorized access. Clients send authentication requests to a central RADIUS server, which contains all user authentication and network service access information. The RADIUS host is normally a multiuser system running RADIUS server software from Cisco or another software provider.
Many Cisco products offer RADIUS support, including the ONS 15454, ONS 15454 SDH, ONS 15327, ONS 15310-CL, and ONS 15600. The ML-Series card also supports RADIUS.
The ML-Series card can operate either in RADIUS relay mode or in RADIUS stand alone mode (default). In either mode, the RADIUS messages from the ML-Series card are passed to a RADIUS server that is on the data communications network (DCN) used to manage the ONS node. For more information about RADIUS modes and operation on the ML-Series card consult the user documentation.
IP and OSI on DCC
As of Release 6.0, IP and OSI can coexist on DCC on a Cisco ONS network, addressing legacy OSI via NSIF Mediation, and allowing migration into IP via G.7712. IP on DCC provides security through strong encryption, SSH, SSL, and HTTPS; centralized control and strong authentication (AAA); RADIUS; communication to Layer 2 and Layer 3 devices (IP + Optical); and pseudo wire, in support of the interworking function between IP and OSI. The ability to address IP/OSI issues gives you flexibility for the future, while working within existing DCN/DCC/OSS infrastructure.
Release 6.0.x uses PPP, a Layer 2 encapsulation protocol, with high-level data link control (HDLC) datagram encapsulation to transport IP and OSI data, and link control protocol (LCP) to establish, configure, and test the point-to-point connections. CTC automatically enables IP over PPP whenever you create an SDCC or LDCC. The SDCC or LDCC can also be provisioned to support OSI over PPP. Link access protocol on the D channel (LAP-D), a data link protocol used in the OSI protocol stack, provides provisionable parameters when you elect to provision an ONS SDCC as OSI only.
Release 6.0.x TCP/IP and OSI networking employs the following additional features, described in detail in the user documentation.
OSI Connectionless Network Service
OSI connectionless network service is implemented by using the Connectionless Network Protocol (CLNP) and Connectionless Network Service (CLNS). CLNP and CLNS are described in the ISO 8473 standard.
OSI Routing
OSI routing uses a set of routing protocols that allow end system and intermediate system information collection and distribution; a routing information base; and a routing algorithm (shortest path first).
TID Address Resolution Protocol (TARP) is used when TL1 target identifiers (TIDs) must be translated to network service access point (NSAP) addresses.
TCP/IP and OSI Mediation
Two mediation processes, T-TD and FT-TD, facilitate TL1 networking and file transfers between NEs and ONS client computers running TCP/IP and OSI protocol suites.
OSI Virtual Routers
Release 6.0.x supports three OSI virtual routers, provisionable on the Provisioning > OSI > Routers tab.
IP-over-CLNS Tunnels
IP-over-CLNS tunnels are used to encapsulate IP for transport across OSI NEs. Release 6.0.x supports two tunnel types, Generic Routing Encapsulation (GRE) and Cisco IP.
OSI Provisioning in CTC
The following OSI features are provisionable in the CTC node view, Provisioning tab. For full explanations of CTC provisioning for OSI, consult the user documentation.
•OSI setup
•TARP configuration, static TDC, and MAT
•Router setup and subnets
•Communication channels
FLT Secondary State
Release 6.0.x introduces a new secondary service state (SST), Fault (FLT). The FLT secondary state is defined as follows:
•FLT (Fault) The entity has a raised alarm or condition.
The FLT SST is an extension to the existing ONS state model. As such, the FLT state is a Telcordia GR-1093 secondary state. It identifies that the affected entity is OOS because it is faulty. The FLT secondary state affects the service state only. The AdminState (the state you manage the entity into) is not affected. The FLT SST is the result of autonomous action; you cannot manage an entity into the FLT SST. The FLT SST is for retrieval purposes only. An entity's service state will transition into the OOS-AU or OOS-AUMA (AU for autonomous) service state if alarms or conditions are present. The FLT SST is appended to the existing secondary state for the entity when an alarm or condition exists.
Equipment FLT Service State
Some Equipment alarms will not generate an FLT SST transition. If a state already exists to represent the equipment condition, FLT will not be added to the secondary state list:
•MEA-Mismatch of equipment is represented as MEA SST
•IMPROPRMVL-Improper Removal is represented as UEQ SST
•No FLT will be added, and there will be no alarms, when equipment is in AINS
FLT SST with Ports
In pre-6.0 releases, an IS-NR port with an LOS alarm remains as IS-NR service state. There is no service state change to reflect the port is down. A new PST-PSTQ service state is introduced in Release 6.0.x to reflect a port in MT state that is alarmed, OOS-AUMA (Autonomous, Management).
Any port alarm that results in the AINS countdown being inhibited will result in an FLT SST transition for the port. Loopback alarms will not result in an FLT SST transition, as there is a LPBK state to represent this information. There is NO FLT SST in the DSBLD state, as all alarms are cleared in the DSBLD state.
Connection FLT Service State
FLT SST connection changes are the same as for port changes. As with the port, the connection with an alarm in pre-6.0 releases has a service state of IS-NR. A new PST-PSTQ pair is introduced in Release 6.0.x to reflect a cross connect in maintenance with an alarm, OOS-AUMA (Autonomous, Management). Any connection alarm that results in the AINS countdown being inhibited will result in the FLT SST transition for the connection. There is no FLT SST in the DSBLD state, as all alarms are cleared in the DSBLD state.
Manage Pluggable Port Modules
Release 6.0.x adds management for multirate (OC-3/OC-12) pluggable port modules (PPMs) in CTC for the 15310-CL-CTX.
Note Single-rate SFPs are autoprovisioned in the PPM screen.
As of Release 6.0 you can provision or delete a multirate PPM, and you can provision or change optical line rates.
Note You cannot delete a PPM if it is in service, part of a protection group, has a communications channel termination in use, is used as a timing source, has circuits, or has overhead circuits.
Change Pluggable Port Module Service States
On the 15310-CL-CTX card, the PPM port is equivalent to an optical port. To change a PPM port's service state you can follow the same procedure as in changing any port's service state (refer to the user documentation for this procedure).
Cisco Service Assurance Agent ML-Series Support
The Cisco Service Assurance Agent (SAA) is an application-aware synthetic operation agent that monitors network performance, especially IP SLAs. Performance can be measured between any Cisco device that supports this feature and any remote IP host (server), Cisco routing device, or mainframe host. Performance measurement statistics provided by this feature can be used for troubleshooting, for problem analysis, and for designing network topologies.
The Cisco SAA can be especially useful for enterprise and service provider networks, because it provides expanded measurement and management capabilities. In particular, the Cisco SAA is a reliable mechanism for accurately monitoring the metrics in SLAs.
Because Cisco SAA is accessible using SNMP, it also can be used in performance monitoring applications for network management systems (NMSs) such as CiscoWorks2000 (CiscoWorks Blue) and the Internetwork Performance Monitor (IPM). SAA notifications also can be enabled through Systems Network Architecture (SNA) network management vector transport (NMVT) for applications such as NetView.
For information on configuring the Cisco SAA to provide advanced network service monitoring information, see the "Network Monitoring Using Cisco Service Assurance Agent" chapter of the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2.
Cisco Service Assurance Agent on the ML-Series
As of Release 6.0, the ML-Series card has a complete IP SLA Cisco IOS subsystem and offers all the normal features and functions available in Cisco IOS Release 12.2S. It uses the standard IP SLA Cisco IOS CLI commands. SNMP support is equivalent to the support provided in the IP SLA subsystem 12.2(S), which is the rttMon MIB.
The following restrictions apply for ML-Series card operation with Cisco SAA.
The ML-Series card supports only features in the Cisco IOS 12.2S branch. It does not support functions available in future Cisco IOS versions, such as the IP SLA accuracy feature or the enhanced Cisco IOS CLI support with updated IP SLA nomenclature.
Setting the CoS bits is supported, but set CoS bits are not honored when leaving or entering the CPU when the sender or responder is an ONS 15454, ONS 15454 SDH or ONS 15310-CL platform. Set CoS bits are honored in intermediate ONS nodes.
On RPR, the direction of the data flow for the IP SLA packet might differ from the direction of customer traffic.
CTC Launcher
Release 6.0.x introduces the CTC Launcher utility, CtcLauncher.jar. The CTC Launcher utility can be used to launch CTC and manage an ONS node running Release 6.0 or higher.
CTC Launcher provides two connection options. First, it can be used to access ONS NEs that have IP connectivity to the CTC computer. Second, CTC Launcher can establish connectivity to ONS NEs that reside behind a third party, OSI-based GNE. To create a connection through the OSI-based GNE, CTC Launcher creates a TL1 tunnel. This tunnel is similar to the static IP-over-CLNS tunnels that are available in CTC Release 6.0.x. (For information about IP-over-CLNS tunnels, refer to the Release 6.0 ONS product documentation.) However, unlike the static IP-over-CLNS tunnels, the TL1 tunnel does not require provisioning on the third party GNE, the DCN routers, or the ONS NEs. The tunnel connection is created using the CTC Launcher. It can then be managed using CTC.
Note To establish a TL1 tunnel, the ONS node behind the GNE must be running Release 6.0 or higher.
Prior to using the CTC Launcher utility, the CTC jar files must be precached, either from the installation CD, using the LDCACHE utility, or from the node, by launching CTC from a web browser. For installation instructions for the CTC Launcher utility, consult the Readme file. The CtcLauncher.jar utility and the CtcLauncher-README.txt file are located in the CtcLauncher directory on the R6.0.x software CD. For additional information about CTC Launcher, refer to the CTC Launcher Application Guide. To access the application guide:
Step 1 Go to http://www.cisco.com.
Step 2 Choose Technical Support & Documentation.
Step 3 Choose Optical Networking.
Step 4 Choose the ONS 15300, ONS 15400, or ONS 15600 product category.
Step 5 Choose the Configuration Guides category.
Step 6 Click the CTC Launcher Application Guide link under the appropriate product.
TL1 Open GNE
TL1 supports the ability to act as a GNE or ENE to an OEM IP DCN (foreign) connected node that also uses TL1. To accomplish TL1 GNE-ENE interoperability, the DCN communication path between the GNE and ENE employs PPP and OSPF in a non-proprietary manner, while ensuring that these connections remain secure. Open GNE TL1 functionality enables you to configure DCC terminations to interoperate with a system on the far end that does not support proprietary PPP vendor extensions or OSPF types.
Open GNE Commands
The following commands support TL1 open GNE. For input and output formats and parameters, plus examples of how to use each command, consult the user documentation.
This command is used to instruct a Gateway NE to return the entries of the TADRMAP. One row is used for each displayed TID name.
This command is used to instruct a Gateway NE to delete an entry in the table which maps the TIDs of the subtending NEs to their addresses. The OSs will address the subtending NEs using the TID in TL1 messages and a Gateway NE will address these NEs using IP Addresses or NSAPs. This table, which resides in a Gateway NE, correlates a TID and an address.
This command is used to instruct a Gateway NE to create an entry in the table which maps the TIDs of the subtending NEs to their addresses. The OSs will address the subtending NEs using the TID in TL1 messages and a Gateway NE will address these NEs using IP Addresses or NSAPs. This table, which resides in a Gateway NE, correlates a TID and an address. This command requires that at least one of (IPADDR or NSAP) be specified.
This command is used to create a proxy tunnel.
This command is used to delete a proxy tunnel.
This command is used to a view the proxy tunnels contained in the NE proxy table.
This command is used to create a firewall tunnel.
This command is used to a delete a firewall tunnel.
This command is used to a view the firewall tunnels contained in the NE proxy table.
Changed Commands for Open GNE
The following previously-existing TL1 commands support new parameters for open GNE.
•foreignFarEnd—Input parameter used to indicate that the far end NE on the DCC is a foreign NE.
•foreignIPAddress—Input parameter specifying the IP Address of the far end Node on the DCC. Used only if foreignFarEnd is `Y'.
•foreignFarEnd—Output parameter used to indicate that the far end NE on the DCC is a foreign NE.
•foreignIPAddress—Output parameter specifying the IP Address of the far end Node on the DCC. Used only if foreignFarEnd is `Y'.
The following command has been modified to support open GNE as described.
Generate an update after an addition to or deletion from the TADRMAP or an addition or deletion of a firewall or proxy tunnel. The ENT-TADRMAP, DLT-TADRMAP, ENT-TUNNEL-PROXY, DLT-TUNNEL-PROXY, ENT-TUNNEL-FIREWALL, and DLT-TUNNEL-FIREWALL commands each generate an appropriate REPT^DBCHG message.
New Card Support
The following new card is supported by TL1 in Release 6.0.x.
•Detectable filler card
TL1 Command Changes
New Commands
The following new TL1 commands are added for Release 6.0.x.
Command Syntax Changes
The syntax of the following commands is changed in Release 6.0.x.
Note These changes apply to all ONS platforms.
COPY-IOSCFG syntax:
Is changed to:
COPY-RFILE syntax:
Is changed to:
DLT-ROUTE syntax:
Is changed to:
ED-10GIGE syntax:
Is changed to:
ED-BITS syntax:
Is changed to:
ED-CRS-STS-PATH syntax:
Is changed to:
ED-E1 syntax:
Is changed to:
ED-EC1 syntax:
Is changed to:
ED-FFP-MOD2 syntax:
Is changed to:
ED-G1000 syntax:
Is changed to:
ED-GIGE syntax:
Is changed to:
ED-NE-GEN syntax:
Is changed to:
ED-POS syntax:
Is changed to:
ED-T1 syntax:
Is changed to:
ED-T3 syntax:
Is changed to:
ED-VC3 syntax:
Is changed to:
ED-VT1 syntax:
Is changed to:
ED-VT2 syntax:
Is changed to:
ENT-EQPT syntax:
Is changed to:
ENT-ROLL syntax:
Is changed to:
SET-ATTR-SECUDFLT syntax:
Is changed to:
Miscellaneous syntax changes:
Is changed to:
Is changed to:
Command Response Changes
The following TL1 responses have changed in Release 6.0.x.
Note These changes apply to all ONS platforms.
RTRV-10GIGE response:
Is changed to:
RTRV-DS3I response:
Is changed to:
RTRV-E1 response:
Is changed to:
RTRV-E3 response:
Is changed to:
RTRV-E4 response:
Is changed to:
RTRV-EC1 response:
Is changed to:
RTRV-EQPT response:
Is changed to:
RTRV-FSTE response:
Is changed to:
RTRV-GIGE response:
Is changed to:
RTRV-INV response:
<aid>,<aidtype>::[<plugtype>],[<pn>],[<hwrev>],[<fwrev>],[<sn>],[<clei>],[<twl1=nwl in code>],[<twl2= wl1 in code>],[<twl3=wl2 in code>],[<twl4=wl3 in code>],[<pluginvendorid>],[<pluginpn>],[<pluginhwrev>],[<pluginfwrev>],[<pluginsn>],[<ilossref>],[<productId>],[<versionId>],[<fpgaVersion>]
Is changed to:
<aid>,<aidtype>::[<pn>],[<hwrev>],[<fwrev>],[<sn>],[<clei>],[<twl1=nwl in code>],[<pluginvendorid>],[<pluginpn>],[<pluginhwrev>],[<pluginfwrev>],[<pluginsn>],[<ilossref>],[<productId>],[<versionId>],[<fpgaVersion>]
RTRV-STM1E response:
Is changed to:
RTRV-T1 response:
Is changed to:
RTRV-VT2 response:
Is changed to:
SET-TOD response:
Is changed to:
TL1 ENUM Changes
Note These changes apply to all ONS platforms.
TL1 ENUM Types Changed
The following enum types have been merged into the EQUIPMENT_TYPE enum type.
TL1 ENUM Items Added or Removed
The following section, including Table 1 through Table 29, highlights ENUM items changed (added or removed) for Release 6.0.x, by ENUM type.
Table 1 ADDRTYPE enum items added to Release 6.0.x
ENUM Name ENUM Value ADDRTYPE_ENUM_IP
ADDRTYPE is used in the following commands:
Table 2 CARDMODE enum items added to Release 6.0.x
ENUM Name ENUM Value CARDMODE_DS1E1_DS1ONLY
CARDMODE is used in the following commands:
Table 3 DL_TYPE enum items added to Release 6.0.x
ENUM Name ENUM Value DL_TYPE_ACCEPT
DL_TYPE is used in the following commands:
Table 4 ENCODING enum items added to Release 6.0.x
ENUM Name ENUM Value ENCODING_ENUM_LV
ENCODING is used in the following commands:
ENV_ALM is used in the following commands:
EQUIPMENT_TYPE is used in the following commands:
EQPT_TYPE is used in the following command response:
Table 8 FC_LINKRATE enum items dropped from Release 5.0.x
ENUM Name ENUM Value FC_LINKRATE_1GFC
FC_LINKRATE is used in the following commands:
Table 9 FC_LINKRATE enum items added to Release 6.0.x
ENUM Name ENUM Value FC_LINKRATE_1GBPS
FC_LINKRATE is used in the following commands:
Table 10 FRAME_FORMAT enum items added to Release 6.0.x
ENUM Name ENUM Value FRAME_FORMAT_LT_JESF
FRAME_FORMAT is used in the following commands:
Table 11 LO_XC_MODE enum items added to Release 6.0.x
ENUM Name ENUM Value LO_XC_MODE_MIXED
LO_XC_MODE is used in the following commands:
Table 12 LPBK_TYPE enum items dropped from Release 5.0.x
ENUM Name ENUM Value LPBK_TYPE_FE_CMD_ESF_PAYLD_LPBK
FC_LINKRATE is used in the following commands:
Table 13 LPBK_TYPE enum items added to Release 6.0.x
ENUM Name ENUM Value LPBK_TYPE_FE_CMD_ESF_PAYLD_LPBK
LPBK_TYPE is used in the following commands:
MOD2 is used in the following commands:
MOD2ALM is used in the following commands:
Table 16 MOD2B enum items added to Release 6.0.x
ENUM Name ENUM Value MOD2B_M2_TSC
MOD2B is used in the following commands:
MOD_PATH is used in the following commands:
OPTICAL_WLEN is used in the following commands:
Table 19 OPTICS enum items added to Release 6.0.x
ENUM Name ENUM Value OPTICS_OP_100_BASE_FX
OPTICS is used in the following commands:
Table 20 PROTOCOLAID enum items added to Release 6.0.x
ENUM Name ENUM Value PROTOCOLAID_EMS
PROTOCOLAID is used in the following commands:
Table 21 PROTOCOLSTAT enum items added to Release 6.0.x
ENUM Name ENUM Value PROTOCOLSTAT_DISABLED
PROTOCOLSTAT is used in the following commands:
REACH is used in the following commands:
REQTYPE is used in the following commands:
RFILE is used in the following commands:
Table 25 SYNCMAP enum items added to Release 6.0.x
ENUM Name ENUM Value SYNCMAP_ASYNC
SYNCMAP is used in the following commands:
Table 26 SYNC_CLOCK_REF_QUALITY_LEVEL enum items dropped from Release 5.0.x
ENUM Name ENUM Value SYNC_CLOCK_REF_QUALITY_LEVEL_QREF_RES_SDH
SYNC_CLOCK_REF_QUALITY_LEVEL is used in the following commands:
TIDADRMODE is used in the following commands:
Table 28 TRANSMODE enum items added to Release 6.0.x
ENUM Name ENUM Value TRANSMODE_AU3
TRANSMODE is used in the following commands:
Table 29 VTMAP enum items added to Release 6.0.x
ENUM Name ENUM Value VTMAP_GR253
VTMAP is used in the following commands:
Related Documentation
Release-Specific Documents
•Release Notes for the Cisco ONS 15310-CL, Release 6.0
•Release Notes for the Cisco ONS 15454 SDH, Release 6.0.1
•Release Notes for the Cisco ONS 15327, Release 6.0.1
•Release Notes for the Cisco ONS 15600, Release 6.0.1
•Release Notes for the Cisco ONS 15454, Release 6.0.1
Platform-Specific Documents
•Cisco ONS 15310-CL Procedure Guide
Provides installation, turn up, test, and maintenance procedures•Cisco ONS 15310-CL Reference Manual
Provides technical reference information for SONET/SDH cards, nodes, and networks•Cisco ONS 15310-CL Troubleshooting Guide
Provides a list of SONET alarms and troubleshooting procedures, general troubleshooting information, and hardware replacement procedures•Cisco ONS SONET TL1 Command Guide
Provides a comprehensive list of TL1 commandsObtaining Optical Networking Information
This section contains information that is specific to optical networking products. For information that pertains to all of Cisco, refer to the Obtaining Documentation and Submitting a Service Request section.
Where to Find Safety and Warning Information
For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product. This publication describes the international agency compliance and safety information for the Cisco ONS 15310 system. It also includes translations of the safety warnings that appear in the ONS 15310 system documentation.
Cisco Optical Networking Product Documentation CD-ROM
Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM is updated periodically and may be more current than printed documentation.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.


text:
Can fat people go skinny dipping?
Can you be a closet claustrophobic?
Why is the word "abbreviation" so long?
Is it possible to be totally partial?
What's another word for thesaurus?
If a book about failures doesn't sell is it a success?
If a funeral procession is at night, do folks drive with their lights off?
When companies ship Styrofoam, what do they pack it in?
If you are cross-eyed and have dyslexia, can you read all right?
If a stealth bomber crashes in a forest is there a sound?
If a parsley farmer is sued, do they garnish his wages?
I found myself drowning in an ocean made out of orange soda yesterday.
It took me a while to work out it was just a Fanta sea.
I apologize in advance for this.
A man walked into the bar at a hotel that was hosting a convention of personal hygiene product salesmen. He sat down at a table with some of his fellow salesmen.
Immediately one of the other salesmen says to him: "Hey Bill! We were just talking about you. Your territory sucks! Nobody was ever able to make a living in it before you. But now, you son-of-a-gun, you win the all-expense-paid trip to Vegas three years in a row, selling almost twice as much as anyone else in the whole Southwest region! How in the heck do you do it?"
Bill replied, "Its easy! I take a big engraved silver bowl and fill it up with fresh dog crap. Next I garnish it carefully with parsley sprigs, celery stalks, scallions, olives and thin-sliced red bell pepper rings. I take this to the airport and set it on a table on an elegantly embroidered white tablecloth. I serve samples on co cktail wafers to all who pass by. As soon as someone takes a bite they usually say 'Jesus Christ!! This stuff tastes like CRAP!!'
I reply 'Yes sir! That's what it is!
Would you care to buy a toothbrush?"
OMG, Rawr!!!
Good thing you gave us a caveat!
I think you need to apologize some more. That's a crap joke.
Nope. I'm only allocated one apology per crap joke.
Lmao @ bobcat, thank you.
Please don't use the name "Pete" in such a way. It annoys me.
Good grief.
Nah, just a gentle jest from the Chavez thread. I have forgotten you lack a sense of humor.
I see that IT is, damn him.

subset: commoncrawl


text:
The Nasha actor feels that her latest erotic movie has been given a raw deal by multiplex owners
While her debut vehicle Nasha is doing well in single theatres, Poonam Pandey says her film has been deliberately kept out of multiplexes. "It is sad that our film is not playing in any multiplex in Mumbai," said Pandey and added, "Director Amit Saxena had packaged the film for multiplex audiences. We are a victim of the politics of other big production houses."
The Pandey babe explains further, "We haven't got screens in multiplexes. Still our film was housefull wherever it was released, although we got fewer shows than expected. Our film got the best opening among all the releases last week."
A source from one of the leading multiplex chains in Mumbai admitted that Nasha was boycotted. "There were too many releases this week. And Bhaag Milkha Bhaag is still doing well. We just didn't have any slots for Nasha," said the source.


text:
Victek RAF Releases 1.25 Tomato by... :thumbup: Victek 1.25.8515 RAF ND is ready... ;^) THIS IS A TEST VERSION!!! ************************************************** TRX Image: Total Size .... : 3235840 (3160.00K) Images ...... : 3233088 Padding ..... : 2752 CRC-32 ........ : C6DA48D6 128K Blocks ... : 25 Offsets: 0: 0x0000001C 1: 0x000A8540 2: 0x00000000 ----------------- 1.25.8515 RAF ND ready ----------------- ************************************************** The test version is ready in... http://victek.is-a-geek.com/tomato.html .. in Test Version section Cheers!!!
Changelog: _ DNSMasq 2.49 _ Busybox 1.14.2 _ Passive mode for Wireless Survey _ Regulatory mode for wireless _ Wireless Auto channel by default _ TCP_Conntrack up to 8192 connection _ Allow multiple MAC address per device _ SSH remote forwarding allowed _ More precise match for l7 ftp pattern _ Miniupnpd updated to ver. 20090605 _ Wan_is_a_LAN feature included when WAN is disabled _ All the features of Official Tomato 1.25 _ All the features of Tomato RAF _ ND version with wireless driver 220.127.116.11 _ 140 IP/MAC in restriction table _ 140 IP/MAC limit in IP/MAC limiter _ ... and a lot of testing hours by 12 people before release .. , Thanks for facilitate me the access to check the logfiles. The source code is available in the same page, Source code section. PS. Amber and White LED enabler are gone in this release. The owner of offical Tomato removed it from the original release. Thanks.
Will the ".5" release be made available for testing? (I see it in your sig... hehe). I have GLs, TMs, and Buffalo routers. I can test it further....
Thanks Victek! Just installed, and will test this version now! So far so good! I really liked the scheme!
1.25.8515 seems to be working great over here. Haven't tested wireless yet...Vic.. Just out of curiosity, what are the wireless issues that have been reported?
Momentarily a new wlan0:1 with BSSID '___.__' appear and then dissipate ...(I'm working in up to three wlan creation) when channel 12 is used. Nothing to be concern but has to be fix in the next r1.
Btw, I dunno whether it is a bug or not, but the option "Show icon on browser" is missing at the Admin Access page.
It's still enabled by default. The checkbox has been removed by Jon (in 1.25), it's not Victek's doing.
Nice to hear it!, the next test version is already running with nocat functional, let's wait some days. I'm very confidence this version will make a hit for the Tomato community keeping the spirit of integrity and open relation. :biggrin:
I have had some unusual behaviour with the wireless channel scan. My first scan after reboot paused for a while and then a dialogue box appeared with 'error: unknown' (I'm sure that is what it said, unfortunately I closed it before thinking to note the exact message). The second and third scans both worked fine so probably an anomaly. Upgraded from 1.23 to 1.25 on Buffalo WHR-HP-G54. No problems so far. Thanks for all the work Vicktek!
I knew it, you did a Wireless Survey when the Ground electrical offset was setting the value, nothing to get worried, you got first time and then the adjustment is fixed. This was the second issue repported. No worries.
Does this mean you're implementing dual and triple SSID? If this is the case you are THE MAN. I have been waiting for this feature in Tomato for a while
Running since early yesterday on Buffalo WHR-HP-G54. No issues to report... Trying to bash at it a bit to see what happens...
I'm noticing a lot of "unknown daemon.err miniupnpd[1513]: recv (state0): Connection reset by peer" messages in my log. Any ideas?
Report from my friend with a WRT54G v2 (corerev=7) using this test build with only 1 wireless client and 3 wired clients. He said it is fine, no problems at all. I will wait for a few more days and check with him again how it is going and will report back here. And mine is up and running just fine.
- For Static DHCP I used names with blanks in it and the names are not shown complete. The second entry is named "Noxon iRadio" and it's not complete. It's a bug? - Is it possible to write the text on the right side from the radio buttons? The version works fine at the moment. I have a WRT54G v2.2 with core =7. :thumbup:
Unable to upgrade. Vic, I'm not able to upgrade from v1.23.8515 .5 RAF ND to 1.25.8515 RAF ND on my Buffalo WHR-G54S I keep getting: "File contains an invalid header" Any thoughts?
I have a friend who uses a Linksys USB 54G hub for his wireless device. Trying it this afternoon with Victek's .25 ND. Disconnects every few seconds, connects-gets IP-synchs with WPA personal AES. Last about 60 seconds, disconnects. Back to .23 non-ND version and connection is stable, fast, solid. This one: http://www.linksysbycisco.com/US/en/products/WUSB54G Tried both XP's Wireless Config Util and Linksys's util. No difference until back to .23 non-ND versions. What's with everything being centered again?
Yes, you're right, some may browse this site from work where they have no choice over what browser they use. Didn't think of it this way. Sorry. Eh well, maybe the site owners will patch the theme up so it will look as it should under IE8 too. Sorry for the off-topic.
Larix, Mine is working just fine, I have one entry in my device list that shows just fine the name with space.
I use Firefox 3.5 and not the IE8. I have reset the nvram before I have flashed the router. To test, I have erased the nvram again but the Name of my clients in Device List is not shown complete. ;( Noxon iRadio is shown as Noxon. From the log file. Code: Jan 1 01:00:11 stargate daemon.info dnsmasq-dhcp[107]: DHCPREQUEST(br0) 192.xxx.xx.xx xx:xx:xx:xx:xx:xx Jan 1 01:00:11 stargate daemon.info dnsmasq-dhcp[107]: DHCPACK(br0) 192.xxx.xx.xx xx:xx:xx:xx:xx:xx Noxon The x are from me.
bandwidth stats (daily, weekly, monthly) doesn't work for me anymore. i've tried storing the stuff in nvram (was (perfectly writable) cifs storage before), resetting the bandwidth data, but it just doesn't want to count a current day/week/month. this started not working with raf 1.23, sometime in may. halp, o gracious victek!
Victek, Thank you for an awesome firmware. Any chance of integrating the iptables time module extension in Tomato RAF? Thanks.
Yes. Maybe the USB device though. Still playing. While it seemed to be stable with the .23 non-nd version I had trouble this morning. Had to get to work so could not fully investigate.
hi, Have a PPPOE connection with my ADSL provider, I loaded this new version on my WRT54G v2 (with wireless version 7). But I immediately could not connect to my dsl modem, so I remember reading about the WAN port speed being an issue at AUTO mode so I changed it to 10mb/half duplex and it works now. Is this still a bug? edit. nvm might be an issue with my ISP, peer1 had a ups battery blow up in their location here in Toronto (17 fire trucks!) and internet was down all night, I guess the authentication servers are still having massive loads on them as many modems try to connect back up. I will do some testing this afternoon to see if the WAN port issue is still an issue. edit 2. so it was an isp issue, not a firmware issue. Set it back to Auto and no problems. THANKS! will report any further problems.
Thanks mau108 .. with your explanation I lived as CNN news the issue in Toronto, LOL. Glad it works without any issue.
Victek when did avaiblable firmware 1.25 with USB IP/MAC Limiter RAF version ?? Maybe you can add something wget gui to this firmware ?? Sorry for my english
Pepe, It's not the goal of RAF version since the target router are not jukebox neither USB available, all the features in RAF version are linked to networking/routing, ask Teddy_Bear about, your wish/demand is targeted to his branch.
you might want to take a look at http://www.linksysinfo.org/forums/showthread.php?t=62234 i guess it contains all you need, albeit still being on 1.23.
hi Victek, A feature request, I saw this option on the FIXPPP version of Tomato for those that are doing MLPPP, all you do is put in the ip of the modem and it allows us to use our dsl modem's stats software to connect directly to the modem.... Can you add such a feature???
I don't understand.. what do you want to see/run? look the módem GUI from your local network? And please, all the features request is suggested to be hanged in Tomato wishes post. Thanks
Im requiring frequent reboots on my WHR-HP-G54 to get my connection back to full speed. For example, tonight I noticed my connection wasn't great earlier so I did a speed test and it was about 1/5 what it should have been. Rebooted the router, did another speed test and was fine. About 3 hours later same problem. I was the only client and traffic was all browsing and some Xbox there was no p2p. Connection when bad: Connection after reboot: Realtime graphs in tomato showed approximately the same speeds reported by speedtest.net so I dont think it's not something else using up the bandwidth. Nothing in logs. I think i will have to go back to 1.23 if it happens again.
Here is a direct quote from fixppp ""Route Modem IP" textbox: Enter the IP of the modem connected to the WAN port here in order to enable access to your modem from the LAN. Devices on your LAN should then be able to access the modem using its IP address. Useful for accessing the modem with DMT, telnet, or a web browser."
I'm also seeing some slow down in connection speeds since the upgrade. I've been video editing (encoding) and surfing at the same time. Not sure if its the processor being overwork but I can see a huge slowdown. I rebooted the PC at one stage and everything came back, will keep a closer eye on the speeds next time
if speeds came back after reboot, it cannot be the router as rebooting the machine does not have any effect on the router. I am using DSL and do not see this slow down at all....all great, its been up for all of 1 day, 12:16:11 with connection up time of 1 day, 12:16:14 (off by 3 seconds due to my copy and paste time lol)
This will be for DSL users using pppoe bridge modems. There's a number of working alternatives - assign a secondary IP to the WAN port in the correct modem range in the init script, and then add a nat MASQUERADE command in firewall script.
Do it simple, if your modem IP is 192.168.1.1 then put this script in Administration/Firewall tab: /usr/sbin/iptables -I POSTROUTING -t nat -o vlan1 -d 192.168.1.0/24 -j MASQUERADE ip addr add 192.168.1.2/24 dev vlan1 brd + Save, Reboot and you can access your modem... no need special GUI for it... easy :biggrin:
Is it possible to add a second WLAN? A virtual WLAN with own security options. I want like to add my nintendo ds into the wlan, but the Nintendo DS support WEP only. I don't want change the WAP2 to WEP and back... ;( A nice feature would a second WLAN that is possible disable without change the first WLAN. And it would be nice if that is possible to disable the reconnect after change WLAN options in the "Basic"-Options.
Larix & Galileo2000, I think there is one post in the forum for 'Tomato wishes' (Der Kief should fix it probably), I think is the right place to make all these request visible for the Tomato team of developer and of course... for the owner of Tomato. Thank you
Hi Victek, My modem ip is either 192.168.1.254 or 10.0.0.38 (it responds to both), what would the command be, hard to follow what the above script means....
Nice to see this new version out. Thanks Victek! I have been out of the loop for a week with out internet. Just moved into a new place. Is every one liking this new version? Thinking about upgrading.... I remember reading some small kinks with 1.25 Was you able to fix those up Victek in the new release you have out?
Yes, stable and lighting fast release, till now two problems in wireless section but not at operational level.
This script creates a virtual LAN able to establish a communication between your LAN and modem LAN. Use the IP you like if both IP's are operational ... then if you want to use 192.168.1.254 the script I wrote is OK.
Yes, thanks. You rox! Just one small quesion i would like to ask You and maybe one small advice i need AS You probably already know i have ADSL 2048/512. It has dynamic IP and the session expires after 48h. I configured router to auto-reconenct every 24hours, to make session not expiring and to change IP. I use both QOS and IP/MAC BW Limiter. All seems to work damn well and i cannot say at least one wrong word about it. However after reconnection all QOS rules seems to be inactive. I found a dirty solution for it... I need to connect with router via SSH and type 'service qos restart' and that helps! So decided to use WAN UP script: at this solves my problem at all. So there is no problem so far Just i cannot stand why QOS needs to be restarted... And that is small quiz for You
... bizarre bug .. one question? .. Do you use Administration/scheduler and Reconnect function to do that? .. just to know where I have to start finding... damm.. QoS fail but not IP/MAC limiter... strange .. but logical (I do not restart qos_limiter service after wanup and I don't know why QoS in original Tomato has to be restarted.. or stopped...). By the way .. 300 seconds are needed to wait after wanup to fix the issue ? Thanks
Vic, Just wondering what the 1.25.8515.5 in your sig comes from? I only see 1.25.8515 on your site. Is there a bugfix release coming up? Sorry if this has been asked before.
@Victek: It does not matter if i disconnect and connect myself (Status->Overview) or if it reconnect automatically (Administration->Scheduler). I set reconnect to 4:00am. so about 4:05am everything should be fine again. This is a time where noone uses the Internet. I have not tested shorted delay, but would probably also work as i disconnect, wait few secs, connect, wait few secs, connect via ssh and type the magic command... Then everything seems to work ok. Things i noticed when i reconenct and DO NOT restart qos: 1) QOS do not work -> i download eg 230KB/s (as limit is set), but eg ICMP is not prioritarized (so i think qos is down) 2) I cannot join game servers (Americas Army & rFactor join time outs; some games do not find any servers). However web server is working. So i think port forwarding works, and other are closed and all traffic stopped? Hard to explain. If something is unclear, please ask questions. I will do my best to help You in providing usefull data Whatever everything works well and damn stable if i restart qos. I set reconnect to 4am mon-fri and sun and router reboot at 4am on Saturday So 5mins after reconnect it restarts qos and everything works then. I will see if it will work after router restart, but i think it also works well. Yesterday it was a thunderstorm here and i had a power loss, so router automatically powered off - today it works again like a charm. But as i said i think restarting qos should be not necessary (however now its not a big deal for me).
not a bug... it was removed by Jon. You can type: led amber on in a SSH or telnet terminal, the light will turn on and stay on. You could also add it to your init script.
Vic, can we consider this release "stable" then or still "testing"... I mean - would you recommend flashing it to a general public...
Awesome. Fast and stable. :thumbups: I have an idea for an enhancement - would it be possible to have a secondary web server on the device that could host a single page with a patterned jpg etc. so that ad blocking scripts could redirect to that address? This could eliminate unloaded banners, by replacing them with an image of the user's choosing.
NocatSplash is, from what I understand from the dd-wrt wiki, used to redirect new requests to a T&C type page prior to letting them on the network. Could that be used to host a splash page on the router and simply redirect any requests for adware and banners to that splash page? I have something like this running but using a second linux box where the 404err page has been modified. For example, the results are as follows:
Yes, it can be done.. If I know how to go it!! , but in the chinesse release it works also in the way you show.
It works on the WL-520GU. The only downside is that the USB feature is not there. From what I've read Victek may not create USB support of this version....
Just upgraded. Very nice! I am really digging the auto channel selection feature. Way to cool. Thanks Victek!
hi , just a small bit of feedback with v1.25.8515RAF ND on an ASUS WL500GP V2 - the AIR LED stays lit even if wireless is disabled. Nice build, thankyou Victek!
Yes, please use the button toggle wireless function to enable/disable wireless, it's quicker than enable/disable through GUI menu every time.
I'm having some problems with 1.25 :-( My router with 1.25.8515 has been up for 2 days, 22:23 and has only 25.28% of memory left. And that's with counting cache as free memory. Without cache as free memory only 5.11% or memory left. I've looked at logs. Most of them are just dhcp requests and log marks, but this one section looks weird. The following log piece repeats itself about 11 times in a row. This is the first instance, I just didn't want to copy-paste 11 copies of it: Code: Jul 8 12:39:35 localhost daemon.info dnsmasq[96]: exiting on receipt of SIGTERM Jul 8 12:39:35 localhost user.notice kernel: klogd: exiting Jul 8 12:39:35 localhost syslog.info syslogd exiting Jul 8 12:39:38 localhost syslog.info syslogd started: BusyBox v1.14.2 Jul 8 12:39:38 localhost user.notice kernel: klogd started: BusyBox v1.14.2 (2009-07-02 18:01:37 CEST) Jul 8 12:39:38 localhost user.info kernel: vlan1: del 01:00:5e:00:00:01 mcast address from master interface Jul 8 12:39:38 localhost user.info kernel: vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface Jul 8 12:39:38 localhost user.info kernel: br0: port 2(eth1) entering disabled state Jul 8 12:39:38 localhost user.info kernel: br0: port 1(vlan0) entering disabled state Jul 8 12:39:38 localhost user.info kernel: br0: port 1(vlan0) entering disabled state Jul 8 12:39:38 localhost user.info kernel: device vlan0 left promiscuous mode Jul 8 12:39:38 localhost user.info kernel: br0: port 2(eth1) entering disabled state Jul 8 12:39:38 localhost user.info kernel: device eth1 left promiscuous mode Jul 8 12:39:38 localhost user.info kernel: device eth1 entered promiscuous mode Jul 8 12:39:38 localhost user.info kernel: br0: port 2(eth1) entering learning state Jul 8 12:39:38 localhost user.info kernel: br0: port 1(vlan0) entering learning state Jul 8 12:39:38 localhost user.info kernel: br0: port 2(eth1) entering forwarding state Jul 8 12:39:38 localhost user.info kernel: br0: topology change detected, propagating Jul 8 12:39:38 localhost user.warn kernel: vlan1: Setting MAC address to 00 23 69 49 17 92. Jul 8 12:39:38 localhost user.info kernel: br0: port 1(vlan0) entering forwarding state Jul 8 12:39:38 localhost user.info kernel: br0: topology change detected, propagating Jul 8 12:39:38 localhost user.info kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface Jul 8 12:39:39 localhost daemon.info dnsmasq[8141]: started, version 2.49 cachesize 150 Jul 8 12:39:39 localhost daemon.info dnsmasq[8141]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-TFTP Jul 8 12:39:39 localhost daemon.info dnsmasq-dhcp[8141]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d Jul 8 12:39:39 localhost daemon.info dnsmasq[8141]: reading /etc/resolv.dnsmasq Jul 8 12:39:39 localhost daemon.info dnsmasq[8141]: using nameserver 18.104.22.168#53 Jul 8 12:39:39 localhost daemon.info dnsmasq[8141]: using nameserver 184.108.40.206#53 Jul 8 12:39:39 localhost daemon.info dnsmasq[8141]: read /etc/hosts - 0 addresses Jul 8 12:39:39 localhost daemon.info dnsmasq[8141]: read /etc/hosts.dnsmasq - 9 addresses Jul 8 12:39:39 localhost user.info init[1]: Linksys WRT54G/GS/GL Jul 8 12:39:39 localhost cron.err crond[8145]: crond (busybox 1.14.2) started, log level 9 Jul 8 12:39:39 localhost daemon.info dnsmasq[8141]: exiting on receipt of SIGTERM Jul 8 12:39:39 localhost daemon.info dnsmasq[8157]: started, version 2.49 cachesize 150 Jul 8 12:39:39 localhost daemon.info dnsmasq[8157]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-TFTP Jul 8 12:39:39 localhost daemon.info dnsmasq-dhcp[8157]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d Jul 8 12:39:39 localhost daemon.info dnsmasq[8157]: reading /etc/resolv.dnsmasq Jul 8 12:39:39 localhost daemon.info dnsmasq[8157]: using nameserver 188.8.131.52#53 Jul 8 12:39:39 localhost daemon.info dnsmasq[8157]: using nameserver 184.108.40.206#53 Jul 8 12:39:39 localhost daemon.info dnsmasq[8157]: read /etc/hosts - 0 addresses Jul 8 12:39:40 localhost daemon.info dnsmasq[8157]: read /etc/hosts.dnsmasq - 9 addresses
OK here is a stupid question. Can I use the TRX to upgrade through the GUI? I have always used bin files up till now and I'm not sure what to do. On a WRT54GL by the way.
Nothing strange on the log, the memory leak is related with multiple out/in connection, can you confirm?
Honestly you can just rename the .trx to .bin and it will work fine. You only need to do that if you're not already running Tomato, as Toastman said. I think the reason it's .trx is because that's the extension that Buffalo routers use for their firmwares, and "technically" the ND firmware is designed for those routers in mind.
Hi Victek, I tried it and when I pinged 192.168.1.254 I get 192.168.1.101 destination host unreachable and DMT still isn't connecting to my modem.
Victek, I had asked this a few posts back but again, is there any plan for a 1.25 RAF non-ND firmware? The reason is that I found for my WRT54GL if I use channel 11 (which seems to be the only reliable channel for me in my household), increasing the transmit power to 150 mW only has an effect if I am using the non-ND firmware. I tried the current 1.25 RAF ND and the previous 1.23 RAF ND and in both cases with channel 11 and transmit power to 150, it had no effect on signal strength from the default. As soon as I put back the 1.23 non-ND firmware and same settings, signal strength goes up by 10 dB.
Yes, as for previous RAF releases 1.25.8025 NON ND version will be released. The reason why not yet? Because I'm testing RAF 1.25ND and read some interesting bugs, I would like to release a clean an stable version. By the way.. somebody has seen this message in the logfile?.. Occur when Access restriction rule is active and many http request to the blocked site overflows skbuffer in the router. Code: Jul 10 15:17:49 Victek user.err kernel: vlan: failed to unshare skbuff Jul 10 15:17:50 Victek user.err kernel: layer7: out of memory in match, bailing. Jul 10 15:17:50 Victek user.err kernel: layer7: out of memory in match, bailing. Jul 10 15:17:50 Victek user.err kernel: layer7: out of memory in match, bailing.
A picture worth hundred words... why the speed become 4.2mbps only? previous it shown 100mbps... router is asus wl500gp v1


text:
This document was made possible with support from the Leon Levy Foundation
get citation
The Embassy of Romania in the DPRK reports on China's relations with North Korea following the Blue House Raid and the seizure of the USS Pueblo."Telegram from Pyongyang to Bucharest, TOP SECRET, No. 76.069, Urgent," March 17, 1968, History and Public Policy Program Digital Archive, Political Affairs Fond, Telegrams from Pyongyang, TOP SECRET, 1968, Archive of the Romanian Ministry of Foreign Affairs. Obtained and translated for NKIDP by Eliza Gheorghe. http://digitalarchive.wilsoncenter.org/document/113968 - Share
- Download
English HTML
On March 16, A. Lazar had a conversation with Wang Peng, counselor and Chargé d'affaires of the People's Republic of China, from which we took note of the following important aspects: Contrary to the harsh language used previously by Chinese diplomats toward the DPRK party and state leadership and DPRK internal and foreign policy, it was noticeable that Wang Peng completely changed his approach, having become an active supporter of the forceful line promoted by the DPRK. The Chinese diplomat has repeatedly underlined that the war preparations of the DPRK are welcome, since it is certain that the United States wants to expand the battlefield in Asia, not only in Vietnam, Thailand, and Cambodia, but definitely in Korea as well. He added that the outbreak of war in Korea is inevitable, a logical consequence given that the country cannot remain separated indefinitely and that for the DPRK, this would be a just liberation war. Wang Peng said that as far as he knew, both parties had made intense war preparations, but the sole difficulty was the poor political training of the masses in South Korea, whose training was comparably inferior to the South Vietnamese masses, to withstand a long-term war and offer substantial help to the liberating forces from the North. A. Lazar said that given the situation in both Koreas, he did not contest the possibility of war reigniting, yet the diplomatic corps commented on the idea that the United States had found itself in a preposterous position in Vietnam and that because of the upcoming elections it would be impossible to open a new front in Vietnam. Wang Peng answered that this idea had the potential to demobilize the Korean people and it did not mirror reality, because it was still possible that the Americans would start a war in less than a week or two. We, the Chinese diplomat added, share the conviction of the Korean comrades that war is drawing near and the People's Republic of China has repeatedly declared that it would grant its full support to the DPRK. A. Lazar added that it was beyond any doubt that in case the DPRK was attacked, it would receive the full support of socialist countries and especially from the People's Republic of China and the Soviet Union. In this respect, the Romanian diplomat added, it seems that Premier Zhou Enlai sent a message to comrade Kim Il Sung in which Zhou Enlai had assured Kim Il Sung of the support of the People's Republic of China in its anti-American struggle. Wang Peng did not deny the existence of a message but with noticeable surprise he said he had not known about such a document, but judging by its essence, it wouldn't be too different from the Chinese governmental declaration released immediately after the incident with the USS Pueblo spy ship. A. Lazar tried to find out more about the results of the recent Sino-Korean economic negotiations. In this respect Wang Peng, just like in our previous conversations with him, avoided giving any concrete facts, figures, but he said that the amount of commercial exchanges for 1968 had increased compared with 1967; that the Chinese, to the best of their abilities, had almost entirely satisfied the demands of the Koreans, especially in terms of coke, coal (2 million, in terms of last year's supplies), cotton, tires, salt supplies, etc. Wang Peng avoided giving a full answer to the question referring to the number and branches in which Chinese specialists are working in the DPRK, but he pointed out that Korean demands for technical-scientific assistance have multiplied lately and these demands include matters related to technical-military items. After pointing out that Sino-Korean bilateral relations have been reinvigorated and that the prospects for mitigating past quarrels are good, Wang Peng said that 'I started to realize that at the basis of Soviet-Korean relations lay no political-ideological principles and the DPRK would have manifested its personality earlier on if it hadn't been tied to the Soviet economic and military aid.' He added that the DPRK would have the opportunity to verify that in the upcoming war, the People's Republic of China would be its most reliable friend. A. Lazar asked whether the Chinese Embassy received the [Romanian] Agerpress bulletin on the consultative meeting in Budapest. Wang Peng thanked us for the respective materials and said that he had been informed about it by the Chinese Ministry of Foreign Affairs and about the position of the Romanian Communist Party at the meeting. After the Romanian diplomat briefly presented the point of view of the Romanian Communist Party adopted by the Central Committee of the RCP on February 14 and the decision adopted on March 1 with respect to the international consultative meeting, Wang Peng said that personally he held in high regard the efforts and the principled position of the RCP at the consultative meeting. Wang Peng added that through the meeting in Budapest the leadership of the Communist Party of the Soviet Union demonstrated yet again its desire to enshrine as urgently as possible the split in the international workers' and communist movement. Signed: N. Popa


text:
By Rabbi Yaakov Dovid Lach A perfect companion for learning Daf Yomi! This breakthrough sefer will truly transform your learning experience. This is a full-color guide to animal anatomy with halachic and scientific discussions. Clearly labeled photographs elucidate the words of the gemara, along with explanation and commentary in English. Provides a detailed, true-to-life documentation of each organ, membrane, bone, and tendon discussed in the Gemarah and Shulchan Oruch. With a complete glossary of terms, index, and an entire chapter devoted to an elucidation of the halachos, aggados, and scientific aspects of Meseches Chullin.
Additional Information
Format | Hardcover |
Ships Free? | Eligible for Free Shipping |
List Price | $39.99 |
Publisher | Feldheim |
Language | Hebrew/ English |


text:
Home » Biology Articles » Biochemistry » Disease Markers That Will Aid Arthritis Research Disease Markers That Will Aid Arthritis ResearchJuly 27, 2009 — A combination of biochemical and MRI markers will allow improved measurement of osteoarthritis (OA) progression. The biomarkers will be useful for the design and interpretation of trials of new disease modifying drugs. Erik Dam, from Nordic Bioscience, Denmark, worked with a team of researchers to develop and evaluate the markers. He said, "Presently, there is no disease-modifying OA drug with a consistent, documented effect despite several clinical attempts in late stage phases. We believe that effective therapies could be demonstrated, if tools were available that allow identification of rapid progressors for inclusion in trials. With this in mind, we investigated whether combinations of biochemical and MRI-based biomarkers might improve diagnosis and prognosis of knee osteoarthritis". Dam and his colleagues included 159 subjects in their trial. After exclusions, a total of 287 knees were measured. At baseline and after 21 months, biochemical (urinary collagen type II C-telopeptide fragment, CTX-II) and MRI-based markers were quantified. MRI markers included cartilage volume, thickness, area, roughness, homogeneity, and curvature in the medial tibio-femoral compartment. Joint space width, the presently accepted marker for population selection in clinical studies, was measured from radiographs. According to Dam, "The best individual diagnostic marker was cartilage roughness and the best individual prognostic marker was homogeneity. The aggregate cartilage longevity marker (combining CTX-II, volume, area, thickness, congruity, roughness, and homogeneity) performed very well both diagnostically and prognostically – and superior to the individual biochemical and MRI markers. We attribute this to the combination of markers with complementary information about cartilage quantity (e.g. volume), quality (e.g. homogeneity), and breakdown (CTX-II) that together allow superior diagnosis/prognosis". The proposed aggregate marker methodology may have a direct impact on the design of clinical studies. The researchers claim, "By allowing the selection of a high risk population, the study sample size can be lowered while still improving the chance of a positive study outcome. This should facilitate the development of effective drugs". Source : BioMed Central rating: 3.67 from 3 votes | updated on: 4 Feb 2010 | views: 5077 | |
© Biology-Online.org. All Rights Reserved. Register | Login | About Us | Contact Us | Link to Us | Privacy Policy


text:
Before and After Photos
Source: J.Crow's.
Here are some amazing historical before and after photos of people treated for Hypothyroidism (also referred to as myxedema) after treatment with Natural Desiccated Thyroid Medicine..
Above: A severely affected 14-year-old hypothyroid girl with puffiness around the eyes, thickened lips, depressed root of the nose (saddle nose), and straight, coarse hair. The second picture was taken after only 6 months of treatment with desiccated thyroid. Note the elevated bridge of the nose, brighter eyes, thinner lips, and glossy, curly hair. Her constipation had resolved and her appetite improved.
Adult woman with the characteristic puffiness that often accompanies hypothyroidism. Her puffiness and hair texture markedly improve after treatment with desiccated thyroid.
Adult man with the "obese form" of hypothyroidism. Note the striking resoltion of his puffiness (myxedema) after treatment with desiccated thyroid. Myxedema is the medical term for hypothyroidism. Myx is the Greek word for mucin, which accumulates in hypothyroidism. Edema means swelling.
This is another example of the resolution of the puffiness (myxedema) following proper treatment of hypothyroidism with desiccated thyroid.
Type 1 Hypothyroidism
is defined as failure of the thyroid gland to produce sufficient amounts of thyroid hormones necessary to maintain "normal" blood levels of those hormones and "normal" blood levels of the thyroid stimulating hormone (TSH) produced by the pituitary gland. The TSH test is the standard blood test your doctor checks when looking for hypothyroidism. Around 7% of Americans suffer Type 1 hypothyroidism.
Type 2 Hypothyroidism
is defined as peripheral resistance to thyroid hormones at the cellular level. It is not due to a lack of adequate thyroid hormones. Normal amounts of thyroid hormones and thyroid stimulating hormone (TSH) are detected by the blood tests; therefore, blood tests do not detect Type 2 hypothyroidism. Type 2 hypothyroidism is usually inherited. However, environmental toxins may also cause or exacerbate the problem. The pervasiveness of Type 2 hypothyroidism has yet to be recognized by mainstream medicine but is already in epidemic proportions


text:
V2 Cigs Fan of the Week: Pat's Story
I am 63 years old and have smoked cigarettes since I was 13. I have tried many times to quit smoking, but it would only last for a short while. I would get so easily irritated I would blow up at the least little thing. My husband would finally tell me to please go buy cigarettes and give us both some relief!
My grandchildren have been begging me to quit smoking since they were old enough to talk. They used to tell me they didn't want me to die. They were afraid I wouldn't live to see them grow up. The last time I tried to quit I didn't last long and I pretended for at least 6 months that I wasn't smoking anymore.
I would sneak out behind the storage building and smoke and then run in and brush my teeth and spray myself with cologne. It was getting harder all the time to pretend because when the family would get together for Sunday dinner I would have the hardest time waiting until we went home to have a cigarette. My husband would drive home with me hanging out the window smoking so I wouldn't stink up the car.
In October of 2011 my dear friend bought me the v2 standard kit for my 63rd. birthday. Not only have I not smoked another cigarette since that day but I haven't even craved one! I feel so much better than I have in a long time and definately smell better! I don't have to go out in the cold to smoke or spray myself with cologne a thousand times a day, which is something I have always done so as not to offend anyone.
Thank you v2cigs! You have totally changed my life! I truly am your biggest fan!!!
-Pat Beck
Clovis, New Mexico
The V2 Cigs Fan of the Week is our way of highlighting a few of the incredible life stories we get to hear on a daily basis, sent by both new and old V2 fans as they experience this amazing product and the family of support from the V2 community and staff. To enter, email your story + photo to: email@example.com. If you are chosen, you will receive some special attention via free products and samples, plus a featured spot in our blog.


text:
Jane (Princess Leya) Bartels, 6 - November 30, 2012
Jane "Princess Leyha" Bartels 6, of Brady passed away Friday, Nov. 30, 2012, at her home after a courageous three-year battle with cancer.Services will take place Wednesday, Dec. 5, at 2:30 p.m. at Brady High School with the Rev. Robert Litzenberger officiating. Burial will be conducted at the Gaslin Cemetery near Brady.
Bartels lived in the Brady community and was currently a kindergartner in the Brady school system.
Her contagious smile and positive attitude spread to the people around her, the family said. She had a love for life that no one had ever seen, and always had compassion for those around her.
Bartels' brother, Hunter, was a large part of her life and she always loved and protected him. She was the leader of her huge group of cousins and everybody's best friend, according to family members. She also had a special friend, Randin Hood, a soldier deployed to Afghanistan who "adopted" her.
She was preceded in death by: her grandfathers—Dan Stewart and Gerald Brown; great-grandparents—LaVonne and Larry Spurgin; great-aunt, Sherry Lynn Spurgin; great-uncle, Gerald Brown; a cousin Brianna Brown.
Survivors include: her father, Jason Bartels of Maxwell; her mother, Katie Stewart of North Platte; brother, Hunter Bartels of North Platte; grandparents—Sue Spurgin and Kathy Hoffman, both of Brady; great-grandmother, Velma Jean Brown of Brady; aunts and uncles—Dan and Torrey Stewart of Curtis, Jeremy and Becky Bartels, Jill Miller and Angel Hoffman, all of Brady, and Mark and April Hoffman of Cozad; numerous other family members and friends.
Memorials are suggested to The Princess Leyha Scholarship Fund, established in her name.


text:
Immediately after Taylor-Hopkins II, Lou DiBella, promoter of Jermain "Bad Intentions" Taylor, states "Taylor's next fight will be in Little Rock (Ark) against a bum." That scenario doesn't play out, instead Taylor fights Winky Wright. Immediately after that fight, DiBella upgrades his previous "bum" statement by telling the world his fighter really had bad intentions and will fight no one more significant than "Bozo the Clown."
Hagler, Duran, Leonard would be ashamed of such comments.  After seeing his remarks had bad intentions written all over them, DiBella than does the unthinkable – he then takes his prize possession in Taylor and proposes a matchup with a "Contender?" that hasn't gone beyond 8 rounds in his professional career, not because he knocks everyone out, but because he's an 8-round fighter (barely)! Â
Now when you thought it couldn't become more comical, DiBella in his infinite wisdom announces that Taylor could next face Giovanni Lorenzo? Giovanni Lorenzo? Opera singer? Italian movie star? Pick one of the above, because he is no where to be found in any of the ratings of the four major sanctioning bodies! And in today's world, that's a pretty hard feat to accomplish. Â
Its pretty simple Jermain on how to resolve your dilemma. Your next opponent should be your promoter, Lou "DiJoker" DiBella. Â
On August 18, 2006 right in beautiful Sergio Mora country, Sam "King" Soliman will fight 24-2, Enrique Ornelas on ESPN at the Pechanga Resort & Casino. Please tune-in and understand why Jermain "Bad Intentions" Taylor has really bad intentions and would prefer to fight Bozo, rather than stepping into the ring with the King, Sam Soliman.
Check Also
WBO Cruiserweight King Usyk Added To Lomachenko vs. Sosa Fight Card
Vasyl Lomachenko vs. Jason "El Canito" Sosa junior lightweight world championship event has become an …