Label: tac inet - Building Automation Knowledge Base

Issue DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 'Cannot open backup device ' C:\Users\Administrator\Desktop\20120919'. Operating System Error 5( Access is denied). [Microsoft][ODBC SQL Server Driver] [SQL Server] BACKUP DATABASE is terminating abnormally' Product Line TAC INET Environment I/NET loaded on Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 Cause The cause is insufficient rights to perform this function based upon a local policy of not allowing users to see the 'C' drive. Resolution Although when Using a Network Administrator account or Administrator for the local machine, you cannot open backup to either the local machine 'C' drive or a network share, you should be able to backup to a thumb drive.  Go to local disk properties - security tab Users do not have permissions to modify or write to the 'C' drive. Windows UAC may over ride the administrator permissions. Check your permissions and make sure you have rights to a folder and perform the backup. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.  

Issue The order of installation is dependent upon the SQL versions installed with Vista and I/NET. I/NET DBCreate does not open after installation is complete.   DBCreate application is not shown even though under Task Manager processes the application is active. Product Line TAC INET, TAC Vista Environment SQL MSDE Express Vista and I/NET Installed on the same PC Cause Vista and I/NET both use SQL databases for purposes of event and trend logging.  They must be installed in the correct order to coexist within the shared SQL installation. It can be confusing to know which software should be installed first on a certain installation because it is completely dependent upon both the I/NET versions and Vista versions.  Later versions are compliant with SQL 2005 Express while earlier versions must use SQL MSDE. Resolution If a previous installation has failed, it is best to start "fresh" before attempting a re-install. Removal of Vista instructions located here: How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Removal of I/NET instructions located here: Procedure for uninstalling I/NET Seven on a stand-alone host Empty Recycle Bin to remove evidence of previous installations.    Use the following guidelines to determine in which order to install I/NET and Vista: If the I/NET version is prior to 2.2.1, then I/NET must be installed before Vista, regardless of the Vista version. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 4.3.0 through 5.0.0, and the I/NET version is 2.2.1 or higher, then Vista must be installed before I/NET. These versions of Vista use TAC Config and SQL MSDE . When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 5.0.1 through to 5.1.6, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET. These versions of Vista use SQL 2005 Express.  I/NET versions 2.2.1 and higher have an option to install SQL 2005 Express. When prompted during the I/NET installation, allow a new SQL instance on the existing SQL 2005 Express that was installed with Vista.   If the Vista version is 5.1.7 and above, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET The default installation of this version of Vista uses SQL 2008 R2 Express.  When prompted during the I/NET installation, select Default Instance of either MSDE or SQL 2005. (Note that if installing on Windows7 operating system, MSDE  option is grayed out and cannot be selected, as it is not supported on Windows7 )..   If the Vista version is 5.1.7, and the I/NET version is 2.4.0 or higher, you can choose either one to be installed first. If Vista is installed first, by default Vista will install SQL 2008 R2 Express SP1. But I/NET 2.4x fails to recognize the instance installed by Vista, while also fails to create a default instance. So after installed Vista, manually create a default instance for I/NET, and then install I/NET. Refer to Item 1 in How to Troubleshoot on DBCreate on how to create it; If I/NET is installed first, you can choose Custom Installation for SQL during the installation of Vista. You need to manually enter the SQL instance name, SQL username and password when installing I/NET SQL. If you don't know the instance name, there is a quicker way to identify it: Open DBCreate of I/NET, and you can see the SQL server name for I/NET. Just copy and paste it here. Then you can finish the installation. For Vista IV installation, the correct procedure can be found here: TAC Vista IV and Peripheral Software Installation Outline

Issue Ports are required to be open for I/NET to communicate Need to know the UDP TCP/IP port settings for I/NET. File Equalization failure or NPR devices not coming online Some links (NPRs) are showing offline and can not be connected too, while others work fine. Product Line TAC INET Environment I/NET NPR NPR-527 Cause A Firewall may be blocking ports required for File Equalization and I/NET communication to occur. Resolution You will need to work with the IT department to verify these settings. I/NET communications occurs through port 50069. When using File Equalization you will also need to ensure that ports 1433 and 1434 are open as these are used by SQL. Integral DVR communicates to I/NET on port 18772 For systems with 527 devices or other Xenta servers, please review Ports used by TAC Vista System.

Issue Where can I find datasheets, install guides and other documentation on the HID SmartID, iClass, HID Proximity and Indala Proximity cards and readers? Product Line Andover Continuum, Field Devices, TAC INET Environment Electronic Access Control cards and readers for Continuum and I/Net products. Cause Additional product information from HID may be required that is not available on Schneider Electric's own websites. Resolution Schneider Electric supply a subset of the full HID range of cards and readers and these are detailed in the Electronic Access Control Catalogue or see How to determine the part number for the card format required for part number information. For HID product information this can be directly downloaded from the HID Global website. This contains  datasheets, installation guides, application notes, feature lists, brochures and other documentation. HID also have a "Knowledge Center" website that allows you to search for product information and help: HID Knowledge Base. Information on the specific ranges can be obtained from the following links: SmartID: SmartID Cards iClass: iClass Readers iClass SE Readers iClass Cards HID Prox: HID Proximity Readers HID Proximity Cards Indala Prox: Indala Proximity Readers Indala Proximity Cards

Issue Lost the password to login to the different media I/NET, SQL, SAV Environment I/NET site Cause Lost Password Resolution I/NET login: Please send the database with version number and SQL version used to ProductSupport.BMS@schneider-electric.com. SQL login: Please see Loading I/NET on a PC that has full SQL and the Password is not known and Changing the MSDE SQL Server Sys Admin account password is not supported by the I/NET Seven DbCreate Utility. DCU login: Please see Recover an I/NET Controller's DCU Password.

Issue Using I/NET trends in StruxureWare Building Operation Product Line EcoStruxure Building Operation, TAC INET Environment I/NET StruxureWare Building Operation 1.3 Cause Ideally trends should reside in the controller rather than at the sever level as this prevents sample data loss due to communication errors. Resolution Before you begin, ensure that all I/NET trends are set up correctly and trend data is visible. For assistance with this see Setting Up I/NET Seven Trends. Ensure that messaging is working so that SmartStruxure receives I/NET messages, and ensure that all controls have points to be trended, are already added to the I/NET Interface. NOTE: For the Enterprise Server level integration, the I/NET Trend Object must be configured as a Seven Trend. For the Automation Server level integration, this is not required, therefore skip to step 3. In I/NET, Select Trends>Data Inquiry/Edit View the trend you wish to see in SmartStruxure and verify that it has data. Open StruxureWare Workstation Refresh the system tree and upload any I/NET controllers that do not show a green dot. Right click on the I/NET Interface and select New>Value When the "Create Object" Window appears, name the value and click "Create" The Value will appear in the I/NET Interface Right Click on the newly created Value and select "Properties" Locate the "Point to Trend" Field Click on the "..." and select the point object you wish to trend Click the select button Verify that the Point to Trend field is correct and Click OK Wait enough time for several samples to populate. Right click on the Value object in the I/NET interface and select View>Trend log lists>New Trend log list The New Trend log List should open and values should visible. The Trend Value object under the I/NET interface will now function the same as a trend object in StruxureWare. If you wish for the I/NET trend to show up as part of an Energy Report, you will need to Ensure that the Extended Trend Log is referenced in a Meter's "Meter Trend Log" property NOTE: For the Enterprise Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven Trend to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must have a current save file The Controller with the I/NET point being trended must be online The I/NET workstation located on the Enterprise Server must be masked to receive data from the trend log on the controller to the Seven Trends Definition For the Automation Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven trend extension to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must be online The I/NET trend object and point object must have some level of masking so that the data will leave the controller.

Issue IDWorks 6.x (on a Remote Client) does not connect to the SQL with Windows 7 64 Bit. Product Line TAC INET Environment Datacard IDWorks 6.x Windows 7 64-bit I/NET 2.43 and above Cause You have to manually install a 32 Bit ODBC connection for this to work correctly. Resolution To resolve this issue, start the EXE file located at: C:\Windows\SYSWOW64\odbcad32.Exe. NOTE: This is NOT the ODBC that is in the Control Panel on the PC. Once you start the EXE file, set this new ODBC Connection up by following the steps that are listed in Setting up ID Works on a Remote Client PC.

Issue There appears to be a low battery on the control board. How can the NiCAD Battery be tested on the controller to see if it needs to be changed? Product Line TAC INET Environment I/NET Seven Cause Possible low battery on control board. Resolution There are some checks you can make regarding the battery condition. The battery has a design life of 7 years and sometimes lasts much longer. With power applied to a controller for at least 72 hours, take a DMM and measure the DC voltage across the battery. It should be in the neighborhood of 4.2-4.3 vDC. Remove power from the controller board and take the same measurement again. The beginning voltage should still be between 4.1-4.3 vDC and should start slowly tapering off (a tenth of a volt over a period of minutes would be normal). When the battery voltage reaches 3.6 vDC this is the threshold at which the battery can sustain the RAM memory. Any voltage below this value will subject the RAM memory to loss of data (+ - a tenth or two). If the initial voltage with power applied to the controller is less than 4.0 vDC after 72 hours, the battery may need replacing. If the battery voltage drops rapidly after power is removed from the controller, the battery needs replacing. If the controller memory inexplicably gets lost (not counting power surges, brownouts, etc.) and a station restore is needed, the battery may need replacing. Normally the above-mentioned tests will show that the battery has lost its storage capacity. The TAC part number for the White NiCAD battery that is on most of the I/Net Controllers is 01-2100-545. These batteries can no longer be ordered through the Customer Care department. For further battery info please reference Replacement I/NET Controller NICAD Battery info.  

Issue After successfully logged into Xenta Server web pages, java loading icon will be displayed as shown below. However, after a while it will automatically log the user out as shown below. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers 5.1.6 (Xenta 511, Xenta 515, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) Java 1.6 update 29 Note: This behavior may happen on other Xenta Server versions with different Java versions. Please refer to the Cause section for the reason. Cause Vista may not support the newest Java versions. For Vista 5.1.6, the recommended Java version is Java 1.6 update 20. Please refer to Recommended Java version for TAC Vista 5 for recommended Java version details. Resolution Go to Start > Settings > Control Panel > Add or Remove Programs. Find Java application (in this example is Java(TM) 6 Update 29), and select “Remove”. Reload the Xenta Server webpage, will find the Java icon will not be displayed this time. Instead, “Download Java” request link will be displayed. Click on the link and download the supported version of Java. The issue should be solved after the recommended version of Java is installed.

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue Unable to connect Remote Client to Standalone Server ASTDIR error when attempting to configure I/NET is sometimes caused by not being logged in as an administrator. Product Line TAC INET Environment I/NET Configuration Cause To configure a remote client open port 50069 between the 2 workstations, use an admin level I/NET password to initiate communication and be logged in as an administrator on the local machine. Resolution Log in to Windows as an administrator level user Make sure that I/O server is not running Open I/NET Configuration Modify the active profile or create a new one Set TCP/IP settings as well as required reference hosts For Workstation type, select Remote Client or Remote Client (w/IO) When the authentication screen comes up enter an I/NET operator name that has full access. Enter the Host name of the standalone machine functioning as the server. (you may also enter the IP address instead) Leave Authentication Type as default. Press OK Press OK and start I/NET For More information see Remote Client Configuration Issues I/Net 2.31 and prior and Remote Client with I/O in the Workstation Type of the I/O Server 2.4 and later.

Issue When upgrading to a different revision of software in I/NET Seven, there are a few steps that are highly recommended to ensure that the database doesn't get corrupted during the upgrade. Product Line TAC INET Environment I/NET Seven Cause Performing an upgrade of I/NET Seven software. Resolution Close I/NET Start DB Create and select the Verify Database option. Verify that the database has 0 differences. Select Upgrade Database to force an upgrade Select the Verify Database option again. Now back up the database to the local drive or media and proceed with the upgrade. Once completed, Select Restore database and proceed to where the back up is and restore the database to the system.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Links not working after TGML conversion Converting I/NET graphics to TGML using the "Create Source Tree" option Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.44 Cause I/NET stored graphics on the hard disk and allowed for complex folder structures to be used in organizing those graphics. When these graphics are converted to TGML, this structure may need to be preserved in order to prevent duplicate graphic names. Resolution For this example I have created a site with 3 buildings containing Identical I/NET graphics. Each Building has a summary page and a VAV page. All pages link back to a home page. In I/NET select System>Export Graphics to TGML(you can also right click on the I/NET interface in StruxureWare Workstation) Set your Source and Destination Path and click All Yes.   When you set your destination path, it must point to a folder that already exists in Windows.  The Export INET Graphics to TGML tool does not create this directory Notice that the default setting is to "Use destination path" If we click convert with that option, we will get only 3 graphics.  The graphics from other folders with the same name are over-written. Select the "Create Source Tree" option, ensure the correct graphics are scheduled to convert and click convert. Notice that In Windows Explorer a new folder structure is created that is identical to the original folder structure. Open StruxureWare Workstation. Create a folder system that matches what is on the Hard disk. Drag and drop the TGML files from Windows explorer to the corresponding folders in StruxureWare Workstation. Test you graphic links to ensure everything is functional. Note: Once the graphics are imported, StruxureWare will allow you to move them freely without breaking the binding between pages. There is another way to import all the I/NET graphic folders in one time. Refer to Import all converted I/NET graphic folders into EcoStruxure at one time.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue After an uninstall of I/NET Seven and MS SQL, you might verify in the Windows Registry that all the items were deleted. Having issues installing I/NET what can I look for. Product Line TAC INET Environment I/NET all 2.4X versions Cause In some cases when re-installing, installing I/NET after a failed attempt or upgrading I/NET you may want to start fresh. After an uninstall of INET Seven and MSDE if items remain in the registry they will cause issues with future installations. Resolution Go to the bottom Task Bar and choose the “Start” button. Select the “Run” option and enter “Regedit” Once in the Windows registry go to “HKEY_CURRENT_USER, if the “CSI” entry is present delete this entry While still in the HKEY_CURRENT_USER look in the Microsoft File Folder for any “SQL” entries and remove them if they are present. Minimize the HKEY_CURRENT_USER folder and open up the HKEY_LOCAL_MACHINE File Folder, if the “CSI” entry is present delete this entry. While still in the HKEY_LOCAL_MACHINE, go to the Microsoft File Folder and look for any “SQL” entries. If you find any delete then from this file folder. Caution:  Before editing the SQL registry items you should ensure that no other software using SQL is still installed - all software that is installed should be uninstalled prior to modifying any registry entries. See also, MSDE and Windows 7.

Issue When trying to download a 5/7/9xx in XBuilder you get "Error code 401 - Unauthorized". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause Password in XBuilder project does not match the password in the Xenta device. Resolution Select the 5/7/9xx in the Network panel The password is in the right hand panel of XBuilder under the TCP/IP Settings section. Change this to match the password in the 5/7/9xx. If the password is not known then refer to Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost.

Issue Original company sold to new company Site License needs to be updated for install/upgrade.  Computer failure and no software/license information is available. Downloaded software and during install it requests a CD Key Product Line Andover Continuum, TAC INET Environment Site Licensing for install/upgrade Cause Changes in company or computer replacement/upgrade or downloaded software and it is requesting a CD Key Resolution I/NET: 1. Original company sold to new company and Site License needs to be updated for install/upgrade: for company naming changes, contact your sales representative who in turn will contact Product Support and request a transfer of information or upgrade/purchase. Once the information has been cross referenced for validity, either a new or replacement CD Key can be generated. Please include the following when requesting transfer: User Name Site Name Site Address Serial Number Version number Build number CD Key 2. Computer failure and no software/license information is available: Send email to Product Support with the following information: User Name Site Name Site Address Serial Number version number Build number CD Key 3. CD Key for licenses on purchase of software can be ordered by contacting Contact Customer Care. Link is available on the Contact tab of this web page. Customer Care offers pricing, order placement, changes, expedites, and order status. Check Licensing of I/NET with SITE and SEAT License with License Key for issues with CD Key and Licensing information. Continuum: since Continuum only has physical security key licensing, the license is owned by the holder of the key. If you hold the key, you own the license. There is no need to contact PSS for moves, changes, restructuring. If the security key's are lost or stolen, you will need to purchase new keys to replace them. Continuum Software Licensing is available with Release 2.0. 

Issue When restoring database, an error will show up, saying that version is incompatible with this server. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause This is usually caused by restoring new SQL database to older version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Microsoft doesn't like to do this. Resolution There is build number matrix for each SQL server version:     RTM (Gold, no SP) SP1 SP2 SP3 SP4 SQL Server 2012 11.00.2100.60 11.00.3000       SQL Server 2008 R2 10.50.1600.1 10.50.2500 10.50.4000     SQL Server 2008 10.00.1600.22 10.00.2531 10.00.4000 10.00.5500   SQL Server 2005 9.00.1399.06 9.00.2047 9.00.3042 9.00.4035 9.00.5000 So check the build number in the error message and download the corresponding version of SQL to restore and be used for I/NET.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Error when installing SQL 2005 Express on a machine that had previously had MSDE installed Product Line TAC INET Environment SQL 2005 Express Cause  MSXML 6.0 SP2 is causing the installation to fail Resolution Download the program linked below Remove SQL 2005 from the system Run the application to remove MSXML 6.0 from the system Re-install SQL2005 Express MicrosoftFixit50568.msi.zip For alternative solutions see SQL Express install fails on MSXML 6 and Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.).

Issue Where to begin troubleshooting Ethernet (TCP/IP) communication problems with a NPR Product Line TAC INET Environment I/NET NetPlus Router (NPR) Model Series 2000 Cause Possible Causes: Ethernet Communication is down Ethernet Port is closed Device is configured incorrectly Device failure Resolution Gather detailed information about exactly what is happening Ethernet Communication is down Using the command prompt ping the devices IP and trace its route. "ping xxx.xxx.xxx.xxx" and "tracert xxx.xxx.xxx.xxx" Watch to see if the Domain server prints out the correct Host name. If the device is shows as offline there may be an error with Firewall settings or Ethernet communication at the Host Workstation Disconnect the Ethernet cable from the Device and plug it into a laptop. See if you are on the network. Ethernet Port Is closed If the above process shows that Ethernet communication between the Workstation and Router is valid, you may have port closed. Use a crossover cable to connect a laptop to the device and see if you can connect to a controller ON THAT LINK in I/NET. Look for live values in Controller Summary. If you are able to do this, and you are able to show that Ethernet communication between the 2 devices is working then you most likely have a firewall that is block the UDP port 50069 Contact the building IT department to assist in rectifying this problem. Device is configured incorrectly If, in the above process, you were unable to connect to I/NET while direct connected to the Router via an Ethernet crossover cable, the device may be configured incorrectly Open the active I/NET configuration Profile Ensure that TCP/IP is enabled Add the Router’s IP address to the Reference Host Table Restart the I/O server Check communication Alternatively you can connect to the router via I/NET Direct Connect configuration profile. Refer to Troubleshoot an NPR problem with Windows Telnet utility on how to do this and check that the IP Address and details are set correctly. Communication should be restored. Device failure Try to reset the NPR: Remove the NPR cover. Depress the center tab of the I/DISC slot and hold it down. Next press the reset button on the front of the unit and hold for 10 seconds. Release the reset button and then release the center tab. Two LEDs should display steadily. Next depress the center tab and hold it down. Press the reset button on the front of the unit and hold for 10 seconds. Release the center tab and reset button simultaneously. The LEDs should display steadily. The NPR unit should now be ready for a software restore. Download and install the latest system file for the NPR. Configure the I/NET communication in your active Configuration Profile. If you not able to successfully update the firmware in the NPR then it is likely that the device is faulty and may require repair or replacement.  The current replacement for the Series 2000 NPR is the Xenta 527-NPR. Other Troubleshooting Steps See if the communication error shows up on multiple computers and if possible multiple locations. There may be an error with Firewall settings or Ethernet communication that only effects part of a large system Host Workstation Use a different Ethernet port to connect the NPR or workstation too. Direct connect to a controller on the controller LAN via TAP and see if any stations are offline. It is theoretically possible that some form of electrical failure on the controller LAN has caused the NPR to appear offline. If you are unable to see the entire controller LAN from anyone one device, you should troubleshoot Controller LAN communication. Contact Product Support with your findings.

Issue Remove the Routing tables from I/NET and Xenta 527 devices Host conflict or station conflict error messages displayed at the I/NET Host. Incorrect Links, Hosts and IP addresses that do not exist in your Network are shown when penetrating Network Configuration. Product Line Other, TAC INET, TAC Vista Environment I/NET IP Routers Xenta 527 Cause Host or station conflict errors can be caused by old information stored in a routing table. From time to time, it may be necessary to purge that information and allow the tables to be rebuilt automatically. The only way that routing tables can become corrupted is if a laptop was used to connect to the system from a different Network or from the Outside. Once connected, its IP table is broadcasted to the other devices like PCs and NPRs, thus populating the table with entries that does not belong or is non-existent for this location or system.  Resolution Managing I/NET Routing Tables   I/NET Host Workstation View the I/NET Routing Table See Viewing the routing tables on a PC using I/NET Seven for complete instructions. Delete a Single entry in the I/NET Routing Table Go to Start > Run Type Telnet and hit Enter Type open, hit the space bar, then enter the IP address of the PC Press Enter When the login comes up, type csi, hit enter Type LA  and hit enter to list all routing table entries Type ipdel xxx.xxx.xxx.xxx with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table Shutdown the I/O Server Open Windows Explorer Browse to C:\INET Seven Data (or C:\Program Files\INET Seven) Delete the .dat files (you may want to save a backup to another location) Delete the routing table from any device listed as a Reference Host or the table will repopulate Start I/NET Other Method: See Bogus Links, Hosts and IP's in Netcon for instructions on using the delall command in Telnet     Xenta 527-NPR; Xenta 913; Xenta 527 Web Server (See Clear the IP routing tables of a Xenta 913)  Viewing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ip” Press enter Deleting a Single entry in the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ipdel” then the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet delall” Press enter Type “inethost” and press enter Verify or set the Reference Hosts Clear the routing table from any referenced device to ensure old data is not repopulated Restart the Controller to re-populate the routing table   You can also realize this through the web page of Xenta device. Open the web page of Xenta controller, browse to Utilities-I/NET-I/NET Command Line, and type the command below or above. The result is the same as using HyperTerminal, which is also an easier way. Typing “inet help” or “inet” gives every I/NET option within the controller inet - I/NET Help ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all lists ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records   NPR-2000 Viewing the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Deleting a Single entry in the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “ipdel xxx.xxx.xxx.xxx” with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table (See Bogus Links, Hosts and IP's in Netcon)  Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the PC Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “delall” and hit enter to clear the table   Appendix A: I/NET Telnet Commands Glossary: Help – Displays all available commands in the NPR or I/O Server.  Note there are some differences between the NPR and I/O Server. ipadd a.b.c.d – Adds the IP to the routing tables. ipdel a.b.c.d – Deletes the IP from the routing tables. gpadd LLSSPPBBTT XX | a.b.c.d – Adds a global point link or global point IP to the routing tables. delall – Deletes “all” local routing table entries. setpass password – Change the telnet login password (6 characters max). +cpdel LLLL SS – Deletes the specified link/site address from the CP table. +debug gp on|off – Turns global point debugging on or off. +reboot – Reboots the NPR. +wdog – Reports watchdog errors. +wdogrst – Clears the watchdog errors. +Dx – Toggle debug output to COM3.  x=0/1; 0 = off, 1=on.   List Commands: +LR – IP Stack routing table. LI – IP routing table. LM – IP routing masks. LL – Link/Station routing table. LG – Global point routing table. +LC – Compressed routing table. +LS # - Compressed routing table: station to site maps for the specified link #. LA – All routing tables. LU – System metrics. *LD – Dial maps.  + = NPR only * = Host PC only   Appendix B: Method for Clearing Routing Tables at a Large Site See Possible solution to doing a Telnet session with a system wide firewall setup.   Appendix C: Suggested Reference Host Settings   Click here to be linked to the TAC INET Seven Getting Started. Click here to be linked to the TAC INET Seven Operator Guide.   A Reference Host is any TAC I/NET workstation, NPR, or Xenta 527/527-NPR that will serve as a source of IP addresses. Any of these devices attached to an Ethernet LAN can be used as a Reference Host. Each time I/O Server is started on a workstation, it provides the workstation’s IP address to each remote host designated as a Reference Host. I/O Server also requests and receives a list of all host IP addresses that are known to the remote host at that time. I/O Server must be running on the remote host for this address exchange to occur. I/O Server compiles and maintains a list of all the remote hosts that it learns about. Ultimately, all hosts in the network will know the IP addresses of all the other hosts. Ideally, you should determine 1 or at most 2 devices to serve as your Reference Host.  This device would ideally be a Xenta Server or an NPR, but a Host workstation that has I/O Server running 100% of the time will work as well.  All devices on the system will use this as a single Reference Host. No others are needed.  When the device comes online it will contact the Reference Host and get the site’s Routing Table.  The Reference Host can have an empty routing table.  Once the Routing Table is shared, Reference Hosts are no longer needed.  You can leave the single entry in place. This will allow a quick recover, in the event of a critical system failure. Here are a few reasons for using multiple Reference Hosts: Temporarily add a new device as a Reference Host on the Sites Reference Host or a workstation to aid in bringing it online A large site may desire to have 2 Reference Hosts in case one is offline when a device comes online. An I/NET site that spans multiple locations may wish to declare a local Reference Host for each building and a network Reference Host