1. 4.5 OneOs Downloading Software Upgrade

2. 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

3. 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

4. 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: bytes
max avail. contig space: 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/ )

5. 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.

6. 2. Software file download (2/2)
Log in to an external FTP server and load the new image :
OneOs> ftp (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.

7. 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 = (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

8. 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)

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

10. 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 /24, broadcast address is
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

11. 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 :
Tx cells count :
Rx overrun cells count :
Rx HEC error cells count :
Idle cell errors :
Type annex : GDMT (ADSL.ANNEX-A)
Up-Down counter : 0
Showtime duration : 0d 0h 0m 58s
CLI> show serial 0/0
CLI> show gshdsl

12. 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 : , tx bytes :
rx packets : , rx bytes :
packets rx > max size : 0
packets rx < min size : 0
tx packets Config Req : , rx packets Config Req :
tx packets Config Acq : , rx packets Config Acq :
tx packets Config Nak : , rx packets Config Nak :
tx packets Config Rej : , rx packets Config Rej :
tx packets Termination Req: , rx packets Termination Req:
tx packets Termination Acq: , rx packets Termination Acq:
tx packets Code Rej : , rx packets Code Rej :
tx packets Protocol Rej : , rx packets Protocol Rej :
tx packets Echo Req : , rx packets Echo Req :
tx packets Echo Rep : , rx packets Echo Rep :
tx packets Discard Req : , rx packets Discard Req :
tx packets Identification : , rx packets Identification :
tx packets Time remaining : , rx packets Time remaining :
NCP Statistics :
PPP IPCP: OPEN
local address is (ip unnumbered) remote Addr is
dns server configured : ,
tx packets : , tx bytes :
rx packets : , rx bytes :
Time for establishing PPP connection seconds
Time since established PPP connection seconds
CLI>

13. 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

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

15. 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

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

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

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

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

20. Event Example
Sales School – May 17th, 2005

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

22. 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

23. 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.

24. 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

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

26. 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 via Ethernet0 ( )
12:42:11.088: RIP: received v2 RESPONSE from 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 /24 through
16:43:41.799: RIP-DB: changing metric to 16 for route /24 through
16:45:41.799: RIP-DB: deleting route to /24 through
OneOs> no debug ip rip database

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

28. 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

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

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

31. 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>

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

33. 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

34. Ping CLI> ping <target> [<source_address>]
Type escape sequence to abort
Sending byte ICMP echos to from ,timeout is 3 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/4/8 ms
CLI>
CLI> ping -t ?
<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

35. Traceroute List of traversed network nodes from source to destination:
CLI> traceroute <target> [<source_address>]
Example:
CLI> traceroute
Type escape sequence to abort.
Tracing the route to from
msec * 2 msec
CLI>
This options are available:
CLI> traceroute -t ?
<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

36. 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

37. 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: dns jitter: 6.05 ms
Loss rate: 0.00%
* enabled: dns jitter: 0.53 ms
Loss rate: 0.00%
[Esc]-Exit.
Remove a xping session:
CLI> no xping <session_name>
Sales School – May 17th, 2005

38. 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