text:
Vertex Full Body Kit Toyota Corolla Trueno AE86 84-87
Model: VER-AE86TRU-FK
Sale: $1,334.40
Product Info
Go To Product
Vertex Full Body Kit Toyota Corolla Trueno AE86 84-87
Vertex has been in the Japanese automotive performance industry since 1996. Vertex strives incorporate technically advanced manufacturing with elegance in all of their products. All Vertex Aero kits are inspired by the vehicles factory body lines. Vertex strives to make their body kits aggressive yet at the same time simple. The goal is to create a subtle design to compliment the cars original form. No design is ever overdone, yet it still customizes the look of the car to enhance the vehicle from its factory form. Vertex's founder, Takahiro Ueno, is a passionate driving enthusiast, and is a long time enthusiast of rear wheel drive Japanese cars such as the Lexus SC300/400. Because of this, Mr. Ueno remains true to his street racing roots, allowing his passion to show in his company and his products. He has competed in the D1 Grand Prix drift circuit with his Lexus SC. Vertex is dedicated to offering quality parts to their customers that they will enjoy for a lifetime.
A vehicles aerodynamics is one of the most overlooked factors of a vehicle by enthusiasts. Improving a vehicles aerodynamics can improve gas mileage, handling, top speed, and stability. It is also a great way to improve your vehicles looks, as the aggressive lines are similar to that found on the race track. But the aggressive lines aren't just for looks; they increase down force, reduce drag, and minimize air turbulence, making your vehicle more stable at high speeds. Body kits also allow you to give your vehicle a new exterior appearance by using bolt on parts. A different front and rear bumper or fenders gives your vehicle a custom look and personalizes your vehicle.
Customizes exterior
Vehicle specific for proper fitment
About Manufacturer: Vertex
For over 25 years, Vertex has built its business on successful, long-term relationships with our clients. Our commitment to a quality product, prompt and efficient service, as well as our extensive product knowledge and technical expertise has made us the Porsche parts industry leader. Whether you are restoring, rebuilding, maintaining or upgrading your Porsche, Vertex Automotive has all the Porsche parts and accessories you'll need.
Vertex Store


text:
|Site sponsored by IGEL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[directfb-users] Re: 1400x1050 not possible with ATI M9?
I've tried the fbmodes utility (http://bisqwit.iki.fi/source/fbmodes.html) for generating modelines for fbset. Most of the refreshrates gave a blank screen directly. The resolutions 1400x1050@62 and 1400x1050@75 were the only two that don't blank the console screen. Unfortunatly both didn;t work with DirectFB. I've played something with DirectFB and concluded that when compiling DirectFB without multi-app support, DirectFB works great on 1400x1050. So i suspect it has to do something with the kernel module fusion (or a combination of fusion and kernel linux 2.6.10). On Sat, 22 Jan 2005 17:25:02 +0100, Andreas <email@example.com> wrote: > > >I really would like to run the native resolution of the laptop, that > >is 1400x1050. That's also the resolution radionfb selects by default > >(and it works). > > > >Am I doing something wrong or is it a bug? > > > > > It seems that your desired mode (1400x1050) is not in /etc/fb.modes > > For TFTs I used to boot with vesafb and then type fbset to get the > correct timings for the TFT, but unfortunately, your VESA BIOS might not > have a mode number for your non-standard 1400x1050, and if it has, it > would be annoying to find it out. There might however be a tool to query > VESA modes. > > maybe searching the web for the correct timings and editing > /etc/fb.modes is easier. > > Andi > >
|Old Archives

subset: commoncrawl


text:
Gary M. Galles: Minimum wage and rent control: failed solutions
"Many cities are pricey places to live." That was the major premise of a recent opinion piece advocating that high-cost cities raise minimum wages. It was striking that the same reason has been used to justify rent controls.
Subscribe to the Ventura County Star
Ready to subscribe to the Ventura County Star? Choose between a Premium or Digital subscription below.
Need Help? Call us at 1-877-710-6182.
Monday-Friday: 6am-3pm / Saturday: 6:30am-10:30am / Sunday: 7am-11am


text:
Copyright 2007-2012
Built with Indexhibit
"An Artist Selects: Portraits from the Collection"
Curated by Dawoud Bey
Weatherspoon Museum of Art, Greensboro, NC
This special Atrium exhibition is of portraits from the permanent collection curated by the renowned Chicago-based photographer, Dawoud Bey, whose own work [was] on view in the exhibition "Class Pictures", through September 7. Each work was selected for its ability to create a momentary sense of engagement with the individual portrayed, reminding us that, in spite of our seeming differences, we are bound together in common humanity. Bey's atrium exhibition opened on August 28, in conjunction with his lecture and dialogue with Weatherspoon curator Xandra Edens.
John Ahearn, Elizabeth Catlett, Chuck Close, Susanna Coffey, Catherine Opie, Red Grooms, Alex Katz, Nicholas Nixon, Robert Phillip, August Schwabe, Elizabeth O'Neill Verner


text:
About this Chapter
More than 3,000 UNCW alumni live in the Greater Charlotte area and surrounding counties.
As a valued member of the Alumni Association, each person in this area is a part of the chapter. The group offers ways for alumni to network and share Seahawk spirit with others in their area.
Megan Iacobellis
Assistant Director - Regional Chapters
Charlotte Area Alumni Chapter
Charlotte Alumni Fall Social
Thursday, November 5
6 - 8 pm
Charlotte City Club
Huck Huxley '01
Erika Hoover '05
Vice President
Joey Morganthall '07
Past Events
Charlotte Alumni Spring Mixer 2014 - Close to 90 alumni from classes of 1979 through 2013 gathered on the rooftop of the Peculiar Rabbit on May 22 to enjoy reconnecting, networking and complimentary appetizers. The weather was beautiful and the view of the Charlotte skyline was spectacular. Check out photos!
Charlotte Alumni Fall Social 2013 - Over 100 Seahawks met at the Charlotte City Club on October 17 for the annual fall social and heard from one of our own, keynote speaker Brandon Beane '90, who is the Director of Football Operations for the Carolina Panthers. Check out photos!
Charlotte Alumni Spring Mixer 2013- Over 100 Charlotte area alumni and friends met at Dressler's Restaurant in the Metropolitan for the chapter's 2013 Spring Mixer. Alumni enjoyed a networking opportunity, complimentary appetizers, and live music from the band Who Rescued Who (compliments of the MetLive Concert Series). Check out photos!
Charlotte Alumni Fall Dinner 2012- Nearly 100 Charlotte alumni and friends of the university welcomed Chancellor Gary L. Miller and his wife, Georgia, at the beautiful downtown Charlotte City Club on October 18. Guests mixed and mingled with fellow Seahawks over drinks while enjoying the view of the Charlotte skyline. Charlotte Chapter president, Jensen Caudle '05, gave an overview about the chapter followed by the keynote speaker, Chancellor Gary Miller, who shared with guests the recent accomplishments and future plans for the university. Take a look at photos!
Charlotte Alumni Spring Mixer 2012 - Close to 100 Charlotte Area Alumni gathered at Dressler's Restaurant in the Metropolitan for the 2012 Spring Mixer. Alumni enjoyed complimentary appetizers courtesy of the UNCW Alumni Association while enjoying live music from Hot Sauce during the METLive concert series. It was a great way to wrap up the spring season and to connect with area alumni. Enjoy photos from the event.
Charlotte Alumni Chapter Fall Dinner 2011 - More than 100 alumni enjoyed each other's company while overlooking the Charlotte skyline during the chapter's second Fall Dinner at the City Club on Thursday, November 3. UNCW Chancellor Gary Miller and his wife, Georgia, met alumni during a wine and beer reception before moving into the ballroom for dinner. A short presentation included chapter president, Robert Abbotts '85, who spoke about the involvement of UNCW alumni in Charlotte, and also Chancellor Miller who shared some of the university's current achievements. Take a look at photos!
Charlotte Alumni Chapter Spring Mixer- Over 100 alumni and friends (from graduation years ranging from 1980-2011) gathered at Andrew Blair's Restaurant in Charlotte on May 26, for the Charlotte Area Alumni Chapter's 1st annual Spring Mixer. As alumni arrived they received a free gift with their registration and enjoyed free appetizers and a cash bar. Since this was the group's first Spring Mixer there were several reunions of alumni who had not seen each other in years. The room buzzed with excitement and stories from days at UNCW. New graduates shared highlights of what the campus is like now while listening to stories of how it used to be. Take a look at photos!
Charlotte Alumni Chapter Fall Interest Dinner 2010 Packed House. Two words describe the dinner held at the Charlotte City Club on Thursday, November 11. Close to 140 alumni met while overlooking the Charlotte skyline to enjoy a wine and beer reception and conversation with friends. This was the first formal meeting of the group. After time spent meeting others and catching up with classmates, the group moved to the ballroom to enjoy a three course meal. After dinner, the presentation began with Rob McInturf, Director of Alumni Relations at UNCW. He spoke about the objectives of the chapter and announced the executive board- President, Robert Abbotts '85; Vice President, Jensen Caudle '05 and Secretary, Brandon Hillis '02. Chancellor DePaolo then spoke about all of the great things happening at UNCW. The group buzzed with excitement as the evening wrapped up. Take a look at photos!


text:
The Dorothy L. Lougee Nursing Assistant I Program
This state approved course introduces basic nursing skills required to provide personal care for patients, residents, the elderly or others requiring medical assistance in a healthcare setting. Through classroom instruction, laboratory work and clinical rotations, students are prepared to take the North Carolina Nurse Aide I Competency Examination. Successful completion is required for listing on the NC Nurse Aide 1 Registry. CPR certification is included in the class.
NOTE: Students must initiate a criminal background check and drug screen before registering for an NA1 class. If denied access to a clinical facility, the student will not be able to progress in the program due to the inability to meet clinical requirements and will be unable to continue in the program.
Occupation Description
The Nursing Assistant Level 1 (NA1) plays an important role in patient care. As the front line care provider, NA1's spend more time in direct contact with the patient than any other member of the health care team. Under supervision of registered and practical nurses, the Nursing Assistant provides basic nursing skills and personal care activities such as measuring vital signs and assisting patients with activities of daily living (feeding, bathing, moving, or grooming patients), and maintaining a safe environment for the resident/patient.
Careers Available (Employment Opportunities)
Nursing Assistants (NA1) are employed in Hospitals, Long Term Care Facilities, Clinics, Hospices, Rehabilitation Centers, Psychiatric Centers, and Home Care. There is a high demand for NA1s, especially in long term care and home health.
Entry-Level Salary (Low-High)
Earnings for NA1s vary depending on experience, shift and length of service. Entry level pay may begin at $8.70 for the new NA1, but range from $9.15 – $14.00 with experience and location.
Learning Objectives (Course Info)
The 173 hour NA1 program at Forsyth Tech is a state approved course which teaches basic nursing skills to the NA1 candidate. Such skills are required to provide personal care for patients, residents, the elderly and others requiring medical assistance in a healthcare setting. Emphasis is placed on patient safety and infection control, the aging process, communication, legal and ethical issues, patient rights, personal care, vital signs, elimination, nutrition, emergencies, rehabilitation, proper body mechanics and mental health. CPR certification sessions are included and supervised clinical experiences are conducted. Students are prepared to take the North Carolina Nurse Aide Competency Examination, a requirement for listing on the NC Nurse Aide I Registry.
Recommended Courses and Skills (Technical Skills)
Nursing Assistant 1 candidates must have a high school diploma or GED and successfully complete a placement test with reading at a 10th grade level and math at a 6th grade level. Completion of a state approved NA1 course is recommended. For State Certification, graduates must also pass a state examination.
Helpful Personal Attributes (Soft Skills)
Human resource skills are essential for work in health care. Such skills include professionalism, teamwork, customer services, and communication skills. They also need to be organized and self-starters. Safety is key and all precautions must be taken to prevent the transmission of infectious diseases.
Program Contact: Graham Hyder at 336.734.7733 or Tiffany Hanes at 336.734.7725


text:
We offer discount to nonprofits, government agencies, and federal contractors
AILA created this PSA, in English and Spanish, to inform DACA grantees who received 3-year work permits erroneously issued or mailed after 2/16/15
AILA Doc No. 11120972 | Dated December 9, 2011 | File Size: 895 KDownload the Document
AILA's comments in response to USCIS's draft policy memo on EB-5 adjudications policy. Special thanks to the AILA EB-5 Committee.
[[To print the PDF on this page please use the print function in the PDF reader.]]
Cite as AILA Doc. No. 11120972.Open the Document
American Immigration Lawyers Association
1331 G Street NW, Suite 300
Washington, DC 20005
Copyright © 1993-2015
American Immigration Lawyers Association.


text:
A method of diagnosing a fault in a network path comprises the steps, performed at a diagnosing node, of initiating a path discovery test. The diagnosing node receives at least one path discovery test response and identifies the diagnosable node on the network path from a path discovery test response. The diagnosing node remotely accesses said diagnosable node and performs a diagnostic routine at said diagnosable node.
1. A method of diagnosing a fault in a Multi Protocol Label Switching (MPLS) network path comprising the steps, performed at a diagnosing node, of:
initiating a path discovery test to a destination node;
receiving at least one path discovery test response;
identifying a diagnosable node on the MPLS network path from the path discovery test response;
remotely accessing said diagnosable node; and
performing a diagnostic routine, using a layer two service of the Open System Interconnection (OSI) reference model, at said diagnosable node to at least determine whether an MPLS packet handled by said diagnosable node carried an incorrect header; wherein the layer two service does not have information about an exchange of layer three routing information with a service provider;
in response to the diagnostic routine not diagnosing the fault at the diagnosable node, using the layer two service of the OSI reference model, the diagnosable node, from forwarding information at the diagnosable node, without sending a test packet, identifying a next-hop node along the MPLS network path to the destination node, and using the layer two service of the OSI reference model, remotely accessing the next-hop node along the MPLS network path to the destination node as a new diagnosable node and performing the diagnostic routine at said new diagnosable node; wherein the method is performed by one or more computing devices; wherein the method is performed in a-the layer two service of the OSI reference model.
2. A method as claimed in
3. A method as claimed in
4. A method as claimed in
5. A method as claimed in
6. A method as claimed in
7. A method as claimed in
8. A method as claimed in
9. A method as claimed in
10. A method as claimed in
11. A method as claimed in
12. A method as claimed in
13. A method as claimed in
14. A method as claimed in
15. A method as claimed in
16. A method as claimed in
17. A method as claimed in
18. A method as claimed in
19. A method as claimed in
20. A method as claimed in
21. A method of
22. A computer readable volatile or non-volatile storage medium storing one or more sequences of instructions for diagnosing a fault in a Multi Protocol Label Switching (MPLS) network path which, when executed by one or more processors, cause the one or more processors to perform the steps of:
initiating a path discovery test to a destination node;
receiving at least one path discovery test response;
identifying a diagnosable node on the MPLS network path from the path discovery test response;
remotely accessing said diagnosable node; and
performing a diagnostic routine, using a layer two service of the Open System Interconnection (OSI) reference model, at said diagnosable node to at least determine whether an MPLS packet handled by said diagnosable node carried an incorrect header;
wherein the layer two service does not have information about an exchange of layer three routing information with a service provider, in response to the diagnostic routine not diagnosing the fault at the diagnosable node, using the layer two service of the OSI reference model, the diagnosable node, from forwarding information at the diagnosable node, without sending a test packet, identifying a next-hop node along the MPLS network path to the destination node, and using the layer two service of the OSI reference model, remotely accessing the next-hop node along the MPLS network path to the destination node as a new diagnosable node and performing the diagnostic routine at said new diagnosable node; wherein the steps are performed in a-the layer two service of the OSI reference model.
23. A computer readable volatile or non-volatile storage medium of
24. An apparatus for diagnosing a fault in a Multi Protocol Label Switching (MPLS) network path comprising:
one or more processors;
a network interface communicatively coupled to the one or more processors and configured to communicate one or more packet flows among the one or more processors in a network;
a computer readable volatile or non-volatile storage medium storing one or more sequences of instructions for diagnosing a fault in the MPLS network path which, when executed by the one or more processors, cause the one or more processors to perform:
initiating a path discovery test to a destination node;
receiving at least one path discovery test response;
identifying a diagnosable node on the MPLS network path from the path discovery test response;
remotely accessing said diagnosable node; and
performing a diagnostic routine, using a layer two service of the Open System Interconnection (OSI) reference model, at said diagnosable node to at least determine whether a-an MPLS packet handled by said diagnosable node carried an incorrect header;
wherein the layer two service does not have information about an exchange of layer three routing information with a service provider,
in response to the diagnostic routine not diagnosing the fault at the diagnosable node, using the layer two service of the OSI reference model, the diagnosable node, from forwarding information at the diagnosable node, without sending a test packet, identifying a next-hop node along the MPLS network path to the destination node, and using the layer two service of the OSI reference model, remotely accessing the next-hop node along the MPLS network path to the destination node as a new diagnosable node and performing the diagnostic routine at said new diagnosable node;
wherein the diagnostic routine is performed in a-the layer two service of the Open OSI reference model.
25. An apparatus of
The present invention generally relates to network paths. The invention relates more specifically to a method and apparatus for diagnosing a fault in a network path.
In computer networks such as the Internet, packets of data are sent from a source to a destination via a network of elements including links (communication paths such as telephone or optical lines) and nodes (for example, routers directing the packet along one or more of a plurality of links connected to it) according to one of various routing protocols.
One such protocol is MPLS (Multi Protocol Label Switching). MPLS is a protocol that is well known to the skilled reader and which is described in document "Multi Protocol Label Switching Architecture" which is available at the time of writing on the file "rfc3031.txt" in the directory "rfc" of the domain "ietf.org" on the World Wide Web. According to MPLS, a complete path for a source-destination pair is established, and values required for forwarding a packet between adjacent label switched routers (LSRs) in the path together with headers, or tags or "labels" are pre-pended to the packet. The labels are used to direct the packet to the correct interface and next hop. The labels precede the Internet Protocol (IP) or other header allowing smaller outer headers.
The path for the source-destination pair, termed a Label Switched Path (LSP) can be established according to various different approaches. One such approach is the Label Distribution Protocol (LDP) in which each router in the path invokes an LDP session with neighbouring LSRs and sends its label to the next hop router on the path as determined from its IP routing table. Alternative label distribution mechanisms include Resource Reservation Protocol (RSVP) in which case, for example, a network administrator can engineer a path, providing strict source routing and Border Gateway Protocol (BGP). In all cases a Label Forwarding Information Base (LFIB) stores both the next-hop information for the LSP, together with the label required by the next hop as a label binding.
For each LSP created, a forwarding equivalent class (FEC) is associated with the path specifying which packets are mapped to it.
At an ingress LSR to the LSP, packets destined, for example, for a certain destination or "prefix" are assigned to a corresponding FEC and injected into the LSP with the LSP next-hops ingress label pre-pended. The LSP next-hop router swaps its ingress label with an egress label received from its next-hop router and so forth. At an LSP egress router, the ingress label is removed and the packet is forwarded on towards the destination prefix according to the routing protocol supported thereafter.
One known use of MPLS is in MPLS virtual private networks (VPN) where an LSP is established between ingress and egress provider edge routers (PE) accessible by respective customer edge (CE) routers hence providing an effective tunnel between the customer edge routers.
MPLS VPN's are used for a range of telecommunications services but can give rise to difficulties in fault finding and troubleshooting. For example troubleshooting may be a manual task requiring complex procedures and hence costly skilled operators to find and diagnose faults. Both the isolation and identification of the cause of "broken" LSPs can hence lead to prolonged loss of connectivity for services using MPLS as a transport. Furthermore, problems tend to occur in ways that are not automatically detectable by the individual routers, such as misconfiguration or software/hardware defects such that customer intervention is required to draw the problem to the attention of the service provider.
Traditional fault management products focus on problem detection, alarm management and "trouble ticket" management. Problem detection is typically based upon receiving messages from network devices using simple network management protocol (SNMP) traps and logging messages, or polling the devices at regular intervals for predetermined fault symptoms. Alternatively test traffic can be injected into the network and problems detected in the form of an alarm. However other than generating a trouble ticket there is minimal support for subsequently diagnosing or troubleshooting the fault.
One known approach for detecting faults is described in "Detecting MPLS Data Plane Failures" of Kompella et al ("Kompella") which is available at the time of writing on the file "draft-ietf-mpls-lsp-ping-03.txt" in the directory "proceedings/03jul/I-D" of the domain "ietf.org" of the World Wide Web. According to the approach described therein, in a first detection step a "LSP ping" command is sent followed by an "LSP traceroute command". The LSP ping corresponds to an internet control message protocol (ICMP) ping comprising a packet sent along the path from the ingress point which is responded to from the egress point. Receipt of the response indicates that the path is healthy. LSP traceroute comprises a message which is received at each router along the LSP, passed along and responded to with additional diagnostic information. If there is a fault then the vicinity in which it occurred can be determined from identifying which furthest router sent a traceroute response. In addition the response itself may carry some low level diagnostic information. Accordingly the approach described in Kompella will tell a network administrator whether the path is healthy or broken and the general vicinity of any fault, but provides little more useful information.
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
A method and apparatus for diagnosing a fault in a network path is described. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.
Embodiments are described herein according to the following outline:
The needs identified in the foregoing Background, and other needs and objects that will become apparent for the following description, are achieved in the present invention, which comprises, in one aspect, a method of diagnosing a fault in a network path comprising the steps, performed at the diagnosing node, of initiating a path discovery test, receiving at least one path discovery test response, identifying a diagnosable node on the network path from a path discovery test response remotely accessing said diagnosable node and performing a diagnostic routine at the diagnosable node.
In other aspects, the invention encompasses a computer apparatus and a computer-readable medium configured to carry out the foregoing steps.
2.0 Structural and Functional Overview
The method can be understood in overview with respect to
The network comprises an MPLS VPN between first and second customer edge routers 100, 102 connected to respective customer devices 104, 106. Each customer edge device is connected to a respective provider edge devices 108 110. The provider edge devices 108, 110 communicate across an MPLS network designated generally 112 and in particular define a network path in the form of an LSP further including an intermediate LSR 114. In the embodiment shown the LSP progresses from the provider edge router acting as an ingress LSR1, 108 via intermediate LSR2, 114 to an egress LSR3, 110. Of course the connection between customer edges may be bi-directional as appropriate in which case a further LSP in the opposite direction is also set up.
In order to perform fault diagnosis of the LSP comprising LSR1, LSR2, LSR3, a network management application is resident on a network management system (NMS) 116 which is off line in the sense that it is not part of the network. Of course the NMS 116 can be located at any appropriate point on or without the network and can be a single or distributed entity or multiple independent but coordinated entities.
Accordingly, MPLS VPN traffic from user device 104 to 106 is forwarded first to customer edge router 100 and then on to provider edge router 108 where it is injected into the LSP defined by routers LSR 1, 2, 3. At LSR 3 the traffic leaves the LSP and is forwarded normally onto customer edge router 102 by provider edge router 110 and from there onto user device 106.
A method of diagnosing a fault in the LSP can be further understood with reference to
Of course if the VPN connectivity is confirmed to be functional by successful ping tests, the MPLS provider can conclude that the problem may be the customer network. However if a VRF connectivity problem is detected, ie the ping or PVP message does not succeed, then a path discovery test which can be any appropriate path discovery technique such as PVP path trace providing LSP traceroute is initiated. The path discovery command ensures that the vicinity of the problem can be identified. In particular, at step 202 the network management system receives a path discovery response. In the case of current traceroute functionality this will either identify the last healthy router in the LSP, further downstream routers failing to respond at all, or will return an unhealthy traceroute response from a router. It will be noted that according to an alternative approach, an image of the network may be constructed at the network management system carrying relevant information such as a forwarding table images, IP address and identifier and access credentials and which is pre-constructed according to known techniques which will be familiar to the skilled reader and are not described in detail here. In that case the path discovery steps can be carried on the image of the network rather than the network itself. In either case, initiation of the path discovery test and the subsequent diagnostic router are fully automated.
At step 204 the network management system identifies from the received path discovery command or traceroute responses a diagnosable node comprising either the last healthy node or the node in the LSP returning an unhealthy traceroute response. It will be noted that in practice the traceroute response may carry only the node's IP address. However the network management system can identify the actual node identity using any appropriate identifier for example from information carried on the network image which automatically maps the IP address to the diagnosable node identifier.
At step 206 the network management system obtains from the network image the access credentials for the diagnosable node. For example any passwords required to log on to the node are obtained. At step 208 the network management system then remotely access the diagnosable node for example automatically logging on using the access credentials obtained from the network image. This remote access or log on step is carried out using any appropriate approach and effectively comprises remote accessing of the operating system or command line interface (CLI) of the diagnosable node, for example using management protocols such as simple network management protocol SNMP or proprietary APIs implemented in XML over some other transport such as HTTP. The management traffic for remote access can be sent "in-band" for example over an LSP or "out-of band" for example over an alternate, logical or hard-wired path such as a serial/terminal server, and in any appropriate form including encrypted form.
At step 210 a diagnostic routine is performed at the diagnostic node, controlled or initiated remotely from the network management system. In particular, as described in more detail below, a sequence of automated troubleshooting and diagnostic steps is performed to diagnose the cause of the fault and depending on the nature and location of the fault. For example basic per-node configuration may be checked, validation of LDP operation may be checked and route installation into the MPLS forwarding table may be checked, together with configuration mismatch errors. As also described in more detail below, forwarding information and other relevant information on the diagnosable node may also be used to identify, log out and carry out corresponding diagnostic routines on its downstream next-hop node in the LSP if it is detected that the fault may in fact lie on the next node which may not have been visible in the traceroute.
At step 212, having isolated and diagnosed the fault, a report is produced automatically for example at a graphical user interface (GUI) or on hard copy at the network management system remotely identifying the diagnosed fault. The report may either present a conclusion as to the nature of the fault and recommended actions to take in response, or an "observation" identifying important characteristics of the path and nodes on the path that have been identified during the diagnosis, for example, Observation 1: traceroute has revealed packet is unlabeled. Observation 2: LDP session not established between peer LSRs, Observation 3: ACL present on interface on path in the case that the fault cannot be identified, allowing the administrator to make an educated decision as to the nature of the actual fault. In addition a test log is produced by the system running providing an audit trail of the steps taken which again can be used by the administrator to assess what further steps need to be taken. Appropriate alarms or alerts can also be generated for example physically or on screen. The LSP can be rendered graphically between the end points on the GUI including network element names, port and interface names as well as label swapping along the path, for example based on the output of PVP ping or path trace.
Accordingly it can be seen that the approach carries out three effective stages. A first validation stage uses LSP ping to validate that the LSP under test is broken, which can be initiated manually or at pre-determined intervals which may be dynamically self-adjusted, or in response to pre-determined events, but can be implemented automatically in software. In a second, isolation step, if the LSP is broken, the use of LSP traceroute and the network image where required to translate an IP address allows identification of candidate routers or nodes that may be causing the problem and which can be automatically issued upon failure of the LSP ping. In a diagnosis step, the system logs into the candidate device or downstream nodes thereafter if necessary and identifies faults such as misconfigurations of MPLS.
Implementation of the method will be described in more detail below, but one possible implementation is described with reference to
It will be noted that all of the steps in
As described in more detail below, the approach described above can be applied for detection of any kind of network path fault such as an LSP problem for example found in an MPLS VPN. This includes network outages caused by operator configuration, failure of LDP not arising from underlying IP forwarding, route installation problems into VRF tables, LSP "black holes" into which packets are being dropped, failure on the LSP return path, failure to start LDP sessions, failure to label packets or label allocation problems, route target mismatches or chip failure on a router line card (LC).
In addition the approach allows visualization of MPLS LSPs that represent specific packet flows across the MPLS network.
The method is easy to install, simple to operate and can release technical resources by reducing diagnostic time. Hence operation expenses and mean time to repair can reduced by performing fast diagnostics based on analysis of network failures in the access, edge and core parts of MPLS networks ranging from simple configuration problems to complex scenarios such as mismatch in a distributed system between route processor (RP) and LC LFIB using device command—line interaction decision points. In addition the system can be used to check connectivity across LSPs such as VPNs before and after configuration changes, whenever significant changes are planned in a network.
The invention can further be understood with reference to the flow diagrams of
If the ICMP ping succeeds then at step 406 a check is carried out to establish whether an LSP packet was transmitted. This check is carried out at the LSP ingress node, LSR1, 108, in the network of
The steps carried out if a reply was received are shown in
If a reply is not received in response to the flagged router alert then the process returns to the flow shown in
At step 418 a check is carried out to establish whether the LSP packet is transmitted. If not then the flow progresses to the branch shown at
At step 420 a check is carried out to establish whether a transmitted packet was untagged. If an untagged packet is not detected at step 420 this indicates that the initial diagnosable node is in fact functioning correctly as it is sending packets with labels and so the flow proceeds to
At step 656 the received label from LDP from the next-hop is determined and at step 658 any sent packet discrepancy is identified, that is to say it is identified whether router LSR2 is sending the wrong label to router LSR3. If so then at step 660, depending on the operating system adopted, it is assessed whether there is a distributed platform. For example for a routing table may be held at the routing processor (RP) and the forwarding table at the line card (LC) in which case there may be a software state difference. If there is a distributed platform, therefore, it is checked at step 662 whether the LC LFIB is corrupt and if so a report is generated at step 664. If however there is no distributed platform or the LC LFIB on a distributed platform is not corrupt then at step 666 a corresponding report is generated once again indicating that there is a sent packet discrepancy not originating from a distributed platform.
If there is no sent packet discrepancy then at step 668 a check is carried out to establish whether the diagnosable node is the ingress point, ie router LSR1. In that case the flow proceeds to the steps set out in
If there is no received packet discrepancy then the flow proceeds to the steps set out in
Referring to
If the next-hop can be reached then at step 704 the network management system logs onto the next-hop router, namely router 3 in the topology of
At step 706 an initial step is carried out to identify whether the next-hop router which has now been logged on to comprises the egress point for the FEC/LSP. For example if router LSR3 is indeed the egress point then at step 708 a check is carried out to establish whether the router implements a compliant internet operating system (IOS) version. If not this indicates that the egress router does not support LSP ping and LSP traceroute and a corresponding report is generated at step 710. In an alternative topology where, for example, there is an additional next-hop router between router LSR 2 and router LSR 3 then this is not the egress point for the FEC and so it is not relevant to establish the compliance of the IOS as it will nonetheless be forwarding ping and traceroute along the path as normal traffic. In that case, step 712 it is checked whether there is an LFIB entry for the prefix. If not then at step 714 a corresponding report is generated. If there is an LFIB entry for the prefix then at step 716 a check is carried out to establish whether a return path is present and valid. For example this can be done by examining the LFIB on the next-hop router in relation to forwarding to the upstream router.
If there is no such path then the process proceeds to the flow shown in
Reverting to
At step 720, if the next-hop node is compliant with the OAM criteria then a further check is carried out to establish where the packets are being dropped at the node. This can be done using any appropriate known command at the node as managed by the network management system. If packets are being dropped then an appropriate report is generated at 722 indicating that packets are being dropped for an unknown reason. Once again together with a test log this provides detailed information allowing the actual fault to be diagnosed very quickly. Finally, if at step 726 a loop is detected using any appropriate detection mechanism such as test packets, then at step 728 once again a corresponding report is generated indicating the presence of a routing loop and suggesting appropriate troubleshooting steps in response.
Reverting to
Referring then to
Reverting to
If the next-hop can be calculated then the network management system proceeds to log on to the identified next-hop and carries out an MPLS configuration check at step 1012 corresponding to that described above with reference to step 1000 and giving rise to any problem reports at step 1002. If there are no problems then at step 1014 an LDP mismatch is checked and if one is present then a report is generated at step 1016. Otherwise at step 1018 a report is once again generated in the form of an observation that the cause is not known but indicating the steps that have been carried out.
Reverting to
Reverting to
In the case that label bindings were not received then, reverting to
In all cases, in addition to the report, a test log comprising an audit trail of the steps taken is available to the administrator to show what has taken place and an image of the actual network can be visually represented showing the relevant information including the routes part of the network, their IP addresses and other appropriate information such as access credentials. The test log can be attached to a "trouble ticket" which is forwarded on to the appropriate manager and shows the steps that have been completed and the conclusions reached. The provision of observations allows a distinction between diagnosable failures and issues that may cause a failure but cannot provide deterministic diagnosis such as ACL blocks and the various other steps described above. It will be seen that in addition to the various reports, further suggested actions can be recommended to correct the fault for example derivable from a database corresponding to the report messages generated. In particular the failure condition can be graphically represented including a summary field identifying in the type of problem encountered, a possible cause field identifying the precise nature of the problem and a recommended action field identifying what the operator should do to rectify the problem. Yet further the network management system can automatically, or under administrator control, effect a repair on a faulty node, based on the diagnosis.
It will be appreciated that the method described herein can be implemented in any appropriate manner. For example the standardized MPLS OAM capability in existing software can be implemented for example that capability in Cisco IOS software available from Cisco Systems, Inc of San Jose, USA and providing support for VRF ping and traceroute, LSP ping and traceroute and so forth
Even where some routers in the MPLS network do not support LSP ping/traceroute functionality, diagnostics may still be possible in a network that consists of nodes that do not support OAM protocols being issued at the ingress of the path. For example such nodes may drop the OAM packets but further nodes downstream may replay and hence can be diagnosed.
In addition the mechanisms described in "MPLS OAM tools for troubleshooting MPLS Networks" and "Cisco MPLS Management Strategy" can be implemented as described in the respective documents and "cdccont—0900aecd80272b7f.pdf" in the directory "application/pdf/en/us/guest/netsol/ns172/c654" of the domain "Cisco.com" of the World Wide Web and "tech_brief0900aecd800f6e31.html" in the directory "en/US/tech/tk436/tk892" of the domain Cisco.com on the World Wide Web. In case where the network management system does not have the authority to modify the remote device configuration it may instead present the recommendation as a set of steps to be performed by the operator/administrator.
The Network management system can be implemented in any location and in any appropriate manner and logging onto remote diagnosable nodes can be carried out in any appropriate manner for example using the Telnet function as is well known to the skilled reader. It will further be appreciated that although discussion is generally directed to label switched paths in the above discussion, the path discovery, node identification, log in and troubleshoot steps described can be carried out in relation to fault diagnosis of any network path. For example end to end troubleshooting can be implemented for a network path between customer equipment points in which packet transport from customer equipment to provider edge is carried out using wide area network (WAN) technology and provider edges communicate via the MPLS protocol, or where parts of the communication path between equipment includes MPLS forwarding. However the method can also be implemented in relation to any other end-to-end path or path portions including pure IP paths.
Indeed it will be seen that the method may be implemented beyond the layer 3 services such as VPN and interne access described above in which the customer devices exchange layer 3 routing information with the service provider and packets are transported initially using layer 3 routing mechanisms and using other transport technologies such as MPLS where appropriate to help deliver packets. For example the method can be applied in relation to layer 2 services in which there is no exchange of layer 3 routing information with the service provider and packets are delivered using layer 2 technologies such as a asynchronous transfer mode (ATM), frame relay or pseudo wire. Whether the service is layer 2 or layer 3 based, the WAN technology can be for example a circuit based technology such as ATM or frame relay, or technologies such as Ethernet, point to point protocol or high-level data link control (HTLC). Where the service is layer 3 then an IP routing protocol may also run over the WA link, between the customer and provider edges as well as potentially an additional protocol running between the provider edges such as multi protocol border gateway protocol (MB-BGP).
The tests supplied effectively run from customer edge to customer edge or across appropriate parts of the path therebetween and the specific form of connectivity and path discovery tests for example ping and traceroute, are selected according to the path requirements.
Accordingly it will be recognized that the diagnosing node can be any appropriate network component dependent on the required technology. Similarly the diagnosable node can be any appropriate network component such as a router, bridge or switch. Generally the diagnosable node is a network device that processes traffic using any layers of the OSI model. For example, At layer 1 it might be a Wave Division Multiplexer or repeater. At Layer 2 it might be a bridge or a switch and at Layer 3 it might be a router. More recent advancements, such as Application Oriented Networking (from Cisco Systems) allow decisions to be made at the application level, by inspecting the full message, not just the headers.
Generally it will be seen that the mechanisms by which the method and optimizations discussed above are implemented it will be well known to the skilled reader and do not require detailed discussion here. Additional steps can be implemented in hardware, software or firmware as appropriate.
4.0 Implementation Mechanisms—Hardware Overview
Computer system 140 includes a bus 142 or other communication mechanism for communicating information, and a processor 144 coupled with bus 142 for processing information. Computer system 140 also includes a main memory 146, such as a random access memory (RAM), flash memory, or other dynamic storage device, coupled to bus 142 for storing information and instructions to be executed by processor 144. Main memory 146 may also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 144. Computer system 140 further includes a read only memory (ROM) 148 or other static storage device coupled to bus 142 for storing static information and instructions for processor 144. A storage device 150, such as a magnetic disk, flash memory or optical disk, is provided and coupled to bus 142 for storing information and instructions.
A communication interface 158 may be coupled to bus 142 for communicating information and command selections to processor 144. Interface 158 is a conventional serial interface such as an RS-232 or RS-422 interface. An external terminal 152 or other computer system connects to the computer system 140 and provides commands to it using the interface 158. Firmware or software running in the computer system 140 provides a terminal interface or character-based command interface so that external commands can be given to the computer system.
A switching system 156 is coupled to bus 142 and has an input interface and a respective output interface (commonly designated 159) to external network elements. The external network elements may include a plurality of additional routers 160 or a local network coupled to one or more hosts or routers, or a global network such as the Internet having one or more servers. The switching system 156 switches information traffic arriving on the input interface to output interface 159 according to pre-determined protocols and conventions that are well known. For example, switching system 156, in cooperation with processor 144, can determine a destination of a packet of data arriving on the input interface and send it to the correct destination using the output interface. The destinations may include a host, server, other end stations, or other routing and switching devices in a local network or Internet.
The computer system 140 implements as a network management or diagnosable node the above described method of forwarding data. The implementation is provided by computer system 140 in response to processor 144 executing one or more sequences of one or more instructions contained in main memory 146. Such instructions may be read into main memory 146 from another computer-readable medium, such as storage device 150. Execution of the sequences of instructions contained in main memory 146 causes processor 144 to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the sequences of instructions contained in main memory 146. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the method. Thus, embodiments are not limited to any specific combination of hardware circuitry and software.
The term "computer-readable medium" as used herein refers to any medium that participates in providing instructions to processor 144 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 150. Volatile media includes dynamic memory, such as main memory 146. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 142. Transmission media can also take the form of wireless links such as acoustic or electromagnetic waves, such as those generated during radio wave and infrared data communications.
Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 144 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 140 can receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector coupled to bus 142 can receive the data carried in the infrared signal and place the data on bus 142. Bus 142 carries the data to main memory 146, from which processor 144 retrieves and executes the instructions. The instructions received by main memory 146 may optionally be stored on storage device 150 either before or after execution by processor 144.
Interface 159 also provides a two-way data communication coupling to a network link that is connected to a local network. For example, the interface 159 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the interface 159 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the interface 159 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
The network link typically provides data communication through one or more networks to other data devices. For example, the network link may provide a connection through a local network to a host computer or to data equipment operated by an Internet Service Provider (ISP). The ISP in turn provides data communication services through the world wide packet data communication network now commonly referred to as the "Internet". The local network and the Internet both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on the network link and through the interface 159, which carry the digital data to and from computer system 140, are exemplary forms of carrier waves transporting the information.
Computer system 140 can send messages and receive data, including program code, through the network(s), network link and interface 159. In the Internet example, a server might transmit a requested code for an application program through the Internet, ISP, local network and communication interface 158. One such downloaded application provides for the method as described herein.
The received code may be executed by processor 144 as it is received, and/or stored in storage device 150, or other non-volatile storage for later execution. In this manner, computer system 140 may obtain application code in the form of a carrier wave.
5.0 Extensions and Alternatives
In the foregoing specification, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
The method steps set out can be carried out in any appropriate order and aspects from the examples and embodiments described juxtaposed or interchanged as appropriate. It would be appreciated that the approach can be adopted in respect of any MPLS network including but not limited to MPLS VPN either at the service provider or enterprise network level. The approach can be used in addition to troubleshooting for post provision in connectivity checks or VPN connections which can reduce the cost of provisioning significantly. The approaches can be implemented in relation to any appropriate label switching protocol including LDP and tag distribution protocol (TDP).
Citations de brevets
Citations hors brevets
Rķfķrencķ par
╔vķnements juridiques
Image d'origine
Faire pivoter


text:
Signup to receive exclusive offers, tips and more.
Expand all
Collapse all
To track your order, please click on the Order Tracking link found in the header of Brinkmann.net and enter the required information to retrieve your order information. If you placed your order by phone, mail or fax, you will be required to enter your order number and zip code to find your order details. If your order was placed online, you will be asked to login to your profile to display your order details.
It can take up to 24-36 hours for your order to process in the Order Tracking system. If Brinkmann.net does not find/recognize your order and you have placed the order within the past 24-36 hours, please check the site again after this time frame has passed. If you continue to experience problems, please contact customer service via the Contact Form or call (800) 468-5252.
In the Order Tracking results, please locate the FedEx tracking number and click on the link. This link will forward you to the FedEx website and provide you details relating to the exact location of your package. Please allow 3-7 days for transit time within the US. International orders can take longer.
The item you have ordered is currently Out of Stock and on Backorder. Brinkmann reviews production dates on a daily basis and updates the Order Tracking database in order to convey to you as much information as possible regarding the status of your order. Once we receive confirmation that production is nearing completion on the item in question, the status will change to include an Estimated Availability Date (EAD). The EAD is an estimate of when the product will arrive at the Brinkmann warehouse and will be available for shipping. Please allow an additional 3-7 days for transit time once the product is ready to ship.
Once Brinkmann has received your order, the first status category is Order Pending. This means that the item in question is available and scheduled to ship. Please check back within 48 hours for the actual ship date (time frames may vary due to seasonal activity). Please allow 3-7 days for transit time once your order has shipped.


text:
Thank you. If a matching email exists we will send you an email in a few minutes with instructions on how to reset your password.
Don't forget to check your spam folder if you cannot find the email. For further assistance please contact us at email@example.com .Okay
Global Views
A gorgeously detailed growth of bamboo shoots is artistically rendered in ceramic, creating a stunning display for a pretty bouquet. It's also a striking accent on its own.


text:
Results 1 to 4 of 4
Thread: need help with wireless
Enjoy an ad free experience by logging in. Not a member yet? Register.
11-01-2007 #1
- Join Date
- Nov 2007
- Posts
- 16
need help with wireless
Please tell me what changes i should make to my kernel and the steps i should follow in order to get it working.....
11-02-2007 #2
I've had nothing but trouble with all the Broadcom chips I have ever used with Linux and the reverse-engineered kernel drivers.
I'd suggest just using ndiswrapper and the Windows drivers; It's worked for me for years.
11-03-2007 #3
Make sure that you have the bcm43xx module in the kernel.
Then do
modprobe bcm43xx
If that doesn't work you should just do as Scratch_ suggests.
I have a broadcomm chip in my laptop, and only Sabayon and Mepis 6.5+ have been able to configure it correctly.How to know if you are a geek.
when you respond to "get a life!" with "what's the URL?"
- Birger
New users read The FAQ
11-03-2007 #4
I third ndiswrapper. I use a Hawking PCMCIA with the broadcom chipset in an old HP laptop with ndiswrapper and it runs perfectly. Has for years now...Linux Mint + IceWM Registered: #371367 New Members: click here


text:
Video:How to Sew Leg Warmerswith Cindy Fetzer
Learn how to sew leg warmers so that you can keep yourself warm in style during the winter months. Here are some tips on how to sew leg warmers.See Transcript
Transcript:How to Sew Leg WarmersHi! My name is Cindy with Learn2SewFlorida.com and today we're going to teach you how to make leg warmers and what you want when you make leg warmers, is some net fabric or something that stretches.
Measure Legs to Sew Leg WarmersYou need something that's going to be able to stretch over your legs. So we don't need any patterns. All we're going to need is some measurements.
You want to measure how long the leg is, so how long you want your leg-warmer, and all the way around the leg. You're going to do about 20 inches here. 20 inches is good depending on how high you want them to go. You can measure your legs to see how big of a piece that you need.
Finish Edges in Lettuce Style to Sew Leg WarmersThe very first thing that we're going to do is just finish off these edges, at the top and the bottom of the leg-warmer. So we're going to go over and put our machine on a zigzag stitch and just zigzag down the fabric. So we're really going to stretch this as we go, because I want it to have a little lettuce look at the edge of it, and when you stretch fabric, stretch your fabric like that, you get this little lettuce look. The more you stretch, the more you get.
So we're going to do this all the way down this fabric. Now we have our square with our finished edges, and you can finish these two edges anyway you want. We just did a zigzag over the edge or you could fold them over like I was saying.
Stitch Down to Sew Leg WarmersSo the last step in this project is we're going to put two right sides together and this is my right side over here. So I'm going to put two right sides together and do the stitches all the way down, and this is going to be our back seam. So it's going to go in the back of the leg and we can throw some pins in to hold it together, because everything we do, we pin together. Make sure your edges are together, so we can lay those flat.
We're just going to go and make this our last seam and then we will have our leg warmer.So now I'm on a straight stitch and I want my length to be a little bit longer, because I had it close together for the zigzag, and when I pin this together, you want to make sure the top edges and the bottom edges are together.
You want these edges to be together, and we're going to sew this 5/8ths of an inch all the way down. All our seam allowances are always 5/8ths of an inch. We're going to pull our pins outs and we have a leg warmer.We're going to flip it out and we have our leg warmer, and this is our leg warmer. It only has one seam with two finished edges on each ends, and don't forget to make another one for your other leg.
But this is Cindy with Learn2SewFlorida.com. Thank you!
About videos are made available on an "as is" basis, subject to the User Agreement.


text:
Oct. 7, 2011
Lobo Football on the Road
Who: Lobos at Nevada
When/Where: Oct. 15, 2 p.m. in Reno, Nev.
On the Air: KKOB-AM (770)
GoLobos.com: Game Story, Final Stats, Notes, Quotes
The words "bad" and "bye" never are used together.
Though "good-bye" obviously has a different connotation, the New Mexico football team sees nothing but good coming from its current bye week - in which no opponent is scheduled. After four much-needed days off, the Lobos will get back to work Monday to prepare for their road trip at Nevada - UNM's first game away from University Stadium in more than a month.
The Lobos already have gone through a season's worth of trials and tribulations during the first six weeks of the college football season. UNM has yet to savor a victory in five games - including last weekend's 42-28 loss to archrival New Mexico State that capped a turbulent seven-day period with the dismissal of coach Mike Locksley.
Interim coach George Barlow gave his players Thursday and Friday off from practice to help them regroup.
The bye week "definitely helps because these kids have been through a lot, already even before last week," Barlow said. "And then you throw in the events of last week, and it's been pretty tough on them. Whenever you get 18- and 19-year-old kids and you have all these pressures of the real world thrown in with playing college football, it's tough on them.
"So them having a week off just to be kids is great for them, and I think it'll help us next week and kind of rejuvenate their spirits."
The student-athletes plan to use their bye weekend off in good, but varying ways.
"I'm just going to lift; I'm going to eat a lot and put some weight back on that I've lost through the weeks practicing," senior middle linebacker Carmen Messina said. "Just lift and work on my speed - things like that. I'm not in a position where I can take a day off. All these days are counting down and I only have a few of them left, so I've got to take every day that I've got and make them useful."
Asked whether he had anything fun planned, Messina responded with a laugh, "Lifting weights has always been fun for me. It's a way to get out a lot of anger, a lot of negativity. So that's what I plan on doing."
Junior quarterback B.R. Holbrook has a less intense weekend in mind, saying the break for him is more mental than physical. "I'm going to try and relax, nothing too exciting," he said. "Maybe just sit on the couch, watch some movies. That's about it. It'll be good. It gives us a little break, gets our minds off football and then we can come back and attack Nevada hard (next week)."
As students, the players understand that any mental break is somewhat pre-empted by their school work.
"I really just plan to get ahead academically," senior defensive end Jaymar Latchison said. "This gives me a chance to focus on school and be a regular student. So I'm definitely going to get ahead and try to be settled for the rest of the semester, so my grades will be great no matter what else happens."
Latchison said he'll work mostly on assignments for a psychology research techniques class; aside from that, he said he'll enjoy a relaxing week as well, before getting refocused on football.
"I feel like we can come back with a second wind and get the right kind of preparation because we know a lot of stuff went on right before the bye week," Latchison said. "It gives us a chance to clear our heads, reset, get our bodies feeling good and then come back and get after it - get ready for Nevada in the second half of the season."
If a refreshed Lobo squad can elevate its game and find a way to get its first win of the season next weekend, then a good bye suddenly would become a great bye.


text:
By Gerry J. GilmoreAmerican Forces Press Service
WASHINGTON, Sept. 19, 2009 Dozens of people, ranging in age from teenagers to senior citizens, gathered yesterday in Occoquan, Va., to hold a "Missing Man" table ceremony in honor of the nation's servicemembers who have been prisoners of war or are missing in action.
President Barack Obama proclaimed Sept. 18, 2009, as National POW/MIA Recognition Day, which was observed at the Pentagon and at military posts, government agencies and veterans' organizations nationwide. In Occoquan, The Veterans of Foreign Wars Post 7916 held their table ceremony, as they do each year.
"The POW/MIA ceremony is significant to all of us because we want to account for all of our brothers and sisters," said Wayne Dearie, the VFW post's 60-year-old commander. Dearie is a retired Navy Master Chief Petty Officer who served on-shore and ashore in Vietnam from 1968 to 1972.
The ceremony features a symbolic table setting that represents the sacrifice borne by those servicemembers who have been prisoners-of-war or still are listed as missing. About 88,000 U.S. servicemembers are recorded as missing or unaccounted for since World War II.
A group of Air Force Junior Reserve Officers' Training Corps cadets from C.D. Hylton High School in Woodbridge, Va., performed the ceremony in a small wooded park located across the street from Post 7916.
The cadets "did a wonderful job. I have never seen that particular ceremony done that well," Dearie said.
"I was very honored to be able to do this POW/MIA ceremony," said Air Force Junior ROTC Cadet Airman 1st Class Jannel Rapier, a 17-year-old member of C.D. Hylton's senior class.
"Every day I learn something new in Junior ROTC," said Rapier, who plans to become an Air Force officer when she graduates from college.
Retired Air Force Maj. Sheila Allen, the senior aerospace science instructor for C.D. Hylton's Air Force Junior ROTC program, accompanied her cadets to Occoquan to watch them perform the "Missing Man" ceremony.
Having her cadets participate in the POW/MIA ceremony "lets the young people know that we'll never forget" America's former prisoners-of-war and missing servicemembers, Allen said.
VFW Post 7916 makes many contributions to the local community, Allen said, noting the post sponsors annual Air Force Junior ROTC awards and scholarship programs.
Retired Navy Lt. Cmdr. B.J. Richardson, was also impressed by the cadets' performance of the "Missing Man" ceremony. Richardson had, in fact, "recruited" the cadets from C.D. Hylton to perform the POW/MIA ceremony. Richardson had preceded Dearie as commander of VFW Post 7916, having served thrice in that capacity.
The ceremony "brings tears to my eyes," said Richardson, 62, who'd served on river patrol duty in Vietnam from 1968 to 1969.
Vietnam veterans, Richardson said, had helped to bring about POW/MIA Day, starting during the waning days of the conflict.
"We still remember; they're not forgotten, he concluded.
The Veterans of Foreign Wars, with its Ladies Auxiliaries organization, boasts more than 2 million members at more than 8,000 posts worldwide. Applicants for VFW membership are to be U.S. military veterans who have served overseas in a combat zone.
The VFW's origins can be traced back to 1899, when veterans of the Spanish-American War and Philippine Insurrection founded local organizations to secure rights and benefits for their service.
Today, the VFW continues to work on behalf of servicemembers, veterans and their families. The veterans' organization also lends a hand for myriad volunteer projects, it funds college scholarships, and it has helped to establish several national war memorials.