EasyManua.ls Logo

Avaya 4500 - IPFM Device Configuration

Avaya 4500
33 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Avaya Inc. External Distribution
28
avaya.com
6.4 IPFM Device Configuration
6.4.1 The device status is always shown as "Inactive" in IPFM Dashboard
Make sure IPFIX Collector configuration in ERS switch is valid and flow data is forwarded to
IPFM server. Sometime there may be a routing issue in network. To validate flow data is
coming to IPFM server user can install Wireshark application in the same m/c where IPFM is
installed and check if flow data is coming there.
Make sure IPFM collector service is active and running.
Make sure that IPFM Collector service has received the device-add notification when user
added the ERS device IP in IPFM dashboard. To verify this user needs to open a console
window and go to IPFM Collectors log directory. Generally this directory can be located at:
For Windows C:\Program Files\Nortel\UCM\IPFM\ipfix_collector\log
For RHEL /opt/nortel/ucm/ipfm/ipfix_collector\log
Open ipfix_collector.log file using an editor and search for the specific Device IP with
"Registering" keyword.
If there is no such entry in log file, restart IPFM Collector Service so that it can load all Device
IP(s) from database and start listening traffic from those devices.
Note that the determination of a device being Active or Inactive is solely based on if IPFIX data is
received within the recent 20 minutes by IPFM server from the specific device.
6.4.2 After changing UDP port definition in IPFM UI, no new flow data is
received
Make sure the switch configuration has the same UDP port definition for exporting flow data.
Restart the IPFM collector service after changing the UDP port number.
On slower machines, it is possible that the IPFM collector service times out while
communicating to Jboss since Jboss service can take a longer time to properly complete its
initialization. In such scenario the devices in IPFM Dashboard will appear as "Inactive". To
resolve this issue, user must re-start IPFM Collector service manually after the Jboss service
has started successfully. User can use "Services panel" (in Windows platform) or CLI (in
RHEL) to restart Collector service.
6.4.3 User cannot invoke packet capture from IPFM UI
Packet capture feature is supported only by ERS 8600 device family.
Ensure that ERS 86XX device has Dual CPU (8692 cards).
Ensure that ERS 86XX device has set the boot config flag: "ha-cpu" to false. (Use "show
bootconfig flags" command to view the bootconfig flags)
Ensure that ERS 86XX device has set the boot config flag: "ftpd" to true. (Use "show
bootconfig flags" command to view the bootconfig flags)
Ensure that ERS 86XX device has set "File capture mode" to use "PCMCIA" device.(Use
"show diag pcap info" command to view the Pcap config flags).

Other manuals for Avaya 4500

Related product manuals