NJEDGE LISP TURNUP REQUIREMENTS

Member Responsibility

1. Member must have a valid Smartnet Contract and CCO account.

2. Provide number of current Service Provider connections and bandwidth requirements.

3. Supply output of show version from router to Cisco (Local Account Team or TAC).

a. This is used to determine platform compatibility (if it meets requirements then continue, if not, obtain qualified platform). If the member does not have correct software revision, obtain the name of current running image (“*.bin”) and the member’s account name from www.cisco.com so that Cisco will be able to publish the correct code for the member to download.

4. Review basic topology of member’s network. It may be necessary to provide a diagram.

5. Provide prefix information. If the prefixes are assigned by another Service Provider and have not been swiped by you, then an LOA is required to announce prefixes through NJEDge.

6. If not already in the NJEDge database, provide the WAN IP addresses.

7. Ensure that ICMP is time-exceeded and unreacheables are permitted through firewall
[NOTE: This procedure is only required for members that do not have end-to-end MTU of 1556 from xTR to PxTR, i.e. members who are not dual-attached to NJEDge.]

8. Member obtains code. (Provide CCO account to ensure proper posting of IOS image.)

9. Member schedules maintenance window and installs new code. The new IOS software must be in production at least two days prior to transition.

10. In the event that a member needs local support for IGP configuration or troubleshooting his IGP issue, he has the option to open a TAC case prior to the turn-up in the event. This will be unique primarily to multiple router/dual-attached members. However as of the writing of this guide, we will collect the necessary data and forward this information to the LISP-support group.

11. Member is solely responsible for ingress traffic from NJEDge router to core and egress traffic from core to edge.

12. Member installs script files provided by NJEDge or turn on SLA tracking. Members must validate the contents of the files as they are specific to their environment.

13. Member executes test plan during transition.

14. After transition, follow normal procedures one has always used for Network remediation.