Page 1 of 1
MDA provisioned incorrectly
Posted: 27 Aug 2013 18:13
by JFoster1977
I have a 7210 SAS-M with a DS1 MDA installed. The tech who provisioned it entered commands for provisioning another type of MDA. The DS1 MDA shows provisioned but the ops status is failed. The MDA was obviously not correctly provisioned, and the bof has been saved since initial config. How do I go about deleting the incorrect config out of the bof so that I can provision the MDA correctly?
Re: MDA provisioned incorrectly
Posted: 28 Aug 2013 03:35
by mivens
I think this bit from the SAS-M Interface Configuration Guide is what you're looking for:
Insertion and removal of CES MDA at any point of time into the system is supported, if the BOF parameter configuration is set to default.
In 7210 devices using 2 x 10G MDA, to insert CES MDA perform the following steps:
1. Configure the BOF parameter "use-expansion-card-type" to m4-ds1-ces. This will provision the system to expect a 4 x T1/E1 CES MDA for use in the expansion slot.
2. Configure the BOF parameter "no-service-ports" to default, if using a 7210 SAS-M 24F 2XFP and 7210 SAS-M 24F 2XFP ETR variants.
3. Re-boot the device.
Re: MDA provisioned incorrectly
Posted: 28 Aug 2013 11:32
by JFoster1977
Thanks for the quick reply. I'm looking forward to using this later in the day when I return to the project sites where this equipment has been deployed. I'll let you know what the results are. Again, thanks!
Re: MDA provisioned incorrectly
Posted: 28 Aug 2013 16:46
by JFoster1977
I discovered that my tech provisioned this to run off of the 10G ports instead of the 1 gig. Giving the *A:TID>bof# no-service-ports 1/1/25 1/1/26 will re enable the 1/1/23 and 1/1/24 ports for service and disable the 10g ports, but what else needs to happen in order for the up-link ports to be operational? Thanks again...