cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
927
Views
0
Helpful
1
Replies

IOS XR 6.7.2 Configure Diameter Gy

maileh
Level 1
Level 1

Hi i have been trying to configure a diameter Gy Connection to our OCS platform but keep having these error.

Appreciate if anyone would help.

 

Here is my Diameter Config according to Cisco Doc.

 

diameter gy
diameter peer a.b.c.d
destination host a.b.c.d
transport tcp port 6553
destination realm www.domain.com
address ipv4 a.b.c.d
source-interface Loopback 50
ip vrf forwarding MANAGEMENT
diameter timer watchdog 300
diameter origin host my.router.loopback50 address
diameter origin realm www.domain.xy
diameter vendor supported cisco

 

I have these lines at the bottom of my logs

 

2020-10-12T14:13:35.111610+13:00 bng-1.kalianet.to 471064: RP/0/RSP0/CPU0:Oct 12 14:13:34.268 TOT: dumper[60]: %OS-DUMPER-6-REMOVE_OLDEST : Removing dump dumper_harddisk:/dumper/diameter_1122.20201012-124901.node0_RSP0_CPU0.ppc.Z as we can have only limited number of cores in fallback path
2020-10-12T14:13:35.123359+13:00 bng-1.kalianet.to 471066: RP/0/RSP0/CPU0:Oct 12 14:13:34.508 TOT: dumper[60]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 4(dumper_harddisk:/dumper) in use
2020-10-12T14:13:35.135327+13:00 bng-1.kalianet.to 471068: RP/0/RSP0/CPU0:Oct 12 14:13:34.518 TOT: dumper[60]: %OS-DUMPER-5-CORE_FILE_NAME : Core for process pkg/bin/diameter at harddisk:/dumper/diameter_1122.20201012-141334.node0_RSP0_CPU0.ppc.Z on local_node
2020-10-12T14:14:14.565594+13:00 bng-1.kalianet.to 471070: RP/0/RSP0/CPU0:Oct 12 14:14:14.557 TOT: dumper[60]: %OS-DUMPER-7-WRITE_FAILED : Write of size 434176 to fd 20 failed. Written -1. Error: No such process
2020-10-12T14:14:14.577673+13:00 bng-1.kalianet.to 471072: RP/0/RSP0/CPU0:Oct 12 14:14:14.557 TOT: dumper[60]: %OS-DUMPER-6-BAD_PATH : Choice 4(dumper_harddisk:/dumper) either not configured or bad path dumper_harddisk:/dumper/diameter_1122.20201012-141334.node0_RSP0_CPU0.ppc.Z at <3539>. Trying next choice.
2020-10-12T14:14:14.589599+13:00 bng-1.kalianet.to 471074: RP/0/RSP0/CPU0:Oct 12 14:14:14.558 TOT: dumper[60]: %OS-DUMPER-6-BAD_PATH : Choice 5(dumper_disk1a:/dumper) either not configured or bad path Fallback at <3447>. Trying next choice.
2020-10-12T14:14:14.872668+13:00 bng-1.kalianet.to 471076: RP/0/RSP0/CPU0:Oct 12 14:14:14.864 TOT: dumper[60]: %OS-DUMPER-6-REMOVE_OLDEST : Removing dump dumper_disk0a:/dumper/diameter_1122.20201012-113142.node0_RSP0_CPU0.ppc.Z as we can have only limited number of cores in fallback path
2020-10-12T14:14:15.372595+13:00 bng-1.kalianet.to 471078: RP/0/RSP0/CPU0:Oct 12 14:14:15.365 TOT: dumper[60]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 6(dumper_disk0a:/dumper) in use
2020-10-12T14:14:15.384626+13:00 bng-1.kalianet.to 471080: RP/0/RSP0/CPU0:Oct 12 14:14:15.372 TOT: dumper[60]: %OS-DUMPER-5-CORE_FILE_NAME : Core for process pkg/bin/diameter at disk0a:/dumper/diameter_1122.20201012-141415.node0_RSP0_CPU0.ppc.Z on local_node

 

And this is result from the semacntic error when commit the config

 

!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.


diameter origin host bng1.domain.xy
!!% The process 'diameter' unregistered before responding to a verification request
diameter origin realm www.domain.xy
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
diameter timer watchdog 300
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
diameter gy
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
diameter gy tx-timer 100
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
diameter vendor supported cisco
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
diameter peer myhostname
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
ip vrf forwarding MANAGEMENT
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
source-interface Loopback50
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
destination host remotehostname
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
transport tcp port 6553
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
destination realm www.domain.com
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
peer-type server
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verification or as an EDM without having previously registered'
address ipv4 remoteOCSipv4address
!!% 'sysdb' detected the 'warning' condition 'A SysDB client attempted to unregister for notification, verifica

 

1 Reply 1

maileh
Level 1
Level 1

anyone on the list have similar issue before ?

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: