infinite metric configured on the link causes to advertise with infinite/2 metric.

[sachinites]

root@juniper> $ conf node R0 int eth0/0 le 1 me /
Parse Success.

root@juniper> config-node-R0-interface-eth0/0-level-1-metric $ ?
Parse Success.
nxt leaf -> INT                               |   metric value [0 - 4294967295]

root@juniper> config-node-R0-interface-eth0/0-level-1-metric $ **4294967295**      _<< configure the infinite metric on link_
Parse Success.
SPF Stats : L1, Node : R0 : #Added:6, #Deleted:0, #Updated:0, #Unchanged:0
SPF Stats : L1, Node : R1 : #Added:6, #Deleted:0, #Updated:0, #Unchanged:0
SPF Stats : L1, Node : R2 : #Added:6, #Deleted:0, #Updated:0, #Unchanged:0

root@juniper> config-node-R0-interface-eth0/0-level-1-metric $ cd

root@juniper> $ show in node R0
Parse Success.
node->node_name : R0(192.168.0.1), L1 PN STATUS = NON_PSEUDONODE, L2 PN STATUS = NON_PSEUDONODE, Area = AREA1
backup-spf-options : DISABLED
Slots :
slot0 : eth0/0, L1 prefix : 10.1.1.1/24, L2 prefix : NIL/0, DIRN: OUTGOING, backup protection type : None
      L1 metric = **2147483647**, L2 metric = 0, edge level = LEVEL1, edge_status = UP
_>> metric configured is exactly half as shown in output_
slot1 : eth0/0, L1 prefix : 10.1.1.1/24, L2 prefix : NIL/0, DIRN: INCOMING, backup protection type : None
      L1 metric = 10, L2 metric = 0, edge level = LEVEL1, edge_status = UP

slot2 : eth0/1, L1 prefix : 30.1.1.1/24, L2 prefix : NIL/0, DIRN: OUTGOING, backup protection type : None
      L1 metric = 10, L2 metric = 0, edge level = LEVEL1, edge_status = UP

slot3 : eth0/1, L1 prefix : 30.1.1.1/24, L2 prefix : NIL/0, DIRN: INCOMING, backup protection type : None
      L1 metric = 10, L2 metric = 0, edge level = LEVEL1, edge_status = UP


LEVEL2 prefixes:
192.168.0.1/32(R0)
LEVEL1 prefixes:
192.168.0.1/32(R0)     10.1.1.1/24(R0)     30.1.1.1/24(R0)
FLAGS :
    IGNOREATTACHED : UNSET
    ATTACHED       : SET
    MULTIAREA      : UNSET
    Overload       : L1 : No, L2 : No
    Stub network interfaces :