Custom Query (1408 matches)

With certain hop exclusion list inputs, SCS returns a malformed VLAN Range for vlanRangeAvailability.

Sent options:

{'geni_routing_profile': {u'link': {'hop_exclusion_list': [u'urn:publicid:IDN+emulab.net+interface+procurveA:3.19=753,764,769,772,779,792,802,805,812,819,831,835,844,845,847,856,863,864,871,873,875,885,886,889,905,907,908,914,918,924,935,937,949,956,981-983,992,1000']}}}

Got back a range that was 865-999-999

The ION AM should

• ensure capacity is available as requested for each hop/link in the stitching extension (using the capacity property in the link if not supplied in the stitching extension)
• ensure compliance of the request with the capacity elements in the Ad (maximumReservableCapacity, minimumReservableCapacity, and granularity)
• pass along the capacity requested to the ION service

Circuit reservations are failing at the ION AM, since the latest code has been installed.

My note:

With the latest changes, my circuit request to ION failed with less
information than before:

{
 "geni_resources": [],
 "geni_urn": "urn:publicid:IDN+emulab.net+slice+ahtest",
 "geni_status": "failed"
}

I believe this was circuit 15021.

- Is there any more to the error message we can get?
- Can the sliver status include the circuit ID?
- Do we know why this particular request failed?

I tried again with a circuit 15041
{
 "geni_resources": [
   {
     "geni_urn":
"urn:publicid:IDN+emulab.net+sliver+ahtest_vlan_ion.internet2
.edu-15041",
     "geni_error": "",
     "geni_status": "changing"
   }
 ],
 "geni_urn": "urn:publicid:IDN+emulab.net+slice+ahtest",
 "geni_status": "failed"
}

At least this time I have the circuit ID. But how come the individual
resource is 'changing' and overall status is 'failed'? And why did it fail?

Chad said:

I restarted tomcat, and SFA.
I actually applied the 4.2 patch, and not patch-4. ( I did this earlier
in the day)

Should I undo the 4.2 patch and just apply the 4 patch?