|
|
CiscoView s not supported in the 1.0 Cisco info Center release.
The following features were not tested in the 1.0 Cisco info Center release.
You can select from two architectures (multisystem and single system) for installation. Multisystem architecture, a fully distributed architecture, is the recommended architecture. For detailed information about installation, see the Cisco Info Center Installation and Configuration guide.
Table 1 lists the hardware requirements for the multisystem architecture.
| Application Type | Machine Type | Size of RAM | Hard Disk Drive | Operating System |
|---|---|---|---|---|
Info Server | Sun Ultra II | 256MB | 200MB | Solaris 2.5.1 |
Info Mediator | Sun Ultra II or higher | +64MB | +100MB | Solaris 2.5.1 |
Info Admin Desktop | Sun workstation | +48MB | +75MB | Solaris 2.5.1 |
Table 2 lists the hardware requirements for the single system architecture.
| Application Type | Machine Type | Size of RAM | Graphic Card Type | Hard Disk Drive | Operating System |
|---|---|---|---|---|---|
Info Server + Info Mediator + Info Admin Desktop | Sun Ultra II or higher
| 512MB | 24 bit | 350MB | Solaris 2.5.1 |
Cisco Info Center Release 1.0 works with HP Openview Release 4.11 on Solaris 2.5.1.
For HP OpenView installation requirements and procedures, see the HP OpenView Network Node Manager Products, Installation Guide.
This section contains general information, things to be cautious of, and limitations known to exist with the 1.0 release of Cisco Info Center.
This section contains information related to installing and configuring the 1.0 release of Cisco Info Center.
hosts: files
| Platform | Software | Firmware |
|---|---|---|
IPX/BPX | 8.4.x | Not applicable |
IGX | 8.2.5 | Not applicable |
AXIS | Not applicable | 4.0.x |
This section contains information related to the installation of the Cisco StrataView Plus Mediators.
This section contains information related to Cisco Info Center traps and alarms.
1. SWSW: Wrong card type as reported by SWSW maintlog. Some IPX cards are reported as BPX cards. ASI cards are reported as BXM and vice versa in 1000 series traps.
2. SWSW: Wrong source nodename as reported by SWSW maintlog occasionally. Some 1000 series traps sent to StrataView Plus contain an incorrect nodename.
3. SWSW: Inconsistent robust CD alarm generated by SWSW. The 20004 alarms sometimes contain an incorrect trap number (removed-no-backup-available for card insertion or card-standby when card is removed).
4. AXIS: 50003 traps (insert traps) with moduleState=4 (failed).
5. SWSW: CD alarm with Trapreason 3088 trap_type=0, unable to map by StrataView Plus. These unexpected trap_types cause StrataView Plus to map to a 0 fc_state and a wrong ObjectStatus is passed to Cisco Info Server.
6. SWSW: no "TRK Deactivated" eventlog (1000 series) is received from SWSW causing Trunk object deletion automation to fail.
7. AXIS: Axis sends 50301 traps with slot number = 125 and 124 causing erroneous slot number to be displayed when a BNM PLCP alarm occurs.
8. AXIS: Config change trap has no 9th varbind occasionally. You may observe (Unavailable parameter $9) in the trapd.log file. Cisco Info Center has logic to deal with this inconsistency. However, ObjectStatus is lost because of the missing varbind.
9. AXIS: delete a line and never receive a 50142 which causes SRM Line deletion automation not to work.
10. AXIS: same fw 4.0.09b, AUSM sends 50101, however, FRSM sends 50121 when line is in alarm state.
11. AXIS: Add lineloop on AUSM line, received a 50100 clear, however, as severity is Major, a 50101 line alarm should be received.
12. AXIS: Del lineloop on AUSM line, received a 50100 clear, however, as severity is Major, a severity Clear should be received.
13. AXIS: varbind $11 in 50400 contains the logical port no DS0 map, making the Decode bitmap display incorrect info.
14. AXIS: Trap 50400, trapPortActive received, however, PortState=Inactive in varbind. This inconsistency causes the ObjectStatus and the Summary to display inconsistent information.
15. AXIS: No 50405 trap when adding a FRSM port. Missing port added trap from AXIS.
16. StrataView Plus: frsm chan trap has been ignored (not forwarded to RtmProxy) by rtm. This causes end point deletion automation to fail. See the following Automation section for details.
17. AXIS: When receiving a 50905 (localloop disabled) trap, $8 tcAlarmState=128 when it should be 0.
18. SWSW: No port alarm 20004 when BXM port failed. SW reported card type 201 in port alarm message. StrataView Plus does not recognize this card type.
19. SWSW: peripheral alarm on BPX is inconsistent and cnfasm cannot be used to generate a peripheral alarm.
This section contains information related to Cisco StrataView Plus Informix OnLine database.
1. StrataView Plus Informix database name should be "stratacom".
This section contains information related to Cisco Info Center network configuration.
1. IPX/BPX/AXIS running 8.4.X and 4.0.X.
2. IGX running 8.2.5.
3. No UFM card support in 8.4.X.
4. no IGX feeder support.
This section contains information related to the Cisco StrataView Plus service and Network agents.
1. StrataView Plus Service and Network Agent should be installed and running. See the StrataView Plus Installation Guide for installation instructions.
2. StrataView Plus SNMPAgent must use default port 8161 for SNMP Trap Registration. Cisco Info Server uses port 8161 to communicate with Service and Network Agent.
This section contains information related to the Cisco Info Center Automation feature.
1. NElookup automation is disabled by default. It should be enabled.
2. 12-hour-Cleared and 24-hour-Deleted automation is disabled by default. You must enable it, when desired.
3. Delay in NEType, NEAddress lookup. After a cold start, an incoming event from a node may be tagged with an unknown NEType and an NEAddress with no value. You may experience a maximum delay of 60 seconds after the StrataView Plus node table is populated.
4. No automation to handle change of IP address. Currently, when a node has an NWIP address already configured, changing the IP address on the node does not trigger an update to the Cisco Info Server. This means all incoming events from that node still carry an old NEAddress. You can create tools to execute nco_sql to run update on a node when that node's IP address has changed.
5. Endpoint deletion automation does not work for AXIS endpoint deletion. When the master end point of a user connection is AXIS, the user connection alarm is not cleared by automation when the AXIS end point is deleted.
6. Object Deletion automation clears any events of the same ObjectType and updates the ObjectStatus and Severity as "Cleared". As designed. These "Cleared" traps will then be physically deleted by 12-hour-Cleared automation (when this automation is enabled).
This section contains information related to the Cisco Info Center Tools.
1. Intermittent failure on Tstcon/Tstdelay. Tstcon/tstdelay sometimes fail, however, they should reflect the result from ConnProxy. Check the /usr/users/svplus/log/ConnProxy.log file on the machine running the Mediators when you encounter Tstcon/tstdelay failure.
2. dsx3RcvEXZCounter in RTC tool displays "does not exist" error message. The AXIS dsx3 counter does not work on the SRM card, however, it works on the BNM card.
3. RTC Graph tool occasionally displays "no such name" error message. This is an HP Openview xnmgraph problem. Please check "Third Party Product Limitations Notes" section for details.
4. No line loopback support for BPX/AXIS. addlnloop is available in BPX and AXIS, however, this feature is not supported in this release.
5. Must have connectivity to StrataView Plus for all the tools to work. All nodes should be reachable from the StrataView Plus machine through IP-relay. The StrataView Plus gateway node should be LAN connected.
6. Equipmgr and NWBrowser invoked from the Desktop sub-event list menu may core dump.
This section contains miscellaneous information related to the Cisco Info Center.
1. getdate in a query needs spaces. When the getdate function is used in a subtraction, one character space must exist on either side of the minus sign, otherwise, the equation is not evaluated correctly. For example: getdate - 200.
Consult the Cisco Info Center Installation and Configuration guide.
This section contains information related to the third party applications Cisco Info Center works with.
1. Xnmgraph occasionally displays "no such name" or "wrapped (0->0). Waiting for next" even though the data is available, as tested by xnmbrowser.
2. Xnmgraph displays an incremental statistics value which is not consistent with the Text counter display.
Cisco Info Center 1.0 operates with the following:
This section contains information about the known Cisco Info Center issues.
AXIS name and IP address not shown in Event List after feeder deletion.
Resolution: BPX traps limitation. Will be resolved in Cisco StrataView Plus Release 9.2.
CDP Card insert/remove identifies it as BNI-E3 card
Resolution: SWSW trap error. Defect forwarded to SWSW.
Functional module type val=1 (other) should be FRSM-4E1.
Resolution: AXIS trap error. Defect forwarded to AXIS.
AXIS: addln Line enabled Severity minor - should be warning.
Resolution: AXIS trap error. Defect forwarded to AXIS.
ObjectType should distinguish between physical, virtual, and feeder trunks.
Resolution: Limitation on 1000 series traps. Will be fixed in Cisco StrataView Plus Release 9.2.
xnmgraph of RTC displays values as delta/duration.
Resolution: HP NNM xnmgraph limitation.
Problem during configuration with NIS+, DNS environment.
Resolution: Will be fixed in Cisco Info Center Release 2.0. See "SV+ Mediators" section for details.
Generate clear power supply alarm 4004 ifc shows BNI-T3 removed.
Resolution: BPX trap error. Defect forwarded to SWSW.
ifc could not display 4002 power fail alarm from IPX.
Resolution: BPX trap error. Defect forwarded to SWSW.
Missing local end point on connection deletion - endpoint.FR.
Resolution: SV+ RTM limitation. Will be fixed in Cisco StrataView Plus Release 9.2.
Change Port Protocol Type from GUI ifc shows ObjectStatus Unknown.
Resolution: AXIS trap error. Defect forwarded to AXIS.
RTC counters display zeros for BXM trunks carrying ATM traffic.
Resolution: BPX counter error. Defect forwarded to SWSW.
AXIS: no line.trunk event for BNM-155 card.
Resolution: AXIS error. Defect forwarded to AXIS.
xnmgraph doesn't display for line alarm events on AUSM-8E1.
Resolution: HP OV NNM xnmgraph error. Defect forwarded to HP.
Test Delay doesn't work for VPC connection.
Resolution: Will be fixed in Cisco Info Center Release 1.1.
No card insert trap for SRM-3T3 and SRM-4T1E1 (trap reason=50003).
Resolution: Axis Trap error. Defect forwarded to AXIS.
FRSM-4E1: No line.access events for line addition/deletion.
Resolution: Axis Trap error. Defect forwarded to AXIS.
FRSM-8T1: No line.access events for line deletion.
Resolution: Axis Trap error. Defect forwarded to AXIS.
CE-CE connection displayed as ATM-ATM.
Resolution: SV+ Error. Defect forwarded to SV+.
Logical Port displayed as "-" when adding a port on IGX.
Resolution: SWSW 1000 series trap limitation. Defect forwarded to SWSW.
SubObjectType is AIT.UNKOWN for BTM trunks.
Resolution: SWSW error. Defect forwarded to SWSW.
IGX (9.2.7.2) Get_Config displays BC as present for missing BC.
Resolution: SV+ error. Defect forwarded to SV+.
UFM cards are not recognized by IGX 8.4.20.
Resolution: SWSW error. Defect forwarded to SWSW.
Problem displaying full Info Server name in the GUI.
Resolution: Will be fixed in Cisco Info Center Release 2.0.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Posted: Wed Mar 24 15:04:16 PST 1999
Copyright 1989-1999©Cisco Systems Inc.