Avaya G250 Administration page 513

6. Verify that the hardware version of the Media Gateway is a FIPS-approved version.
- Use the show system command and verify that HW ready for FIP: Yes.
G350-N(super)# show system
System Name
System Location
System Contact
Uptime (d,h:m:s)
MV Time
MAC Address
WAN MAC address
Serial No
Model No
HW Vintage
HW Suffix
FW Vintage
HW ready for FIPS
7. Verify that both firmware banks contain firmware images that have been FIPS-approved.
- Use the dir command. The output should be similar to the following:
For the G350:
●
G350-N(super)# dir
M# file
-- ----
1 Voice (Initializing) N/A
- image
7 Voice (Initializing) N/A
- image
7 Analog
10 startup-config
10 running-config
10 G350-A
10 G350-B
B
10 G350
10 G350-Booter
10 sniffer
10 phone-ScriptA
10 phone-ScriptB
10 phone-ImageA
10 phone-ImageB
10 phone-ImageC
10 phone-ImageD
10 dhcp-binding
:
:
:
: 1,16:03:33
: 11:03:59 22 FEB 2005
: 00:04:0d:6d:30:e1
: 00:04:0d:6d:30:e1
: 03IS07639510
: G250-BRI
: 3
: A
: 24.11.0
: Yes
ver num file type
-------- ----------
SW RT Image
SW RT Image
57 SW RT Image
N/A Startup Conf Nv-Ram
N/A Running Conf Ram
24.x.y SW RT Image
24.x.y SW Component Flash Bank B
1.0.19 SW Web Image Nv-Ram
23.x.y SW BootImage Nv-Ram
N/A Other
N/A Phone Script Nv-Ram
N/A Phone Script Nv-Ram
N/A Phone Image
N/A Phone Image
N/A Phone Image
N/A Phone Image
N/A DHCP Binding Nv-Ram
Administration procedures
file location file description
------------- ----------------
Nv-Ram Voice (Initializing)
Nv-Ram Voice (Initializing)
Nv-Ram Analog - image
Startup Config
Running Config
Flash Bank A Software Image Bank A
Software Image Bank
EmWeb application
Booter Image
Ram Sniffer Capture
N/A
N/A
Ram N/A
Ram N/A
Ram N/A
Ram N/A
Ip Address Binding
Issue 1.1 June 2005 513