- The JSystem Wiki Demo Guide
- Version 2.0
- Prepared by Sassy Natan (sassy.natan@…)
- Version 2.0
The JSystem Wiki Demo Guide
Version 2.0
Prepared by Sassy Natan (sassy.natan@…)
1. Introduction
"In the beginning, the file was without form, and void; and emptiness was upon the face of the bits. And the Fingers of the Author moved upon the face of the keyboard. And the Author said, Let there be words, and there were words."
The Ethos System Demo Guide describes the system architecture of Ethos Traffic System Control and the required information in order to build a working demo environment. It is intended for people who know next to nothing about system administration (those saying "what is it?"), but who have already mastered at least the basics of normal usage. This manual doesn't tell you how to configure and install Ethos Devices; that is described in the Installation and Configure Ethos Device document.
The structure of this manual is such that many of the chapters should be usable independently, so if you need information about how to connect the device, for example, you can read just that section. However, this manual is first and foremost a tutorial and can be read sequentially or as a whole.
In trying to describe how things work, rather than just listing "five easy steps" for each task, there is much information here that is not necessary for everyone, but those parts are marked as such and can be skipped if you use a pre-configured system. Reading everything will, naturally, increase your understanding of the system and should make using and administering it more productive.
2. Trademarks
- Ethos is Trademark of Ethos-Networks.
- Microsoft, Windows, Windows NT, Windows 2000, and Windows XP are trademarks and/or registered trademarks of Microsoft Corporation.
- Red Hat is a trademark of Red Hat, Inc. in the United States and other countries.
- Linux is a registered trademark of Linus Torvalds.
- GNU is a registered trademark of the Free Software Foundation.
- EZchip is a trademark of EZchip Technologies Ltd. TOPcore, NP-1 and Network-Specific Processor (NSP) are trademarks of EZchip Technologies Ltd.
- The Ixia is a registered trademark of Ixia.
- Other product names mentioned herein may be trademarks and/or registered trademarks of their respective companies.
3. Overview of an Ethos System
This describes the architecture parts of Ethos Demo environment. Based on the following diagrams you can understand each of the components of the Ethos Demo, and you will be able to operate the demo system. Although not all networks architectures follow this standard it is still generic enough to give you a fully overview.
Host Name Type IP Address OS Username Password Core01 Netgear Switch 7212 172.18.0.2 N/A admin admin Core02 Netgear Switch 7212 172.18.0.3 N/A admin amin Core03 Netgear Switch 7212 172.18.0.4 N/A admin admin Core04 Netgear Switch 7212 172.18.0.5 N/A admin admin Edge01 Ethos Bridge 172.18.0.6 EOS root operator Edge02 Ethos Bridge 172.18.0.7 EOS root operator Edge03 Ethos Bridge 172.18.0.8 EOS root operator Edge04 Ethos Bridge 172.18.0.9 EOS root operator Aggr01 Switch Aggregator 172.18.0.10 N/A admin N/A Aggr02 Switch Aggregator 172.18.0.10 N/A admin N/A Aggr03 Switch Aggregator 172.18.0.10 N/A admin N/A Aggr04 Switch Aggregator 172.18.0.10 N/A admin N/A Ixia Ixia 400T Traffic Generator 172.18.0.11 Windows 2000 N/A N/A Management-Switch 3Com Switch 172.18.0.12 N/A admin N/A NMS X86 - Dell Optiplex GX620 172.18.0.13 RH Linux E4F4 root 123456 NMSClient X86 - HP Laptop 172.18.0.14 Debian Linux root 123456 Presentation X86 - HP Laptop 172.18.0.15 Windows XP Administrator 123456 Video-Server01 ? 192.168.0.1 ? ? ? Video-Client01 ? 192.168.0.2 ? ? ? Video-Client02 ? 192.168.0.3 ? ? ? Video-Client03 ? 192.168.0.4 ? ? ?
4. Network Topology
- Interconnecting the devices is a simple task which can be easily achieved if you go simply by the following diagram. Keep in mind that they are two basic principles which need to be followed:
- Using the right cables for connecting the devices
- Connecting each network port to his relevant one
4.1 - Connecting Core Devices with Ethos Devices
Due to historical reasons ports labeled as zero are actually physical ports labeled as one on the EZBox, so all EZBox ports are shifted by one in accordance.
4.2 - Connecting Clients to Ethos Edge01
All red object are IXIA virtual servers. c1p1 staned for Card 1, Port 1. c2p1 staned for Card 2, Port 1.
4.3 - Connecting Clients to Ethos Edge02
All red object are IXIA virtual servers. c1p2 staned for Card 2, Port 1. c2p2 staned for Card 2, Port 2.
4.4 - Connecting Clients to Ethos Edge03
All red object are IXIA virtual servers. c1p3 staned for Card 3, Port 1. c2p3 staned for Card 2, Port 3.
4.5 - Connecting Clients to Ethos Edge04
All red object are IXIA virtual servers. c1p4 staned for Card 4, Port 1. c2p4 staned for Card 2, Port 4.
5. Service and Tunnel Provisioning
Ethos Demo is divided into three scenarios (DynTE, WEIR, CIR Utiliaztion). Each scenario present different and unique behavior of Ethos Technology. The First scenario, which is the basic understanding for the other scenarios of the demo, is basically a quick introduction of Ethos DynTE mechanism. This mechanism provided network fairness along services who share the same provisioning path (Tunnel) and QoS policy. The WEIR scenario build on top of the Ethos DynTE scenario, present Ethos Weighted EIR control parameter who effect how Ethos control EIR services. The last scenario is a mix of the other two scenarios which emphasize Ethos Network in a mix network topology where E-Line, E-Tree share the same provisioning path (Tunnel) with different QoS policy (CIR, EIR and WEIR). In the following table you can find a list of services and QoS policies for each demo scenario.
QoS Policy Table
Policy Name CIR CBS PIR PBS WEIR HD-Video 24MB 1024Kb 26 MB 1024Kb 10 CIR0PIR200W10 0 0 200MB 1024Kb 10 CIR0PIR500W10 0 0 500MB 1024Kb 10 CIR0PIR200W20 0 0 200MB 1024Kb 20 CIR200PIR400W10 200MB 1024Kb 400MB 1024Kb 10 CIR0PIR400W10 0 0 400MB 1024Kb 10 CIR0PIR400W40 0 0 400MB 1024Kb 40
Network Services Table
Service Name Service Type Client Source Client Destination Edge Source Edge Destination Ixia Port Policy Name Demo Type HD-Video E-Tree Video-Server01 Video-Client 01, 02, 03 Edge01 Edge02, Edge03, Edge04 c0p1 CIR0PIR200W10 DynTE 01To15 E-Line Server01 Server15 Edge01 Edge04 c0p1 CIR0PIR200W10 DynTE 02To15 E-Line Server02 Server15 Edge01 Edge04 c0p1 CIR0PIR200W10 DynTE 03To15 E-Line Server03 Server15 Edge01 Edge04 c0p1 CIR0PIR200W10 DynTE 04To15 E-Line Server04 Server15 Edge02 Edge04 c0p2 CIR0PIR200W10 DynTE 05To15 E-Line Server05 Server15 Edge02 Edge04 c0p2 CIR0PIR200W10 DynTE 06To15 E-Line Server06 Server15 Edge02 Edge04 c0p2 CIR0PIR200W10 DynTE 07To15 E-Line Server07 Server15 Edge03 Edge04 c0p3 CIR0PIR200W10 DynTE 08To15 E-Line Server08 Server15 Edge03 Edge04 c0p3 CIR0PIR200W10 DynTE 09To15 E-Line Server09 Server15 Edge03 Edge04 c0p3 CIR0PIR200W10 DynTE 10To12 E-Line Server10 Server12 Edge01 Edge02 c1p1 CIR0PIR500W10 DynTE 11To14 E-Line Server11 Server14 Edge01 Edge03 c1p1 CIR0PIR200W10 DynTE 13To14 E-Line Server13 Server14 Edge02 Edge03 c1p2 CIR0PIR200W10 DynTE 16To15* E-Line Server16 Server15 Edge01 Edge04 c0p1 CIR0PIR200W20 WEIR 20To25* E-Line Server20 Server25 Edge01 Edge04 c0p1 CIR0PIR400W40 CIR Utiliaztion 21To25* E-Line Server21 Server25 Edge01 Edge04 c0p1 CIR0PIR400W10 CIR Utiliaztion 22To25* E-Line Server22 Server25 Edge01 Edge04 c0p1 CIR200PIR400W10 CIR Utiliaztion 23To25* E-Line Server23 Server25 Edge02 Edge04 c0p2 CIR200PIR400W10 CIR Utiliaztion 24To25* E-Line Server24 Server25 Edge03 Edge04 c0p3 CIR200PIR400W10 CIR Utiliaztion
* Services are not include in the drawing
6. Power up the system
"Knowledge speaks, but wisdom listens." Jimi Hendrix
The way to start Ethos System Demo is to use some simple steps. Each step is dependency of the previous one, so you must first finish the current step in order to continue. In this section will assume that you have a full access to Ethos Edge devices and the NMS server.
Before power up any of the components make sure all devices are plugged in to the correct ports. Ethos Technology is based on a well known network provisioning, if you plugged for example the Video Server adapter to the Video Client port on the EZBox – the demo will not work
6.1 Power up Core switches, Aggregator and Management Switch.
- Power up lower power strip first (Management Switch must be on berfore any other device in the ethos Domain).
- Core Switches should be fully operational after 90sec.
- Change Led Mode to Act mode on the core switch using the small front panel button.
- No Network activity is present in the network at the moment, so activity leds of the ports of the core switch should be off.
- Access to the system core is done via any Telnet client. In this tutorial we will be using the build-in Telnet client of common Linux distribution.
- In order to login to any of the core switches, please do the following:
[root@nms ~]# telnet core01 Trying 172.18.0.2... Connected to core01.Ethos.Local (172.18.0.2). Escape character is '^]'. (GSM7212) User:admin Password:***** (GSM7212) >
6.2 Power up the NMS Server
- The NMS Server is running Red Hat Enterprise Linux WS release 4 (Nahant Update 4).
- System should be fully operational after 90sec.
- Access to the NMS Server is done via any SSH client (such as Putty). In this tutorial we will be using the build-in ssh client of common Linux distribution. If this is the first time you connect the NMS server, you must accept the RSA key fingerprint.
linux:~/.ssh# ssh nms The authenticity of host 'nms (172.18.0.13)' can't be established. RSA key fingerprint is 80:2a:ee:5b:9c:15:6d:d0:7f:2d:0e:2e:cb:2a:67:ee. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'nms,172.18.0.13' (RSA) to the list of known hosts. root@nms's password: Last login: Sun Aug 26 11:34:10 2007 from 172.18.0.31 [root@nms ~]#
- Since Ethos Switches are configured as a DHCP client, we must make sure that the DHCP server is up and running on the NMS server.
[root@nms ~]# service dhcpd status dhcpd (pid 12528) is running... [root@nms ~]#
if the dhcp server is down, or inactive you can easy restart[root@nms ~]# service dhcpd restart Shutting down dhcpd: [ OK ] Starting dhcpd: [ OK ] [root@nms ~]#
6.3 Power up the Ethos Devices
Warning: Ethos devices MUST be powered up only after the NMS server is operative and DHCP is turned on.
- The Ethos Device is running Ethos Operation System.
- System should be fully operational after 150sec.
- Access to the Ethos Devices is done via any SSH client (such as Putty). In this tutorial we will be using the build-in ssh client of common Linux distribution.
- The easiest way to connect to the Ethos Devices is from the NMS Server. This is due the fact that the Ethos Devices trusted the SSH Public Key generated by the NMS Server. See the following Example:
[root@nms ~]# ssh edge01 Warning: Permanently added 'edge01' (RSA) to the list of known hosts. [root@ezbox-6]
- In order to check if Ethos system is up and running on All Ethos Devices ship the command 'ethos-app-domain.sh' from the NMS 'command line'. The stdout should print the follwing ouput (by order of the Ethos device and processes runing on device)
[root@nms ~]# ethos-app-domain.sh status 172.18.0.6 monit -c /usr/local/ethos/etc/monit.conf -g eapp summary | grep Process Process 'syslog-ng' running Process 'portmap' running Process 'snmpd' running Process 'ntpd' running Process 'crond' running Process 'collector' running Process 'dispatcher' running Process 'dynte_client' running Process 'pa' running Process 'sa' running Process 'snmp_pa' running Process 'tebroker' running Process 'snmp_subagent_system' running 172.18.0.7 monit -c /usr/local/ethos/etc/monit.conf -g eapp summary | grep Process Process 'syslog-ng' running Process 'portmap' running Process 'snmpd' running Process 'ntpd' Connection failed Process 'crond' running Process 'collector' running Process 'dispatcher' running Process 'dynte_client' running Process 'pa' running Process 'sa' running Process 'snmp_pa' running Process 'tebroker' not monitored Process 'snmp_subagent_system' running 172.18.0.8 monit -c /usr/local/ethos/etc/monit.conf -g eapp summary | grep Process Process 'syslog-ng' running Process 'portmap' running Process 'snmpd' running Process 'ntpd' running Process 'crond' running Process 'collector' running Process 'dispatcher' running Process 'dynte_client' running Process 'pa' running Process 'sa' running Process 'snmp_pa' running Process 'tebroker' not monitored Process 'snmp_subagent_system' running 172.18.0.9 monit -c /usr/local/ethos/etc/monit.conf -g eapp summary | grep Process Process 'syslog-ng' running Process 'portmap' running Process 'snmpd' running Process 'ntpd' running Process 'crond' running Process 'collector' running Process 'dispatcher' running Process 'dynte_client' running Process 'pa' running Process 'sa' running Process 'snmp_pa' running Process 'tebroker' not monitored Process 'snmp_subagent_system' running [root@nms ~]#
Make sure all process are running, except the 'tebroker' service which should run on the chosen 'tebroker' server.
Common messages:- 'running'/'not monitored'/'Changed' mode is status OK.
- 'Data access error'/'failed' mode is status failed.
- 'Does not exist' mode is status not initalized.
- 'initalizing' mode is status initalizing.
In the event of an error message or an abnormal behavior wait for a couple of seconds and view status again. If the status did not change after transmitting traffic through the system see the troubleshooting section below.
6.4 Power up the IXIA
- The IXIA Device is running on Windows 2000 Operation System.
- System should be fully operational after 300sec.
- (Optional) If you want to connect to the operation system window you can login via VNC (hostname IXIA, no-password) or directly connect to the IXIA device interface (keyboard/mouse/display).
- Access to the system core is done a TCL/TK client or via Ixia Ix-Explorer.
- Configuring the IXIA Server via the TCL/TK client is done with a predefine script with specific parameters. If you wish to configure the IXIA with other parameters or a new network steams please use the Ix-Explorer (requires GUI).
f.In this tutorial we will be using our predefine ixia script located on the NMS Server.
root@nms /]# [root@nms /]# cd /opt/ [root@nms opt]# pwd /opt [root@nms opt]# ./HWEIR2.0.ixia -v ixia Application initialization failed: no display name and no $DISPLAY environment variable ###### WEIR Streaming Test ###### Tcl Client is running Ixia Software version: 4.10.250.23 Connecting to Tcl Server ixia ... ixTakeOwnership {{1 1 1} {1 1 2} {1 1 3} {1 1 4} {1 2 1} {1 2 2} {1 2 3}} force Took ownership of following ports: {1 1 1} {1 1 2} {1 1 3} {1 1 4} {1 2 1} {1 2 2} {1 2 3} port setFactoryDefaults 1 1 1 port setPhyMode 1 1 1 1 port reset 1 1 1 port config -transmitMode portTxModeAdvancedScheduler port config -receiveMode 4096 port set 1 1 1 stream write 1 2 1 2 stream set 1 2 2 1 stream write 1 2 2 1 ## Play profile ## Flow: 0 -> Card.Port: 1.1 -> Stream ID: 1 -> Stream Name: A_01To15 (true) Flow: 1 -> Card.Port: 1.1 -> Stream ID: 2 -> Stream Name: A_02To15 (true) Flow: 2 -> Card.Port: 1.1 -> Stream ID: 3 -> Stream Name: A_03To15 (true) Flow: 3 -> Card.Port: 1.2 -> Stream ID: 1 -> Stream Name: B_04To15 (true) Flow: 4 -> Card.Port: 1.2 -> Stream ID: 2 -> Stream Name: B_05To15 (true) Flow: 5 -> Card.Port: 1.2 -> Stream ID: 3 -> Stream Name: B_06To15 (true) Flow: 6 -> Card.Port: 1.3 -> Stream ID: 1 -> Stream Name: C_07To15 (true) Flow: 7 -> Card.Port: 1.3 -> Stream ID: 2 -> Stream Name: C_08To15 (true) Flow: 8 -> Card.Port: 1.3 -> Stream ID: 3 -> Stream Name: C_09To15 (true) Flow: 9 -> Card.Port: 2.1 -> Stream ID: 1 -> Stream Name: D_10To12 (true) Flow: 10 -> Card.Port: 2.1 -> Stream ID: 2 -> Stream Name: D_11To14 (true) Flow: 11 -> Card.Port: 2.2 -> Stream ID: 1 -> Stream Name: E_13To14 (true) Enter command (e:enable #id|a, d:disable #id|a, g:go, s:stop, n:next, q:quit, i:info):
Control Switches
- i for 'Info'; prints all streams current status (true/false).
- g for 'go'; starts generating traffic according to current streams setup.
- s for 'stop'; stops transmitting on all streams.
- d a for 'disable'; disables all streams
- d % for 'disable'; disables the % stream
- e a for 'enable'; enables all streams
- e % for 'enable'; enables the % stream
For example: To start streaming network traffic hit the 'g' key and press enter. To disable all stream hit 'd a' and enter. To enable on of the stream hit 'e' followed by the stream number. The 's' key will stop all streaming.
7. Video Client/Server Configuration
To start streaming High-Definition video content over the network, we will use video server application that supports video streaming. VideoLAN is one of the open source application available in the public domain, with cross platform support and various audio and video formats (MPEG 1, MPEG 2, MPEG 4, DivX, mp3, Ogg, etc.). In this tutorial we will use a ripped High-Definition TS/MPEG, and stream it over the network to the several video clients using Multicast Technology.
7.1 Video Server
- Open the VideoLAN Application on the Video Server (this can be done on any machine that support VideoLAN)
- under the file menu select “Open File” and navigate to your saved TS/MPEG file.
- In the same window select the streaming output and click on the setting button.
- In the setting window check out UDP as the output method, and provide '239.255.12.42' as the multicast address. Make sure that the Encapsulation Method is MPEG TS – which a widely used as a common container for digital contents.
- Click OK and start streaming the file by pressing the play button.
7.2 Video Clients
- On each Video Client Open the VideoLAN Application, under the file menu select “Open Network Stream”.
- Click on the network tab, select UDP/RTP, and write at the open bar the multicast address. You should have something like the following, assuming your multicast address is '239.255.12.42' – udp://239.255.12.42. Click OK and then click on the play button.
- If you using a linux based machine use the vlc command as follow:
videoclientI:/#vlc -vvv udp:@239.255.12.42
- Grab a popcorn/coke or other fatty food and enjoy the movie.
8. NMS Graphical User Interface
- The NMS Server must be up and running before connecting the NNS GUI.
- The NMS Server daemon is not started by default. You must start it manually via the service command:
[root@nms ~]# service ethos-nms start [root@nms ~]#
- The NMS GUI Client running on Microsoft Windows XP.
- The NMS GUI Client must have Sun Java installed.
- In order to open the NMS GUI Console open Microsoft Internet Explorer and navigate to NMS server. For exmaple http://nms:8080/NMSGUI/. In this example we provide the nms as the NMS hostname, but an IP address is also a valid option.
- In the NMS GUI login window please provide the NMS IP address.
- Once the NMS GUI will open, navigate to the performance window and check out the flows you want to display.
- Make sure to check Chart as view type, with Advanced mode on for classic demo graphs display.
- The refresh time period is depened on how much flows you monitor at the same time. For Power Point Based Demo, or High-Level NMS Based Demo the 0.1 sec refresh rate is supported.
- If this is a Power Point Based Demo' please select the following service to present: 01To015, 02To015, 03To015, 04To015, 05To015, 06To015, 07To015, 08To015, 09To015. Once it is done, click next and select the services flows. The simple way to select service flows is to sort them by the flow source (From EdgeX to Edge04) see the example:
- If this is a High-Level, NMS Based Demo ' please select the following service to present: ???
9. Power Point Based Demo
- The objective of a 'power point' based demo is too supply an easy control methodology that enables operating a short , predefined, sequence of a demonstration without the need for deep knowledge in either the NMS or any scripting capabilities.
- The NMS demo is based on an event-driven script identifying certain slides in a power point presentation and using their screening as the event to triggering changes in the Ethos domain.
- At the current version (Geneva demo) these changes only include DynTE-On or DynTE-Off.
- The power point script-end is based on Visual Basic.
- Operation:
- The Ethos Demo system must be up and running on all Ethos devices in a 'DynTE-On' mode before power point start. The Default Ethos Mode is 'DynTE-On', if from some reason you want to change Ethos Mode, please check the Ethos Devices properties under the Topology Perspective window.
- Presentation server must resolve all Ethos host names; Make sure you have an update HOSTS file in your system.
- Leaving the presentation (screening mode) at any moment will leave the system at its last DynTE state.
- The screen-saver on the presentation server must be turned off.
- The presentation is screened using Power Point 2007 with the EventGen plugin over Windows XP.
10. High-Level, NMS Based Demo
11. Troubleshooting
- Why I can't telnet to the switch core device?
Check to see if the computer you are truning to connect with is part of the Network ID 172.18.0.0/24.
- How can I check and see if the static MAC addresses are configure on the core switches?
Telnet to each Core Device and use the mac-address-table command as follow:[root@nms ~]# [root@nms ~]# [root@nms ~]# telnet core01 Trying 172.18.0.2... Connected to core01.Ethos.Local (172.18.0.2). Escape character is '^]'. (GSM7212) User:admin Password:***** (GSM7212) >show mac-address-table static all Destination MAC Address VLAN ID Port(s) ----------------- ------- ------------------- 00:00:00:07:A1:20 2 0/9 00:00:00:0C:35:00 2 0/12 01:00:5E:7F:0C:2A 2 0/12 (GSM7212) > - How can I restart the NMS Serivce
Logon to the NMS server and user the service command as follow:[root@nms ~]# [root@nms ~]# [root@nms ~]# service ethos-nms restart Stopping Front End Server Running JBoss found.... Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion Stopping BackEnd Server Stopping DB Server startBES.sh: no process killed Starting Ethos-NMS R2.0 Server:MYSQL was Started Successfully Starting mysqld daemon with databases from /var/lib/mysql Front End Server will be ready in two minutes ... FES was Started Successfully BackEnd Server will be ready in two minutes ... BES was Started Successfully 0 Started, please confirm with /etc/init.d/ethos-nms stat [root@nms ~]#
- Some service not loaded successfully when checking the Ethos Devices using the ethos-app-domain.sh command.
The ethos-app-domain.sh can start/stop or get status of the Ethos devices. If you want to restart the entire Ethos Domain use the ethos-app-domain.sh command as follow:[root@nms ~]# ethos-app-domain.sh stop 172.18.0.6 monit -c /usr/local/ethos/etc/monit.conf -g eapp stop all Warning: Permanently added '172.18.0.6' (RSA) to the list of known hosts. 172.18.0.7 monit -c /usr/local/ethos/etc/monit.conf -g eapp stop all Warning: Permanently added '172.18.0.7' (RSA) to the list of known hosts. 172.18.0.8 monit -c /usr/local/ethos/etc/monit.conf -g eapp stop all Warning: Permanently added '172.18.0.8' (RSA) to the list of known hosts. 172.18.0.9 monit -c /usr/local/ethos/etc/monit.conf -g eapp stop all Warning: Permanently added '172.18.0.9' (RSA) to the list of known hosts. [root@nms ~]# [root@nms ~]# [root@nms ~]# [root@nms ~]# ethos-app-domain.sh start 172.18.0.6 monit -c /usr/local/ethos/etc/monit.conf -g eapp start all 172.18.0.7 monit -c /usr/local/ethos/etc/monit.conf -g eapp start all 172.18.0.8 monit -c /usr/local/ethos/etc/monit.conf -g eapp start all 172.18.0.9 monit -c /usr/local/ethos/etc/monit.conf -g eapp start all [root@nms ~]#
- Restore Core Switch configuration from factory default mode
The Core switch may restore is default configuration from a hardware failure or a software one. If you need to restore the core configuration please do the following:- Download SolarWins TFTP Server and installed it on a Windows based PC.
- Copy the CoreX.scr backup files from the Backup DVD to the default TFTP home directory (usually C:\TFTP-Root) and start the application.
- Connect the serial (RS232) cable to the failure core switch and to your host pc. If you don't have a RS232 connector you can use the USB convertor cable, but you must have the Conceptronic driver installed on your PC.
- Open a basic console application that support serial connection. Hyper Terminal or Tera Term Pro are good choices. Configure the serial connection as follow:
- Baud rate: 9600
- Data: 8 bit
- Parity: none
- Stop: 1 bit
- Flow control: none
- The first step is to configure a IP address to the switch. In this example we assume that the Core01 is the malfunctioning core device. Please Note that there is no password for the user admin in a factory-default mode.
(GSM7212) User:admin Password: (GSM7212) >en Password: (GSM7212) #network protocol none Changing protocol mode will reset ip configuration. Are you sure you want to continue? (y/n)y (GSM7212) # (GSM7212) #network parameters 172.18.0.2 255.255.255.0 172.18.0.1 (GSM7212) #logout The system has unsaved changes. Would you like to save them now? (y/n) y
- Our last step is to download-load the Core Switch configuration file from the TFTP server. Again in this example we assume that the Core01 is the mal-functioning core device.
(GSM7212) User:admin Password:***** (GSM7212) > (GSM7212) > (GSM7212) > (GSM7212) >en Password:***** (GSM7212) # (GSM7212) # (GSM7212) #copy tftp://TFTPServerIPAddress/Core01.scr nvram:startup-config Mode........................................... TFTP Set TFTP Server Address........................ 172.18.0.31 TFTP Path...................................... TFTP Filename.................................. Core01.scr Data Type...................................... Config Download configuration file. Current configuration will be cleared. Management access will be blocked for the duration of the transfer Are you sure you want to start? (y/n) y TFTP config transfer starting TFTP receive complete... updating configuration
The Switch will now restart itself and will be up and running with the new configuration.
- When opening the NMS GUI Client and configuring the chart graphs only transmited data apper in the graph
The Ethos Device DB is based on the NMS configuration. If the NMS server get an error on one of his devices it might damage the DB on the Ethos Device. In order to fix that please do the following:- Open the NMS GUI Client.
- Click the topology window and refresh each device status. This should change the device status to normal and bring the link status to online state (color will be change from red to green).
- Now we will change the service USN number in the NMS Database. This will push the new database to the Ethos Devices. In order to do that please open the MYSQL Query Browser in the Presentation server and login to the NMS DataBase? Server:
- Username:root
- password:root
- Database-name: operDB
- Click on the global_param table and then on the execute button.
- Check out the value under the services_version.
- Run the following PL/SQL script in the query browser:
update global_param set value = 'current-value+1' where value = 'current-value'
- Click on the execute button and wait for 1 min. System will sync and will be ready.
Please note that the current-value is the value you checked out in step 5.
