Motorola 49901 Software Release Notes - Page 35

Detailed Port Statistics - Incorrect State, Vanguard 6400 Series Event Log Port Information

Get Motorola 49901 - Vanguard 340 Router PDF manuals and user guides
UPC - 786523499018
View all Motorola 49901 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

Software Improvements Part No. T0001-42, Rev C October, 2002 Page 35 of 103 Figure 10 shows that the port statistics page reports the following conditions as the current port state: • Rx State = 0000 and Voice State = IDLE_UNCON - This means that the port has booted to the incorrect state. Figure 10. Detailed Port Statistics - Incorrect State If the Rx State = 0000 this means that: • the port has booted to an incorrect state • the port is not physically connected to a PBX Station or CO trunk This is fixed. Vanguard 6400 Series Event Log Port Information When a Vanguard 6455 is defaulted with an ISDN data card in slot 1 the node comes up and alarms appear in the event log for ports 51-53, even if a quad card is not installed. (Ports 51-53 are for the quad FXS/FXO card.) If you have a quad FXS port installed and configured in slot 2, and you remove this card and install a single FXO the log should show a problem. The node comes up, but there is no log that states "cannot boot ports 61-64 because of a hardware mismatch". (DRCaa23067) This is fixed. Vanguard 6455 PRI-DATA and PRI-Voice Alarm Errors Upon completion of a node boot, level one alarms are generated for every virtual port mapping table entry with Virtual Port Type configured as PRI-DATA or PRI-VOICE. Example: (1) 102 20-JUN-2001 08:25 Assert 897 vpmt.c (DRCaa22532) This is fixed.

  • 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
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
Part No. T0001-42, Rev C
October, 2002
Software Improvements
Page 35 of 103
Figure 10 shows that the port statistics page reports the following conditions as the
current port state:
•
Rx State = 0000 and Voice State = IDLE_UNCON - This means that the port
has booted to the incorrect state.
Figure 10. Detailed Port Statistics - Incorrect State
If the Rx State = 0000 this means that:
•
the port has booted to an incorrect state
•
the port is not physically connected to a PBX Station or CO trunk
This is fixed
.
Vanguard 6400 Series Event Log Port Information
When a Vanguard 6455 is defaulted with an ISDN data card in slot 1 the node comes
up and alarms appear in the event log for ports 51-53, even if a quad card is not
installed. (Ports 51-53 are for the quad FXS/FXO card.) If you have a quad FXS port
installed and configured in slot 2, and you remove this card and install a single FXO
the log should show a problem. The node comes up, but there is no log that states
“cannot boot ports 61-64 because of a hardware mismatch”. (DRCaa23067)
This is fixed
.
Vanguard 6455 PRI-DATA and PRI-Voice Alarm Errors
Upon completion of a node boot, level one alarms are generated for every virtual
port mapping table entry with Virtual Port Type configured as PRI-DATA or
PRI-VOICE. Example:
(1) 102 20-JUN-2001 08:25 Assert 897 vpmt.c
(DRCaa22532)
This is fixed
.