4.5 OneOs Downloading Software Upgrade

Software upgrade - Loading a New OneOs Image 5 steps: 1. Check for free volume on the flash memory (Note: In the flash memory there is a space for 2 OneOs images. => when testing a new sw image you can keep the old image loaded in the flash) 2. Download a new sw image file 3. Check the new sw image file integrity 4. Rename the sw image file name 5. Reboot

CLI Administration Commands OneOs> help commands cat - Display contents of a file cd - Change working directory clear - Reset functions copy - Copy a file date - Print/set the date devs - List or change all system-known devices format - Format the flash ls - List files mkdir - Create directory mv - Move file (you can use this command to rename a file) pwd - Print curent working directory serial-port - Change serial port caracteristics rm - Remove (Delete) a file show - Show running system information system - System settings time - Print/set the time user - User configuration who - Display users currently logged in

1. Checking Flash Memory Space Before downloading the new OneOs image check available flash size. Minimum required free flash space = 6 MBytes OneOs> show device status flash : (check the last two lines of displayed output) available space: 3024896 bytes max avail. contig space: 1722368 bytes OneOs> Note: If there is not enough of free space, one of the OneOs binaries must be removed ( command « rm ») from the flash memory ( /BSA/binaries/ )

2. Software file download (1/2) Read the bsaBoot.inf file to see the current image location and name: OneOs> cd BSA OneOs> cat bsaBoot.inf flash:/BSA/binaries/OneOs (software image/binary) flash:/BSA/config/bsaStart.cfg (configuration file) Note: “bsaBoot.inf” text file is a definition of: a) which software binary (image with OneOs operating system) is loaded during boot process b) which configuration file is loaded during boot process Move to the right folder: OneOs> cd /BSA/binaries Note: Directory /BSA/binaries is used for storing software binaries ( images with OneOs operating system). Normally there is enough space for 2 images.

2. Software file download (2/2) Log in to an external FTP server and load the new image : OneOs> ftp 10.10.10.11 (FTP Server IP address) username:oneadmin (login to FTP Server) password:oneadmin OneOs(ftp session)> cd <ONEOS_directory> OneOs(ftp session)> get ONEOS1-VOIP-H323-V3.6R10E15.ZZZ OneOs(ftp session)> OneOs(ftp session)> bye OneOs> Note: Using the command “get” you will load required OneOs image from the external FTP server. After loading the image you will check integrity and rename it using command “mv” - see next slides.

3. Verification of Software Integrity Verify loaded image for integrity : CLI> show soft-file info [<path>/]<filename> CLI> show soft-file info ONEOS1-VOIP-H323-V3.6R10E15.ZZZ one200-COLT>sh soft-file info OneOs Binary file informations : file name = /BSA/binaries/OneOs software version = ONEOS1-VOIP_H323-V3.6R10E14 software creation date = 19/04/07 18:17:57 file size = 6360069 (0x610C05) header checksum = 0x8B3BA334 computed checksum = 0x8B3BA334 target device = One30/50/60/200 file is OK CLI> CLI> verify soft-file [<path>/]<filename> CLI> verify soft-file NewOneOs

4. Rename and 5. Reboot Rename the old and new OneOs images and reboot the ONE device : OneOs> mv OneOs OneOs_OLD OneOs> mv ONEOS1-VOIP-H323-V3.6R10E15.ZZZ OneOs OneOs> reboot Do you want to save the running configuration ? (Y/N) Do you want to reboot ? (Y/N) Note: - To display available files use command : “ls” Using the command “mv” you rename the old image “OneOs” to a new name : “OneOs_OLD” Using the command “mv” you rename the new image “ONEOS1-VOIP-H3236V3.6R10E14.ZZZ” to a new name : “OneOs”. Image “OneOs” will be loaded after reboot. (see the definition in “/BSA/bsaBoot.inf” file)

4.5 Trouble Shooting Show Statistics Commands Event Filters System Logging Capture Tool Debug Tool Troubleshooting Commands Sales School – May 17th, 2005

Show Interface Statistics For “IP” interfaces CLI> show interface <type><unit> CLI> show interface fastethernet 0/0 FastEthernet 0/0 is up, line protocol is down Flags: (0x8023) BROADCAST MULTICAST ARP, interface index is 101 Encapsulation: Ethernet v2, MTU 1500 bytes Hardware address is 00:12:ef:20:03:04, ARP timeout 7200 sec Internet address is 192.168.0.10/24, broadcast address is 192.168.0.255 Duplex unknown, Output queuing strategy: fifo, output queue length/depth 0/126 IN: 0 packets, 0 bytes, 0 non-unicast packets 0 unknown protocols, 0 errors, 0 queue drops OUT: 1 packets, 60 bytes, 0 non-unicast packets 0 errors, 0 collisions, 0 queue drops CLI> CLI> show interfaces atm 0.1 CLI> show interfaces loopback 1

Show Interface Statistics For “no IP” interfaces CLI> show adsl --- Configuration of the ADSL Line --- Type annex configured : GDMT (ADSL.ANNEX-A) Modem software version : 0220 Modem state : Modem in Showtime Upstream Bitrate Fast : 0 kbps Downstream Bitrate Fast : 0 kbps Upstream Bitrate Interleaved : 160 kbps Downstream Bitrate Interleaved : 608 kbps Downstream Noise Margin : 29 dB Upstream Noise Margin : 31 dB Downstream Transmit Power : 1 dB Upstream Transmit Power : 12 dB Downstream Attenuation : 1 dB Upstream Attenuation : 3 dB . . . . . . . . . . Power-on Lastread Rx cells count : 0000000111 0000000111 Tx cells count : 0000000016 0000000016 Rx overrun cells count : 0000000000 0000000000 Rx HEC error cells count : 0000000000 0000000000 Idle cell errors : 0000000000 0000000000 Type annex : GDMT (ADSL.ANNEX-A) Up-Down counter : 0 Showtime duration : 0d 0h 0m 58s CLI> show serial 0/0 CLI> show gshdsl

Show Protocol Statistics CLI> show statistics pvc pppoa 0 PPPoA PVC Statistics of ATM interface 0 PVC Pppoa Statistics : vcd = 1, vpi = 8, vci = 35, vcn = LCP Statistics : PPP LCP: OPEN Local MRU: 1500, Remote MRU: 1500 tx packets : 19, tx bytes : 232 rx packets : 18, rx bytes : 220 packets rx > max size : 0 packets rx < min size : 0 tx packets Config Req : 4, rx packets Config Req : 1 tx packets Config Acq : 1, rx packets Config Acq : 3 tx packets Config Nak : 0, rx packets Config Nak : 0 tx packets Config Rej : 0, rx packets Config Rej : 0 tx packets Termination Req: 0, rx packets Termination Req: 0 tx packets Termination Acq: 0, rx packets Termination Acq: 0 tx packets Code Rej : 0, rx packets Code Rej : 0 tx packets Protocol Rej : 0, rx packets Protocol Rej : 0 tx packets Echo Req : 7, rx packets Echo Req : 7 tx packets Echo Rep : 7, rx packets Echo Rep : 7 tx packets Discard Req : 0, rx packets Discard Req : 0 tx packets Identification : 0, rx packets Identification : 0 tx packets Time remaining : 0, rx packets Time remaining : 0 NCP Statistics : PPP IPCP: OPEN local address is 20.19.1.4 (ip unnumbered) remote Addr is 20.19.1.3 dns server configured : 220.6.2.201, 220.6.2.100 tx packets : 3, tx bytes : 108 rx packets : 3, rx bytes : 84 Time for establishing PPP connection 20.18 seconds Time since established PPP connection 75.22 seconds CLI>

Show Protocol Statistics CLI> show statistics serial 0/0 Statistics for interface serial 0/0 : X25 encapsulation Statistics for LINK LEVEL LAYER (LAPB) . . . . . . . . . . . . Statistics for PACKET LAYER CLI> CLI> show statistics ? authentication - Display authentication statistics connect - Show connection statistics frame-relay - Show frame relay statistics frfiwf - Show all connection statistics ima - Show ima statistics isdn - Show statistics isdn pstn - show pstn statistics pvc - Show pvc statistics radius - Show RADIUS statistics serial - Show statistics serial interface tacacs - Display TACACS+ statistics xot - XOT statistics

Troubleshoot verbosity level 3 different levels of verbosity info/traces: Level 1: Information Level 2: Event Level 3: Debug / Traces

Event Function Logging Events for interfaces and protocols can be sent to: console Telnet log file into the file system SNMP traps Syslog Filters must be defined to specify: event family: admin, ip, sys (interface drivers), vox (voice protocols), wan an output device (console or log file): LOG for log file output (RAMDISK:/event1.log) MEM for memory buffers (can be displayed in the Telnet client) SHOW for console output on the console port SYSLOG to send traces to syslog servers TRAP to send as SNMP traces Sales School – May 17th, 2005

Functions for Event Logging Event logging configuration: Sales School – May 17th, 2005

Functions for Event Logging Event logging configuration: Sales School – May 17th, 2005

Functions for Event Logging Event logging configuration: Sales School – May 17th, 2005

Functions for Event Logging Event logging configuration: Sales School – May 17th, 2005

Event Example Sales School – May 17th, 2005

‘Event’ Example CLI> event filter add vox voip all mem CLI> monitor events 00:13:44.092 Info vox voip controlplan 3 Incoming call on voip id: 0, calling: 141870024, called: 9001, call-id: 8. 00:13:44.093 Info vox voip controlplan 3 Outgoing call on local port: 5/0, calling: 141870024, called: 9001, call-id: 8. 00:13:44.305 Info vox voip controlplan 3 Alert received, call-id: 8. 00:13:44.320 Info vox voip userplan 3 VoIP RTP transmission started, coder: G729, call-id: 8. 00:13:44.420 Info vox voip userplan 3 VoIP RTP reception started, coder: G729,call-id: 8. 00:13:45.456 Info vox voip controlplan 3 Call connected, call-id: 8. 00:13:48.200 Info vox voip userplan 3 VoIP RTP transmission stopped, coder: G729, call-id: 8. 00:13:48.200 Info vox voip userplan 3 VoIP RTP reception stopped, coder: G729,call-id: 8. 00:13:48.201 Info vox voip controlplan 3 Call Disconnection received on voip id: 0, cause: (16)[Normal call clearing], call-id: 8.

4. Remove all event filters Event management 1. Add an event filter 2. Event filter display 3. Remove an event filter 4. Remove all event filters

System Logging Another type of logging is the system logging, more intended to IP protocols and functions. It works along with any ‘debug <…>’ command. Redirection of traces: CLI> configure terminal CLI(configure)> logging buffered debug console file syslog buffered: stored in device memory. Use the command «monitor trace» to view the buffered traces console: the traces are output on the console interface file: the traces are recorded under ramdisk:/trace1.log and ramdisk:/trace2.log (circular) syslog: the traces are send to a syslog server. CLI(configure)> show logging To view the buffered logs.

System Logging System logging defines where debug and traces should be redirected to, and the associated severity level : System logging defines the severity level of traces Sales School – May 17th, 2005

Events redirected to telnet session 1. Event filter definition: 2. Event redirection to telnet session:

Debug Function Sample Activate rip event traces CLI> debug sip L….. CLI> debug isdn L….. : Sample Activate rip event traces OneOs> debug ip rip events 12:42:01.679: RIP: sending v2 RESPONSE to 224.0.0.9 via Ethernet0 (192.1.1.1) 12:42:11.088: RIP: received v2 RESPONSE from 192.1.1.2 on Ethernet 0 OneOs> no debug ip rip events Activate rip database traces OneOs> debug ip rip database 16:40:41.871: RIP-DB: adding route to 194.1.1.0/24 through 192.1.1.2 16:43:41.799: RIP-DB: changing metric to 16 for route 194.1.1.0/24 through 192.1.1.2 16:45:41.799: RIP-DB: deleting route to 194.1.1.0/24 through 192.1.1.2 OneOs> no debug ip rip database

Debug / traces redirected to Telnet session 1. Debug or/and trace definition: 2. Traces buffering: 3. Traces redirected to Telnet session:

Analysing Input/Output Traffic Decoding packets at the physical interface level: capture ATM traffic on a specific pvc atm-capture <vpi> <vci> verbose <verbosity> […] serial-capture vxx0 verbose <verbosity> […] Decoding IP packet: debug ip packet { in | out } [<acl>][exclude-telnet] ‘Capture tool’: Enables to filter and decode only specified flows on an interface Captured packets can be stored in a *.cap file (comprehensive decoding using Ethereal or Wireshark) Sales School – May 17th, 2005

ATM-capture mode: example Sales School – May 17th, 2005

Capture Capture mode filter specifies captured traffic / <ESC> stops the capture mode example: Sales School – May 17th, 2005

Analysing Input/Output Traffic ‘Capture’ configuration example: Upload file: CLI > capture CLI(capture)> filter all CLI(capture)> attach 1 atm 0.1 CLI(capture)> exit CLI> monitor capture 1 verbose 3 file capture.cap CLI> copy capture.cap1 tftp://<serveur>/<path>/<name>

Capture on Ethereal Here, we can see all details of RIP updates. Sharp precision, deep protocol analysis.

Troubleshooting Tools Ping source/dest. IP, few TOS values, packet length, frequency Trace-Route (‘traceroute’ networks) List of traversed network nodes to check routing configuration and to detect discontinuity points Extended ping (‘xping’ command) Ping with many configurable characteristics (source, DF-bit, TOS, …) Provides also extended statistics (jitter, …)  ‘monitor xping’ Sales School – May 17th, 2005

Ping CLI> ping <target> [<source_address>] Type escape sequence to abort Sending 5 100-byte ICMP echos to 10.191.250.2 from 20.13.0.10,timeout is 3 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 3/4/8 ms CLI> CLI> ping -t 220.13.1.3 ? <source> - Source address to use -l - Size of packet used for ping -n - Number of packets used for ping -v - Type of service : [no-tos], low-delay, throughput, reliability, min-cost -f - Set don't fragment flag -w - timeout in seconds to wait for each reply Sales School – May 17th, 2005

Traceroute List of traversed network nodes from source to destination: CLI> traceroute <target> [<source_address>] Example: CLI> traceroute 220.13.1.3 20.13.0.10 Type escape sequence to abort. Tracing the route to 220.13.1.3 from 20.13.0.10 1 20.13.1.3 2 msec * 2 msec CLI> This options are available: CLI> traceroute -t 220.13.1.3 ? <source> - Source address to use -l - Packet size -i - Time to live -v - Type of service : [no-tos], low-delay, throughput, reliability,min-cost -f - Set don't fragment flag -w - timeout in seconds to wait for each reply Sales School – May 17th, 2005

Xping (eXtended Ping) XPING the xping allows to initiate several ping sessions to several destinations. the output are round-trip-delay (min, max, average) jitter and loss CLI> xping <session_name> CLI(xping)> ? activate - activate a xping session address - destination IP address data-size - data size of icmp packet deactivate - stop the session exit - exit xping mode df-flag - set the DF flag of outgoing packets dsfield - DSCP value frequency - frequency (interval in seconds). probe-count - nr of sent packets per ping show - show the xping session source - IP source address timeout - Time out. <cr> CLI(xping)> Sales School – May 17th, 2005

Xping Activate a xping session: Statistics in real time : CLI(xping)> activate Statistics in real time : CLI> monitor xping Destination Source Freq. Tx Tmin Tavg Tmax Address Address Pings (sec) Rx (ms) (ms) (ms) ------------------------------------------------------------------------------ * enabled: dns1 jitter: 6.05 ms 2.73 5.82 7.55 84.103.237.142 81.185.33.162 1 1570 19 28 39 157 1570 Loss rate: 0.00% * enabled: dns2 jitter: 0.53 ms 0.35 0.43 0.57 86.64.145.142 81.185.33.162 10 8 55 57 62 8 8 Loss rate: 0.00% [Esc]-Exit. Remove a xping session: CLI> no xping <session_name> Sales School – May 17th, 2005

The Ultimate Tech. Support Command The ‘show tech-sup’ command is an useful command that shows many interesting information for OneAccess support engineers: OneOs> show tech-sup [paging] So, including a ‘show tech-sup’ in a Trouble Ticket never hurts and is often more efficient than explanations. Also, it is often helpful to call this command two times, so that OneAccess can observe which counters gets incremented (and which one are not) Sales School – May 17th, 2005