Network Traffic Management 8920 Network Traffic Management software Front-End Processor (FEP) Administration Guide FEP, Release 5
190-406-737 Issue 1.1 September 2010
Alcatel-Lucent - Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements.
Copyright © 2010 Alcatel-Lucent. Unpublished and not for publication. All rights reserved. This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alcatel-Lucent), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Alcatel-Lucent and the business management owner of the material. Notice Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change. Trademarks All trademarks and service marks specified herein are owned by their respective companies. Warranty Alcatel-Lucent provides a limited warranty to this product. Customer Notification The Alcatel-Lucent contract specifies your system configuration (e.g., capacities) and identifies the optional features you have purchased. The standard NTM Feature Set documentation contains information on all of the features available in the Release, including those you may not have purchased, which are thereby not available for use. Alcatel-Lucent will not support external use of the third-party software packages included in the NTM Feature Set. Acknowledgements We wish to acknowledge: The NTM product includes software developed by: Red Hat Enterprise Linux® - Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. APACHE TOMCAT - The Apache License, version 2.0 (http://www.apache.org/licenses/).
APACHE ActiveMQ - The Apache License, version 2.0 (http://www.apache.org/licenses/).
MOD_JK (APACHE Tomcat Connectors) - The Apache License, version 2.0 (http://www.apache.org/licenses/). Apache Xerces C++ - The Apache License, version 2.0 (http://www.apache.org/licenses/).
Apache Axis2 - The Apache License, version 2.0 (http://www.apache.org/licenses/).
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the Apache Group for use in the Apache HTTP server project (http://www.apache.org/)." 4. The names "Apache Server" and "Apache Group" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected] 5. Products derived from this software may not be called "Apache" nor may "Apache" appear in their names without prior written permission of the Apache Group. 6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the Apache Group for use in the Apache HTTP server project (http://www.apache.org/)." THIS SOFTWARE IS PROVIDED BY THE APACHE GROUP ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE GROUP OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
MOD_SSL - Copyright (c) 1998-2004 Ralf S. Engelschall. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by Ralf S. Engelschall
Alcatel-Lucent - Proprietary See notice on first page. WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Bugzilla - Mozilla Foundation; License: http://creativecommons.org/licenses/by-sa/2.0/
CentOS - CentOS Project;
Dom4J - DOM4J Project; License: http://www.dom4j.org/dom4j-1.6.1/license.html
LDAP C SDK - Mozilla Foundation; License: http://www.mozilla.org/MPL/MPL-1.1.html mksh - Korn shell by David Korn; Distributed under BSD License. (https://www.mirbsd.org/htman/i386/man7/BSD-Licence.htm) ncurses - ncurses, GNU 5.5; Distributed under MIT + GPL2+ nmon - IBM nmon; License: http://www.gnu.org/copyleft/gpl.html
PAM_RADIUS_AUTH - This module is a merger of an old version of pam_radius.c, and code which went into mod_auth_radius.c, with further modifications by Alan DeKok of CRYPTOCard Inc.. The original pam_radius.c code is copyright (c) Cristian Gafton, 1996, redhat.com> The additional code is copyright (c) CRYPTOCard Inc, 1998. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, and the entire permission notice in its entirety, including the disclaimer of warranties. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. ALTERNATIVELY, this product may be distributed under the terms of the GNU Public License, in which case the provisions of the GPL are required INSTEAD OF the above restrictions. (This clause is necessary due to a potential bad interaction between the GPL and the restrictions contained in a BSD- style copyright.) THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
JAVA JDK - Sun Microsystems Inc. Binary Code License Agreement (http://java.sun.com/j2se/1.5.0/jdk-1_5_0_12-license.txt). edtFTPj - Enterprise Distributed Technologies under LGPL License (http://www.gnu.org/licenses/lgpl.txt). Perl DBD - Perl DBD Copyright (c) 1994-2003 Tim Bunce, Ireland is used with permission. Distributions of the standard package can be found through the http://www.cpan.org website. Perl Convert::ASN1 - Perl DBD Copyright (c) 1994-2003 Tim Bunce, Ireland is used with permission. Distributions of the standard package can be found through the http://www.cpan.org website. Perl URI - Perl DBD Copyright (c) 1994-2003 Tim Bunce, Ireland is used with permission. Distributions of the standard package can be found through the http://www.cpan.org website.
Prototype - Copyright (c) 2005-2007 Sam Stephenson Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Scmbug - Scmbug by Martin Tomes; License: http://www.subversionary.org/projects/scmbug
SNMP4j - SNMP4J.org; License: http://www.snmp4j.org/LICENSE-2_0.txt
Subversion - CollabNet; License: http://subversion.tigris.org/license-1.html
SWISH-E - Copyright 1995-1998 by Miles O'Neal, Austin, TX, USA. GNU General Public License. w4ais - Copyright 1995-1998 by Miles O'Neal, Austin, TX, USA. (http://yolo.net/w4ais/license.html)
Alcatel-Lucent - Proprietary See notice on first page. GNU LESSER GENERAL PUBLIC LICENSE - Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things. To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others. Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License. In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does. 1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
Alcatel-Lucent - Proprietary See notice on first page. a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.
In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.
Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.
If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things: a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to ecompile the application to use the modified definitions.) b) Use a suitble shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.
Alcatel-Lucent - Proprietary See notice on first page. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.
7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.
11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
Alcatel-Lucent - Proprietary See notice on first page. 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Alcatel-Lucent - Proprietary See notice on first page. Alcatel-Lucent - Proprietary See notice on first page. Contents
About This Document Purpose ...... xxv Scope ...... xxv Intended audience ...... xxv Conventions used ...... xxvi Note on DMS switches ...... xxvi Note on use of the term “entity” ...... xxvi Entering commands ...... xxvi
1 Getting Started What is FEP? ...... 1-2 FEP software ...... 1-4 FEP hardware ...... 1-5 Logins ...... 1-6 Manual pages ...... 1-9 Routine tasks ...... 1-10
2 Installing the FEP Before you begin installation ...... 2-3 Installation tasks ...... 2-4 Retrofitting from FEP4.0 to FEP5.0 ...... 2-6 Installing Solaris 2.5.1 on a Sun Ultra system ...... 2-12 Installing FEP installation scripts ...... 2-16 Installing SPARCompiler C 4.2 ...... 2-18 Installing BaseWorX ...... 2-23 Installing BaseWorX packages ...... 2-24 Provisioning BaseWorX 5.1 ...... 2-26 Installing Datakit VCS host interface ...... 2-28 Installing FEP’s Ethernet TCP/IP connection ...... 2-31 Installing the FEP application ...... 2-34 Installing features ...... 2-37
...... 190-406-737 Alcatel-Lucent — Internal ix Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing Solaris 2.5.1 recommended and Year 2000 patches ...... 2-38 Installing Y2K compliant SUN patches ...... 2-40
3 Administering the FEP Administering user logins ...... 3-4 Adding a “fep” type user login using Admintool ...... 3-5 Adding a “fep” type user login from the command line ...... 3-7 Deleting a user login using Solaris Admintool ...... 3-9 Deleting a user login from the command line ...... 3-11 Administering hosts using Solaris ...... 3-12 Adding a host using Admintool ...... 3-13 Adding a host from the command line ...... 3-15 Deleting a host using Solaris Admintool ...... 3-16 Deleting a host from the command line ...... 3-18 Audit, error logs, and BDR ...... 3-19 Looking into error, audit, and BDR logs ...... 3-21 Monitoring the audit, error, or BDR log files ...... 3-23 Throttling or unthrottling an audit or error message ...... 3-24 FEP application software ...... 3-28 Rebooting the FEP ...... 3-29 Checking application status ...... 3-30 Starting the FEP software ...... 3-33 Stopping the FEP software ...... 3-34 Installing an update ...... 3-35 Removing an update ...... 3-38 Backup ...... 3-41 Performing a full or incremental backup in single-user mode ...... 3-45 Keeping or putting away the tape after backup ...... 3-48 Performing an automatic full/incremental backup of filesystems ...... 3-49 Dynamic data backup ...... 3-51 Performing automatic backup of dynamic data ...... 3-53 Performing a manual backup of dynamic data ...... 3-55 Restoring ...... 3-56 Forcing a crash dump and rebooting the system ...... 3-58
...... x Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Restoring the FEP after a disk crash ...... 3-59 Restoring /(root) and /usr filesystem ...... 3-61 Restoring filesystems other than /(root) and /usr ...... 3-66 Restoring a directory or file (not dynamic data) ...... 3-68 Restoring dynamic data (all or some) ...... 3-72 Partitioning and formatting a disk ...... 3-75 Booting from Solaris CD ...... 3-82 Backup Disaster and Recovery (BDR) ...... 3-85 Configuring BDR ...... 3-87 Verifying BDR ...... 3-91 BDR take over/switch back system administration tasks ...... 3-95 Government emergency telecommunications service (GETS) ...... 3-98
4 Switch Administration Switch connectivity ...... 4-2 Connecting a switch to your FEP ...... 4-5 Disconnecting a switch from your FEP ...... 4-6 Checking switch status ...... 4-7 Synchronizing switches, FEPs, and NTM ...... 4-11 Determining if switch time is wrong ...... 4-12 Checking switch data collection ...... 4-14 Testing FEP-switch links — monitored GTD-5 switches ...... 4-16 Testing FEP-switch links — 5ESS, DMS, polled GTD5 ...... 4-19 Creating a switch ...... 4-25 Deleting a switch ...... 4-27 Activating a switch-FEP link ...... 4-29 Deactivating a switch-FEP link ...... 4-30 Changing a switch’s record base data on the FEP ...... 4-31
5Link Administration Overview of FEP-NTM links ...... 5-2 Connecting a FEP to NTM ...... 5-3 Disconnecting a FEP from NTM ...... 5-4 Checking the FEP-NTM link status ...... 5-5 Creating the FEP-NTM link ...... 5-7
...... 190-406-737 Alcatel-Lucent — Internal xi Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Deleting the FEP-NTM link ...... 5-9 Activating the FEP-NTM link ...... 5-11 Deactivating the FEP-NTM link ...... 5-13 Testing the FEP-NTM link ...... 5-15 Reestablishing FEP-Datakit links ...... 5-17
6AISwitch Configuration Introduction ...... 6-2 Tips on navigating through the AISwitch menu ...... 6-3 Configuring the AISwitch ...... 6-4 Configuring the AI296 Smart Line Cards ...... 6-7 Configuring the links for the AI296 Smart Line Cards ...... 6-10 Adding a new switch to the AISwitch ...... 6-15 Deleting a switch from the AISwitch ...... 6-20 Port–to–Link Mapping (SVC) ...... 6-22 Monitoring the AISwitch for troubleshooting purposes ...... 6-29 Copying the AI configuration onto the FEP ...... 6-31 Recovering the AI configuration file from the FEP ...... 6-33
AFEP Manual Pages aentity ...... A-3 anlink ...... A-4 appstat ...... A-5 bdr_act ...... A-7 bdr_commit ...... A-8 bdr_deact ...... A-10 bdr_stat ...... A-11 bdr_takeover ...... A-12 centity ...... A-13 chentity ...... A-17 cnlink ...... A-21 ddbkup_fep ...... A-22 ddrstr_fep ...... A-24 deaentity ...... A-27 deanlink ...... A-28
...... xii Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... delentity ...... A-29 delnlink ...... A-31 fsbackup_fep ...... A-32 fsrestore_fep ...... A-34 load_fep ...... A-36 logCat ...... A-37 prtsint ...... A-41 rsentity ...... A-42 rsnlink ...... A-44 startfep ...... A-46 stopfep ...... A-47 tlentity ...... A-48 tnlink ...... A-53
B Datakit VCS Settings Datakit VCS settings with GTD-5 switches ...... B-2 Entering Datakit VCS settings for CPM-HS with a FEP ...... B-3 Entering Datakit VCS settings for TY-12 ...... B-7 Datakit VCS settings with 5ESS, DMS, and DMS 250 switches ...... B-11 Entering Datakit VCS setting w/SLM ...... B-14
C FEP System Responses FEP system responses ...... C-3 AUD — Audit Trail Messages AUD 001 ...... C-7 AUD 002 ...... C-8 AUD 003 ...... C-9 AUD 004 ...... C-10 AUD 005 ...... C-11 AUD 006 ...... C-12 AUD 007 ...... C-13 AUD 008 ...... C-14 AUD 009 ...... C-15 AUD 010 ...... C-16 AUD 011 ...... C-17
...... 190-406-737 Alcatel-Lucent — Internal xiii Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 012 ...... C-18 AUD 013 ...... C-19 AUD 014 ...... C-20 AUD 015 ...... C-21 AUD 016 ...... C-22 BDR — Backup and Disaster Recovery Commands BDR 001 ...... C-24 BDR 002 ...... C-25 BDR 003 ...... C-26 BDR 004 ...... C-27 BDR 005 ...... C-28 BDR 006 ...... C-29 BDR 007 ...... C-30 BDR 008 ...... C-31 BDR 009 ...... C-32 BDR 010 ...... C-33 BDR 011 ...... C-34 BDR 012 ...... C-35 BDR 013 ...... C-36 BDR 014 ...... C-38 BDR 015 ...... C-39 BDR 016 ...... C-40 BDR 017 ...... C-41 BDR 018 ...... C-42 BDR 019 ...... C-43 BDR 020 ...... C-44 BDR 021 ...... C-45 BDR 022 ...... C-46
CMD — User Commands CMD 017 ...... C-48 CMD 019 ...... C-49 CMD 020 ...... C-50 CMD 021 ...... C-51
...... xiv Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... CMD 022 ...... C-52 CMD 023 ...... C-53 CMD 024 ...... C-54 CMD 025 ...... C-55
EDCS — GTD-5 Event Data Collection Subsystem EDCS 001 ...... C-57 EDCS 002 ...... C-58 EDCS 003 ...... C-59 EDCS 004 ...... C-60 EDCS 005 ...... C-61 EDCS 021 ...... C-62 EDCS 022 ...... C-63 EDD — GTD-5 Data Distributor EDD 001 ...... C-65 EDD 002 ...... C-66 EDD 003 ...... C-67 EDD 004 ...... C-68 EDD 005 ...... C-70 EDD 006 ...... C-71 EDD 007 ...... C-72 EDD 008 ...... C-73 EDD 009 ...... C-74 EDD 010 ...... C-75 EDD 011 ...... C-76 EDD 012 ...... C-77 EDD 013 ...... C-78 EDD 014 ...... C-79 EDD 015 ...... C-80 EDD 016 ...... C-81
IPNDC — Internet Protocol Network Data Collector IPNDC 101 ...... C-85 IPNDC 111 ...... C-86 IPNDC 114 ...... C-87
...... 190-406-737 Alcatel-Lucent — Internal xv Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 115 ...... C-88 IPNDC 116 ...... C-89 IPNDC 117 ...... C-90 IPNDC 118 ...... C-92 IPNDC 119 ...... C-93 IPNDC 120 ...... C-94 IPNDC 121 ...... C-95 IPNDC 122 ...... C-96 IPNDC 123 ...... C-97 IPNDC 125 ...... C-98 IPNDC 126 ...... C-99 IPNDC 127 ...... C-100 IPNDC 128 ...... C-101 IPNDC 129 ...... C-102 IPNDC 130 ...... C-103 IPNDC 132 ...... C-104 IPNDC 133 ...... C-106 IPNDC 134 ...... C-108 IPNDC 135 ...... C-110 IPNDC 139 ...... C-111 IPNDC 140 ...... C-113 IPNDC 144 ...... C-114 IPNDC 145 ...... C-116 IPNDC 146 ...... C-118 IPNDC 149 ...... C-120 IPNDC 150 ...... C-122 IPNDC 152 ...... C-124 IPNDC 153 ...... C-125 IPNDC 154 ...... C-127 IPNDC 155 ...... C-128 IPNDC 156 ...... C-129 IPNDC 157 ...... C-130 IPNDC 158 ...... C-131
...... xvi Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 159 ...... C-132 IPNDC 161 ...... C-133 IPNDC 162 ...... C-134 IPNDC 165 ...... C-135 IPNDC 166 ...... C-136 IPNDC 167 ...... C-137 IPNDC 168 ...... C-139 IPNDC 169 ...... C-140 IPNDC 170 ...... C-141 IPNDC 171 ...... C-142 IPNDC 172 ...... C-144 IPNDC 173 ...... C-145 IPNDC 174 ...... C-147
LM — BaseWorX Log Manager LM 001 ...... C-149
NDC — Network Data Collector NDC 101 ...... C-153 NDC 111 ...... C-154 NDC 114 ...... C-155 NDC 115 ...... C-156 NDC 116 ...... C-157 NDC 117 ...... C-158 NDC 118 ...... C-160 NDC 119 ...... C-161 NDC 120 ...... C-162 NDC 121 ...... C-163 NDC 122 ...... C-164 NDC 123 ...... C-165 NDC 125 ...... C-166 NDC 126 ...... C-167 NDC 127 ...... C-168 NDC 128 ...... C-169 NDC 129 ...... C-170
...... 190-406-737 Alcatel-Lucent — Internal xvii Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 130 ...... C-171 NDC 132 ...... C-172 NDC 133 ...... C-174 NDC 134 ...... C-176 NDC 135 ...... C-178 NDC 139 ...... C-179 NDC 140 ...... C-181 NDC 144 ...... C-182 NDC 145 ...... C-184 NDC 146 ...... C-186 NDC 149 ...... C-188 NDC 150 ...... C-190 NDC 152 ...... C-192 NDC 153 ...... C-193 NDC 154 ...... C-195 NDC 155 ...... C-196 NDC 156 ...... C-197 NDC 157 ...... C-198 NDC 158 ...... C-200 NDC 159 ...... C-202 NDC 161 ...... C-203 NDC 162 ...... C-204 NDC 165 ...... C-205 NDC 166 ...... C-206 NDC 167 ...... C-207 NDC 168 ...... C-209 NDC 169 ...... C-210 NDC 170 ...... C-211 NDC 171 ...... C-212 NDC 172 ...... C-214 NDC 173 ...... C-215 NDC 174 ...... C-217
...... xviii Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT — Network Management NMT 001 ...... C-221 NMT 004 ...... C-222 NMT 006 ...... C-223 NMT 007 ...... C-225 NMT 008 ...... C-226 NMT 009 ...... C-227 NMT 010 ...... C-228 NMT 013 ...... C-230 NMT 014 ...... C-231 NMT 015 ...... C-234 NMT 016 ...... C-235 NMT 018 ...... C-236 NMT 019 ...... C-238 NMT 022 ...... C-239 NMT 023 ...... C-240 NMT 024 ...... C-242 NMT 025 ...... C-244 NMT 026 ...... C-246 NMT 027 ...... C-247 NMT 029 ...... C-248 NMT 030 ...... C-249 NMT 037 ...... C-251 NMT 038 ...... C-252 NMT 041 ...... C-253 NMT 042 ...... C-254 NMT 045 ...... C-255 NMT 046 ...... C-256 NMT 047 ...... C-258 NMT 048 ...... C-259 NMT 049 ...... C-260 NMT 050 ...... C-261 NMT 051 ...... C-262
...... 190-406-737 Alcatel-Lucent — Internal xix Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 052 ...... C-263 NMT 054 ...... C-264 NMT 055 ...... C-265 NMT 056 ...... C-266 NMT 057 ...... C-268 NMT 058 ...... C-270 NMT 059 ...... C-271 NMT 060 ...... C-272 NMT 061 ...... C-273 NMT 062 ...... C-274
RT — BaseWorX Rapid Transit RT 004 ...... C-276 RT 007 ...... C-277
SLM — Synchronous Line Module SLM 005 ...... C-279
SYM — FEP System SYM 001 ...... C-283 SYM 002 ...... C-284 SYM 003 ...... C-285 SYM 004 ...... C-286 SYM 006 ...... C-287 SYM 007 ...... C-288 SYM 011 ...... C-289 SYM 012 ...... C-290 SYM 014 ...... C-291 SYM 015 ...... C-292
TRN — GTD-5 Translators TRN 001 ...... C-295 TRN 002 ...... C-296 TRN 003 ...... C-298 TRN 004 ...... C-300 TRN 005 ...... C-302 TRN 006 ...... C-303
...... xx Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 007 ...... C-304 TRN 008 ...... C-305 TRN 009 ...... C-306 TRN 010 ...... C-308 TRN 011 ...... C-309 TRN 012 ...... C-310 TRN 013 ...... C-311 TRN 014 ...... C-312 TRN 015 ...... C-313 TRN 016 ...... C-314 TRN 017 ...... C-315 TRN 018 ...... C-317 TRN 019 ...... C-318 TRN 020 ...... C-319 TRN 021 ...... C-320 TRN 022 ...... C-321 TRN 023 ...... C-323 TRN 024 ...... C-324 TRN 025 ...... C-326 TRN 026 ...... C-328 TRN 027 ...... C-329 TRN 028 ...... C-330 TRN 029 ...... C-331 TRN 030 ...... C-333 TRN 031 ...... C-334 TRN 032 ...... C-335 TRN 033 ...... C-336 TRN 034 ...... C-338 TRN 035 ...... C-339 TRN 036 ...... C-341 TRN 037 ...... C-342 TRN 038 ...... C-343 TRN 039 ...... C-344
...... 190-406-737 Alcatel-Lucent — Internal xxi Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 040 ...... C-345 TRN 041 ...... C-346 TRN 042 ...... C-347 TRN 044 ...... C-349 TRN 045 ...... C-350 TRN 046 ...... C-351 TRN 047 ...... C-352 TRN 048 ...... C-353 TRN 049 ...... C-355 TRN 050 ...... C-356
GL Glossary IN Index
...... xxii Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
List of figures
1-1 FEP (Front-End Processor) ...... 1-2 1-2 Data flow and switch types ...... 1-3 3-1 Items included in the audit log ...... 3-19 3-2 Throttle summary message example ...... 3-25 3-3 End-of-period throttle summary message example ...... 3-25 3-4 “appstat” output example ...... 3-31 3-5 Back up onto un-write-protected tape ...... 3-43 3-6 bdr_stat command output ...... 3-91 3-7 bdr_stat output ...... 3-92 3-8 bdr_act output ...... 3-93 4-1 Connecting a switch to your FEP ...... 4-3 4-2 Output for office connected via Datakit ...... 4-8 4-3 Output for a polled GTD-5 office ...... 4-8 4-4 Output for a DMS 250 office ...... 4-8 4-5 Office collecting valid 5-minute data ...... 4-14 4-6 Office collecting suspect 5-minute data ...... 4-15 4-7 Example of tlentity ...... 4-18 4-8 Sample rsentity output ...... 4-32 5-1 Connecting your FEP to NTM ...... 5-2 5-2 “rsnlink” output example ...... 5-5 B-1 Boards with GTD-5 switches ...... B-2 B-2 Boards with 5ESS and DMS type switches ...... B-12 B-3 Datakit II SLM (synchronous line module) switch settings for I/O board ED-5P077-30,G1 ...B-12 C-1 A FEP system response, with its software subsystem code circled ...... C-3
...... 190-406-737 Alcatel-Lucent — Internal xxiii Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction List of tables
1-1 Logging in as “fep” ...... 1-7 1-2 Logging in as “root” ...... 1-8 1-3 Routine tasks ...... 1-10 2-1 Task List: Installation tasks ...... 2-5 3-1 Default logins ...... 3-4 3-2 Log Types/Contents ...... 3-19 3-3 Examples: Reading the audit, error or BDR logs ...... 3-21 3-4 Three types of backups ...... 3-41 3-5 Default list of files and directories backed up by “ddbkup_fep” ...... 3-51 3-6 Which restore procedure to use ...... 3-56 3-7 Disk Layout Configuration ...... 3-59 3-8 BDR task/enter/response ...... 3-86 4-1 Supported Switch Generics ...... 4-3 4-2 “rsentity” output fields/descriptions ...... 4-9 4-3 “prtsint” Output Fields/Description ...... 4-15 4-4 Items/Descriptions of Changeable Fields ...... 4-33 5-1 “rsnlink” Output Fields/Descriptions ...... 5-6 6-1 Port to X25 Link Mapping (SVC Example Setup) ...... 6-22 C-1 Software subsystem codes ...... C-3
...... 190-406-737 Alcatel-Lucent — Internal xxiv Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction About This Document
Purpose This document tells how to install, monitor, and manage a FEP (Front End Processor) as part of 8920 Network Traffic Management software network (NetMinder is a registered trademark of Alcatel-Lucent Inc. in various countries outside the United States).
Scope Areas beyond the scope of the document are as follows: • NTM. The NTM guides are described in “About This Document Set” (p. 1) in the System Overview. • vi. You are expected to be able to use vi or another visual editor, so file editing is not explained here. • FEP application software. Although you may be called upon to install, start, or stop FEP application software, you do not need to understand how that software works. Generally, this guide mentions process names only as information you may need to report to support persons when you are troubleshooting. • FEP Hardware. A FEP runs on a Sun Ultra I or Ultra II computer. See that computer’s manuals for how to operate it. • FEP Operating system. A FEP uses the Solaris 2.5.1 Operating system, the BaseWorX platform, and Korn shell (also called “ksh”). See respective vendor documents for details about each. (However, this guide will rarely refer you to those documents. Instead, we attempt to tell you exactly what to enter.) The FEP also uses Datakit VCS and TCP/IP to collect data from switches.
Intended audience The guide is for system administrators who manage the FEP(s).
...... 190-406-737 Alcatel-Lucent — Internal xxv Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Conventions used This section describes the conventions used in this and other NTM documents, when those conventions differ from the ones described in “About This Document Set” (p. 1) in the NTM System Overview.
Note on DMS switches In this document, information pertaining to the DMS 100 switch can also be applied to the DMS 200 switch.
Note on use of the term “entity” Generally, in this guide, we say “switch” to refer to a switch. However, FEP manual pages, error messages, and other references often use the term “entity”. Other synonyms are “office” and “network element”.
Entering commands When you are instructed to enter a command (for example, “Enter rsentity at the CMD: prompt of any menu.”), it is implied that you follow that command with Return.
Note: Some FEP commands related to NTM may use an earlier name for the product — NTMOS (Network Traffic Management Operations System).
...... xxvi Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
1 Getting Started
Overview
Purpose This chapter provides basic information on what FEP is and what it does.
This chapter contains the following topics:
What is FEP? 1-2
FEP software 1-4
FEP hardware 1-5
Logins 1-6
Manual pages 1-9
Routine tasks 1-10
...... 190-406-737 Alcatel-Lucent — Internal 1-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... What is FEP?
Overview FEP (Front End Processor) is a computer that gathers data from one or more switches and forwards it to the NTM computer. The FEP also carries audit requests and switch controls from the NTM computer to the switches.
Other terms NTM documents refer to collectors generically as DCCs (Data Collector Concentrators). Other NTM DCCs at various sites are called EADAS (Engineering and Data Acquisition System), NPM (Network Performance Monitor), and TDM (Traffic Data Management) machines. In this document, we discuss FEPs only.
Figures See Figure 1-1 and Figure 1-2. For a more hardware-oriented view of switch-FEP-NTM connections, see the figures in Appendix B, “Datakit VCS Settings” to determine how the FEP fits into NTM.
Figure 1-1 FEP (Front-End Processor)
Most NTM guides deal with system administration you do at the NTM host computer’s system console. As shown in Figure 1-1, this guide explains system administration you do at the FEP’s system console or a remote terminal logged in to the FEP.
...... 1-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Remote login is recommended due to the sporadic error messages that appear on the FEP system console. Most administrative tasks can be done remotely. When logging in remotely, the X-terminal emulation is recommended. This will become more of a standard due to the use of Graphic User Interfaces (GUIs). See Figure 1-2 for information on data flow.
Figure 1-2 Data flow and switch types
...... 190-406-737 Alcatel-Lucent — Internal 1-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... FEP software
Prerequisites Before the processor (Sun Ultra I or Ultra II) can run the FEP application software, it must be running the following software platforms: • Solaris Operating System: the workstation processor must be running its Solaris 2.5.1 Operating system and associated patches. Sun has issued several patches to fix operating system bugs or to better comply with Year 2000 requirements. • C Compiler: is required for data collection from monitored GTD-5 switches. • Datakit VCS: handles communications with various network elements. The FEP needs to run Datakit VCS SBus Interface software. Pacific Access is the vendor for Datakit VCS software. • BaseWorX: manages the FEP application processes and error messages. • TCP/IP: handles communications between the FEP and the NTM Host. TCP/IP is also used to communicate with polled GTD-5 switches.
Features If additional features have been purchased, you will need to turn on those features by loading the feature tape that was customized for your company.
...... 1-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... FEP hardware
Components 1. Processor • Sun Ultra I computer with one internal 2.1 G disk or • Sun Ultra II computer with one internal 8.6G disk 2. Terminal (also called the system console, or the FEP console). A Sun color monitor. (The system console becomes the FEP console only when the FEP application software is running. But, in this guide we usually say FEP console in any case.) 3. cdrom drive. An internal CDROM (one that is built into the processor unit). 4. 4mm tape drive. A Sun Desktop Storage Module external drive unit, with a 5.0 Gbyte 4mm tape drive. (for backups) 5. Datakit interface board. A Pacific Access board inside the FEP processor. It is connected by the optical fiber cable to the CPM-HS (Computer Port Module-High Speed) board in the Datakit VCS processor. 6. Optical fiber cable. This connects the CPM-HS board to a Datakit VCS node. 7. Ethernet cable with RJ45 connectors (not shown). This connects the built-in Ethernet connector on the processor to your Ethernet network. This cable is only needed if you plan to connect the FEP to NTM via TCP/IP or if you plan to collect data from polled GTD-5 switches. 8. AISwitch 180 with 1-3 AI296 X.25/IP interface cards. This is only needed if you plan to collect data from polled GTD-5 switches.
...... 190-406-737 Alcatel-Lucent — Internal 1-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Logins
Default logins The “fep”, “root”, “bworx”, and “support1” logins are default logins set up during installation.
To l o g in a s … …enter this login ID Comment FEP fep This is the login you use administrator (Or any “fep” type login.) most often. Super user root There can be only one root login. BaseWorX bworx This login is only used for administrator installing BaseWorX software. Customer support1 Customer support persons Support would use this to remotely log in, if needed.
Remote login In the next two tables we show how to log in at the FEP console, or through a remote terminal. You can log in through a remote terminal if it is connected through Datakit VCS to the FEP. To do this you must know the Datakit VCS dialstring to the FEP, which you can get from your Datakit VCS administrator. Alternatively, you can log in via Ethernet. Table 1-1 tells how to log in as “fep”. Table 1-2 tells how to log in as “root”.
...... 1-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
Table 1-1 Logging in as “fep” If you are at this terminal... At this prompt… Then enter … FEP console
...... 190-406-737 Alcatel-Lucent — Internal 1-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
Table 1-2 Logging in as “root” If you are at this terminal… At this prompt… Then enter… FEP console
FEP console or None, but instead you are su - remote terminal already logged in as “fep”
...... 1-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Manual pages
Description A manual page explains how to use a command. In most cases, you can call up a manual page online by using the man command. In more detail:
If a procedure says, then, to see the command’s manual for example… page… Enter the FEP command Enter man startfep or see page (A-46). startfep. Enter the Solaris Enter man ufsdump or see Solaris command ufsdump. documents. Enter pwd.Enter man pwd or see Solaris documents. (We don’t bother with “Enter the Solaris command” for Solaris’s common, UNIX type commands such as vi, ls, pwd, and so on.) Enter the BaseWorx Enter man logCat. command logCat. (The only BaseWorX commands you use are appstat, logCat, tapemgr, and throtcnfg. These manual pages are on- line. Also, see “appstat” (p. A-5) and “logCat” (p. A-37).) Enter the Datakit See Datakit VCS documents. command enter (Datakit commands are only mentioned in group. Appendix B, “Datakit VCS Settings” only. Typically, only the Datakit administrator would use these commands. They can only be used at the Datakit console.)
Note: Except for Datakit VCS commands, all of the command types above can be entered from “fep”, or “root” logins, as well as from any “fep” type logins you create. However, some commands require you to log in as “root”. Procedures always tell you when this is needed.
...... 190-406-737 Alcatel-Lucent — Internal 1-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Routine tasks
Description Table 1-3 explains routine tasks you do to monitor and maintain the FEP. Not included here, or in this document, are maintenance procedures for FEP hardware.
Note: See the FEP hardware vendor’s documentation for maintenance procedure tasks. Table 1-3 Routine tasks (Sheet 1 of 4) Task Name Frequency Description Reference Monitor FEP Daily The error log shows informational “Monitoring the audit, audit BDR, and error messages generated by error, or BDR log files” and error log the FEP application. The audit log (p. 3-23). (At first, you may messages shows informational messages want to use these several regarding messages passed between times a day, until you get a the NTM host and the FEP. The feel for normal FEP BDR log shows informational and operations.) error messages regarding the Reference: Backup and Disaster Recovery feature. Reference: See Appendix C, “FEP System Responses” for how to respond to error messages. Monitor Occasionally or when To see the most recent listing of Appendix C, “FEP Solaris or having problems with these messages, use the dmesg System Responses” does Datakit VCS Solaris or Datakit command. Older messages are in NOT tell how to respond to messages VCS. files at “/var/adm”. The newest of these messages. Instead, see these files is named “messages”, the Solaris or Datakit VCS next newest is “messages.0”, then documents. “messages.1”, “messages.2”, and so on. To see when each file was last written, enter ls -l messages*. To read these files, use the view command. Monitor Daily Do for all switches you are “Checking switch status” switches responsible for, to make sure data is (p. 4-7). being collected and forwarded to NTM.
...... 1-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Table 1-3 Routine tasks (Sheet 2 of 4) Task Name Frequency Description Reference Read mail sent Daily Log in as root and read root’s to root mail. There are two ways to do this, as follows: • At the FEP console, log in directly as root and then enter mail to see root’s mail. However, console error messages may make it hard to read mail here. • Log in initially with another login ID then enter su - to become root, and then enter mail. (Be sure to use su - and not just su. If you use only su, the mail command will show you mail to your initial login ID, not mail to root). Perform At least weekly, if not Make sure there is always a tape in “Restoring” (p. 3-56) to set dynamic data daily. the tape drive. up “cron” to do this backups automatically. Perform You should do this after This backs up only those files that “Performing a full or incremental any software update is have changed since the last full incremental backup in backups applied to the system. backup. Make sure there is always a single-user mode” (p. 3-45) (This could be a patch or tape in the tape drive if you choose Use “Performing an generic update for to do this automatically. automatic full/incremental Solaris, for FEP backup of filesystems” application software (p. 3-49) to set up “cron” to etc.) do this automatically.
...... 190-406-737 Alcatel-Lucent — Internal 1-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table 1-3 Routine tasks (Sheet 3 of 4) Task Name Frequency Description Reference Perform full There are two cases If you always have a current full A full backup (“Full or backups when a full backup is backup, you will never need to do incremental backup” essential: an incremental backup. Of course, (p. 3-43)) takes about an • After initial full backups take longer to hour. installation complete than incremental backups. You may use “Performing • After you do a full In the event you need to restore just an automatic restore (the full a file or small directory, it will take full/incremental backup of restore procedure longer to recover it from a full or filesystems” (p. 3-49) to set reminds you to do incremental backup tape versus a up “cron” to do this this). dynamic data backup tape. automatically. Then, all you There are two cases will have to do is make sure when a full backup is there is always a tape in the highly recommended: tape drive. • Every month, in case full backup tapes are lost or damaged. Additionally, this will cause you to reboot the FEP (see Reboot below). • If you add a lot of software patches, you may find incremental backups are taking longer and longer to do. To speed up incremental backups, you can do a new full backup. Reboot Once a month. Rebooting takes about 15 minutes “Rebooting the FEP” and helps keep the FEP “clean” by (p. 3-29) checking file systems and performing simple diagnostics on FEP hardware.
...... 1-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Table 1-3 Routine tasks (Sheet 4 of 4) Task Name Frequency Description Reference Update for Arizona and parts of Define each switch Daylight Indiana do not use See “Creating a switch” Savings Time, Daylight Savings Time, (p. 4-25) with its time zone if needed so if you have switches difference relative to its or a FEP in those areas, FEP. you will need to update See “Changing a switch’s the time zone difference record base data on the for affected switches FEP” (p. 4-31) if it is every spring and fall necessary to change the when Daylight Savings time zone offset in the FEP. Time begins and ends.
...... 190-406-737 Alcatel-Lucent — Internal 1-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
...... 1-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
2 Installing the FEP
Overview
Purpose This chapter tells how to install the FEP (Front End Processor) 5.0 system, either from scratch, or retrofitting from an existing FEP 4.0 system. The FEP 5.0 runs on an Ultra I or Ultra II, running the Solaris 2.5.1 Operating system.
When to use This should be the only time to reference this chapter, assuming you make full backups of the FEP on a monthly basis. If you do not make regularly scheduled full backups (which we strongly recommend that you do), revisit this chapter in the event of a fatal hardware problem, such as a disk crash.
Disclaimer This chapter was correct when written, but installation procedures are apt to change. For that reason, a Lucent Technologies representative will assist you during your initial FEP installation.
...... 190-406-737 Alcatel-Lucent — Internal 2-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
This chapter contains the following topics:
Before you begin installation 2-3
Installation tasks 2-4
Retrofitting from FEP4.0 to FEP5.0 2-6
Installing Solaris 2.5.1 on a Sun Ultra system 2-12
Installing FEP installation scripts 2-16
Installing SPARCompiler C 4.2 2-18
Installing BaseWorX 2-23
Installing BaseWorX packages 2-24
Provisioning BaseWorX 5.1 2-26
Installing Datakit VCS host interface 2-28
Installing FEP’s Ethernet TCP/IP connection 2-31
Installing the FEP application 2-34
Installing features 2-37
Installing Solaris 2.5.1 recommended and Year 2000 patches 2-38
Installing Y2K compliant SUN patches 2-40
...... 2-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Before you begin installation
Hardware information These instructions assume the following hardware has been set up. • Processor • Terminal • 4mm tape drive • For Datakit connections: – Datakit interface board – Optical fiber cable • For Ethernet connections: – Ethernet cable with RJ45 connectors – AISwitch 180 and up to 3 AI296 X.25/IP interface cards for polled GTD-5 switches
Reference: “FEP hardware” (p. 1-5)
Software information To install the FEP 5.0 system software, you need a: • Solaris 2.5.1 installation CD (11/97 version) (Solaris 2.5.1 is also referred to as Solaris 5.5.1.) • FEP 5.0 Installation tape • SPARCompiler C 4.2 CD • BaseWorX 5.1 tape • PAC Access SBus version 3.8 Datakit Interface software tape — Enterprise (ET) • FEP 5.0 Application tape • FEP 5.0 Feature tape • Solaris 2.5.1 Recommended and Year 2000 patch clusters tape • Sun Patches 2.5.1 and 2.5.6 CD • Any FEP 5.0 Application Patch tape
...... 190-406-737 Alcatel-Lucent — Internal 2-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installation tasks
Purpose Use the Task List in Table 2-1 if you are installing FEP 5.0 from scratch to keep track of the software installation. If you are upgrading your existing FEP 4.0 system to FEP5.0, use “Retrofitting from FEP4.0 to FEP5.0” (p. 2-6). Each of these tasks must be performed in order, with the exception that the Datakit SBus Interface software can be installed any time after Solaris 2.5.1 is installed — but before the FEP application is installed. This procedure assumes hardware has already been set up. A complete installation should take about 13 hours, not including a full backup which should be done immediately after completing the installation. Please note that: • In this chapter, we show you the prompts you need to respond to, but we omit most informational screen output. • This document does not cover the setup of Datakit hardware at the Datakit VCS node. (However, for settings, see Appendix B, “Datakit VCS Settings”.
...... 2-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... List of tasks The following table lists the tasks involved in installing the FEP, with their associated page numbers and estimated time. Table 2-1 Task List: Installation tasks Estimated Loading Time on an Ultra II Task Name (page) (minutes) “Installing Solaris 2.5.1 on a Sun Ultra system” 60 (p. 2-12) “Installing FEP installation scripts” (p. 2-16) 5 “Installing SPARCompiler C 4.2” (p. 2-18) 20 “Installing BaseWorX packages” (p. 2-24) 10 “Provisioning BaseWorX 5.1” (p. 2-26) 5 “Installing Datakit VCS host interface” (p. 2-28) 15 “Installing FEP’s Ethernet TCP/IP connection” 15 (p. 2-31) “Installing the FEP application” (p. 2-34) 5 “Installing features” (p. 2-37) 2 “Installing Solaris 2.5.1 recommended and Year 180 2000 patches” (p. 2-38) “Installing Y2K compliant SUN patches” 480 (p. 2-40) “Performing a full or incremental backup in 120 single-user mode” (p. 3-45)
...... 190-406-737 Alcatel-Lucent — Internal 2-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Retrofitting from FEP4.0 to FEP5.0
Purpose Use the following procedure to upgrade your system from FEP4.0 to 5.0. This procedure will take approximately 3 hours to complete.
Before you begin You need: • FEP5.0 installation tape • FEP5.0 application tape • FEP5.0 feature tape
Restrictions FEP5.0 supports a maximum of 150 offices. If there are currently more than 150 offices defined on your FEP4.0 system, you must delete the extra offices and create them on another FEP having ample capacity. If you attempt to retrofit a FEP4.0 system containing more than 150 offices, only the first 150 offices will be retrofitted to FEP5.0. Any remaining offices will be lost in FEP5.0 and thus not monitored by your NTM host.
References Read the memorandum (if any) that came with the software. It supplies any instructions you may need in addition to this procedure. This procedure assumes you are familiar with the vi editor.
Instructions Follow these steps:
......
1 Make a full backup of your FEP4.0 system.
Reference: “Procedure: Full or Incremental Backup in Single-User Mode” in the FEP4.0 Administration Guide
......
2 Log in as “root”.
...... 2-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
3 Ensure the FEP application is “Shutdown”. Enter: appstat Reference: appstat command (A-5)
......
4 If the FEP application is running, enter: stopfep Reference: stopfep command (A-47)
......
5 Load the FEP5.0 Installation tape. Enter: cd /install_fep_scripts ......
6 Insert tape labelled “Installation Tape” into the tape drive. Enter: tar xvf /dev/rmt/0 ......
7 Remove the tape from the tape drive.
......
8 Load the FEP5.0 Application tape.
Reference: “Installing the FEP application” (p. 2-34)
......
9 Unset the following variables. Enter: unset FEP_ROOT unset FEP_ETC ......
10 Verify the variables are unset. Enter: echo $FEP_ROOT echo $FEP_ETC Result: You should see a blank line when echoing these variables. This signifies they are unset.
...... 190-406-737 Alcatel-Lucent — Internal 2-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
11 Run the load_fep script. Enter: /usra/fep/bin/baseworx/scripts/load_fep ......
12 Load the FEP5.0 feature tape.
Reference: “Installing features” (p. 2-37)
......
13 Log off and log back in as “fep” to pick up the FEP5.0 environment.
......
14 Verify you are user “fep”. Enter: id ......
15 Verify the following environmental variables are set correctly. Enter: echo $FEP_ROOT (This should be “/usra/fep/bin”) echo $FEP_ETC (This should be “/usra/fep/etc”) ......
16 If any of this output is incorrect, repeat Step 13 through Step 15.
......
17 Run the retrofit script to gather existing entity information. Enter: retrofit Result: This will create the script,” ~fep/create_ents”, which you’ll run later to recreate your old FEP4.0 offices on your new FEP5.0 system.
......
18 Create a new FEP5.0 entities file. Enter: cd /usra/tusr/na/entity mv entities entities.fep4 crtentfile ......
19 Verify the entities file has been initialized. Enter: rsentity all
...... 2-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: No offices should be displayed. Ignore the REL003 error message if it appears in the output.
Reference: rsentity command (A-42)
......
20 Recreate the old FEP4.0 offices on your new FEP5.0 system. Enter: cd ......
21 Verify you are in the FEP home directory. Enter: pwd Result: You should see “/usra/grp/fep”.
......
22 Run the create_ents script. Enter: ./create_ents > create_ents.out 2>&1 ......
23 Scan the output file, create_ents.out, for any errors. Notify FEP Field Support if any errors are seen.
Result: An example of the expected output for a given office is as follows:
Retrofitting
Enter en_name (char[12]): Enter en_type (short): Enter dialstring (char[72]): Enter en_time (short): Enter en_generic (char[15]): Enter en_active (0 or 1): Enter en_nmtype (0 to 15): Enter en_collect (0 or 1): Enter dc_num (int): ......
24 Become “root”. Enter: su – ......
25 Convert the VPORT database from FEP4.0 to FEP5.0. Enter: echo $VPBASE
...... 190-406-737 Alcatel-Lucent — Internal 2-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
26 Determine VPBASE directory: • If VPBASE is not /usra, contact FEP Field Support for help before running the following commands. • If VPBASE is /usra, enter: initvp convert_vpdb > ~fep/convert_vpdb.out 2>&1 Result: The convert_vpdb script will take about 2 minutes to complete. Scan the output file, ~fep/convert_vpdb.out, for errors. An example of the expected output follows:
Port deleted Vport Name:
27 Start the FEP application. Enter: startfep Reference: startfep command (A-46)
......
28 Verify the FEP application is running. Enter: appstat Reference: appstat command (A-5)
......
29 Verify all entities appear on your FEP5.0 system and 5-minute data is being collected. Enter: rsentity all Reference: rsentity command (A-42)
......
30 Make a full backup of your FEP5.0 system.
...... 2-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Reference: “Performing a full or incremental backup in single-user mode” (p. 3-45)
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing Solaris 2.5.1 on a Sun Ultra system
Purpose Use the following procedure to install the Solaris 2.5.1 basic operating system on a Sun Ultra system.
Before you begin This procedure assumes that you have booted from the Solaris CD.
Reference: “Booting from Solaris CD” (p. 3-82)
Instructions Follow these steps:
......
1 Click Continue at the Install Solaris Software - Initial Menu display.
......
2 Click Continue at the System Type display to assume the default of Stand-alone.
......
3 Click the Entire Distribution plus OEM support button at the Software display to assume the default of Stand-alone.
......
4 Click Continue.
......
5 Select the only disk shown (c0t0d0) from the list of available disks.
......
6 Click Add to move the c0t0d0 from the Available Disks submenu to the Selected Disks submenu.
......
7 Click Continue.
......
8 Click Continue at the Preserve Data? display.
...... 2-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
9 Click Auto-layout at the Automatically Layout File Systems? display.
......
10 Click /opt, /usr/openwin, and /var to select all of the file systems at the Automatically Layout File Systems display.
......
11 Click Continue.
......
12 Click Customize at the File System and Disk Layout display.
......
13 Click /export/home at the Customize Disks display and:
For ULTRA 1: a. Change the directory to /usra and its size to 800. b. Change the swap size to 384. c. Change the /var size to 363. d. Change the /usr size to 110. e. Change the /size to 59.
For ULTRA 2: a. Change the directory to /usra and its size to 2026. b. Change the swap size to 1000. c. Change the /var size to 1500. d. Change the /usr size to 1500. e. Change the /size to 600. f. Change the /opt size to 1000. g. Change the /usr/openwin size to 1000.
......
14 Press Tab to show zero free MB left.
Note: There should be zero free MB left.
......
15 Click OK.
...... 190-406-737 Alcatel-Lucent — Internal 2-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
16 Choose the layout:
For ULTRA 1: a. If the layout shown below is correct, click Continue. b. If the layout is not correct, click Customize and modify the layout to match this example. File System and Disk Layout / c0t0d0s0 59 MB swap c0t0d0s1 384 MB overlap c0t0d0s2 2028 MB /usr/openwin c0t0d0s3 146 MB /var c0t0d0s4 363 MB /opt c0t0d0s5 163 MB /usr c0t0d0s6 110 MB /usra c0t0d0s7 800 MB
For ULTRA 2: a. If the layout shown below is correct, click Continue. b. If the layout is not correct, click Customize and modify the layout to match this example. File System and Disk Layout / c0t0d0s0 601 MB swap c0t0d0s1 1001 MB overlap c0t0d0s2 8633 MB /usr/openwin c0t0d0s3 1001 MB /var c0t0d0s4 1500 MB /opt c0t0d0s5 1001 MB /usr c0t0d0s6 1500 MB /usra c0t0d0s7 2026 MB ......
17 Click Continue at the Mount Remote File Systems? display.
......
18 Verify the information on the screen is correct at the Profile display. a. If correct, click Begin Installation. b. If incorrect, click Change.
......
19 Click Reboot at the Reboot option display
...... 2-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
20 Monitor the progress of the installation by watching the Solaris Install Console Window or the Installing Solaris Progress window at the Installing Solaris - Progress Menu display.
Result: After the Solaris installation is completed, you are prompted twice for a root password.
......
21 Enter the root password both times you are prompted for it at the Root password: display.
Note: The delete key takes the place of the backspace key. The Control-C sequence takes the place of the delete key. The backspace key does not function.
......
22 Log in as root at the Console Login prompt display.
......
23 Enter: eject cdrom ......
24 Remove the CD ROM.
......
25 Check the installation patch logs for any errors by entering: cd /var/sadm/install_data pg install_log pg Maintenance_Update_log.*
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-15 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing FEP installation scripts
Purpose Use the following procedure to install the FEP installation scripts.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Make a directory for FEP install scripts by entering: mkdir /install_fep_scripts ......
3 Change to directory for FEP install scripts by entering: cd /install_fep_scripts ......
4 Load the tape labeled “Installation Tape” in to the tape drive.
......
5 Wait for green light on the tape drive to stop flashing.
......
6 If /dev/rmt/
......
7 Enter: tar xvf /dev/rmt/0 ......
8 Set up FEP’s default environment, enter: ./config_fepsys ......
9 Enter a new password for bworx.
......
10 Enter a new password for fep.
...... 2-16 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
11 Enter a new password for support1.
......
12 Remove the tape from the tape drive.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-17 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing SPARCompiler C 4.2
Purpose Use the following procedure to install the SPARCompiler C 4.2 and license on a Sun Workstation.
Before you begin This procedure assumes that you are familiar with the workstation and the windows environment. You will need to complete the following steps before starting this task: • Find the serial number and authorization code. To do this, look on the license certificate that came with the compiler. • Find the machine name and host ID. To do this, log onto the host machine on which the compiler will be licensed and enter:
Example: /usr/ucb/hostid Output will be the host ID, such as:
Example: 72300dd9 • With the information you got from above steps, call SunPro at the following number:
Example: 1-800-USA-4SUN and ask for your 20-digit hexadecimal password and other password related information. SunPro will provide you with a password and vendor string. This password and Vendor String (VS) will be used later on in this procedure.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Insert the Solaris 2.X CD-ROM, labeled “Sun WorkShop Compilers C/C++ 4.2”, in the cdrom drive.
......
3 Start OpenWindows. Enter: /usr/openwin/bin/openwin
...... 2-18 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
4 Start kornshell in the CONSOLE window. Enter: /bin/ksh ......
5 Create an xterm window in the CONSOLE window. Enter: export DISPLAY=
......
6 Click on the xterm window.
......
7 Enter: cd /cdrom/devpro_v5n1_sparc ......
8 Enter: ./workshop_install ......
9 Choose n at the following display: The software will be installed by default in /opt. Do you wish to change the installation location?
......
10 Click both: • License Manager Software and Utilities. • WS Comp C/C++ SPARC, 4.2
......
11 Verify those buttons are selected.
......
12 Click the Install button (not Install Licenses) to start the software installation. This will take approximately 10 minutes to complete.
...... 190-406-737 Alcatel-Lucent — Internal 2-19 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
Result: The Installing software - progress window appears.
......
13 After the installation is complete, click the “Install Licenses” button.
Result: The License installation Tool (lit) window appears.
......
14 Click Entered by hand... You will be entering information for the Compiler only. Result: A “lit: Add license to be installed window” will appear.
......
15 Click No for Demo Licensing.
......
16 Verify that the Feature Name field is set to WS Complier C SPARC.
......
17 Click Right to Use (RTU) and enter 1.
......
18 Click Password and enter the password you received from Sun for the Compiler.
......
19 Click Vendor String (VS) and enter 0.
......
20 Verify that the data checksum number and the Password checksum number matches the information you have received from the license distribution center. • If either checksum number is different from yours, you must contact the license distribution center so that the checksum numbers match.
......
21 Click add, then click close.
......
22 Verify that in License Installation Tool window WS Compiler C SPARC, 4.2 1
......
23 Click install.
...... 2-20 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: The message “License Installation was successful” should appear in the bottom left corner of the window.
......
24 Click OK in the informational message box.
......
25 Click Cancel in the License Installation Tool (lit) menu.
......
26 Click Cancel in the Install Software menu.
......
27 Stop the License Manager. Enter: /etc/rc2.d/S85lmgrd stop ......
28 Enter y at the following display: Shutting down FLEXm on nodes:
29 Exit from the xterm. Enter: exit ......
30 Click on the CONSOLE window.
......
31 Eject the CD-ROM. Enter: cd / eject ......
32 Start the License Manager. Enter: /etc/rc2.d/S85lmgrd start ......
33 Verify the license manager is running, enter: /etc/opt/licenses/lmstat -a -c /etc/opt/licenses/licenses_combined
...... 190-406-737 Alcatel-Lucent — Internal 2-21 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: You should see the following output:
Copyright (C) 1989-1994 Globetrotter Software, Inc. Flexible License Manager status on
34 Exit out of all windows to # prompt.
Hint: Right button on mouse, click exit.
...... E ND OF STEPS ......
...... 2-22 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Installing BaseWorX
Overview The following procedures comprise this process: • “Installing BaseWorX packages” (p. 2-24) • “Provisioning BaseWorX 5.1” (p. 2-26)
...... 190-406-737 Alcatel-Lucent — Internal 2-23 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing BaseWorX packages
Purpose Use the following procedure to install the BaseWorX 5.1 tape.
Instructions Follow these steps:
......
1 Insert the BaseworX tape and wait for the tape to rewind (until the light on the tape drive stops flashing).
......
2 Log in as bworx (or enter “id” to verify that you are “bworx”).
......
3 Read in BaseworX tape. Enter: cd /install_fep_scripts ./read_bworx ......
4 Enter the tape drive name or press Return to select the default device.
Result: The system responds with messages similar to:
Reading in tape... cpio -icbv tapemgr < /dev/rmt/0 When the tape has been read, proceed to the next step.
......
5 For each tapemgr prompt listed below, enter the response shown. Enter the name of the REWIND tape device [?, q]: /dev/rmt/0 Enter the name of the NON-REWINDING tape device [?, q]: /dev/rmt/0n Do you wish to install or remove packages: [install remove quit?] install Result: The list of packages available will appear.
Enter selections to install [all help quit]: all Selection complete — installpkg starting...... 2-24 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: The next few prompts will be repeated several times, each time with the name of a different package, such as “Common Software”.
INSTALLING
6 Since you want the default, press Return.
......
7 Remove the BaseWorX 5.1 tape from the tape drive.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-25 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Provisioning BaseWorX 5.1
Purpose Use the following procedure to provision the BaseWorX 5.1 system.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Enter: ln -s /opt/SUNWspro/bin/cc /bin/cc ......
3 Log in as bworx.
......
4 Enter: cd /install_fep_scripts ./provision_bworx ......
5 For each prompt listed below, enter the response shown. Do you want an explanation on the screen, in addition to prompts? y Do you want an explanation file to be created (it will be /usra/grp/bworx/platsetlog) with extra information and pointers to documentation? (y) [y,n,?,q]: y Enter the root directory (RAPIDROOT) where BaseWorX is installed (/usra/baseworx) [?,q]: /usra/baseworx Enter the directory (ROAMCNFG) where you want your application area to be created (/usra/grp/bworx/bwx5.1) [?,q]: /usra/grp/bworx/bwx5.1 Enter a short tag (APPTAG) for your application (fep): fep If you plan to use TUXEDO/T, enter the directory where it is installed (none) [n,q,?]: n
...... 2-26 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: Next, several pages of information will appear on your screen, ending with the message:
platesetup completed successfully ......
6 Enter: exit
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-27 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing Datakit VCS host interface
Purpose Use the following procedure to connect the FEP to Datakit VCS.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Insert the PacAccess SBus Datakit Interface tape in the tape drive. Wait while the tape rewinds. This takes about a minute.
......
3 Start the installation. Enter: pkgadd -d /dev/rmt/0 ......
4 For each prompt listed below, enter the response shown. Type [go] when ready, or [u] to unload/offline the tape, or [q] to quit: go Select package(s) you wish to process (or ‘all’ to process all packages). (default: all) [?,??,q]: 1 Processing package instance
Note: At this point, if you see a prompt asking if you want to replace administrative files, answer y. If this is the first time Datakit is being installed, you will not see this prompt. Do you want the NEW uucp files installed; (default = y) [y,n,?,q]: y Note: The installation will take approximately 5 minutes Result: At this point, you may have to wait about 2 minutes until the next prompt appears.
...... 2-28 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 For each prompt listed below, enter “y”. Do you want the TLI drivers installed; (default = n) [y,n,?,q]: This package can be configured to run on a Commkit Server or Client. Is this package being installed on a Commkit Server; (default = y) [y,n,?,q] Do you want to install these conflicting files [y,n,?,q]: Do you want to install these setuid/setgid files [y,n,?,q]: Do you want to continue with the installation of
Installation of
6 Enter “q” for the prompt: Type [go] when ready, or [u] to unload/offline the tape, or [q] to quit: ......
7 To find the host ID, enter: /usr/ucb/hostid Result: Output will be the host ID, such as: 72300dd9
......
8 Find the last four digits of the serial number of the Datakit VCS software tape. This number is found on the envelope the tape came in, and also on a licensing sheet in the front of the Datakit VCS user manual.
......
9 Call 1-800-648-6022 with the host ID and the last four digits of the serial number of the delivered software tape and ask for the password. The password is a 20-digit alpha numeric value.
......
10 Use the password (for the “password” parameter), and the last four digits of the serial number of the delivered software (for the “4digits” parameter), in the following command to install the license: /usr/dk/etc/dkdaemon -k <4digits>
......
11 Enter: cd /install_fep_scripts ./install_dkit ......
12 Ask the Datakit administrator to do any needed Datakit VCS node configuration, and to activate the connection.
Reference: “Entering Datakit VCS settings for CPM-HS with a FEP” (p. B-3).
Hint: You may proceed with “Installing FEP’s Ethernet TCP/IP connection” (p. 2-31), and return to this procedure when this step has been completed.
......
13 Start the host interface daemon. Enter: /usr/dk/etc/dkdaemon -i0 -c 256 -x -t ......
14 Start the host interface server. Enter: /usr/dk/etc/dkserver -i0 -v3 ......
15 Verify that the daemon is running. Enter: ps -ef | grep dkdaemon ......
16 Remove the tape from the tape device.
...... E ND OF STEPS ......
...... 2-30 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Installing FEP’s Ethernet TCP/IP connection
Purpose Use the following procedure to configure the FEP for TCP/IP networking. This enables the FEP to communicate over the Ethernet already installed on NTM. The FEP configuration comes with 1 TCP/IP port, which is hme0, so plug the Ethernet cable into the hme0 port.
Before you begin Your local network administrator must have already made preparations for allowing your FEP to use TCP/IP. Contact one local network administrator for the following information: • TCP/IP address for this FEP • Default router address for this FEP • Network mask if the FEP is part of a network that is subnetted
Instructions Follow these steps:
......
1 Log in as root.
......
2 Enter: uname -n > /etc/hostname.hme0
Note: The extension is the letter ‘l’ — not the number 1 (one).
......
3 Enter: cat /etc/hostname.hme0 ......
4 Verify that the output of this command is the hostname of the FEP. You will need this in the next step.
...... 190-406-737 Alcatel-Lucent — Internal 2-31 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
5 If your local network administrator has given you a default router address for the FEP, enter: echo
6 Verify the contents of the file. Enter: cat /etc/defaultrouter Repeat this step if the output does not match the information given to you by your local network administrator.
......
7 If your local network administrator has given you a network mask address for the FEP’s network, enter: echo
8 Verify the contents of the file. Enter: cat /etc/inet/netmasks Repeat this step if the output does not match the information given to you by your local network administrator.
......
9 Enter: vi /etc/inet/hosts ......
10 Change the contents of the file from: 127.0.0.1 localhost loghost
11 Write and quit the file.
......
12 Check if the FEP is running. Enter: appstat
...... 2-32 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
13 If it is running, then shut down the FEP by entering: stopfep ......
14 At the # prompt enter: halt ......
15 At the OK prompt enter: boot -r ......
16 If your FEP does not come up multi-user or you have problems using TCP/IP to talk to the NTM host, please contact your local network administrator for assistance.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-33 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing the FEP application
Purpose Use this procedure to install the FEP application software. This is the program that is automatically started when you boot your computer, and which turns your computer into the FEP.
Before you begin Before beginning the installation of the FEP application, check that the “fep” login has been set up. If not, follow the instructions in “Installing FEP installation scripts” (p. 2-16) for setting up the “fep” login.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Install the FEP application. Enter: cd /install_fep_scripts ./install_fep Result: The system responds with:
---- Installing Fep Application Software ---- Attention!!!! Insert the fep application tape into tape drive and wait until the tape rewinds (until the light on the tape drive stops flashing) Hit
3 When you are prompted for “rewind device”, enter: /dev/rmt/0 ......
4 When you are prompted for “nonrewind device”, enter: /dev/rmt/0n
...... 2-34 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 When you are prompted “Do you wish to install or remove packages?”, enter: [install remove quit?]: install ......
6 Respond as indicated to the following prompts: Packages available 1. fep Enter selection(s) to install [all, help, quit] all Selection complete — installpkg starting. INSTALLING
7 Ignore the following message: /usra/fep already exists ......
8 Respond as indicated to the following prompts: Continuing the installation may result in over written files Do you want to continue the installation [y,n,q]: y Do you want to select another directory [y,n,q]: n Hint: This step will generate many pages of output. If you are directing output to a printer, you may want to stop doing so until you continue with the next step.
......
9 Wait for the following message: fep Release 5 version:0 issue:0 has been installed......
10 Remove the tape from the tape drive.
...... 190-406-737 Alcatel-Lucent — Internal 2-35 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
11 Add any software updates that have been issued in the proper numerical order.
Reference: “Installing an update” (p. 3-35)
......
12 Follow this decision tree: • If you are retrofitting from FEP 4.0 to FEP5.0, STOP, YOU HAVE COMPLETED THIS PROCEDURE. Go back to the procedure that referred you here. • If you are NOT retrofitting from FEP4.0 to FEP5.0, continue with the next step.
......
13 To execute the load_fep script, while logged in as root, enter: /usra/fep/bin/baseworx/scripts/load_fep Result: This script displays trace output as commands are executed.
...... E ND OF STEPS ......
...... 2-36 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Installing features
Purpose Use this procedure to turn on any features you have purchased.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Load the FEP feature tape in the tape device.
......
3 Enter: /usra/fep/bin/readfeat ......
4 Remove the tape from the tape device.
......
5 Go back to the procedure that referred you here.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-37 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing Solaris 2.5.1 recommended and Year 2000 patches
Purpose Use this procedure to install Solaris 2.5.1 and year 2000 patches.
Instructions Follow these steps:
......
1 Log in as root.
Hint: To verify you are “root” with group “tdms”, enter “id”. You should see “uid=0(root) gid=100(tdms)”. If you do not see this, log off and log back in, then verify again.
......
2 Load the Solaris 2.5.1 mandatory patches tape in the tape drive.
......
3 Wait until it finishes rewinding. This should take about a minute.
......
4 Go into the patch directory. Enter: cd /usra/patches/2.5.1patch ......
5 Enter pwd to ensure that your current directory is “/usra/patches/2.5.1patch” before running the tar command. To read the installed tape, enter: tar xvf /dev/rmt/0
Note: Wait while all the files are extracted from the tape. This will take about 10 minutes.
......
6 Remove the tape from the tape drive after it is finished rewinding.
......
7 Install Solaris 2.5.1 Recommended patches. Enter: cd Recommended ./install_cluster -q
Note: This will take approximately 3 hours.
...... 2-38 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... If you see the following message during or at the conclusion of the patch installation, contact Lucent Customer Support: “The following patches were not able to be installed:”
......
8 Install Year 2000 patches. Enter: cd .. cd y2000 ./install_cluster -q
Note: This will take approximately 15 minutes. If you see the following message during or at the conclusion of the patch installation, contact Lucent Customer Support: “The following patches were not able to be installed:”
......
9 Remove the patch directories that were read in from the tape. Enter: cd ......
10 Enter pwd to ensure that your current directory is “/usra/patches/2.5.1patch” before running the rm command.
......
11 From the /usra/patches/2.5.1patch directory, enter: rm -rf * ......
12 Reboot the FEP to activate the Solaris 2.5.1 patches. Enter: reboot ......
13 After the FEP has rebooted, log in as “fep” and verify that the FEP processes are up. Enter: appstat Reference: appstat command (A-5)
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-39 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Installing Y2K compliant SUN patches
Purpose Use this procedure to install the SUN PATCHES 2.5.1 and 2.6 CD. This CD must be installed after the Solaris 2.5.1 mandatory patches tape.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Stop the FEP Application. Enter: stopfep ......
3 Insert the CDROM in the CD drive.
......
4 Access the contents of the CDROM. Enter: cd /cdrom/cdrom ls Result: The contents of the CDROM should contain 3 directories:
• rr_moved — This is empty and is used only as part of making the CDROM. • solaris2.5.1 — This has the SUN 2.5.1 patches. • solaris2.6 — This has the SUN 2.6 patches.
......
5 Change directory to the correct version of Solaris Directory. Enter: cd solaris2.5.1 ls Result: The contents under the Solaris 2.5.1directory of the CDROM should contain the following information:
• README file • RecommendedPatches — a directory of patches necessary to bring Solaris 2.5.1 up-to- date so that the Year 2000 patches will work • Y2KPatches — a directory of patches to make solaris 2.5.1 year 2000 compliant. • install_patch — a shell script called by y2kpatch to actually install the necessary patches
...... 2-40 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
• y2kpatch — the main shell script to install Year 2000 patches
......
6 Start a log file to capture installation output. Enter: script /load.out (this will save output to a file) ......
7 Install the patches. Enter: ./y2kpatch Result: The installation of patches takes approximately 8 hours (Ultra1/2).
......
8 Stop writing to the log file. Enter: exit ......
9 Verify no errors are in load. Enter: cat /load.out Result: There should be 2 patches that fail: 104317-01 and 103566-41. These are rendered obsolete.
......
10 Reboot the system. Enter: reboot
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 2-41 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
...... 2-42 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
3 Administering the FEP
Overview
Purpose This chapter provides procedures you use at the FEP.
Switch name parameter Various FEP commands in this chapter use switch name as a parameter. Switch name is the 11-character CLLI. In each case, you can instead use the switch number, which is a unique “nickname” you assign to the switch.
Hint: Switch numbers are assigned using “Creating a switch” (p. 4-25)
This chapter contains the following topics:
Administering user logins 3-4
Adding a “fep” type user login using Admintool 3-5
Adding a “fep” type user login from the command line 3-7
Deleting a user login using Solaris Admintool 3-9
Deleting a user login from the command line 3-11
Administering hosts using Solaris 3-12
Adding a host using Admintool 3-13
Adding a host from the command line 3-15
Deleting a host using Solaris Admintool 3-16
Deleting a host from the command line 3-18
Audit, error logs, and BDR 3-19
...... 190-406-737 Alcatel-Lucent — Internal 3-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
Looking into error, audit, and BDR logs 3-21
Monitoring the audit, error, or BDR log files 3-23
Throttling or unthrottling an audit or error message 3-24
FEP application software 3-28
Rebooting the FEP 3-29
Checking application status 3-30
Starting the FEP software 3-33
Stopping the FEP software 3-34
Installing an update 3-35
Removing an update 3-38
Backup 3-41
Performing a full or incremental backup in single-user mode 3-45
Keeping or putting away the tape after backup 3-48 Performing an automatic full/incremental backup of filesystems 3-49
Dynamic data backup 3-51
Performing automatic backup of dynamic data 3-53
Performing a manual backup of dynamic data 3-55
Restoring 3-56
Forcing a crash dump and rebooting the system 3-58
Restoring the FEP after a disk crash 3-59
Restoring /(root) and /usr filesystem 3-61
Restoring filesystems other than /(root) and /usr 3-66
Restoring a directory or file (not dynamic data) 3-68
Restoring dynamic data (all or some) 3-72
Partitioning and formatting a disk 3-75
Booting from Solaris CD 3-82
Backup Disaster and Recovery (BDR) 3-85
Configuring BDR 3-87
Verifying BDR 3-91
...... 3-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
BDR take over/switch back system administration tasks 3-95
Government emergency telecommunications service (GETS) 3-98
...... 190-406-737 Alcatel-Lucent — Internal 3-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Administering user logins
Overview The following procedures comprise this process: • “Adding a “fep” type user login using Admintool” (p. 3-5) • “Adding a “fep” type user login from the command line” (p. 3-7) • “Deleting a user login using Solaris Admintool” (p. 3-9) • “Deleting a user login from the command line” (p. 3-11)
Adding “fep” logins When your FEP was installed, four default logins were set up, as listed in Table 3-1. As this table explains, you may need to add more “fep” type logins. Table 3-1 Default logins Default login Used by Would you add another login of this type? fep FEP administrators Yes. If there is more than one person who will be administering the FEP, you may want to give each FEP administrator his or her own login. bworx BaseWorX installer No. This login is used only when installing the FEP from scratch. root System administrators No. There can be only one root login. support1 Customer support No. Support persons share this login.
Administering logins using Solaris Solaris provides two methods for administering logins: 1. Through a point and click interface 2. By the command line
Choosing the right procedure If you have access to an X-terminal emulator, or you are adding logins at the FEP console (a Sun color monitor), we recommend using “Adding a “fep” type user login using Admintool” (p. 3-5). The Solaris admintool is the preferred method for adding or deleting user logins. Use “Adding a “fep” type user login using Admintool” (p. 3-5) to add users from an X- terminal window.
...... 3-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Adding a “fep” type user login using Admintool
Purpose This procedure adds a user login with the same permissions as the default login “fep”.
Instructions Follow these steps:
......
1 If you will be logging in remotely to add a user, on your local system, enter: xhost
2 If you will be logging in directly to add a user from the fep system console (which must be a Sun color monitor), then start Openwindows if it is not already running. Enter: openwin ......
3 Open a kornshell window to run Admintool.
......
4 Enter: admintool ......
5 From the Browse menu, select “Users”.
......
6 From the Edit menu, select “Add”.
......
7 The following fields should be defined: User Name:
...... 190-406-737 Alcatel-Lucent — Internal 3-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: This option forces the user to assign a password upon first login.
Select “Create Home Dir” box (This should be default) Path: /usra/grp/
Note: Please consult with your Network Administrator for Account Security information.
......
8 Select “OK”.
......
9 From the file menu, select “Exit”.
......
10 The new user will need a “.profile”. Get a copy from the default “fep” login, and change its ownership to the user. For example, if the new user is “jas” enter the following: cp /usra/grp/fep/.profile /usra/grp/jas chown jas /usra/grp/jas/.profile
...... E ND OF STEPS ......
...... 3-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Adding a “fep” type user login from the command line
Purpose This procedure adds a user login with the same permissions as the default login “fep”.
Instructions Follow these steps:
......
1 Log in as fep. Then enter: su - ......
2 Do not create a home directory for the user. That will happen automatically in the next step.
Hint: If you already created the home directory ahead of time, you can keep it if you give it correct permissions. For example, if the new user has a login ID of “jas”, enter: chown jas /usra/grp/jas chgrp tdms /usra/grp/jas chmod 755 /usra/grp/jas ......
3 To add a new user, enter the following Solaris command (you would type this as one line): useradd -c
...... 190-406-737 Alcatel-Lucent — Internal 3-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
4 Prevent others from writing in your home directory. Enter: chmod 755 /usra/grp/jas Hint: The new user will need a “.profile”. Get a copy from the default “fep” login, and change its ownership to the user. For example, if the new user is “jas”, enter: cp /usra/grp/fep/.profile /usra/grp/jas chown jas /usra/grp/jas/.profile ......
5 To verify that Step 3 worked, look for the user’s login ID in “/etc/passwd”. For example, for user “jas”, enter: grep jas /etc/passwd Result: You should see something similar to:
jas:x:10575:100:John A. Smith:/usra/grp/jas:/bin/ksh Meaning: • jas — The user’s login ID. • x — The user’s encoded password is in “/etc/shadow”. • 10575 — A unique number representing the user. • 100 — The user’s group ID number, which is “100” (user group “tdms”). • John A. Smith — The comments you entered in Step 3. • /usra/grp/jas — The path to the user’s home directory. • /bin/ksh — The shell program the user will use.
......
6 Still logged in as root, enter the passwd command. For example, for new login ID “jas”, you would enter: passwd jas Result: System prompts will guide you in assigning the new password.
......
7 Tell the user the password you assigned, and tell him or her to log in and enter passwd as soon as possible, to assign a new password.
...... E ND OF STEPS ......
...... 3-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Deleting a user login using Solaris Admintool
Purpose Use this procedure to delete user logins using the Admintool.
Before you begin As a courtesy, warn the to-be-deleted user that his or her login and home directory will be removed. This gives the user an opportunity to look through his or her home directory files, so he or she can print them or save them to tape.
Instructions Follow these steps:
......
1 Follow this decision tree: • If you will be logging in remotely to delete a user, on your local system, enter: xhost
• If you will be logging in directly to add a user from the fep system console (which must be a Sun color monitor), then start Openwindows if it is not already running. Enter: openwin ......
2 Open a kornshell window to run Admintool.
......
3 Enter: admintool ......
4 From the Browse menu, select Users.
......
5 Scroll down until you highlight the user you wish to delete.
...... 190-406-737 Alcatel-Lucent — Internal 3-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
6 From the Edit menu, select Delete.
......
7 Select OK
......
8 From the file menu, select Exit.
...... E ND OF STEPS ......
...... 3-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Deleting a user login from the command line
Purpose Use this procedure to delete user logins from the command line.
Before you begin As a courtesy, warn the to-be-deleted user that his or her login and home directory will be removed. This gives the user an opportunity to look through his or her home directory files, so he or she can print them or save them to tape.
Instructions Follow these steps:
......
1 Log in as fep. Enter: su - ......
2 Delete the user. Enter: userdel -r
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Administering hosts using Solaris
Overview The following procedures comprise this process: • “Adding a host using Admintool” (p. 3-13) • “Adding a host from the command line” (p. 3-15) • “Deleting a host using Solaris Admintool” (p. 3-16) • “Deleting a host from the command line” (p. 3-18) Solaris provides two methods for administering hosts: 1. Through a point and click interface 2. By the command line
Choosing the right procedure If you have access to an X-terminal emulator, or you are adding logins at the FEP console (which is a Sun color monitor), we recommend using “Adding a host using Admintool” (p. 3-13). If you have access to a terminal with only an ASCII interface, use “Adding a host from the command line” (p. 3-15).
Adding a host These procedures describe how to add a host to the FEP. In order for the two machines to communicate, the FEP will also need to be added on the other host.
Deleting a host When you no longer need to communicate with a host, use one of the following procedures to remove it. The preferred method is using Solaris Admintool.
...... 3-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Adding a host using Admintool
Purpose This procedure adds a host using the Solaris Admintool.
Instructions Follow these steps:
......
1 Follow this decision tree: • If you will be logging in remotely to add a user, on your local system, enter: xhost
• If you will be logging in directly to add a user from the fep system console (which must be a Sun color monitor), then start Openwindows if it is not already running. Enter: openwin ......
2 Open a kornshell window to run Admintool.
......
3 Enter: admintool ......
4 From the Browse menu, select Hosts.
......
5 From the Edit menu, select Add.
......
6 The user then inputs existing host name(s) and IP address(es).
......
7 Select OK.
...... 190-406-737 Alcatel-Lucent — Internal 3-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
8 Select OK.
......
9 From the file menu, select Exit.
...... E ND OF STEPS ......
...... 3-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Adding a host from the command line
Purpose This procedure adds a host using the command line.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Edit the “/etc/inet/hosts” file, adding a line for each host you wish to add. You will need to enter the host name and TCP/IP address. Enter: vi /etc/inet/hosts
Example: For example, if the new host’s TCP/IP address were “127.7.29.99”, you would enter: 127.7.29.99
3 Write and quit the file.
Note: To communicate with the new host you’ve added, it is necessary for the administrator of that host to add your FEP’s host name and TCP/IP address to their system.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-15 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Deleting a host using Solaris Admintool
Purpose This procedure deletes a host using Solaris Admintool.
Instructions Follow these steps:
......
1 Follow this decision tree: • If you will be logging in remotely to delete a user, on your local system, enter: xhost
• If you will be logging in directly to add a user from the fep system console (which must be a Sun color monitor), then start Openwindows if it is not already running. Enter: openwin ......
2 Open a kornshell window to run Admintool.
......
3 Enter: admintool ......
4 From the Browse menu, select Hosts.
......
5 Scroll until you highlight the host you wish to delete.
......
6 From the Edit menu, select Delete.
Result: The prompt “Are you sure you want to delete
......
7 Select Delete
...... 3-16 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
8 From the file menu, select Exit.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-17 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Deleting a host from the command line
Purpose This procedure deletes a host using the command line.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Edit the “/etc/inet/hosts” file, deleting the line for each host you wish to remove.
......
3 Write and quit the file.
...... E ND OF STEPS ......
...... 3-18 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Audit, error logs, and BDR
Overview The following procedures comprise this process: • “Looking into error, audit, and BDR logs” (p. 3-21) • “Monitoring the audit, error, or BDR log files” (p. 3-23) • “Throttling or unthrottling an audit or error message” (p. 3-24)
Overview of audit and error messages Figure 3-1 lists items included in the audit log. Table 3-2 lists log types and their contents.
Figure 3-1 Items included in the audit log
Table 3-2 Log Types/Contents This Log … Contains … Audit Audit messages about data collection and transmission, as illustrated in Figure 3-1.
...... 190-406-737 Alcatel-Lucent — Internal 3-19 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table 3-2 Log Types/Contents This Log … Contains … Error All of the messages found in the audit log Error messages from the FEP and BaseWorX systems Informational messages such as process starts and terminations BDR Error and informational messages when running BDR commands.
...... 3-20 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Looking into error, audit, and BDR logs
Purpose Use this procedure to view log files.
Before you begin With all these examples, log in as “fep”.
Hint: In these examples, “-l” is minus-lowercase-L.
Instructions Follow these steps:
......
1 To look into the error and log files, use the logCat command, as demonstrated in the Table 3-3.
Note: You cannot vi audit and error logs. They are compressed, at cd $LOGDATA.
Reference: logCat command (A-37)
Table 3-3 Examples: Reading the audit, error or BDR logs If the log type is To … …Enter … List 50 most recent Errors logCat -t 50 … Audits logCat -t 50 -l audit BDR logCat -t 50 -l bdr List all messages Errors logCat -a “07/07/98 00:00:00” -z “07/07/98 logged between 12:00:00” midnight and noon Audits logCat -a “07/07/98 00:00:00” -z “07/07/98 on July 7, 1998 … 12:00:00” -l audit BDR logCat -a “07/07/98 00:00:00” -z “07/07/98 12:00:00” -l bdr
...... 190-406-737 Alcatel-Lucent — Internal 3-21 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table 3-3 Examples: Reading the audit, error or BDR logs If the log type is To … …Enter … List all messages Errors logCat -a “07/07/98 00:00:00” -z “07/07/98 logged between 12:00:00” -s/ AUD007”/ midnight and noon on July 7, 1998, Hint: Remember, the error file also holds all audits. that also contain Audits logCat -a “07/07/98 00:00:00” -z “07/07/98 the string 12:00:00” -s/ “AUD007”/ -l audit “AUD007” … BDR logCat -a “07/07/98 00:00:00” -z “07/07/98 12:00:00” -s/ “AUD007”/ -l bdr Use paging with Errors logCat -t 50 | pg the logCat Audits logCat -t 50 -l audit | pg command … BDR logCat -t 50 -l bdr | pg Hint: With paging, data will come to your screen one page at a time. Use Return to advance a page. Use q to end paging.
...... E ND OF STEPS ......
...... 3-22 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Monitoring the audit, error, or BDR log files
Purpose Use this procedure to turn your terminal into a monitor of messages sent to the audit log, error log, or to the BDR log. Because this will tie up your terminal, you may want to do this on a remote terminal dedicated to that use, or in a software window, if available. You may see not only audit messages but also summary messages for throttled messages.
Reference: Figure 3-2; “Throttling or unthrottling an audit or error message” (p. 3-24)
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Choose a type of message to monitor: • Error. To monitor error messages, enter: logcat -t # -c
• Audit. To monitor audit messages, enter: logcat -t # -l audit -c
• BDR. To monitor BDR messages, enter: logcat -t # -l bdr -c Where # is the number of messages you want to view (up to 100)
Result: Since switch data is collected every 30 seconds and every 5 minutes, that is when you would see most switch-to-NTM audit messages.
Reference: logCat command (A-37)
......
3 To return from logcat, enter Delete.
Hint: If the terminal is listing messages, you may have to wait a few seconds before your shell prompt returns.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-23 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Throttling or unthrottling an audit or error message
Overview The number of routine messages going to the log files has already been minimized, so you will probably never need to use throttling. For customers who have purchased Feature 131, “FEP Backup and Disaster Recovery”, we do not recommend throttling BDR messages. These messages are only generated when an entity or NTM link definition is modified (which is infrequent after initial FEP setup). You may get tired of seeing the same message repeated in the audit or error logs. To enable you to cut down on this traffic, we offer “throttling”. When you throttle a message you do not totally screen it out. Instead, the error or audit log shows a summary (either daily, hourly or quarter-hourly), as illustrated in Figure 3-2.
Example If you throttled AUD007 type messages to quarter-hours, then the audit or error log (Figure 3-2) will show the first occurrence of a message of that type during a 15-minute interval. Then, at the end of the quarter-hour, the identical message is repeated, but now with a summary on two added lines, beginning with the word “Until”. Figure 3-3 shows that, from 15:00 until 15:15, the AUD007 message occurred 58 times.
Note: Figure 3-2 and Figure 3-3 refer to the same switch. This does NOT mean all counted messages refer to that same switch.
...... 3-24 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Figure 3-2 Throttle summary message example
Figure 3-3 End-of-period throttle summary message example
As detailed in Instructions, you throttle a message type by listing it in a specific file. Then the FEP throttles that message in the logs. If the message type goes to more than one log type, you cannot throttle it in one log and not in another.
Purpose Use the following procedure both to throttle and to unthrottle messages or to change the throttle interval of a message type.
Instructions Follow these steps:
......
1 Enter logcat to look into the log and find an example of the message you want to throttle. One such example might be the following: LOGGED: 10/20/98 16:09:04 SENT: 10/20/98 15:09:04 AUD007 INFO: 30-second report sent to NTMOS link 1 (1800 bytes). cbtdms5 fep:nmt FIX: rcv_nm.c :58
...... 190-406-737 Alcatel-Lucent — Internal 3-25 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
2 Write down the message’s number — in this example, AUD007.
......
3 Log in as fep.
......
4 Go to where the message format files are. Enter: cd $ROAMCNFG/config_data/fm/api/formats ......
5 Search the message format files for the message number you wrote down in Step 1. grep
Example: grep AUD007 *msg Result: A response resembling the following appears:
AUDmsg:AUD007 AUD_30STRN 30-second report received sent to NTOMS link %d (%d bytes) ......
6 Write down the file name and message name indicated in the response (in this case, AUDmsg and AUD_30STRN, respectively).
......
7 Enter: throtcnfg Result: This will put you in vi (visual editor) mode, inside the file listing all message types currently throttled, with each message type on a separate line.
To add a new message to be throttled … • If you want to throttle a message type, add a line with the following format (don’t forget the “:”):
...... 3-26 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Example: To hourly throttle AUD007 messages, add the following line: AUDmsg:AUD30STRN H
To change the interval by which a message is throttled … • If you want to change the throttling interval for a message type that is already throttled, find the message type’s line in this file and change its interval code.
Example: To take a message that has hourly throttling and change it to daily throttling, change “H” in the following line: AUDmsg:AUD30STRN H to “D”, as follows: AUDmsg:AUD30STRN D
To stop a message from throttling … • If you want to unthrottle a message… – Delete its line from the file, or – Comment it out using the # sign so the line will be ignored
Example: #AUDmsg:AUD30STRN H
......
8 After you finish editing the file (in Step 6), press the escape key and type :wq.
Result: This saves and exits the file.
Result: A “Validating configuration file….” message appears.
......
9 Wait a few minutes until you see a second message, as follows: Successful Validation Updates will be discarded if syntax errors exist. Re- edit? [y, n, ?, q] Where: • y — Take you back into the file for further editing. • n — Exit the command and installs your edits. • ? — Give you an explanation of the message above. • q — Discard your edits and exits the command.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-27 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... FEP application software
Overview The following procedures comprise this process: • “Rebooting the FEP” (p. 3-29) • “Checking application status” (p. 3-30) • “Starting the FEP software” (p. 3-33) • “Stopping the FEP software” (p. 3-34) • “Installing an update” (p. 3-35) • “Removing an update” (p. 3-38)
...... 3-28 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Rebooting the FEP
Recommended rebooting schedule Lucent Technologies recommends that the FEP system be rebooted on a regularly scheduled basis (once a month is highly suggested), because rebooting: • Executes machine-dependent diagnostics to verify hardware integrity • Executes operating system filesystem checks • Executes OS and application initialization • Verifies/maintains familiarity with local system procedures • Resets and verifies interfaces to networks and other applications including non-Lucent software • Minimizes unplanned system downtime
Purpose Use this procedure to reboot the FEP from multi-user mode. Prior to executing this procedure, you may want to issue a “wall” message to users to warn them of the impending reboot.
Instructions Follow these steps:
......
1 Log in as fep and shut down the FEP application software. Enter: stopfep ......
2 Enter su - to become root.
......
3 Enter reboot to reboot the FEP.
......
4 All connections to the FEP will be terminated and the processor will be restarted.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-29 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Checking application status
Purpose Use this procedure to see if the FEP application software processes are running. You might use this if the FEP were behaving abnormally. You are NOT expected to understand how FEP processes work, but if you are discussing problems with a Lucent Customer Support person, you may be asked to run the command and read them the output.
Instructions Follow these steps:
......
1 Log in as fep and enter: appstat Result: Output appears on your terminal screen (Figure 3-4).
Reference: appstat command (A-5)
......
2 If the FEP is: • NOT running its application software, you will see “CURRENT RUN LEVEL IS: Shutdown”. Use “Starting the FEP software” (p. 3-33) to restart it. • Running its application software, you will see “CURRENT RUN LEVEL IS: Running”, followed by a list of FEP application processes (“daemons”).
......
3 Determine process number: • If each process has a number other than “0” under the “Pid” column, all processes are running; STOP. YOU HAVE COMPLETED THIS PROCEDURE. • If any process has “0” under the “Pid” column, then that process is not running. Continue with this procedure.
......
4 For the process with “0” under the “Pid” column, if the number in the “Respawn” column is “4”, FEP has given up trying to respawn. a. If “Respawn” is less than “4”, enter appstat a few more times, to see if respawn is successful, returning “Pid” to a number other than “0”. If respawn is successful, STOP. YOU HAVE COMPLETED THIS PROCEDURE, but every so often use appstat again, to check. b. If “Respawn” becomes “4”, with “Pid” “0”, go to the next step.
...... 3-30 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 Stop and restart FEP software. • That is, while logged in as “fep”, enter: stopfep • Then, after you see the message, “NEW RUN LEVEL: Shutdown”, enter: startfep Reference: “Stopping the FEP software” (p. 3-34) “Starting the FEP software” (p. 3-33)
......
6 If appstat shows that the “Pid” is still “0”, log in as root and enter the following Solaris command to reboot the Solaris operating system: reboot ......
7 After reboot finishes, you can log in again. You will not need to restart FEP application software — that happens automatically with reboot.
......
8 If appstat shows that the “Pid” is still “0”, report the problem to Lucent Customer Support
...... E ND OF STEPS ......
Output Output is illustrated in Figure 3-4. If you want a detailed explanation of output, see the appstat manual page (enter man appstat). But, for purposes of this procedure, you are primarily interested in the “Pid” column. This column gives the UNIX process ID. If this is “0”, the process (the “daemon”) is not running.
Figure 3-4 “appstat” output example CURRENT RUN LEVEL IS: Running
DEMONS:
Demon Name Pid Process Name Strt Persist Respawns Opt
logdaemon 357 logdaemon -a -t -m 6 R Yes 0 logmgr 423 logmgr R Yes 0 monitor1 424 monitor C1 R Yes 0 nmt 930 $FEP_ROOT/nmt >/dev/ R No 0
...... 190-406-737 Alcatel-Lucent — Internal 3-31 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... ndc 937 $FEP_ROOT/ndc >/dev/ R No 0 ipndc 1061 $FEP_ROOT/ipndc >/de R No 0 dc_mgr 1203 $FEP_ROOT/dc_mgr >/d R No 0 edcsdd 3217 $FEP_ROOT/edcsdd >/d R No 0 ctlAud 5211 $FEP_ROOT/ctlAud >/d R No 0 transdisc 5214 $FEP_ROOT/transdisc R No 0 trans5min 5314 $FEP_ROOT/trans5min R No 0
...... 3-32 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Starting the FEP software
Purpose Use this procedure to start the FEP software.
Hint: If you want to see if FEP application software is currently running or shutdown, use the appstat command, explained in “Checking application status” (p. 3-30).
Instructions Follow these steps:
......
1 Start the software: • If the Sun Ultra I or Ultra II is NOT running, boot it. Then, STOP. YOU HAVE COMPLETED THIS PROCEDURE — the startfep command will execute automatically. • If the Sun Ultra I or Ultra II is running, but the FEP software is not running (for example, after you used the stopfep command to stop it), then log in as fep and enter: startfep Result: As processes are started, messages will scroll down your screen, ending with the message:
NEW RUN LEVEL: Running
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-33 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Stopping the FEP software
Purpose Use this procedure to start the FEP software.
Hint: If you want to see if FEP application software is currently running or shutdown, use the appstat command, explained in “Checking application status” (p. 3-30).
Instructions Follow these steps:
......
1 Log in as fep and enter: stopfep Result: First, the following warning message will appear on the screen of any terminal logged in at the FEP:
Warning: FEP Application shutting down in 60 seconds.
Then, as processes are killed, messages will scroll down your screen, ending with the message: NEW RUN LEVEL: Shutdown
Now your computer is running only the Solaris operating system, in MULTI-user mode.
...... E ND OF STEPS ......
...... 3-34 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Installing an update
Purpose A FEP software update (also called a patch) may be delivered with the initial software, and you may receive additional updates after that. If you receive more than one update at the same time, you must install them in order (the installation program will stop you if you attempt to install updates out of order). Differentiate updates by comparing the “Issue” numbers.
Before you begin If you changed any of the following, then your changes will be lost — overwritten by the defaults from the update patch. • “/etc/profile” • “/.profile” • “/usra/grp/fep/.profile” • “/usra/grp/support1/.profile” • “/usra/fep/bin/ddfiles” So, before you begin this procedure, take some action to preserve your changes. For example, you could print a hard copy of the files, and then reenter your changes after completing this procedure. Or copy the files to tape/disk, or to other filenames/directories. Read the memorandum that came with the update tape. It will give you any instructions you may need in addition to this procedure.
Instructions Follow these steps:
Note: If, for any reason, you want to back out during update installation, returning your software to its pre-update state, select the “quit” option during the installation procedure.
......
1 Log in as root at the system console.
......
2 Enter: stopfep Result: When you see the message, “NEW RUN LEVEL: shutdown”, your computer is running only the Solaris operating system, in MULTI-user mode.
...... 190-406-737 Alcatel-Lucent — Internal 3-35 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
3 Enter: cd /usra/fep ......
4 Load the FEP application update tape in the tape drive. Enter: cpio -icBvu tapemgr
......
5 Enter: /bin/sh ./tapemgr
Note: Use the full path, “/bin/sh ./tapemgr”. Entering “tapemgr” alone could cause problems.
......
6 When you are prompted for “REWIND”, enter: /dev/rmt/0 ......
7 When you are prompted for “NON-REWINDING”, enter: /dev/rmt/0n ......
8 When you are prompted “Do you wish to install or remove packages?”, enter: install ......
9 When you are prompted for the package to install, enter: all ......
10 When you are prompted to install it, enter: y ......
11 When you are prompted for the directory to install fep’s root directory, enter: /usra Result: A list of files appears.
...... 3-36 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
12 If you see “End of medium on ‘input’. To continue, type device/file name when ready”, enter: /dev/rmt/0 ......
13 Wait for the following message: fep Release 5 Version:0 Issue:1 has been installed.
The installpkg from tape has completed- You may remove the tape after the rewind is complete......
14 Execute the load_fep script. Enter: /usra/fep/bin/baseworx/scripts/load_fep This script produces trace output as commands are executed. Check that all commands execute normally; note any exceptions. Contact FEP development about any exceptions.
Reference: load_fep command (A-36)
......
15 Do an incremental or full software backup.
Reference: “Performing a full or incremental backup in single-user mode” (p. 3-45) starting with Step 2.
Note: It is recommended that you do the incremental or full backup now. If you are not doing it now, then you will need to restart the FEP. To do that, enter the following (unless the memorandum that came with the update tells you to do a reboot instead): startfep
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-37 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Removing an update
Purpose When Customer Support informs you that a FEP software update is no longer required, use the following procedure to remove it.
Before you begin If you changed any of the following, then your changes will be lost — overwritten by the defaults from the “load_fep” script. • “/etc/profile” • “/.profile” • “/usra/grp/fep/.profile” • “/usra/grp/support1/.profile” • “/usra/fep/bin/ddfiles” So, before you begin this procedure, take some action to preserve your changes. For example, you could print a hard copy of the files, and then reenter your changes after completing this procedure. Or copy the files to tape/disk, or to other filenames/directories. Read the memorandum that came with the update tape. It will give you any instructions you may need in addition to this procedure.
Instructions If, for any reason, you want to stop the “tapemgr” command, select the “quit” option during the removal procedure.
......
1 Log in as fep.
......
2 Enter su - to become root.
......
3 Enter: stopfep Result: When you see the message, “NEW RUN LEVEL: shutdown”, your computer is running only the Solaris operating system, in MULTI-user mode.
...... 3-38 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
4 Enter: cd /usra/fep ......
5 Load the FEP application update tape that contains the patch to be removed in the tape drive. Then, enter: cpio -icBvu tapemgr
......
6 Enter: /bin/sh ./tapemgr
Note: Use the full path, “/bin/sh ./tapemgr”. Entering “tapemgr” alone could cause problems.
......
7 When you are prompted for “REWIND”, enter: /dev/rmt/0 ......
8 When you are prompted for “NON-REWINDING”, enter: /dev/rmt/0n ......
9 When you are prompted “Do you wish to install or remove packages?”, enter: remove ......
10 When you are prompted for the package to remove, enter: all ......
11 When you are prompted to remove it, enter: y
...... 190-406-737 Alcatel-Lucent — Internal 3-39 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
12 When you are prompted for the directory from which the fep’s root directory is to be removed, enter: /usra Result: The following message appears:
About to remove ALL files and directories associated with
13 When you are prompted to remove the package, enter: y Result: A list of files appears with the message:
fep Release:5 Version:0 Issue:1 has been removed.
The removepkg from tape has completed- You may remove the tape after the rewind is complete......
14 Execute the load_fep script. Enter: /usra/fep/bin/baseworx/scripts/load_fep ......
15 This script produces trace output as commands are executed. Check that all commands execute normally; note any exceptions. Contact FEP development about any exceptions.
......
16 Do an incremental or full software backup.
Reference: “Performing a full or incremental backup in single-user mode” (p. 3-45) starting with Step 2.
Note: It is recommended that you do the incremental or full backup now. If you are not doing it now, then you will need to restart the FEP. To do that, enter the following (unless the memorandum that came with the update tells you to do a reboot instead): startfep
...... E ND OF STEPS ......
...... 3-40 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Backup
Overview The following procedures comprise this process: • “Performing a full or incremental backup in single-user mode” (p. 3-45) • “Keeping or putting away the tape after backup” (p. 3-48) • “Performing an automatic full/incremental backup of filesystems” (p. 3-49) • “Dynamic data backup” (p. 3-51) • “Performing a manual backup of dynamic data” (p. 3-55)
What is backed up? Data that is backed up can be restored; and vice versa. Backups save almost all data on the system, including: • FEP • BaseWorX and Solaris software • Software updates • User and entity definitions • AISwitch Configuration
Backup types There are three types of backups, as explained in Table 3-4:
Table 3-4 Three types of backups (Sheet 1 of 2) Backup Types FAQs Full Backup Incremental Backup Dynamic Backup What is backed up? Everything. Anything changed since Files that may change daily last full backup (such as (such as user “.profiles”, software updates). and files holding passwords).
How often should I • Immediately after initial After you install a Daily. do this? installation software update to FEP, • Every month Solaris, BaseWorX, or • Any time you restore Datakit software. even one filesystem • Any time you restore a disk
...... 190-406-737 Alcatel-Lucent — Internal 3-41 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table 3-4 Three types of backups (Sheet 2 of 2) Backup Types FAQs Full Backup Incremental Backup Dynamic Backup What if I forget to do If you lose data, you may If you lose data, you may Dynamic data is lost (such this? have to reinstall everything need to reload all as yesterday’s changes to (Chapter 2, “Installing the software updates made passwords). FEP”). since the last full backup. How long does it take About 2 hours. About 1 hour. About 30 minutes. to do this? Does this take the Yes. Yes. No. FEP offline? Back up onto… Tape. Tape. Tape. To back up, use… Manually … “Performing a full or “Performing a full or “Performing a manual incremental backup in incremental backup in backup of dynamic data” single-user mode” (p. 3-45) single-user mode” (p. 3-55) (with (with fsbackup_fep). (p. 3-45) (with ddbkup_fep). fsbackup_fep). Automatically: “Performing an automatic full/incremental backup of filesystems” (p. 3-49)
Using un-write-protected tape You always back up onto tape. Make sure the tape is NOT write protected. That is, on the back of the tape, make sure the little red or white tab is pushed to the right, in the “REC” position, as illustrated in the following figure. Otherwise, you cannot back up onto the tape.
...... 3-42 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Figure 3-5 Back up onto un-write-protected tape
Logging in remotely You can log in remotely to use any of the backup procedures, but you or someone else will need to load a tape or tapes at the tape drive. However, if you’re performing a full or incremental backup, we recommend logging in at the FEP console and performing the backup in single-user mode. The user cannot log in to the system remotely as a single- user.
Full or incremental backup What is a full or incremental backup? • Full — A full backup backs up all files and directories in all filesystems. • Incremental — An incremental backup backs up only those files and directories that have changed since the last full backup. Sun recommends doing backups at single-user mode to ensure file sanity for proper recovery. We recommend you do this monthly. If you desire more frequent backups, you may run the fsbackup_fep script at multi-user mode (follow Step 8 in “Performing a full or incremental backup in single-user mode” (p. 3-45)). However, some files may not be properly backed up if they are in a “busy” state. You may even run the fsbackup_fep script automatically from cron.
Reference: “Performing an automatic full/incremental backup of filesystems” (p. 3-49)
...... 190-406-737 Alcatel-Lucent — Internal 3-43 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Which backup this procedure does depends on the option selected from the menu presented while running the fsbackup_fep script in Step 8. (This command was built from the Solaris ufsdump command, and you can refer to ufsdump in Solaris documents for details, if needed.)
...... 3-44 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Performing a full or incremental backup in single-user mode
Purpose Use this procedure to perform a full or incremental backup in single-user mode.
Instructions Follow these steps:
Note: The first time you use this procedure, you must use it for a full backup.
......
1 Obtain a tape appropriate for the kind of tape drive your FEP uses. Label the tape with: • “Full Backup” or “Incremental Backup” • Date • The name of the FEP machine (what you see if you enter uname -n). Don’t back up on a current backup tape (incremental or full). If a problem occurs during this new backup, you could lose the current backup as well as the new backup.
......
2 Log in as root. Enter: stopfep Result: The following warning message will appear on the screen of any terminal logged in at the FEP:
Warning: FEP Application shutting down in 60 seconds. Result: As processes are killed, messages will scroll down your screen, ending with the message:
NEW RUN LEVEL: Shutdown Result: Now your computer is running only the Solaris operating system, in MULTI- user mode.
......
3 Ensure no one will attempt to modify files while you are doing the backup. Enter: cd / halt Hint: Ignore any message saying “umount: warning: /raw not in mnttab” or “umount: /opt busy”.
...... 190-406-737 Alcatel-Lucent — Internal 3-45 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
Result: The prompt changes to “#”, and then, after about 10 lines of output, OK.
......
4 Boot the FEP to single (“-s”) user mode. Enter: boot -s ......
5 When the FEP comes back up again, enter the root password.
Result: You will now see the “#” cursor prompt.
Result: You are now in single-user mode. FEP application software is not running.
......
6 Check all filesystems. Enter: fsck -y Result: For each filesystem, fsck will give output similar to: ** /dev/rdsk/c0t3d0s0 ** Last Mounted on / ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 3255 files, 13378 used, 615412 free (460 frags, 76869 blocks, 0.1% fragmentation It will be obvious if fsck fails, with various messages among the lines above, and maybe even some lines omitted. If fsck fails, you will need to restore the bad filesystem. Use “Restoring /(root) and /usr filesystem” (p. 3-61). (If you are restoring a filesystem OTHER than “/” or “/usr”, use “Restoring filesystems other than /(root) and /usr” (p. 3-66).)
......
7 Mount all filesystems. Enter: mountall This will mount each filesystem, printing a line for each, telling you it is mounted.
......
8 Still logged in as root, enter: /usra/fep/bin/fsbackup_fep
...... 3-46 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
9 When the program prompts you to load the tape, do so. You will be prompted for the type of backup to be performed. Respond appropriately. ----- File System Backup ------You have the following options to choose from: 1) Full backup of all the file systems. 2) Incremental backup of all the file systems. 3) Exit (from this program) Enter your choice (1/2/3): Are you sure that the option you selected is correct? (Y/N): Hit
10 After the backup finishes, shut the system down and bring it back to multi-user mode. Enter: cd / reboot Hint: Ignore any message saying “…:kill: no such process” or “umount: warning: /raw not in mnttab”.
Result: As processes are started, messages will scroll down your screen, ending with the message:
NEW RUN LEVEL: Running
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-47 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Keeping or putting away the tape after backup
Purpose It is a good idea to put away obsolete tapes so you won’t be confused when you need to do restores.
Instructions Follow these steps:
......
1 Before your first full backup: • Keep: All installation tapes (including any third-party software), and all software update tapes (if any). • Put away: None.
......
2 After a full backup: • Keep: This current full backup tape. • Put away: All other tapes including: installation tapes (including any third-party software), the previous full backup tape (if any), the current incremental backup tape (if any), and all software updates already loaded (if any).
......
3 After an incremental backup: • Keep: This incremental backup tape and the current full backup tape. • Put away: All other tapes including: the previous incremental backup tape (if any), and all software updates already loaded (if any).
...... E ND OF STEPS ......
...... 3-48 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Performing an automatic full/incremental backup of filesystems
Purpose Use this procedure to have the Solaris “cron” program automatically back up the file systems.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Enter: crontab -e Result: You will find yourself editing the file that lists commands to be run automatically by the Solaris cron command. This file will initially resemble:
0 2 * * 0,4 /etc/cron.d/logchecker 5 4 * * 6 /usr/lib/newsyslog # # FEP specific scripts # 0 1 * * * /usra/fep/bin/cleanlogdir 2 * * * * /usra/fep/bin/cleandatadir 0 0 * * 1 /usra/fep/bin/cleandklogs 0 0 * * 2 /usra/fep/bin/cleansyslogs 0 * * * * /usra/fep/bin/cleanrel_int 4 * * * * /usra/fep/bin/chk_fs 10 >/dev/console 2>&1 # Uncomment the “ddbkup_fep” line for automatic backup of dynamic data #5 4 * * 1-5 /usra/fep/bin/ddbkup_fep # Uncomment the “fsbackup_fep” lines for automatic backup of file systems #0 20 * * 5 /usra/fep/bin/fsbackup_fep full /dev/rmt/0 #0 20 * * 1-4 /usra/fep/bin/fsbackup_fep incr /dev/rmt/0 ......
3 Look at the line with “fsbackup_fep full /dev/rmt/0”. This line tells cron that at 20:00 hours (“0 20”), on Friday of every week (“* * 5”), cron will execute the fsbackup_fep command, which makes a full backup of all the file systems.
...... 190-406-737 Alcatel-Lucent — Internal 3-49 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
4 Look at the line with “fsbackup_fep incr /dev/rmt/0”. This line tells cron that at 20:00 hours (“0 20”), Monday through Thursday of every week (“* * 1-4”), cron will execute the fsbackup_fep command, which makes an incremental backup of all the file systems.
......
5 To put these lines into effect, remove the “#” at the beginning of the line. If you want to change this schedule, you can further edit these lines (refer to the Solaris manual page for cron). When you are done, write and quit the file.
......
6 Remember to keep a tape in the tape drive.
...... E ND OF STEPS ......
Notes • You could leave the same tape in at all times, but we suggest you keep 3 sets of backup tapes. – For full backup, maintain a rotation of 3 separate backup tapes. – For incremental backup, maintain one full set of incremental tapes per each full backup tape. – For example, if you make a weekly full backup and four incremental backups in a week, you will need 15 tapes to keep 3 sets of backups on hand. • Tapes wear out, so plan to replace a tape after it has been used for about 30 backups. • If you use the tape drive for something else, such as loading a software update, remember to take out the other tape before the cron scheduled backup time. Otherwise, that tape may be overwritten with the backup!
...... 3-50 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Dynamic data backup
Overview Dynamic data is data that may change daily, such as user “.profile” files group IDs, and so on. The next procedure uses the FEP command ddbkup_fep to back up this data.
Choosing what is backed up If you want one file (or all files in a directory) to be backed up by ddbkup_fep, enter that file or directory in the “/usra/fep/bin/ddfiles” file. List each file or directory on a separate line. The default list of files is in the following table. You should NOT delete default lines from this file. We do NOT recommend you use dynamic data backup in place of full or incremental backups. Backing up too much data dynamically could hurt performance, and this guide does not give a procedure for doing full or incremental restores from the dynamic data backup tape alone.
Table 3-5 Default list of files and directories backed up by “ddbkup_fep” (Sheet 1 of 2) …is on this This file or directory… filesystem, and disk… …and pertains to this. /install_fep_scripts (directory) / FEP installation, backup, and restore scripts /etc/group (file) / login groups /etc/motd (file) / the message of the day /etc/opasswd (file) / old user login information /etc/oshadow (file) / old encrypted passwords /etc/passwd (file) / current user login information /etc/profile (file) / the universal “profile” /etc/shadow (file) / current encrypted passwords /etc/system (file) / Solaris specifications /etc/resolv.conf (file) / Solaris networking files /etc/inet/hosts (file) / Solaris networking files /etc/uucp (directory) / uucp configuration files /usra/fep/bin/ddfiles (file) /usra this file, itself /usra/fep/bin/ddfilesX (file) /usra files excluded from this backup
...... 190-406-737 Alcatel-Lucent — Internal 3-51 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table 3-5 Default list of files and directories backed up by “ddbkup_fep” (Sheet 2 of 2) …is on this This file or directory… filesystem, and disk… …and pertains to this. /usra/fep/bin/baseworx/scripts/active.ee (file) /usra store AISwitch 180 configuration /usra/fep/bin/edcs (directory) /usra EDCS configuration files /usra/fep/etc (directory) /usra BDR Backup Disaster Recovery file /usra/grp (directory) /usra all user home directories /usra/grp/bworx/bwx5.1/config_data/cm/em/ (file) /usra FEP processes started by FEP boot deconfig /usra/grp/bworx/bwx5.1/config_data/fm/log/ (file) /usra potential destinations for audit, Config BDR, and error messages /usra/grp/bworx/bwx5.1/config_data/fm/log/l (file) /usra error messages to be throttled ogThrottle /usra/tdms/cf_parms (file) /usra FEP configuration file /usra/tdms/ipndc/active.ee (file) /usra AISwitch 180 configuration file /usra/tdms/ndc (directory) /usra NDC configuration files /usra/tdms/nmt/rmNMTchild (file) /usra NMT housekeeping script /usra/tdms/nmt/ntmsinfo (file) /usra FEP-NTM interface file /usra/tdms/trans5min/rpt_times.def (file) /usra 5-minute translator time window /usra/tdms/nmt/tmout.def (file) /usra control and audit time-outs. /usra/tdms/nmt/tcp_port.def (file) /usra TCP/IP port information /usra/tusr/na/entity (directory) /usra all switch databases /usra/vpdb (directory) /usra vport db for all switches /var/opt/dk (directory) /var Datakit VCS files Below you can list any files or directories you add to “ddfiles”.
...... 3-52 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Performing automatic backup of dynamic data
Purpose Use this procedure to have the Solaris “cron” program automatically back up dynamic data.
Instructions Follow these steps:
......
1 Log in as root.
......
2 Enter: crontab -e Result: You will find yourself editing the file that lists commands to be run automatically by the Solaris cron command. This file will initially resemble: 0 2 * * 0,4 /etc/cron.d/logchecker 5 4 * * 6 /usr/lib/newsyslog # # FEP specific scripts # 0 1 * * * /usra/fep/bin/cleanlogdir 2 * * * * /usra/fep/bin/cleandatadir 0 0 * * 1 /usra/fep/bin/cleandklogs 0 0 * * 2 /usra/fep/bin/cleansyslogs 0 * * * * /usra/fep/bin/cleanrel_int 4 * * * * /usra/fep/bin/chk_fs 10 >/dev/console 2>&1 # Uncomment the “ddbkup_fep” line for automatic backup of dynamic data #5 4 * * 1-5 /usra/fep/bin/ddbkup_fep # Uncomment the “fsbackup_fep” lines for automatic backup of file systems #0 20 * * 5 /usra/fep/bin/fsbackup_fep full /dev/rmt/0 #0 20 * * 1-4 /usra/fep/bin/fsbackup_fep incr /dev/rmt/0 ......
3 Look at the line with “ddbkup_fep”. This line tells cron that at 4:05 a.m. (“5 4”), Monday through Friday of every week (“* * 1-5”), cron will execute the ddbkup_fep command, which backs up dynamic data.
...... 190-406-737 Alcatel-Lucent — Internal 3-53 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
4 To put this line into effect, remove the “#” at the beginning of the line. If you want to change this schedule, you can further edit this line (refer to the Solaris manual page for cron). When you are done, write and quit the file.
......
5 Remember to keep a tape in the tape drive.
...... E ND OF STEPS ......
Notes • You could leave the same tape in at all times, but what if the system fails DURING a backup? Then you have no good backup tape. So, we suggest you rotate tapes, as follows: – When you are first setting up your FEP, you will have a lot of data changes, so rotate tapes daily, with tapes labelled “Monday” through “Friday”. – Once your FEP is stabilized (all your switches and users have been added), you can rotate tapes weekly. • Tapes wear out, so plan to replace a tape after it has been used for about 30 backups. • If you use the tape drive for something else, such as loading a software update, remember to take out the other tape before the cron scheduled backup time. Otherwise, that tape may be overwritten with the backup!
...... 3-54 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Performing a manual backup of dynamic data
Purpose Use this procedure to manually backup dynamic data.
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter su - to become superuser.
Note: Typically, the FEP machine would now be in normal running mode, which is multi-user mode with the FEP application running. However, this procedure can be used as long as the FEP machine is in multi-user mode, even if the FEP application is not running.
......
3 Load a tape in the tape drive.
......
4 Enter: ddbkup_fep
......
5 The last FULL Backup date can be observed in the “/etc/dumpdates” file.
......
6 The ddbackup_fep process log can be observed in the “/etc/dumpdates2” file.
......
7 Remove the tape and label with: a. “Dynamic Data” b. Date c. The name of the FEP machine (what you see if you enter uname -n).
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-55 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Restoring
Overview The following procedures comprise this process: • “Forcing a crash dump and rebooting the system” (p. 3-58) • “Restoring the FEP after a disk crash” (p. 3-59) • “Restoring /(root) and /usr filesystem” (p. 3-61) • “Restoring filesystems other than /(root) and /usr” (p. 3-66) • “Restoring a directory or file (not dynamic data)” (p. 3-68) • “Restoring dynamic data (all or some)” (p. 3-72)
Restore categories Restores are categorized as follows: • Disk restore • Filesystem restore • File or directory restore
Logging in remotely You can log in remotely to restore dynamic data or a file or directory, but you or someone else will need to load a tape or tapes at the tape drive. You may not log in remotely when restoring a filesystem.
When to use which restore procedure Each of the restore types may use full, incremental, or dynamic data backup tapes — and in various combinations. Don’t worry about how or why. The restore procedures will walk you through needed decisions. All you have to figure out is which restore procedure to use. This is explained in Table 3-6.
Table 3-6 Which restore procedure to use If you lost this data… …use this procedure to restore it. The internal disk “Restoring the FEP after a disk crash” (On a Sun Ultra I or Ultra II the only disk is named as “c0t0d0”) (p. 3-59).
...... 3-56 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Table 3-6 Which restore procedure to use If you lost this data… …use this procedure to restore it. A filesystem “Restoring /(root) and /usr filesystem” [each filesystem consists of all files and directories under each of (p. 3-61) and/or “Restoring filesystems the following directories: “/” (minus the other filesystems listed other than /(root) and /usr” (p. 3-66). here), “/opt”, “/usr” (minus “openwin”), “/usr/openwin”, “/usra”, and “/var”]. A file or directory that is NOT backed up as dynamic data “Restoring a directory or file (not (that is, a file or directory NOT in Table 3-5, “Default list of files dynamic data)” (p. 3-68). and directories backed up by “ddbkup_fep”” (p. 3-51)). A file or directory that is backed up as dynamic data “Restoring dynamic data (all or some)” (that is, a file or directory in Table 3-5, “Default list of files and (p. 3-72). directories backed up by “ddbkup_fep”” (p. 3-51))
...... 190-406-737 Alcatel-Lucent — Internal 3-57 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Forcing a crash dump and rebooting the system
Purpose Saving crash dumps of the operating system is sometimes necessary for troubleshooting purposes.
Instructions Follow these steps:
......
1 Stop the system by entering:
2 The monitor displays the OK PROM prompt.
......
3 Synchronize the disk and write the crash dump by entering at the prompt: sync
Note: The system is now forcing a Crash Dump and Rebooting the system.
......
4 After the crash dump is written to disk, the system will continue to reboot.
...... E ND OF STEPS ......
...... 3-58 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Restoring the FEP after a disk crash
Purpose If a disk crashes: • A hardware person would correct the problem. • The hardware person will tell you that you definitely need to repartition, and maybe format, the disk. If so, use “Partitioning and formatting a disk” (p. 3-75). • Use one of the procedures below as appropriate to restore lost data.
Before you begin You will need the following: • Solaris 2.5.1 operating system CD • Latest FULL backup tape • The latest INCREMENTAL backup tape, if it is newer than the latest full backup tape • The latest dynamic data backup tape, if it is newer than the latest full or incremental backup tape
Note: If you have any patches that are not on the incremental (or full) backup tape, you will need to reinstall them after you finish this procedure.
Disk layout configuration Table 3-7 identifies the directories and their locations for configuring the disk. Table 3-7 Disk Layout Configuration Sun Ultra I or Ultra II Disk c0t0d0 3. /usr/openwin on c0t0d0s3 4. /opt on c0t0d0s5 5. /usra on c0t0d0s7 6. /var on c0t0d0s4 7. /usr on c0t0d0s6 8. / on c0t0d0s0
Instructions Follow these steps:
...... 190-406-737 Alcatel-Lucent — Internal 3-59 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Note: It is not recommended that you restore either “/”(root) or “/usr” filesystem alone. Both filesystems should only be restored in case of a disk crash.
......
1 To restore lost data after a disk crash, follow “Restoring /(root) and /usr filesystem” (p. 3-61).
......
2 Then follow “Restoring filesystems other than /(root) and /usr” (p. 3-66).
......
3 If you have a dynamic data backup tape made more recent than the full or incremental backup tape used for restore, follow the “Restoring dynamic data (all or some)” (p. 3-72).
......
4 Then make a full backup tape.
Reference: “Full or incremental backup” (p. 3-43)
...... E ND OF STEPS ......
...... 3-60 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Restoring /(root) and /usr filesystem
Instructions Follow these steps:
......
1 Assuming that the cdrom drive is set up and ready, use “Booting from Solaris CD” (p. 3-82). That procedure will return you to the following step.
Result: An Install Solaris Software - Initial Menu will appear.
......
2 Click Exit
Result: An informational box on exit will appear.
......
3 Click Exit
......
4 Click on the system console window.
......
5 Create a temporary mount point (/tmp/fep_mnt) under /tmp directory by entering: mkdir /tmp/fep_mnt ......
6 Determine directory to be restored: • To restore the / (root) filesystem, complete Step 7 through Step 12. • To restore the /usr filesystem, complete Step 14 through Step 19.
......
7 Perform a filesystem check on /(root). Enter: fsck -y /dev/dsk/c0t0d0s0 • If fsck succeeds, go to the next step. • If fsck fails, build a new filesystem by entering: newfs -v /dev/dsk/c0t0d0s0
...... 190-406-737 Alcatel-Lucent — Internal 3-61 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
8 Enter y at the system prompt: newfs: construct a new file system /dev/dsk/c0t0d0s0: (y/n)? ......
9 Mount the root filesystem on to the temporary mount point. Enter: mount /dev/dsk/c0t0d0s0 /tmp/fep_mnt cd /tmp/fep_mnt ......
10 Insert the tape labeled “full backup” into the tape drive. Then enter: mt -f /dev/rmt/0 rewind ufsrestore rvfs /dev/rmt/0n 6 Result: Files will be restored from the tape. This may take 10–15 minutes.
......
11 Remove the “full backup” tape from the tape drive and insert the tape labeled “incremental backup” into the tape drive. Then enter: mt -f /dev/rmt/0 rewind ufsrestore rvfs /dev/rmt/0n 6 Result: Files will be restored from the tape. This may take 10–15 minutes.
......
12 Unmount the / (root) filesystem. Enter: cd / umount /dev/dsk/c0t0d0s0 ......
13 Remove the tape from the tape drive. If you need to restore /usr filesystem continue with the next step, otherwise, skip to Step 22.
......
14 Perform a filesystem check on /usr. Enter: fsck -y /dev/dsk/c0t0d0s6 • If fsck succeeds, go to the next step. • If fsck fails, build a new filesystem by entering: newfs -v /dev/dsk/c0t0d0s6
...... 3-62 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
15 Enter y at the system prompt: newfs: construct a new file system /dev/dsk/c0t0d0s0: (y/n)? ......
16 Mount the /usr filesystem on to the temporary mount point. Enter: mount /dev/dsk/c0t0d0s6 /tmp/fep_mnt cd /tmp/fep_mnt ......
17 Insert the tape labeled “full backup” into the tape drive. Then enter: mt -f /dev/rmt/0 rewind ufsrestore rvfs /dev/rmt/0n 5 Result: Files will be restored from the tape. This may take 10–15 minutes.
......
18 Remove the “full backup” tape from the tape drive and insert the tape labeled “incremental backup” into the tape drive. Then enter: mt -f /dev/rmt/0 rewind ufsrestore rvfs /dev/rmt/0n 5 Result: Files will be restored from the tape. This may take 10–15 minutes.
......
19 Install boot block. Enter: installboot /usr/platform/ůname -ě/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0 ......
20 Unmount the /usr filesystem. Enter: cd / umount /dev/dsk/c0t0d0s6 ......
21 Remove the tape from the tape drive.
......
22 Halt and then boot to single-user mode. Enter: halt
...... 190-406-737 Alcatel-Lucent — Internal 3-63 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
23 At the “ok” prompt, enter: boot -s ......
24 When the FEP comes back up, enter the root password.
Result: You will now see the # cursor prompt. Result: You are now in single-user mode. FEP application software is not running.
......
25 Check and correct all filesystems. Enter: fsck -y Result: For each filesystem, fsck will give output resembling: ** /dev/rdsk/
26 If you see many output messages indicating that some kind of corrective action took place, rerun fsck -y to get a clean file system check.
......
27 Remove the CDROM. Enter: cd / eject cdrom ......
28 Remove the CDROM and store it. Remember to close the CDROM drive.
......
29 Refer back to the section that sent you to this procedure.
...... 3-64 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
30 Perform a full backup, starting with Step 7 of “Performing a full or incremental backup in single-user mode” (p. 3-45).
Result: At the end of that procedure, you return to multi-user mode, which means your FEP application software is running.
Note: You must do a full backup because a full restore repositions files, so any future incremental backup would not fit with the old full backup.
......
31 (You could do a full backup later. If you do, you will need to enter reboot now. Then when you do the full backup, start with Step 1.)
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-65 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Restoring filesystems other than /(root) and /usr
Instructions Follow these steps:
......
1 Ensure that the system has the /(root) and /usr file systems mounted and operational. If not, follow “Restoring /(root) and /usr filesystem” (p. 3-61) to restore them.
......
2 If you are in single-user mode continue with the next step, otherwise, halt and then boot to single-user mode by entering: halt ......
3 At the “ok” prompt, enter: boot -s ......
4 When the FEP comes back up again, enter the root password.
Result: You will now see the # cursor prompt. You are now in single-user mode. FEP application software is not running.
......
5 Change to the FEP install scripts directory. Enter: cd /install_fep_scripts ......
6 Run the filesystem restore script. Enter: ./fsrestore_fep ......
7 Select the filesystem(s) that you want to restore from the menu presented by the fsrestore script.
......
8 Halt and then boot to single-user mode. Enter: halt
...... 3-66 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
9 At the “ok” prompt, enter: boot -s Result: When the FEP comes back up again, enter the root password. You will now see the # cursor prompt. You are now in single-user mode. FEP application software is not running.
......
10 Perform a full backup, starting with Step 5 of “Performing a full or incremental backup in single-user mode” (p. 3-45).
Result: At the end of that procedure, you return to multi-user mode, which means your FEP application software is running.
Note: You must do a full backup because a full restore repositions files, so any future incremental backup would not fit with the old full backup.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-67 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Restoring a directory or file (not dynamic data)
Purpose Use this procedure if you lose a directory or file that is NOT on the dynamic data backup tape (to see if it is there, use Step 1).
Before you begin You will need the following: • Latest FULL backup tape • The latest INCREMENTAL backup tape, IF it is newer than the latest full backup tape.
Instructions Follow these steps:
......
1 Refer to Table 3-5, “Default list of files and directories backed up by “ddbkup_fep”” (p. 3-51). Is the file or directory you want to restore listed there? If so, don’t use this procedure; use “Restoring dynamic data (all or some)” (p. 3-72).
......
2 Log in as root.
Note: If you use this procedure at a remote terminal, you would need to call someone at the FEP console to load the tape in the next step.
......
3 Insert the tape labelled “FULL BACKUP” into the tape drive.
......
4 Are you restoring the “/usra/fep” or “/usra/fep/bin” directory? Or, are you restoring one of the following files? • /usra/fep/bin/ctlAud • /usra/fep/bin/dc_mgr • /usra/fep/bin/dcol_std • /usra/fep/bin/edcsdd • /usra/fep/bin/ipndc • /usra/fep/bin/ndc • /usra/fep/bin/nmt
...... 3-68 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... • /usra/fep/bin/transdisc • /usra/fep/bin/trans5min If the answer to both questions is “no”, go to the next step. If the answer to either question is “yes”, enter: stopfep Result: The following warning message will appear on the screen of any terminal logged in at the FEP:
Warning: FEP Application shutting down in 60 seconds. Result: As processes are killed, messages will scroll down your screen, ending with the message:
NEW RUN LEVEL: Shutdown Result: Now your computer is running only the Solaris operating system, in MULTI- user mode.
......
5 Restore the file or directory to a temporary area. Enter: cd /tmp mt -f /dev/rmt/0 rewind ufsrestore xfs /dev/rmt/0n
Example: To restore “/usra/fep/bin/nmt”, enter: ufsrestore xfs /dev/rmt/0n 3 fep/bin/nmt Where: • 0 rewind is zero-rewind • 0n is zero-n •
Example: If the full path to the file were “/usra/fep/bin/nmt”, the
If the file or directory you are restoring is in the … … filesystem 1 /usr/openwin 2 /opt 3/usra
...... 190-406-737 Alcatel-Lucent — Internal 3-69 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
4/var 5/usr 6 /(root)
Result: This may take about 5 minutes. As long as the light on the tape drive is flashing, everything is okay.
......
6 When you receive a prompt saying “Specify next volume #”, enter: 1 ......
7 When you receive a prompt saying “set owner/mode for ‘.’? [y,n]”, enter: n ......
8 If you see a prompt, “Directories already exist, set modes anyway? [y,n]”, then enter: n
......
9 When your prompt returns, verify that the file or directory is restored. For example, use ls -l.
......
10 If you have restored a file, mv it from “/tmp” to the appropriate location. For restored file “fileA”, enter: mv /tmp/fep/bin/fileA /usra/fep/bin/fileA
......
11 If you have restored a directory, you cannot use mv (not across filesystems), so use cp.
Example: For restored directory “fep”, enter: cd /tmp cp -R ./fep /usra/ Then remove the copied-from directory under “/tmp”.
......
12 Go back to Step 4 and loop through this procedure again for each file or directory you are restoring.
...... 3-70 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
13 IF you have an INCREMENTAL backup tape that is newer than the FULL backup tape, go back to Step 3 and repeat this procedure, using the incremental backup tape.
Note: If you restore from the incremental backup tape, don’t be alarmed if a file or directory is not on that tape. If the file or directory has not changed since the last full backup, it will not be found on the incremental backup.
......
14 If you used Step 4 (which uses stopfep). Enter: startfep
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-71 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Restoring dynamic data (all or some)
Purpose Dynamic data is data that may change daily, such as individual “.profile” files, passwords, group IDs, and so on (see the default list of backed up files, Table 3-5, “Default list of files and directories backed up by “ddbkup_fep”” (p. 3-51)). The next procedure uses the ddrstr_fep command to restore this data from the last Dynamic Data backup tape you made using either of the last two procedures.
Why am I here? You may have been referred to this procedure by either: “Restoring filesystems other than /(root) and /usr” (p. 3-66) or “Restoring a directory or file (not dynamic data)” (p. 3-68).
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter su - to become superuser.
Note: At this point you should be in multi-user mode, with or without the FEP application running. But, if you were referred here from one of the restore procedures, it is okay to be in single-user mode, since those procedures had you mount all file systems.
......
3 Insert the most recent tape of backed up dynamic data.
......
4 Rewind the tape. Enter: mt -f /dev/rmt/0 rewind Where the last character is zero
......
5 Determine files to be restored: • If you want to restore all files in Table 3-5, skip to the next step. • If you want to restore only some files, then — for each file you want to restore.
...... 3-72 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... a. Enter: tar xvpf /dev/rmt/0
Example: To restore “/etc/profile”, enter: tar xvpf /dev/rmt/0 /etc/profile Continue with Step 6.
......
6 To restore all files on the Dynamic Data Backup, enter: ddrstr_fep Result: When you see “successful completion of dynamic data restore”, all files on the tape have been restored.
......
7 If you have restored one of the following files or directories: • /etc/profile • /usra/tdms/cf_parms • /usra/tdms/ndc • /usra/tdms/nmt/ntmsinfo • /usra/tdms/nmt/tmout.def • /usra/tdms/trans5min/rpt_times.def • /usra/tusr/na/entity then, shut down and restart the FEP application. a. Enter: stopfep b. Enter: startfep
......
8 ONLY if you have restored “/etc/system”, log in as root on the system console and enter: stopfep ......
9 Reboot the FEP. Enter: cd / reboot
Note: Ignore any message saying “umount: warning: /raw not in mnttab” or “umount: /opt busy”.
...... 190-406-737 Alcatel-Lucent — Internal 3-73 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: The FEP will automatically bring up the application.
...... E ND OF STEPS ......
...... 3-74 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Partitioning and formatting a disk
Purpose In the event of a disk failure, a hardware person may tell you that you need to repartition, and maybe format, the disk. If he or she does, use the following procedure.
Terminology In the following procedure, you may see the following: • Select means tab or arrow to the selection and press Return to select. • Type in means type in the selection and press Return to select.
Instructions Follow these steps:
......
1 Boot the FEP off Solaris CD. Use “Booting from Solaris CD” (p. 3-82). That procedure will return you to the following step.
Result: An Install Solaris Software - Initial Menu will appear.
......
2 Click Exit
Result: An informational box on exit will appear.
......
3 Click Exit
......
4 Click on the system console window. Drag a corner of the window to enlarge it.
Result: Your cursor is now a “#”.
......
5 Enter format. Result: The following message(s) appear:
Searching for disks...done
...... 190-406-737 Alcatel-Lucent — Internal 3-75 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... For Ultra I: AVAILABLE DISK SELECTIONS: 0. c0t0d0
For Ultra II: AVAILABLE DISK SELECTIONS: 0. c0t0d0
6 For disk c0t0d0, type in 0. Result: The following message(s) appear:
selecting c0t0d0 [disk formatted]
FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector able - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8 character volume name quit format>
Note: In the next step, normally, you would NOT need to format. New disks are already formatted. You might need to format the disk if your hardware person had mapped around a bad place on a disk and you plan to continue using that disk.
......
7 Format and/or partition the disk:
...... 3-76 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
a. If you do not need to format the disk, type in partition. (This is the normal case.) b. If you do need to format the disk, type in format. Result: Formatting, plus its verification, takes about 4 hours.
......
8 After formatting, type in partition.
Result: The following message(s) appear:
PARTITION MENU: 0 - change“0” partition 1 - change“1” partition 2 - change“2” partition 3 - change“3” partition 4 - change“4” partition 5 - change“5” partition 6 - change“6” partition 7 - change“7” partition select - select a predefined table modify - modify a predefined partition table name - name the current table print - display the current table label - write partition map and label to the disk quit partition> ......
9 Type in modify.
Result: The following message(s) appear:
Select partitioning base: 0 - Current partition table (original) 1 - All Free Hog Choose base (enter number) [0]? ......
10 Type in 1.
Result: The following message(s) appear:
...... 190-406-737 Alcatel-Lucent — Internal 3-77 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... For Ultra I: Part Tag Flag Cylinders Size Blocks 0 root wm 0 0 (0/0/0) 1 swap wu 0 0 (0/0/0) 2 backup wu 0-2732 1.98GB (2733/0/0) 3 unassigned wm 0 0 (0/0/0) 4 unassigned wm 0 0 (0/0/0) 5 unassigned wm 0 0 (0/0/0) 6 usr wm 0 0 (0/0/0) 7 unassigned wm 0 0 (0/0/0)
For Ultra II: Part Tag Flag Cylinders Size Blocks 0 root wm 0 0 0/0/0 0 1 swap wu 0 0 0/0/0 0 2 backup wm 0-4923 8.43GB 4924/0/0 17682084 3 unassigned wm 0 0 0/0/0 0 4 unassigned wm 0 0 0/0/0 0 5 unassigned wm 0 0 0/0/0 0 6 usr wm 0 0 0/0/0 0 7 unassigned wm 0 0 0/0/0 0 ......
11 Type in yes.
Result: The following message(s) appear:
Do you wish to continue creating a new partition table based on above table[yes]? Free Hog partition [6]? ......
12 Type in 7. Result: The following message(s) appear:
Enter size of partition “0” [0b, 0c, 0.00mb]: ......
13 Respond with: • For Ultra I, type in 59m • For Ultra II, type in 601m
...... 3-78 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: The following message(s) appear:
Enter size of partition “1” [0b, 0c, 0.00mb]: ......
14 Respond with: • For Ultra I, type in 384m • For Ultra II, type in 1001m
Result: The following message(s) appear:
Enter size of partition “3” [0b, 0c, 0.00mb]: ......
15 Respond with: • For Ultra I, type in 146m • For Ultra II, type in 1001m Result: The following message(s) appear:
Enter size of partition “4” [0b, 0c, 0.00mb]: ......
16 Respond with: • For Ultra I, type in 363m • For Ultra II, type in 1500m Result: The following message(s) appear:
Enter size of partition “5” [0b, 0c, 0.00mb]: ......
17 Respond with: • For Ultra I, type in 163m • For Ultra II, type in 1001m
Result: The following message(s) appear:
Enter size of partition “6” [0b, 0c, 0.00mb]: ......
18 Respond with: • For Ultra I, type in 110m • For Ultra II, type in 1500m
...... 190-406-737 Alcatel-Lucent — Internal 3-79 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: The following message(s) appear:
For Ultra I: Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 79 59.38MB (80/0/0) 121600 1 swap wu 80-597 384.45MB (518/0/0) 787360 2 backup wm 0-2732 1.98GB (2733/0/0) 4154160 3 unassigned wm 598-795 146.95MB (198/0/0) 300960 4 unassigned wm 796-1285 363.67MB (490/0/0) 744800 5 unassigned wm 1286-1505 163.28MB (220/0/0) 334400 6 usr wm 1506-1654 110.59MB (149/0/0) 226480 7 unassigned wm 1655-2732 800.08MB (1078/0/0) 1638560
For Ultra II: Part Tag Flag Cylinders Size Blocks 0 root wm 0-342 601.42MB (343/0/0) 1231713 1 swap wu 343-913 1001.20MB (571/0/0) 2050461 2 backup wm 0-4924 8.43GB (4924/0/0) 17682084 3 unassigned wm 914-1484 1001.20MB (571/0/0) 2050461 4 unassigned wm 1485-2340 1.47GB (856/0/0) 3073896 5 unassigned wm 2341-2911 1001.20MB (571/0/0) 2050461 6 usr wm 2912-3767 1.47GB (856/0/0) 3073896 7 unassigned wm 3768-4923 1.98GB (1156/0/0) 4151196
Okay to make this the current partition table [yes]?
Note: The decimal values under “Size” may vary.
......
19 Type in yes.
Result: The following message(s) appear:
Enter table name (remember quotes): ......
20 Type in (in quotation marks): “temp_table”.
Result: The following message(s) appear:
Ready to label disk, continue? ......
21 Type in yes.
Result: The following prompt appears:
partition >
...... 3-80 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
22 Type in quit.
Result: The following message(s) appear:
FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8 character volume name quit format> ......
23 Type in quit.
Result: You will see the # prompt.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 3-81 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Booting from Solaris CD
Purpose Use this procedure to boot from the Solaris CD.
Why am I here? You were probably referred here from one of the following procedures: • “Restoring /(root) and /usr filesystem” (p. 3-61) • “Partitioning and formatting a disk” (p. 3-75) • “Installing Solaris 2.5.1 on a Sun Ultra system” (p. 2-12)
Terminology The term Solaris 2.5.1 CD refers to the CD with the label “2.5.1 Hardware: 11/97 Solaris”.
Instructions Follow these steps:
......
1 Insert the Solaris 2.5.1 CD into the cdrom drive.
......
2 Press break or
Note: The screen may become blank momentarily.
Result: The following prompt appears:
Solaris Installation Program Menu ......
3 Click Continue to start the installation. Result: The following prompt appears:
Identify This System ......
4 Click Continue.
...... 3-82 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: The following prompt appears:
Host name ......
5 Click on the hostname box to input hostname. Enter hostname in the text field and click continue.
Result: The following prompt appears:
Network Connectivity ......
6 Click No (even if your FEP is networked). Network Configuration will be completed after the FEP is installed.
......
7 Click Continue. Result: The following prompt appears:
Confirm Information ......
8 If the information is correct, click Continue. Otherwise, click Change to reenter the information.
Result: The following prompt appears:
Time Zone ......
9 Click Set. Result: The following prompt appears:
Geographic Region Menu ......
10 Select the Region and Time Zone as applicable (For example, United States and Eastern).
......
11 Click Continue. Result: The following prompt appears:
Date and Time Menu
...... 190-406-737 Alcatel-Lucent — Internal 3-83 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
12 Set the date and time as appropriate. Click Continue.
Result: The following prompt appears:
Confirm Information......
13 If correct, click Continue; otherwise, click Change. Result: The system will show that system identification is completed in the Solaris install console window, and continues building device files and filesystems.
......
14 Go back to procedure that referred you here.
...... E ND OF STEPS ......
...... 3-84 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Backup Disaster and Recovery (BDR)
Feature restrictions BDR is optional. It is available only if Feature 131, “FEP Backup and Disaster Recovery” has been purchased.
Overview The BDR (Backup and Disaster Recovery) Feature is predicated upon there being a “backup” NTM FEP in a one-to-one pairing arrangement with the “primary” NTM FEP. The primary FEP commits files to the backup FEP: • Every time there is a change in an entity or an NTM link AND • Once a day at 12:02 a.m. With the primary and backup FEP files synchronized, the backup FEP can take over processing if the primary FEP fails. The following procedures comprise this process: • “Configuring BDR” (p. 3-87) • “Verifying BDR” (p. 3-91) • “BDR take over/switch back system administration tasks” (p. 3-95)
Error messages The BDR-specific status and error messages can be examined using the “logCat -t 50 -l bdr” command. This command views the last 50 messages. Any reported problems should be corrected as quickly as possible, to ensure that the machines remain synchronized with each other.
BDR administrative commands Use the following table as a reference while configuring or verifying BDR on the primary and backup FEPs.
...... 190-406-737 Alcatel-Lucent — Internal 3-85 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
Table 3-8 BDR task/enter/response To perform the following task… Log in as user and enter… The system responds as follows… Check status of BDR on the host /usra/fep/etc/bdr_stat Displays the: • status of the FEP application, • status of the BDR feature, • status of BDR • name of the remote FEP. Activate BDR /usra/fep/etc/bdr_act Changes the state for the entire BDR to active on an NTM FEP. BDR in the active state enables the application software on the primary FEP to commit files to the backup FEP. Deactivate BDR /usra/fep/etc/bdr_deact Changes the state for the entire BDR to deactive on an NTM FEP. BDR in deactive state disables the application software on the primary FEP from committing files to the backup FEP. Sync files from the primary FEP /usra/fep/etc/bdr_commit Forces a remote copy of the files from the to the backup FEP. primary FEP to the backup FEP. Normally, this will happen automatically. This command should only be run under the direction of Lucent Customer Support.
References “bdr_act” (p. A-7) “bdr_commit” (p. A-8) “bdr_deact” (p. A-10) “bdr_stat” (p. A-11)
...... 3-86 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Configuring BDR
Purpose Use the following procedure for the initial configuration of BDR.
Instructions Follow these steps:
......
1 Log into the primary and backup FEPs as fep.
......
2 On the primary and backup FEPs, use the /usra/fep/etc/bdr_stat command to verify that the BDR feature is available on the FEP. If the feature is not available and you have purchased it, contact FEP Customer Support to install the feature.
Note: BDR cannot be active on the backup FEP.
Reference: “BDR task/enter/response” (p. 3-86) “bdr_stat” (p. A-11) “bdr_deact” (p. A-10)
......
3 On the primary FEP, use the centity -B
Reference: “BDR task/enter/response” (p. 3-86) “centity” (p. A-13)
......
4 To change or delete the backup FEP, use the chentity or delentity commands.
......
5 On the backup FEP, use the centity -B
......
6 On the primary FEP, add the backup FEP system name to the .rhosts file in the FEP-type user’s home directory and root’s home directory. a. Enter: vi .rhosts
...... 190-406-737 Alcatel-Lucent — Internal 3-87 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Example:
Example:
......
7 On the primary FEP, add the hostname of the backup FEP to the /etc/inet/hosts file.
Example: 127.0.0.1 loghost 135.7.29.104 cbfepuc
8 Exit from login root, becoming fep again. Enter:
9 Verify you are logged in as fep. Enter: id ......
10 On the backup FEP, add the primary FEP system name to the .rhosts file in the FEP-type user’s home directory and root’s home directory. a. Enter: vi .rhosts
Example:
Example:
......
11 On the backup FEP, add the hostname of the primary FEP to the /etc/inet/hosts file.
...... 3-88 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Example: 127.0.0.1 loghost 135.7.29.103 cbfepud
12 Exit from login root, becoming fep again. Enter:
13 Verify you are logged in as fep. Enter: id ......
14 On the primary FEP, activate BDR. Enter: /usra/fep/etc/bdr_act Result: You will be prompted for confirmation.
Reference: “BDR task/enter/response” (p. 3-86) “bdr_act” (p. A-7) If a message is displayed indicating the FEP application is running on the backup FEP, then go to the next step. Otherwise, go to Step 16.
......
15 On the backup FEP, enter stopfep. Reference: “BDR task/enter/response” (p. 3-86) “stopfep” (p. A-47)
......
16 On the primary FEP, sync the entity and link information on the backup FEP with the primary FEP, enter /usra/fep/etc/bdr_commit Reference: “BDR task/enter/response” (p. 3-86) “bdr_commit” (p. A-8)
Result: The bdr_commit command takes a few minutes to run. You can monitor its progress by running (on the primary FEP)
logcat -l bdr -t5 -c
......
17 On the NTM host machine, create fep (dcc) office for the backup FEP and activate this newly-created fep office.
...... 190-406-737 Alcatel-Lucent — Internal 3-89 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
18 On the NTM host machine, enter linkstat.
......
19 Connection status for the newly created FEP entity should indicate fail. This is the correct status for the entity, because the backup FEP application is not running. When FEP processing is taken over by the backup FEP, linkstat will show the connection status of conn for the backup FEP and fail for the primary FEP.
...... E ND OF STEPS ......
...... 3-90 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Verifying BDR
Overview Figure 3-6 shows typical output of the bdr_stat command and a description of the procedures (based on this output) that should be used by the customer to verify that BDR is configured correctly. Although you will need to log into both the primary and backup FEPs to configure BDR, you only need to log into the primary FEP to verify BDR setup.
Figure 3-6 bdr_stat command output System name: fep1. The FEP application is Running. BDR Feature is available. BDR is ACTIVE. BDR backup system is fep2.
Backup system name: fep2. The FEP application is Shutdown. BDR Feature is available. BDR is DEACTIVE. BDR backup system is fep1.
• fep1 is the local system that the user is logged into. • fep2 is the remote system. • primary fep is the FEP that is processing the network entities. • backup fep is the FEP that is ready to take over processing of the network entities if something, e.g., a hardware problem should prevent the primary FEP from processing them.
Note: The term “remote” refers to the dedicated FEP for your local FEP. A “remote” FEP does not imply that it is either a backup or a primary FEP.
Instructions Follow these steps:
......
1 Log in to the primary FEP as fep.
......
2 Refer to Figure 3-7 for Step 3 through Step 8.
...... 190-406-737 Alcatel-Lucent — Internal 3-91 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Figure 3-7 bdr_stat output $ /usra/fep/etc/bdr_stat
System name: cbfepuc. The FEP application is Running. BDR Feature is available. BDR is ACTIVE. BDR backup system is cbfepud.
Figure notes: • The line “System name:
......
3 Verify the state of the FEP application and BDR. Enter: /usra/fep/etc/bdr_stat ......
4 Skip the line “BDR is
......
5 Perform one of these steps: a. Define the name of the remote FEP. Enter: centity -B
......
6 Return to the line “BDR is
...... 3-92 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... • If the system name is the primary FEP and “BDR is ACTIVE”, go to Step 9. • If the system name is the backup FEP, then you are logged into the wrong FEP. Restart this procedure to log into the primary FEP.
......
7 Activate BDR. Enter: /usra/fep/etc/bdr_act ......
8 Refer to Figure 3-8 for Step 9 through the end of this procedure.
Figure 3-8 bdr_act output Backup system name: cbfepud. The FEP application is Shutdown BDR Feature is available. BDR is DEACTIVE. BDR backup system is cbfepuc. $
Figure notes: • The line “Backup system name
......
9 Skip the line “BDR is
......
10 Log in to the backup FEP.
......
11 Perform one of these steps: ...... 190-406-737 Alcatel-Lucent — Internal 3-93 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... a. To define the name of the remote FEP, enter: centity -B
......
12 The line “BDR is
......
13 Log in to the remote system.
......
14 To deactive BDR, enter: /usra/fep/etc/bdr_deact Result: The system is now set up to run the BDR commands and commit files from the primary FEP to the backup FEP.
...... E ND OF STEPS ......
...... 3-94 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR take over/switch back system administration tasks
Overview Situations that warrant the backup FEP taking over the functionality of the primary FEP are: 1. The primary FEP system has failed (the system has hardware problems). 2. The primary FEP application has failed but the primary FEP is still active. 3. The primary FEP needs to be shutdown for maintenance reasons. 4. Control to the primary FEP from the backup FEP is returned.
Scenario 1 — primary FEP system has failed This scenario assumes that the primary FEP system has crashed, has been turned off, or is off the network. This requires the backup FEP to take over operations for the primary FEP. Before the primary FEP must be out-of-service and the connections to all of its collectible network entities must be dropped so that they can be started on the backup FEP. This means that the NTM FEP application must NOT be running on the primary FEP. To resolve this scenario: 1. Log in to the backup FEP as fep. 2. Enter: startfep Result: This will start the FEP application on the backup FEP. Since the primary FEP is down, the backup FEP will connect to all the network entities that were attached to the primary FEP.
Scenario 2 — Primary FEP application has failed This scenario assumes that the backup FEP can reach the primary FEP and that the FEP application has failed due to some application or network problem (e.g., Datakit or TCP/IP) To resolve this scenario:. 1. Log in to the primary FEP as fep. 2. Enter: /usra/fep/etc/bdr_takeover
If you continue the FEP application will be started on
...... 190-406-737 Alcatel-Lucent — Internal 3-95 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: This will start the FEP application on the backup FEP. Since the primary FEP application is down, the backup FEP will connect to all the network entities that were attached to the primary FEP.
Scenario 3 — primary FEP taken over due to scheduled maintenance This scenario assumes that the primary FEP is still active and collecting data, but the user wants to move the data collection to the backup FEP. 1. Log in to the primary FEP as fep. 2. Enter: /usra/fep/etc/bdr_takeover
If you continue the FEP application will be stopped on
Scenario 4 — returning control to primary FEP from the backup FEP This procedure allows the backup FEP to return control to the primary FEP. 1. Log in to the backup FEP as fep. 2. If you have made changes on the backup FEP (such as creating, changing or deleting an office or link from the FEP to the NTM host), then you need to transfer these updates back to the primary FEP. Enter: /usra/fep/etc/bdr_act /usra/fep/etc/bdr_commit /usra/fep/etc/bdr_deact
Result: You will be prompted for confirmation for the bdr_act and bdr_deact commands.
3. Enter: /usra/fep/etc/bdr_takeover
Do you want to stop the FEP application on
...... 3-96 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: This will stop the FEP application on the backup FEP and start it on the primary FEP. Since the backup FEP application was stopped, the primary FEP will connect to all the network entities that were attached to the backup FEP.
5. On Primary FEP, enter: /usra/fep/etc/bdr_act Result: You will be prompted for confirmation.
Result: This will enable any entity and link changes that occur on the primary FEP to be automatically copied from the primary FEP to the backup FEP.
...... 190-406-737 Alcatel-Lucent — Internal 3-97 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Government emergency telecommunications service (GETS)
Feature/generic restrictions Feature 328, “Enhanced Switch Support for GTD-5 Generic 1732” is available only if it has been purchased. GETS information is only valid for GTD-5 1732 switch generic or later. It is not supported for any other office type.
Overview Feature 328, “Enhanced Switch Support for GTD-5 Generic 1732” provides enhanced routing and priority service through the interexchange carrier networks during times of crisis or natural disasters. Universal access is provided for appropriate authorities through 1-710- NCS-GETS. After authentication, they proceed to dial the destination number. The networks are required to provide special routing and, in some cases, trunk queuing to enhance the probability that the call will receive answer supervision. GETS calls will be exempted from most network management controls. The FEP does not process GETS information but merely relays the information to the NTM host.
...... 3-98 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
4 Switch Administration
Overview
Purpose This chapter provides procedures and background information regarding administering the switch.
This chapter contains the following topics:
Switch connectivity 4-2
Connecting a switch to your FEP 4-5
Disconnecting a switch from your FEP 4-6
Checking switch status 4-7
Synchronizing switches, FEPs, and NTM 4-11
Checking switch data collection 4-14
Testing FEP-switch links — monitored GTD-5 switches 4-16
Testing FEP-switch links — 5ESS, DMS, polled GTD5 4-19
Creating a switch 4-25
Deleting a switch 4-27
Activating a switch-FEP link 4-29
Deactivating a switch-FEP link 4-30
Changing a switch’s record base data on the FEP 4-31
...... 190-406-737 Alcatel-Lucent — Internal 4-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Switch connectivity
Overview FEP5.0 supports 5ESS, DMS 100/200, DMS 250, DMS 500 and GTD-5 switch types. The FEP connects to all supported switch types via Datakit VCS, except for the GTD-5. The FEP connects to the GTD-5 either via Datakit VCS or TCP/IP.
GTD1732 If the GTD-5 is on generic gtd1732, then it connects to the FEP using Datakit using a monitored interface, sending ASCII data. This means the FEP does not poll for data, but rather waits for it to arrive from the switch.
GTD4003 and later If the GTD-5 is on generic gtd4003 or later, then the FEP connects via TCP/IP through the AISwitch 180. The AISwitch 180 performs TCP/IP to X.25 protocol conversion and vice versa. In this manner, the FEP polls for binary data using a polled interface, just as it does for the 5ESS, DMS 100/200, DMS 250 and DMS 500 switch types. The FEP’s poll is received by a General Processing Unit (GPU) connected to the actual GTD-5 switch. GTD-5 data collection via TCP/IP is only available if the GTD-5 switch has been defined on generic gtd4003 or later.
Diagram Figure 4-1 provides a diagram of how the switches connect to the FEP.
...... 4-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Figure 4-1 Connecting a switch to your FEP
Supported generics For your convenience, the following is a list of the switch generics supported. Table 4-1 Supported Switch Generics Switch Type Generics 5ESS 5e4, 5e5, 5e6, 5e7, 5e8, 5e9_2, 5e10, 5e11, 5e12, 5e13, 5e14, 5e15 DMS 100 & dms24, dms25, dms26, dms27, dms 28, na007, na009, DMS 200 na010, na012, na014 DMS 250 ucs07, ucs10, usc12, usc14 DMS 500 ncs07, ncs12, ncs14 GTD-5 gtd1732, gtd4003
Additional information For the FEP-NTM version of the figure above, see Figure 5-1, “Connecting your FEP to NTM” (p. 5-2), and its procedure (“Connecting a FEP to NTM” (p. 5-3)). That procedure is independent from the procedure below. That is, either procedure can be done before the other. All references to “FEP-Switch” links could equally be termed “Switch-FEP” links. We are not implying direction.
...... 190-406-737 Alcatel-Lucent — Internal 4-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Various FEP commands in this chapter use switch name as a parameter. Switch name is the 11-character CLLI. In each case, you can instead use the switch number, which is a unique number you assign to the switch. (You assign switch numbers in “Creating a switch” (p. 4-25).)
...... 4-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Connecting a switch to your FEP
Instructions Follow these steps:
......
1 Physically connect the switch to the NTM network. How this is done depends on the switch type.
Responsibility: Network administrators
Reference: Appendix B, “Datakit VCS Settings”
......
2 For a polled GTD-5, configure the AISwitch 180.
Responsibility: You
Reference: Chapter 6, “AISwitch Configuration” and AI (Applied Innovation’s) Web Site at: http://www.aiinet.com/
......
3 Create the switch — that is, define it in the FEP.
Responsibility: You
Reference: “Creating a switch” (p. 4-25)
......
4 Activate the switch — that is, tell the FEP to start collecting data from the switch, and to start forwarding data to the switch.
Responsibility: You
Reference: “Activating a switch-FEP link” (p. 4-29)
......
5 Add the switch to NTM. (You can do Steps 2, 3 and 4 before or after this step.)
Responsibility: NTM administrators
Reference: Chapter 9, “Adding and Removing Network Elements” in the System Administration Guide
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 4-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Disconnecting a switch from your FEP
Instructions Follow these steps:
......
1 Remove the switch from NTM. (You can do Steps 2, 3 and 4 before or after this step.)
Responsibility: NTM administrators
Reference: Chapter 9, “Adding and Removing Network Elements” in the System Administration Guide
......
2 Deactivate the switch — that is, tell the FEP to stop collecting data from the switch.
Responsibility: You
Reference: “Deactivating a switch-FEP link” (p. 4-30)
......
3 Delete the switch — that is, remove it from the FEP.
Responsibility: You
Reference: “Deleting a switch” (p. 4-27)
......
4 For a polled GTD-5, delete the appropriate AISwitch 180 entries.
Responsibility: You
Reference: Chapter 6, “AISwitch Configuration” and AI (Applied Innovation’s) Web Site at: http://www.aiinet.com/
......
5 If needed, physically disconnect the switch from the NTM network. How this is done depends on the switch type.
Responsibility: Network administrators
Reference: Appendix B, “Datakit VCS Settings”
...... E ND OF STEPS ......
...... 4-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Checking switch status
Purpose Use this procedure to see if each switch’s status is “active” or “off”. This gives some additional information about the switch, including: switch generic, Datakit or TCP/IP address, and time offset and issue (DMS 250 and DMS 500 only), which are the parameters you can change using “Changing a switch’s record base data on the FEP” (p. 4-31). It also lists the time the FEP last received 5-minute data from the switch, which lets you know whether the switch and FEP are communicating. If you want to see all data types collected, use “Checking switch data collection” (p. 4-14).
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter: rsentity all Result: Output appears as illustrated in “Check switch status output” (p. 4-8). The command above shows you the status for all switches, regardless of whether the switch is activated or deactivated. If there are a lot of switches, you may want to use rsentity all | pg to enable you to page through output. To see the status for just one switch, use its switch name in place of the all. To see the status for only activated offices, use active instead of all.
......
3 If “TIME” says “none”, or shows a time from a previous 5-minute period, then either the FEP is having problems processing the data, or the data is arriving from the switch too early or too late for FEP to process.
Reference: To see if switches and the FEP need to be synchronized, see “Determining if switch time is wrong” (p. 4-12).
......
4 If a switch’s “STATUS” is “AC/NC” (active but not collecting), use the tlentity command to further diagnose the problem.
Reference: For monitored GTD-5 switches, see “Testing FEP-switch links — monitored GTD-5 switches” (p. 4-16) for a tlentity example.
...... 190-406-737 Alcatel-Lucent — Internal 4-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Reference: For 5ESS, DMS, DMS 250, DMS 500 and polled GTD-5 switches, see “Testing FEP-switch links — 5ESS, DMS, polled GTD5” (p. 4-19) for a tlentity example.
...... E ND OF STEPS ......
Check switch status output Figure 4-2 shows switch status output for an office connected to the FEP via Datakit VCS.
Figure 4-2 Output for office connected via Datakit ENTITY NAME DATAKIT or TCP/IP ADDRESS ISSUE # TYPE GENERIC STATUS TIME OFFSET SUSPECT fepuagtd001 dvsim2.gtd5SIM9 0 gtd5 gtd1732 ACTIVE Jul 11 13:21:58 0 Figure 4-3 shows switch status output for a polled GTD-5. The switch communicates using X.25 protocol to the AISwitch 180, which converts the protocol to TCP/IP and forwards the data to the FEP.
Figure 4-3 Output for a polled GTD-5 office ENTITY NAME DATAKIT or TCP/IP ADDRESS ISSUE # TYPE GENERIC STATUS TIME OFFSET SUSPECT gtd5agcslab ai296a1:2001:2002:2003 149 gtd5 gtd4003 OFF none -3 Figure 4-4 shows switch status output for a DMS 250. Notice the ISSUE column is populated to indicate the interface being used by the switch.
Figure 4-4 Output for a DMS 250 office ENTITY NAME DATAKIT or TCP/IP ADDRESS ISSUE # TYPE GENERIC STATUS TIME OFFSET SUSPECT fepuadms139 ostcnm/nmsim3.rdtty..40588 issue2 138 dms250 ucs08 ACTIVE Jul 14 14:30:36 0 Y
...... 4-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... rsentity output fields/descriptions Table 4-2 provides descriptions for the output fields of the rsentity command. Table 4-2 “rsentity” output fields/descriptions Output Field Description ENTITY The 11-character CLLI that identifies the switch. NAME DATAKIT or The destination dialstring for Datakit VCS for all TCP/IP switch types except the polled GTD-5. For the polled ADDRESS GTD-5, this is the name of the “converter_interface_card_name” followed by 3 colon separated TCP/IP port numbers representing (respectively) the discrete control channel, 5-minute data channel, and audit/scheduling channel. # Switch number. TYPE Switch type: “dms100”, “dms200”, “dms250”, “dms500”, “gtd5”, or “ess5”. GENERIC Switch generic. STATUS Switch status: “OFF” or “ACTIVE”. For 5ESS, DMS, DMS 250, DMS 500 and polled GTD-5 switches, this can also be “AC/NC” (active but not collecting). TIME Time that the FEP finished processing the last 5-minute data report from the switch (using the switch’s time zone, if different from the FEP’s or NTM’s time zone). OFFSET Time zone offset. This is switch time minus FEP time. For example, if it is 9 a.m. at the switch when it is 10 a.m. at the FEP, this is 9 minus 10, which is “-1”. If it is 10 a.m. at the switch when it is 9 a.m. at the FEP, this is 10 minus 9, which is “1”. Range is “-12” to “12”.
...... 190-406-737 Alcatel-Lucent — Internal 4-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table 4-2 “rsentity” output fields/descriptions
...... 4-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Synchronizing switches, FEPs, and NTM
Overview Each switch, FEP, and NTM machine is a computer– each with its own operating system time. Hours on switch, FEP, and NTM computers can vary by time zone, but minutes and seconds must be synchronized.
FEP-NTM synchronization Do nothing. The FEP automatically synchronizes itself to its NTM machine. However, if you see one NTM006 message once during a 5-minute period, no problem. But if you see it more than once, it probably means you have more than one FEP-NTM link active, causing the FEP to try to synchronize to more than one NTM. To see if you have more than one link, use the rsnlink all command. If more than one is active, deactivate all but one.
FEP-Switch synchronization Switches should be synchronized as close as possible to the FEP time. For the monitored GTD-5, the FEP refuses ASCII data that arrives more than 20 seconds early. The FEP accepts ASCII data for the monitored GTD-5 up to 240 seconds late, but such tardy data can cause problems with real-time data display at NTM. For 5ESS, DMS, DMS 250, DMS 500 and polled GTD-5 switch types, the FEP polls for 5- minute data and will mark the data suspect if the switch time is more than 30 seconds early or more than 120 seconds late.
...... 190-406-737 Alcatel-Lucent — Internal 4-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Determining if switch time is wrong
Instructions Follow these steps:
......
1 Make a quick survey of switch times. Enter: rsentity active Result: This command shows you data for all activated switches under your FEP. If the FEP has many switches, you may want to use rsentity active | pg to enable you to page. Output for each switch resembles the following: ENTITY NAME DATAKIT or TCP/IP ADDRESS ISSUE # TYPE GENERIC STATUS TIME OFFSET SUSPECT fepuagtd001 dvsim2.gtd5SIM9 0 gtd5 gtd1732 ACTIVE Jul 11 13:21:58 0 The switch time under the “TIME” column is NOT the time at the switch. Instead, it is the time when the FEP finished processing each switch’s data. However, this “TIME” can alert you to synchronization problems.
......
2 If FEP-switch synchronization is okay, you should not see “none” or old times in the “TIME” field (old would be more than 5 minutes old). In that case, STOP. YOU HAVE COMPLETED THIS PROCEDURE. If you do see “none” or old times in the “TIME” field, it may be because the switch’s time is so far out of synchronization with the FEP that the FEP did not accept the data. If this is the case, the switch time needs to be reset. Continue with the next step.
......
3 If you do see “none” or old times, there is a chance they were caused by corrupt data instead of synchronization problems. To check this, wait for the next 5-minute period and enter rsentity active again. If “none” or old times go away, then apparently FEP-switch synchronization is okay — and you do not need to continue with this procedure. If you do see them again, continue with the next step.
......
4 Call the switch administrators and have them check their times and reset them.
...... 4-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Note: If you want, you can check switch time yourself for 5ESS, DMS, DMS 250 and DMS 500 and polled GTD-5 switches. To do this, use the tlentity command with the time argument. That is enter tlentity switch name, and then enter time at the prompt.
Reference: See “Testing FEP-switch links — 5ESS, DMS, polled GTD5” (p. 4-19) for a tlentity example.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 4-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Checking switch data collection
Purpose This command tells you when the last file of 5-minute, control, and audit data was received from switches.
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter: prtsint all Result: Output appears, as illustrated in “Check switch data collection output” (p. 4-14). This command shows you all data for all switches. If there are a lot of switches, you may want to use prtsint all | pg to enable you to page through output. To see data for just one switch, use its switch name in place of the all. To see data for all activated switches, use active instead of all. To see only a particular data type, use the “-n” option to prtsint. Enter: prtsint all -n5min To see the last time 5-minute data was collected for all switches, use ctl or aud in place of 5min to see the last control and audit response, respectively.
...... E ND OF STEPS ......
Check switch data collection output The output lists the last file of 5-minute, audit, and control data received from each switch. Each such file is kept until the next file is received, or until it is a week old. So, if you see, for example, “ctl Data not available”, it means no such data has been received for at least a week. An “s” in the FLAG column indicates suspect data. Figure 4-5 shows an example of an office collecting valid 5-minute data:
Figure 4-5 Office collecting valid 5-minute data ENTITY NAME TYPE BYTES TIME FLAG PATH NAME
...... 4-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... fepuagtd001 5min 6722 Jul 11 13:46 /raw/fepuagtd001/5min/000711134656 Entity aud Data not available - fepuagtd001 Entity ctl Data not available - fepuagtd001 Figure 4-6 shows an example of an office collecting suspect 5-minute data:
Figure 4-6 Office collecting suspect 5-minute data ENTITY NAME TYPE BYTES TIME FLAG PATH NAME fepuaes5105 5min 3224 Jul 20 08:45 s /raw/fepuaes5105/5min/000720084532 Entity aud Data not available - fepuaes5105 Entity ctl Data not available - fepuaes5105 prtsint output fields/descriptions Table 4-3 provides descriptions for the output fields of the prtsint command. Table 4-3 “prtsint” Output Fields/Description Output Field Description ENTITY The 11-character name that identifies the switch. NAME TYPE Data type: “5min”, “aud”, or “ctl”. BYTES Number of bytes in the file. TIME Time that the FEP received the last data file from the switch. This uses the FEP time zone, if different from the switch or NTM time zone. FLAG Blank or “s”. An “s” means the FEP found the data is “suspect”. PATH Full path to file holding the data. NAME
...... 190-406-737 Alcatel-Lucent — Internal 4-15 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Testing FEP-switch links — monitored GTD-5 switches
Purpose Use this procedure to verify that data is crossing the FEP-switch link.
Before you begin You must deactivate the switch whose FEP-switch link you are testing. While deactivated, the switch cannot send data to the FEP, nor can it receive control or audit requests from NTM. Coordinate with the NTM administrator to ensure you will be using this procedure when NTM will NOT be sending control or audit requests to the switch. Also, it is a good idea NOT to use this procedure near 5-minute boundaries, when you might prevent the switch from sending its 5-minute data to NTM.
......
1 Log in as fep.
......
2 See if the switch is active. Enter: rsentity
Example: For switch “tampflxe62h”, enter: rsentity tampflxe62h Result: Output is similar to the following. Look for the “ACTIVE” status.
ENTITY NAME DATAKIT or TCP/IP ADDRESS ISSUE # TYPE GENERIC STATUS TIME OFFSET SUSPECT tampflxe62h dvsim2.gtd5SIM9 0 gtd5 gtd1732 ACTIVE Jul 11 13:21:58 0 If the switch is active, deactivate it by entering deaentity. Reference: “Deactivating a switch-FEP link” (p. 4-30)
......
3 Enter: tlentity
Example: For switch “tampflxe62h”, enter: tlentity tampflxe62h
...... 4-16 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: Output lists all switch-to-FEP data, as it is received at the FEP. Depending on when you run tlentity, you may need to wait up to 30 seconds before seeing any data (a discrete message). See Figure 4-7, “Example of tlentity”.
......
4 To stop output, press the DELETE key.
......
5 Reactivate the switch. Enter: aentity
Example: For switch “tampflxe62h”, enter: aentity tampflxe62h
...... E ND OF STEPS ......
Testing FEP-Switch Links — Monitored GTD-5 Switches Output Typically, only NTM network managers need to know what output fields mean (that information is in switch documents). You need to know only that data is arriving from the switch, which you verify simply by noting that you are getting output. Figure 4-7 shows discrete data in the top section and 5-minute data in the bottom portion of the screen.
...... 190-406-737 Alcatel-Lucent — Internal 4-17 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Figure 4-7 Example of tlentity
Note: If controls or audit data are also being sent from the switch, they will also be listed. (But, you would probably not want to run this when controls or audits are scheduled.
)
...... 4-18 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Testing FEP-switch links — 5ESS, DMS, polled GTD5
Purpose Use this procedure to verify that data is crossing the FEP-switch link. The following procedure (sends a data request to) polls 5ESS, DMS, DMS 250, DMS 500 and polled GTD-5 switches. By polling the switch, and receiving a reply, we prove the FEP-switch link is okay.
Before you begin In this procedure you will deactivate the switch whose FEP-switch link you are testing. While deactivated, the switch cannot send data to the FEP, nor can it receive control or audit requests from NTM. Coordinate with the NTM administrator to ensure you will be using this procedure when NTM will NOT be sending control or audit requests to the switch. Also, it is a good idea NOT to use this procedure near 5-minute boundaries, when you might prevent the switch from sending its 5-minute data to NTM.
Instructions Follow these steps:
......
1 Log in as fep.
......
2 See if the switch is active. Enter: rsentity
Example: For switch “dublin5ess1”, enter: rsentity dublin5ess1 Result: Output is similar to the following. Look for the “ACTIVE STATUS”.
ENTITY NAME DATAKIT or TCP/IP ADDRESS ISSUE # TYPE GENERIC STATUS TIME OFFSET SUSPECT
dublin5ess1 oh/testdk/dub5ess 11 ess5 5e12 ACTIVE May 17 01:39:40 1 If the switch is active, deactivate it. Enter: deaentity
...... 190-406-737 Alcatel-Lucent — Internal 4-19 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Example: For switch “dublin5ess1”, enter: deaentity dublin5ess1
......
3 Enter: tlentity
Example: For switch “dublin5ess1”, enter: tlentity dublin5ess1 Result: You will see a few messages indicating that the FEP is trying to connect. Then you may see one or more of the following messages, which may be repeated: Waiting for chan 1 to come up, state=1 - WAITING FOR CONNECT Waiting for chan 2 to come up, state=1 - WAITING FOR CONNECT Waiting for chan 3 to come up, state=1 - WAITING FOR CONNECT Eventually you will see: Chan ‘1’ in active state Chan ‘2’ in active state Chan ‘3’ in active state Finally, you will receive the following prompt: Cmd(time): ......
4 At the “Cmd(time)” prompt, enter: ? Result: This will list what you can enter:
Inputs: time - send time poll, print difference poll - (poll a b …) send poll down - send FEP planned down message status - check link status quit - quit program ......
5 At the “Cmd(time)” prompt, enter: status
...... 4-20 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: Output will resemble:
Link Status: Chan ‘1’ in active state Chan ‘2’ in active state Chan ‘3’ in active state The prompt changes to: Cmd(status) If channel 1 is not active, you cannot poll for discrete data or the switch’s time (later in this procedure). Channel 1 is also used for sending control requests, but we don’t typically do this in this procedure. If channel 2 is not active, you cannot poll for 5-minute data (later in this procedure). Channel 3 does not matter — although it is used for audits and scheduling, we don’t use channel 3 in this procedure as most problems can be identified by just looking at channels 1 or 2.
......
6 At the “Cmd(status)” prompt, enter: time Result: Output resembling the following tell you that the poll was sent:
SENT (channel 1) 105 0 If the switch receives the poll and responds to it, output resembling the following appears: RECEIVED Message (channel 1) LOCAL time = 15:13:13 ENTITY time = 15:13:17 (time zone offset= 0) Time Difference (ENTITY - LOCAL) = 4 seconds Most noteworthy is simply the fact that you got the “RECEIVED”. This tells you that data is travelling across the FEP-switch link. (If the link is not good, you would see only the “SENT” part of the output.) The “Message (channel 1)” part of the output tells you that the link’s channel 1 carried the response to your poll for time data. (There is no special reason you would want to know this, but it does tell you that channel 1 is working.) The “LOCAL time”, “Entity time”, and “Time difference” part of the output tells you the time set at the switch and at the FEP. A time difference of 30 seconds or more or -120 seconds or more (actually less, since this is a negative number) will cause the data to be marked suspect. (Use “Determining if switch time is wrong” (p. 4-12) to synchronize.)
...... 190-406-737 Alcatel-Lucent — Internal 4-21 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
7 Now we will check discrete data, which is on channel 1. At the “Cmd(time)” prompt. Enter: poll 101 0 At the “Channel:” prompt. Enter: 1 At the “Output format (format)” prompt, press Return. Result: If you are receiving discrete data from the switch, output should be similar to this. format
SENT (channel 1) 101 0
RECEIVED received 32 bytes - end of message
Message (channel 1)
Header:
generic id = 4 2 1 message type = 101(NM discrete) time & date = 3 105 30 37777777740 43 146 43 146 (Mon Oct 24 15:14:20 1998) header length = 24 option switches = 20040005674
Section definitions:
sec_id prec sec_ptr num_rec rec_len ______112414
Data:
Section 1: reg: 0 1 2 3 4 5 6 7 8 9 ______0:259 8 0 0
Total of 32 bytes received
...... 4-22 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... The “message type = 101 (NM discrete)” tells you that the switch recognized the request to send discrete data over this link. If you see “unknown” or anything else in place of “NM discrete”, tell the switch administrator. The day shown should match the current day. If it does not, tell the switch administrator.
......
8 Check 5-minute data on channel 2. At the “Cmd(poll)” prompt. Enter: poll 102 0 At the “Channel:” prompt, enter: 2 At the “Output format (format)” prompt, press Return. Result: If you are receiving 5-minute data from the switch, output should be similar to the sample in the following step.
......
9 Check 5-minute data on channel 2. At the “Cmd(poll)” prompt. Enter: poll 102 0 At the “Channel:” prompt, enter: 2 At the “Output format (format)” prompt, press Return.
Result: If you are receiving 5-minute data from the switch, output should be similar to this:
format
SENT (channel 2) 102 0
RECEIVED (The following line will be repeated until all data has been received.) received 256 bytes - more coming received 256 bytes - end of message
Message (channel 2) Header:
...... 190-406-737 Alcatel-Lucent — Internal 4-23 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... generic id = 4 2 1 message type = 102(NM 5 minute) time & date = 3 31125 37777777700 43 146 43 146 (Mon Oct 24 14:26:32 1998) header length = 24 option switches = 37777777777
Section definitions:
sec_id prec sec_ptr num_rec rec_len ______1 1 24 1407 1
Data:
Section 1: reg: 0 1 2 3 4 5 6 7 8 9 ______0: 4 4 6 6 8 4 11 17 0 7 (The line above is repeated, listing all registers from the switch.) Total of 2835 bytes received The “message type = 102 (NM 5 minute)” tells you that the switch knows to send 5- minute data over this link. If you see “unknown” or anything else in place of “NM 5- minute”, tell the switch administrator.
......
10 At the “Cmd(status)” prompt, enter: quit ......
11 Reactivate the switch. Enter: aentity
Example: For switch “tampflxe62h”, enter: aentity tampflxe62h Reference: “Activating a switch-FEP link” (p. 4-29)
...... E ND OF STEPS ......
...... 4-24 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Creating a switch
Purpose Use this procedure to introduce the switch to the FEP by: • Creating the FEP files and directories the FEP must have to know about the switch • Putting those tables into effect • Creating the FEP-switch link
Before you begin To see if a switch has already been created, enter rsentity all | pg. If the switch is listed, it has already been created.
Note: If this is a polled GTD-5 switch, you must configure the AISwitch 180 first using the TCP/IP port numbers as described in the “-a” option of the centity command.
Reference: See “Tips on navigating through the AISwitch menu” (p. 6-3) for more background on the AISwitch 180. For help with selecting TCP/IP port numbers, see “Port–to–Link Mapping (SVC)” (p. 6-22).
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter: centity entity_name -t entity_type [-n entity_number] {-a destination_dialstring|converter_interface_card_name:TCP/IP port for discrete/control channel:TCP/IP port for 5-minute data channel:TCP/IP port for audits/scheduling channel} -d time_difference -g generic_id [-h header_issue] If the switch type is a DMS is on generic NA007 or later, or a DMS 250 generic UCS10 or later, and it is sending more than 250 trunk groups worth of data (i.e. Feature 263, “DMS 100/200 Switch Surveillance of 1024 Trunk Groups Via FEP”), the data must be sent at 19,200 baud rate to ensure no delay or loss of data. To achieve 19,200 baud rate, an entire SLM must be dedicated to that one office.
Example: Creating a monitored GTD-5 switch centity tampflxe62h -t gtd5 -n 101 -d -1 -a dvfep4.gtd5sim -g gtd1732
...... 190-406-737 Alcatel-Lucent — Internal 4-25 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Example: Creating a polled GTD-5 switch centity fepuagtd000 -t gtd5 -n 149 -d 0 -a ai296a1:1001:1002:1003 -g gtd4003 Reference: See the centity command (A-13) for details about parameter values.
......
3 Watch for response on your FEP console.
Result: A successful execution will give you output similar to the following:
Vport Name: tampflxe62h Vport Device: /dev/vport/vpapl0073 Outcall Address: dvfep4.gtd5sim Transport Device: /dev/dk Server Name: /usra/fep/bin/dkoutsrvr Semantics: PVC NOHUP Entity tampflxe62h was successfully created. A polled GTD-5 will only give the following: Entity tampflxe62h was successfully created......
4 If you are ready to activate the switch, use “Activating a switch-FEP link” (p. 4-29).
...... E ND OF STEPS ......
...... 4-26 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Deleting a switch
Purpose Use this procedure to remove all references to a switch from the FEP database.
Note: Once you have deleted a switch, you cannot “un-delete” it to get it back again. Instead, you would have to create it again, using “Creating a switch” (p. 4-25).
Instructions Follow these steps:
......
1 Log in as “fep”.
......
2 See if the switch is active. Enter: rsentity
Example: For switch “tampflxe62h”, enter: rsentity tampflxe62h Result: Output is similar to the following. Look for the “ACTIVE” status.
ENTITY NAME DATAKIT or TCP/IP ADDRESS ISSUE # TYPE GENERIC STATUS TIME OFFSET SUSPECT tampflxe62h fl/tampdk/tampflxe 11 gtd5 17.21 ACTIVE May 17 01:39:40 1 If the switch is active, deactivate it by using the FEP command deaentity. Reference: “Deactivating a switch-FEP link” (p. 4-30)
......
3 Enter: delentity
...... 190-406-737 Alcatel-Lucent — Internal 4-27 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: The following lines are displayed:
delentity tampflxe62h Entity “tampflxe62h” will be deleted Are you sure? (y or n) y Port deleted Entity was successfully deleted ......
4 If this is a polled GTD-5 switch, delete the corresponding AISwitch 180 entries.
Note: Each polled GTD-5 switch has 3 AISwitch 180 aliases defined for it.
Reference: “Deleting a switch from the AISwitch” (p. 6-20)
...... E ND OF STEPS ......
...... 4-28 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Activating a switch-FEP link
Purpose Use this procedure to start switch-to-FEP data collection. Use this procedure after creating a switch or after temporarily deactivating it.
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter: rsentity
......
3 If this is the first time this switch has been activated (or if you have problems in the previous step), then use one of the following procedures to test the link to the switch: • “Testing FEP-switch links — monitored GTD-5 switches” (p. 4-16) • “Testing FEP-switch links — 5ESS, DMS, polled GTD5” (p. 4-19)
......
4 Enter: aentity
Note: For a polled GTD, the AISwitch links need to be activated.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 4-29 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Deactivating a switch-FEP link
Purpose Use this procedure to stop switch-to-FEP data collection for the switch you specify. Typically, you would use this in three cases: 1. Before executing tlentity to test a switch link, see: – “Testing FEP-switch links — 5ESS, DMS, polled GTD5” (p. 4-19) – “Testing FEP-switch links — monitored GTD-5 switches” (p. 4-16) 2. Before executing delentity to delete a switch, see: – “Deleting a switch” (p. 4-27) 3. After executing chentity, to change a switch, see: – “Changing a switch’s record base data on the FEP” (p. 4-31) Reactivate the switch using aentity. See “Activating a switch-FEP link” (p. 4-29).
Note: If you use this procedure for a monitored GTD-5 switch, and if the switch is currently processing a control or audit, termination is delayed until the control or audit is complete. Please wait. In this case, a TRN034 system response will go to the error log (this is not an error, and you do not need to take any action).
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter: deaentity switch name After about 5 seconds, the switch is deactivated and you will receive a message similar to the following: Entity ‘tampflxe62h’ deactivated
...... E ND OF STEPS ......
...... 4-30 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Changing a switch’s record base data on the FEP
Background A switch’s record base of data is the information in the FEP that identifies the switch. You could change this data by deleting it (“Deleting a switch” (p. 4-27)) and then creating it again (“Creating a switch” (p. 4-25)).
Purpose The procedure below enables you to change a switch’s data more easily. However, this can change only the four items in Table 4-4. To change other parameters, such as switch type, you would have to delete and create the switch again.
Reference: Background
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter: rsentity
......
3 If the switch is valid, look at the current values of the parameters that you can change in this procedure. See Table 4-4, “Items/Descriptions of Changeable Fields” (p. 4-33).
......
4 Enter: chentity Reference: See the chentity command (A-17) for valid parameter values.
Example: To change switch “dms250test1” so it has a new time difference of “-1”, enter the following: chentity dms250test1 -d -1 If a parameter is invalid, the entire update will fail, and a screen message will warn you about your bad parameter (or the first bad parameter, if more than one is bad).
...... 190-406-737 Alcatel-Lucent — Internal 4-31 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: If the update is successful, screen output will resemble the following:
Port deleted Vport Name: dms250test1 Vport Device: /dev/vport/vpapl0001 Outcall Address: oh/ntm/slm51p1 Transport Device: /dev/dk Server Name: /usra/fep/bin/dkoutsrvr Semantics: PVC NOHUP Entity information was successfully changed. However, changes will not take effect until entity has been deactivated and activated. A polled GTD-5 will only give the following: Entity information was successfully changed. However, changes will not take effect until entity has been deactivated and activated......
5 Deactivate the switch. Enter: deaentity
......
6 Activate the switch. Enter: aentity
...... E ND OF STEPS ...... rsentity output Figure 4-8 provides a sample of output from the rsentity command.
Figure 4-8 Sample rsentity output ENTITY NAME DATAKIT or TCP/IP ADDRESS ISSUE # TYPE GENERIC STATUS TIME OFFSET SUSPECT fepuadms130 ostcnm/nmsim3.rdtty..40588 issue2 129 dms250 ucs08 ACTIVE Jul 17 09:30:26 0 Y
Changeable fields Table 4-4 provides item names and descriptions for fields that can be changed for the rsentity command.
...... 4-32 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
Table 4-4 Items/Descriptions of Changeable Fields Item Description OFFSET Time zone offset. This is switch time minus FEP time. For example, if it is 9 a.m. at the switch when it is 10 a.m. at the FEP, this is 9 minus 10, which is “-1”. If it is 10 a.m. at the switch when it is 9 a.m. at the FEP, this is 10 minus 9, which is “1”. GENERIC Switch generic. You cannot change the switch generic from gtd1732 to gtd4003 and later for the GTD-5. This is because generic gtd1732 implies monitored data collection, while gtd4003 and later implies polled data collection. If you wish to upgrade a GTD-5 switch’s generic from gtd1732 to gtd4003 or later, you must delete the gtd1732 entity and recreate it using the gtd4003 generic. Reference: Reference: “delentity” (p. A-29), “centity” (p. A-13) DATAKIT or This is the destination dialstring for Datakit VCS for all TCP/IP switch types except the polled GTD-5. For the polled ADDRESS GTD-5, this is the “converter_interface_card_name” followed by 3 colon-separated TCP/IP port numbers representing respectively: discrete control channel, 5- minute data channel, audit/scheduling channel. ISSUE (DMS 250 and DMS 500 only) • issue1 — FEP will communicate with the DMS 250 and DMS 500 using the FEP release 3 and prior interface • issue2 — FEP will communicate with the DMS 250 and DMS 500 using the TR-740 compliant interface
...... 190-406-737 Alcatel-Lucent — Internal 4-33 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
...... 4-34 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
5 Link Administration
Overview
Purpose This chapter provides procedures and background information related to administering links.
This chapter contains the following topics:
Overview of FEP-NTM links 5-2
Connecting a FEP to NTM 5-3
Disconnecting a FEP from NTM 5-4
Checking the FEP-NTM link status 5-5
Creating the FEP-NTM link 5-7
Deleting the FEP-NTM link 5-9
Activating the FEP-NTM link 5-11
Deactivating the FEP-NTM link 5-13
Testing the FEP-NTM link 5-15
Reestablishing FEP-Datakit links 5-17
...... 190-406-737 Alcatel-Lucent — Internal 5-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Overview of FEP-NTM links
Diagram Figure 5-1 provides an overview of how the FEP is connected to an NTM.
Figure 5-1 Connecting your FEP to NTM
For the FEP-switch version of Figure 5-1, see Figure 4-1, “Connecting a switch to your FEP” (p. 4-3) and “Connecting a switch to your FEP” (p. 4-5). That procedure is independent from the procedure below. That is, either procedure can be done before the other.
Note: All references to “FEP-NTM” links could equally be termed “NTM-FEP” links. We are not implying direction.
...... 5-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Connecting a FEP to NTM
Instructions Follow these steps:
......
1 Physically connect your FEP to the NTM machine.
Responsibility: Network administrators
Reference: Appendix B, “Datakit VCS Settings”
......
2 Create the FEP-NTM link — that is, define it in the FEP.
Responsibility: You
Reference: “Creating the FEP-NTM link” (p. 5-7)
......
3 Activate the link — that is, tell the FEP to allow communication between itself and the NTM machine you name.
Responsibility: You
Reference: “Activating the FEP-NTM link” (p. 5-11)
......
4 Add the link to NTM. (You can do Steps 2 and 3 after this step.)
Responsibility: NTM administrators
Reference: “Adding a DCC” (p. 13) in the System Administration Guide
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 5-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Disconnecting a FEP from NTM
Instructions Follow these steps:
......
1 Remove the link from NTM. (You can do Steps 2 and 3 before this step.)
Responsibility: NTM administrators
Reference: “Removing a DCC” (p. 23) in the System Administration Guide
......
2 Deactivate the link — that is, tell the FEP to stop communicating with NTM.
Responsibility: You
Reference: “Deactivating the FEP-NTM link” (p. 5-13)
......
3 Delete the FEP-NTM link — that is, remove it from the FEP.
Responsibility: You
Reference: “Deleting the FEP-NTM link” (p. 5-9)
......
4 If needed, remove physical connections between your FEP and the NTM machine.
Responsibility: Network administrators
Reference: Appendix B, “Datakit VCS Settings”
...... E ND OF STEPS ......
...... 5-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Checking the FEP-NTM link status
Purpose Use this procedure to determine the status of FEP-NTM links. This link is a TCP/IP connection between a FEP computer and an NTM computer.
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter: rsnlink all Result: Output appears, as illustrated in Figure 5-2.
...... E ND OF STEPS ......
Checking the FEP-NTM link status output Figure 5-2 shows four links of which three are active and two are up. This is not what you would normally see, but it is shown here so that you can see each of the different possibilities available. It is possible that you might define more than one NTM link. Even then, it would be unlikely that you would define more than two links.
Figure 5-2 “rsnlink” output example NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK ------cop1ntms 0 ACTIVE A A A A TCP/IP cop2ntms 1 OFF I I I I cop3ntms 2 ACTIVE I I I I cop4ntms 3 ACTIVE A A A A TCP/IP
Two NTMs, one link each This setup indicates that your NTM has one of the Backup and Disaster Recovery (BDR) features — Feature 8, “Disaster Recovery (Duplex)”and Feature 40, “Enhanced Disaster Recovery”. With those features, if the active link goes bad, NTM would use the backup link. Both the active and backup links would have to be activated on your FEP so that
...... 190-406-737 Alcatel-Lucent — Internal 5-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NTM could switch without manual FEP intervention. The NTM BDR feature is documented in Chapter 12, “BDR Administration on a Host” of the System Administration Guide. rsnlink output fields/descriptions Table 5-1 provides descriptions for the output fields from the rsnlink command. Table 5-1 “rsnlink” Output Fields/Descriptions Output Field Description NTMOS NAME The name of an NTM machine. This name came from NTM. That is, if you called an NTM administrator, and asked him or her to enter hostname on the NTM console, this is the machine name that they would see. NUMBER A number used in place of the NTM name when entering commands such as rsnlink. You assign this number in “Creating the FEP-NTM link” (p. 5-7). This is NOT known to the NTM administrators. STATUS This can be: • ACTIVE. Someone has activated the FEP-NTM link (using anlink). • OFF. Someone has deactivated the FEP-NTM link (using deanlink), or else the link has never been activated. DISCRETE, AUD, These are the different channels in the link between the FEP and NTM, each CONTROL, 5 MINUTE channel carrying a different type of data. Each channel is either “I” (inactive) or “A” (active). This relates to the “STATUS” column, as follows: • If “STATUS” is “OFF”, these channels will all be “I” (inactive). • If “STATUS” is “ACTIVE”, these channels will usually be “A” (active), although you may sometimes see them temporarily “I” (inactive). NETWORK This can be: • TCP/IP if connectivity is up via a TCP/IP protocol. • UNKNOWN if the link is up and the network type is not able to be determined. • blank, if no channels (Discrete, Aud, Control, 5 minute) are up on the specified link. This will be so whether the STATUS is ACTIVE or OFF.
...... 5-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Creating the FEP-NTM link
Purpose Use this procedure to define this FEP-NTM link in the FEP database. Typically, you would use this after completing initial installation (Chapter 2, “Installing the FEP”).
Instructions Follow these steps:
......
1 Log in as fep.
......
2 Enter: cnlink ntmos name -n location number Where: • ntmos name is the name of a NTM machine. This name came from NTM. That is, if you called a NTM administrator, and asked him or her to enter uuname -l on the NTM console, this is the machine name they would see. • location number is a unique number you choose (range 0-3) which you can use in place of the NTM machine when you are entering commands such as rsnlink. Use any number not yet used (you can use the rsnlink command to see which numbers were used.)
......
3 Enter: cnlink cop2ntms -n <0 to 3> Result: You will see a confirmation message, similar to the following:
NTMOS link cop2ntms successfully created.
......
4 Verify the link has been created. Enter: rsnlink all Result: Output lists all created links, resembling the following:
NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK ------cop1ntms 0 ACTIVE A A A A TCP/IP
...... 190-406-737 Alcatel-Lucent — Internal 5-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... cop2ntms 1 OFF I I I I
...... E ND OF STEPS ......
...... 5-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Deleting the FEP-NTM link
Purpose Use this procedure to remove the NTM link from the FEP database. Once you have deleted an NTM link, you cannot “un-delete” it. Instead, you must create it again, using “Creating the FEP-NTM link” (p. 5-7).
Instructions Follow these steps:
......
1 Log in as fep.
......
2 List all links. Enter: rsnlink all Result: Output lists all created links, resembling the following:
NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK ------cop1ntms 0 ACTIVE A A A A TCP/IP cop2ntms 1 OFF I I I I Reference: “Checking the FEP-NTM link status” (p. 5-5) If the link is listed as “ACTIVE”, deactivate it.
Reference: “Deactivating the FEP-NTM link” (p. 5-13)
Example: deanlink cop1ntms
......
3 Enter: delnlink ntmos name Result: You will see the following prompt:
NTMOS Link ‘cop2ntms’ will be deleted. Are you sure? (y or n) _ Enter y to delete the link.
Result: You will see a confirmation message, similar to this:
NTMOS Link ‘cop2ntms’ was deleted.
...... 190-406-737 Alcatel-Lucent — Internal 5-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
4 Verify the link has been deleted. Enter: rsnlink all Result: Output lists all created links, resembling the following:
NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK ------cop1ntms 0 ACTIVE A A A A TCP/IP
...... E ND OF STEPS ......
...... 5-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Activating the FEP-NTM link
Purpose Use this procedure to give the NTM machine specified permission to connect to this FEP so that data can be sent over the link.
Instructions Follow these steps:
......
1 Log in as fep.
......
2 List all links. Enter: rsnlink all Result: Output lists all created links, resembling the following:
NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK ------cop1ntms 0 ACTIVE A A A A TCP/IP cop2ntms 1 OFF I I I I Reference: “Checking the FEP-NTM link status” (p. 5-5) Note the name (such as “cop2ntms”) and note whether the link is “ACTIVE” or “OFF”. If the link is not listed, you cannot activate it, so you cannot continue with this procedure. (To create a link, use “Creating the FEP-NTM link” (p. 5-7).)
......
3 Enter the following command, using the “NTMOS NAME” of an inactive (“OFF”) link listed in Step 2. Example: anlink cop2ntms Result: A message is displayed similar to the following:
NTMOS link is activated - cop2ntms ......
4 Verify the link has been activated. Enter: rsnlink all Result: Output lists all created links, resembling the following:
NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK ------
...... 190-406-737 Alcatel-Lucent — Internal 5-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... cop1ntms 0 ACTIVE A A A A TCP/IP cop2ntms 2 ACTIVE I I I I
...... E ND OF STEPS ......
...... 5-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Deactivating the FEP-NTM link
Purpose Use this procedure to closes the link between FEP and the NTM machine so that data cannot be sent over the link. To reactivate the link, use the anlink command. Reference: “Activating the FEP-NTM link” (p. 5-11)
Instructions Follow these steps:
......
1 Log in as fep.
......
2 List all links. Enter: rsnlink all Result: Output lists all created links, resembling the following:
NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK ------cop1ntms 0 ACTIVE A A A A TCP/IP cop2ntms 1 OFF I I I I Reference: “Checking the FEP-NTM link status” (p. 5-5) Note the name (such as “cop2ntms”) and whether the link is “ACTIVE” or “OFF”.
......
3 Enter the following command, using the “NTMOS NAME” of an “ACTIVE” link listed in Step 2. Example: deanlink cop2ntms Result: A message is displayed similar to the following:
NTMOS link is deactivated - cop2ntms ......
4 Verify the link has been deactivated. Enter: rsnlink all Result: Output lists all created links, resembling the following:
NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK
...... 190-406-737 Alcatel-Lucent — Internal 5-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... ------cop1ntms 0 ACTIVE A A A A TCP/IP cop2ntms 1 OFF I I I I
...... E ND OF STEPS ......
...... 5-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Testing the FEP-NTM link
Purpose Use this procedure to send a test message to the NTM console.
Instructions Follow these steps:
......
1 Log in as fep.
......
2 List all links. Enter: rsnlink all Result: Output lists all created links, resembling the following:
NTMOS NAME NUMBER STATUS DISCRETE AUD CONTROL 5 MINUTE NETWORK ------cop1ntms 0 ACTIVE A A A A TCP/IP cop2ntms 1 OFF I I I I Reference: “Checking the FEP-NTM link status” (p. 5-5) Note the name (such as “cop1ntms”) and note whether the link is “ACTIVE” or “OFF”. If the link is not listed, you cannot test it, so you cannot continue with this procedure. (To create a link, use “Creating the FEP-NTM link” (p. 5-7).)
......
3 If the link is “OFF”, you cannot test it. In that case, either stop here, or activate it, by using the FEP command anlink. Reference: “Activating the FEP-NTM link” (p. 5-11)
Example: anlink cop2ntms
......
4 Test the link. Enter: tnlink ntmos link name
Example: tnlink cop1ntms Result: You will receive a prompt, similar to the following:
Enter test message for cop1ntms:
...... 190-406-737 Alcatel-Lucent — Internal 5-15 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
5 Enter anything, such as: This is test of link cop1ntms at 12:52 p.m......
6 Contact an NTM system administrator at that console to ensure the message was received. (If it was not, ask the administrator if he or she has remembered to activate the NTM link to your FEP.)
......
7 To exit the test, enter Ctrl - D.
...... E ND OF STEPS ......
...... 5-16 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Reestablishing FEP-Datakit links
Background If someone stops the Datakit VCS, your Datakit administrator must restart Datakit VCS. You will find three problems remaining: 1. You can log in only at the FEP console. 2. The FEP cannot send network element data to NTM for offices that are connected to the FEP through Datakit. 3. The FEP cannot collect network element data from any offices that are connected to the FEP through Datakit. To correct these problems, reintroduce the FEP to Datakit VCS, using the following procedure.
Instructions Follow these steps:
......
1 Log in as root on the system console.
......
2 Enter: /etc/init.d/dkitrc stop /etc/init.d/dkitrc start ......
3 From a remote terminal, log in to the FEP (using the dkcu command to reach the FEP). You can log in as fep or anything else.
......
4 If your remote login was successful, STOP. YOU HAVE COMPLETED THIS PROCEDURE. If your login failed, or there are other problems, continue with the next step.
......
5 Log in as root at the system console and enter: stopfep Reference: “Starting the FEP software” (p. 3-33)
...... 190-406-737 Alcatel-Lucent — Internal 5-17 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
6 Reboot the Solaris operating system. Enter: reboot ......
7 After reboot finishes, log in again. You will not need to restart the FEP application software — that happens automatically with reboot.
...... E ND OF STEPS ......
...... 5-18 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
6 AISwitch Configuration
Overview
Purpose This chapter details AISwitch 180 connections and configuration, as well as how to add and/or monitor an AISwitch 180.
This chapter contains the following topics:
Introduction 6-2
Tips on navigating through the AISwitch menu 6-3
Configuring the AISwitch 6-4
Configuring the AI296 Smart Line Cards 6-7
Configuring the links for the AI296 Smart Line Cards 6-10
Adding a new switch to the AISwitch 6-15
Deleting a switch from the AISwitch 6-20
Port–to–Link Mapping (SVC) 6-22
Monitoring the AISwitch for troubleshooting purposes 6-29
Copying the AI configuration onto the FEP 6-31
Recovering the AI configuration file from the FEP 6-33
...... 190-406-737 Alcatel-Lucent — Internal 6-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Introduction
Overview For the polled GTD-5 switch type on generic gtd4003, the FEP will connect via TCP/IP through the AISwitch 180. The AISwitch 180 receives polls from the FEP using TCP/IP and converts it into X25 packets. Conversely, the AISwitch 180 receives responses from the GTD-5 as X25 packets and forwards the data using TCP/IP back to the FEP. The FEP polls for binary data using an LSSGR-like interface. The FEP’s poll is received by a General Processing Unit (GPU) connected to the actual GTD-5 switch. GTD-5 data collection via TCP/IP is only available if Feature 257, “FEP Release 5” is installed and the GTD-5 switch has been defined on generic gtd4003 or later.
Initial connection to the AISwitch 180 When you first get the AISwitch 180, the only way you can get into it is via the craft port. After you have configured the AISwitch 180 and set up the name, you can telnet to the AISwitch 180 instead. Connecting a terminal or PC to the AISwitch 180 requires a null modem or null modem cable. In a null modem cable, pins 2 and 3 are reversed on one end. A dumb terminal or any computer running terminal emulation software can be connected to the craft port of the AISwitch 180. Communications with the craft port must be set to 8 bits per character, no parity, 1 stop bit, and 9600 baud. The craft port also responds to XON/XOFF flow control. The craft port should be port 256 on the system. The screen prompt will refer to it as the craft port. 9600 BPS 8 Data Bits 1 Stop Bit NO Parity Bit
References See the “AISwitch Series” chapter of the AISwitch Hardware Manual for more information. This information is also available at http://aiinet.com/documents/Manuals.asp.
...... 6-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Tips on navigating through the AISwitch menu
Overview In the AI menu system, the following rules apply: • A number followed by a description means you can enter that number followed by a space and a value to set that parameter. • A number followed by a “+” and a description means there is a submenu. • A number followed by an “*” and a description means you can toggle through the allowable settings by repeatedly entering the number and carriage return. • Any changes made in sub-menus are never fully saved until you save at each menu above it until reaching the main menu.
...... 190-406-737 Alcatel-Lucent — Internal 6-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Configuring the AISwitch
Purpose Use the following procedure to set up the TCP/IP address and AISwitch name so that you can telnet to the switch.
Before you begin Have your network administrator define a TCP/IP address for the AISwitch (that is, the AI198 controller board) and each converter interface card (that is, each AI296 smart line card). You will also need to know the router address and subnet mask for the AISwitch.
Note: Use this procedure so that you are able to simply telnet to the AISwitch 180 (i.e. the AI198 board).
Instructions Follow these steps:
......
1 Connect to the AISwitch.
Reference: “Initial connection to the AISwitch 180” (p. 6-2)
......
2 Enter menu and the Main Menu is displayed. 01+Configure options affecting the system as a whole 02+Create, delete, or modify a destination name 03+Display all destination names 04+Configure cards 05+Set or remove connection restrictions based on port numbers 06+Display all connection restrictions 07+Configure slot density 08+Configure the alias translation table 09+Display the list of alias translation entries
21 Exit the configuration menu system Enter item number and optional ",value" then push
3 At the Main Menu, enter 1.
...... 6-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
4 Enter 12 to advance to the “Network Parameters” menu.
......
5 Enter 1 and the TCP/IP address of the AISwitch.
......
6 Enter 2 and the Router address.
......
7 Enter 3 and the Subnet mask.
......
8 Enter 4 and add the telnet server port number 23
......
9 Enter 5 and add the ftp server control port number 21
......
10 Enter 20 to save the changes.
......
11 Enter 20 again to return to the Main Menu.
......
12 Enter 21 to exit the menu system.
......
13 Enter menu and the Main Menu is displayed. 01+Configure options affecting the system as a whole 02+Create, delete, or modify a destination name 03+Display all destination names 04+Configure cards 05+Set or remove connection restrictions based on port numbers 06+Display all connection restrictions 07+Configure slot density 08+Configure the alias translation table 09+Display the list of alias translation entries
21 Exit the configuration menu system Enter item number and optional ",value" then push
...... 190-406-737 Alcatel-Lucent — Internal 6-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
14 At the Main Menu, enter 1. The following menu should be displayed: 01+Set log and alarm thresholds 02*The display of connection information on user terminals is turned------ON 03 The duration of a long break sequence in 1/64 seconds------0000000120 04*The automatic baud rate detection system is turned------ON 05*Printing of a destination name menu on user terminals is turned------ON 06*Allow ports of different speeds to be connected (down speed)------ON 07 The designator for this node is------ai180a<10><13> 08*Allow dual CPUs to automatically switch if fault------ON 09+AISwitch automatic commands 10*The display of destination names in four columns is turned------OFF 11*Automatic CLC update is------OFF 12+Network parameters 13+Time and Date format is hh:mm:ss mmddyy 14+SNMP Trap Table 15+Configure Banner
20 Save the changes made 21 Exit this menu with no changes Enter item number and optional ",value" then push
15 Enter 7
......
16 Enter 20 to save the changes.
......
17 Enter 21 to exit the menu system.
......
18 Reboot the AISwitch by pressing the “boot” button as shown in the AISwitch Hardware Manual or by entering the reset command at the AI system prompt.
...... E ND OF STEPS ......
...... 6-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Configuring the AI296 Smart Line Cards
Purpose Use this procedure to configure the AI296 Smart Line Cards.
Instructions Follow these steps:
......
1 Telnet to the AI198 Controller board and call up the AI198 menu system. Enter: telnet
2 Log in as ai. Reference: See the “System Configuration by Menu” chapter of the AI198 System Manager/User’s Manual for information on menu navigation and menu descriptions.
......
3 Enter menu and the Main Menu is displayed. 01+Configure options affecting the system as a whole 02+Create, delete, or modify a destination name 03+Display all destination names 04+Configure cards 05+Set or remove connection restrictions based on port numbers 06+Display all connection restrictions 07+Configure slot density 08+Configure the alias translation table 09+Display the list of alias translation entries
21 Exit the configuration menu system Enter item number and optional ",value" then push
4 At the Main Menu, enter 4 to advance to the “Configure cards” menu.
......
5 Enter baseport of the card to edit; enter 1 0 for the first AI296 card, 1 16 if you have a second AI296 card and 1 32 if you have three AI296 cards.
...... 190-406-737 Alcatel-Lucent — Internal 6-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
6 Enter 2 to advance to the “Configure as AI296 network interface card” menu.
......
7 Enter 11 to advance to the “Configure as AI296 network interface card” menu. The following menu should be displayed: Menu 4.2.11 01 IP Address (0.0.0.1 - 255.255.255.254)------135.007.029.022 02 IP Address Range (1 - 255)------001 03 IP Subnet Mask (0.0.0.1 - 255.255.255.254) ------255.255.255.000 04 Primary IP Router Address (0.0.0.0 - 255.255.255.254) ------135.007.029.254 05 Secondary IP Router Address (0.0.0.0 - 255.255.255.254) ----- 000.000.000.000 06*TCP Default Window Size (200, 512, 1024, 2048)------2048 07*TCP Send Ahead------ON 08+SNMP System Parameters 09*Bring passive link down when all calls have cleared------OFF 10 Passive link Standby Mode timer------0000060 11 Passive link Stay Inactive timer------0000025 12+X.25 Link Setup 13+Async Link Setup 14+IP Over X.25 Subnets 15+IP Static Routes 16 Telnet port number (1..65534)------00023
20 Retain these changes for saving in Menu 4 21 Exit this menu with no changes Enter item number and optional ",value" then push
8 At the menu, enter 1 and the TCP/IP address of the AISwitch.
...... 6-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
9 Enter 3 and the Subnet mask.
......
10 Enter 4 and the router address.
......
11 Enter 20 to save the changes.
......
12 Enter 21 to exit the menu system.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 6-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Configuring the links for the AI296 Smart Line Cards
Purpose Use this procedure to configure the links for the AI296 Smart Line Cards.
Instructions Follow these steps:
......
1 Telnet to the AI198 Controller board and call up the AI198 menu system. Enter: telnet
2 Log in as ai. Reference: See the “System Configuration by Menu” chapter of the AI198 System Manager/User’s Manual for information on menu navigation and menu descriptions.
......
3 Enter menu and the Main Menu is displayed. 01+Configure options affecting the system as a whole 02+Create, delete, or modify a destination name 03+Display all destination names 04+Configure cards 05+Set or remove connection restrictions based on port numbers 06+Display all connection restrictions 07+Configure slot density 08+Configure the alias translation table 09+Display the list of alias translation entries
21 Exit the configuration menu system Enter item number and optional ",value" then push
4 Configure each of the AI296 cards. • Select 4 to advance to “Configure cards” menu. • Enter baseport of the card to edit; enter 1 0 for the first AI296 card, 1 16 if you have a second AI296 card and 1 32 if you have three AI296 cards. • Enter 2 to advance to “Configure as AI296 network interface card” menu
...... 6-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
• Enter 11 to advance to “Configure as AI296 network interface card” menu • Enter 12 to advance to “X25 Link Setup” Result: You should now be at the following menu:
Menu 4.2.11.12 01 Link number (1-16)------01 02*Link Type (Async, X25)------X.25 03 Link description------04*Link state (Enabled, Disabled)------Enabled 05*Link mode (Normal, Passive, Extended)------Normal 06 Port speed (0 - 128000 bps, 0 is external clocking)------056000 07+X25 LAPB Parameters 08+X25 Parameters 09+Virtual Circuits 10*Hardware Interface (RS232,RS530,V.35)------V.35
20 Save the changes made 21 Exit this menu with no changes Enter item number and optional ",value" then push
5 Enter 1 followed by the link number to enter each link on the AI296 card’s data
......
6 Enter 2, Link Type (Async, X25), until you see X25 on the right hand side of that line.
......
7 Enter 4, Link state (Enabled, Disabled), until you see Enabled
......
8 Enter 5, Link mode (Normal, Passive, Extended), until you see Normal
......
9 Enter 6, Port speed (0-128000 bps, 0 is external clocking) and the correct speed, probably 56000.
...... 190-406-737 Alcatel-Lucent — Internal 6-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
10 Enter 7 to advance to “X25 LAPB Parameters” (most of these defaults should apply, only item 1, interface mode may need to be changed). Menu 4.2.11.12.7 01*Interface mode (DTE or DCE)------DTE 02*Frame level disconnect (Active, Passive, Other)------Active 03 Frame Window size (1 - 7)------7 04 N2 retry count (0 - 255)------020 05 T1 ack timer (1 - 25500 ms)------03000 06 T2 ack delay timer (1 - 25500 ms)------00400 07 T4 idle timer (0 - 200000 ms)------025000
20 Save the changes made 21 Exit this menu with no changes Enter item number and optional ",value" then push
11 Enter 20 to save changes
......
12 Enter 8 to advance to “X25 Parameters” (again most of these defaults should apply). Menu 4.2.11.12.8 01*X25 Facilities negotiation------OFF 02*Max packet size (128, 256, 512)------256 03 Packet window size (1-7)------007 04 X121 local address (0-15 decimal digits)------05 T20 restart timer (0-3200000ms)------0180000 06 T21 call timer (0-3200000ms)------0200000 07 T22 reset timer (0-3200000ms)------0010000
...... 6-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... 08 T23 clear timer (0-3200000ms)------0180000 09 T24 window timer (0-3200000ms)------0075000 10 T25 data retransmission timer (0-3200000ms)------0150000 11 T26 interrupt timer (0-3200000ms)------0180000 12 T28 registration timer (0-3200000ms)------0180000 13 R20 restart count (0 - 255)------001 14 R22 reset transmission count (0 - 255)------001 15 R23 clear retransmission count (0 - 255)------001 16 R28 registration retransmission count (0 - 255)------001 17*Protocol version (1980, 1984, 1988)------1984
20 Save the changes made 21 Exit this menu with no changes Enter item number and optional ",value" then push
13 Enter 20 to save changes
......
14 Enter 9 to advance to “Virtual Circuits” (enter information based on your setup, Permanent Virtual Circuit (PVC) or Switched Virtual Circuit (SVC): if it is PVC, enter information in 1 and 2; if it is SVC, enter 3-8 for whatever applies to you). Menu 4.2.11.12.9 01 Number of PVCs (0 - 1024)------0300 02+PVC configuration 03 Incoming only SVC low (0 - 4095)------0000 04 Incoming only SVC high (0 - 4095)------0000 05 Two-way SVC low (0 - 4095)------0000 06 Two-way SVC high (0 - 4095)------0000
...... 190-406-737 Alcatel-Lucent — Internal 6-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... 07 Outgoing only SVC low (0 - 4095)------0000 08 Outgoing only SVC high (0 - 4095)------0000
20 Save the changes made 21 Exit this menu with no changes Enter item number and optional ",value" then push
15 Enter 20 to save changes
......
16 Enter 10, Hardware interface (RS232, RS530, V.35), until you see the correct interface, probably V.35.
......
17 Enter 20. Repeat until you are back at the main menu.
......
18 Enter 21 to exit the menu system.
......
19 Reboot the AISwitch by pressing the “boot” button as shown in the AISwitch Hardware Manual or by entering the reset command at the AI system prompt.
...... E ND OF STEPS ......
...... 6-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Adding a new switch to the AISwitch
Purpose Use the following procedure to add and configure a new switch. See the AI (Applied Innovation’s) Web Site at: http://www.aiinet.com/ for more information on the AI switch and “Creating a switch” (p. 4-25) to add a switch to FEP.
Before you begin You need to know if your switch connection is SVC or PVC. This information will be used in Step 6 of this procedure.
Instructions Follow these steps:
......
1 Telnet to the AI198 Controller board and call up the AI198 menu system. Enter: telnet
2 Log in as ai. Bring up the menu system, enter: menu Reference: See the “System Configuration by Menu” chapter of the AI198 System Manager/User’s Manual for information on menu navigation and menu descriptions.
......
3 From the Main Menu, enter 8 to advance to the alias translation table
......
4 Enter 17 to display the first entry in the alias translation table. (If you get an alias name filled with all asterisks, start entering your aliases here; otherwise enter 18)
......
5 Enter 18 to display the second entry in the alias translation table. Continue entering 18 until you get an alias name filled with all asterisks. Then you can begin entering your aliases.
...... 190-406-737 Alcatel-Lucent — Internal 6-15 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... If your switch connection is SVC, follow Step 6 to Step 12. If it is PVC, follow Step 13 to Step 25.
......
6 Enter 1 followed by the TCP/IP address of the AI296 card, followed by the port number set up for this office on your FEP machine (all 3 logical port numbers used by each office need to be set up). This can be determined by referring to Table 6-1, “Port to X25 Link Mapping (SVC Example Setup)” (p. 6-22)
......
7 Enter 2 and 4 until you see it set to SLC routing translation.
......
8 Enter 4 followed by X25 followed by the values 1-48, (which is the [A] value used when you set up your office on the FEP machine, the AI296 interface board number, ranging from 1-3, multiplied by the AI296 link number, ranging from 1-16), and then this should be followed by the X.121 address for that office (where all 3 logical port numbers for this office should all have the same X.121 address)i.e. 4 X25.2.7409747629
......
9 Enter 7 and add the AISwitch caller’s address.
......
10 Enter 10 =””
......
11 Enter 11 AEPN. Result: If Steps 5-9 are done correctly, you should see something like the following for port 2001. (Identical entries need to be set up for ports 2002 and 2003 as well)
Menu 8 01 Alias name ------135.7.29.22#2001 02+SLC routing translation 03 Destination - 04 Called address ------X25.2.7409747629 05 This alias is visible in the destination menu------YES 06 Link number is (1..16) - 07 Caller’s address - 08 Call data - 09 App. string -
...... 6-16 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... 10 Called protocol ------="" 11 Caller’s protocol ------AEPN 12 Alternate routing alias -
16+Test macros 17 Show the first entry in the alias translation table 18 Show the next entry in the alias translation table 19+Delete the above alias translation entry 20 Save the changes made 21 Exit this menu with no changes Enter item number and optional ",value" then push
12 Enter 20 after each alias to save the changes.
If your switch is PVC, follow Step 13 to Step 18 to create the first alias and Step 20 to Step 25 to create a second alias entry for call data.
......
13 Enter 1 followed by the TCP/IP address of the AI296 card, followed by the port number set up for this office on your FEP machine (all 3 logical port numbers used by each office need to be set up).
......
14 Enter 2 and 4 until you see it set to SLC routing translation.
......
15 Enter 4 and PVC
......
16 Enter 8. At the menu, enter call data, enter format: (baseport #=0,16,32) x25.
......
17 Enter 10 =””
......
18 Enter 11 AEPN
......
19 Enter 20 to save the alias ...... 190-406-737 Alcatel-Lucent — Internal 6-17 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
20 Enter 1 (whatever you entered in Step 16 alone and enter 0.X25.1.1)
......
21 Enter 2 (same as above)
......
22 Enter 4 (enter destination IP address (called address); enter format: TCP/IP address of destination #, port # i.e. 135.7.29.22#1001
......
23 Enter 10 AEPN
......
24 Enter 11 =””
......
25 Enter 20 to save the alias
......
26 Enter 21 to return to the main menu.
......
27 Enter 9 to advance to “Display the list of alias translation entries” from the main menu as a summary view of your changes.
Result: The output should show the added values like the following:
Menu 9 01 The following alias translation entries have been defined
Alias Destination Visible Trans. Calling String Type 135.7.29.22#1001 Y 8 X25.1.6302456 135.7.29.22#1002 Y 8 X25.1.6302456 135.7.29.22#1003 Y 8 X25.1.6302456 135.7.29.22#2001 Y 8 X25.2.7409747629 135.7.29.22#2002 Y 8 X25.2.7409747629 135.7.29.22#2003 Y 8 X25.2.7409747629
...... 6-18 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Enter item number and optional ",value" then push
28 Enter 21 to exit the main menu.
......
29 Enter bye to exit or terminate the telnet session.
......
30 Reboot the AISwitch by pressing the “boot” button as shown in the AISwitch Hardware Manual or by entering the reset command at the AI system prompt.
......
31 Now save the AISwitch configuration file to the FEP.
Reference: “Copying the AI configuration onto the FEP” (p. 6-31)
......
32 Add the switch to the FEP Feature Set.
Reference: “Creating a switch” (p. 4-25)
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 6-19 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Deleting a switch from the AISwitch
Purpose Use this procedure to delete a switch from the AISwitch.
Reference: See the AI (Applied Innovation’s) Web Site at: http://www.aiinet.com/ for more information on the AI switch and “Deleting a switch” (p. 4-27) to delete a switch from the AISwitch.
Instructions Follow these steps:
......
1 Delete the switch to the FEP Feature Set.
Reference: “Deleting a switch” (p. 4-27)
......
2 Telnet to the AI198 Controller board and call up the AI198 menu system. Enter: telnet
3 Log in as ai. Bring up the menu system, enter: menu Reference: See the “System Configuration by Menu” chapter of the AI198 System Manager/User’s Manual for information on menu navigation and menu descriptions.
......
4 From the Main Menu, enter 8 to advance to the alias translation table
......
5 Display the first entry in the alias translation table. Enter: 17 ......
6 Enter 18 to display each alias in the alias translation table until you find the aliases you wish to delete. Each switch requires 3 aliases. When you find the first alias to delete, enter 19. Enter 18 again to find the second alias to delete. Once you find it, enter 19. Keep entering 18 until you find the third and final alias to delete for this switch. Enter 19. Enter 20 to save your changes.
...... 6-20 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
7 Enter 9 to advance to “Display the list of alias translation entries” from the main menu as a summary view of your changes.
Result: The output should not show the deleted values like the following:
Menu 9 01 The following alias translation entries have been defined
Alias Destination Visible Trans. Calling String Type 135.7.29.22#1001 Y 8 X25.1.6302456 135.7.29.22#1002 Y 8 X25.1.6302456 135.7.29.22#1003 Y 8 X25.1.6302456 135.7.29.22#2001 Y 8 X25.2.7409747629 135.7.29.22#2002 Y 8 X25.2.7409747629 135.7.29.22#2003 Y 8 X25.2.7409747629
8 Enter 21 to return to the main menu.
......
9 Enter 21 to exit the main menu.
......
10 Enter bye to exit or terminate the telnet session.
......
11 Reboot the AISwitch by pressing the “boot” button as shown in the AISwitch Hardware Manual or by entering the reset command at the AI system prompt.
......
12 Now save the AISwitch configuration file to the FEP.
Reference: “Copying the AI configuration onto the FEP” (p. 6-31)
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal 6-21 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Port–to–Link Mapping (SVC)
Overview The FEP uses the AISwitch 180 to handle protocol conversion between TCP/IP and X25. The AISwitch 180 has a 10BaseT Ethernet port and can have up to three AI296 interface cards. Each interface card has 16 V.35 links connected to an X25 PDN using V.35 cables. Thus, an AISwitch 180 could have up to 48 links on it. 16 offices will be multiplexed onto 1 link. Thus, 7 links will be used on one AI296 card to support 100 polled GTD-5 switches.
Table The information in Table 6-1 allows you to map an AI link number, a TCP/IP address and port, and an X25 address. When you are doing port-to-link mapping, remember the following: • The
Note: We recommend defining 16 offices per link. Since 100 offices may be supported on a single AI box, 6 links will be fully configured with 16 offices on it (16 offices x 6 = 96 offices) and the 7th link will be configured with 4 offices on it. Table 6-1 Port to X25 Link Mapping (SVC Example Setup) (Sheet 1 of 5) AI Link Number TCP/IP Address and Port X25 Address Link#1(Office 1-16) Board 1 starts here
1st office
1st office
1st office
2nd office
2nd office
2nd office
...... 6-22 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Table 6-1 Port to X25 Link Mapping (SVC Example Setup) (Sheet 2 of 5) AI Link Number TCP/IP Address and Port X25 Address
16th office
16th office
16th office
17th office
17th office
17th office
18th office
18th office
18th office
32nd office
32nd office
32nd office
33rd office
33rd office
33rd office
34th office
34th office
34th office
48th office
48th office
48th office
...... 190-406-737 Alcatel-Lucent — Internal 6-23 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table 6-1 Port to X25 Link Mapping (SVC Example Setup) (Sheet 3 of 5) AI Link Number TCP/IP Address and Port X25 Address Link#4(Office 49-64)
49th office
64th office
65th office
80th office
81st office
96th office
97th office
100th office
112th office
113th office
128th office
129th office
144th office
...... 6-24 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Table 6-1 Port to X25 Link Mapping (SVC Example Setup) (Sheet 4 of 5) AI Link Number TCP/IP Address and Port X25 Address Link#10(Office 145-160)
145th office
160th office
161st office
176th office
177th office
192nd office
193rd office
208th office
209th office
224th office
225th office
240th office
241st office
...... 190-406-737 Alcatel-Lucent — Internal 6-25 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table 6-1 Port to X25 Link Mapping (SVC Example Setup) (Sheet 5 of 5) AI Link Number TCP/IP Address and Port X25 Address
256th office
Link#33-48 Board 3 starts here
...... 6-26 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Monitoring the AISwitch for troubleshooting purposes
Purpose Use this procedure to monitor communication between the AISwitch and the GTD-5 switch using the AISwitch diag-line tool.
Reference: For more information on AISwitch tools, see the AI (Applied Innovation’s) Web Site at: http://www.aiinet.com/.
Instructions Follow these steps:
......
1 Telnet to the AI296 Interface board on the AISwitch and log in as ai.
......
2 Enter diag-line. Result: Data will start to scroll on the screen.
......
3 Enter d, then enter i while the data is scrolling on the screen. Result: The output will be formatted like this:
02=> 03 DISC p 01=> 01 RR 006 p 01<- 01 RR 000 f 02=> 03 DISC p 02=> 03 DISC p 02=> 03 DISC p The d and i convert some of the data displayed to allow for a better understanding of the data.
......
4 Press the
Note: Never leave a monitoring session up for an extending period of time since only one diag-line can be performed on an interface board at a time.
...... 190-406-737 Alcatel-Lucent — Internal 6-27 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
5 Enter exit to terminate the telnet session.
...... E ND OF STEPS ......
...... 6-28 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Copying the AI configuration onto the FEP
Purpose This procedure is used to ftp to the AI198 card, log in, and get the “active.ee” configuration file. In the event that the AISwitch ever becomes corrupted or must be replaced, its configuration can be recovered if the active.ee file is saved on another machine. Use this procedure whenever you have updated the AISwitch configuration.
Instructions Follow these steps:
......
1 Log in to the FEP connected to this AISwitch as fep.
......
2 Change directory to where the AISwitch configuration file will be stored on the FEP. Enter: cd /usra/tdms/ipndc ......
3 Enter: ftp
......
4 Enter ai in the Name field
......
5 Verify the existence of the “active.ee” file. Enter: ls ......
6 Enter: bin ......
7 Copy the file from the AISwitch to the FEP. Enter: get active.ee
...... 190-406-737 Alcatel-Lucent — Internal 6-29 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
8 Enter: quit Result: You are now back on the FEP.
......
9 Verify the existence of the “active.ee” file under /usra/tdms/ipndc. To check the timestamp, enter: ls -l
...... E ND OF STEPS ......
...... 6-30 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Recovering the AI configuration file from the FEP
Purpose Use this procedure to recover the AI configuration file from the FEP.
Instructions Follow these steps:
......
1 Log in to the FEP connected to this AISwitch as user fep.
......
2 Change directory to where the AISwitch configuration file will be stored on the FEP. Enter: cd /usra/tdms/ipndc ......
3 Enter: ftp
......
4 Enter ai in the Name field (
......
5 Enter: bin ......
6 Copy the file from FEP to the AISwitch. Enter: put active.ee ......
7 Verify the existence of the “active.ee” file.
......
8 Enter: quit
...... 190-406-737 Alcatel-Lucent — Internal 6-31 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: You are now back on the FEP.
...... E ND OF STEPS ......
...... 6-32 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
A FEP Manual Pages
Overview
Purpose Information contained on the online manual pages is reproduced in this appendix for easy access. In addition to the information provided in this appendix, manual pages also include copyright and date-last-changed information for each command. Headings, such as NOTES, that do not include information in the manual pages have been omitted from this appendix. These pages explain a set of commands designed to be used by the FEP system administrator. You can call up each manual page by typing man command.
Example: man aentity
BaseWorX commands The appstat and logCat commands are the only BaseWorx commands in this appendix. All other commands are FEP commands.
This appendix contains the following topics:
aentity A-3
anlink A-4
appstat A-5
bdr_act A-7
bdr_commit A-8
bdr_deact A-10
bdr_stat A-11
...... 190-406-737 Alcatel-Lucent — Internal A-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
bdr_takeover A-12
centity A-13
chentity A-17
cnlink A-21
ddbkup_fep A-22
ddrstr_fep A-24
deaentity A-27
deanlink A-28
delentity A-29
delnlink A-31
fsbackup_fep A-32
fsrestore_fep A-34
load_fep A-36
logCat A-37
prtsint A-41
rsentity A-42
rsnlink A-44
startfep A-46
stopfep A-47
tlentity A-48
tnlink A-53
...... A-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... aentity
Description The aentity (activate entity) command activates the link to the named entity. This starts data collection from the entity. This command returns an error message if the: • Link has not yet been created • Link is already active • FEP detects a problem connecting to the switch
Syntax aentity {entity_name | entity_number}
Parameters entity_name An 11-character alphanumeric string that matches the name of the entity to which communication is being activated.
entity_numberFor an existing entity. Must be in the range 0-149. This parameter or the entity_name must be the first parameter entered on the command line.
File(s) /usra/tusr/na/entity/entities
Examples aentity tampflxe62h After about 5 seconds, the switch is activated, and you receive a message, similar to the following: Entity ‘tampflxe62h’ activated
References “centity” (p. A-13) “chentity” (p. A-17) “deaentity” (p. A-27) “delentity” (p. A-29) “rsentity” (p. A-42) “tlentity” (p. A-48) “Activating a switch-FEP link” (p. 4-29)
...... 190-406-737 Alcatel-Lucent — Internal A-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... anlink
Description The anlink (activate NTM link) command activates the link to the NTM machine specified by ntmos_link or location_number. It returns an error message if the link has not yet been created or if it cannot communicate with the “nmt” process. The ntmos_link name is an 11-character (or fewer) string that matches the name of an NTM machine to which communication is being activated.
Syntax anlink {ntmos_link | location_number}
Parameters ntmos_link An 11-character (or fewer) string that matches the name of an NTM machine to which communication is being activated.
location_numberA unique number in the range 0–3
File(s) /usra/tdms/nmt/ntmsinfo
Examples anlink cop2ntms Almost immediately, the link is activated and you receive a message similar to the following: NTMOS link is activated - cop2ntms
References “cnlink” (p. A-21) “deanlink” (p. A-28) “delnlink” (p. A-31) “rsnlink” (p. A-44) “tnlink” (p. A-53) “Activating the FEP-NTM link” (p. 5-11)
...... A-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... appstat
Description The purpose of the appstat (application status for execution state and tracing status) command is to allow the user to get a quick status of the running application. The information presented to the user via this command includes information related to the application that is BaseWorX specific. The information includes daemons and server status information.
Syntax appstat roam appstat Reference: “Checking application status” (p. 3-30)
Note: This is a BaseWorX command.
Detailed description The daemon information includes: • The daemon tag name • The process ID of the daemon • The command used to start up the daemon process • The start option used (i.e. Respawn, Once, or Wait) • Whether the daemon was tagged as persistent • How many times the daemon process respawned If the process ID for any daemon is zero, the daemon process is no longer running, but is still displayed in the demonstrate display. This can occur for several reasons. For example, the daemon process may have been respawned the maximum number of times or the daemon may have been tagged as a ONCE or WAIT process and it has either died or run to completion. The RMPID attribute in the daemon configuration file, deconfig(4) suppresses the status display of any daemon if it dies (e.g., has a pid of zero). This same information on daemons is available through the demonstat(1) command. Information about TUXEDO services and clients, including their current tracing and measuring settings, is provided only if your application uses TUXEDO.
...... 190-406-737 Alcatel-Lucent — Internal A-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Environment @APPTAG@ @ROAMCNFG@ @ROAMROOT@ @ROAMUIPATH@
Caveat(s) When clients stop clienting, the TUXEDO bulletin board does not clean up after them for a specified period. Given this, the tracing status displays may be out of sync with reality for a few minutes.
Diagnostics Information related to clients and services is only available in the “Running” run level. If the current run level is “Administrative”, the only information displayed to the user is the information related to daemons. If the current run level is “Shutdown”, the only information displayed is the run level.
Return Value 0 Success 1 Failure
References chexstate(1S), cm_manager(1E), cm_agent(1E), demonstat(1S), em_dwatch(1), roam(1), servcstat(1), servrstat(1), tracestat(1), cmrequest(1)
...... A-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... bdr_act
Syntax bdr_act
Description The bdr_act (activate backup and disaster recovery) command is used to activate backup and disaster recovery (BDR) for the FEP. Before it activates BDR, the bdr_act command verifies that: • A backup FEP is defined • The feature is unlocked • BDR is not running on the backup FEP Once the BDR feature is activated, the bdr activation file is created which is used by the bdr_commit command. If bdr_act has any problems, an error message is displayed to the screen and logged to the bdrlog.
File(s) /usra/fep/etc/bdr_act /usra/fep/etc/bdrfep
References “bdr_commit” (p. A-8) “bdr_deact” (p. A-10) “bdr_takeover” (p. A-12)
...... 190-406-737 Alcatel-Lucent — Internal A-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... bdr_commit
Description The bdr_commit (data file synchronizer for the FEP) command copies all of the files that are contained in the “.bdrfiles” file from the primary FEP to the backup FEP.
Syntax bdr_commit [file_name]
Parameters file_name Name of the file to be committed.
Detailed description The “.bdrfiles” file is provided with the FEP4.0 software. It contains a list of filenames necessary to start data collection and data transmission to the NTM host. The bdr_commit command copies the files if all of the following are true: 1. The BDR feature is unlocked 2. BDR is active on the primary FEP 3. The backup FEP system has been defined 4. BDR is not active on the backup FEP 5. The “.rhosts” for root on the backup FEP must contain the primary FEP name The bdr_commit command runs every time entity information is changed and every day at 12:02 a.m. The bdr_commit command can also be run from the command line at any time by a FEP-type user. This command displays no error messages to the screen. All associated error messages are logged in the BDR error log, which can be displayed by running the command:
Examples logCat -t 50 -l bdr
...... A-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... File(s) to be committed /raw/
File(s) /usra/fep/etc/bdr_act /usra/fep/etc/bdrfiles /usra/fep/etc/bdrfep
Caveat(s) If BDR is not active, bdr_commit will fail. If BDR is active on the backup FEP, bdr_commit will fail. If files have been copied to the backup FEP and the entity information seems to be inconsistent with the primary FEP, it will be necessary to update shared memory on the backup FEP with the new entity information by starting and then stopping the FEP application. If the shared memory is not updated, the FEP commands continue to display old entity information.
Note: Remember to run stopfep on the backup FEP or you may have data collection problems.
References “bdr_act” (p. A-7) “bdr_deact” (p. A-10) “bdr_takeover” (p. A-12) “centity” (p. A-13) “chentity” (p. A-17) “logCat” (p. A-37)
...... 190-406-737 Alcatel-Lucent — Internal A-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... bdr_deact
Description The bdr_deact (deactivate backup and disaster recovery) command is used to deactivate BDR for the FEP. This command verifies that the feature is unlocked before it deactivates BDR.
Syntax bdr_deact
File(s) /usra/fep/etc/bdr_act
References “bdr_act” (p. A-7) “bdr_commit” (p. A-8) “bdr_takeover” (p. A-12)
...... A-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... bdr_stat
Description The bdr_stat (backup and disaster recovery status) command provides the status of the: • BDR feature • FEP application • BDR state (active or deactivated) • BDR entity for the primary and backup FEP
Syntax bdr_stat
File(s) /usra/fep/etc/bdr_stat
References “bdr_act” (p. A-7) “bdr_deact” (p. A-10)
...... 190-406-737 Alcatel-Lucent — Internal A-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... bdr_takeover
Description The bdr_takeover (BDR takeover) command is run on the primary FEP. This command only takes one parameter, which is the name of the backup FEP.
Syntax bdr_takeover {fep_name}
Parameters fep_name Name of the fep machine.
Detailed description bdr_takeover shuts down the FEP application on the primary FEP, if running, and starts the FEP application running on the backup FEP only if all of the following are true: 1. The BDR feature is unlocked 2. The backup FEP system has been defined 3. The FEP name on the command line matches the backup FEP 4. The FEP application is not running on the backup FEP 5. The FEP-type user has permission to do an “rsh” command to the backup FEP After bdr_takeover runs, the backup FEP becomes the primary FEP. If bdr_takeover has any problems, an error message is displayed to the screen and logged to the bdrlog
File(s) /usra/fep/etc/bdrfep
References “bdr_act” (p. A-7) “bdr_commit” (p. A-8) “bdr_deact” (p. A-10) “bdr_stat” (p. A-11) “centity” (p. A-13) “chentity” (p. A-17) “logCat” (p. A-37)
...... A-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... centity
Description The centity (create entity) command has two functions. 1. The most common use of centity is for defining a new office on the FEP. In this case, the command: • creates the entity table and database table other entries required by the entity • initializes the system tables • creates the FEP-entity link 2. The centity command is also used to define a backup FEP if the BDR feature has been purchased. The backup FEP is kept up-to-date with any changes occurring on the primary FEP. For example, once a backup FEP has been defined, any changes to an entity or FEP-NTM link on the primary FEP automatically propagate from the primary FEP to the backup FEP.
Syntax centity entity_name -t entity_type [-n entity_number] -d time_diff -a datakit | TCP/IP address -g generic_id [-h header_issue] centity -B bdr_fep
Parameters All arguments to the command are mandatory.
entity_name An 11-character alphanumeric string that uniquely identifies an entity.
entity_type Specifies the entity type of the entity being created. Valid values are dms100, dms200, dms500, es5, or gtd5.
entity_numberSpecifies the entity number of the entity being created. Valid values are in the range 0-149. The value selected for an entity may not previously have been allocated to another entity. If this option is not on the command line, the lowest unused entity number is assigned automatically.
time_diff Specifies the time difference between the FEP and the entity relative to the FEP time. Valid values range from -12 to 12. (Example: If switch X is in the Eastern time zone and the FEP is in the Central time zone, then enter 1 here. If the switch and FEP time zones were reversed, this would be -1.)
datakit | TCP/IP addressSpecifies the destination dialstring or the interface card name, as follows:
...... 190-406-737 Alcatel-Lucent — Internal A-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... For all switch types except the polled GTD-5 … The Datakit destination dial string for this entity, with a maximum size of 72 characters. Get this value from the Datakit administrator.
For polled GTD-5 switches … The interface card name on the protocol converter and 3 colon-separated port numbers (for high, medium and low channels), where:
A[A] Link # on the converter interface card (1-16) multiplied by the converter interface card number (1-3).
BBB Unique number between 001 and 300. These port numbers are used when configuring the AISwitch 180.
Reference: See “Tips on navigating through the AISwitch menu” (p. 6-3) and “Port– to–Link Mapping (SVC)” (p. 6-22) for more information on the converter interface card and help with selecting TCP/IP port numbers.
generic_id Specifies the generic of the entity being created. Allowable values for the generic identification depend on the switch type. • ess5 — 5e4, 5e5, 5e6, 5e7, 5e8, 5e9, 5e9_2, 5e10, 5e11, 5e12, 5e13, 5e14, 5e15 • dms100 and dms200 — dms24, dms25, dms26, dms27, dms28, na007, na009, na010, na012, na014 • dms250 — ucs07, ucs10, ucs12, ucs14 • dms500 — ncs07, ncs12, ncs14 • gtd5 — gtd1732, gtd4003
header_issueSpecifies the type of message header for the dms250 and dms500 switch type. This parameter is mandatory for the dms250 and dms500 switch type and is not necessary for the dms100, dms200, es5 or gtd5 switch types. The dms250 and dms500 may use the old message header like what is used by the dms100, or it may use the new message header which is TR-740 compliant. Valid values for the header are issue1 (old message header) or issue2 (TR-740 compliant message header). • issue1 — FEP communicates with dms250 and dms500 using the FEP release 3 and prior interface
...... A-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... • issue2 — FEP communicates with dms250 and dms500 using the TR-740 compliant interface
bdr_fep Specifies the hostname of the backup FEP being created.
Restrictions When defining a DMS office on generic NA007 or later and the office is sending more than 250 trunk groups worth of data (i.e. Feature 263, “DMS 100/200 Switch Surveillance of 1024 Trunk Groups Via FEP”), the data must be sent at 19,200 baud rate to ensure no delay or loss of data. To achieve 19,200 baud rate, an entire SLM must be dedicated to that one office. When defining a GTD-5 office on generic gtd4003 or later, the FEP will connect to the office via TCP/IP through a protocol converter that changes TCP/IP to X.25 protocol and vice versa. If the GTD-5 office is on generic gtd1732, the FEP will connect to the office via DataKit. This distinction is handled through the -a option.
File(s) /usra/tusr/na/entity/entity_name/dc /raw/entity_name/5min /raw/entity_name/ctl /raw/entity_name/aud /raw/entity_name/tmp /usra/vpdb/entity_name /usra/vpdb/entity_name/callerdb
Examples
Non-GTD-5 Switch Types and GTD-5 on generic gtd4003 or later Entering the following at the command line: $ centity clmbohdm250 -t dms250 -n 141 -a oh/clmb/slm54p1 -d 0 -g ucs07 -h issue2 produces the following output. Vport Name: clmbohdm250 Vport Device: /dev/vport/vpapl0145 Outcall Address: oh/clmb/slm54p1 Transport Device: /dev/dk Server Name: /usra/fep/bin/dkoutsrvr Semantics: PVC NOHUP Entity clmbohdm250 was successfully created.
...... 190-406-737 Alcatel-Lucent — Internal A-15 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... GTD-5 on generic gtd4003 or later switches Entering the following at the command line: $ centity clmbohpgtd5 -t gtd5 -n 140 -a ai296a1:1001:1002:1003 -d 0 -g gtd4003 produces the following output. Entity clmbohpgtd5 was successfully created.
References “aentity” (p. A-3) “chentity” (p. A-17) “deaentity” (p. A-27) “delentity” (p. A-29) “rsentity” (p. A-42) “tlentity” (p. A-48) “Creating a switch” (p. 4-25)
...... A-16 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... chentity
Description The chentity (change entity) command has two functions. 1. The most common use of chentity is for modifying an entity parameter. In this case, the command changes the entity table and other database table entries required by the entity without requiring the entity to be deleted. The entity type (entity_type), entity number (entnum), and entity name (entity_name) cannot be changed using the chentity command. The entity must be deactivated and activated again for the changes made by this command to take effect. 2. The chentity command is also used to change a backup FEP if the BDR feature has been purchased. Reference: “centity” (p. A-13)
Syntax chentity {entity_name | entity_number} {[-d time_dif] [-g generic_id] [-a datakit | TCP/IP address] [-h header_issue]}} chentity -B bdr_fep
Parameters entity_name An 11-character alphanumeric string that uniquely identifies an entity. This parameter or the entity_number must be the first parameter entered on the command line.
entity_numberFor an existing entity. Must be in the range 0-149. This parameter or the entity_name must be the first parameter entered on the command line.
time_dif Specifies the time difference between the FEP and the entity relative to the FEP time. Valid values range from -12 to 12. (Example: If switch X is in the Eastern time zone and the FEP is in the Central time zone, then enter 1 here. If the switch and FEP time zones were reversed, this would be -1.)
generic_id Specifies the generic of the entity being created. Allowable values for the generic identification depend on the switch type. • ess5 — 5e4, 5e5, 5e6, 5e7, 5e8, 5e9, 5e9_2, 5e10, 5e11, 5e12, 5e13, 5e14, 5e15 • dms100 and dms200 — dms24, dms25, dms26, dms27, dms28, na007, na009, na010, na012, na014, na016 • dms250 — ucs07, ucs10, ucs12, ucs14 • dms500 — ncs07, ncs12, ncs14 • gtd5 — gtd1732, gtd4003; however:
...... 190-406-737 Alcatel-Lucent — Internal A-17 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... – the gtd1732 generic implies a monitored interface to the GTD-5 switch – the gtd4003 generic implies an LSSGR interface to the GTD-5 switch. As a result, you may not use the chentity command to switch between these generics. If you plan to upgrade from generic gtd1732 to gtd4003, you will need to delete the gtd1732 office (delentity) and recreate it with generic gtd4003 (centity).
datakit | TCP/IP addressSpecifies the destination dialstring or the interface card name, as follows:
For all switch types except the polled GTD-5 … The Datakit destination dial string for this entity, with a maximum size of 72 characters. Get this value from the Datakit administrator.
For polled GTD-5 switches … The interface card name on the protocol converter and 3 colon-separated port numbers (for high, medium and low channels), where:
A[A]BBB Where:
A[A] Link # on the converter interface card (1-16) multiplied by the converter interface card number (1-3).
BBB Unique number between 001 and 300. These port numbers are used when configuring the AISwitch 180.
Reference: See “Tips on navigating through the AISwitch menu” (p. 6-3) and “Port– to–Link Mapping (SVC)” (p. 6-22) for more information on the converter interface card and help with selecting TCP/IP port numbers.
header_issueSpecifies the type of message header for the dms250 and dms500 switch type. This parameter is mandatory for the dms250 and dms500 switch type and is not necessary for the dms100, dms200, ess5 or gtd5 switch types. The dms250 and dms500 may use the old message header like what is used by the dms100, or it may use the new message header which is TR-740 compliant. Valid values for the header are issue1 (old message header) or issue2 (TR-740 compliant message header). • issue1 — FEP communicates with dms250 and dms500 using the FEP release 3 and prior interface
...... A-18 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... • issue2 — FEP communicates with dms250 and dms500 using the TR-740 compliant interface
bdr_fep Specifies the hostname of the new backup FEP.
File(s) /usra/tusr/na/entity/entity_name/dc /raw/entity_name/5min /raw/entity_name/ctl /raw/entity_name/aud /raw/entity_name/tmp /usra/vpdb/entity_name /usra/vpdb/entity_name/callerdb
Examples
Switch Types other than gtd4003 or later To change switch “tampflxe62h”, so it has a new time difference of “-1”, enter the following: chentity tampflxe62h -d -1 If the update is successful, screen output resembles the following for switch types other than the GTD-5 on generic gtd4003 or later: Port deleted Vport Name: tampflxe62h Vport Device: /dev/vport/vpapl0001 Outcall Address: fl/tampdk/tampflxe Transport Device: /dev/dk Server Name: /usra/fep/bin/dkoutsrvr Semantics: PVC NOHUP Entity information was successfully changed. However, changes will not take effect until entity has been deactivated and activated.
gtd4003 or later switches Entering the following at the command line: $ chentity gtd5agcslab -a ai296a1:2001:2002:2003 produces the following output. Entity information was successfully changed. However, changes will not take effect until entity has been deactivated and activated.
...... 190-406-737 Alcatel-Lucent — Internal A-19 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29) “rsentity” (p. A-42) “tlentity” (p. A-48) “Changing a switch’s record base data on the FEP” (p. 4-31)
...... A-20 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... cnlink
Description The cnlink (create NTM link) command associates an NTM name with a location number.
Syntax cnlink ntmos_link -n location_number
Parameters ntmos_link An 11-character (or fewer) string that matches the name of an NTM machine that is being linked to the FEP
location_numberA unique number in the range 0–3
File(s) /usra/tdms/nmt/ntmsinfo
Examples cnlink cop1ntms -n 0 You will see a confirmation message, similar to the following: NTMOS link cop1ntms successfully created.
References “anlink” (p. A-4) “deanlink” (p. A-28) “delnlink” (p. A-31) “rsnlink” (p. A-44) “tnlink” (p. A-53) “Creating the FEP-NTM link” (p. 5-7)
...... 190-406-737 Alcatel-Lucent — Internal A-21 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... ddbkup_fep
Description The ddbkup_fep (backup FEP dynamic data files) command backs up FEP application reference data and UNIX system files. This command takes no arguments.
Syntax ddbkup_fep
Logins The user of the command need not be superuser. However, to restore UNIX system files backed up by this command, the user must be the superuser.
Detailed description This command backs up the application and UNIX files to the tape drive. It prompts for a tape to be loaded if one is not loaded at the time it is executed. If a tape is loaded, it initiates the backup without operator intervention. The command reads the “/usra/fep/bin/ddfiles” file to determine which files to back up. This file contains one line for each file or directory to be backed up. If a directory is specified, all files in that directory are backed up. Specify files and subdirectories that you do NOT wish to back up in the “/usra/fep/bin/ddfilesX” file. These files or directories listed in the “/usra/fep/bin/ddfilesX” files are excluded from the backup.
...... A-22 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... File(s) /install_fep_scripts /etc/group /etc/motd /etc/opasswd /etc/oshadow /etc/passwd /etc/profile /etc/shadow /etc/system /etc/hosts.equiv /etc/resolv.conf /etc/inet/hosts /etc/inet/inetd.conf /etc/inet/netmasks /etc/inet/networks /etc/uucp /usra/fep/bin/ddfiles /usra/fep/bin/ddfilesX /usra/fep/bin/edcs /usra/tdms/ipndc/active.ee /usra/fep/etc /usra/grp /usra/grp/bworx/bwx5.1/config_data/cm/em/deconfig /usra/grp/bworx/bwx5.1/config_data/fm/log/Config /usra/grp/bworx/bwx5.1/config_data/fm/log/logThrottle /usra/tdms/cf_parms /usra/tdms/ndc /usra/tdms/nmt/ntmsinfo /usra/tdms/nmt/rmNMTchild /usra/tdms/nmt/tmout.def /usra/tdms/trans5min/rpt_times.def /usra/tusr/na/entity /usra/vpdb /var/opt/dk
References “ddrstr_fep” (p. A-24) “Performing a manual backup of dynamic data” (p. 3-55)
...... 190-406-737 Alcatel-Lucent — Internal A-23 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... ddrstr_fep
Description The ddrstr_fep (restore FEP application files) command restores ALL FEP application reference data and UNIX system files on the dynamic data backup tape. This command takes no arguments. The command restores the files from the tape drive. The command assumes that the backup tape is in the tape drive when the command is executed. Ensure that the tape in the drive is the one you need. If there is no tape in the drive, the command prompts for the tape.
Syntax ddrstr_fep
Logins You must be the superuser to run this command.
...... A-24 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... File(s) /install_fep_scripts /etc/group /etc/motd /etc/opasswd /etc/oshadow /etc/passwd /etc/profile /etc/shadow /etc/system /etc/hosts.equiv /etc/resolv.conf /etc/inet/hosts /etc/inet/inetd.conf /etc/inet/netmasks /etc/inet/networks /etc/uucp /usra/fep/bin/ddfiles /usra/fep/bin/ddfilesX /usra/fep/bin/edcs /usra/tdms/ipndc/active.ee /usra/fep/etc /usra/grp /usra/grp/bworx/bwx5.1/config_data/cm/em/deconfig /usra/grp/bworx/bwx5.1/config_data/fm/log/Config /usra/grp/bworx/bwx5.1/config_data/fm/log/logThrottle /usra/tdms/cf_parms /usra/tdms/ndc /usra/tdms/nmt/ntmsinfo /usra/tdms/nmt/rmNMTchild /usra/tdms/nmt/tmout.def /usra/tdms/trans5min/rpt_times.def /usra/tusr/na/entity /usra/vpdb /var/opt/dk
Examples ddrstr_fep When you see “successful completion of dynamic data restore”, all files on the tape have been restored.
References “ddbkup_fep” (p. A-22)
...... 190-406-737 Alcatel-Lucent — Internal A-25 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... “Restoring dynamic data (all or some)” (p. 3-72)
...... A-26 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... deaentity
Description The deaentity (deactivate entity) command deactivates the link to the named entity. This stops data collection from the entity and disables the logical connection to the switch. This command returns an error message if the link has not yet been created or if it is not active.
Syntax deaentity {entity_name | entity_number}
Parameters entity_name An 11-character alphanumeric string that matches the name of the entity to which communication is being deactivated.
entity_numberFor an existing entity. Must be in the range 0-149. This parameter or the entity_name must be the first parameter entered on the command line.
File(s) /usra/tusr/na/entity/entities
Examples deaentity tampflxe62h After about 5 seconds, the switch is deactivated and you receive a message similar to the following: Entity ‘tampflxe62h’ deactivated
References “aentity” (p. A-3) “centity” (p. A-13) “chentity” (p. A-17) “delentity” (p. A-29) “rsentity” (p. A-42) “tlentity” (p. A-48) “Deactivating a switch-FEP link” (p. 4-30)
...... 190-406-737 Alcatel-Lucent — Internal A-27 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... deanlink
Description The deanlink (deactivate NTM link) command deactivates the link to the NTM machine specified by ntmos_link or location_number. It returns an error message if the link is not active.
Syntax deanlink {ntmos_link | location_number}
Parameters ntmos_link An 11-character (or fewer) string that matches the name of an NTM machine to which communication is being deactivated
location_numberAn integer in the range 0–3 that matches the location number assigned to a particular NTM connection at the time the link is created.
File(s) /usra/tdms/nmt/ntmsinfo
Examples deanlink cop1ntms Almost immediately, the link is deactivated and you receive a message similar to the following: NTMOS link is deactivated - cop1ntms
References “anlink” (p. A-4) “cnlink” (p. A-21) “delnlink” (p. A-31) “rsnlink” (p. A-44) “tnlink” (p. A-53) “Deactivating the FEP-NTM link” (p. 5-13)
...... A-28 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... delentity
Description The delentity (delete entity) command has two functions. The most common use of delentity is to delete the defined link between the FEP and the specified entity. It returns an error message if the link to the specified entity is active or has not been created.
Syntax delentity {entity_name | entity_number} [-f] [-B]
Parameters entity_nameAn 11-character alphanumeric string that matches the name of an entity that is being eliminated from the FEP database.
entity_numberThe entity number of the entity being deleted. Valid values are in the range 0-149.
-f The “Are you sure? (y or n)” prompt is skipped and the command is executed.
-B Specifies the existing backup FEP to be deleted.
Detailed description This command removes all data pertaining to the specified entity from the FEP. A warning message appears before each successful execution of the delentity command. The user of the command is prompted to verify that the command should be executed. The delentity command is also used to delete the backup FEP if the BDR feature has been purchased. Once the backup FEP has been deleted, any changes made on the primary FEP remain solely on the primary FEP since it knows of no backup FEP to which files can be downloaded.
File(s) /usra/tusr/na/entity/entity_name/dc /raw/entity_name/5min /raw/entity_name/ctl /raw/entity_name/aud /raw/entity_name/tmp /usra/vpdb/entity_name /usra/vpdb/entity_name/callerdb
...... 190-406-737 Alcatel-Lucent — Internal A-29 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Examples Enter the FEP command: delentity switch name Enter “y” when prompted.
Example: delentity tampflxe62h You see the following output: Entity “tampflxe62h” will be deleted Are you sure? (y or n) y Port deleted Entity was successfully deleted
References “aentity” (p. A-3) “centity” (p. A-13) “chentity” (p. A-17) “deaentity” (p. A-27) “rsentity” (p. A-42) “tlentity” (p. A-48) “Deleting a switch” (p. 4-27)
...... A-30 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... delnlink
Description The delnlink (delete NTM link) deletes the link to the NTM machine specified by ntmos_name. It returns an error message if the link to the specified ntmos_name is active or has not been created. A warning message appears before each successful execution of the delnlink command. The user of the command is prompted to verify that the command should be executed.
Syntax delnlink ntmos_name [-f]
Parameters ntmos_name An 11-character (or fewer) string that matches the name of an NTM machine with which communication is being eliminated
-f The “Are you sure? (y or n)” prompt is skipped and the command is executed
File(s) /usra/tdms/nmt/ntmsinfo
Examples delnlink cop1ntms You see the following output: NTMOS Link ‘cop1ntms’ will be deleted. Are you sure? (y or n) y NTMOS Link ‘cop1ntms’ was deleted.
References “anlink” (p. A-4) “cnlink” (p. A-21) “deanlink” (p. A-28) “rsnlink” (p. A-44) “tnlink” (p. A-53) “Deleting the FEP-NTM link” (p. 5-9)
...... 190-406-737 Alcatel-Lucent — Internal A-31 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... fsbackup_fep
Description The fsbackup_fep (full or incremental backup of FEP file systems) command can be used to take a full or incremental backup of the disk file systems onto a tape.
Syntax fsbackup_fep fsbackup_fep [full | incr] tape device name
Logins You must be the superuser to run this command.
Parameters tape device nameName of the tape device to be used.
Detailed description This command should only be used when the machine is in single user mode to avoid inconsistencies in the backed up file systems. However, it can also be run in the multi-user mode (as a cron job), but file system sanity is not guaranteed as some of the files may not be backed up properly if they are in a busy state at the time of backup. This command can be run either manually (from the command line) or can be setup to run automatically (as a cron job). When it is executed from the command line, it requires no arguments. It presents a menu from which the user can make a choice to either make a full backup or an incremental backup. The command backs up six FEP file systems in the following order: /usr/openwin, /opt, /usra, /var, /usr, and /. When the command is executed as a cron job, it requires two arguments. The first argument is either the keyword “full” (to take a full backup) or the keyword “incr” (to take an incremental backup). The second argument is the device name for the tape device (for example, /dev/rmt/0). It also performs a verify pass at the end of the backup process to ensure that the backup that was made is in a retrievable state. Backup tapes made using this command can be used to restore a lost or corrupt file system(s) on the disk.
File(s) /usr/fep/bin/fsbackup_fep
...... A-32 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Examples To make a full or incremental backup of file systems manually, at the command line (preferably in the single-user mode) enter: /usra/fep/bin/fsbackup_fep From the menu presented, select option 1 for full backup or option 2 for incremental backup. When prompted, enter the tape device name (default is /dev/rmt/0) and insert the tape in the drive and follow the instructions. To set up automatic full or incremental backup of file systems, the following lines must exist in the root’s crontab file:
For full backup 0 20 * * 5 /usra/fep/bin/fsbackup_fep full /dev/rmt/0
For incremental backup 0 20 * * 1-4 /usra/fep/bin/fsbackup_fep incr /dev/rmt/0 This starts a full backup every Friday at 20:00 hrs and an incremental backup Monday through Thursday every week at 20:00 hrs.
References “fsrestore_fep” (p. A-34)
...... 190-406-737 Alcatel-Lucent — Internal A-33 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... fsrestore_fep
Description The fsrestore_fep (full or incremental restore of FEP filesystem(s)) command can be used to restore one or more of the file systems /usra/openwin, /opt, /usra, and /var, on to the disk(s). This command cannot be used to restore either the “/”(root) file system or the “/usr” file system. To restore the “/”(root) or the “/usr” file systems, the system has to be first booted from the Solaris 2.5.1 CDROM (refer to the FEP5.0 Administration Guide for details).
Syntax fsrestore_fep
Logins You must be the superuser to run this command.
Detailed description The command should only be used when the machine is in single user mode. The command allows the user to either do a full or an incremental restore of the selected file systems. When this command is run, it presents a menu from which the user can choose either to do a full restore or an incremental restore. It requires the Full or Incremental backup tape (that was made using the fsbackup_fep command). The user can select the file systems to be restored from the list presented by the command.
File(s) /usr/fep/bin/fsrestore_fep
Examples To perform a full or an incremental restore of filesystems, at the command line (while in single-user mode) enter: /usra/fep/bin/fsrestore_fep From the menu presented, select option 1 for full restore or option 2 for incremental restore. When prompted, enter the tape device name (default is /dev/rmt/0) and insert the Full or Incremental tape into the tape drive. Finally, select the file system(s) that have to be restored from the menu presented. Once the selected file system(s) is restored, the process continues in a loop and the user is prompted to either select other file system(s) (if any) to restore or exit out of the program.
...... A-34 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “fsbackup_fep” (p. A-32)
...... 190-406-737 Alcatel-Lucent — Internal A-35 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... load_fep
Description The load_fep (load FEP application) command: • Creates directories required for the FEP application • Sets file ownerships and protections • Loads FEP application files into the proper directories • Sets up crontab jobs • Initializes the configuration file • Sets up auto-boot files • Executes initialization procedures for several FEP subsystems This command takes no arguments and is executed immediately after the application is installed from tape. The command may be executed more than once.
Syntax load_fep
Logins You must be the superuser to run this command.
Environment FEP_ROOT must be set to the directory in which FEP application is installed (e.g., “/usra/fep/bin”). The default directory for FEP_ROOT is “/usra/fep/bin”.
Examples To load the FEP application tape, enter: /usra/fep/bin/baseworx/scripts/load_fep This script produces trace output as commands are executed.
References “Installing the FEP application” (p. 2-34)
...... A-36 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... logCat
Description The logCat commands takes compressed messages and expands them to human readable form. The default behavior with no arguments is to list all log files of the type specified first in the Config file, that is: logCat -d${LOGROOT}/data -l{primary- log-prefix}
Syntax logCat [-t lines | -b lines] [-a locant | -z locant] [-v] [-c] [-r root] [-s locant...] [-+] [-w width] [-p cont-prefix] [-f format] [-X] [-V] [-d data -l log-prefix | file] Reference: “Looking into error, audit, and BDR logs” (p. 3-21) and “Monitoring the audit, error, or BDR log files” (p. 3-23).
Note: This is a BaseWorX command.
Parameters -t lines Tail the last lines of a file.
-b lines Show beginning lines of file.
-a locant Specifies to start displaying the expanded messages beginning with the one that contains locant.
-z locant Specifies to stop displaying the expanded messages ending with the one that contains locant.
-v Verbose — report the file names of the files examined.
-c Continuously display last lines of a file. If the logdaemon switches to a new file, logCat also switches to the new file.
-r root Specify an alternate root directory for LOGROOT. If LOGROOT is not set, the default is “/usr/spool/log”. The “data” directory containing the compressed log data files is expected to be in the root directory if not overridden by the -d data flag or the LOGDATA environment variable (e.g., “/usr/spool/log/data”).
...... 190-406-737 Alcatel-Lucent — Internal A-37 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
-s locant Specifies to display the expanded messages that contain locant. A maximum of 10 “-s” locants may be specified. The search capability supports the following meta-search constructs:
^ Beginning of message $ End of message * Any number of unspecified characters ? A single unspecified character [xxx] Any character in the list “xxx” [!xxx] Any character NOT in the list “xxx” \{chr} Normal C backslash conventions, \n \t \b \f \r \NNN \\ \/ \ [
-+ Find messages that match all the “-s” locants. The default is to find the messages that match any of the “-s” locants. At least one “-s” locant must be used.
-w width If lines are to be wrapped, this is the width at which the wrapping should take place. 0 means no wrapping and is the default. The width can also be supplied via the environment variable LOGCOLUMN.
-p cont-prefixThe string to be appended to each continuation line. The default is no continuation prefix. The prefix can also be provided via the environment variable LOGCONTPREFIX.
-f format Format specification for the display of the messages. If the format is to contain white space or escape characters, the format should be enclosed in double quotes. The default is the LOGFORMAT environment, or if LOGFORMAT is unset, the Common Event Message Format. See the expandLog(3) manual page for a complete list of the format specifications. All other characters are printed as is.
-X Make control characters visible. They are printed as \X if they have a special C notation, otherwise as
-V Print the current version number of the ROAM Logger logCat command.
Note: If a file name is specified, the -d data and -l log-prefix options are overridden.
-d data Explicit path name of the directory where the log files are. The data directory can be specified by the environment variable LOGDATA. The default is “$LOGROOT/data”.
...... A-38 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
-l log-prefixPrefix of the log files to examine. Default: first flat log file in the Config file. The log-prefix can also be provided via the environment variable LOGFILEPREFIX.
file Explicit file to be displayed. Specify the explicit path name of the file, or the current directory is used. If “-”, use standard input. The use of a file name overrides the -d data and -l log-prefix options. If a file is specified, it must be the last item on the command line invoking logCat.
locant Either: • Date/Time Stamp Dates can be any of the standard human readable forms: mmm dd, yyyy, mm/dd/yy, mm-dd-yy, etc. The time is hh:mm:ss. It is also possible to specify the separate elements as: sec=nn, min=nn, hour=nn, mday=mm, mon=nn or mon=mmm, year=nn[nn], wday=n or wday=ddd, yday=nnn. Portions left out default to this date, 0 hours, 0 minutes, and 0 seconds, i.e. giving only the time of day indicates today’s date. If the form “item=xxx” form is used, all elements not specified default to ‘*’, hence “wday=Sun” means all messages on any Sunday. DO NOT mix standard format with the “item=xxx” format. The results are not predictable. • Search Pattern Spaces should be enclosed in quotes, e.g., -a “7/14/87 05:08:30”. Search patterns are enclosed in ‘/’ characters, with an optional repetition count following, e.g., -z /GEN006/2 means the second message containing “GEN006”. The repetition count has no meaning with the “-s” locant, but does for the “-a” and “-z” locants. Search patterns specified with multiple -s options — by default — result in the display of any message matching one of the locants. The -x option can be used to make logCat display only those messages that match all the given locants.
Environment Environment variables are checked whenever the related command argument is missing from the command line. If both the command argument and the environment variable are missing, the specified default is used. @ROAMCNFG@ @LOGROOT@ @LOGDATA@ @LOGFORMAT@ @LOGCOLUMN@ @LOGCONTPREFIX@ @LOGFILEPREFIX@
...... 190-406-737 Alcatel-Lucent — Internal A-39 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... File(s) The $LOGROOT directory contains the Config file. $LOGDATA or $LOGROOT/data contains the compressed log data files. $ROAMCNFG/config_data/fm/api/formats contains the message catalogs.
Caveat(s) Any value for LOGCOLUMN other than 0 (zero) inserts blank spaces within the message for proper wraparound. This may cause a search pattern to fail. Setting LOGCOLUMN to 0 ensures that the search pattern will succeed if the pattern exists in the message.
References logEvent(3), vlogEvent(3), logperror(3), expandLog(3), Config(4), cmpMsg(5)
...... A-40 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... prtsint
Description The prtsint (print interval status) command shows the: • Entity name • Data type • Number of bytes • Time of the last data collection (end of collection) • Whether the FEP considers the data suspect • Full pathname of the file for all data selected by the arguments to the command
Syntax prtsint {entity_name | all | active} [-n {5min | aud | ctl}]
Parameters The command takes a minimum of one argument and a maximum of two. The possible arguments are:
entity_name An 11-character alphanumeric string for a single entity to be reported
all Indicates that all created entities should be reported.
active Indicates that active entities should be reported.
-n Indicates type of data to be reported. The valid values are 5min, aud, and ctl. If this argument is missing, all three are reported.
File(s) /raw/entity_name/5min /raw/entity_name/ctl /raw/entity_name/aud
Examples To display interval status data for all switches, enter: prtsint all
References “Checking switch data collection” (p. 4-14)
...... 190-406-737 Alcatel-Lucent — Internal A-41 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... rsentity
Description The rsentity (report entity status) command shows the following items for each entity selected by the argument: • entity name • destination dialstring and TCP/IP address • header issue • entity number • entity type • entity status • end time of the last 5 minute data collected by the FEP • time offset • 5-minute data suspect flag. If no entities are selected by the argument, an error message is printed.
Syntax rsentity {entity_name | entity_number | all | active}
Parameters The command takes exactly one argument. The possible arguments are:
entity_name A single entity to be reported. An 11-character alphanumeric string.
entity_numberA single entity to be reported. An integer assigned to this entity when it was created in the FEP database.
Reference: “centity” (p. A-13)
all Indicates that all created entities should be reported.
active Indicates that active entities should be reported.
...... A-42 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... File(s) /usra/tusr/na/entity/entity_name/dc /usra/tusr/na/entity/entities /usra/tusr/na/entity/xentities /raw/entity_name/5min /raw/entity_name/ctl /raw/entity_name/aud /raw/entity_name/tmp /usra/vpdb/entity_name /usra/vpdb/entity_name/callerdb
Examples To report status for all entities, enter: rsentity all To report status for active entities, enter: rsentity active
References “aentity” (p. A-3) “centity” (p. A-13) “chentity” (p. A-17) “deaentity” (p. A-27) “delentity” (p. A-29) “tlentity” (p. A-48) “Checking switch status” (p. 4-7) Figure 4-8, “Sample rsentity output” (p. 4-32)
...... 190-406-737 Alcatel-Lucent — Internal A-43 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... rsnlink
Description The rsnlink (report NTM link status) command shows the ntmos_name, status, and channel status for all FEP-NTM links or for the single FEP-NTM link specified on the command line. It also shows the network type connectivity for those links that are currently up. If no argument is supplied to rsnlink, it defaults to the ‘all’ option, displaying the status of all defined FEP-NTM links.
Syntax rsnlink [ntmos_name | all]
Parameters ntmos_name An 11-character (or fewer) string that matches the name of an NTM machine for which a single report is to be produced. This is assigned with the cnlink command.
all Indicates that a report is to be generated for all created NTM links.
Detailed description The status of the NTM link may be either:
ACTIVE Link has been created and activated. OFF Link is not activated.
The command reports on four channel statuses. The channels are the discrete (30-second), audit, control, and register (5-minute) data. The report indicates the status of each channel with an “A” indicating that data can pass between the two systems and an “I” indicating that it cannot. The link is functioning normally if “STATUS” is “ACTIVE” and all four channels are “A”. If at least one of the four channels is listed as “A”, then the network type is listed as:
TCP/IP if connectivity is up via a TCP/IP protocol UNKNOWN if the link is up and the network type is not able to be determined.
If all four channels are listed as “I”, the network type column is blank.
File(s) /usra/tdms/nmt/ntmsinfo
...... A-44 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Examples To report status for all links, enter: rsnlink all
References “anlink” (p. A-4) “cnlink” (p. A-21) “deanlink” (p. A-28) “delnlink” (p. A-31) “tnlink” (p. A-53) “Checking the FEP-NTM link status” (p. 5-5)
...... 190-406-737 Alcatel-Lucent — Internal A-45 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... startfep
Description The startfep command takes no arguments. It starts or restarts the FEP application. It transitions the FEP from the Shutdown to the Running state. If the FEP is in the Running state when this command is executed, it will do nothing. This command is also installed in the auto-boot directories “/etc/init.d” and “/etc/rc3.d”. It is automatically executed as part of a system reboot.
Syntax startfep
Examples To start FEP application software, enter: startfep As processes are started, messages scroll down your screen, ending with the message: NEW RUN LEVEL: Running
References “stopfep” (p. A-47) “Starting the FEP software” (p. 3-33)
...... A-46 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... stopfep
Description The stopfep command takes no arguments. This command transitions the FEP application from the Running state to the Shutdown state. This command is also installed in the auto-boot directories “/etc/init.d” and “/etc/rc3.d”. It is automatically executed as part of a system shutdown.
Syntax stopfep
Examples To stop FEP application software, enter: stopfep First, the following warning message appears on the screen of any terminal logged in at the FEP: Warning: FEP Application shutting down in 60 seconds. Then, as processes are killed, messages scroll down your screen, ending with the message: NEW RUN LEVEL: Shutdown Now your computer is running only the Solaris operating system, in multiuser mode.
References “startfep” (p. A-46) “Stopping the FEP software” (p. 3-34)
...... 190-406-737 Alcatel-Lucent — Internal A-47 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... tlentity
Description The tlentity (test entity link) command tests the entity indicated by the entity_name argument. The command sets up a session between a FEP and a deactivated entity. The entity must be deactivated (see “deaentity” (p. A-27)).
Syntax tlentity {entity_name | entity_number} [-f file]
Parameters entity_name An 11-character alphanumeric entity name of the entity to be tested.
entity_numberAn integer assigned to the entity when it was created. Reference: “centity” (p. A-13)
file An optional argument that indicates the file to which responses are to be sent. If no file is indicated, the responses are sent to the user terminal.
Detailed description
Monitored Entities Monitored entities in the GTE FEP configuration are those whose entity_type is “gtd5” and generic is “gtd1732”. Entering tlentity and specifying a GTD-5 entity on generic “gtd1732” will cause tlentity to print the message “MONITORING INPUT FOR ENTITY entity_name” and immediately begin looking for input bytes from the entity. Any data output from the GTD-5 under test will be received. Data is printed as it is received from the entity. Once input from a monitored entity begins, it is expected to arrive in a continuous stream until it is complete. Every time input stops for 10 seconds or more, the input is considered to be ended. The number of bytes received in the most recent input is reported on the user’s terminal as follows: “xxxx BYTES RECEIVED”. When input restarts, the byte count will restart from 1. Whenever 1 minute has passed with no data from the entity (this can be before any data is received, or after the 10-second count has completed), the message “NO DATA FOR ONE MINUTE FROM entity_name,” is reported on the users terminal. The test remains active until “QUIT” is entered on the users terminal. If the communications line for the entity under test is not receiving carrier, the message “WAITING FORCARRIER DETECT” occurs at 5-second intervals until carrier is detected or until the tlentity command is terminated.
...... A-48 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Polled GTD-5 Entities When bringing up a tlentity session with a polled GTD-5 entity (implied by generic “gtd4003” or later), the physical link to the entity is always established first. tlentity waits a maximum of 40 seconds for the link to come up. It prints the “LINK (chan 0) STATUS - WAITING FOR CONNECT” message every 5 seconds of the 40-second period that the link is down. Cmd (time): is the prompt for tlentity. The following commands are supported by tlentity:
time Send the switch time to the FEP. Compare the switch time returned with the time expected at the FEP (after correcting for time zone difference). Display both times, any time difference (seconds) and the FEP time zone correction used.
...... 190-406-737 Alcatel-Lucent — Internal A-49 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
poll a b The following poll types can be sent to BX.25 entities: c DATA TYPE POLL LOGICAL CHANNEL NM discrete 101 0 1 NM 5 Minute 102 0 2 Time poll 105 0 1 Planned down 204 0 1
The following messages can be returned from a poll: MESSAGE TYPE CODE NM discrete 101 NM 5 minute data 102 Time conflict 201 Invalid request 202 Overwritten data 203 Min-mode 205
Time conflict means the switch was polled during its lockout period, a time when it is updating its holding registers and cannot respond to FEP polls. Invalid request means the switch considered the message it received to be invalid. A switch may sometimes respond to a valid FEP poll with an “invalid request” because it could not, for some reason, send the data. Min-mode means the switch recently reinitialized and is not able to send the requested data. down Send a “FEP planned down” message to the switch. No switch response is expected. quit Exit tlentity.
Examples To test links for a monitored GTD-5 switch “tampflxe62h”, enter: tlentity tampflxe62h Output lists all switch-to-FEP data.
...... A-50 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
Here is an example of tlentity on a 5ESS switch: # tlentity dublin5ess1 LINK (chan 0) STATUS - WAITING FOR CONNECT LINK (chan 0) STATUS - WAITING FOR CONNECT LINK (chan 0) STATUS - WAITING FOR CONNECT LINK (chan 0) STATUS - WAITING FOR CONNECT LINK is up
Chan ‘1’ in active state Chan ‘2’ in active state Chan ‘3’ in active state
Cmd(time): t time
SENT (channel 1) 105 0 0
RECEIVED ESS MESSAGE (CHANNEL 1)
FEP TIME = 15:20:42 ESS TIME = 15:20:41 (time zone offset = 0)
Time Difference (ENTITY - LOCAL) = -1 seconds
Cmd(time): s status
Chan ‘1’ in active state Chan ‘2’ in active state Chan ‘3’ in active state
Cmd(time): q quit
References “aentity” (p. A-3) “centity” (p. A-13) “chentity” (p. A-17)
...... 190-406-737 Alcatel-Lucent — Internal A-51 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... “deaentity” (p. A-27) “delentity” (p. A-29) “rsentity” (p. A-42) “Testing FEP-Switch Links — Monitored GTD-5 Switches Output” (p. 4-17) “Testing FEP-switch links — 5ESS, DMS, polled GTD5” (p. 4-19)
...... A-52 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... tnlink
Description The tnlink (test NTM link) command sets up a dialog between FEP and NTM specified by ntmos_name or location_number. The link must be active before it can be tested with tnlink. When tnlink is entered, the user is prompted to enter the next message to be sent. To terminate tnlink, a Delete must be entered as the only character in the message.
Syntax tnlink {ntmos_name | location_number}
Parameters ntmos_name An 11-character (or fewer) string that matches the name of an NTM machine to be tested
location_numberA unique number in the range 0 to 3, corresponding to an ntmos_name
Examples To test NTM link cop1ntms, enter: tnlink cop1ntms You receive a prompt, similar to the following: Enter test message for cop1ntms: Enter anything, such as: This is test of link cop1ntms at 12:52 p.m. Contact an NTM system administrator at that console to ensure the message was received.
References “anlink” (p. A-4) “cnlink” (p. A-21) “deanlink” (p. A-28) “delnlink” (p. A-31) “rsnlink” (p. A-44) “Testing the FEP-NTM link” (p. 5-15)
...... 190-406-737 Alcatel-Lucent — Internal A-53 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
...... A-54 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
B Datakit VCS Settings
Overview
Purpose This appendix gives the settings for various boards connecting switch-Datakit-FEP-NTM components. This information is supplied to Datakit and other administrators during initial system installation, and when and if they reconfigure or repair your network. Unless you will be doing this Datakit or network configuring, you would not use this yourself.
This appendix contains the following topics:
Datakit VCS settings with GTD-5 switches B-2
Entering Datakit VCS settings for CPM-HS with a FEP B-3
Entering Datakit VCS settings for TY-12 B-7
Datakit VCS settings with 5ESS, DMS, and DMS 250 switches B-11
Entering Datakit VCS setting w/SLM B-14
...... 190-406-737 Alcatel-Lucent — Internal B-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Datakit VCS settings with GTD-5 switches
Overview Figure B-1 depicts the board layout for GTD-5 switches with FEP.
Figure B-1 Boards with GTD-5 switches
GTD-5 The following procedures give board settings for a CPM-HS and networks with GTD-5 switches.
...... B-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Entering Datakit VCS settings for CPM-HS with a FEP
Purpose For where the following procedure is used, see Figure B-1 and Figure B-2.
Instructions Follow these steps:
......
1 At a Datakit VCS terminal, enter: enter group and follow the prompts as indicated below.
Result: GROUP [up to 8 chars]:
......
2 Enter an up-to-8-character name you will use to identify the FEP. We suggest you log in on the FEP console and enter uuname -l to see what the FEP calls itself, and then use that same name here.
Result: TYPE [local, trunk: +(local)]
......
3 Press return to select default.
Result: DIRECTION [originate, receive, 2way]:
......
4 Enter: 2way Result: DEVICE OR HOST [up to 8 chars]:
......
5 Enter the FEP’s processor name. In other words, log on the FEP console and enter uuname -l. The name you then see is the name you will enter here.
Result: HOST AUTOBAUD [on, off: +(off)]:
......
6 Press return to select default.
Result: NETWORK ACCESS PASSWORD [up to 8 chars]:
...... 190-406-737 Alcatel-Lucent — Internal B-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
7 Press return to select default.
Result: ROUND ROBIN SERVICE [per_port, per_module, none: +(none)]:
......
8 Press return to select default.
......
9 At a Datakit VCS terminal, enter: enter addr and follow the prompts as indicated below.
Result: TYPE [dk, pdn, x25host: +(dk)]:
......
10 Press return to select default.
Result: NAME [up to 8 chars]:
......
11 Enter the same 8-character name you entered for “GROUP”, above.
Result: LEVEL [area, exch, local, speedcall or +(local)]:
......
12 Press return to select default.
Result: DIRECTORY ENTRY [up to 30 chars, double quoted]:
......
13 Press return to skip.
Result: GROUP(S) [up to 4 separated by commas]:
......
14 Enter the same name you entered for “GROUP” above.
Result: ORIGINATING GROUP NAME SECURITY PATTERN(S) [separated by commas] [chars, ?, *, [x-y], or same_as]:
......
15 Press return to skip.
...... B-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Result: RESTORE NAME TO SERVICE? [yes/no, +(no)]:
......
16 Enter: yes
......
17 At a Datakit VCS terminal, enter: enter cpm and follow the prompts as indicated below.
Result: MODULE ADDRESS [2-127]:
......
18 Use address for slot A.
Result: COMMENT [up to 60 chars double quoted]:
......
19 Enter anything, if you want.
Result: HARDWARE TYPE [dr, 422, hs: +(hs)]:
......
20 Enter: hs Result: NUMBER OF CHANNELS [2-512: +32]:
......
21 Enter: 256 Responsibility: SERVICE TYPE [dstr, unix: +(unix)]:
......
22 Enter: unix Result: SINGLE OR MULTIPLE GROUPS [single, multiple: +single)]:
......
23 Enter: single Result: GROUP [up to 8 characters]:
......
24 Enter the same name you entered for “GROUP” above...... 190-406-737 Alcatel-Lucent — Internal B-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Result: CHANNEL RANGE [low-high: +(2-1270]:
......
25 Enter: 2-255
...... E ND OF STEPS ......
...... B-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Entering Datakit VCS settings for TY-12
Purpose For where the following procedure is used, see Figure B-1. This procedure is used for TY- 12 in networks with GTD-5 switches.
Instructions Follow these steps:
......
1 At a Datakit VCS terminal, enter: enter group and follow the prompts as indicated below.
Result: GROUP [up to 8 chars]:
......
2 Enter an 8-character name you will use to identify the switch.
Result: TYPE [local, trunk: +(local)]
......
3 Press return to select default.
Result: DIRECTION [originate, receive, 2way]:
......
4 Enter: receive Result: DEVICE OR HOST [up to 8 chars]:
......
5 Enter: async
Result: HOST AUTOBAUD [on, off: +(off)]:
......
6 Press return to select default.
Result: ROUND ROBIN SERVICE [per_port, per_module, none: +(none)]:
...... 190-406-737 Alcatel-Lucent — Internal B-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
7 Press return to select default.
......
8 At a Datakit VCS terminal, enter: enter address and follow the prompts as indicated below.
Result: TYPE [dk, pdn, x25host: +(dk)]:
......
9 Press return to select default.
Result: NAME [up to 8 chars]:
......
10 Enter the same 8-character name you entered for “GROUP”, above.
Result: LEVEL [area, exch, local, speedcall or +(local)]:
......
11 Press return to select default.
Result: DIRECTORY ENTRY [up to 30 chars, double quoted]:
......
12 Press return to skip.
Result: GROUP(S) [up to 4 separated by commas]:
......
13 Enter the same 8-character name you entered for “GROUP”, above.
Result: ORIGINATING GROUP NAME SECURITY PATTERN(S) [separated by commas] [chars, ?, *, [x-y], or same_as]:
......
14 Press return to skip.
Result: RESTORE NAME TO SERVICE? [yes/no, +(no)]:
......
15 Enter: yes
...... B-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
16 At a Datakit VCS terminal, enter: enter ty and follow the prompts as indicated below.
Result: TY TYPE [6, 12 or bal2]:
......
17 6 or 12, depending on if you are using “ty6” or “ty12”.
Result: MODULE ADDRESS [2-127]:
......
18 This depends on your hardware configuration. Specifically, this is the Datakit slot where “ty” resides.
Result: CHANNEL NUMBER [1-12: +(1-12)]:
......
19 Any spare port on the “ty”.
Result: COMMENT [up to 60 chars double quoted]:
......
20 Anything, if you want.
Result: SERVICE TYPE [console, dialer, host, modem, 2way, or terminal: +9terminal)]:
......
21 Enter: host Result: GROUP [up to 8 characters]:
......
22 Enter the same 8-character name you entered for “GROUP”, above.
Result: BAUD RATE [300, 1200, 9600, ext, auto: +(9600)]:
......
23 Press return to select default of “9600”.
Result: EXTERNAL BAUD RATE [2400, 4800, 19200: +(2400)]:
...... 190-406-737 Alcatel-Lucent — Internal B-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
24 Enter: 2400
Result: PARITY [off, even, odd: +(off)]:
......
25 Enter: off Result: FLOW CONTROL OF TY-12 BY DEVICE [xon_xoff, eia, none: +(none)]:
......
26 Enter: none
Result: FLOW CONTROL OF DEVICE BY TY-12 [xon_xoff, eia, none: +(xon_xoff)]:
......
27 Enter: none Result: IS AN Lucent Technologies VDM CONNECTED TO THIS LINE [yes, no: +(no)]:
......
28 Enter: no
...... E ND OF STEPS ......
...... B-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Datakit VCS settings with 5ESS, DMS, and DMS 250 switches
Overview Figure B-2 and Figure B-3 depicts the board layout for 5ESS, DMS, and DMS 250 switches with FEP.
...... 190-406-737 Alcatel-Lucent — Internal B-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Figure B-2 Boards with 5ESS and DMS type switches
Figure B-3 Datakit II SLM (synchronous line module) switch settings for I/O board
...... B-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... ED-5P077-30,G1
...... 190-406-737 Alcatel-Lucent — Internal B-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Entering Datakit VCS setting w/SLM
Before you begin Before using the following procedure, hardware must be set up as shown in Figure B-2 and Figure B-3. This procedure is used for 5ESS, DMS and DMS 250 switches.
Instructions Follow these steps:
......
1 At a Datakit VCS terminal, enter: enter group and follow the prompts as indicated below.
Result: GROUP [up to 8 characters]
......
2 Enter an 8-character name you will use to identify the switch.
Result: TYPE [local, trunk: +(local)]:
......
3 Press return to select default.
Result: DIRECTION [originated, receive, 2way]:
......
4 Enter: receive Result: DEVICE OR HOST [up to 8 chars]:
......
5 Enter: sync
Result: HOST AUTOBAUD [on or off +(off)]:
......
6 Press return to select default.
Result: ROUND ROBIN SERVICE [per_port, per_module, none: +(none)]:
...... B-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
7 Press return to select default.
......
8 At a Datakit VCS terminal, enter: enter address and follow the prompts as indicated below.
Result: TYPE [dk, pdn, x25host: +(dk)]:
......
9 Press return to select default.
Result: NAME [up to 8 chars]:
......
10 Enter the same 8-character name you entered for “GROUP”, above.
Result: LEVEL [area, exch, local, speedcall or +(local)]:
......
11 Press return to select default.
Result: DIRECTORY ENTRY [up to 30 chars, double quoted]:
......
12 Press return to skip.
Result: GROUP(S) [up to 4 separated by commas]:
......
13 Enter the same 8-character name you entered for “GROUP”, above.
Result: ORIGINATING GROUP NAME SECURITY PATTERN(S) [separated by commas] [chars, ?, *, [x-y], or same_as]:
......
14 Press return to skip.
Result: RESTORE NAME TO SERVICE? [yes/no, +(no)]:
......
15 Enter: no
...... 190-406-737 Alcatel-Lucent — Internal B-15 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
16 At a Datakit VCS terminal, enter: enter slm and follow the prompts as indicated below.
Result: DOWNLOAD SERVER [+(controller)]:
......
17 Enter the FEP’s processor name. In other words, log in on the FEP terminal and enter uuname -l. The name you then see is the name you will enter here.
Result: VERSION OF SOFTWARE [+(slm.1)]
......
18 For 5ESS switches, enter: tfs.bx.iss2 For DMS and DMS 250 switches, enter: tfs.bx.iss3 Result: MODULE ADDRESS [2-127]:
......
19 This depends on your hardware configuration. Specifically, this is the Datakit slot where SLM resides.
Result: PORT 1 GROUP NAME (or ‘none’) [up to 8 chars]:
......
20 Use same name you entered for GROUP above, for the first switch.
Result: PORT 2 GROUP NAME (or ‘none’) [up to 8 chars]:
......
21 Use same name you entered for GROUP above, for the second switch.
Result: PORT 3 GROUP NAME (or ‘none’) [up to 8 chars]:
......
22 Use same name you entered for GROUP above, for the third switch.
Result: PORT 4 GROUP NAME (or ‘none’) [up to 8 chars]:
...... B-16 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
23 Use same name you entered for GROUP above, for the fourth switch.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal B-17 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
...... B-18 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
C FEP System Responses
Overview
Purpose This appendix lists FEP system responses, which are the FEP error and audit messages. With each message we give instructions telling what each message means, and what you should do. (To see the FEP system responses, use “Monitoring the audit, error, or BDR log files” (p. 3-23).)
Reference: Solaris and Datakit VCS messages are NOT in this appendix. Solaris or Datakit VCS messages are explained in Solaris and Datakit VCS documents.
This appendix contains the following topics:
FEP system responses C-3
Software subsystem codes C-3
AUD — Audit Trail Messages C-5
BDR — Backup and Disaster Recovery Commands C-23
CMD — User Commands C-47
EDCS — GTD-5 Event Data Collection Subsystem C-56
EDD — GTD-5 Data Distributor C-64
IPNDC — Internet Protocol Network Data Collector C-82
LM — BaseWorX Log Manager C-148
NDC — Network Data Collector C-150
NMT — Network Management C-218
RT — BaseWorX Rapid Transit C-275
...... 190-406-737 Alcatel-Lucent — Internal C-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
SLM — Synchronous Line Module C-278
SYM — FEP System C-282
TRN — GTD-5 Translators C-293
...... C-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... FEP system responses
Software subsystem codes Each message includes a code, which tells you the subsystem that sent the message. In the figure above, the “AUD” subsystem sent the message. (In the real error files, the code is NOT circled.) We spell out subsystem names in Table C-1. Knowing the subsystem may give you some insight into problems, but you are NOT expected to understand FEP software.
Figure C-1 A FEP system response, with its software subsystem code circled
Table C-1 Software subsystem codes Software subsystem code What the messages are about. AUD Audit trail messages. These are informational only and don’t indicate a problem. BDR Backup Disaster and Recovery CMD User commands. Errors, usually from user commands. EDCSI, EDCS GTD-5 event data collection subsystem. Errors from data collection from GTD-5 switches. EDD GTD-5 data distributor. Errors from sending data to a translator for GTD-5 switches. LM BaseWorX log manager. These are status messages about the FEP daemon processes that BaseWorX controls.
...... 190-406-737 Alcatel-Lucent — Internal C-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Table C-1 Software subsystem codes Software subsystem code What the messages are about. NDC Network data collector. Errors from data collection from 5ESS or DMS switches. NMT Network management transmitter. Errors from data transmission between the FEP and NTM. RT BaseWorX Rapid Transit. These are status messages about the FEP daemon processes that BaseWorX controls. SLM Synchronous line module. Errors from downloading “pump code” to Datakit VCS SLMs. SLMs are required for data collection from 5ESS or DMS switches. SYM FEP system. Internal errors, usually from serious problems at the FEP. TRN GTD- 5 translators. Errors from translating discrete or 5-minute data, or controls or audits, for GTD-5 switches.
Other messages You should never see messages with software subsystem codes not listed in the table above. If you do see such a message, and it is informational, you can ignore it. But if it appears to indicate there is a problem, report it to FEP Customer Support.
...... C-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD — Audit Trail Messages Overview
Purpose This section provides all of the AUD error messages.
Messages in this section include:
• AUD 001
• AUD 002
• AUD 003
• AUD 004
• AUD 005
• AUD 006
• AUD 007
• AUD 008
• AUD 009
• AUD 010
• AUD 011
• AUD 012
• AUD 013
• AUD 014
...... 190-406-737 Alcatel-Lucent — Internal C-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
• AUD 015
• AUD 016
...... C-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD 001
Message ID
AUD 001 Discrete report received from entity entity
Description The FEP has received a 30-second report from the specified GTD-5 entity. This message may only appear when FEP Customer Support is contacted for fault isolation. This message is normally not logged on the FEP as it does not indicate a problem, and it would generate many messages, making it cumbersome to identify true error conditions.
Status
Parameters entity FEP entity number of the GTD-5 switch that sent the 30-second report
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-7 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 002
Message ID
AUD 002 5-minute data report received from entity entity
Description The FEP has received a 5-minute report from the specified GTD-5 entity. This message may only appear when FEP Customer Support is contacted for fault isolation. This message is normally not logged on the FEP as it does not indicate a problem, and it would generate many messages, making it cumbersome to identify true error conditions.
Parameters
entity FEP entity number of the switch that sent the 5-minute report
Status
Corrective action This message is for your information only. No action is required.
...... C-8 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD 003
Message ID
AUD 003 Control response received from entity entity
Description The FEP has received a control response from the specified entity.
Parameters
entity FEP entity number of the switch that sent the control response
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-9 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 004
Message ID
AUD 004 Audit response received from entity entity
Description The FEP has received an audit response from the specified entity.
Parameters
entity FEP entity number of the switch that sent the audit response
Status
Corrective action This message is for your information only. No action is required.
...... C-10 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD 005
Message ID
AUD 005 Control request sequence # seq_no received for entity entity from NTMOS link NTMOS_link (num_bytes bytes)
Description The FEP has received a control request from NTM for the specified entity.
Parameters
seq_no A unique number generated by NTM, used to keep track of outstanding control and audit jobs requests
entity FEP entity number of the switch that will receive the control request
NTMOS_link The NTM link used to send the control request
num_bytes The number of bytes in the control request received by the FEP from NTM
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-11 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 006
Message ID
AUD 006 Audit request sequence # seq_no received for entity entity from NTMOS link NTMOS_link (num_bytes bytes)
Description The FEP has received an audit request from NTM for the specified entity.
Parameters
seq_no A unique number generated by NTM, used to keep track of outstanding control and audit jobs requests
entity FEP entity number of the switch that will receive the audit request
NTMOS_link The NTM link used to send the audit request
num_bytes The number of bytes in the audit request received by the FEP from NTM
Status
Corrective action This message is for your information only. No action is required.
...... C-12 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD 007
Message ID
AUD 007 30-second report sent to NTMOS link NTMOS_link (num_bytes bytes)
Description The FEP has sent the discrete report to NTM. This single message contains the discretes for all entities activated on NTM.
Parameters
NTMOS_link The NTM link used to send the discrete report
num_bytes The number of bytes (which is always 1800 bytes) sent in the discrete message
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-13 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 008
Message ID
AUD 008 5-minute report from entity entity sent to NTMOS link NTMOS_link (num_bytes bytes)
Description The FEP has sent the 5-minute report for the specified GTD-5 entity to NTM.
Parameters
entity FEP entity number of the switch
NTMOS_link The NTM link used to send the 5-minute report
num_bytes The number of bytes sent in the binary 5-minute report. This number will be substantially less than the number of bytes in the GTD-5 ASCII 5- minute report
Status
Corrective action This message is for your information only. No action is required.
...... C-14 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD 009
Message ID
AUD 009 Control response sequence # seq_no from entity entity sent to NTMOS link NTMOS_link (num_bytes bytes)
Description The FEP has sent a control response to NTM.
Parameters
seq_no A unique number generated by NTM, used to keep track of outstanding control and audit jobs requests
entity FEP entity number of the switch whose control response was sent to NTM
NTMOS_link The NTM link used to send the control response
num_bytes The number of bytes in the control response sent to NTM
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-15 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 010
Message ID
AUD 010 Audit response sequence # seq_no from entity entity sent to NTMOS link NTMOS_link (num_bytes bytes)
Description The FEP has sent an audit response to NTM.
Parameters
seq_no A unique number generated by NTM, used to keep track of outstanding control and audit jobs requests
entity FEP entity number of the switch whose audit response was sent to NTM
NTMOS_link The NTM link used to send the audit response
num_bytes The number of bytes in the audit response sent to NTM
Status
Corrective action This message is for your information only. No action is required.
...... C-16 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD 011
Message ID
AUD 011 Control request sent to entity entity
Description The FEP has received a binary control request from NTM, translated it to ASCII, and sent it to the specified entity.
Parameters
entity FEP entity number of the switch that was sent the control request
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-17 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 012
Message ID
AUD 012 Audit request sent to entity entity
Description The FEP has received a binary audit request from NTM, translated it to ASCII, and sent it to the specified entity.
Parameters
entity FEP entity number of the switch that was sent the audit request
Status
Corrective action This message is for your information only. No action is required.
...... C-18 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD 013
Message ID
AUD 013 Entity entity indicated illegal request
Description The FEP has received an audit response from the specified entity that indicates the initial audit request is invalid for this entity or the request is not in the correct format.
Parameters
entity FEP entity number of the switch that was sent the audit response
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-19 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 014
Message ID
AUD 014 Entity entity feature not available
Description The FEP has received an audit response from the specified entity that indicates this feature does not exist for this entity.
Parameters
entity FEP entity number of the switch that sent the audit response
Status
Corrective action This message is for your information only. No action is required.
...... C-20 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... AUD 015
Message ID
AUD 015 Entity entity indicated not ready condition
Description The FEP has received an audit response from the specified entity that indicates the entity is not ready to receive the request.
Parameters
entity FEP entity number of the switch that sent the audit response
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-21 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... AUD 016
Message ID
AUD 016 Entity entity indicated severe problems
Description The FEP has received an audit response from the specified entity that indicates the entity has severe problems.
Parameters
entity FEP entity number of the switch that sent the audit response
Status
Corrective action This message is for your information only. No action is required.
...... C-22 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR — Backup and Disaster Recovery Commands Overview
Purpose This section provides all of the BDR error messages.
Messages in this section include:
• BDR 001
• BDR 002
• BDR 003
• BDR 004
• BDR 005
• BDR 006
• BDR 007
• BDR 008
• BDR 009
• BDR 010
• BDR 011
• BDR 012
• BDR 013
• BDR 014
• BDR 015
• BDR 016
• BDR 017
• BDR 018
• BDR 019
• BDR 020
• BDR 021
• BDR 022
...... 190-406-737 Alcatel-Lucent — Internal C-23 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 001
Message ID BDR 001 Too many parameters given as arguments to the command.
Description A user attempted to call a BDR-specific command with an incorrect number of parameters.
Minor
Corrective action Follow these steps:
......
1 Verify the format of the command entered.
...... E ND OF STEPS ......
...... C-24 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 002
Message ID
BDR 002 FEP = fep_name is running the NetMinder System’s NTM Function FEP application.
Description The user tried to take over a FEP that the system thinks is already running the FEP application.
Parameters fep_name The name of a FEP as specified by the user in a centity command
Status
Corrective action This message is for your information only. No action is required.
References “centity” (p. A-13)
...... 190-406-737 Alcatel-Lucent — Internal C-25 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 003
Message ID BDR 003 Starting takeover of NetMinder/NTM FEP application on FEP = fep_name.
Description This is a status message indicating that the specified NTM FEP can be taken over.
Parameters fep_name The name of a FEP as specified by the user in a centity command
Status
Corrective action This message is for your information only. No action is required.
References “centity” (p. A-13)
...... C-26 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 004
Message ID
BDR 004 Command = cmd_name cmd parameters on FEP = fep_name completed.
Description This is a status message to log the completion of a BDR-specific command.
Parameters
cmd_name The name of a FEP BDR command
cmd parametersThe parameters associated with the logged BDR command
fep_name The name of a FEP where the command was executed
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-27 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 005
Message ID
BDR 005 Command = cmd_name cmd parameters for FEP = fep_name failed.
Description A BDR-specific command has failed to execute on a FEP.
Parameters
cmd_name The name of a FEP BDR command
cmd parametersThe parameters associated with the logged BDR command
fep_name The name of a FEP where the command was executed
Minor
Corrective action Follow these steps:
......
1 Verify the format of the command entered.
...... E ND OF STEPS ......
...... C-28 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 006
Message ID
BDR 006 No backup FEP or multiple backup FEPs defined on FEP = fep_name.
Description No FEP or multiple FEPs have been defined as the backup for the indicated FEP as part of BDR.
Parameters fep_name The name of a FEP as specified by the user in a centity command
Minor
Corrective action Follow these steps:
......
1 Verify the centity procedure for the backup FEP.
...... E ND OF STEPS ......
References “centity” (p. A-13)
...... 190-406-737 Alcatel-Lucent — Internal C-29 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 007
Message ID
BDR 007 Could not access target processor FEP = fep_name.
Description The user attempted to access a FEP that is unreachable.
Parameters fep_name The name of a FEP as specified by the user in a centity command
Major
Corrective action Follow these steps:
......
1 Verify the status of the FEP being contacted.
......
2 Verify the status of the connecting communication network by running “/usr/sbin/ping fep_name” to see if the target FEP is reachable.
...... E ND OF STEPS ......
References “centity” (p. A-13)
...... C-30 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 008
Message ID
BDR 008 FEP = fep_name is not a valid system name.
Description A FEP application or user attempted to access an undefined FEP.
Parameters fep_name The name of a FEP as specified by the user in a centity command
Minor
Corrective action Follow these steps:
......
1 Verify the FEP name being used by running the bdr_stat command.
...... E ND OF STEPS ......
References “bdr_stat” (p. A-11) “centity” (p. A-13)
...... 190-406-737 Alcatel-Lucent — Internal C-31 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 009
Message ID
BDR 009 Executed from FEP = fep_name, command = cmd_name is not executable.
Description A FEP application or user has attempted to execute a command that the user does not have permission to run.
Parameters
cmd_name The name of a FEP BDR command
fep_name The name of a FEP as specified by the user in a centity command
Minor
Corrective action Follow these steps:
......
1 Verify the access permissions for the listed command.
...... E ND OF STEPS ......
References “centity” (p. A-13)
...... C-32 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 010
Message ID
BDR 010 State of BDR feature has been changed to state.
Description This is a status message to log that the state of the entire BDR has been changed.
Parameters
state The state of BDR in the reporting FEP
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-33 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 011
Message ID BDR 011 Backup and Disaster Recovery Feature is not available.
Description This is a status message to inform a user that their FEP does not have the BDR capability.
Status
Corrective action This message is for your information only. No action is required.
...... C-34 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 012
Message ID
BDR 012 Could not change BDR state to state.
Description A FEP application or a user attempted to change the BDR state of the FEP and the change failed.
Parameters
state The state of BDR in the reporting FEP
Major
Corrective action Follow these steps:
......
1 Verify that BDR is purchased and installed on the FEP.
......
2 Verify the format of the command entered.
......
3 Enter bdr_stat to verify the current state of the FEP.
......
4 Report the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “bdr_stat” (p. A-11)
...... 190-406-737 Alcatel-Lucent — Internal C-35 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 013
Message ID
BDR 013 FEP = fep_name is in the “not active” BDR state.
Description A user or FEP application attempted to execute a BDR-specific command on the specified FEP but its BDR state is “not active”.
Parameters
fep_name The name of a FEP where the command was executed
Major
Corrective action Follow these steps:
......
1 Verify that BDR is purchased and installed on the FEP.
......
2 Verify the format of the command entered.
......
3 Enter bdr_stat to verify the current state of the FEP.
......
4 Enter bdr_act and then “yes” to change the BDR state to “active”, then reenter the desired command.
......
5 If the BDR state is not changed to “active” and the problem persists, report the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “bdr_act” (p. A-7) “bdr_stat” (p. A-11)
...... C-36 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
...... 190-406-737 Alcatel-Lucent — Internal C-37 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 014
Message ID BDR 014 Cannot start NetMinder System’s NTM Function FEP application. Backup NetMinder System’s NTM Function FEP already running.
Description An NTM FEP application or a user attempted to execute the bdr_takeover command but the defined “backup” NTM FEP already has its NTM FEP application running.
Major
Corrective action Follow these steps:
......
1 Stop the backup FEP application by entering stopfep on the backup FEP.
......
2 Then run the startfep command again or run bdr_takeover from the primary FEP.
...... E ND OF STEPS ......
References “bdr_takeover” (p. A-12) “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-38 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 015
Message ID BDR 015 Starting bdr_commit
Description A FEP application or a user has started synchronizing the files between the primary FEP and the backup FEP.
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-39 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 016
Message ID
BDR 016 Completed bdr_commit state
Description A FEP application has completed synchronizing the files between the primary FEP and the backup FEP.
Parameters
state BDR commit was successful or unnecessarily
Status
Corrective action This message is for your information only. No action is required.
...... C-40 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 017
Message ID
BDR 017 BDR could not commit all the files to the backup FEP fep_name. The problems are listed in the file file_name.
Description BDR could not commit all the files to the backup FEP (fep_name). The problems are listed in the file file_name. The FEP BDR application has determined that there may have been problems copying files to the backup FEP.
Parameters fep_name The name of a FEP as specified by the user in a centity command
file_name The name of the file listing the errors
Major
Corrective action Follow these steps:
......
1 Verify that the FEP type user has permissions to copy the files to the backup FEP.
...... E ND OF STEPS ......
References “centity” (p. A-13)
...... 190-406-737 Alcatel-Lucent — Internal C-41 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 018
Message ID
BDR 018 File filename not found, errno=errno_num
Description A FEP BDR application or a user could not find the indicated file on the system. This file (and/or directory) may have: • been accidently removed from the system and may need to be restored • the wrong permissions
Parameters filename The name of the file that is missing
errno_num Error number that indicates the possible problem
Major
Corrective action Follow these steps:
......
1 Verify that BDR is active and that the backup FEP has been defined.
......
2 Verify that the user has permission for the file and directory for
......
3 If the problem persists, report the problem to FEP Customer Support.
...... E ND OF STEPS ......
...... C-42 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 019
Message ID
BDR 019 Could not open filename
Description A FEP application or a user could not open the indicated file.
Parameters
filename The name of the file that could not be opened
Major
Corrective action Follow these steps:
......
1 Verify that the user has permission to read this file.
......
2 If the problem persists, report the problem to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-43 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 020
Message ID
BDR 020 The .rhost file on backup_fep for user user_name is not correct.
Description A FEP BDR application or a user attempted to execute a BDR-specific command on the specified NTM FEP but the “.rhost” file on the backup FEP does not exist or does not contain the name of the primary FEP.
Parameters backup_fep The name of the backup FEP as specified by the user in a centity command
user_name The name of the (FEP type) user who ran the command
Major
Corrective action Follow these steps:
......
1 Verify that the “.rhost” file exists on the backup FEP and includes the primary FEP name in the user’s home directory.
......
2 If the problem persists, report the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “centity” (p. A-13)
...... C-44 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... BDR 021
Message ID
BDR 020 BDR will not be activated on primary_fep because it is already active on backup_fep. Also, files will not be committed to the backup FEP.
Description The FEP BDR application has determined that the backup FEP has BDR active.
Parameters
primary_fep The name of the FEP that the BDR command was run on
backup_fep The name of the backup FEP as specified by the user in a centity command
Major
Corrective action Follow these steps:
......
1 Verify that the BDR is deactivated on the backup FEP.
......
2 Run bdr_deact on the backup fep to turn off BDR.
...... E ND OF STEPS ......
References “bdr_deact” (p. A-10) “centity” (p. A-13)
...... 190-406-737 Alcatel-Lucent — Internal C-45 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... BDR 022
Message ID
BDR 022 All the files were not copied to the backup FEP. FEP primary_fep has number BDR files and FEP backup_fep has number BDR files.
Description The bdr_commit command verifies that all the files were copied to the backup FEP. If there are less files on the backup FEP then the primary FEP, this message is logged to the bdrlog so that the customer knows that both systems are not in sync. The difference in the number of BDR files could be due to a permission problem on the backup FEP.
Parameters
primary_fep The name of the FEP system the command was run on
backup_fep The name of the backup FEP as specified by the user in a centity command
number The number of primary files on the primary FEP or the backup FEP
Major
Corrective action Follow these steps:
......
1 Run the bdr_commit command manually to determine if the problem persists.
...... E ND OF STEPS ......
References “bdr_commit” (p. A-8) “centity” (p. A-13)
...... C-46 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... CMD — User Commands Overview
Purpose This section provides all of the CMD error messages.
Messages in this section include:
• CMD 017
• CMD 019
• CMD 020
• CMD 021
• CMD 022
• CMD 023
• CMD 024
• CMD 025
...... 190-406-737 Alcatel-Lucent — Internal C-47 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... CMD 017
Message ID
CMD 017 Entity entity already active
Description This appears if you are trying to activate an entity that is already active.
Parameters
entity FEP entity number you are attempting to activate
Warning
Corrective action Verify that the entity is already active by using the rsentity command.
References “aentity” (p. A-3) “rsentity” (p. A-42)
...... C-48 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... CMD 019
Message ID
CMD 019 Entity entity not activated
Description This appears if an attempt to activate a FEP entity is unsuccessful. This may occur if there is a problem with the entity database. This may also occur if there is a problem sending an internal message to the ndc process or if there is a problem with shared memory.
Parameters
entity FEP entity number you are attempting to activate
Warning
Corrective action Follow these steps:
......
1 Enter ipcs -qa and redirect the output to a file.
......
2 Use the logCat command to capture errors that occurred a few minutes before this error.
......
3 Run edbview entity number and redirect the output to a file to capture the database entry for the entity experiencing problems.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37)
...... 190-406-737 Alcatel-Lucent — Internal C-49 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... CMD 020
Message ID
CMD 020 Entity entity activated
Description This message appears if a FEP entity was successfully activated.
Parameters
entity FEP entity number that was activated
Status
Corrective action This message is for your information only. No action is required.
References “aentity” (p. A-3)
...... C-50 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... CMD 021
Message ID
CMD 021 Error updating shared memory - code = code
Description This normally appears if a problem is encountered while a user is trying to update a FEP entity in the entity database when running the command deaentity.
Parameters
code Error code returned for use by FEP Customer Support
Warning
Corrective action Follow these steps:
......
1 Enter ipcs -qa and redirect the output to a file.
......
2 Use the logCat command to capture errors that occurred a few minutes before this error.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “deaentity” (p. A-27) “logCat” (p. A-37)
...... 190-406-737 Alcatel-Lucent — Internal C-51 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... CMD 022
Message ID
CMD 022 Entity entity deactivated
Description This message appears if a FEP entity was successfully deactivated.
Parameters
entity FEP entity number that was deactivated
Status
Corrective action This message is for your information only. No action is required.
References “deaentity” (p. A-27)
...... C-52 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... CMD 023
Message ID CMD 023 Can’t send message to NDC
Description This normally appears if a problem is encountered while a user is trying to send an internal entity deactivation message to the ndc process while running the command deaentity.
Warning
Corrective action Follow these steps:
......
1 Enter ipcs -qa and redirect the output to a file.
......
2 Use the logCat command to capture errors that occurred a few minutes before this error.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “deaentity” (p. A-27) “logCat” (p. A-37)
...... 190-406-737 Alcatel-Lucent — Internal C-53 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... CMD 024
Message ID
CMD 019 Entity entity not deactivated
Description This normally appears if an attempt to deactivate a FEP entity number is unsuccessful. This can occur if there is a problem sending an internal message to the ndc process or if there is a problem with shared memory.
Parameters
entity FEP entity number you are attempting to deactivate
Warning
Corrective action Follow these steps:
......
1 Enter ipcs -qa and redirect the output to a file.
......
2 Use the logCat command to capture errors that occurred a few minutes before this error.
......
3 Run edbview entity number and redirect the output to a file to capture the database entry for the entity experiencing problems.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “deaentity” (p. A-27) “logCat” (p. A-37)
...... C-54 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... CMD 025
Message ID
CMD 025 Entity entity already deactive
Description This normally appears if you are trying to deactivate an entity that is already deactive.
Parameters
entity FEP entity number you are attempting to deactivate
Warning
Corrective action Follow these steps:
......
1 Verify that the entity is already deactivated by using the rsentity command.
...... E ND OF STEPS ......
References “deaentity” (p. A-27) “rsentity” (p. A-42)
...... 190-406-737 Alcatel-Lucent — Internal C-55 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDCS — GTD-5 Event Data Collection Subsystem Overview
Purpose This section provides all of the EDCS error messages.
Messages in this section include:
• EDCS 001
• EDCS 002
• EDCS 003
• EDCS 004
• EDCS 005
• EDCS 021
• EDCS 022
...... C-56 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDCS 001
Message ID
EDCS 001 Program Initialized: program
Description An EDCS program has started. You would see this message normally after a startfep or reboot has been done.
Parameters
program Name of the program
Status
Corrective action Follow these steps:
......
1 IF this message occurred after a startfep or reboot was done, no action is required.
......
2 IF not, stop and start the FEP using the stopfep and startfep commands to clear this problem.
......
3 If the problem persists, stop the FEP and reboot it.
......
4 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-57 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDCS 002
Message ID
EDCS 002 Program Terminated: program
Description An EDCS program has stopped.
Parameters
program Name of the program
Status
Corrective action Follow these steps:
......
1 IF this message occurs as the FEP is shutting down, no action is required.
......
2 IF not, stop and start the FEP using the stopfep and startfep commands to clear this problem.
......
3 If the problem persists, stop the FEP and reboot it.
......
4 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-58 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDCS 003
Message ID
EDCS 003 DCOL: Init Failed: message
Description An initialization step in the EDCS data collector has failed.
Parameters
message What has failed
Critical
Corrective action Follow these steps:
......
1 Run ipcs -qa and ps -ef and redirect the output to a file.
......
2 Run logCat to capture errors from the previous few minutes.
......
3 Stop and start the FEP using the stopfep and startfep commands.
......
4 If the problem persists, stop the FEP and reboot it.
......
5 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-59 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDCS 004
Message ID EDCS 004 DCOL: message
Description This is a variable message logged by the EDCS data collector.
Parameters message Contents of the message
Status
Corrective action This message is for your information only. No action is required.
...... C-60 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDCS 005
Message ID
EDCS 005 DCOL LOG Message: message
Description The EDCS data collector has a problem logging data.
Parameters
message Description of the problem
Minor
Corrective action Follow these steps:
......
1 Run ipcs -qa and ps -ef and redirect the output to a file.
......
2 Run logCat to capture errors from the previous few minutes.
......
3 Stop and start the FEP using the stopfep and startfep commands.
......
4 If the problem persists, stop the FEP and reboot it.
......
5 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-61 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDCS 021
Message ID
EDCS 021 DCLMGR: message
Description This is a variable message logged by the EDCS data collector manager.
Parameters
message Contents of the message
Status
Corrective action This message is for your information only. No action is required.
...... C-62 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDCS 022
Message ID
EDCS 022 DCLMGR: errmsg
Description The EDCS data collector manager has an error.
Parameters
errmsg Contents of the error message
Major
Corrective action Follow these steps:
......
1 Run ipcs -qa and ps -ef and redirect the output to a file.
......
2 Run logCat to capture errors from the previous few minutes.
......
3 Stop and start the FEP using the stopfep and startfep commands.
......
4 If the problem persists, stop the FEP and reboot it.
......
5 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-63 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD — GTD-5 Data Distributor Overview
Purpose This section provides all of the EDD error messages.
Messages in this section include:
• EDD 001
• EDD 002
• EDD 003
• EDD 004
• EDD 005
• EDD 006
• EDD 007
• EDD 008
• EDD 009
• EDD 010
• EDD 011
• EDD 012
• EDD 013
• EDD 014
• EDD 015
• EDD 016
...... C-64 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDD 001
Message ID EDD 001 EDCSDD started
Description The EDCS data distributor started. You would normally see this message after startfep has been run or after the FEP has just been rebooted.
Status
Corrective action Follow these steps:
......
1 IF this message occurred after a startfep or reboot was done, no action is required.
......
2 IF not, stop and start the FEP using the stopfep and startfep commands to clear this problem.
......
3 If the problem persists, stop the FEP and reboot it.
......
4 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-65 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD 002
Message ID EDD 002 EDCSDD shutdown
Description EDCS data distributor is shut down. You would normally see this message after stopfep has been run. As a result, all GTD-5 switch data collection will terminate.
Status
Corrective action Follow these steps:
......
1 IF this message occurs as the FEP is shutting down, no action is required.
......
2 IF not, stop and start the FEP using the stopfep and startfep commands to clear this problem.
......
3 If the problem persists, stop the FEP and reboot it.
......
4 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-66 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDD 003
Message ID EDD 003 data pool environment not set up
Description A process tried to access an EDCS data pool but does not have the right environment. As a result of this error, GTD-5 switch data collection will terminate.
Major
Corrective action Follow these steps:
......
1 Log in as “fep” and do echo $EDCS_ROOT.
......
2 If it shows a non-empty value, use stopfep and startfep to restart the FEP application, which should clear the problem.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-67 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD 004
Message ID
EDD 004 cannot open pool data pool in EDCS_ROOT
Description A process failed to open a data pool in the EDCS environment. As a result of this error, GTD-5 switch data collection will probably terminate.
Parameters
pool The name of the data pool
EDCS_ROOT The environment for the EDCS application
Major
Corrective action Follow these steps:
......
1 Run the following commands: cd $EDCS_ROOT/pool ls -l Result: It should show “dc_pool” and “dd_pool”.
......
2 Stop and start the FEP application using the stopfep and startfep commands to clear this problem.
......
3 If the problem persists, stop the FEP and reboot it.
......
4 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-68 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-69 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD 005
Message ID
EDD 005 cannot attach channel number of pool data pool in EDCS_ROOT
Description A process failed to attach to a channel in a data pool in an EDCS environment. As a result of this error message, GTD-5 switch data collection will probably terminate.
Parameters
number The channel number
pool The name of the data pool
EDCS_ROOT The environment for the EDCS application
Major
Corrective action Follow these steps:
......
1 Run poolstatus -p pool and redirect the output to a file.
......
2 Stop and start the FEP application using the stopfep and startfep commands to clear this problem.
......
3 If the problem persists, stop the FEP and reboot it.
......
4 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-70 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDD 006
Message ID EDD 006 CCPRT environment not set up
Description A process tries to access EDCS CCPRT but does not have the right environment.
Major
Corrective action Follow these steps:
......
1 Log in as “fep” and do echo $CCP_RT_BASE.
......
2 If it shows a non-empty value, use stopfep and startfep to restart the FEP application, which should clear the problem.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-71 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD 007
Message ID EDD 007 CCPRT message queue initialization failed
Description A process failed to access a CCPRT message queue.
Major
Corrective action Follow these steps:
......
1 Run ipcs -qa and ps -ef and redirect the output to a file.
......
2 Use stopfep and startfep to restart the FEP application, which should clear the problem.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-72 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDD 008
Message ID
EDD 008 got DC message - message
Description The EDCS data distributor got a message from the data collector. This message may only appear when FEP Customer Support is contacted for fault isolation. This message is normally not logged on the FEP as it does not indicate a problem, and it would generate many messages, making it cumbersome to identify true error conditions.
Parameters
message The message from the EDCS data collector
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-73 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD 009
Message ID
EDD 009 got size bytes invalid data data from entity number
Description The EDCS data collector got a piece of invalid data from an entity. Valid data is considered to be a 30-second report, 5-minute report, or control/audit request/response. The FEP will also recognize a high-priority interrupt sent during a 5-minute report so a 30-second report may be sent on time. This could be the result of a noisy line, a network problem, a Datakit port problem, etc.
Parameters
size The size of the invalid data
data The first 30 bytes of the invalid data
number The entity number of the GTD-5 switch
Minor
Corrective action Follow these steps:
......
1 If this message appears frequently, run tlentity to see the data the FEP is receiving and compare that to what the switch really sends.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-74 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDD 010
Message ID
EDD 010 cannot put data from entity number into pool channel channel, errno=err
Description The EDCS data distributor failed to put a piece of data from a GTD-5 entity into a channel in “dd_pool”. This means this piece of data will be lost.
Parameters
number The entity number of the GTD-5 switch
channel The channel number (one for each GTD-5 translator process)
err The error number
Major
Corrective action Follow these steps:
......
1 Run poolstatus -p dd_pool and redirect the output to a file.
......
2 If this message appears frequently, run tlentity to see the data the FEP is receiving and compare that to what the switch really sends.
......
3 Report this information to FEP Customer Support as this should never happen.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-75 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD 011
Message ID
EDD 011 cannot put data from entity number into pool channel channel because pool is full
Description The EDCS data distributor failed to put a piece of data from a GTD-5 entity into a channel in “dd_pool” because that channel is full. This implies data loss for that entity.
Parameters
number The entity number of the GTD-5 switch
channel The channel number (one for each GTD-5 translator process)
Major
Corrective action Follow these steps:
......
1 Log in as “fep” and do appstat to see if all GTD-5 translator processes “ctlAud”, “transdisc”, and “trans5min” are running.
......
2 If not, use stopfep and startfep to restart the FEP application, which should clear the problem.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “appstat” (p. A-5) “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-76 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDD 012
Message ID
EDD 012 cannot send notice of pool channel channel data from entity number
Description The EDCS data distributor failed to notify a GTD-5 translator process to pick up a piece of data. This implies data loss for that entity; even though the data made it into the FEP, it was unable to reach its appropriate translator process and thus the data is lost.
Parameters
channel The channel number (one for each GTD-5 translator process)
number The entity number of the GTD-5 switch
Major
Corrective action Follow these steps:
......
1 Use stopfep and startfep to restart the FEP application, which should clear the problem.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-77 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD 013
Message ID
EDD 013 got partial message from channel channel of pool data pool due to reason
Description A process got part of a piece of data from a channel in a data pool. Data is expected to arrive as an entire message, not broken up into parts.
Parameters
channel The channel number
pool The name of the data pool
reason The reason why only part of the message was picked up
Minor
Corrective action Follow these steps:
......
1 If you are seeing this for several entities, stop and start the FEP application using the stopfep and startfep commands.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-78 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDD 014
Message ID
EDD 014 put partial message into channel channel of pool data pool
Description A process put part of a piece of data into a channel in a data pool.
Parameters
channel The channel number
pool The name of the data pool
Minor
Corrective action Follow these steps:
......
1 If you are seeing this for several entities, stop and start the FEP application using the stopfep and startfep commands.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-79 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... EDD 015
Message ID
EDD 015 size bytes entity number type data collected at time
Description A piece of data from a GTD-5 entity was collected. This message may only appear when FEP Customer Support is contacted for fault isolation. This message is normally not logged on the FEP as it does not indicate a problem, and it would generate many messages, making it cumbersome to identify true error conditions.
Parameters
size The size of the data in bytes
number The entity number
type The data type
time The data collection time
Status
Corrective action This message is for your information only. No action is required.
...... C-80 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... EDD 016
Message ID
EDD 016 got size bytes non-data message from entity number
Description A message other than the standard data from a GTD-5 entity was collected. This is typically a high-priority interrupt sent during a 5-minute report so a 30-second report can come out on time. Also, a low-priority resume message would generate this message.
Parameters
size The size of the message in bytes
message The first 30 bytes of the message
number The entity number
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-81 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC — Internet Protocol Network Data Collector Overview
Purpose This section provides all of the IPNDC error messages.
Messages in this section include:
• IPNDC 101
• IPNDC 111
• IPNDC 114
• IPNDC 115
• IPNDC 116
• IPNDC 117
• IPNDC 118
• IPNDC 119
• IPNDC 120
• IPNDC 121
• IPNDC 122
• IPNDC 123
• IPNDC 125
...... C-82 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
• IPNDC 126
• IPNDC 127
• IPNDC 128
• IPNDC 129
• IPNDC 130
• IPNDC 132
• IPNDC 133
• IPNDC 134
• IPNDC 135
• IPNDC 139
• IPNDC 140
• IPNDC 144
• IPNDC 145
• IPNDC 146
• IPNDC 149
• IPNDC 150
• IPNDC 152
• IPNDC 153
...... 190-406-737 Alcatel-Lucent — Internal C-83 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
• IPNDC 154
• IPNDC 155
• IPNDC 156
• IPNDC 157
• IPNDC 158
• IPNDC 159
• IPNDC 161
• IPNDC 162
• IPNDC 165
• IPNDC 166
• IPNDC 167
• IPNDC 168
• IPNDC 169
• IPNDC 170
• IPNDC 171
• IPNDC 172
• IPNDC 173
• IPNDC 174
...... C-84 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 101
Message ID IPNDC 101 Data collector started - entity reactivation complete
Description The ipndc process has started and has reactivated all entities that were previously active before the FEP was brought down. Typically, you would see this message after a startfep was done or a reboot was done.
Status
Corrective action Follow these steps:
......
1 IF this message appears after a startfep or reboot was done, no action is required.
......
2 If this message occurs at any other time, you should do logCat to look for reasons why the ipndc process terminated and had to restart.
......
3 If this error occurs repeatedly, there is a serious problem preventing the ipndc process from running, and the problem should be referred to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “startfep” (p. A-46)
...... 190-406-737 Alcatel-Lucent — Internal C-85 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 111
Message ID
IPNDC 111 Data from wrong interval; entity clli, data type dtype
Description The data sent back from the specified CLLI code contained a timestamp different from what the FEP expected. This normally indicates a clock synchronization problem between the switch and the FEP.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Warning
Corrective action Follow these steps:
......
1 Contact switch personnel to check the time on the switch.
......
2 If it differs from the FEP, the switch's time should be reset, as the FEP automatically synchronizes to NTM.
...... E ND OF STEPS ......
...... C-86 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 114
Message ID
IPNDC 114 link down; entity clli, channel chan_no
Description This error means the link has gone down for the specified channel for the specified CLLI code. This message may occur initially at entity activation time. The FEP will try to bring the link back up for the specified channel automatically. If this attempt is successful, you will see the IPNDC 115 message logged.
Parameters
clli Name of the switch
chan_no Logical channel number. The valid value is 1, 2 or 3.
Status
Corrective action Follow these steps:
......
1 If this occurs frequently, use the tlentity command to check the link status of the specified entity.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-87 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 115
Message ID
IPNDC 115 link up; entity clli, channel chan_no
Description The link has been restored for the specified channel for the specified CLLI code. Data collection will resume automatically for this channel. Under some conditions, this message will be logged a few times. This signifies the ipndc process is having problems collecting data even though the link is up. Under such cases, this message will follow message IPNDC 118.
Reference: “Corrective action” (p. C-92)
Parameters clli Name of the switch
chan_no Logical channel number. The valid value is 1, 2 or 3.
Status
Corrective action This message is for your information only. No action is required.
...... C-88 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 116
Message ID
IPNDC 116 Wrong data received; entity clli, data type dtype, received si_type
Description The FEP polled the specified entity for dtype data, but received a different type of data. Most likely, the switch responded with 30-second data to a 5-minute poll or vice versa.
Parameters
clli Name of the switch
dtype Data type, such as 5min
si_type The data type switch sent back
Warning
Corrective action Follow these steps:
......
1 Use the tlentity command to verify that the switch will respond correctly to a poll for the specified data type.
......
2 If the switch does not respond correctly, refer this problem to your switch personnel.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-89 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 117
Message ID
IPNDC 117 Channel reset; entity clli, channel chan_no
Description The FEP detected protocol errors, making it impossible to collect data. This is often caused by a noisy data link or reinitialization of the switch software that communicates with the FEP.
Parameters
clli Name of the switch
chan_no Logical channel number. The valid value is 1, 2 or 3.
Major
Corrective action Follow these steps:
......
1 If the problem occurs frequently, have the data link checked out.
......
2 If the data link is OK, use the tlentity command to send a few polls on channel chan_no.
......
3 After sending each poll, check the status of the link using the tlentity STATUS command.
......
4 If the channel is reset again, confer with switch personnel to verify that they are using the correct version of the protocol software.
...... C-90 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 As a last resort, have switch personnel compare protocol parameters of this switch with another switch known to have stable communications to this same FEP.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-91 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 118
Message ID
IPNDC 118 Data timeout; entity clli, data type dtype
Description The FEP sent a poll to the specified entity for the specified data type, but received a timeout message from the switch.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to see if the switch responds correctly to the specified poll.
......
2 If it doesn't, refer the problem to your switch personnel.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-92 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 119
Message ID
IPNDC 119 Time conflict; entity clli, data type dtype
Description The FEP sent a poll to the specified entity for the specified data type but received a “time conflict” response. This normally means the FEP polled the switch inside one of its lockout windows when the switch was updating its holding registers and could not send data to the FEP. This is usually caused by the switch's time being out of sync with the FEP's time.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Warning
Corrective action Follow these steps:
......
1 Check the clocks.
......
2 If they are not in sync, reset the switch's clock.
......
3 If the clocks are synchronized, the switch may not be in EADAS mode. Ask switch personnel to verify this.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-93 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 120
Message ID
IPNDC 120 Invalid request; entity clli, data type dtype, poll b1 b2
Description The FEP sent a poll to the switch for the specified data type, but the switch sent back an invalid request message, meaning the switch did not recognize the poll we sent it. However, the switch may also respond this way if the switch is unable to send the requested data.
Parameters
clli Name of the switch
dtype Data type, such as 5min
b1 b2 The poll bytes received by switch
Status
Corrective action Follow these steps:
......
1 Determine if the poll the FEP sent was valid or not.
Reference: The man page for tlentity lists all valid polls.
......
2 If the poll is invalid, then refer this problem to FEP Customer Support.
......
3 Assuming the poll is valid, there is probably a problem in the switch, in which case you should refer this problem to your switch personnel.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-94 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 121
Message ID
IPNDC 121 Data overwritten; entity clli, data type dtype
Description This error means that while the FEP was collecting data of type dtype from the specified entity, the data was overwritten in the switch's holding registers by the next interval's data. When the switch detects this, it sends an “overwritten data” message. This message should rarely occur, if ever. For it to occur, the poll would have to have been sent before the start of the lockout period of the switch, but data collection took so long that the FEP was still collecting data when the holding registers were updated.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Minor
Corrective action Follow these steps:
......
1 Verify that the switch and FEP clocks are in sync.
......
2 If they are off, reset the switch's clock, as the FEP automatically synchronizes to NTM.
......
3 If this does not clear the problem, notify FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-95 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 122
Message ID
IPNDC 122 switch in min-mode; entity clli, data type dtype
Description When the FEP polled the switch for data, the switch sent back a min-mode message, meaning that the switch (5ESS switch only) is in some type of minimal or recovery mode that prevents it from sending data to FEP.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Warning
Corrective action Follow these steps:
......
1 This error should not be seen frequently or for extended periods of time. If it is, contact the switch operating or maintenance personnel to see if their switch is experiencing problems.
...... E ND OF STEPS ......
...... C-96 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 123
Message ID
IPNDC 123 protocol error; entity clli, data type dtype at channel chan_no
Description Protocol errors occurred during the collection of data type dtype from the specified entity, resulting in data not being received properly. This message will often be seen in conjunction with another error message that gives details of the protocol link problem.
Parameters
clli Name of the switch
dtype Data type, such as 5min
chan_no Logical channel number: 1, 2 or 3
Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to check the status of the link. Most likely, you will be able to trace this to some sort of hardware problem.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-97 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 125
Message ID
IPNDC 125 SPCS unequipped for requested data type; entity clli, data type dtype
Minor
Description The FEP sent a poll to the specified entity for dtype data and received a “not equipped” response. This means the switch is not configured to generate the requested type of data.
Parameters clli Name of the switch
dtype Data type, such as 5min
Corrective action Follow these steps:
......
1 Use tlentity to manually poll the switch for dtype data.
......
2 If this works, reactivate the entity and see if the problem disappears.
......
3 If the switch fails the tlentity poll, contact the switch person to verify that the switch is set up to respond to the specified data type poll.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-98 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 126
Message ID
IPNDC 126 Received small data block; entity clli, data type dtype, size=size
Description The ipndc process received a data block too small to process. For example, the first data block in the message was smaller than the length of a message header.
Parameters
clli Name of the switch
dtype Data type, such as 5min
size Size of received date in bytes
Minor
Corrective action Follow these steps:
......
1 Use tlentity to verify that the switch is sending correctly formatted messages.
......
2 If not, the switch has a problem or data is being corrupted by the network between the switch and the FEP.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-99 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 127
Message ID
IPNDC 127 Bad number of sections; entity clli, data type dtype, sections=sctcnt
Description The ipndc process received a message with an incorrect number of sections. The number of sections is calculated from the message header length, which must range from 0 to 255.
Parameters
clli Name of the switch
dtype Data type, such as 5min
sctcnt Sections of received data
Minor
Corrective action Follow these steps:
......
1 Use tlentity to verify that the switch is sending correctly formatted messages.
......
2 If not, the switch has a problem or data is being corrupted by the network between the switch and the FEP.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-100 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 128
Message ID
IPNDC 128 Clock mismatch of secs seconds; entity clli
Description The FEP's clock and switch's clock are off by secs seconds. A positive number of seconds indicates the switch clock is ahead of the FEP clock. A negative number of seconds indicates the switch clock is behind the FEP clock.
Parameters
clli Name of the switch
secs Number of seconds
Minor
Corrective action Follow these steps:
......
1 Set the specified switch's time to match the FEP, as the FEP clock automatically synchronizes to the NTM clock.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-101 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 129
Message ID
IPNDC 129 Data collection started; entity clli
Description This message occurs whenever data collection is started on an entity. You would see this after doing the aentity command or after a startfep was done or the FEP was rebooted.
Parameters
clli Name of the switch
Status
Corrective action No action is required. This message is for your information only.
References “aentity” (p. A-3) “startfep” (p. A-46)
...... C-102 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 130
Message ID IPNDC 130 Data collection stopped; entity clli
Description Data collection stopped for entity clli. You would see this after doing the deaentity command.
Parameters
clli Name of the switch
Status
Corrective action No action is required. This message is for your information only.
References “deaentity” (p. A-27)
...... 190-406-737 Alcatel-Lucent — Internal C-103 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 132
Message ID
IPNDC 132 Received multiple request for entity entno for NM req
Description The FEP can only process one audit at a time or only one control per entity at a time. This error means the ipndc process received a second request for an NTM audit or control as specified by req while it was still processing a previous one.
Parameters
req Audit or control
entno The entity number that received multiple requests
Warning
Corrective action Follow these steps:
......
1 If this error occurs a number of times, check with NTM personnel to verify that they are really sending multiple requests.
......
2 If the problem persists, deactivate and reactivate the entity.
......
3 If the problem still does not disappear, stop and start the FEP application using the stopfep command followed by startfep command.
......
4 If this still does not clear the problem, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
...... C-104 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “deaentity” (p. A-27) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-105 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 133
Message ID
IPNDC 133 Can’t open UNIX file, entity clli data type dtype
Description The ipndc process is trying to write dtype data for the specified entity to a file so it can be shipped to NTM. However, it is unable to open the file for writing.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if the “/raw” file system is out of space. If the “capacity” column shows a value near 100%, then the “/raw” file system is not being properly cleaned up.
......
2 Verify that the directory to which the file is being written exists by entering ls -l /raw/clli/dtype/ where clli and dtype are specified in the error message. If the directory does not exist, make sure the clli code is correct by doing rsentity clli.
......
3 If the directory does not exist, deactivate the entity, delete the entity, recreate the entity, and then finally reactivate the entity.
......
4 If the directory still fails to be built, refer this problem to FEP Customer Support.
...... E ND OF STEPS ......
...... C-106 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... 190-406-737 Alcatel-Lucent — Internal C-107 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 134
Message ID
IPNDC 134 Can't write UNIX file; entity clli data type dtype
Description The ipndc process is trying to write dtype data for the specified entity to a file so it can be shipped to NTM. However, it is unable to write to the file.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if the “/raw” file system is out of space. If the “capacity” column shows a value near 100%, then the “/raw” file system is not being properly cleaned up.
......
2 Verify that the directory to which the file is being written exists by entering ls -l /raw/clli/dtype/ where clli and dtype are specified in the error message. If the directory does not exist, make sure the clli code is correct by doing rsentity clli.
......
3 If the directory does not exist, deactivate the entity, delete the entity, recreate the entity, and then finally reactivate the entity.
......
4 If the directory still fails to be built, refer this problem to FEP Customer Support.
...... E ND OF STEPS ......
...... C-108 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... 190-406-737 Alcatel-Lucent — Internal C-109 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 135
Message ID IPNDC 135 Message to NMT failed
Description The ipndc process failed in an attempt to pass information to the nmt process. This may be a temporary problem caused by an overflow of space for messages in the system, or it may mean the nmt process has stopped running.
Critical
Corrective action Follow these steps:
......
1 To clear the message passing problem, restart the FEP application by doing stopfep followed by startfep.
......
2 If the message still continues to appear, bring down the FEP application by doing stopfep and then reboot the FEP.
......
3 If this error occurs consistently, do ipcs -qa and ps -ef while the error appears and redirect the output to a file; then report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-110 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 139
Message ID
IPNDC 139 Can't close UNIX file; entity clli data type dtype
Description The ipndc process is trying to write dtype data for the specified entity to a file so it can be shipped to NTM. However, it is unable to close the file it has written to close the file it has written to.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if the “/raw” file system is out of space. If the “capacity” column shows a value near 100%, then the “/raw” file system is not being properly cleaned up.
......
2 Verify that the directory to which the file is being written exists by entering ls -l /raw/clli/dtype/ where clli and dtype are specified in the error message. If the directory does not exist, make sure the clli code is correct by doing rsentity clli.
......
3 If the directory does not exist, deactivate the entity, delete the entity, recreate the entity, and then finally reactivate the entity.
......
4 If the directory still fails to be built, refer this problem to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-111 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... C-112 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 140
Message ID
IPNDC 140 Received unknown message type - mtype
Description The ipndc process received an unrecognizable message from another FEP process.
Parameters
mtype A digit representing a message type, the valid message types are: 1. NM request data 2. Activate an entity 3. Deactivate an entity 4. Dump an entity queues polls
Minor
Corrective action Follow these steps:
......
1 If this message appears consistently, restart the FEP application by entering stopfep followed by startfep.
......
2 If this does not clear the problem, enter ipcs -aq and ps -ef and redirect the output to a file.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-113 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 144
Message ID
IPNDC 144 Received invalid poll command; entity clli data type dtype
Description The ipndc process received an invalid poll command from the nmt process.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Warning
Corrective action Follow these steps:
......
1 Deactivate and reactivate the specified entity.
......
2 If this message still appears consistently, restart the FEP application by entering stopfep followed by startfep.
......
3 If this does not clear the problem, enter ipcs -aq tand ps -ef and redirect the output to a file.
......
4 Use the logCat command to search for any recent NMT messages indicating why this happened.
......
5 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-114 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “deaentity” (p. A-27) “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-115 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 145
Message ID
IPNDC 145 Received invalid entity activation; entity clli pdn pdno
Description The ipndc process was sent an invalid activation command and thus failed to activate entity clli.
Parameters
clli Name of the switch
pdno Protocol number
Minor
Corrective action Follow these steps:
......
1 If this message is appearing for only one entity, then delete and recreate the entity and then activate the entity.
......
2 If this does not clear the problem or if this message is coming out for several entities, restart the FEP application using stopfep followed by startfep.
......
3 If the problem still persists, use command edbview entno of clli and redirect the output to a file.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-116 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “centity” (p. A-13) “delentity” (p. A-29) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-117 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 146
Message ID
IPNDC 146 mpx write failed; channel entno, errno errno
Description The ipndc process's attempt to send a poll for the specified entity on the specified channel failed. A failure indicates some problem either with the link or the ipndc's internal devices. The ipndc process will try to recover the link automatically once the error occurs.
Parameters
entno The entity number
errno UNIX errno
Minor
Corrective action Follow these steps:
......
1 Use the rsentity entno command to determine whether or not there is data loss for this entity.
......
2 If there is no data loss, then no action is required.
......
3 If, however, this entity is experiencing data loss and this error occurs frequently and along with other ipndc errors (such as IPNDC 114, IPNDC 149, IPNDC 150), then you should run the tlentity command to establish end-to-end communication and send polls on all the channels.
......
4 If you are able to successfully send polls and get back data, activate the entity using the aentity command.
......
5 If the problem still persists:
...... C-118 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
a. Verify that the SLM is in service in Datakit, using the verify slm command on the Datakit VCS console. b. Verify that the dialstring to the entity is correct, using the rsentity entno command.
......
6 If the problem still does not go away, restart the FEP application using the stopfep and startfep commands.
......
7 If this doesn't clear the problem, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “rsentity” (p. A-42) “startfep” (p. A-46) “stopfep” (p. A-47) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-119 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 149
Message ID
IPNDC 149 Entity entno in invalid state; reinitializing data collection
Description This error message means the ipndc process considered one of the internal data structures associated with entity entno to be invalid. The ipndc process is reinitializing the entity in an attempt to resume its data collection. If this does not clear the problem, error messages IPNDC 114 and IPNDC 150 may be generated.
Parameters
entno The entity number being reinitialized
Minor
Corrective action Follow these steps:
......
1 Run the tlentity command to establish end-to-end communication and send polls on all the channels.
......
2 If you are able to successfully send polls and get back data, activate the entity using the aentity command.
......
3 If the problem still does not go away, restart the FEP application using the stopfep and startfep commands.
......
4 If this doesn't clear the problem, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
...... C-120 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “rsentity” (p. A-42) “startfep” (p. A-46) “stopfep” (p. A-47) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-121 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 150
Message ID
IPNDC 150 Entity entno in invalid state; stopping data collection
Description Error message IPNDC 150 normally follows error message IPNDC 149 if the ipndc process found an internal data structure associated with the specified entity to be inconsistent. This means the ipndc process could not automatically reinitialize the data structure and has stopped trying to collect for this entity until 30 minutes has passed. This message will be generated every 30 minutes until the data starts being collected from the switch.
Parameters
entno The entity number
Minor
Corrective action Follow these steps:
......
1 Try deactivating and activating the entity to see if the problem persists.
......
2 Run the tlentity command to establish end-to-end communication and send polls on all the channels.
......
3 If you are able to successfully send polls and get back data, activate the entity using the aentity command.
......
4 If the problem still does not go away, restart the FEP application using the stopfep and startfep commands.
...... C-122 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 If this doesn't clear the problem, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “deaentity” (p. A-27) “rsentity” (p. A-42) “startfep” (p. A-46) “stopfep” (p. A-47) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-123 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 152
Message ID
IPNDC 152 Can't access edb_fld field of ent entno in entity database
Description The ipndc process is trying to access a field in shared memory for the specified entity but cannot.
Parameters
entno The entity number
edb_fld The entity database field name
Minor
Corrective action Follow these steps:
......
1 Try deactivating and reactivating the entity using the deaentity and aentity commands.
......
2 If you continue to see this error, deactivate the entity, delete the entity, recreate the entity and reactivate the entity.
......
3 If the problem still continues, refer it to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... C-124 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 153
Message ID
IPNDC 153 Entity entno database field edb_fld had bad value
Description This error occurred while trying to activate an office, either via the aentity command or when the ipndc process initialized as the FEP application was started.
Parameters
entno The entity number
edb_fld The entity database field name
Minor
Corrective action Follow these steps:
......
1 If this message is coming out for only one entity, then deactivate the entity and reactivate it using the deaentity and aentity commands.
......
2 If you continue to see this error, deactivate the entity, delete the entity (using delentity), recreate the entity (using centity), and reactivate the entity.
......
3 If this message is coming out for several entities, then it’s likely the entity database is corrupt. Reinitialize it by running stopfep followed by startfep.
......
4 If the problem still continues, refer it to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-125 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29) “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-126 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 154
Message ID
IPNDC 154 Terminated by signal sig_no
Description The ipndc process was killed by the specified signal. There are two reasons for this. Either there is a fatal FEP system problem, or the system was gracefully shut down with the stopfep command. If the FEP was not shutting down, the ipndc process will respawn automatically.
Parameters
sig_no The signal number
Major
Corrective action Follow these steps:
......
1 If the FEP was brought down using the stopfep command, then this message is for your information only.
......
2 If however, the FEP was not brought down and the ipndc process died on its own, use the logCat command to determine why the ipndc process restarted itself.
......
3 If this message occurs frequently, refer this error to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-127 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 155
Message ID IPNDC 155 Can't lock into memory
Description In order to function, the ipndc process locks itself into core memory almost immediately upon coming up. If for some reason it cannot do this, the message above will be generated and the ipndc process will exit. BaseWorX functions will respawn the ipndc process up to four times, so it's possible that you could see four of these messages in short order.
Major
Corrective action Follow these steps:
......
1 Restart the FEP application by entering stopfep followed by startfep.
......
2 If the message reappears, stop the FEP application and reboot the computer.
......
3 If the message still appears, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-128 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 156
Message ID IPNDC 156 Can't access shared memory
Description The ipndc process could not access shared memory, indicating a FEP system problem. This will restrict the ipndc process from communicating with other FEP processes and from accessing its database.
Major
Corrective action Follow these steps:
......
1 Restart the FEP application by entering stopfep followed by startfep.
......
2 If the message reappears, stop the FEP application and reboot the computer.
......
3 If the message still appears, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-129 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 157
Message ID
IPNDC 157 Can't open file message
Description The ipndc process could not open a device file to collect data from a synchronized entity.
Parameters
message Contains the entity CLLI code along with a (VPORT) error message
Major
Corrective action Follow these steps:
......
1 Run the tlentity command to establish end-to-end communication and send polls on all the channels.
......
2 If you are able to successfully send polls and get back data, activate the entity using the aentity command.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “rsentity” (p. A-42) “tlentity” (p. A-48)
...... C-130 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 158
Message ID
IPNDC 158 Can't read file message
Description The ipndc process could not read from a device file to collect data from a synchronized entity.
Parameters
message This could be one of two messages: 1. Channel of entity entno (produces Major alarm) 2. 0, n_read=byte errno=errno (produces Minor alarm). Ignore the “0”; it means the entity is a synchronous entity (5ESS/DMS switches)
entno The entity number of the entity experiencing problems
errno The error number returned from the read failure
Major, Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to establish end-to-end communication and send polls on all the channels.
......
2 If you are able to successfully send polls and get back data, activate the entity, using the aentity command.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “rsentity” (p. A-42) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-131 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 159
Message ID IPNDC 159 Can't write file
Description The ipndc process could not write to a device file to poll a synchronized entity.
Warning
Corrective action Follow these steps:
......
1 If this message occurs frequently, contact FEP Customer Support.
...... E ND OF STEPS ......
...... C-132 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 161
Message ID
IPNDC 161 Can't enable messages for proc_name
Description The ipndc process could not enable messages from the specified proc_name. This will inhibit reception of service requests from other FEP processes and users.
Parameters
proc_name Process name like ipndc
Major
Corrective action Follow these steps:
......
1 Restart the FEP application by entering stopfep followed by startfep.
......
2 If the message reappears, stop the FEP application and reboot the computer.
......
3 If the message still appears, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-133 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 162
Message ID
IPNDC 162 Can't disable messages for proc_name
Description The ipndc process could not disable messages for the specified process.
Parameters
proc_name Process name like ipndc
Warning
Corrective action Follow these steps:
......
1 If this message occurs frequently, contact FEP Customer Support.
...... E ND OF STEPS ......
...... C-134 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 165
Message ID
IPNDC 165 Invalid switch data type - dtype, MsgQid = ID
Description The ipndc process is calling a routine to write data it collected to a file, but the specified data type is invalid. This may be a software error in the ipndc process.
Parameters
dtype Data type, such as 5min
ID Number representing a process, such as 0x601 - ipndc
Major
Corrective action Follow these steps:
......
1 Refer this error to FEP Customer Support.
Note: You'll probably need to do stopfep followed by startfep to clear the problem (possibly reboot if stopfep and startfep don't work), but it would be beneficial to contact FEP Customer Support first so they can analyze the FEP in its current state.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-135 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 166
Message ID
IPNDC 166 Memory allocation for bufname failed
Description The ipndc process could not allocate more memory. This may be a software error in the ipndc process.
Parameters
bufname Buffer name, e.g., receive buffer, NM poll buffer
Major
Corrective action Follow these steps:
......
1 Refer this error to FEP Customer Support.
Note: You'll probably need to do stopfep followed by startfep to clear the problem (possibly reboot if stopfep and startfep don't work), but it would be beneficial to contact FEP Customer Support first so they can analyze the FEP in its current state.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-136 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 167
Message ID
IPNDC 167 Get file status failed for file fpath
Description The ipndc process stores collected traffic data in the “/raw/clli/tmp/file” file.
It then links the “/raw/clli/tmp/file” to either the “/raw/clli/5min/file”, the “/raw/clli/aud/file”, or the” /raw/clli/ctl/file” (depending on the type of data that was collected) and then finally unlinks the “/raw/clli/tmp/file” file.
This message means the ipndc process could not access the “/raw/clli/tmp/file” file.
Parameters
fpath Full path to the file name
Major
Corrective action Follow these steps:
......
1 Run ls -l /raw/clli, where clli is embedded in the specified fpath, to verify that the data directory exists for this entity.
......
2 If the directory does not exist, deactivate the entity, delete the entity, recreate the entity, and then finally reactivate the entity.
......
3 If the directory still fails to be built, or the directory exists but this message is still being logged, refer this problem to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-137 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... C-138 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 168
Message ID
IPNDC 168 Link to file fpath failed
Description The ipndc process stores collected traffic data in the “/raw/clli/tmp/file” file.
It then links the “/raw/clli/tmp/file” to either the “/raw/clli/5min/file”, the “/raw/clli/aud/file”, or the “/raw/clli/ctl/file” (depending on the type of data that was collected) and then finally unlinks the “/raw/clli/tmp/file”.
This message means the ipndc process could not link the “/raw/clli/tmp/file” file to the proper file as described above.
Parameters
fpath Full path to the file name
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if the “/raw” file system is out of space.
......
2 If the “capacity” column shows a value near 100%, then the “/raw” file system is not being properly cleaned up.
......
3 Contact FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-139 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 169
Message ID
IPNDC 169 Sending dtype poll to entity entno, channel chan_no
Description The ipndc process is polling the specified entity for dtype data on the specified channel. This message may only appear when FEP Customer Support is contacted for fault isolation. This message is normally not logged on the FEP as it does not indicate a problem, and it would generate many messages, making it cumbersome to identify true error conditions.
Parameters
dtype Data type
entno Entity number
chan_no Logical channel number: 1, 2 or 3
Status
Corrective action This message is for your information only. No action is required.
...... C-140 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 170
Message ID
IPNDC 170 Timeout of dtype poll for entity entno, channel chan_no
Description The ipndc process has timed out waiting for a response from a particular switch for the specified data type. The ipndc process will repoll. The FEP will allow 2 minutes to collect 5-minute data. The FEP will allow 1 minute to collect 30-second data.
Parameters
dtype Data type
entno Entity number
chan_no Logical channel number: 1, 2 or 3
Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to see if the switch responds quickly to the specified poll.
......
2 If it doesn't, the problem may either be in the switch or in the network between the switch and the FEP.
......
3 Ask switch personnel if they see the poll coming into the switch.
......
4 If they do see the poll and are responding, chances are it's a networking problem.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-141 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 171
Message ID
IPNDC 171 dtype poll for entity entno, channel chan_no result
Description The ipndc process sent the specified poll — but instead of getting back the expected dtype data, it got back result. The ipndc process will repoll.
Parameters
dtype Data type
entno Entity number
chan_no Logical channel number: 1, 2 or 3
result Result sent back by the process
Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to see if the FEP receives valid data to the specified poll.
......
2 If it doesn't, the problem may either be in the switch or in the network between the switch and the FEP.
......
3 Ask switch personnel if they see the poll coming into the switch.
......
4 If they do see the poll and believe the switch is responding correctly, chances are it is a networking problem corrupting the data.
...... E ND OF STEPS ......
...... C-142 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-143 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... IPNDC 172
Message ID
IPNDC 172 Received nbyte byte response to dtype poll for entity entno, channel chan_no
Description The ipndc process received nbyte bytes of data back for the specified poll. This message may only appear when FEP Customer Support is contacted for fault isolation. This message is normally not logged on the FEP as it does not indicate a problem, and it would generate many messages, making it cumbersome to identify true error conditions.
Parameters
dtype Data type
entno Entity number
chan_no Logical channel number: 1, 2 or 3
nbyte Number of bytes
Status
Corrective action This message is for your information only. No action is required.
...... C-144 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 173
Message ID
IPNDC 173 Data collector ipndcno cannot open /read/usra/tdms/ipndc/dksleep, using default value of secs seconds
Description During the startup of the ipndc process (whether it be after startfep or a reboot has been done), it reads the “/usra/tdms/ipndc/dksleep” file, to determine how many seconds it should wait between entity activations. This is done so the Datakit controller does not get too many call setup requests at the same time. This message means the ipndc process could not read the “/usra/tdms/ipndc/dksleep” file, so it is using the default value of secs seconds to sleep between entity activations.
Parameters
ipndcno IPNDC number: 1. 0 - 5ESS/DMS 2. 1 - GTD-5 monitored 3. 2 - GTD-5 LSSGR-like
secs Number of seconds
Minor
Corrective action You have three options to recover this file so it will be accessible the next time the ipndc process is started when startfep is done:
......
1 If you want to use the standard values for this file delivered with the FEP application, become “root” and enter: echo “3” > /usra/tdms/ipndc/dksleep chown root /usra/tdms/ipndc/dksleep chgrp tdms /usra/tdms/ipndc/dksleep ......
2 You could alternatively restore “/usra/tdms/ipndc/dksleep” from your latest Dynamic Data backup.
...... 190-406-737 Alcatel-Lucent — Internal C-145 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
3 If neither of the above are successful, contact FEP Customer Support. They will help you recreate this file with appropriate values.
...... E ND OF STEPS ......
References “Restoring dynamic data (all or some)” (p. 3-72)
...... C-146 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 174
Message ID
IPNDC 174 Data collector ipndcno sleep interval between activates will be secs seconds
Description During the startup of the ipndc process, it reads the “/usra/tdms/ipndc/dksleep” file, to determine how many seconds it should wait between entity activations. This is done so the Datakit controller does not get too many call setup requests at the same time. This message means the ipndc process will sleep secs seconds between each entity activation (after startfep or reboot has been done).
Parameters
ipndcno IPNDC number: 1. 0 - 5ESS/DMS 2. 1 - GTD-5 monitored 3. 2 - GTD-5 LSSGR-like
secs Number of seconds
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-147 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... LM — BaseWorX Log Manager Overview
Purpose This section provides all of the LM error messages.
Messages in this section include:
• LM 001
...... C-148 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... LM 001
Message ID
LM 001 log management message
Description The BaseWorX logmgr process will log a message for each process it is responsible for managing (see the output of appstat for a list of processes). As each process is brought up (after a startfep or reboot has been done), the logmgr process will log this message. In addition if a process is terminated (whether by stopfep or the process died on its own), logmgr will also log this message. In general, you can ignore this message. We expect this message to appear when processes controlled by the logmgr are started or stopped.
Parameters
log management messageInformation that includes the date and time, process name and whether the process completed OK or abnormally. If the process completed abnormally, make a note of the return code and exit status.
Status
Corrective action This message is for your information only. No action is required.
References “appstat” (p. A-5) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-149 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC — Network Data Collector Overview
Purpose This section provides all of the NDC error messages.
Messages in this section include:
• NDC 101
• NDC 111
• NDC 114
• NDC 115
• NDC 116
• NDC 117
• NDC 118
• NDC 119
• NDC 120
• NDC 121
• NDC 122
• NDC 123
• NDC 125
...... C-150 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
• NDC 126
• NDC 127
• NDC 128
• NDC 129
• NDC 130
• NDC 132
• NDC 133
• NDC 134
• NDC 135
• NDC 139
• NDC 140
• NDC 144
• NDC 145
• NDC 146
• NDC 149
• NDC 150
• NDC 152
• NDC 153
...... 190-406-737 Alcatel-Lucent — Internal C-151 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
• NDC 154
• NDC 155
• NDC 156
• NDC 157
• NDC 158
• NDC 159
• NDC 161
• NDC 162
• NDC 165
• NDC 166
• NDC 167
• NDC 168
• NDC 169
• NDC 170
• NDC 171
• NDC 172
• NDC 173
• NDC 174
...... C-152 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 101
Message ID NDC 101 Data collector started - entity reactivation complete
Description The ndc process has started and has reactivated all entities that were previously active before the FEP was brought down. Typically, you would see this message after a startfep was done or a reboot was done.
Status
Corrective action Follow these steps:
......
1 No action is required as long as this message appears after a startfep or reboot was done.
......
2 If this message occurs at any other time, use logCat to look for reasons why the ndc process terminated and had to restart.
......
3 If this error occurs repeatedly, there is a serious problem preventing the ndc process from running, and the problem should be referred to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “startfep” (p. A-46)
...... 190-406-737 Alcatel-Lucent — Internal C-153 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 111
Message ID
NDC 111 Data from wrong interval; entity clli, data type dtype
Description The data sent back from the specified CLLI code contained a timestamp different from what the FEP expected. This normally indicates a clock synchronization problem between the switch and the FEP.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Warning
Corrective action Follow these steps:
......
1 Contact switch personnel to check the time on the switch.
......
2 If it differs from the FEP, the switch's time should be reset, as the FEP automatically synchronizes to NTM.
...... E ND OF STEPS ......
...... C-154 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 114
Message ID
NDC 114 link down; entity clli, channel chan_no
Description This error means the link has gone down for the specified channel for the specified CLLI code. This message may occur initially at entity activation time. The FEP will try to bring the link back up for the specified channel automatically. If this attempt is successful, you will see the NDC 115 message logged.
Parameters
clli Name of the switch
chan_no Logical channel number. The valid value is 1, 2 or 3.
Status
Corrective action Follow these steps:
......
1 If this occurs frequently, use the tlentity command to check the link status of the specified entity.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-155 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 115
Message ID
NDC 115 link up; entity clli, channel chan_no
Description The link has been restored for the specified channel for the specified CLLI code. Data collection will resume automatically for this channel. Under some conditions, this message will be logged a few times. This signifies the ipndc process is having problems collecting data even though the link is up. Under such cases, this message will follow message IPNDC 118.
Reference: “Corrective action” (p. C-92)
Parameters clli Name of the switch
chan_no Logical channel number. The valid value is 1, 2 or 3.
Status
Corrective action This message is for your information only. No action is required.
...... C-156 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 116
Message ID
NDC 116 Wrong data received; entity clli, data type dtype, received si_type
Description The FEP polled the specified entity for dtype data, but received a different type of data. Most likely, the switch responded with 30-second data to a 5-minute poll or vice versa.
Parameters
clli Name of the switch
dtype Data type, such as 5min
si_type The data type switch sent back
Warning
Corrective action Follow these steps:
......
1 Use the tlentity command to verify that the switch will respond correctly to a poll for the specified data type.
......
2 If the switch does not respond correctly, refer this problem to your switch personnel.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-157 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 117
Message ID
NDC 117 Channel reset; entity clli, channel chan_no
Description The FEP detected protocol errors, making it impossible to collect data. This is often caused by a noisy data link or reinitialization of the switch software that communicates with the FEP.
Parameters
clli Name of the switch
chan_no Logical channel number. The valid value is 1, 2 or 3.
Major
Corrective action Follow these steps:
......
1 If the problem occurs frequently, have the data link checked out.
......
2 If the data link is OK, use the tlentity command to send a few polls on channel chan_no.
......
3 After sending each poll, check the status of the link using the tlentity STATUS command.
......
4 If the channel is reset again, confer with switch personnel to verify that they are using the correct version of the protocol.
...... C-158 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 As a last resort, have switch personnel compare protocol parameters of this switch with another switch known to have stable communications to this same FEP.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-159 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 118
Message ID
NDC 118 Data timeout; entity clli, data type dtype
Description The FEP sent a poll to the specified entity for the specified data type, but received a timeout message from the switch.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to see if the switch responds correctly to the specified poll.
......
2 If it doesn't, refer the problem to your switch personnel.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-160 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 119
Message ID
NDC 119 Time conflict; entity clli, data type dtype
Description The FEP sent a poll to the specified entity for the specified data type but received a “time conflict” response. This normally means the FEP polled the switch inside one of its lockout windows when the switch was updating its holding registers and could not send data to the FEP. This is usually caused by the switch's time being out of sync with the FEP's time.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Warning
Corrective action Follow these steps:
......
1 Check the clocks.
......
2 If they are not in sync, reset the switch's clock.
......
3 If the clocks are synchronized, the switch may not be in EADAS mode.
......
4 Ask switch personnel to verify this.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-161 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 120
Message ID
NDC 120 Invalid request; entity clli, data type dtype, poll b1 b2
Description The FEP sent a poll to the switch for the specified data type, but the switch sent back an invalid request message, meaning the ESS switch did not recognize the poll we sent it. However, the switch may also respond this way if the switch is unable to send the requested data.
Parameters
clli Name of the switch
dtype Data type, such as 5min
b1 b2 The poll bytes received by switch
Status
Corrective action Follow these steps:
......
1 Determine if the poll the FEP sent was valid or not.
Reference: The man page for tlentity lists all valid polls.
......
2 If the poll is invalid, then refer this problem to FEP Customer Support.
......
3 Assuming the poll is valid, there is probably a problem in the switch, in which case you should refer this problem to your switch personnel.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-162 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 121
Message ID
NDC 121 Data overwritten; entity clli, data type dtype
Description This error means that while the FEP was collecting data of type dtype from the specified entity, the data was overwritten in the switch's holding registers by the next interval's data. When the switch detects this, it sends an “overwritten data” message. This message should rarely occur, if ever. For it to occur, the poll would have to have been sent before the start of the lockout period of the switch, but data collection took so long that the FEP was still collecting data when the holding registers were updated.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Minor
Corrective action Follow these steps:
......
1 Verify that the switch and FEP clocks are in sync.
......
2 If they are off, reset the switch's clock, as the FEP automatically synchronizes to NTM.
......
3 If this does not clear the problem, notify FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-163 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 122
Message ID
NDC 122 ESS switch in min-mode; entity clli, data type dtype
Description When the FEP polled the switch for data, the switch sent back a min-mode message, meaning that the switch (5ESS switch only) is in some type of minimal or recovery mode that prevents it from sending data to FEP.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Warning
Corrective action This error should not be seen frequently or for extended periods of time. If it is, contact the switch operating or maintenance personnel to see if their switch is experiencing problems.
...... C-164 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 123
Message ID
NDC 123 protocol error; entity clli, data type dtype at channel chan_no
Description Protocol errors occurred during the collection of data type dtype from the specified entity, resulting in data not being received properly. This message will often be seen in conjunction with another error message that gives details of the protocol link problem.
Parameters
clli Name of the switch
dtype Data type, such as 5min
chan_no Logical channel number: 1, 2 or 3
Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to check the status of the link. Most likely, you will be able to trace this to some sort of hardware problem.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-165 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 125
Message ID
NDC 125 SPCS unequipped for requested data type; entity clli, data type dtype
Description The FEP sent a poll to the specified entity for dtype data and received a “not equipped” response. This means the switch is not configured to generate the requested type of data.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Minor
Corrective action Follow these steps:
......
1 Use tlentity to manually poll the switch for dtype data.
......
2 If this works, reactivate the entity and see if the problem disappears.
......
3 If the switch fails the tlentity poll, contact the switch person to verify that the switch is set up to respond to the specified data type poll.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-166 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 126
Message ID
NDC 126 Received small data block; entity clli, data type dtype, size=size
Description The ndc process received a data block too small to process. For example, the first data block in the message was smaller than the length of a message header.
Parameters
clli Name of the switch
dtype Data type, such as 5min
size Size of received date in bytes
Minor
Corrective action Follow these steps:
......
1 Use tlentity to verify that the switch is sending correctly formatted messages.
......
2 If not, the switch has a problem or data is being corrupted by the network between the switch and the FEP.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-167 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 127
Message ID
NDC 127 Bad number of sections; entity clli, data type dtype, sections=sctcnt
Description The ndc process received a message with an incorrect number of sections. The number of sections is calculated from the message header length, which must range from 0 to 255.
Parameters
clli Name of the switch
dtype Data type, such as 5min
sctcnt Sections of received data
Minor
Corrective action Follow these steps:
......
1 Use tlentity to verify that the switch is sending correctly formatted messages.
......
2 If not, the switch has a problem or data is being corrupted by the network between the switch and the FEP.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... C-168 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 128
Message ID
NDC 128 Clock mismatch of secs seconds; entity clli
Description The FEP's clock and switch's clock are off by secs seconds. A positive number of seconds indicates the switch clock is ahead of the FEP clock. A negative number of seconds indicates the switch clock is behind the FEP clock.
Parameters
clli Name of the switch
secs Number of seconds
Minor
Corrective action Follow these steps:
......
1 Set the specified switch's time to match the FEP, as the FEP clock automatically synchronizes to the NTM clock.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-169 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 129
Message ID
NDC 129 Data collection started; entity clli
Description This message occurs whenever data collection is started on an entity. You would see this after doing the aentity command or after a startfep was done or the FEP was rebooted.
Parameters
clli Name of the switch
Status
Corrective action No action is required. This message is for your information only.
References “aentity” (p. A-3) “startfep” (p. A-46)
...... C-170 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 130
Message ID
NDC 130 Data collection stopped; entity clli
Description Data collection stopped for entity clli. You would see this after doing the deaentity command.
Parameters
clli Name of the switch
Status
Corrective action No action is required. This message is for your information only.
References “deaentity” (p. A-27)
...... 190-406-737 Alcatel-Lucent — Internal C-171 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 132
Message ID
NDC 132 Received multiple request for entity entno for NM req
Description The FEP can only process one audit at a time or only one control per entity at a time. This error means the ndc process received a second request for an NTM audit or control as specified by req while it was still processing a previous one.
Parameters
req Audit or control
entno The entity number that received multiple requests
Warning
Corrective action Follow these steps:
......
1 If this error occurs a number of times, check with NTM personnel to verify that they are really sending multiple requests.
......
2 If the problem persists, deactivate and reactivate the entity.
......
3 If the problem still does not disappear, stop and start the FEP application using the stopfep command followed by startfep command.
......
4 If this still does not clear the problem, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
...... C-172 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “deaentity” (p. A-27) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-173 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 133
Message ID
NDC 133 Can’t open UNIX file, entity clli data type dtype
Description The ndc process is trying to write dtype data for the specified entity to a file so it can be shipped to NTM. However, it is unable to open the file for writing.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if the “/raw” file system is out of space.
......
2 If the “capacity” column shows a value near 100%, then the “/raw” file system is not being properly cleaned up.
......
3 Verify that the directory to which the file is being written exists by entering ls -l /raw/clli/dtype/ where clli and dtype are specified in the error message.
......
4 If the directory does not exist, make sure the clli code is correct by doing rsentity clli.
......
5 If the directory does not exist, deactivate the entity, delete the entity, recreate the entity, and then finally reactivate the entity.
...... C-174 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
6 If the directory still fails to be built, refer this problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... 190-406-737 Alcatel-Lucent — Internal C-175 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 134
Message ID
NDC 134 Can't write UNIX file; entity clli data type dtype
Description The ndc process is trying to write dtype data for the specified entity to a file so it can be shipped to NTM. However, it is unable to write to the file.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if the “/raw” file system is out of space.
......
2 If the “capacity” column shows a value near 100%, then the “/raw” file system is not being properly cleaned up.
......
3 Verify that the directory to which the file is being written exists by entering ls -l /raw/clli/dtype/ where clli and dtype are specified in the error message.
......
4 If the directory does not exist, make sure the clli code is correct by doing rsentity clli.
......
5 If the directory does not exist, deactivate the entity delete the entity, recreate the entity, and then finally reactivate the entity.
...... C-176 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
6 If the directory still fails to be built, refer this problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... 190-406-737 Alcatel-Lucent — Internal C-177 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 135
Message ID NDC 135 Message to NMT failed
Description The ndc process failed in an attempt to pass information to the nmt process. This may be a temporary problem caused by an overflow of space for messages in the system, or it may mean the nmt process has stopped running.
Critical
Corrective action Follow these steps:
......
1 To clear the message passing problem, restart the FEP application by doing stopfep followed by startfep.
......
2 If the message still continues to appear, bring down the FEP application by doing stopfep and then reboot the FEP.
......
3 If this error occurs consistently, do ipcs -qa and ps -ef while the error appears and redirect the output to a file; then report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-178 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 139
Message ID
NDC 139 Can't close UNIX file; entity clli data type dtype
Description The ndc process is trying to write dtype data for the specified entity to a file so it can be shipped to NTM. However, it is unable to close the file it has written to close the file it has written to.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if the “/raw” file system is out of space.
......
2 If the “capacity” column shows a value near 100%, then the “/raw” file system is not being properly cleaned up.
......
3 Verify that the directory to which the file is being written exists by entering ls -l /raw/clli/dtype/ where clli and dtype are specified in the error message.
......
4 If the directory does not exist, make sure the clli code is correct by doing rsentity clli.
......
5 If the directory does not exist, deactivate the entity, delete the entity, recreate the entity, and then finally reactivate the entity.
...... 190-406-737 Alcatel-Lucent — Internal C-179 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
6 If the directory still fails to be built, refer this problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... C-180 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 140
Message ID
NDC 140 Received unknown message type - mtype
Description The ndc process received an unrecognizable message from another FEP process.
Parameters
mtype A digit representing a message type, the valid message types are: 1. NM request data 2. Activate an entity 3. Deactivate an entity 4. Dump an entity queues polls
Minor
Corrective action Follow these steps:
......
1 If this message appears consistently, restart the FEP application by entering stopfep followed by startfep.
......
2 If this does not clear the problem, enter ipcs -aq and ps -ef and redirect the output to a file.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-181 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 144
Message ID
NDC 144 Received invalid poll command; entity clli data type dtype
Description The ndc process received an invalid poll command from the nmt process.
Parameters
clli Name of the switch
dtype Data type, such as 5min
Warning
Corrective action Follow these steps:
......
1 Deactivate and reactivate the specified entity.
......
2 If this message still appears consistently, restart the FEP application by entering stopfep followed by startfep.
......
3 If this does not clear the problem, enter ipcs -aq tand ps -ef and redirect the output to a file.
......
4 Use the logCat command to search for any recent NMT messages indicating why this happened.
......
5 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-182 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “deaentity” (p. A-27) “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-183 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 145
Message ID
NDC 145 Received invalid entity activation; entity clli pdn pdno
Description The ndc process was sent an invalid activation command and thus failed to activate entity clli.
Parameters
clli Name of the switch
pdno Protocol number
Minor
Corrective action Follow these steps:
......
1 If this message is appearing for only one entity, then delete and recreate the entity and then activate the entity.
......
2 If this does not clear the problem or if this message is coming out for several entities, restart the FEP application using the stopfep command followed by the startfep command.
......
3 If the problem still persists, use command edbview entno of clli and redirect the output to a file.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-184 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “centity” (p. A-13) “delentity” (p. A-29) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-185 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 146
Message ID
NDC 146 mpx write failed; channel entno, errno errno
Description The ndc process's attempt to send a poll for the specified entity on the specified channel failed. A failure indicates some problem either with the link or the ndc's internal devices. The ndc process will try to recover the link automatically once the error occurs.
Parameters
entno The entity number
errno UNIX errno
Minor
Corrective action Follow these steps:
......
1 Use the rsentity entno command to determine whether or not there is data loss for this entity.
......
2 If there is no data loss, then no action is required.
......
3 If, however, this entity is experiencing data loss and this error occurs frequently and along with other ipndc errors (such as IPNDC 114, IPNDC 149, IPNDC 150), then you should run the tlentity command to establish end-to-end communication and send polls on all the channels.
......
4 If you are able to successfully send polls and get back data, activate the entity using the aentity command.
......
5 If the problem still persists:
...... C-186 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
a. Verify that the SLM is in service in Datakit, using the verify slm command on the Datakit VCS console. b. Verify that the dialstring to the entity is correct, using the rsentity entno command.
......
6 If the problem still does not go away, restart the FEP application using the stopfep and startfep commands.
......
7 If this doesn't clear the problem, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “rsentity” (p. A-42) “startfep” (p. A-46) “stopfep” (p. A-47) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-187 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 149
Message ID
NDC 149 Entity entno in invalid state; reinitializing data collection
Description This error message means the ndc process considered one of the internal data structures associated with entity entno to be invalid. The ndc process is reinitializing the entity in an attempt to resume its data collection. If this does not clear the problem, error messages NDC 114 and NDC 150 may be generated.
Parameters
entno The entity number being reinitialized
Minor
Corrective action Follow these steps:
......
1 Run the tlentity command to establish end-to-end communication and send polls on all the channels.
......
2 If you are able to successfully send polls and get back data, activate the entity using the aentity command.
......
3 If the problem still persists, verify that the SLM is in service in Datakit, using the verify slm command on the Datakit VCS console.
......
4 Verify that the dialstring to the entity is correct, using the rsentity entno command.
......
5 If the problem still does not go away, restart the FEP application using the stopfep and startfep commands.
...... C-188 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
6 If this doesn't clear the problem, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “rsentity” (p. A-42) “startfep” (p. A-46) “stopfep” (p. A-47) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-189 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 150
Message ID
NDC 150 Entity entno in invalid state; stopping data collection
Description Error message NDC 150 normally follows error message NDC 149 if the ndc process found an internal data structure associated with the specified entity to be inconsistent. This means the ndc process could not automatically reinitialize the data structure and has stopped trying to collect for this entity until 30 minutes has passed. This message will be generated every 30 minutes until the data starts being collected from the switch.
Parameters
entno The entity number
Minor
Corrective action Follow these steps:
......
1 Try deactivating and activating the entity to see if the problem persists.
......
2 Run the tlentity command to establish end-to-end communication and send polls on all the channels.
......
3 If you are able to successfully send polls and get back data, activate the entity using the aentity command.
......
4 If the problem still persists, verify that the SLM is in service in Datakit, using the verify slm command on the Datakit VCS console.
......
5 Verify that the dialstring to the entity is correct, using the rsentity entno command.
...... C-190 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
6 If the problem still does not go away, restart the FEP application using the stopfep and startfep commands.
......
7 If this doesn't clear the problem, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “deaentity” (p. A-27) “rsentity” (p. A-42) “startfep” (p. A-46) “stopfep” (p. A-47) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-191 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 152
Message ID
NDC 152 Can't access edb_fld field of ent entno in entity database
Description The ndc process is trying to access a field in shared memory for the specified entity but cannot.
Parameters
entno The entity number
edb_fld The entity database field name
Minor
Corrective action Follow these steps:
......
1 Try deactivating and reactivating the entity using the deaentity and aentity commands.
......
2 If you continue to see this error, deactivate the entity, delete the entity, recreate the entity and reactivate the entity.
......
3 If the problem still continues, refer it to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... C-192 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 153
Message ID
NDC 153 Entity entno database field edb_fld had bad value
Description This error occurred while trying to activate an office, either via the aentity command or when the NDC process initialized as the FEP application was started.
Parameters
entno The entity number
edb_fld The entity database field name
Minor
Corrective action Follow these steps:
......
1 If this message is coming out for only one entity, then deactivate the entity and reactivate it using the deaentity and aentity commands.
......
2 If you continue to see this error, deactivate the entity, delete the entity (using delentity), recreate the entity (using centity), and reactivate the entity.
......
3 If this message is coming out for several entities, then it’s likely the entity database is corrupt. Reinitialize it by running stopfep followed by startfep.
......
4 If the problem still continues, refer it to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-193 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29) “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-194 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 154
Message ID
NDC 154 Terminated by signal sig_no
Description The ndc process was killed by the specified signal. There are two reasons for this. Either there is a fatal FEP system problem, or the system was gracefully shut down with the stopfep command. If the FEP was not shutting down, the ndc process will respawn automatically.
Parameters
sig_no The signal number
Major
Corrective action Follow these steps:
......
1 If the FEP was brought down using the stopfep command, then this message is for your information only.
......
2 If however, the FEP was not brought down and the ndc process died on its own, use the logCat command to determine why the ndc process restarted itself.
......
3 If this message occurs frequently, refer this error to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-195 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 155
Message ID NDC 155 Can't lock into memory
Description In order to function, the ndc process locks itself into core memory almost immediately upon coming up. If for some reason it cannot do this, the message above will be generated and the ndc process will exit. BaseWorX functions will respawn the ndc process up to four times, so it's possible that you could see four of these messages in short order.
Major
Corrective action Follow these steps:
......
1 Restart the FEP application by entering stopfep followed by startfep.
......
2 If the message reappears, stop the FEP application and reboot the computer.
......
3 If the message still appears, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-196 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 156
Message ID NDC 156 Can't access shared memory
Description The ndc process could not access shared memory, indicating a FEP system problem. This will restrict the ndc process from communicating with other FEP processes and from accessing its database.
Major
Corrective action Follow these steps:
......
1 Restart the FEP application by entering stopfep followed by startfep.
......
2 If the message reappears, stop the FEP application and reboot the computer.
......
3 If the message still appears, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-197 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 157
Message ID
NDC 157 Can't open file message
Description The ndc process could not open a device file to collect data from a synchronized entity.
Parameters
message Contains the entity CLLI code along with a (VPORT) error message
Major
Corrective action Follow these steps:
......
1 Run the tlentity command to establish end-to-end communication and send polls on all the channels.
......
2 If you are able to successfully send polls and get back data, activate the entity using the aentity command.
......
3 If tlentity fails, verify that the SLM is in service in Datakit, using the verify slm command on the Datakit VCS console.
......
4 Verify that the dialstring to the entity is correct, using the rsentity entno command.
......
5 If the SLM looks OK but the problem still doesn't go away, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
...... C-198 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “aentity” (p. A-3) “rsentity” (p. A-42) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-199 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 158
Message ID
NDC 158 Can't read file message
Description The ndc process could not read from a device file to collect data from a synchronized entity.
Parameters
message This could be one of two messages: 1. NDC channel of entity entno (produces Major alarm) 2. 0, n_read=byte errno=errno (produces Minor alarm). Ignore the “0”; it means the entity is a synchronous entity (5ESS/DMS switches)
entno The entity number of the entity experiencing problems
errno The error number returned from the read failure
Major, Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to establish end-to-end communication and send polls on all the channels.
......
2 If you are able to successfully send polls and get back data, activate the entity, using the aentity command.
......
3 If tlentity fails, verify that the SLM is in service in Datakit, using the verify slm command on the Datakit VCS console.
......
4 Verify that the dialstring to the entity is correct, using the rsentity entno command.
...... C-200 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 If the SLM looks OK but the problem still doesn't go away, refer the problem to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “rsentity” (p. A-42) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-201 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 159
Message ID NDC 159 Can't write file
Description The ndc process could not write to a device file to poll a synchronized entity.
Warning
Corrective action Contact FEP Customer Support if this message occurs frequently.
...... C-202 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 161
Message ID
NDC 161 Can't enable messages for proc_name
Description The ndc process could not enable messages from the specified proc_name. This will inhibit reception of service requests from other FEP processes and users.
Parameters
proc_name Process name like ndc
Major
Corrective action Follow these steps:
......
1 Restart the FEP application by entering stopfep followed by startfep.
......
2 If the message reappears, stop the FEP application and reboot the computer.
......
3 If the message still appears, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-203 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 162
Message ID
NDC 162 Can't disable messages for proc_name
Description The ndc process could not disable messages for the specified process.
Parameters
proc_name Process name like ndc
Warning
Corrective action Contact FEP Customer Support if this message occurs frequently.
...... C-204 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 165
Message ID
NDC 165 Invalid switch data type - dtype, MsgQid = ID
Description The ndc process is calling a routine to write data it collected to a file, but the specified data type is invalid. This may be a software error in the ndc process.
Parameters
dtype Data type, such as 5min
ID Number representing a process, such as 0x601 - ndc
Major
Corrective action Follow these steps:
......
1 Refer this error to FEP Customer Support.
Note: You'll probably need to do stopfep followed by startfep to clear the problem (possibly reboot if stopfep and startfep don't work), but it would be beneficial to contact FEP Customer Support first so they can analyze the FEP in its current state.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-205 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 166
Message ID
NDC 166 Memory allocation for bufname failed
Description The ndc process could not allocate more memory. This may be a software error in the ndc process.
Parameters
bufname Buffer name, e.g., receive buffer, NM poll buffer
Major
Corrective action Follow these steps:
......
1 Refer this error to FEP Customer Support.
Note: You'll probably need to do stopfep followed by startfep to clear the problem (possibly reboot if stopfep and startfep don't work), but it would be beneficial to contact FEP Customer Support first so they can analyze the FEP in its current state.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-206 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 167
Message ID
NDC 167 Get file status failed for file fpath
Description The ndc process stores collected traffic data in the “/raw/clli/tmp/file” file.
It then links the “/raw/clli/tmp/file” to either the “/raw/clli/5min/file”, the “/raw/clli/aud/file”, or the” /raw/clli/ctl/file” (depending on the type of data that was collected) and then finally unlinks the “/raw/clli/tmp/file” file.
This message means the ndc process could not access the “/raw/clli/tmp/file” file.
Parameters
fpath Full path to the file name
Major
Corrective action Follow these steps:
......
1 Run ls -l /raw/clli where clli is embedded in the specified fpath to verify that the data directory exists for this entity.
......
2 If the directory does not exist, deactivate the entity, delete the entity, recreate the entity, and then finally reactivate the entity.
......
3 If the directory still fails to be built, or the directory exists but this message is still being logged, refer this problem to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-207 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27) “delentity” (p. A-29)
...... C-208 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 168
Message ID
NDC 168 Link to file fpath failed
Description The ndc process stores collected traffic data in the “/raw/clli/tmp/file” file.
It then links the “/raw/clli/tmp/file” to either the “/raw/clli/5min/file”, the “/raw/clli/aud/file”, or the “/raw/clli/ctl/file” (depending on the type of data that was collected) and then finally unlinks the “/raw/clli/tmp/file”.
This message means the ndc process could not link the “/raw/clli/tmp/file” file to the proper file as described above.
Parameters
fpath Full path to the file name
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if the “/raw” file system is out of space.
......
2 If the “capacity” column shows a value near 100%, then the “/raw” file system is not being properly cleaned up.
......
3 Contact FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-209 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 169
Message ID
NDC 169 Sending dtype poll to entity entno, channel chan_no
Description The ndc process is polling the specified entity for dtype data on the specified channel. This message may only appear when FEP Customer Support is contacted for fault isolation. This message is normally not logged on the FEP as it does not indicate a problem, and it would generate many messages, making it cumbersome to identify true error conditions.
Parameters
dtype Data type
entno Entity number
chan_no Logical channel number: 1, 2 or 3
Status
Corrective action This message is for your information only. No action is required.
...... C-210 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 170
Message ID
NDC 170 Timeout of dtype poll for entity entno, channel chan_no
Description The ndc process has timed out waiting for a response from a particular switch for the specified data type. The ndc process will repoll. The FEP will allow 2 minutes to collect 5- minute data. The FEP will allow 1 minute to collect 30-second data.
Parameters
dtype Data type
entno Entity number
chan_no Logical channel number: 1, 2 or 3
Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to see if the switch responds quickly to the specified poll.
......
2 If it doesn't, the problem may either be in the switch or in the network between the switch and the FEP.
......
3 Ask switch personnel if they see the poll coming into the switch.
......
4 If they do see the poll and are responding, chances are it's a networking problem.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-211 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 171
Message ID
NDC 171 dtype poll for entity entno, channel chan_no result
Description The ndc process sent the specified poll — but instead of getting back the expected dtype data, it got back result. The ndc process will repoll.
Parameters
dtype Data type
entno Entity number
chan_no Logical channel number: 1, 2 or 3
result Result sent back by the process
Minor
Corrective action Follow these steps:
......
1 Use the tlentity command to see if the FEP receives valid data to the specified poll.
......
2 If it doesn't, the problem may either be in the switch or in the network between the switch and the FEP.
......
3 Ask switch personnel if they see the poll coming into the switch.
......
4 If they do see the poll and believe the switch is responding correctly, chances are it is a networking problem corrupting the data.
...... E ND OF STEPS ......
...... C-212 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-213 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 172
Message ID
NDC 172 Received nbyte byte response to dtype poll for entity entno, channel chan_no
Description The ndc process received nbyte bytes of data back for the specified poll. This message may only appear when FEP Customer Support is contacted for fault isolation. This message is normally not logged on the FEP as it does not indicate a problem, and it would generate many messages, making it cumbersome to identify true error conditions.
Parameters
dtype Data type
entno Entity number
chan_no Logical channel number: 1, 2 or 3
nbyte Number of bytes
Status
Corrective action This message is for your information only. No action is required.
...... C-214 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 173
Message ID
NDC 173 Data collector ndcno cannot open/read/usra/tdms/ndc/dksleep, using default value of secs seconds
Description During the startup of the ndc process (whether it be after startfep or a reboot has been done), it reads the “/usra/tdms/ndc/dksleep” file, to determine how many seconds it should wait between entity activations. This is done so the Datakit controller does not get too many call setup requests at the same time. This message means the ndc process could not read the “/usra/tdms/ndc/dksleep” file, so it is using the default value of secs seconds to sleep between entity activations.
Parameters
ndcno IPNDC number: 1. 0 - 5ESS/DMS 2. 1 - GTD-5 monitored 3. 2 - GTD-5 LSSGR-like
secs Number of seconds
Minor
Corrective action You have three options to recover this file so it will be accessible the next time the ndc process is started when startfep is done:
......
1 If you want to use the standard values for this file delivered with the FEP application, become “root” and enter: echo “3” > /usra/tdms/ndc/dksleep chown root /usra/tdms/ndc/dksleep chgrp tdms /usra/tdms/ndc/dksleep ......
2 You could alternatively restore “/usra/tdms/ndc/dksleep” from your latest Dynamic Data backup.
...... 190-406-737 Alcatel-Lucent — Internal C-215 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
3 If neither of the above are successful, contact FEP Customer Support. They will help you recreate this file with appropriate values.
...... E ND OF STEPS ......
References “Restoring dynamic data (all or some)” (p. 3-72)
...... C-216 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NDC 174
Message ID
NDC 174 Data collector ndcno sleep interval between activates will be secs seconds
Description During the startup of the ndc process, it reads the “/usra/tdms/ndc/dksleep” file, to determine how many seconds it should wait between entity activations. This is done so the Datakit controller does not get too many call setup requests at the same time. This message means the ndc process will sleep secs seconds between each entity activation (after startfep or reboot has been done).
Parameters
ndcno IPNDC number: 1. 0 - 5ESS/DMS 2. 1 - GTD-5 monitored 3. 2 - GTD-5 LSSGR-like
secs Number of seconds
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-217 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT — Network Management Overview
Purpose This section provides all of the NMT error messages.
Messages in this section include:
• NMT 001
• NMT 004
• NMT 006
• NMT 007
• NMT 008
• NMT 009
• NMT 010
• NMT 013
• NMT 014
• NMT 015
• NMT 016
• NMT 018
• NMT 019
...... C-218 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
• NMT 022
• NMT 023
• NMT 024
• NMT 025
• NMT 026
• NMT 027
• NMT 029
• NMT 030
• NMT 037
• NMT 038
• NMT 041
• NMT 042
• NMT 045
• NMT 046
• NMT 047
• NMT 048
• NMT 049
• NMT 050
...... 190-406-737 Alcatel-Lucent — Internal C-219 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
• NMT 051
• NMT 052
• NMT 054
• NMT 055
• NMT 056
• NMT 057
• NMT 058
• NMT 059
• NMT 060
• NMT 061
• NMT 062
...... C-220 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 001
Message ID
NMT 001 miscellaneous ASCII text
Description The FEP has received the miscellaneous ASCII text across the FEP/NTM link from an NTM computer.
Parameters
miscellaneous ASCII textText was generated by NTM personnel to test link to FEP
Status
Corrective action Follow these steps:
......
1 Check the message content with what was generated on the NTM side.
......
2 If there are differences, diagnose the network connection between the two computers.
......
3 If it is consistent, congratulate yourself on a job well done.
...... E ND OF STEPS ......
References “tlentity” (p. A-48) “sendmsg” (p. 20) in the Input Commands Guide
...... 190-406-737 Alcatel-Lucent — Internal C-221 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 004
Message ID
NMT 004 Message received in error by NM link
Description The FEP has received notification that data it sent to the NTM computer identified by link did not receive the data correctly. The interface is set up to automatically resend the data.
Parameters
link This number is the NTM link number associated with a NTM name. The NTM name/link association can be ascertained with the rsnlink command.
Minor
Corrective action No need for action if this occurs infrequently. If it becomes a habit on your FEP, it means that the link between the FEP and NTM is not clean. You should have your networking personnel diagnose the network between NTM and the FEP. If the network seems in good working order, contact FEP Customer Support.
References “rsentity” (p. A-42) “tlentity” (p. A-48) “sendmsg” (p. 20) in the Input Commands Guide
...... C-222 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 006
Message ID
NMT 006 FEP TIME time NM link TIME time [CLOCK MISMATCH OF N SECONDS]
Description The NTM has notified the FEP of its current system time. The FEP compares its system times (taking time zone differences into consideration) and generates the message above.
Parameters
time Current time represented by day, date hh:mm:ss yyyy (e.g., Tue Jul 11 08:36:31 1995)
link This number is the NTM link number associated with a NTM name. The NTM name/link association can be ascertained with the rsnlink command.
N The number of seconds that separate the times of the two system clocks. This part of the message is displayed only if N is greater than 5.
Status If clocks are within plus or minus 5 seconds of one another
Warning If clocks differ by more than 5 seconds, the “CLOCK MISMATCH OF N SECONDS” message is appended.
Corrective action Follow these steps:
......
1 Determine alarm type: a. If this is a Status message, there is no need for action if this message. b. If it is listed as a Warning message, you may want to take note of it and watch that as each 5-minute interval passes the time difference decreases.
......
2 The FEP will automatically try to synchronize itself to NTM's time by no more than 10 seconds each 5-minute interval until the difference is less than 5 seconds.
...... 190-406-737 Alcatel-Lucent — Internal C-223 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
3 If the difference does not decrease over time, check with the administrator of the NTM computer to see if someone has changed the time there.
......
4 If so, the FEP is probably just iterating the time change that occurred on NTM.
......
5 If this message appears more than once in a 5-minute period, then the FEP may have multiple NTM links active instead of just one.
......
6 This will cause the FEP to vacillate between the multiple NTM times that it receives.
......
7 To correct this, enter rsnlink all and deactivate all but one NTM link, using the deanlink command.
...... E ND OF STEPS ......
References “deanlink” (p. A-28) “rsnlink” (p. A-44)
...... C-224 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 007
Message ID NMT 007 NMT started - nm reactivation complete
Description This message tells you that the nmt process — the one that supports the interface to NTM — has started and that all work needed to allow active NTM links to connect has completed. You should see this message after a startfep command has been run.
Status
Corrective action Follow these steps:
......
1 If you see this message after a startfep or a reboot was done, then no action is required.
......
2 Otherwise, stop and start the FEP application using the stopfep and startfep commands to clear this problem.
......
3 If the problem persists, stop the FEP and reboot it.
......
4 If the problem still persists, report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-225 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 008
Message ID
NMT 008 NMT activated; nm NTMOS name
Description This message tells you that the NTM link to NTMOS name specified has been activated with the anlink command or through the nmt process (see NMT 007 message) initializing.
Parameters
NTMOS name The name of the NTM for which this message applies
Status
Corrective action No action is required.
References “anlink” (p. A-4) “delnlink” (p. A-31) “rsnlink” (p. A-44)
...... C-226 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 009
Message ID
NMT 009 NMT deactivated; nm NTMOS name
Description This message tells you that the NTM link to the specified NTMOS name has been deactivated with the deanlink command.
Parameters
NTMOS name The name of the NTM for which this message applies
Warning
Corrective action Follow these steps:
......
1 If you know that there is another NTM link is active, no action is required.
......
2 If a FEP has no active NTM links, it has no ability to transmit data to NTM, thus greatly affecting the ability of NTM to function.
......
3 This message has a severity level of Warning rather than Status because of its ability to affect FEP operation.
...... E ND OF STEPS ......
References “anlink” (p. A-4) “cnlink” (p. A-21) “delnlink” (p. A-31) “rsnlink” (p. A-44)
...... 190-406-737 Alcatel-Lucent — Internal C-227 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 010
Message ID
NMT 010 NMT Link up nm NTMOS name channel chan
Description This message tells you that the specified NTM link NTMOS name and chan has come in to service and is currently connected with NTM. Data can now be transmitted across the channel.
Parameters
NTMOS name The name of the NTM to which this message applies
chan This channel number is the channel number associated with a specific type of NTM data. The type of each data and its associated channel number are:
C Discrete Data h a n n e l
1 C Audit Data (Command/Response) h a n n e l
2
...... C-228 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
C Control Data (Command/Response) h a n n e l
3 C 5-minute Register Data. h a n n e l
4 The current status of each channel on each NTM link can be ascertained by with the rsnlink command.
Status
Corrective action This message is for your information only. No action is required.
References “rsnlink” (p. A-44)
...... 190-406-737 Alcatel-Lucent — Internal C-229 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 013
Message ID
NMT 013 Write error on NM NTMOS name channel chan; detail
Description This message tells you that there has been a problem writing data out to the specified NTMOS name and chan. The detail should give you a more distinct reason why this has occurred.
Parameters
NTMOS name The name of the NTM to which this message applies
chan The specific channel on the NTM link
detail Specific detail of the problem
Warning
Corrective action Follow these steps:
......
1 If you see this message once, attribute it to link congestion.
......
2 If it occurs regularly, contact FEP Customer Support and have the exact text of the message ready.
...... E ND OF STEPS ......
...... C-230 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 014
Message ID
NMT 014 NMT internal error: error text
Description This message tells you that there has been an internal error within the nmt process. The error text indicates what the specific problem seems to be.
Parameters
error text Can be any of the following text strings and will be seen with the listed severity level:
C bind failure, error error r listen failure, error error i accept failure, error error t i c a l W REGDTA poll already in progress ofid out a of range in post_reg r n i n g
M BAD NM REQUEST-check NTM link i n o r
...... 190-406-737 Alcatel-Lucent — Internal C-231 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
M INTERFACE/write error, aborting a connection j INTERFACE error ALI:partials o r INTERFACE/write error, aborting connection receive buffer overflow
REGSIZE ERR ent:entity max:allowable maximum size:size
error TCP/IP error message
entity FEP entity number affected
allowable maximumThe maximum allowable size for register data
size The size of the register data that the specified entity sent to the FEP. For GTD-5 entities, this will be the size of the file after it has been converted from ASCII data to binary form.
Severity level depends upon error text see below.
Corrective action Follow these steps:
......
1 The Warning and Minor messages tell you that there are inconsistencies in the interface between the FEP and NTM.
......
2 Check link integrity and/or take the link down and bring it back up (i.e. deanlink, then anlink command).
......
3 If the condition continues, contact FEP Customer Support.
......
4 The Major messages tell you that there are serious problems with the interface between the FEP and NTM; FEP/NTM will automatically bring the link down and back up to try to resolve the problem.
...... C-232 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 Refer to your networking personnel to diagnose the network between NTM and the FEP.
......
6 Should the messages continue or reoccur, contact FEP Customer Support.
...... E ND OF STEPS ......
References “anlink” (p. A-4) “deanlink” (p. A-28)
...... 190-406-737 Alcatel-Lucent — Internal C-233 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 015
Message ID
NMT 015 NMT received unknown message type type
Description The nmt process has received an interprocess communication (IPC) message that it does not recognize.
Parameters
type The invalid message type that was received
Warning
Corrective action Follow these steps:
......
1 Chances are that the interprocess communication (IPC) mechanism on your FEP has been corrupted as a result of a panic or other system error.
......
2 Use stopfep to stop the FEP application and then reboot the FEP; the FEP application should come back up automatically.
...... E ND OF STEPS ......
References “stopfep” (p. A-47)
...... C-234 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 016
Message ID
NMT 016 Entity entno invalid for CTL or AUD request from NM link
Description A control or audit request for the specified entity number was received from the NTM associated with the NM link. The listed entity number is not one to which the FEP considers to be available for sending control or audit requests.
Parameters
entno A number associated with a particular CLLI name. The CLLI name/entity number association can be ascertained with the rsentity command.
link This number is the NTM link number associated with an NTM name. The NTM name/link association can be ascertained with the rsnlink command.
Warning
Corrective action This message indicates inconsistencies between NTM and the FEP. Follow these steps:
......
1 Bring down the FEP/NTM connection, using deanlink, and bring it back up, using anlink.
......
2 If the message repeats after doing so, contact FEP customer support.
...... E ND OF STEPS ......
References “anlink” (p. A-4) “deanlink” (p. A-28)
...... 190-406-737 Alcatel-Lucent — Internal C-235 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 018
Message ID
NMT 018 NMT can't send message to NDC ndc number
Description The nmt process cannot send an interprocess communication (IPC) message to either the ndc process or the ctlAud process. The particular process depends upon the ndc number.
Parameters
ndc number 0 — ndc process 1 — ctlAud process
Major
Corrective action Follow these steps:
......
1 Use the UNIX command ps -eaf | grep ndc and/or ps -eaf | grep ctlAud to ascertain whether the autonomous process the nmt is complaining about is currently running.
......
2 If not, stop and restart the FEP application to bring the process back up.
Note: Don't forget to watch the log file (see logCat) to verify that the process came up and stayed up. If it does not, there's a larger problem that FEP Customer Support will help you with.
......
3 If both processes are up, chances are that the IPC mechanism on your FEP has been corrupted as a result of a panic or other system error.
......
4 Use stopfep to stop the FEP application and then reboot the FEP; the FEP application should come back up automatically.
...... C-236 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 Check the log file as explained above to make sure all FEP autonomous processes come up and stay up.
......
6 If the problem persists, contact FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-237 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 019
Message ID
NMT 019 NMT can't open file pathname;text string
Description The nmt process was not able to access the named file. The pathname should indicate to you whether the file contained control, audit, or 5-minute data. If the nmt process could not access the file, then the data cannot be delivered to NTM. Therefore, data has been lost.
Parameters
pathname The full UNIX pathname of the file in question
text string An explanation field to further isolate the exact problem with the file
Minor
Corrective action Follow these steps:
......
1 If this message is occurring frequently, stop and start the FEP application, using the stopfep and startfep commands.
......
2 Contact FEP Customer Support with the exact message text.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-238 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 022
Message ID NMT 022 CANNOT OPEN ENTITIES FILE
Description The nmt process cannot open the UNIX “/usra/tusr/na/entity/entities” file.
Minor
Corrective action Follow these steps:
......
1 Use the UNIX command ls -l /usra/tusr/na/entity/entities to ascertain whether the file exists. The response to this command should be identical to: -rwxrwxr-x 1 root tdms 26400 Nov 1 09:54 /usra/tusr/na/entity/entities except the date can/should be different, as well as the 26400 number.
......
2 Make sure that the “-rwxrwxr-x” and “root tdms” parts of the response are consistent with what you see on your FEP.
......
3 If you cannot find this file on your FEP, restore it from Dynamic Data backup.
......
4 Then stop and restart the FEP application, using the stopfep and startfep commands.
......
5 If the message persists, call FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47) “Restoring dynamic data (all or some)” (p. 3-72)
...... 190-406-737 Alcatel-Lucent — Internal C-239 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 023
Message ID NMT 023 CANNOT READ ENTITIES FILE
Description The nmt process cannot read the UNIX “/usra/tusr/na/entity/entities” file.
Minor
Corrective action Follow these steps:
......
1 Use the UNIX command ls -l /usra/tusr/na/entity/entities to ascertain the permissions/owner/group of the file. The response to this command should be identical to: -rwxrwxr-x 1 root tdms 26400 Nov 1 09:54 /usra/tusr/na/entity/entities* except the date can/should be different, as well as the 26400 number.
......
2 Make sure that the “-rwxrwxr-x” and “root tdms” parts of the response are consistent with what you see on your FEP.
......
3 If the “-rwxrwxr-x” part of the response is not correct, become the “root” user and use the following command to correct the file permissions: chmod 775 /usra/tusr/na/entity/entities ......
4 If the “root tdms” part of the response is not correct, become the “root” user and use the following commands to correct the owner/group: chown root /usra/tusr/na/entity/entities chgrp tdms /usra/tusr/na/entity/entities ......
5 If all information for the entities files is consistent with what you see above and this message continues to occur, restore the “/usra/tusr/na/entity/entities” file from your latest Dynamic Data backup.
...... C-240 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
6 If the message still persists, contact FEP Customer Support.
...... E ND OF STEPS ......
References “Restoring dynamic data (all or some)” (p. 3-72)
...... 190-406-737 Alcatel-Lucent — Internal C-241 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 024
Message ID
NMT 024 Bad Activation; nm link;text string
Description A request to activate a link to an NTM was unsuccessful.
Parameters
link This number is the NTM link number associated with an NTM name. The NTM name/link association can be ascertained with the rsnlink command.
text string Expanded reason regarding why the activation could not occur. Current possibilities for this field and their related severity level are:
M Could not internally activate link a j o r M NM number out of range i n o r W NM number already active a r n i n g
Warning, Minor, or Major depending upon the text string
Corrective action Follow these steps:
...... C-242 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
1 If you know that there is another NTM link active and that NTM is up and running, no immediate action is required.
......
2 If a FEP has no active NTM links to active NTM systems, it has no ability to transmit data to NTM, thus, greatly affecting the ability of NTM to function.
......
3 If the NM link was already active, the warning message will appear if someone attempts to activate it again.
......
4 The other two messages indicate system errors, either a type of the nm link (Minor error) or a serious FEP problem (Major error) that should be directed to FEP Customer Support.
...... E ND OF STEPS ......
References “anlink” (p. A-4) “cnlink” (p. A-21) “delnlink” (p. A-31) “rsnlink” (p. A-44)
...... 190-406-737 Alcatel-Lucent — Internal C-243 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 025
Message ID
NMT 025 NMT: can't access NMDBfield field in NM database
Description The nmt process could not access the specified field in the NM database.
Parameters
NMDBfield The name of the field in the NM database that the process was attempting to access.
Warning
Corrective action Follow these steps:
......
1 Use the UNIX command ls -l /usra/tdms/nmt/ntmsinfo to ascertain the permissions/owner/group of the file. The response to this command should be similar to: -rw-rw-rw- 1 fep tdms 96 Oct 31 08:03 /usra/tdms/nmt/ntmsinfo The date can/should be different. In FEP R1, the number before the date will be 96 as shown above; in FEP R2 and beyond, the number will be 112.
......
2 Make sure that the “-rw-rw-rw” and “fep tdms” parts of the response are consistent with what you see on your FEP.
......
3 If the “-rw-rw-rw” part of the response is not correct, become the “root” user and use the following command to correct the file permissions: chmod 666 /usra/tdms/nmt/ntmsinfo ......
4 If the “fep tdms” part of the response is not correct, become the “root” user and use the following commands to correct the owner/group: chown fep /usra/tdms/nmt/ntmsinfo chgrp tdms /usra/tdms/nmt/ntmsinfo
...... C-244 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
......
5 Then, stop and restart the FEP application using stopfep and startfep.
......
6 If all information for the NM database files is consistent with what you see above and this message continues to occur, restore the file from your last Dynamic Data backup.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47) “Restoring dynamic data (all or some)” (p. 3-72)
...... 190-406-737 Alcatel-Lucent — Internal C-245 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 026
Message ID NMT 026 NMT: bad value from NM database field 'N_network'
Description The value retrieved from the NM database field ‘N_network’ was not consistent with accepted values.
Warning
Corrective action Follow these steps:
......
1 Stop and restart the FEP application using stopfep and startfep in an attempt to repopulate the NM database with correct values.
......
2 If this does not solve the problem, restore the file “/usra/tdms/nmt/ntmsinfo” from your last Dynamic Data backup.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47) “Restoring dynamic data (all or some)” (p. 3-72)
...... C-246 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 027
Message ID
NMT 027 Entity entno invalid for REGDTA request from NM link
Description The NTM specified by NM link has requested 5-minute register data for an entity number that is not valid. Typically this would mean that the entity number was either a negative number or greater than 199. This message indicates inconsistencies between NTM and the FEP.
Parameters
entno The value that NTM sent to the FEP as an entity number.
link This number is the NTM link number associated with an NTM name. The NTM name/link association can be ascertained with the rsnlink command.
Warning
Corrective action Follow these steps:
......
1 Bring down the FEP/NTM connection, using deanlink, and bring it back up, using anlink.
......
2 If the message repeats, contact FEP Customer Support.
...... E ND OF STEPS ......
References “anlink” (p. A-4) “deanlink” (p. A-28)
...... 190-406-737 Alcatel-Lucent — Internal C-247 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 029
Message ID
NMT 029 NM link REGDTA poll requested too many entities
Description An NTM request for 5-minute register data was too large. Since the interface between the FEP and NTM has maximum sizes for these requests, this message should not be seen unless the request message has been corrupted somehow.
Parameters
link This number is the NTM link number associated with an NTM name. The NTM name/link association can be ascertained with the rsnlink command.
Warning
Corrective action Follow these steps:
......
1 Check link integrity and/or take the link down and bring it back up (i.e. deanlink, then anlink command).
......
2 If the condition continues, contact FEP Customer Support.
...... E ND OF STEPS ......
References “anlink” (p. A-4) “deanlink” (p. A-28) “tnlink” (p. A-53)
...... C-248 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 030
Message ID
NMT 030 NMT timed out waiting on REG data for NM link
Description The 5-minute register data that NM link link had requested was not available to send to NTM prior to close of the data collection window for this 5-minute interval.
Parameters
link This number is the NTM link number associated with an NTM name. The NTM name/link association can be ascertained with the rsnlink command.
Warning
Corrective action Follow these steps:
......
1 Use the rsentity or prtsint command to inspect the date/time that 5-minute data was last received for each active entity. Any entity for which data arrived after approximately 239 seconds into the 5-minute window is the likely candidate for which the timeout occurred.
......
2 If data for an entity was late, check the switch’s time versus the FEP’s and correct the switch time if necessary.
......
3 If data for a synchronous entity did not arrive at all, look for additional error messages with the NDC prefix to determine the exact cause of the problem.
......
4 If data for a GTD-5 entity did not arrive at all, determine if the connection between the FEP and the switch is still up (are discretes being collected?) and whether the switch might be in some sort of overload condition.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-249 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “rsentity” (p. A-42) “prtsint” (p. A-41)
...... C-250 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 037
Message ID NMT 037 NMT TERMINATED: Can't lock process into core
Critical
Description In order to function, the nmt process locks itself into core memory almost immediately upon coming up. If for some reason it cannot do this, the message above will be generated and the nmt process will exit. BaseWorX functions will respawn the nmt process up to four times, so it's possible that you could see four of these messages in short order.
Corrective action This is not a condition that would normally occur. Stop the FEP application by running stopfep and then restart it using startfep. If the message reappears, stop the FEP application and reboot the computer. If the message still appears, contact FEP Customer Support.
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-251 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 038
Message ID NMT 038 NMT TERMINATED: Can't enable messages
Description In order to function, the nmt process must enable an interprocess communication (IPC) message queue while initializing. If for some reason it cannot do this, the message above will be generated and the nmt process will exit. BaseWorX functions will respawn the nmt process up to four times, so it's possible that you could see four of these messages in short order. This is not a condition that would normally occur.
Critical
Corrective action Follow these steps:
......
1 Stop the FEP application by running stopfep and then restart it using startfep.
......
2 If the message reappears, stop the FEP application and reboot the computer.
......
3 If the message still appears, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-252 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 041
Message ID NMT 041 NMT TERMINATED: Can't disable messages
Description When the nmt process is terminated for any reason, it attempts to clean up any outstanding system resources prior to finally exiting. One of the resources it returns to the system is its message queue. If it has difficulty doing this, the above message is generated.
Status
Corrective action This is a status message only, because the process is on its way down. If there is a real problem, other messages will be generated the next time the process comes up. Any corrective action listed for those messages should be followed.
...... 190-406-737 Alcatel-Lucent — Internal C-253 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 042
Message ID
NMT 042 NMT TERMINATED: Got signal signal number
Description To terminate the nmt process, one of several UNIX signals can be sent to the process. This messages indicates which one. The signal number normally seen should be 15, but 9 or 18 may be seen occasionally. Any other number should be considered suspicious.
Parameters
signal numberUNIX signal number. What each signal number represents can be found in the SunOS 5.3 Reference Manual, Section 5 under signal (5).
Major
Corrective action No corrective action is needed if signal number is 15, 18, or 9 and stopfep has been run. If there are other signal numbers in the message or stopfep was not executed, contact FEP Customer Support.
...... C-254 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 045
Message ID
NMT 045 NMT:ALI Connection Failed (Abort), nm NTMOS name, code = errno, text string
Description A connection between the FEP and the NTMOS name specified has gone down or can't initially come up.
Parameters
NTMOS name The name of the NTM for which this message applies
errno An error number that will help isolate the cause
text string An explanation of why the connection attempt failed
Major
Corrective action The corrective action will depend heavily on why the connection attempt failed. One possible reason that a connection will fail is that NTMOS name has not been activated on the FEP. In this case, use anlink to do so. In any case, use tnlink to test the link between the FEP and NTM. Other possible reasons would indicate FEP database problems related to the definition of NTM links. To validate this, use the rsnlink command to look at all defined links. If this command comes back with garbage of any kind, restore the “/usra/tdms/nmt/ntmsinfo” file from your last Dynamic Data backup.
References “anlink” (p. A-4) “rsnlink” (p. A-44) “tnlink” (p. A-53) “Restoring dynamic data (all or some)” (p. 3-72)
...... 190-406-737 Alcatel-Lucent — Internal C-255 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 046
Message ID
NMT 046 NMT:send/write failed; nm NTMOS name, channel chan, code = errno text string
Description While attempting to send data to the specified NTM, FEP detected an error that prevented the data from being sent.
Parameters
NTMOS name The name of the NTM to which this message applies
chan This channel number is the channel number associated with a specific type of NTM data. The type of each data and its associated channel number are:
C Discrete Data h a n n e l
1 C Audit Data (Command/Response) h a n n e l
2
...... C-256 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
C Control Data (Command/Response) h a n n e l
3 C 5-minute Register Data. h a n n e l
4
The current status of each channel on each NTM link can be ascertained by with the rsnlink command.
errno This is a return value that should be used if you report this error to FEP Customer Support
text string An ASCII text string that attempts to explain exactly what problem was found
Minor
Corrective action If the text string says “Too many” then the capacity of the FEP/NTM interface has been surpassed. During FEP/NTM capacity testing this message would appear if volumes of data far above that guaranteed from the FEP were attempted. If you know the data volume is not greater than that advertised, check the network between the two systems for backlogs. If the FEP/NTM link is connected via Datakit, another possibility is that a circuit pack in the Datakit node (other than those used for the FEP to NTM interface) is failing and causing a large number of service requests of the Datakit node, which will decrease its ability to service valid data transfers. No other instance of this message is expected unless severe hardware and/or software malfunction occurs.
...... 190-406-737 Alcatel-Lucent — Internal C-257 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 047
Message ID
NMT 047 NMT:Link DOWN, NTMOS name, code = errno text string
Description The link to the named NTM has gone down. From the message text of the specific instance you should be able to tell if this is actually an error condition or a normal occurrence. For example, if NTM executes a command to bring down its side of the link, this message will be generated letting you know that the FEP received an abort message. Alternatively, if there is a software error while a connection is being brought up, the message will be generated with different explanatory text.
Parameters
NTMOS name The name of the NTM for which this message applies
errno An error code that will help FEP Customer Support diagnose the problem
text string ASCII text sting that gives additional information regarding why the link may have gone down
Minor
Corrective action If you believe corrective action should be taken, given the exact message text, contact FEP Customer Support.
...... C-258 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 048
Message ID
NMT 048 NMT: NTMOS name Link In Progress/UP
Description A link to the specified NTM has been successfully established.
Parameters
NTMOS name The name of the NTM for which this message applies
Status
Corrective action This message is for your information only. No action required.
...... 190-406-737 Alcatel-Lucent — Internal C-259 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 049
Message ID
NMT 049 ALI protocol error; nm NTMOS name code = errno text string
Description There has been a low level protocol error between the FEP and the specified NTM.
Parameters
NTMOS name The name of the NTM for which this message applies
errno An error code that will help FEP Customer Support diagnose the problem
text string ASCII text sting that gives additional information regarding why the link may have gone down
Minor
Corrective action If this error occurs once, you can ignore it. If it occurs frequently, contact FEP Customer Support with the exact message text.
...... C-260 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 050
Message ID
NMT 050 NMT: can't access field field in entity database
Description The nmt process cannot access data from the FEP entity database that it requires to forward control/audit requests.
Parameters
field The field which cannot be retrieved from the entity database
Major
Corrective action You should not see this message unless data in the “/usra/tusr/na/entity” directory has become corrupted. Restore all files in this directory from your last Dynamic Data backup and bring the FEP application back up.
References “Restoring dynamic data (all or some)” (p. 3-72)
...... 190-406-737 Alcatel-Lucent — Internal C-261 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 051
Message ID
NMT 051 NMT: Could not unlink file filename after processing, errno errno
Description The nmt process could not remove the file specified by filename. The UNIX error number that prevented it from doing so is in errno.
Parameters
filename The full UNIX path name of the file
errno The UNIX error number that was present
Minor
Corrective action Become the root user. Use the UNIX command ls -l filename to ascertain the date/time on the filename. If the date/time is prior to the time that the error message was generated, manually remove the file. If the date/time is after the time that the error message was generated, do nothing. If you see this message on a continual basis contact FEP Customer Support. Both the filename and errno fields from all NMT 051 messages will be important for FEP Customer Support to help you resolve the problem.
...... C-262 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 052
Message ID NMT 052 NMT: can't access shared memory
Description The nmt process cannot access a segment of shared memory that is critical to its operation. The FEP cannot perform its functions while this error is present.
Corrective action Stop the FEP application by running stopfep and then restart it using startfep. If the message reappears, contact FEP Customer Support.
Critical
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-263 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 054
Message ID
NMT 054 NMT: Received invalid message type type_no from NDC, entity entno
Description An invalid IPC message was received by the nmt process from an ndc process. You should never see the message coming from a correctly operating FEP.
Parameters
type_no Message type number that was invalid
entno The entity number for which the message was received
Warning
Corrective action Contact FEP Customer Support. Please have ready all log messages for 60 minutes prior to the occurrence of this message.
References “logCat” (p. A-37)
...... C-264 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 055
Message ID NMT 055 NMT: Can't get values from timeout file - defaults used
Description The “/usra/tdms/nmt/tmout.def” file cannot be found or cannot be read by the nmt process, therefore the default values for both control response and audit response timers will be used. You would see this message only if the nmt process restarted and one of the above conditions were true.
Warning
Corrective action You have three options to recover this file so it will be accessible the next time the nmt process is started when startfep is done: 1. If you want to use the standard values for this file delivered with the FEP application, become “root” and enter: echo “180 600 80 95" > /usra/tdms/nmt/tmout.def chown root /usra/tdms/nmt/tmout.def chgrp tdms /usra/tdms/nmt/tmout.def 2. You could alternatively restore “/usra/tdms/nmt/tmout.def” from your latest Dynamic Data backup. 3. If neither of the above is successful, contact FEP Customer Support. They will help you recreate this file with appropriate values.
Note: To maintain consistency with NTM, the values in the tmout.def file should not be changed without the written consent of Lucent Technologies. To do so voids support of the FEP/NTM interface.
References “Restoring dynamic data (all or some)” (p. 3-72)
...... 190-406-737 Alcatel-Lucent — Internal C-265 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 056
Message ID
NMT 056 NMT: Timeout values for sw_type are value1 (controls) and value2 (audits)
Description You should see this message each time the nmt process initializes.
Parameters sw_type The type of switch for which value1 and value2 are relevant. This field will either say GTD-5 switches or non GTD-5 switches.
value1 The timeout value for control responses. This value should always be 180 when sw_type is GTD-5 switches and 90 when sw_type is non GTD-5 switches.
value2 The timeout value for audit responses. This value should always be 600 when sw_type is GTD-5 switches and 70 when sw_type is non GTD-5 switches.
Status
Corrective action If the listed values are not those specified above, modify the “/usra/tdms/nmt/tmout.def” file. The file should contain one line consisting of “180 600 80 95". [Quotes are not included in the file.] You have three options to recover this file so it will be accessible the next time the nmt process is started when startfep is done: 1. If you want to use the standard values for this file delivered with the FEP application, become “root” and enter: echo “180 600 80 95" > /usra/tdms/nmt/tmout.def chown root /usra/tdms/nmt/tmout.def chgrp tdms /usra/tdms/nmt/tmout.def 2. You could alternatively restore “/usra/tdms/nmt/tmout.def” from your latest Dynamic Data backup. 3. If neither of the above is successful, contact FEP Customer Support. They will help you recreate this file with appropriate values.
...... C-266 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Note: To maintain consistency with NTM, the values in the tmout.def file should not be changed without the written consent of Lucent Technologies. To do so voids support of the FEP/NTM interface.
References “Restoring dynamic data (all or some)” (p. 3-72)
...... 190-406-737 Alcatel-Lucent — Internal C-267 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 057
Message ID
NMT 057 NMT: Timeout value [value1] for timer_type is out of range (0 to value2), default of value3 used
Description The “/usra/tdms/nmt/tmout.def” file has an invalid value in it for either the control or audit response timer, therefore, the default value for the timer will be used. You will see this message only if the nmt process restarts and finds inconsistencies in the tmout.def file.
Parameters
value1 Timer value found in the tmout.def file
timer_type Indicates which value is out of range. This field will contain one of the four following phrases: GTD-5 controls, GTD-5 audits, non GTD-5 controls, non GTD-5 audits.
value2 The maximum allowable timer value
value3 The default timer value
Status
Corrective action You have three options to recover this file so it will be accessible the next time the nmt process is started with startfep: 1. If you want to use the standard values for this file delivered with the FEP application, become “root” and enter: echo “180 600 80 95" > /usra/tdms/nmt/tmout.def chown root /usra/tdms/nmt/tmout.def chgrp tdms /usra/tdms/nmt/tmout.def 2. You could alternatively restore “/usra/tdms/nmt/tmout.def” from your latest Dynamic Data backup. 3. If neither of the above is successful, contact FEP Customer Support. They will help you recreate this file with appropriate values.
Note: To maintain consistency with NTM, the values in the tmout.def file should not be changed without the written consent of Lucent Technologies. To do so voids support of the FEP/NTM interface.
...... C-268 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “Restoring dynamic data (all or some)” (p. 3-72)
...... 190-406-737 Alcatel-Lucent — Internal C-269 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 058
Message ID NMT 058 NMT: Can't get value from tcp_port.def file - default used
Description The “/usra/tdms/nmt/tcp_port.def” file cannot be found or cannot be read by the nmt process, therefore the default value (of 1010) for the TCP/IP port number will be used. You will see this message only if the nmt process restarts and one of the above conditions is true. This number must always match the value that NTM uses as the socket number when they specify a TCP/IP address to a FEP. It should always be 1010 on both the FEP and NTM unless your network administrator specifies another number and it’s agreed to between the FEP and NTM administrators.
Warning
Corrective action You have three options to recover this file so it will be accessible the next time the nmt process is started with startfep: 1. If you want to use the standard values for this file delivered with the FEP application, become “root” and enter: echo “1010” > /usra/tdms/nmt/tcp_port.def chown root /usra/tdms/nmt/tcp_port.def chgrp tdms /usra/tdms/nmt/tcp_port.def 2. You could alternatively restore “/usra/tdms/nmt/tcp_port.def” from your latest Dynamic Data backup. 3. If neither of the above is successful, contact FEP Customer Support. They will help you recreate this file with the appropriate value.
References “Restoring dynamic data (all or some)” (p. 3-72)
...... C-270 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 059
Message ID
NMT 059 NMT: TCP/IP port number is value
Description You should see this message each time the nmt process initializes.
Parameters
value This is the TCP/IP socket number being used for TCP/IP connectivity to NTM. Unless it has been changed by mutual agreement between the FEP and NTM administrators, this number should be 1010.
Status
Corrective action This message is for your information only. No action required.
...... 190-406-737 Alcatel-Lucent — Internal C-271 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 060
Message ID
NMT 060 NMT: TCP/IP port number [value1] is out of range (value2 to value3), default used
Description The “/usra/tdms/nmt/tcp_port.def” file has an invalid value in it, therefore, the default value for the TCP/IP socket number (1010) will be used. You will see this message only if the nmt process restarts and finds inconsistencies in the tcp_port.def file.
Parameters
value1 The value found in the tcp_port.def file
value2 The minimum allowable port number value
value3 The maximum allowable port number value
Status
Corrective action You have three options to recover this file so it will be accessible the next time the nmt process is started with startfep: 1. If you want to use the standard values for this file delivered with the FEP application, become “root” and enter: echo “1010” > /usra/tdms/nmt/tcp_port.def chown root /usra/tdms/nmt/tcp_port.def chgrp tdms /usra/tdms/nmt/tcp_port.def 2. You could alternatively restore “/usra/tdms/nmt/tcp_port.def” from your latest Dynamic Data backup. 3. If neither of the above is successful, contact FEP Customer Support. They will help you recreate this file with the appropriate value.
References “Restoring dynamic data (all or some)” (p. 3-72)
...... C-272 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... NMT 061
Message ID
NMT 061 NMT CHILD TERMINATED: Got signal signal number
Description To terminate an nmt child process, one of several UNIX signals can be sent to the process. This message indicates which one was sent. The signal number normally seen should be 15, but 9 may be seen occasionally. Any other number should be considered suspicious. Under normal conditions, this message should only be seen when the FEP application software is being brought down with the stopfep command.
Parameters
signal numberUNIX signal number. What each signal number represents can be found in the SunOS 5.3 Reference Manual, Section 5 under signal (5).
Major
Corrective action No corrective action is needed if signal number is 15 or 9 and stopfep has been run. If there are other signal numbers in the message or stopfep was not executed, contact FEP Customer Support.
...... 190-406-737 Alcatel-Lucent — Internal C-273 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NMT 062
Message ID NMT 062 NMT Can’t execute rmNMTchild.
Description When the NMT process starts up, it will run a script to clean up an orphaned child process if one exists. If this script is missing or cannot be run, this message will appear and the NMT will continue processing.
Warning
Corrective action Follow these steps:
......
1 Verify that the “/usra/tdnms/nmt/rmNMTchild” file exists.
......
2 If it is missing, then restore the file from Dynamic Data Backup.
......
3 If the file is there, but not executable, then change the mode of the file by entering: chmod 755 /usra/tdms/nmt/rmNMTchild
...... E ND OF STEPS ......
References “Restoring dynamic data (all or some)” (p. 3-72)
...... C-274 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... RT — BaseWorX Rapid Transit Overview
Purpose This section provides all of the RT error messages.
Messages in this section include:
• RT 004
• RT 007
...... 190-406-737 Alcatel-Lucent — Internal C-275 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... RT 004
Message ID
RT 004 - Monitor starting, pid= pid
Description When the FEP application is started, one process that is brought up is the monitor process, which is actually a BaseWorX process used for rapid transit (RT) communication. You'll always see this message after a startfep or reboot has been done.
Parameters
pid The process ID of the monitor process
Status
Corrective action This message is for your information only. No action is required.
References “startfep” (p. A-46)
...... C-276 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... RT 007
Message ID RT 007 - Warning: Failed to lock shared memory.
Description Although this message may appear to be critical, it in fact is not, and should be ignored. This message is generated by BaseWorX and does not appear in later releases of BaseWorX. This message will be logged after a startfep or a reboot has been done.
Status
Corrective action This message is for your information only. No action is required.
References “startfep” (p. A-46)
...... 190-406-737 Alcatel-Lucent — Internal C-277 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... SLM — Synchronous Line Module Overview
Purpose This section provides all of the SLM error messages.
Messages in this section include:
• SLM 005
...... C-278 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... SLM 005
Message ID
SLM 005 SLM download failed on virtual channel chan
Description The FEP received a SLM download request across the specified virtual channel and it was not able to successfully service the request.
Parameters
chan The Datakit virtual channel that the incoming request used
Minor
Corrective action Follow these steps:
......
1 If the FEP is correctly downloading any SLM board, the likely problem is a hardware fault on the individual SLM board for which you received an error. In this instance, notify your Datakit administrator to diagnose the hardware problem.
......
2 If the FEP is not downloading any SLM board correctly, the problem is likely a software problem in the slmdwnld process. In this instance, contact FEP Customer Support.
......
3 Attempt to download a different SLM board (not currently out-of-service because of a fault) to determine which case you are seeing.
......
4 To determine which SLM board cannot download, use the steps outlined below.
Note: Not all instances of downloading a SLM board will cause a message to appear on the FEP. If the software on the Datakit node does not progress far enough to initiate a call to the Datakit download software on the FEP, the FEP will have no knowledge of the attempt. This information would only be available on the Datakit console.
...... 190-406-737 Alcatel-Lucent — Internal C-279 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Instructions for Finding the SLM Board: a. Ascertain which Datakit node/module number requested the download. The node/module number information is not communicated to the slmdwnld process; only the virtual channel over which the request is made is communicated. However, armed with that information, you can determine which node/module it was. b. Change to the directory “/var/opt/dk/log” and look for a file named “dksrvlog” using the UNIX command ls -l. There might also be a file named “dksrvlog.old”. From the time stamp of the SLM 005 message, determine whether the additional information you need is in “dksrvlog” or “dksrvlog.old”. For example, if the time stamp on the SLM 005 message is 10:26:28 Nov 4, 1995, and the output from the ls -l command is: $ ls -l total 1996 -r-Sr--r-- 1 root bin 22 Nov 1 15:33 dk.0.stfep1 -rw-r--r-- 1 root bin 1382 Nov 3 05:40 dkdaemonlog -rw-r--r-- 1 root bin 1042 Nov 1 15:07 dkdaemonlog.old -r-Sr--r-- 1 root bin 15 Nov 1 15:33 dkdmn.0 -rw-r--r-- 1 root bin 734625 Nov 4 10:45 dksrvlog -rw-r--r-- 1 root bin 261011 Nov 1 15:07 dksrvlog.old
The output you want will be in “dksrvlog”. Notice that the time on the “dksrvlog.old” file is before 10:26 on November 4. If the time on “dksrvlog.old” was after 10:26:28 on November 4, the information should be in “dksrvlog.old”.
Note: The “dksrvlog” and “dksrvlog.old” files wrap around. Therefore, if a message is particularly old, it may not be found in the system. For example, something from 08:17:34 on October 3, 1995, probably isn't here anymore. How long information stays around in the “dksrvlog” files is directly related to the frequency/volume of incoming call requests to your FEP. c. Use the UNIX command pg to scan the appropriate file. You'll be looking for a section of the file that is similar to: ------start of sample output------95.31830.R.3.8 eadast/stfep1.download oh/eadasd/?dwnld.eadasd.60.2.F IZZ.W88.P0 dkmgr: M=5,C=95,T=31830,URP=3,W=8,D=eadast/stfep1,U=,R=oh/eadasd/ ?dwnld,L= Nov 4 10:26:30 (7423) [0.095] Protocol “NULL”
...... C-280 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Nov 4 10:26:30 (7423) [0.095] REQUEST s=download, u=?=root, r=oh/ eadasd/?dwnld Nov 4 10:26:30 (7423) [0.095] DEBUG flag=u, uid=root, file=/usra/fep/bin/ slmdwnld, fixedparms=slmdwnld:%t Nov 4 10:26:30 (7423) [0.095] DEBUG linep=/dev/dk/0.095 rlinep=/dev/dk/ 0.095 Nov 4 10:26:30 (11268) [0.095] chkidle return 0 file = /usra/fep/bin/ slmdwnld Nov 4 10:26:31 (11268) [0.095] Send ioctl init = 3 Nov 4 10:26:31 (11268) [0.095] ORIGIN h=eadasd.60.2, c=/usra/fep/bin/ slmdwnld Nov 4 10:27:29 (7423) [0.095] EXIT l=/dev/dk/0.095 p=11268 e=x0 ------end of sample output------d. Notice that the time stamp of these messages is consistent with the time stamp of the SLM 005 message received. e. To find the slmdwnld that failed, match up the virtual channel number you have with what you find in the brackets [e.g., (0.095) above]. The first 0 means that this message relates to Datakit interface 0; since a FEP only has one interface card, this number should always be zero. The number after the “dot” (095 in our example) is the virtual channel number that this request came in across. Since it's possible that the FEP could be downloading more than one SLM at once, matching the channel number is important. The next line to look at is about four lines down from the top of our example. It has the “?dwnld” string in it. This line can tell you the Datakit node/module that failed. In our example, the Datakit node is “oh/eadasd” and the module number is 60. You can also see this information other places in the file, but the line reference has the full Datakit node address on it. f. You (or the Datakit administrator on the Datakit node implicated) can check the Datakit console for error messages regarding the specified module number.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-281 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... SYM — FEP System Overview
Purpose This section provides all of the SYM error messages.
Messages in this section include:
• SYM 001
• SYM 002
• SYM 003
• SYM 004
• SYM 006
• SYM 007
• SYM 011
• SYM 012
• SYM 014
• SYM 015
...... C-282 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... SYM 001
Message ID
SYM 001 open of file failed
Description The specified file cannot be opened. The cause of the problem may be the file path does not exist or incorrect file permission.
Parameters
file The full path and name of the file that cannot be opened
Minor
Corrective action Follow these steps:
......
1 Note the permission of the file by doing ls -l file.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-283 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... SYM 002
Message ID
SYM 002 create of file failed
Description The specified file cannot be created. The cause of the problem may be the file path does not exist or incorrect directory permission. You might get this error when creating, activating, or deactivating an entity.
Parameters
file The full path and name of the file that cannot be created
Minor
Corrective action Follow these steps:
......
1 Go to the directory to see if the directory even exists and what its permission is.
......
2 Enter cd path_name where path_name is the directory where the file is trying to be created.
......
3 If you are able to go to that directory, then check the permissions by entering ls -ld.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “centity” (p. A-13) “deaentity” (p. A-27)
...... C-284 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... SYM 003
Message ID
SYM 003 read of file failed
Description The specified file cannot be read. You might get this error when creating, changing, activating, or deactivating an entity.
Parameters
file The full path and name of the file that cannot be read
Minor
Corrective action Follow these steps:
......
1 Note the permission of the file by doing ls -l file.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-285 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... SYM 004
Message ID
SYM 004 write of file failed
Description Data cannot be written to the specified file. This would typically occur with an entity activation or deactivation. You might get this error when creating, activating, or deactivating an entity.
Parameters
file The full path and name of the file that is not writable
Minor
Corrective action Follow these steps:
......
1 Note the permission of the file by doing ls -l file.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-286 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... SYM 006
Message ID
SYM 006 message to process failed
Description You may see this error if an entity activation or deactivation fails. This error indicates a message queue problem.
Parameters
process The process name where the message is being sent
Minor
Corrective action Follow these steps:
......
1 Enter ipcs -qa and redirect the output to a file.
......
2 Use the logCat command to capture errors that occurred a few minutes before this error.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37)
...... 190-406-737 Alcatel-Lucent — Internal C-287 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... SYM 007
Message ID
SYM 007 can’t change directory to dir_name
Description Tried to change to the specified directory by dir_name, but failed. You may see this error when trying to create an entity.
Parameters
dir_name The full path and name of the directory
Minor
Corrective action Follow these steps:
......
1 Check to see if the directory exists by doing cd dir_name.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “centity” (p. A-13)
...... C-288 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... SYM 011
Message ID
SYM 011 bad entry in entities file, entity entity
Description An invalid value is present in the entity database for the specified entity. You may see this error when trying to activate an entity.
Parameters
entity FEP entity number of the entity containing invalid data
Major
Corrective action Follow these steps:
......
1 Run edbview entity number and redirect the output to a file to capture the database entry for the entity experiencing problems.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “centity” (p. A-13)
...... 190-406-737 Alcatel-Lucent — Internal C-289 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... SYM 012
Message ID
SYM 012 entity entity not properly created
Description The specified entity does not exist in the entity database. You may see this error when trying to activate or deactivate an entity.
Parameters
entity FEP entity number that is not found in the database
Major
Corrective action Follow these steps:
......
1 Verify that the entity exists by entering rsentity entity.
......
2 If the entity exists, then the database is having problems; run edbview entity number and redirect the output to a file to capture the database entry for this entity.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “deaentity” (p. A-27) “rsentity” (p. A-42)
...... C-290 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... SYM 014
Message ID
SYM 014 System error
Description You may see this error when trying to activate, change, or deactivate an entity. You could also see this when running the tlentity command.
Parameters
System errorWill be replaced by a message from the command you were trying to run
Minor
Corrective action Follow these steps:
......
1 Use the logCat command to capture errors that occurred a few minutes before the SYM 014 error was logged.
......
2 Use appstat to verify that all processes are running.
......
3 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “appstat” (p. A-5) “chentity” (p. A-17) “deaentity” (p. A-27) “logCat” (p. A-37) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-291 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... SYM 015
Message ID
SYM 015 can’t access fld_name field in entity database
Description Failed to access the specified field in the entity database. You may see this when running the tlentity command.
Parameters
fld_name Will be replaced by the field name that could not be accessed
Major
Corrective action Follow these steps:
......
1 Use the logCat command to capture errors that occurred a few minutes before the SYM 015 error was logged.
......
2 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “logCat” (p. A-37) “tlentity” (p. A-48)
...... C-292 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN — GTD-5 Translators Overview
Purpose This section provides all of the TRN error messages.
Messages in this section include:
• TRN 001
• TRN 002
• TRN 003
• TRN 004
• TRN 005
• TRN 006
• TRN 007
• TRN 008
• TRN 009
• TRN 010
• TRN 011
• TRN 012
• TRN 013
• TRN 014
• TRN 015
• TRN 016
• TRN 017
• TRN 018
• TRN 019
• TRN 020
• TRN 021
• TRN 022
• TRN 023
...... 190-406-737 Alcatel-Lucent — Internal C-293 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
• TRN 024
• TRN 025
• TRN 026
• TRN 027
• TRN 028
• TRN 029
• TRN 030
• TRN 031
• TRN 032
• TRN 033
• TRN 034
• TRN 035
• TRN 036
• TRN 037
• TRN 038
• TRN 039
• TRN 040
• TRN 041
• TRN 042
• TRN 044
• TRN 045
• TRN 046
• TRN 047
• TRN 048
• TRN 049
• TRN 050
...... C-294 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 001
Message ID
TRN 001 translator_process started.
Description One of the 3 GTD-5 translator processes has started up: “ctlAud”, “transdisc” or “trans5min”. This normally appears after startfep has been run.
Parameters
translator_processThe translator process that just came up
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-295 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 002
Message ID TRN 002 An environmental variable is not set correctly. Either EDCS_ROOT, CCP_RT_BASE or FEP_ROOT is not defined correctly.
Description These variables are required by all the GTD-5 translator processes. The result of this message is that the GTD-5 translator processes will die, resulting in no collection of 30- second reports or 5-minute reports from your GTD-5 entities. In addition, no controls or audits can be sent to your GTD-5 entities and no GTD-5 entities may be activated or deactivated.
Critical
Corrective action Follow these steps:
......
1 Find out what EDCS_ROOT, CCP_RT_BASE and FEP_ROOT are set to by logging into your FEP with “fep” login and entering: echo $EDCS_ROOT echo $CPP_RT_BASE $FEP_ROOT Result: The values should be “/usra/tdms/edcs”, “/usra/baseworx/ccprt/config_info” and “/usra/fepbin”, respectively.
......
2 Use the logCat command to capture errors that occurred a few minutes before the TRN 002 error was logged.
......
3 Stop and start the FEP application, using the stopfep and startfep commands.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-296 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-297 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 003
Message ID
TRN 003 translator_process cannot open the data distributor
Description The specified GTD-5 translator_process cannot retrieve incoming data from its data distributor channel. If the process generating this error is the ctlAud process, then no controls or audits can be sent to your GTD-5 entities and no GTD-5 entities may be activated or deactivated. If the process is transdisc, then no 30-second data will be processed by the FEP. Likewise, if the process is trans5min, then no 5-minute data will be processed by the FEP.
Parameters
translator_processThe GTD-5 translator process that cannot retrieve data from the data distributor
Critical
Corrective action Follow these steps:
......
1 Use the logCat command to capture errors that occurred a few minutes before the TRN 003 error was logged.
......
2 Run appstat to see if any processes are respawning.
......
3 Run stopfep followed by startfep to rectify the situation.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-298 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “appstat” (p. A-5) “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-299 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 004
Message ID
TRN 004 translator_process unable to initialize queue to EDCS
Description The specified GTD-5 translator process cannot attach to EDCS, which is the process that collects all data from GTD-5 entities. If the process generating this error is the ctlAud process, then no controls or audits can be sent to your GTD-5 entities and no GTD-5 entities may be activated or deactivated. If the process is transdisc, then no 30-second data will be processed by the FEP. Likewise, if the process is trans5min, then no 5-minute data will be processed by the FEP.
Parameters
translator_processThe GTD-5 translator process that cannot connect to the EDCS queue
Critical
Corrective action Follow these steps:
......
1 Use the logCat command to capture errors that occurred a few minutes before the TRN 004 error was logged.
......
2 Run appstat to see if any processes are respawning.
......
3 Run stopfep followed by startfep to rectify the situation.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-300 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “appstat” (p. A-5) “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-301 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 005
Message ID
TRN 005 There is an outstanding audit request for entity entity
Description The control and audit translator received an audit request from NTM while currently processing another audit. Only one audit may be processed on the FEP at a time.
Parameters
entity FEP entity number of the switch that NTM wants to audit
Warning
Corrective action Ask the NTM person requesting this audit to wait until the outstanding audit has completed before starting this audit again.
...... C-302 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 006
Message ID
TRN 006 Unrecognized control or audit request sent by NTMOS for entity entity
Description NTM has requested an audit or a control (for a GTD-5 entity) that the FEP does not understand. The NTM has encoded the request incorrectly, the FEP has interpreted the request incorrectly, or the request was garbled on the network between the NTM and FEP machines.
Parameters
entity FEP entity number of the switch that will not receive the control or audit request
Warning
Corrective action Follow these steps:
......
1 Ask the NTM person what kind of audit or control he or she requested
......
2 Relay this information to FEP and NTM Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-303 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 007
Message ID
TRN 007 There is an outstanding control request for entity entity
Description The control and audit translator received a control request from NTM while currently processing another control for that same entity. Only one control per entity may be processed on the FEP at a time.
Parameters
entity FEP entity number of the switch that is currently processing a control
Warning
Corrective action Ask the NTM person requesting this control to wait until the outstanding control for this entity has completed before starting another control for this entity.
...... C-304 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 008
Message ID
TRN 008 No control response from entity entity. Control request has timed out (180 seconds)
Description The FEP has received a control request (for a GTD-5 switch) from NTM and has forwarded it to the switch. However, the FEP has not received a response from the switch within its timeout period (180 seconds).
Parameters
entity FEP entity number of the switch that has not responded to the FEP control request
Minor
Corrective action Follow these steps:
......
1 Ask switch personnel to verify that the switch received the request. It's possible the switch received the request but is very busy and thus hasn't responded to the request yet.
......
2 Ask the NTM person who sent the request to audit the switch to see if the control was actually applied.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-305 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 009
Message ID
TRN 009 Trying to match control request on offset offset, but bptr is out of bounds data is data, msgLength is msgLength and bptr is bptr
Description The FEP has received a control or audit request from NTM and is trying to determine what kind of control or audit request it is. However, the FEP cannot access the data used for distinguishing the requests received from NTM. Either the FEP is looking in the wrong position for these bytes or an invalid request was sent from NTM to the FEP.
Parameters
offset The particular byte in the data that the FEP is trying to access in order to identify the kind of request it received
data The binary message received from NTM that the FEP is trying to identify
msgLength The length of the binary message (in bytes) received from NTM
bptr A pointer to the message (variable data defined above) received from NTM
Major
Corrective action Follow these steps:
......
1 Use the logCat command to capture errors that occurred a few minutes before the TRN 009 error was logged.
......
2 Run appstat to see if any processes are respawning.
......
3 Notify FEP Customer Support of this condition.
...... E ND OF STEPS ......
...... C-306 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “appstat” (p. A-5) “logCat” (p. A-37)
...... 190-406-737 Alcatel-Lucent — Internal C-307 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 010
Message ID TRN 010 Trying to read control request but offset to read is out of bounds. Control request is probably missing some data. offset is offset but msgLength is msgLength
Description The FEP has identified a particular control request received from NTM. The FEP is now trying to translate the request from a binary stream to an ASCII command that the GTD-5 switch will understand. The translation routine is requesting data from a particular offset in the binary stream but that offset is inaccessible, so the translation fails. Either the offset is an invalid number or the FEP did not receive the entire amount of data so that offset does not exist in the data. This message is different from the TRN 009 message in that the FEP is able to identify the type of request it received but is unable to translate it.
Parameters offset The particular byte in the data that the FEP is trying to access in order to translate it into a meaningful GTD-5 ASCII string
msgLength The length of the binary message (in bytes) received from NTM
Major
Corrective action It's possible that the message just got garbled in the network between the NTM and FEP machines. Have NTM resend the request, and if you see this error again, report it to FEP Customer Support.
...... C-308 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 011
Message ID
TRN 011 Job number mismatch for entity entity for a control or audit response
Description The FEP has received a message from the specified GTD-5 entity. However, there is no outstanding control or audit on the FEP having the same job number contained in the response. The message is just thrown away.
Parameters
entity FEP entity number of the switch that sent the message
Warning
Corrective action It's possible that someone at the switch site applied a control or audit directly, instead of through NTM. If this is the case, the FEP might see the (“I@” and “R@”) messages produced by the switch and try to analyze those messages but fail. In this scenario, this message does not indicate a problem; however, controls and audits should be applied through NTM and not directly at the switch. If you see this message repeatedly when trying to apply control or audits through NTM, report it to FEP Customer Support.
...... 190-406-737 Alcatel-Lucent — Internal C-309 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 012
Message ID
TRN 012 Bad control response for entity entity
Description The FEP is trying to form the binary control response to send back to NTM, but is unable to populate some part of the response header. This message could represent a variety of problems. The FEP could be having a problem with identifying the generic of the GTD-5 switch, the time and date fields, or the error code or error type fields; or maybe the first part of the ASCII response does not match any string the FEP expects. It's also possible the FEP is trying to access a configuration file used for translation, but the file is missing or unreadable.
Parameters
entity FEP entity number of the switch that received the bad control response
Minor
Corrective action See if this problem is reproducible by having NTM resend the request. If the problem happens again, contact FEP Customer Support. Support personnel will probably turn on fault-isolation tools and ask for the control to be resent from NTM.
...... C-310 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 013
Message ID TRN 013 ctlAud proc: Can't access shared memory
Description There are two scenarios that may produce this error. First, an attempt has been made to activate or deactivate a GTD-5 entity. The activation routine is unable to attach to shared memory, which is necessary to update the activation status of the entity. Secondly, the FEP may be attempting to forward a control or audit request to the switch, requiring shared memory to be updated (to prevent a user from inadvertently deactivating an entity while a control or audit is outstanding on that entity).
Major
Corrective action The FEP application needs to be restarted. Run stopfep followed by startfep, which will reinitialize shared memory.
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-311 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 014
Message ID
TRN 014 ctlAud proc: Can't access field field in entity database
Warning
Description The ctlAud process received an entity activation request for a GTD-5 switch. It then called the appropriate activation routine but this routine was unable to retrieve one or more fields from the entity database.
Parameters field The field in the entity database that the activation routine was trying to retrieve
Corrective action Follow these steps:
......
1 Try activating the entity again, using the aentity command.
......
2 If the entity still fails to come up, run edbview entity number and redirect this output to a file.
......
3 Report this information to FEP Customer Support. They may have you do a stopfep, restore the “/usra/tusr/na/entity/entities” file, and then do a startfep to restore the database to a previous state.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “startfep” (p. A-46) “stopfep” (p. A-47) “Restoring dynamic data (all or some)” (p. 3-72)
...... C-312 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 015
Message ID TRN 015 Data collection started; entity “entity” (p. C-313)
Description Either a user activated an entity (using aentity command) or a startfep was just done, which automatically activates all entities that were active when the stopfep command was done or when the FEP was rebooted.
Parameters
entity FEP CLLI code of the switch that was just activated
Status
Corrective action This message is for your information only. No action is required.
References “aentity” (p. A-3) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-313 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 016
Message ID
TRN 016 Data collection stopped; entity entity
Description A user deactivated an entity (using deaentity command).
Parameters
entity FEP CLLI code of the switch that was just deactivated
Status
Corrective action This message is for your information only. No action is required.
References “deaentity” (p. A-27)
...... C-314 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 017
Message ID
TRN 017 ctlAud proc: Received invalid entity activation; entity entity pdn pdn
Minor
Description You would see this message if a GTD-5 entity activation had problems. For example, you would probably see this message after seeing either the TRN 014, TRN 021, or TRN 022 message. This typically indicates a problem with retrieving fields from the entity database for the specified entity.
Parameters entity FEP entity number of the switch that failed activation
pdn This value indicates a GTD-5 entity
Corrective action Follow these steps:
......
1 Try activating the entity again, using the aentity command.
......
2 If the entity still fails to come up, run edbview entity number and redirect this output to a file.
......
3 Report this information to FEP Customer Support. They may have you do a stopfep, restore the “/usra/tusr/na/entity/entities” file, and then do a startfep to restore the database to a previous state.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-315 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “aentity” (p. A-3) “startfep” (p. A-46) “stopfep” (p. A-47) “Restoring dynamic data (all or some)” (p. 3-72)
...... C-316 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 018
Message ID TRN 018 dc_mgr proc: Entity reactivation complete
Description Most likely, the startfep command has just been run or the FEP has just been rebooted. When either of these two events occur, the FEP will automatically activate all entities that were active prior to a stopfep or a reboot.
Status
Corrective action No action is required, as long as a startfep or reboot was just done. Otherwise, do a stopfep followed by a startfep to correct the problem of entities continuously being activated.
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-317 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 019
Message ID
TRN 019 ctlAud proc: ENT_ACT: Bad entity entity
Description The specified entity number is out of range. The FEP supports up to 200 entities, ranging 0 to 199. Most likely, a user was trying to activate an entity and supplied an entity number that was out of range.
Parameters
entity The entity number that was rejected by the entity activation routine
Warning
Corrective action Follow these steps:
......
1 Rerun the command (most likely, the aentity command) using a valid entity number.
......
2 If the command still fails, run rsentity CLLI code and this should give you the valid entity number corresponding to the CLLI code.
......
3 Use this entity number to rerun your (aentity) command.
......
4 If you still are experiencing problems, call FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “rsentity” (p. A-42)
...... C-318 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 020
Message ID
TRN 020 ctlAud proc: ENT_ACT: Entity entity number already active
Description A user has probably run the aentity command for an entity that is already activated.
Parameters
entity numberThe entity number that is already activated
Warning
Corrective action Follow these steps:
......
1 Use the rsentity entity number command to verify that the entity is activated.
......
2 If the output from rsentity shows “OFF” in the STATUS column, then something is wrong and you should report this to FEP Customer Support.
......
3 Otherwise, you know you supplied an entity that was already active.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “rsentity” (p. A-42)
...... 190-406-737 Alcatel-Lucent — Internal C-319 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 021
Message ID TRN 021 ctlAud proc: ENT_ACT: Can't get valid EDCS message ID
Description The FEP received an entity activation or deactivation request for a GTD-5 switch. However, the FEP was unable to connect to the Event Data Collection Subsystem (EDCS). This prohibits the FEP from adding or deleting the specific channel in EDCS corresponding to a particular entity. This will cause the entity activation or deactivation to fail.
Minor
Corrective action Follow these steps:
......
1 Try activating or deactivating the entity again, using the aentity or deaentity command.
......
2 If this fails again, try doing stopfep followed by a startfep to clear the problem.
......
3 If the entity still fails to activate or deactivate properly, run edbview entity number and redirect this output to a file.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “deaentity” (p. A-27) “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-320 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 022
Message ID
TRN 022 ctlAud proc: ENT_ACT: Can't notify EDCS to connect entity entity
Description The FEP received an entity activation or deactivation request for a GTD-5 switch. Although the FEP was able to connect to the Event Data Collection Subsystem (EDCS), it was unable to add or delete the channel associated with the specified entity number. This will cause the entity activation or deactivation to fail.
Parameters
entity FEP entity number of the switch whose EDCS channel could not be added or deleted
Major
Corrective action Follow these steps:
......
1 Try activating or deactivating the entity again, using the aentity or deaentity command.
......
2 If this fails again, try doing stopfep followed by a startfep to clear the problem.
......
3 If the entity still fails to activate or deactivate properly, run edbview entity number and redirect this output to a file.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-321 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “aentity” (p. A-3) “deaentity” (p. A-27) “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-322 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 023
Message ID TRN 023 transdisc proc: Can't access shared memory
Description The transdisc process could not attach to shared memory. This means the FEP cannot process any discrete reports received from GTD-5 entities. Something is seriously wrong with the FEP.
Major
Corrective action Follow these steps:
......
1 Restart the FEP, using the stopfep command followed by the startfep command.
......
2 If this error is logged again after the FEP has been restarted, run appstat and redirect the output to a file.
......
3 Gather errors occurring a few minutes before the TRN 023 was generated, using the logCat command.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “appstat” (p. A-5) “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-323 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 024
Message ID
TRN 024 transdisc proc: No Discrete report received for entity entity during the last 30-second interval
Description Although the specified GTD-5 entity is activated, the FEP did not receive a discrete report from this entity within the last 30-second period. This could indicate the switch's clock may be “walking” (not sending a discrete report every 30 seconds exactly, but maybe every 31 seconds).
Parameters
entity FEP entity number of the GTD-5 switch whose current discrete report is missing
Warning
Corrective action If you see this message only once, then you may want to inquire about the switch's clock (if it tends to “walk” or not). If the switch walks, you will occasionally lose a discrete report. If you repeatedly see this message, there may be a problem with the switch or the network between the switch and the FEP. In addition to discrete data loss, there may be 5-minute data loss for this entity. To verify this, deactivate the entity using the deaentity command and then run the tlentity command to see what the switch is outputting. If you see discrete data in the tlentity output, check the time stamps of the discrete data messages to verify that they are coming out every 30 seconds. If you are able to use tlentity and see discrete (and 5- minute) report output, then the network between the switch and the FEP is OK. If, however, you are unable to see data from tlentity, ask someone at the switch site to verify that the switch is sending data properly. If the switch seems OK, refer this problem to your networking personnel to see why the data is getting lost between the switch and the FEP.
...... C-324 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “deaentity” (p. A-27) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-325 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 025
Message ID TRN 025 transdisc proc: Cannot initialize
Description The discrete translator cannot be brought up because an environmental variable is set incorrectly, it cannot open its data pool, or it cannot attach to the Event Data Collection Subsystem (EDCS). In any case, the transdisc process has died and no discretes received from GTD-5 entities will be processed.
None
Corrective action Follow these steps:
......
1 Find out what EDCS_ROOT, CCP_RT_BASE and FEP_ROOT are set to by logging into your FEP with “fep” login and entering: echo $EDCS_ROOT echo $CPP_RT_BASE $FEP_ROOT Result: The values should be “/usra/tdms/edcs”, “/usra/baseworx/ccprt/config_info” and “/usra/fepbin”, respectively.
......
2 Use the logCat command to capture errors that occurred a few minutes before the TRN 002 error was logged.
......
3 Stop and start the FEP application, using the stopfep and startfep commands.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-326 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-327 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 026
Message ID
TRN 026 transdisc proc: Cannot get entity type for entity entity
Description This message is generated if the discrete translator cannot retrieve the entity type for the specified entity from the entity database.
Parameters
entity FEP entity number of the switch with an invalid entity type
Major
Corrective action Follow these steps:
......
1 Run the command rsentity entity and verify that the TYPE field contains the valid entity type.
......
2 If the entity type is wrong in the TYPE field: a. Deactivate the entity using deaentity b. Use the chentity command to correct the entity type c. Reactivate the entity using aentity
...... E ND OF STEPS ......
References “aentity” (p. A-3) “chentity” (p. A-17) “deaentity” (p. A-27) “rsentity” (p. A-42)
...... C-328 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 027
Message ID TRN 027 GTD-5 Discrete translation process initialized
Description The discrete translator has successfully been started.
Status
Corrective action This message is for your information only. No action is required.
...... 190-406-737 Alcatel-Lucent — Internal C-329 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 028
Message ID
TRN 028 process translation process terminating
Description The specified GTD-5 translation process has received a signal to stop processing (probably from the stopfep command), so it is shutting down.
Parameters
process The GTD-5 process that received the signal to terminate
Status
Corrective action If you see this message after doing a stopfep, then no action is required. However, if you see this message when you believe the FEP to be in a running state, then something is wrong. For the second case, run appstat and redirect the output to a file. Capture recent error messages by using the logCat command to gather errors that occurred a few minutes before the TRN 028 error, and redirect the output to a file. Report this information to FEP Customer Support.
References “appstat” (p. A-5) “logCat” (p. A-37)
...... C-330 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 029
Message ID
TRN 029 Sent control or audit request to entity entity but did not receive a response from switch
Description The FEP has received a binary control or audit request from NTM and has successfully translated it into an ASCII GTD-5 command. The FEP has tried to get the switch's attention (by sending a ctl b) so that it may send the ASCII command, but the switch has not responded with the expected “I@” prompt. The FEP will wait at most 10 seconds to get the “I@” prompt back and then quit, producing this error message.
Parameters
entity FEP entity number of the switch that did not send a response back to the FEP
Major
Corrective action Possibly the switch is busy and is thus taking a long time to respond to the ctl b sent to it. There could also be a problem with the network between the FEP and the GTD-5 switch where a ctl b is being garbled or blocked by the network. To determine this, deactivate the entity on the FEP and run the tlentity command. After seeing a discrete report appear on your terminal, type a ctl b sequence and see if the switch responds with an “I@” prompt. If the switch responds but is very slow in responding, then you know the switch is busy. You may want to inquire as to why and retry this control or audit request at a later time. If the switch does not respond to your ctl b sequence, then you should retry it at the switch directly to make sure the switch does respond to ctl b when you eliminate the network between it and the FEP. Assuming the switch does respond to ctl b directly, inquire with your networking people as to why the ctl b is being blocked between the FEP and the switch.
References “deaentity” (p. A-27) “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-331 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
...... C-332 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 030
Message ID
TRN 030 ctlAud could not write control or audit response for entity entity
Description The FEP has finished processing a control or audit request. It has a formed a binary response that should be written to a file and then shipped back to NTM. However, the FEP was unable to write the binary response to a file.
Parameters
entity FEP entity number of the switch whose response cannot be written to a file or sent to the NMT
Major
Corrective action Follow these steps:
......
1 Use the df /raw command to see if there is ample disk space to write the file. The “capacity” column in the df output indicates the percentage of space used in the “/raw” filesystem. So, if this value is high (95% to 100%), then old data is probably not getting properly removed. If this is the case, report the condition to FEP Customer Support.
......
2 If, however, you do have ample disk space on the “/raw” filesystem, use the logCat command to capture errors that occurred a few minutes before the TRN 030 error was logged. Also, run appstat to see if any processes are respawning. Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-333 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 031
Message ID
TRN 031 No audit response from entity entity. Audit request has timed out (10 minutes)
Description The FEP has received an audit request from NTM and has forwarded it to the switch. The switch responded to the initial request from the FEP (ctl b), allowing the FEP to send the audit request. However, the FEP has not received the entire audit response from the switch within its timeout period (10 minutes).
Parameters
entity FEP entity number of the switch that has failed to send all its audit responses to the FEP within 10 minutes
Minor
Corrective action Ask switch personnel to verify that the switch received the request. It's unlikely that the switch did not receive the request, but if it didn't, then this problem can be attributed to network problems between the FEP and the GTD-5 switch. It's more likely that the switch received the request but is very busy and thus hasn't responded fully to the request yet. In this situation, we recommend retrying the audit at a later time, when the switch may have more idle time.
...... C-334 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 032
Message ID
TRN 032 process cannot get data from EDCS data distributor
Description Something is seriously wrong with the FEP and the specified process cannot retrieve data from the Event Data Collection Subsystem (EDCS). This means if the transdisc process logged this message, no discretes from GTD-5 entities will be processed. Likewise, if the trans5min process logged this message, no 5-minute reports from GTD-5 entities will be processed. And last, if the ctlAud process logged this message, no controls or audits or entity activations or deactivations will work for GTD-5 entities.
Parameters
process The GTD-5 translation process that cannot get data from EDCS
Critical
Corrective action Follow these steps:
......
1 Restart the FEP application by entering stopfep followed by startfep.
......
2 If this error repeats, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... 190-406-737 Alcatel-Lucent — Internal C-335 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 033
Message ID
TRN 033 process translation process abnormally terminating (sig signal)
Description The specified process received a signal telling it to shut down. This is abnormal because it is not the result of a stopfep.
Parameters
process The GTD-5 translation process that terminated
signal The UNIX signal number the GTD-5 translation process received
Major
Corrective action Follow these steps:
......
1 Run appstat and redirect the output to a file. There may be other processes that have died.
......
2 Use the logCat command to capture error messages that occurred a few minutes before the TRN 033 message.
......
3 Restart the FEP by entering stopfep followed by startfep.
......
4 Report this information to FEP Customer Support.
...... E ND OF STEPS ......
...... C-336 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... References “appstat” (p. A-5) “logCat” (p. A-37) “startfep” (p. A-46) “stopfep” (p. A-47) SunOS 5.3 Reference Manual, Section 5 under signal (5)
...... 190-406-737 Alcatel-Lucent — Internal C-337 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 034
Message ID
TRN 034 A control/audit command is outstanding on entity entity, deactivation will occur after the command completes
Description A GTD-5 entity may not be deactivated while the FEP is processing a control or an audit for that specific entity. Thus, when you see this message, the entity will remain active until the control or audit finishes, and then it will be deactivated.
Parameters
entity FEP entity number of the GTD-5 switch that has an outstanding control or audit
Status
Corrective action This message is for your information only. No action is required.
References “Deactivating a switch-FEP link” (p. 4-30)
...... C-338 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 035
Message ID
TRN 035 Cannot retrieve CLLI from shared memory for entity entity
Description The FEP was trying to process a control or an audit for a GTD-5 entity and it was unable to get the entity CLLI code from the entity database. Most likely, this means the entity database has a problem. This will result in the control or audit failing.
Parameters
entity FEP entity number of the GTD-5 switch whose CLLI code is inaccessible
Minor
Corrective action Follow these steps:
......
1 Verify that the entity is active and its CLLI code is correct, using the rsentity entity command.
......
2 If the CLLI code does not look correct, fix it using the chentity command.
......
3 Look for additional errors that occurred a few minutes prior to the TRN 035 message, using the logCat command and redirecting the output to a file.
......
4 If all looks OK in the rsentity output, then try deactivating the entity and then activating it, using the deaentity and aentity commands.
......
5 If this does not work, restart the FEP, using the stopfep and startfep commands.
...... 190-406-737 Alcatel-Lucent — Internal C-339 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
6 If you have to do this step, you should report this to FEP Customer Support.
...... E ND OF STEPS ......
References “aentity” (p. A-3) “deaentity” (p. A-27) “logCat” (p. A-37) “rsentity” (p. A-42) “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-340 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 036
Message ID
TRN 036 ENT_ACT: Activation failed - entity entity under test
Description The requested entity could not be activated because someone is testing the link to the entity (tlentity).
Parameters
entity FEP entity number of the switch that could not be activated
Warning
Corrective action This message is for your information only. No corrective action is required, but if the entity needs to be activated, contact the user who is executing the tlentity command on the requested entity and ask the user to quit the tlentity command. To find out who the user is, enter w | grep tlentity | egrep -v grep. The user's login ID will appear in the left-most column.
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-341 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 037
Message ID
TRN 037 Five minute proc: Received a report for a bad entity number (entity)
Description The 5-minute translator received a report with an invalid entity number for a GTD-5 switch.
Parameters
entity Invalid entity number received by the 5-minute translator
Major
Corrective action This message indicates a problem in the network or with the FEP entity database. Follow these steps:
......
1 Run rsentity entity to see if the FEP recognizes this entity number.
......
2 Please report this information to FEP Customer Support.
...... E ND OF STEPS ......
References “rsentity” (p. A-42)
...... C-342 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 038
Message ID
TRN 038 Five minute proc: received an incomplete report for entity entity, starting on the new report
Description The 5-minute report is not being received by the FEP in time for the report to be processed.
Parameters
entity FEP entity number of the GTD-5 switch sending the report late
Major
Corrective action There are several reasons this message will occur. First, the entity's time may not be in sync with the FEP's time. Also, the network between the entity and the FEP may be having problems, causing the 5-minute report to be late in arriving at the FEP. Finally, the switch might be having problems, causing it to be very slow with outputting the 5-minute report. If the switch's clock differs from the FEP's clock by more than plus or minus 20 seconds, synchronize the switch's time to the FEP's time. In doing this, you should not alter the FEP's time, as the FEP automatically synchronizes its clock to its corresponding NTM. If this does not eliminate this error, use the tlentity command to see when the switch is sending the 5-minute report. If the switch is late sending the report or you do not see any report in the tlentity output, ask switch personnel to verify that the report is leaving the switch on time. If the report is leaving the switch on time, then refer the problem to your networking personnel as to why the report is received late.
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-343 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 039
Message ID
TRN 039 Five minute proc: received an invalid report header for entity entity
Description The 5-minute translator received a report with a non-standard header.
Parameters
entity FEP entity number of the GTD-5 switch sending a non-standard report header
Major
Corrective action This message typically indicates the switch is sending data too early. The 5-minute translator is expecting the report header and is receiving the middle of a switch report. Synchronize the switch time to the FEP system time. Remember, don't change the FEP's time; it syncs to NTM automatically. If, however, the times are in sync between the switch and the FEP, please contact FEP Customer Support.
...... C-344 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 040
Message ID
TRN 040 process name translation for entity entity failed
Description One of the GTD-5 translator processes, transdisc or trans5min, has failed in trying to translate a switch message.
Parameters
process nameName of the FEP translator that failed
entity FEP entity number of the GTD-5 switch sending the message
Major
Corrective action This message indicates some of the data received by the FEP translator's could not be processed. Typically, this problem appears if the data being sent by the switch is corrupted (because of transmission problems) before it reaches the FEP. To confirm transmission problems, use the tlentity command to see how the report looks as it comes into the FEP. If the report seems corrupted in the tlentity output, then check with switch personnel to see if the report being sent from the switch is identical to what is seen on the FEP. If the reports differ, then the report is being corrupted in the network between the switch and the FEP. If the reports are identical, then either the switch has a problem or the FEP has a problem. If switch personnel think the report being outputted by the switch is valid, refer this problem to FEP Customer Support.
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-345 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 041
Message ID TRN 041 Five minute translation received a report for entity “entity” (p. C-346) outside the valid time range
Description The 5-minute translator received parts of a switch report before or after the valid time that the report should have been received.
Parameters
entity FEP entity number of the GTD-5 switch that failed during testing
Major
Corrective action Contact switch personnel to sync the entity's system time to the FEP's time.
...... C-346 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 042
Message ID TRN 042 Could not read the report processing times from the report configuration file. Setting the report processing times as seconds seconds before the interval and seconds seconds into the five minute interval.
Description Since the configuration file could not be read, the trans5min process is setting the report processing for each 5-minute period to the default setting.
Parameters
seconds The number of seconds a switch report can arrive before the start of a 5- minute period, or the number of seconds into the 5-minute period
Warning
Corrective action Follow these steps:
......
1 Enter cd /usra/tdms/trans5min followed by ls -l rpt_times.def.
......
2 If the file is missing, restore it from the latest Dynamic Data backup.
......
3 If the file is there, make sure the file is readable; enter cat rpt_times.def. The contents will probably say “20 240" (without the double quotes).
......
4 If you cannot read the file at all, become “root” and enter chmod 644 rpt_times.def (assuming you're still under the “/usra/tdms/trans5min” directory).
......
5 If, however, you were able to read the contents and it didn't look correct, restore this file from Dynamic Data backup.
...... 190-406-737 Alcatel-Lucent — Internal C-347 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
......
6 The next time the FEP application is restarted, the trans5min process will pick up the new report time values and you should not see this error.
...... E ND OF STEPS ......
References “Restoring dynamic data (all or some)” (p. 3-72)
...... C-348 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 044
Message ID TRN 044 Report time boundaries in the configuration file were invalid. Setting the report processing times as seconds seconds before the interval and seconds seconds into the five minute interval.
Description Since the configuration file contained invalid time boundaries, the trans5min process is setting the report processing for each 5-minute period to the default setting.
Parameters
seconds The number of seconds a switch report can arrive before the start of a 5- minute period, or the number of seconds into the 5-minute period
Warning
Corrective action This message is for your information only. To correct the problem, recreate the report configuration file with the default range values as follows: su root cd /usra/tdms/trans5min echo 20 240 > rpt_times.def chmod 664 rpt_times.def exit The next time the FEP application is restarted, the trans5min process will pick up the new report time values and you should not see this error.
...... 190-406-737 Alcatel-Lucent — Internal C-349 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 045
Message ID TRN 045 Ran out of buffer space to store the Trunk Group Controls Audit for entity entity. Audit response truncated to bytes bytes
Description There are too many controls on this GTD-5 switch, and the resulting Trunk Group Controls Audit is too large.
Parameters
entity FEP entity number of the GTD-5 switch whose Trunk Group Controls Audit failed
bytes Number of bytes in the final message sent to NTM
Minor
Corrective action The maximum number of controls supported by this audit is 500. If there are more than 500 applied to the switch, ask the NTM administrator to remove controls until the number is below 500. If there are 500 or fewer controls applied to the switch and you still see this error, contact FEP Customer Support.
...... C-350 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 046
Message ID TRN 046 Using the report times in the configuration file. The report processing times are: seconds seconds before the five minute interval and seconds seconds into the five minute interval
Description This message occurs during the initialization of the 5-minute translator. This normally appears after startfep has been run. The translator is printing the 5-minute report processing interval.
Parameters
seconds The number of seconds a switch report can arrive before the start of a 5- minute period, or the number of seconds into the 5-minute period
Status
Corrective action This message is for your information only. No action is required.
References “startfep” (p. A-46)
...... 190-406-737 Alcatel-Lucent — Internal C-351 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 047
Message ID TRN 047 Could not read the EDCS message queue. Five minute translator terminating
Description The initialization of the 5-minute translator, trans5min process, failed and reports cannot be processed, so the trans5min process is terminating.
Critical
Corrective action Follow these steps:
......
1 Restart the FEP application, using the stopfep command followed by the startfep command.
......
2 If this does not correct the problem, contact FEP Customer Support.
...... E ND OF STEPS ......
References “startfep” (p. A-46) “stopfep” (p. A-47)
...... C-352 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 048
Message ID
TRN 048 A late/incomplete five minute report received for entity entity
Description When the 5-minute processing interval ended, the 5-minute translator had received part of the switch report for the specified GTD-5 entity. This message indicates the entity's time may need to be synchronized with the FEP time, there may be a problem with the network between the switch and the FEP, or there may be a problem with the switch itself.
Parameters
entity FEP entity number of the GTD-5 switch that sent a partial report
Warning
Corrective action Follow these steps:
......
1 Contact switch personnel to verify that the switch's clock is in sync with the FEP's clock.
......
2 If the clocks are not in sync, reset the switch's time to match the FEP's time.
......
3 If they are in sync, ask switch personnel to verify that the switch is outputting a valid 5- minute report. Assuming the switch is sending a valid report on time, use the tlentity command on the FEP to verify that the FEP is receiving the report on time.
......
4 If the FEP does not receive the report on time, then there must be a problem with the network between the switch and the FEP that is delaying transmission of the report to the FEP.
...... E ND OF STEPS ......
...... 190-406-737 Alcatel-Lucent — Internal C-353 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... References “tlentity” (p. A-48)
...... C-354 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... TRN 049
Message ID
TRN 049 Five minute data for entity entity arrived too early or too late to be processed
Description The 5-minute translator received a report outside the valid processing time for the specified GTD-5 entity.
Parameters
entity FEP entity number of the GTD-5 switch whose report was late
Critical
Corrective action Follow these steps:
......
1 Contact switch personnel to verify that the switch's clock is in sync with the FEP's clock.
......
2 If the clocks are not in sync, reset the switch's time to match the FEP's time.
......
3 If they are in sync, ask switch personnel to verify that the switch is outputting a valid 5- minute report. Assuming the switch is sending a valid report on time, use the tlentity command on the FEP to verify that the FEP is receiving the report on time.
......
4 If the FEP does not receive the report on time, then there must be a problem with the network between the switch and the FEP that is delaying transmission of the report to the FEP.
...... E ND OF STEPS ......
References “tlentity” (p. A-48)
...... 190-406-737 Alcatel-Lucent — Internal C-355 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 050
Message ID
TRN 050 Five minute data for entity entity_id is missing packet(s) packet
Description The FEP has determined that the switch did not send all the 5-minute data packets. Data is missing,
Parameters
entity_id FEP entity number of the switch that is missing one or more data packets
packet List of 5-minute data packets that are missing
Major
Corrective action Follow these steps:
......
1 Verify the switch generic is correct.
......
2 If the problem persists, report the problem to the GTD-5 switch vendor or report the problem to FEP Customer Support.
...... E ND OF STEPS ......
...... C-356 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
Glossary
ABCDEFGHI LMNORSTW
......
A
Activate To make an office active for data collection. Alarm Visible report of a trouble condition in the network. Alarms usually require immediate attention from network personnel. ASCII
American Standard Code for Information Interchange A 7-bit code for providing as many as 128 different characters. An eighth bit can be added as a parity check for error detection purposes. Audit An integrity check through which NTM corrects differences between its own database and office databases.
......
B
Backing Up The process of copying data onto a separate medium for the purpose of data retention. BDR Backup and Disaster Recovery BPS Bits Per Second
......
C
Client A client uses the resources of another device (computer) or application. Client is another term for a PC on a local area network. CLLI Common Language Location Identifier
...... 190-406-737 Alcatel-Lucent — Internal G-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Code A numbering system for telephone addresses, for example, 614-555-1234 (NPA-NXX-XXX). Connection An attempt for a circuit that succeeds in obtaining a circuit. Also called a seizure. Control Data Data that describes the actual controls in place for the network. CPM-HS
Computer Port Module-High Speed An interface board in the Datakit II VCS that connects a fiber optic cable from the DECxpress Gateway 100 (DXG 100) software to the Datakit II VCS. Crash Dump The output from the hardware registers, the hardware stack, and the CPU.
......
D
Database A collection of data organized for rapid search and retrieval by a computer. DCC Data Collection Concentrator DCE Distributed Computing Environment Deactivate To make an office inactive for data collection. Destination A specified area or country in which the called subscriber is located. A destination is identified by its destination code (the digits used for routing the call). Discrete An on/off indicator that notifies network managers that: • Changes have been made to the status of the office • Significant events have taken place within the office NTM polls the offices for discretes at regular intervals.
......
E
EADAS
Engineering and Administration Data Acquisition System A system in which traffic data are measured at switching systems by electronic devices, transmitted to a centrally located minicomputer, and recorded on magnetic tape in a format that is suitable for computer processing and analysis. Performs data collection in NTM for certain switch types.
...... G-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... Error Log The error log is a file that contains the error messages being generated by NTM. Error Messages System responses resulting from software-detected errors, changes in the system status, or non- executable commands. Error Number Number associated with error codes that help identify specific messages. ESS Electronic Switching System
......
F
FEP
Front-End Processor An application that acts as a DCC. Available with purchase of Feature 214, “FEP Release 4” or Feature 257, “FEP Release 5”.
......
G
Generic The version released to provide specific services, features, or functions. GETS Government Emergency Telecommunications Service Group A type of equipment that a Datakit II VCS may contact, signal or communicate with. In NTM, there are three group designations. Each is identified by the NTM equipment to which the group connects. The three group designations are: receive groups, originate groups, and 2-way groups.
......
H
h partition (hog partition) The partition or space on a disk that occupies whatever space is left over after other partitions or spaces are allocated for other uses on the disk. Hardware The physical components of a computer system. Header Area at the top of window that shows the name of the display. Host Computer Computer (machine) used to run the NTM software.
...... 190-406-737 Alcatel-Lucent — Internal G-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ......
I
IP In Progress Issue This refers to the office generic issue number.
......
L
Link Status The connection status of an office. LSSGR LATA (Local Access and Transport Area) Switching System Generic Requirements
......
M
Menu Mouse Button Mouse button used to display context-sensitive menus. (Usually the right mouse button.) Click the menu mouse button once to display the menu, then use the Select Mouse Button (usually the left mouse button) to select an item (or subitem) from the menu.
......
N
8920 Network Traffic Management software A system that provides near-real time surveillance of the network elements connected to it for the purpose of managing network congestion. Network Data Traffic data that is collected from the network elements on a periodic basis, typically 5 or 15 minutes. Network Management A set of procedures, equipment, and operations designed to keep a traffic network (a telephone network, for example) operating near maximum efficiency when unusual loads or equipment failures would otherwise force the network into a congested, inefficient state. NTM Network Traffic Management NTM host The server on which the NTM is run.
...... G-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
......
O
Office The name of the local Datakit II VCS, switch, DCC, or FEP connected to your host computer.
......
R
Record Base A collection of ASCII files containing reference information about the network to be managed by the NTM.
......
S
Shared Memory A RAM-based data structure on the host that is used to store discrete, control, and exception data. Portion of memory accessible to multiple processes. Step An instruction to perform one or more specific actions. A series of steps make up a procedure. SVC
Switched Virtual Circuit A virtual circuit connection established across a network on an as-needed basis and lasting only for the duration of the transfer. Switch A computer system that channels telephone calls from one place to another and keeps track of each call that it transfers. Switch Name A code name that identifies an office. Syntax The format in which a command is entered, including the input command name, parameters, and action options. System Error The NTM GUI presents error messages in response to conditions such as improper permission, execution errors, etc. A system error is presented when an error occurs on the NTM host during the generation of a web page or during the processing of a request from a web page (except certain control related requests).
......
T
Terminal A general term referring to any device that provides input to or receives output from the system.
...... 190-406-737 Alcatel-Lucent — Internal G-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Translations Information the switch uses to convert incoming data on a call into an outgoing trunk location. The switch accesses various tables or “translators” stored in the system to choose the appropriate physical path (trunk group) over which to send the call. The end product of a translation is a physical location (or trunk) in the network. The process of updating and maintaining the translation tables in switching systems is referred to as writing or creating “recent change” orders. (fep, reportwriter, responses) Trunk A telephone communication path or channel between two points, one of them usually being a telephone company central office or switching center. Trunk Group A group of trunks with similar electrical characteristics that go between two geographical points. A trunk group performs the same function as a single trunk, except that on a trunk group multiple conversations can be carried. Trunk groups are used as traffic demands them.
......
W
Window A window is box-type graphic displayed when specific buttons, icons, function keys or hot keys are selected in a windows operating system environment. Each window contains various control attributes including a means to close the box, typically an “X” in the upper right corner. The window identifier is displayed in the task bar. The user opens and closes windows.
...... G-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
Index
...... AUD 014, C-20 BDR 018, C-42 5-minute data channel, 5-6 AUD 015, C-21 BDR 019, C-43 8mm tape, 3-42 AUD 016, C-22 BDR 020, C-44
...... audit data channel, 5-6 BDR 021, C-45
A activate a switch, 4-29 audit log, 3-19 BDR 022, C-46 activate entity command, A-3 ...... BDR administration Activating BDR on a host, activate switch command A-3 , B backup disaster recovery feature, 3-95, 3-96 Activating BDR on a host 3-95 5-5 , , Deactivating BDR on a host, 3-96 backup dynamic data command, 3-86 Adding a New Switch to the A-23 bworx login, 1-6, 3-4 AISwitch, 6-15 backup FEP data, 3-41 ...... aentity command, 4-29, A-3 backup, incremental, 3-43 anlink command, A-4 BaseWorX, 1-4 C cdrom drive unit, 1-5 application status for execution BaseWorX commands, 1-9 centity command, 4-25, 4-31, state and tracing status A-13 BDR — Backup and Disaster command, A-5 Recovery Commands, C-23 change entity command, A-20 appstat command, 3-30, A-5 BDR 001, C-24 change switch command, A-20 AUD, C-3, C-5 BDR 002, C-25 chentity command, A-20 AUD — Audit Trail Messages, BDR 003, C-26 CLLI, 3-1, 4-4 C-5 BDR 004, C-27 CMD, C-3, C-47 AUD 001, C-7 BDR 005, C-28 CMD — User Commands, C-47 AUD 002, C-8 BDR 006, C-29 CMD 017, C-48 AUD 003, C-9 BDR 007, C-30 CMD 019, C-49 AUD 004, C-10 BDR 008, C-31 CMD 020, C-50 AUD 005, C-11 BDR 009, C-32 CMD 021, C-51 AUD 006, C-12 BDR 010, C-33 CMD 022, C-52 AUD 007, C-13 BDR 011, C-34 CMD 023, C-53 AUD 008, C-14 BDR 012, C-35 CMD 024, C-54 AUD 009, C-15 BDR 013, C-36 CMD 025, C-55 AUD 010, C-16 BDR 014, C-38 cnlink command, A-21 AUD 011, C-17 BDR 015, C-39 complete installation, 2-4 AUD 012, C-18 BDR 016, C-40 Configuring the AI296 Smart AUD 013, C-19 Line Cards, 6-7 BDR 017, C-41
...... 190-406-737 Alcatel-Lucent — Internal IN-1 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... Configuring the AISwitch, 6-4 delentity command, 4-27, A-29 EDD 009, C-74 Configuring the Links for the delete a switch, 4-27 EDD 010, C-75 AI296 Smart Line Cards, 6-10 delete entity command, A-30 EDD 011, C-76 connect FEP and a switch, 4-5 delete NTMOS link command, EDD 012, C-77 control data channel, 5-6 A-31 EDD 013, C-78 Copying the AI Configuration delete switch command, A-30 EDD 014, C-79 onto the FEP, 6-31 Deleting a Switch from the EDD 015, C-80 CPM-HS board, 1-5, 2-3, B-2 AISwitch, 6-20 EDD 016, C-81 create a switch, 4-25 delnlink command, A-31 entity activate command, A-3 create entity command, A-16 directory restore, 3-68 entity change command, A-20 create NTMOS link command, discrete data channel, 5-6 entity create command, A-16 A-21 dkcu, 1-7 entity deactivate command, A-27 create switch command, A-16 dynamic data backup command, entity delete command, A-30 ...... A-23 entity status command A-43 dynamic data restore command, , D data channels, 5-6 A-26 entity test command, A-52 data interval status command , error log, 3-19 A-41 ...... Ethernet, 2-31 Datakit address of switch 4-7 C-3 , E EDCS, installation, 2-31 Datakit interface board, 1-5, 2-3 EDCS — GTD-5 Event Data ...... Datakit VCS commands, 1-9 Collection Subsystem, C-56 F FEP application software 3-28 Datakit VCS problems, 5-17 EDCS 001, C-57 , FEP application software status Datakit-FEP links, 5-17 EDCS 002, C-58 , 3-30 daylight savings time, 1-13 EDCS 003, C-59 FEP console, 1-5 DCC, data collector concentrator, EDCS 004, C-60 fep login 1-2 EDCS 005, C-61 , 1-6, 3-4 FEP software load command ddbkup_fep, A-22 EDCS 021, C-62 , A-36 ddrstr_fep, A-24 EDCS 022, C-63 FEP software subsystems, C-3 deactivate a switch, 4-30 EDD, C-3, C-64 FEP start command, A-46 deactivate entity command, A-27 EDD — GTD-5 Data FEP stop command, A-47 deactivate FEP-NTMOS link, Distributor, C-64 FEP System Responses 5-13 EDD 001, C-65 , C-3 FEP system responses deactivate NTMOS link EDD 002, C-66 , C-1 FEP, what is a 1-2 command, A-28 EDD 003, C-67 , FEP-Datakit links deactivate switch command, EDD 004, C-68 , 5-17 A-27 FEP-NTMOS link testing 5-15 EDD 005, C-70 , Deactivating BDR on a host, 3-86 file restore 3-68 EDD 006, C-71 , deaentity command, 4-30, A-27 fullbkup_fep command 3-46 EDD 007, C-72 , , deanlink command, A-28 A-32, A-34 EDD 008, C-73 default logins, 1-6
...... IN-2 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... IPNDC 134, C-108 LM — BaseWorX Log Manager, G generic of switch, 4-7 IPNDC 135, C-110 C-148 GETS, 3-98 IPNDC 139, C-111 LM 001, C-149 Government Emergency IPNDC 140, C-113 load FEP software command, Telecommunications Service A-36 IPNDC 144, C-114 (GETS), 3-98 load_fep command, A-36 IPNDC 145, C-116 ...... log files, 3-19 IPNDC 146, C-118 logCat command, 3-21, A-37 H hardware, 2-3 IPNDC 149, C-120 login via dkcu, 1-7 ...... IPNDC 150, C-122 login, delete a, 3-12 I incremental backup, 3-43 IPNDC 152, C-124 login, remote, 1-6 Initial Connection to the IPNDC 153, C-125 AISwitch 180, 6-2 IPNDC 154, C-127 ...... Initial Connection to the IPNDC 155, C-128 M manual pages, 1-9 AISwitch 180 , 6-2 IPNDC 156, C-129 monitor audit log, 3-23, 3-29 Installing an Update 3-35 , IPNDC 157, C-130 Monitor the AISwitch for Trouble Introduction 6-2 Shooting Purposes 6-29 , IPNDC 158, C-131 , IPNDC — Internet Protocol IPNDC 159, C-132 ...... Network Data Collector, C-82 IPNDC 161, C-133 N NDC, C-4, C-82, C-148, C-150 IPNDC 101, C-85 IPNDC 162, C-134 NDC — Network Data Collector, IPNDC 111, C-86 IPNDC 165, C-135 C-150 IPNDC 114, C-87 IPNDC 166, C-136 NDC 101, C-153 IPNDC 115, C-88 IPNDC 167, C-137 NDC 111, C-154 IPNDC 116, C-89 IPNDC 168, C-139 NDC 114, C-155 IPNDC 117, C-90 IPNDC 169, C-140 NDC 115, C-156 IPNDC 118, C-92 IPNDC 170, C-141 NDC 116, C-157 IPNDC 119, C-93 IPNDC 171, C-142 NDC 117, C-158 IPNDC 120, C-94 IPNDC 172, C-144 NDC 118, C-160 IPNDC 121, C-95 IPNDC 173, C-145 NDC 119, C-161 IPNDC 122, C-96 IPNDC 174, C-147 NDC 120, C-162 IPNDC 123, C-97 NDC 121, C-163 IPNDC 125, C-98 ...... NDC 122, C-164 IPNDC 126, C-99 K kshell, 1-4 NDC 123, C-165 IPNDC 127, C-100 ...... NDC 125, C-166 IPNDC 128, C-101 L link activate, FEP-NTMOS, 5-11 NDC 126, C-167 IPNDC 129, C-102 link status, FEP-NTMOS, 5-5 NDC 127, C-168 IPNDC 130, C-103 link test, FEP-NTMOS, 5-15 NDC 128, C-169 IPNDC 132, C-104 Link, FEP-Datakit, 5-17 NDC 129, C-170 IPNDC 133, C-106
...... 190-406-737 Alcatel-Lucent — Internal IN-3 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... NDC 130, C-171 NMT 007, C-225 NMT 061, C-273 NDC 132, C-172 NMT 008, C-226 NMT 062, C-274 NDC 133, C-174 NMT 009, C-227 NTMOS link create command, NDC 134, C-176 NMT 010, C-228 A-21 NDC 135, C-178 NMT 013, C-230 NTMOS link deactivate command, A-28 NDC 139, C-179 NMT 014, C-231 NTMOS link delete command, NDC 140 NMT 015 , C-181 , C-234 A-31 NDC 144 C-182 NMT 016 C-235 , , NTMOS link status command, NDC 145, C-184 NMT 018, C-236 A-45 NDC 146, C-186 NMT 019, C-238 NTMOS link test command, NDC 149, C-188 NMT 022, C-239 A-53
NDC 150, C-190 NMT 023, C-240 ......
NDC 152, C-192 NMT 024, C-242 O operating system, 1-4 NDC 153, C-193 NMT 025, C-244 optical fiber cable, 1-5, 2-3 NDC 154, C-195 NMT 026, C-246 ...... NDC 155, C-196 NMT 027, C-247 P Port–to–Link Mapping (SVC), NDC 156, C-197 NMT 029, C-248 6-22 NDC 157, C-198 NMT 030, C-249 processor, 1-5, 2-3 NDC 158, C-200 NMT 037, C-251 prtsint command, 4-14, A-41 NDC 159, C-202 NMT 038, C-252 ...... NDC 161, C-203 NMT 041, C-253 NDC 162, C-204 NMT 042, C-254 R read audit and error log command, A-37 NDC 165, C-205 NMT 045, C-255 Reboot, 1-12 NDC 166, C-206 NMT 046, C-256 Recovering the AI Configuration NDC 167, C-207 NMT 047, C-258 File from the FEP, 6-33 NDC 168, C-209 NMT 048, C-259 remote login, 1-6 NDC 169, C-210 NMT 049, C-260 restore directory or file, 3-68 NDC 170, C-211 NMT 050, C-261 restore dynamic data command, NDC 171, C-212 NMT 051, C-262 A-26 NDC 172, C-214 NMT 052, C-263 restore FEP data, 3-56 NDC 173, C-215 NMT 054, C-264 root login, 1-6, 3-4 NDC 174, C-217 NMT 055, C-265 rsentity command, 4-7, 4-12, NMT, C-4, C-218 NMT 056, C-266 4-16, 4-19, 4-25, 4-27, 4-29, 4-31, A-42 NMT — Network Management, NMT 057, C-268 rsnlink command, A-44 C-218 NMT 058, C-270 RT, C-4, C-275 NMT 001, C-221 NMT 059, C-271 RT — BaseWorX Rapid Transit, NMT 004, C-222 NMT 060, C-272 C-275 NMT 006, C-223 ...... IN-4 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010
...... RT 004, C-276 switch status check, 4-7 test entity command, A-52 RT 007, C-277 switch status command, A-43 test FEP-NTMOS link, 5-15
...... switch test command, A-52 test NTMOS link command, switch time offset, 4-7 A-53 S shell, 1-4 switch, activate, 4-29 test switch command, A-52 SLM, C-4, C-278 switch, change Datakit VCS throttle error and audit messages, SLM — Synchronous Line address, 4-31 3-24 Module, C-278 switch, change generic, 4-31 time offset of switch, 4-7 SLM 005, C-279 switch, change time zone offset, time synchronization, 4-11 SLM board, B-14 4-31 time zone offset, change, 4-31 software, 2-3 switch, create a new one, 4-25 Tips on Navigating through the Software Subsystem Codes, C-3 switch, deactivate, 4-30 AISwitch Menu, 6-3 software subsystems, C-3 switch, delete, 4-27 tlentity command, A-48 start FEP command, A-46 switches, 4-2 tlentity command with 5ESS and startfep command, A-46 DMS switches, 4-19 switch-FEP link test, 5ESS and status of data interval command, DMS switches, 4-19 tlentity command, with GTD-5 A-41 switches, 4-16 switch-FEP link test, GTD-5, status of entity command, A-43 4-16 tnlink command, A-53 status of NTMOS link command, SYM, C-4, C-282 traffic data files, path to, 4-15 A-45 SYM — FEP System, C-282 TRN, C-4, C-293 status of switch command, A-43 SYM 001, C-283 TRN — GTD-5 Translators, stop FEP command, A-47 C-293 SYM 002, C-284 stopfep command, A-47 TRN 001, C-295 SYM 003, C-285 subsystems, software, C-3 TRN 002, C-296 SYM 004, C-286 support1 login, 3-4 TRN 003, C-298 SYM 006, C-287 Switch TRN 004, C-300 SYM 007, C-288 conventions used, xxvi TRN 005, C-302 SYM 011, C-289 switch activate command, A-3 TRN 006, C-303 SYM 012, C-290 switch change command, A-20 TRN 007, C-304 SYM 014, C-291 switch create command, A-16 TRN 008, C-305 SYM 015, C-292 switch data collection, checking, TRN 009, C-306 4-14 synchronization, at switch, FEP and NTMOS, 4-11 TRN 010, C-308 switch Datakit address, 4-7 system console, 1-5, 2-3 TRN 011, C-309 switch deactivate command, TRN 012, C-310 A-27 system responses, C-1 TRN 013, C-311 switch delete command, A-30 ...... TRN 014, C-312 switch generic, 4-7, 4-9 T tape drive unit, 1-5, 2-3 TRN 015, C-313 switch name, 3-1, 4-4 TCP/IP, 2-31 TRN 016, C-314 switch number, 3-1, 4-4 terminal, 1-5, 2-3 TRN 017, C-315
...... 190-406-737 Alcatel-Lucent — Internal IN-5 Issue 1.1 September 2010 Proprietary — Use pursuant to Company instruction ...... TRN 018, C-317 TRN 019, C-318 TRN 020, C-319 TRN 021, C-320 TRN 022, C-321 TRN 023, C-323 TRN 024, C-324 TRN 025, C-326 TRN 026, C-328 TRN 027, C-329 TRN 028, C-330 TRN 029, C-331 TRN 030, C-333 TRN 031, C-334 TRN 032, C-335 TRN 033, C-336 TRN 034, C-338 TRN 035, C-339 TRN 036, C-341 TRN 037, C-342 TRN 038, C-343 TRN 039, C-344 TRN 040, C-345 TRN 041, C-346 TRN 042, C-347 TRN 044, C-349 TRN 045, C-350 TRN 046, C-351 TRN 047, C-352 TRN 048, C-353 TRN 049, C-355 TRN 050, C-356 Trouble Shooting, 6-29 TY-12 board, B-2, B-7
......
U unthrottle, 3-25
...... IN-6 Alcatel-Lucent — Internal 190-406-737 Proprietary — Use pursuant to Company instruction Issue 1.1 September 2010