Nokia IP390 Installation Guide - Page 81

Appliance Does Not Recognize New Memory Configuration, Appliance Not Receiving Power

Get Nokia IP390 - Security Appliance PDF manuals and user guides View all Nokia IP390 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 81 highlights

General Troubleshooting Information Appliance Not Receiving Power Problem Power cord is not properly plugged in. Solution Check cord. Make sure it is properly seated at both ends. Problem Power supply not providing power. Solution Check power source. If there is no power at the source, take appropriate action such as inserting a new fuse or resetting circuit breaker. Appliance Does Not Recognize New Memory Configuration Problem DIMMs are not properly seated in DIMM sockets. Solution Repeat memory installation procedures. Make sure DIMMs are fully seated in sockets. Be sure DIMMs click into place. Appliance locks up after you upgrade Nokia IPSO with a console connection. No error messages appear, but the appliance stops responding to console and network. Problem During the upgrade process, some of the environment variables might not have updated correctly. Solution You can verify what the current boot manager settings are by issuing a printenv command at the boot manager prompt, as shown in this example: Loading boot manager .. BOOTMGR[0]> printenv Bootmgr Revision: 3.3,base kernel=3.5.1-fcs1 02.12-2001-102644 autoboot: NO bootwait: 5 boot-file: boot-flags: boot-device: No referenced boot-file or boot-device appears. Setting the boot manager to defaults causes the boot manager to determine that no environment variables are set, and it responds by importing the defaults from the binary file. To set the boot manager to defaults, issue the set-defaults command at the boot manager prompt as shown in this example: BOOTMGR> set-defaults IP390 Security Platform Installation Guide 81

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
General Troubleshooting Information
IP390 Security Platform Installation Guide
81
Appliance Not Receiving Power
Problem
Power cord is not properly plugged in.
Solution
Check cord. Make sure it is properly seated at both ends.
Problem
Power supply not providing power.
Solution
Check power source. If there is no power at the source, take appropriate action such
as inserting a new fuse or resetting circuit breaker.
Appliance Does Not Recognize New Memory Configuration
Problem
DIMMs are not properly seated in DIMM sockets.
Solution
Repeat memory installation procedures. Make sure DIMMs are fully seated in
sockets. Be sure DIMMs click into place.
Appliance locks up after you upgrade Nokia IPSO with a console
connection. No error messages appear, but the appliance stops
responding to console and network.
Problem
During the upgrade process, some of the environment variables might not have
updated correctly.
Solution
You can verify what the current boot manager settings are by issuing a
printenv
command at the boot manager prompt, as shown in this example:
Loading boot manager ..
BOOTMGR[0]>
printenv
Bootmgr Revision: 3.3,base kernel=3.5.1-fcs1
02.12-2001-102644
autoboot: NO
bootwait: 5
boot-file:
boot-flags:
boot-device:
No referenced boot-file or boot-device appears.
Setting the boot manager to defaults causes the boot manager to determine that no environment
variables are set, and it responds by importing the defaults from the binary file. To set the boot
manager to defaults, issue the
set-defaults
command at the boot manager prompt as shown in
this example:
BOOTMGR>
set-defaults